-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 9/24/12 6:03 AM, Julian Reschke wrote:
> FYI:
>
> Quoting AvK in
> <http://lists.w3.org/Archives/Public/public-whatwg-archive/2012Sep/0297.html>:
>
>
>> The plan is to obsolete the RFCs. But yes, I will add some
>> references in the Goals section most likely. Similar to what has
>> been done in the DOM Standard.
>
> Note this is about RFC 3986, which is a Full Standard.
Hi Julian,
It's not completely clear to me what Anne meant there by saying "the
plan is to obsolete the RFCs" (naturally that is not something that
anyone outside the IETF can do, although they can ignore the RFCs).
It's also not clear to me what the WHATWG HTML Living Standard [1]
really means by "willful violation" [2] -- e.g., is it just an
allowance for APIs and browser software to not be completely strict
about processing some input for the sake of backward compatibility
with existing (messy) web content, or is it an active attempt at
redefining core protocols? However, it is interesting that the willful
violations are not limited to RFC 3986: the spec also mentions willful
violations of RFC 2046, RFC 2616, RFC 2781, RFC 5322, EcmaScript,
XPath, XSLT, and Unicode. Quite a list...
Peter
[1] http://www.whatwg.org/specs/web-apps/current-work/
[2]
http://www.whatwg.org/specs/web-apps/current-work/multipage/introduction.html#willful-violation
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
iEYEARECAAYFAlBgqWQACgkQNL8k5A2w/vxD/QCeNTDVz/kaXkhROIm1/N9QB5Tf
QroAoPI96pCgHUCnjZqGLjmCrqLBQ1ym
=Nscu
-----END PGP SIGNATURE-----