W3C home > Mailing lists > Public > www-rdf-interest@w3.org > July 2001

Re: syntax-question-id-about

From: Aaron Swartz <me@aaronsw.com>
Date: Wed, 11 Jul 2001 13:11:36 -0500
Cc: RDF interest group <www-rdf-interest@w3.org>
To: Stefan Kokkelink <skokkeli@mathematik.uni-osnabrueck.de>
Message-Id: <20010711181136.NQKR21617.femail17.sdc1.sfba.home.com@localhost>
On Wednesday, July 11, 2001, at 01:04  PM, Stefan Kokkelink wrote:

> suppose I have an RDF Schema at http://purl.org/dc/elements/1.1/,
> (that means: base URI = "http://purl.org/dc/elements/1.1/")
> defining (in that document!):
> <rdf:Description ID="title">
> ...
> </rdf:Decsription>
> The resulting URI for this property is
> http://purl.org/dc/elements/1.1/title,
> right?
> If this is true and rdf:ID="..." is equivalent to 
> rdf:about="#...", then
> <rdf:Description about="#title"> should result in
> http://purl.org/dc/elements/1.1/title too.
> Hm, am I missing something?

Apparently you are. Stating rdf:ID="foo" is the same as 
rdf:about="#foo" so you're using the relative URI "#foo". If you 
were to join this with any base URI, it would add #foo to the 
URI if there was no fragment, otherwise it would replace the 
fragment already there.

Here are some examples:

<#foo> and <http://purl.org/dc/elements/1.1/> => 

<#foo> and <http://purl.org/dc/elements/1.1/#bar> => 

This is implemented by many software packages, I keep a list at:


There's nothing RDF-special about this -- it's how URIs work. 
They work the same way in your web browser too.

       "Aaron Swartz"      |           Blogspace
  <mailto:me@aaronsw.com>  |  <http://blogspace.com/about/>
<http://www.aaronsw.com/> |     weaving the two-way web
Received on Wednesday, 11 July 2001 14:11:44 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:44:31 UTC