Re: [hybi] Opera's Pre-Last Call review of websocket -06

[Julian Reschke <[e-mail]>]

On 04.04.2011 14:42, Simon Pieters wrote:
> ...
>> The term "URI" is used in this section in a manner consistent with
>> the terminology used in HTML, namely, to denote a string that might
>> or might not be a valid URI or IRI and to which certain error
>> handling behaviors will be applied when the string is parsed.
>> [RFC3986]
>
> HTML calls it "URL", so doesn't seem particularly consistent.
> ...

All remaining references to how HTML5 uses URIs should simply be 
removed; including the specific text about parsing and resolving.

 > ...
>> 6. Error Handling
>> 6.1. Handling errors in UTF-8 from the server
>> When a client is to interpret a byte stream as UTF-8 but finds that
>> the byte stream is not in fact a valid UTF-8 stream, then any bytes
>> or sequences of bytes that are not valid UTF-8 sequences must be
>> interpreted as a U+FFFD REPLACEMENT CHARACTER.
>
> Maybe use the HTML spec's definition of UTF-8 with error handling:
> http://www.whatwg.org/specs/web-apps/current-work/complete/infrastructure.html#decoded-as-utf-8,-with-error-handling

I recommend avoiding any normative reference to HTML5. The text above 
appears to be simple enough standalone.


 > ...

Best regards, Julian