Lloyd.Rutledge_at_cwi.nl wrote:
> Actually, I'd be happy simply with a better label to the resource itself.
> Sesame's explore mode has "visit this resource on the Web" as the
> link text, slightly better (I think) than the URI. I like Semame's
> approach: one button with one label that means the same thing in each
> display. Though I could use a smaller label, such as "document web"
> or "media web".
>
> In a semantic display, this button takes you to the same point in the
> "Document Web". Similarly, you have one button with one label to take
> you from any Document Web display to the Semantic browser display of
> the meta data for that document. Thus you switch between two browsing
> worlds, both with portals at the document resources.
I hadn't considered this. We could have an additional vocabulary element
for this, in the non-presentational part of Fresnel styles. What do you
think?
> In Noadster papers we've stated that a browswer can check the
> mimetype of a resource to know if it a media resourse, and thus give
> such a button, or a conceptual resource, and offer no such button.
>
> Originally, Noadster displayed both the media/document and metadata
> together. Worked well for small and medium-sized images, which would
> appear as part of the display. Large images and documents would not
> work so well, so we stopped the approach.
>
> -Lloyd
>
>
>>Emmanuel Pietriga wrote:
>>
>>
>>>>That URI http://www.bizer.de shouldn't be interpreted as a RDF
>>>>Resource,
>>>>meaning that the browser looks in the repository for information
>>>>about the
>>>>resource, but as an external UR*L* which is retrieved and displayed.
>>>
>>>Isn't the browser smart enough to figure that out by itself?
>>
>>Jacco van Ossenbruggen wrote:
>>
>>Nope. There could be loads of interesting RDF metadata attached to
>>http://www.bizer.de, so the user might be interested in viewing
>>http://www.bizer.de as a concept in the RDF repository. But in other
>>cases the user might want to browse to the page itself.
>>
>>We encountered this problem in Noadster too. The current "solution" is
>>that for the current focal point, we add a link at the bottom of the
>>page that links to the uri itself (and not to another Noadster page
>>displaying information about the resource with that URI). We use the
>>URI itself as the anchor of the link. We never liked this solution
>>ourselves.
>>
>>Lloyd wanted to remove this feature completely, because in many cases
>>the URI provides no clue about the destination of the link. In
>>addition, most pages have a URI as a focal point that only exists as the
>>URI of an RDF resource, and resolving it results in an non-existing page
>>(often) or leads to the source RDF file defining the page (only slightly
>>better). Only RDF-literate users would understand this behavior,
>>another good reason Lloyd wanted to delete this feature.
>>
>> I only argued for including it because it is the only general way to
>>"get out" of the system and go to the Web - an important aspect of a
>>SemWeb application.
>>
>>So I would be in favor of adding a hint that allows an application to
>>make a clever decision about offering only a link to repository
>>information about the URI, a link to the URI itself or both. It would
>>make me happy, because it allows me to offer sensible "exit" links when
>>appropriate, and it would make Lloyd happy becuase it would remove all
>>those nonsense links with ugly anchors.
>>
>>Jacco
--
Emmanuel Pietriga
INRIA Futurs - Projet In Situ tel : +33 1 69 15 34 66
Bat 490, Université Paris-Sud fax : +33 1 69 15 65 86
91405 ORSAY Cedex http://www.lri.fr/~pietriga
Received on Mon May 09 2005 - 08:49:29 EDT