- From: Joseph Holsten <joseph@josephholsten.com>
- Date: Tue, 23 Feb 2010 22:55:06 -0600
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: Lachlan Hunt <lachlan.hunt@lachy.id.au>, uri-review@ietf.org, public-html <public-html@w3.org>, URI <uri@w3.org>
On Feb 23, 2010, at 7:08 AM, Julian Reschke wrote:
> Base URI: <about:config>
>
> Reference: <#foo>
>
> According to RFC 3986, Section 5, these are parsed into the components scheme, authority, path, query, fragment:
>
> Base URI: ("about", undefined, "config", undefined, undefined)
>
> Reference: (undefined, undefined, undefined, undefined, "foo")
>
> According to <http://greenbytes.de/tech/webdav/rfc3986.html#rfc.section.5.2.2>, the resulting resolved URI would have the following components:
>
> ("about", undefined, "config", undefined, "foo")
>
> Recomposition according to <http://greenbytes.de/tech/webdav/rfc3986.html#rfc.section.5.3> yields:
>
> <about:config#foo>
>
> So I don't see a problem here. Am I getting this wrong?
Nope, I simply misunderstood the recomposition code. I kept imagining that it would append "//" after the scheme. No doubt I was confusing an undefined authority with an authority of "".
I should note that at least one set of about URIs will act funny with reference parsing, those with a colon in the segment, say "about:foo:bar". When parsed by the <URI> rule, it's (scheme: "about", path-rootless: "foo:bar"). But a reference from a base URI of "about:config" to reference "foo:bar" would not match entirely into the <relative-part> rule, as it is not a <path-noscheme>. Any URI with a <path-rootless> that contains colons will not match <path-noscheme>, and so will have this issue. I assume this is a known issue to people who work with URNs often. It seems harmless not to mention it, right?
I've removed the section about Relative URIs (ugh). Thanks for suggesting this and walking me through it.
It seems all that's left is text clarifying what is involved with reserving an about URI.
--
j
Received on Wednesday, 24 February 2010 04:55:44 UTC