Re: parsing URI (references) according to RFC 3986

On 6/23/11 2:05 PM, Boris Zbarsky wrote:
> Consider the following HTML documents:

And to be clear, I definitely think that the HTML spec should define 
behavior here, whatever that behavior is.  But it's not clear how it can 
do this without conflicting with whatever the heck section 4.4 is 
talking about, because it's not clear what 4.4 is supposed to mean in 
various contexts.

On its face, either a URI is just a string (in which case it doesn't 
matter where it came _from_ and what happens when you do things with it 
should just be covered by the spec that defines said things and has no 
place in the URI RFC) or a URI has some sort of additional metadata 
attached to it about being a same-document reference (or not) as 4.4 
seems to imply.  Which is it?

-Boris

Received on Thursday, 23 June 2011 18:12:16 UTC