- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Fri, 29 Aug 2014 21:04:41 +0200
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: Ian Hickson <ian@hixie.ch>, Daniel Appelquist <appelquist@gmail.com>, WebApps WG <public-webapps@w3.org>, TAG List <www-tag@w3.org>, Philippe Le Hegaret <plh@w3.org>, Arthur Barstow <art.barstow@gmail.com>, Charles McCathie Nevile <chaals@yandex-team.ru>
On Fri, Aug 29, 2014 at 8:11 AM, Julian Reschke <julian.reschke@gmx.de> wrote: > "W3C-specific note: 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." That's a contradictory goal. Anyway, if W3C actually wanted to help here they would focus on getting implementations aligned with the specification before starting to fork and seed confusion. That's the biggest problem for the web at the moment when it comes to URLs.
Received on Friday, 29 August 2014 19:05:08 UTC