- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Mon, 3 Nov 2014 16:32:00 +0100
- To: David Singer <singer@apple.com>
- Cc: WhatWG <whatwg@whatwg.org>, Graham Klyne <gk@ninebynine.org>, Sam Ruby <rubys@intertwingly.net>
On Mon, Nov 3, 2014 at 4:19 PM, David Singer <singer@apple.com> wrote: > The readability is much better (I am not a fan of the current trend of writing specifications in pseudo-basic, which makes life easier for implementers and terrible for anyone else, including authors), and I also think that an approach that doesn’t obsolete RFC 3986 is attractive. Is Apple interested in changing its URL infrastructure to not be fundamentally incompatible with RFC 3986 then? Other than slightly different eventual data models for URLs, which we could maybe amend RFC 3986 for IETF gods willing, I think the main problem is that a URL that goes through an RFC 3986 pipeline cannot go through a URL pipeline. E.g. parsing "../test" against "foobar://test/x" gives wildly different results. That is not a state we want to be in, so something has to give. -- https://annevankesteren.nl/
Received on Monday, 3 November 2014 15:32:28 UTC