Forwarded message 1
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
Konrad
--
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]