- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Thu, 11 Sep 2014 18:13:37 +0200
- To: Julian Reschke <julian.reschke@greenbytes.de>
- Cc: Marcos Caceres <marcos@marcosc.com>, Robin Berjon <robin@w3.org>, Arthur Barstow <art.barstow@gmail.com>, "www-tag@w3.org" <www-tag@w3.org>, public-webapps <public-webapps@w3.org>
On Thu, Sep 11, 2014 at 5:58 PM, Julian Reschke <julian.reschke@greenbytes.de> wrote: > It's my understanding that the intent is to actually make technical changes, > as indicated in: > >> This specification documents current RFC 3986 and RFC 3987 handling in >> contemporary Web browser implementations. As a consequence, this >> specification is not compatible with those RFCs. It is published for the >> purpose of providing a stable reference for the HTML5 specification and >> reflecting current Web browser HTML5 implementations. The W3C Technical >> Architecture Group expects to continue the work on the URL specification and >> produce a future version that will attempt to re-align the URL specification >> with an updated version of RFC 3986 while preserving interoperability. > > In which case the WHATWG version wouldn't be "canonical" anymore anyway. It would be for implementers. Seems ill-advised to implement something that contains contradictory goals and is bound to be incompatible with deployed content. -- http://annevankesteren.nl/
Received on Thursday, 11 September 2014 16:14:08 UTC