On 07.10.2016 at 16:45, David Walker wrote: > On Fri, Oct 7, 2016 at 4:37 AM Nikita Popov <nikita....@gmail.com> wrote: > >> Are you aware of the WHATWG URL standard [1]? Quoting the first goal >> statement: >> >>> Align RFC 3986 and RFC 3987 with contemporary implementations and >> obsolete them in the process. (E.g., spaces, other "illegal" code points, >> query encoding, equality, canonicalization, are all concepts not entirely >> shared, or defined.) URL parsing needs to become as solid as HTML parsing. > > I was not. I assume that WHATWG ought to supersede the IETF standards on > the subject. I can obviously make an implementation follow the standards > and algorithms set out in this doc.
That might be hard, because WHATWG has "living standards", i.e. they can change over time. If we state that our new functionality conforms to WHATWG's URL standard we have to always apply the latest changes even into revisions, potentially causing BC breaks. -- Christoph M. Becker -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
