W3C home > Mailing lists > Public > www-xml-linking-comments@w3.org > April to June 2002

RE: Resolving references against base URIs

From: Martin Duerst <duerst@w3.org>
Date: Thu, 9 May 2002 22:21:02 -0400 (EDT)
Message-Id: <>
To: Brian McBride <bwm@hplb.hpl.hp.com>, Paul Grosso <pgrosso@arbortext.com>, Al Gilman <asgilman@iamdigex.net>, "Jeremy Carroll" <jjc@hplb.hpl.hp.com>, "Williams, Stuart" <skw@hplb.hpl.hp.com>
Cc: <www-xml-linking-comments@w3.org>, <uri@w3.org>
At 18:15 02/04/15 +0100, Brian McBride wrote:

>First: the problem RDF is trying to solve.  The current RDF specs have 
>encouraged the use of the following idiom:
>   <rdf:Description rdf:about="#foo">
>     ...
>The value of the rdf:about attribute is turned into an absolute URI 
>reference by concatenating the '#foo' with the URI of the containing document.
>This causes problems.  Folks copy the file from the web to their hard 
>drive so they can work on it in a plane, and the uri changes to something 
>like file:c:\temp\....rdf and this is really useless for rdf users.

There are two cases:

A) RDF documents (i.e. Content-Type: application/rdf+xml)

If you have: <rdf:Description ... rdf:about="#foo">

Then you *may* want the #foo to refer to whatever application/rdf+xml
says, and may ideally want to say that #foo refers to <xml:base#foo.

B) RDF embedded in other documents (XHTML, SVG,...):

Here the meaning of the fragment identifier is defined by the format
these fragment identifiers appear in. If you have

              <rdf:Description ... rdf:about="#section1">

then #section1 refers to e.g. Section 1 of the the HTML document in
front of you, independent of xml:base, and you don't want to change

Regards,    Martin.
Received on Saturday, 11 May 2002 10:46:20 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:08:14 UTC