- From: Larry Masinter <masinter@adobe.com>
- Date: Tue, 7 Oct 2014 02:09:45 +0000
- To: Sam Ruby <rubys@intertwingly.net>, David Sheets <sheets@alum.mit.edu>
- CC: "public-urispec@w3.org" <public-urispec@w3.org>, Anne van Kesteren <annevk@annevk.nl>, John Klensin <klensin@jck.com>
> For what it is worth, examples of problem I do have: I think the problem you have has something to do with the normative reference from HTML5 to WHATWG URL, for which these two issue are impediments, but perhaps there are others. http://lists.w3.org/Archives/Public/public-html/2014Sep/0079.html and that we should include Roy, PLH, Dan Applequist, and mnot if 'consensus' is going to mean 'consensus'. > 1) Neither RFC 3986 nor RFC 3987 define the content you will find here: > https://url.spec.whatwg.org/#api > > 2) The WHATWG URL Living Standard makes a large number of > normative > statements, particularly concerning parsing, that do not reflect current > implementations. > > I'm not intending to advocate any particular solutions to these > problems; I'm just providing an early heads up of the types of questions > I likely will be seeking answers to when you have something to show. > > - Sam Ruby
Received on Tuesday, 7 October 2014 02:10:16 UTC