- From: Graham Klyne <Graham.Klyne@MIMEsweeper.com>
- Date: Wed, 13 Mar 2002 17:18:18 +0000
- To: Dave Beckett <dave.beckett@bristol.ac.uk>
- Cc: Jeremy Carroll <jjc@hplb.hpl.hp.com>, w3c-rdfcore-wg <w3c-rdfcore-wg@w3.org>
At 12:06 PM 3/13/02 +0000, Dave Beckett wrote:
>Isn't this implying (since it is an error case) that RDF applications
>have to validate URI-refs or at least know some non-hierarchical uri
>schemes. I understand RDF apps need to do relative URI resolution
>but until the xmlbase test cases, we never checked that they worked
>right.
>
>We seem to be sort-of generating test cases for other specifications
>(RFC 2396, xml base) which we generally shouldn't be doing :)
IIRC, RFC 2396 is crafted so that the non-hierarchical schemes can be
detected syntactically; i.e. the base URI doesn't start with a "/"
immediately following the schema name. If the scheme name is followed
immediately by a '/' then it's hierarchical.
[Follow-up]
Here's the relevant syntax from RFC 2396:
[[[
URI-reference = [ absoluteURI | relativeURI ] [ "#" fragment ]
absoluteURI = scheme ":" ( hier_part | opaque_part )
relativeURI = ( net_path | abs_path | rel_path ) [ "?" query ]
hier_part = ( net_path | abs_path ) [ "?" query ]
opaque_part = uric_no_slash *uric
uric_no_slash = unreserved | escaped | ";" | "?" | ":" | "@" |
"&" | "=" | "+" | "$" | ","
net_path = "//" authority [ abs_path ]
abs_path = "/" path_segments
rel_path = rel_segment [ abs_path ]
]]]
#g
-------------------
Graham Klyne
<GK@NineByNine.org>
-------------------
Graham Klyne
<GK@NineByNine.org>
Received on Wednesday, 13 March 2002 12:19:04 UTC