On Mon, Sep 22, 2014 at 3:48 PM, Robin Berjon <ro...@w3.org> wrote: > On 22/09/2014 14:40 , Henri Sivonen wrote: >> >> On Mon, Sep 22, 2014 at 2:41 PM, Robin Berjon <ro...@w3.org> wrote: >>> >>> I was hoping that we could simply reference WHATWG URL as a (small) token >>> of >>> good faith and normalisation, adding a small cobblestone to pave the way >>> to >>> cooperation. >> >> >> If that was the goal, changing the "Goals" section of the spec to cast >> doubts about whether the direction the W3C envisions for the spec is >> consistent with the goal that are the actual reason for the spec's >> existence was a rather bad way to go about it. > > > For context, you are talking about changing the "Goals" section of the URL > spec, right?
Yes. For reference for those following along who don't want to bother to look it up, the WHATWG URL Goals section reads: > The URL standard standardizes URLs, aiming to make them fully interoperable. > It does so as follows: > > * 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. [URI] [IRI] > > * Standardize on the term URL. URI and IRI are just confusing. In practice > a single algorithm is used for both so keeping them distinct is not helping > anyone. URL also easily wins the search result popularity contest. > > * Supplanting Origin of a URI [sic]. [ORIGIN] > > * Define URL's existing JavaScript API in full detail and add > enhancements to make it easier to work with. Add a new URL object > as well for URL manipulation without usage of HTML elements. > (Useful for Web Workers.) > > Note: As the editor learns more about the subject matter the goals might > increase in scope somewhat. The W3C Goals section replaces the last "Note" paragraph with: > 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. -- Henri Sivonen hsivo...@hsivonen.fi https://hsivonen.fi/ _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
