W3C and the WHATWG sign agreement to collaborate on single version of HTML, DOM
1–10 of 287 posts
Re: W3C and the WHATWG sign agreement to collaborate on single version of HTML, DOM
#2Impressive
Re: W3C and the WHATWG sign agreement to collaborate on single version of HTML, DOM
#3This looks like W3C capitulating:
> WHATWG maintains the HTML and DOM Living Standards
Which is understandable, since all of the main implementers of HTML are active in WHATWG, not so much W3C.
What will be the concrete impact of this agreement?
Re: W3C and the WHATWG sign agreement to collaborate on single version of HTML, DOM
#4Extremely condensed version:
W3C is giving up publishing future HTML and DOM standards. They will focus on writing 'recommendations' for the WHATWG's living standards.
Versioned vs living HTML discussions aside, I personally admit some mild sadness that the original group responsible for maintaining Sir TBL's work on HTML has been forced to give up.
Re: W3C and the WHATWG sign agreement to collaborate on single version of HTML, DOM
#5Sounds like a recognition of WHATWG as the master, with W3C becoming more of a publishing / vetting organization for snapshots of the standard?
Re: W3C and the WHATWG sign agreement to collaborate on single version of HTML, DOM
#6W3C will now publish a Recommendation instead of a "version" as such. The Recommendation will be from a "Review Draft" published by WHATWG, this draft will then go through the W3C process (Candidate Recommendation → Proposed Recommendation → Recommendation).
And then there is patent exclusion ( What? )
Anyway I don't see anything new to developers. Apart from the politics and two parties bury the hatchet.
Re: W3C and the WHATWG sign agreement to collaborate on single version of HTML, DOM
#7So W3C is signing to confirm their irrelevance?
Re: W3C and the WHATWG sign agreement to collaborate on single version of HTML, DOM
#8W3C will now publish a Recommendation instead of a "version" as such. The Recommendation will be from a "Review Draft" published by WHATWG, this draft will then go through the W3C process (Candidate Recommendation → Proposed Recommendation → Recommendation). And then there is patent exclusion ( What? ) Anyway I don't see anything new to developers. Apart from the politics and two parties bury the hatchet.
Why don't W3C just leave it to WHATWG entirely? Why do we need two groups involved? Why should I put any value in what W3C recommends? What would they ever recommend instead of WHATWG?
Re: W3C and the WHATWG sign agreement to collaborate on single version of HTML, DOM
#9I still maintain that the "living standard" is an oxymoron. It's a collaborative browser dev document. Don't get me wrong, that's great. However for everyone else an unversioned document, any part of which can change at any moment, is not what's usually thought of as a standard.
Re: W3C and the WHATWG sign agreement to collaborate on single version of HTML, DOM
#10W3C will now publish a Recommendation instead of a "version" as such. The Recommendation will be from a "Review Draft" published by WHATWG, this draft will then go through the W3C process (Candidate Recommendation → Proposed Recommendation → Recommendation). And then there is patent exclusion ( What? ) Anyway I don't see anything new to developers. Apart from the politics and two parties bury the hatchet.
Why don't W3C just leave it to WHATWG entirely? Why do we need two groups involved? Why should I put any value in what W3C recommends? What would they ever recommend instead of WHATWG?
> Why should I put any value in what W3C recommends?
For the same reason you put any value in, e.g., ISO or ANSI. Because others recognize them as the standard organization and put value in what they recommend.