W3C home > Mailing lists > Public > public-xml-core-wg@w3.org > June 2006

[Konrad Lanz] Re: Canonicalization xml:base processing

From: Henry S. Thompson <ht@inf.ed.ac.uk>
Date: Thu, 01 Jun 2006 11:22:21 +0100
To: public-xml-core-wg <public-xml-core-wg@w3.org>
Message-ID: <f5bfyipjhuq.fsf@erasmus.inf.ed.ac.uk>

attached mail follows:

Richard Tobin wrote:
> [...]
> The base URI is file://three/four/a.file, but any use of it to resolve
> a relative URI will involve throwing away the "a.file" bit.  The first
> step of the resolution algorithm throws away everything after the last
> slash in the base URI.  So it has the same effect as if it were
> file://three/four/ .
I'm not sure this is true as RFC 2396 section 5.2 step 2) is as follows:

   2) If the path component is empty and the scheme, authority, and
      query components are undefined, then it is a reference to the
      current document and we are done.  Otherwise, the reference URI's
      query and fragment components are defined as found (or not found)
      within the URI reference and not inherited from the base URI.


The first sentence is true for a relative uri reference such as #bare-name.
And the reverse of the second sentence implies either that the 
"a.file" bit has an effect.

An alternative interpretation is that #bare-name = ""+#bare-name and does not 
inherit anything at all from xml:base, which is not very reasonable from my point of view.

best regards

 Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
                     Half-time member of W3C Team
    2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
            Fax: (44) 131 650-4587, e-mail: ht@inf.ed.ac.uk
                   URL: http://www.ltg.ed.ac.uk/~ht/
[mail really from me _always_ has this .sig -- mail without it is forged spam]
Received on Thursday, 1 June 2006 10:22:34 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:16:36 UTC