Re: [apps-discuss] Fwd: Willful violation of RFC in HTML5

[Eric Burger <[e-mail]>]

Does a willful violation result in twice as much jail time?

On Jul 25, 2011, at 10:55 AM, Mark Nottingham wrote:

> FYI.
> 
> Begin forwarded message:
> 
>> From: Philippe Le Hegaret <[e-mail]>
>> Date: 25 July 2011 9:34:12 AM EDT
>> To: Mark Nottingham <[e-mail]>
>> Cc: Thomas Roessler <[e-mail]>
>> Subject: Willful violation of RFC in HTML5
>> organization: World Wide Web Consortium
>> 
>> Hi Mark,
>> 
>> here are links to the willful violation of RFCs in HTML5. if you prefer
>> this email to be archived somewhere, let me know.
>> 
>> [[
>> This step is a willful violation of RFC 3986, which would require base
>> URL processing here. This violation is motivated by a desire for
>> compatibility with legacy content. [RFC3986]
>> ]]
>> http://www.w3.org/TR/html5/association-of-controls-and-forms.html#form-submission-algorithm
>> 
>> [[
>> This is a willful violation of RFC 2046, which requires all text/* types
>> to only allow CRLF line breaks. This requirement, however, is outdated;
>> the use of CR, LF, and CRLF line breaks is commonly supported and indeed
>> sometimes CRLF is not supported by text editors. [RFC2046]
>> ]]
>> http://www.w3.org/TR/html5/offline.html#writing-cache-manifests
>> 
>> [[
>> This algorithm is a willful violation of the HTTP specification, which
>> requires that the encoding be assumed to be ISO-8859-1 in the absence of
>> a character encoding declaration to the contrary, and of RFC 2046, which
>> requires that the encoding be assumed to be US-ASCII in the absence of a
>> character encoding declaration to the contrary. This specification's
>> third approach is motivated by a desire to be maximally compatible with
>> legacy content. [HTTP] [RFC2046]
>> ]]
>> http://www.w3.org/TR/html5/parsing.html#determining-the-character-encoding
>> 
>> [[
>> The requirement to default UTF-16 to LE rather than BE is a willful
>> violation of RFC 2781, motivated by a desire for compatibility with
>> legacy content. [RFC2781]
>> ]]
>> http://www.w3.org/TR/html5/parsing.html#character-encodings-0
>> 
>> [[
>> This requirement is a willful violation of RFC 5322, which defines a
>> syntax for e-mail addresses that is simultaneously too strict (before
>> the "@" character), too vague (after the "@" character), and too lax
>> (allowing comments, white space characters, and quoted strings in
>> manners unfamiliar to most users) to be of practical use here.
>> ]]
>> http://www.w3.org/TR/html5/states-of-the-type-attribute.html#e-mail-state
>> 
>> [[
>> The term "URL" in this specification is used in a manner distinct from
>> the precise technical meaning it is given in RFC 3986. Readers familiar
>> with that RFC will find it easier to read this specification if they
>> pretend the term "URL" as used herein is really called something else
>> altogether. This is a willful violation of RFC 3986. [RFC3986]
>> ]]
>> http://www.w3.org/TR/html5/urls.html#urls
>> 
>> [[
>> These parsing rules are a willful violation of RFC 3986 and RFC 3987
>> (which do not define error handling), motivated by a desire to handle
>> legacy content. [RFC3986] [RFC3987]
>> ]]
>> http://www.w3.org/TR/html5/urls.html#parsing-urls
>> 
>> Philippe
>> 
>> 
>> 
> 
> --
> Mark Nottingham   http://www.mnot.net/
> 
> 
> 
> _______________________________________________
> apps-discuss mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/apps-discuss