Re: Relative URI resolution and fragments: editorial comment from Roy T.Fielding on 2004-07-15 (uri@w3.org from July 2004)

From: Roy T.Fielding <fielding@gbiv.com>
Date: Wed, 14 Jul 2004 21:08:21 -0700
To: Elliotte Harold <elharo@metalab.unc.edu>
Cc: uri@w3.org
Message-Id: <9C3A47F4-D614-11D8-81D2-000393753936@gbiv.com>

On Saturday, June 19, 2004, at 09:06  AM, Elliotte Harold wrote:
> One thing I noticed while doing so surprised me. The fragment ID of 
> the base URI reference is never considered. Even if you're resolving a 
> URI such as "" (the empty string) against a URI such as 
> http://www.example.com/test#fragID the resolved URI is 
> http://www.example.com/test.
>
> This isn't a problem, and I can see the sense of making URI resolution 
> work that way. However, it did surprise me. If there's any epxlicit 
> language in the spec that notes this, I didn't find it. I suggest 
> adding a sentence to section 5.2 that makes this epxlicit; something 
> like "The fragment in the base URI is ignored" or "The fragment in the 
> base URI always comes from the relative URI,never the base URI."

I have added the following to the first para of 5.1:

   A base URI must conform to the &lt;absolute-URI&gt; syntax rule
   (<xref target="absolute-uri"/>): if the base URI is obtained from a
   URI reference, then that reference must be converted to absolute form
   and stripped of any fragment component prior to use as a base URI.

....Roy

Received on Thursday, 15 July 2004 00:08:22 UTC