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?
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
Received on Fri May 06 2005 - 14:16:07 EDT