- From: Boris Zbarsky <bzbarsky@MIT.EDU>
- Date: Thu, 23 Jun 2011 12:24:04 -0400
- To: Julian Reschke <julian.reschke@gmx.de>
- CC: Adam Barth <ietf@adambarth.com>, Chris Weber <chris@lookout.net>, public-iri@w3.org
On 6/23/11 12:15 PM, Julian Reschke wrote:
> Their resolution is IMHO clearly described in RFC 3986; could you be a
> bit more specific about what your concern is?
My concern is RFC 3986 section 4.4, which says:
When a URI reference refers to a URI that is, aside from its fragment
component (if any), identical to the base URI (Section 5.1), that
reference is called a "same-document" reference.
and then says:
When a same-document reference is dereferenced for a retrieval
action, the target of that reference is defined to be within the same
entity (representation, document, or message) as the reference
What that means is that it's impossible to implement section 4.4 by
canonicalizing all URIs into absolute URIs. All URIs used by a system
have to remember whether they were "same-document" references (which you
only know at URI creation time) and if so need to know what document
they're associated with to be properly retrieved.
This is not interoperably implemented by UAs, last I checked, and you
were asking about things that cause interop problems.
-Boris
P.S. I also happen to think that the requirements of section 4.4 are
insane, which is why there is no interop on it.
Received on Thursday, 23 June 2011 16:24:33 UTC