- From: Graham Klyne <GK@ninebynine.org>
- Date: Thu, 22 Jun 2006 08:34:24 +0100
- To: Dan Connolly <connolly@w3.org>
- CC: www-rdf-comments@w3.org
Dan, I agree with the test case, or I'm missing your point. Why do you think one might get "http:reluri"? The base URI contains an authority component, which as I understand it is required to be part of the expanded relative URI. At: http://www.gbiv.com/protocols/uri/rfc/rfc3986.html#components Note that the leading '//' always indicates an authority component present, which may be followed by an empty path or '/' -- there a special case in the syntax to cover the empty path. Also, ins ection 5.3.2, we have "If the base URI has a defined authority component and an empty path, then return a string consisting of "/" concatenated with the reference's path; otherwise, ..." #g -- Dan Connolly wrote: > In developing an RDF/XML parser in Javascript for the tabulator[1], > > We tripped over this test case: > > http://www.w3.org/2000/10/rdf-tests/rdfcore/xmlbase/test011.rdf > http://www.w3.org/2000/10/rdf-tests/rdfcore/xmlbase/test011.nt > associated with issue > http://www.w3.org/2000/03/rdf-tracking/#rdfms-xml-base > in http://www.w3.org/TR/2004/REC-rdf-testcases-20040210/ > aka http://www.w3.org/TR/rdf-testcases/ > > > It seems to say that in the case of xml:base declarations of > things like "http://www.example.com" we get > "http://www.example.com/reluri" instead of "http:reluri". > > That seems to be add odds with the URI spec > > http://www.gbiv.com/protocols/uri/rfc/rfc3986.html#relative-base > > > [1] http://dig.csail.mit.edu/2005/ajar/ajaw/About.html > -- Graham Klyne For email: http://www.ninebynine.org/#Contact
Received on Thursday, 22 June 2006 08:15:39 UTC