Re: Info from HTML5 editors: merging WHATWG patches

On Fri, Sep 14, 2012 at 5:21 AM, Arthur Barstow <art.barstow@nokia.com> wrote:
> On 9/13/12 4:00 AM, ext Silvia Pfeiffer wrote:
>>
>> I followed Ian's keywords in his commits for classification of these
>> patches. I've isolated this in its separate branch because I don't
>> know if it should go into the source document. It seems the patches
>> just fix some cross-references and resurrect the ArrayBuffer argument.
>
>
> Yes, following the "keywords" is a good start but unfortunately, a diff may
> include changes for more than one of the keywords (sections) :-(.
>
>
>> To be honest, I don't even know if this part ends up in the final
>> HTML5 document, since there is some filtering happening from the
>> source document to the result. So, it may be safe to completely ignore
>> this.
>>
>> I'm not across that part of the HTML specification nor the WebSocket
>> specification. If you are, would you mind following the given URL and
>> let me know if it contains appropriate changes to the HTML
>> specification?
>
>
> I scanned those changes again. It appears to me that most of the changes are
> for the WebSocket API and Web Workers specs (and those would presumably not
> be applied to W3C's HTML5). However, it also appears at least some of the
> changes are for the HTML5 spec; f.ex. the addition of lines 4028-4033
> (complete.html).
>
> (Perhaps the line numbers will give you a clue as to which
> part/section/keyword  they apply).

So, what you're saying is that the first part that applies to the
WebSocket API is harmless for us to apply since it doesn't get
rendered into the HTML spec (and our file is not the basis for any
other spec than the HTML and the Canvas spec).

What about the second part the? I checked
http://dev.w3.org/html5/websockets/ and it contains ArrayBuffer. I
assume for consistency it would be good to apply it then?

Thanks for your help.

Cheers,
Silvia.

Received on Friday, 14 September 2012 00:02:39 UTC