Re: parsing URI (references) according to RFC 3986

On 6/23/11 1:02 PM, Julian Reschke wrote:
> Is your concern that not all kinds of normalization are allowed?

No, not at all.

My concern is that the entire section is not really something that 
belongs in a URI spec.  See below.

>> 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.
>
> There isn't? I think we need more examples.

<img src="#foo"> doesn't follow section 4.4 in any browser I'm aware of, 
as one example.  Nor should it, imo.

I think the best course of action here is to remove 4.4 altogether and 
let specifications that actually have a concept of "document" define 
what should happen with URIs in various circumstances instead of trying 
to create blanket definitions and behavior prescriptions that don't 
actually work in many situations.

-Boris

Received on Thursday, 23 June 2011 17:07:08 UTC