W3C home > Mailing lists > Public > www-tag@w3.org > November 2011

RE: URL/URI/IRI resolution in HTML5/RDF/RDFa

From: Larry Masinter <masinter@adobe.com>
Date: Fri, 4 Nov 2011 12:21:07 -0700
To: "julian.reschke@gmx.de" <julian.reschke@gmx.de>, Jeni Tennison <jeni@jenitennison.com>
CC: "www-tag@w3.org List" <www-tag@w3.org>
Message-ID: <C68CB012D9182D408CED7B884F441D4D06061B198A@nambxv01a.corp.adobe.com>
It might be more useful to focus on the IRI processing spec than patching the text in HTML that should be removed.


-----Original Message-----
From: Julian Reschke [mailto:julian.reschke@gmx.de] 
Sent: Friday, November 04, 2011 1:51 AM
To: Jeni Tennison
Cc: www-tag@w3.org List
Subject: Re: URL/URI/IRI resolution in HTML5/RDF/RDFa

On 2011-11-03 19:44, Julian Reschke wrote:
> On 2011-11-03 19:22, Jeni Tennison wrote:
>> Julian,
>>
>> (I wasn't ignoring what you wrote, just wanted to check it out, hence 
>> the delay :)
>>
>> On 2 Nov 2011, at 15:11, Julian Reschke wrote:
>>> 2) "\" and "/":
>>>
>>> 2a) The uniform treatment of "\" hasn't agreement; for instance, 
>>> Firefox does it only for file URIs (as far as I recall).
>>>
>>> 2b) That being said, "\" doesn't appear in syntactically valid URIs 
>>> or IRIs anyway, so maybe we can ignore the question; it won't affect 
>>> any valid URI/IRI anyway.
>>
>>
>> That being the case, how would any URL that contained a "\" get to 
>> step 12 of the HTML5 resolution algorithm [1] where they're swapped 
>> for "/"s given that step 10 says (I think!) that syntactically 
>> invalid URI/IRIs will raise an error and stop the resolution?
>> ...
>
> That appears to be a bug (or a feature, depending on p.o.v.).
> ...

Raised as <http://www.w3.org/Bugs/Public/show_bug.cgi?id=14693>.

Best regards, Julian
Received on Friday, 4 November 2011 19:21:53 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 26 April 2012 12:48:40 GMT