Re: aftermath on Bug 8953 URL decomp. IDL attributes when parsing fails

On 18.02.2010 22:54, Ian Hickson wrote:
> ...
>> For now it's not, until you change the spec's reference.
> So if I write a draft that redefines HTTP, and then make HTML refer to
> that draft instead of the HTTP spec, you'd argue that HTTP is in scope for
> this group?
> ...

Not helpful.

I thought we have agreed that we *want* IRIbis to become a replacement 
for WEBADDRESSES. To get there, it's essential to understand what it 
says, and why it does so.

You wrote the algorithms in there (as far as I know), so I am asking 
you. Why does it matter on which mailing list I ask?

>> That being said -- what do you *want* IRIbis to define here? As the UAs
>> do not implement what you specified I'm wondering what the rational for
>> this special case could be.
> So long as it's defined and compatible with legacy content, I don't really
> care what the spec says. In general I would encourage making things as
> simple as possible, but I don't know what that means in this case.

In this case it would mean removing the special case in step 3 of 
Section 2 of <>. So, instead of:

"If w begins with either of:

     * a string matching the <scheme> production, followed by "://"
     * the string "//"

then percent-encode any left or right square brackets (U+005B, U+005D, 
"[" and "]") following the first occurrence of "/", "?", or "#" which 
follows the first occurrence of "//".

Otherwise, percent-encode all left and right square brackets."

it would simply be:

"Percent-encode all left and right square brackets."

That would make the web address mentioned in 


an "absolute URL" (in HTML5 speak).

In particular I *believe* it means that "parsing a Web address" would 
never fail.

Best regards, Julian

Received on Thursday, 18 February 2010 22:06:54 UTC