W3C home > Mailing lists > Public > www-rdf-interest@w3.org > March 2004

Re: pound sign vs. slash as final URI delimiter

From: Janne Saarela <janne.saarela@profium.com>
Date: Sat, 20 Mar 2004 13:57:47 +0200
Message-ID: <405C31BB.1030407@profium.com>
To: www-rdf-interest@w3.org

Coming back to this thread after a while...

> Just say no to "#".

I just ran across RDF schemas that use xml:base attribute
with a URI that ends with a # character.

It appears the RDF test cases [1] do not address this
issue or deliberately avoid use of it. I was browsing
through old documents from RDF Core WG discussions
but couldn't find out why this type of test is missing.

Let me demonstrate a sample schema:

<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
          xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
          xml:base="http://www.schemas.org/music#">

<rdfs:Class rdf:ID="Artist" />

</rdf:RDF>

Is this supposed to produce triple:

S:http://www.schemas.org/music#Artist
P:http://www.w3.org/1999/02/22-rdf-syntax-ns#type 
O:http://www.w3.org/2000/01/rdf-schema#Class

or

S:http://www.schemas.org/Artist
P:http://www.w3.org/1999/02/22-rdf-syntax-ns#type 
O:http://www.w3.org/2000/01/rdf-schema#Class

I believe the former but RFC239 [3] suggests
the relative URI (Artist) is resolved against the base
URI by omitting characters after the last slash (/)
resulting in http://www.schemas.org/Artist. Which one
is now right?

Janne

[1] http://www.w3.org/TR/2004/REC-rdf-testcases-20040210/#tc_cert
[2] http://www.w3.org/TR/2001/REC-xmlbase-20010627/#resolution
[3] http://www.ietf.org/rfc/rfc2396.txt
-- 
Janne Saarela <janne.saarela@profium.com>
Profium, Lars Sonckin kaari 12, 02600 Espoo, Finland
Received on Saturday, 20 March 2004 06:57:56 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 18 February 2014 13:20:07 UTC