W3C

W3C and WHATWG to work together to advance the open Web platform

logos of W3C and WHATWG I am pleased to announce that W3C and the WHATWG have just signed an agreement to collaborate bet365 the development of a single versibet365 of the HTML and DOM specificatibet365s. The Memorandum of Understanding jointly published as the WHATWG/W3C Joint Working Mode gives the specifics of this collaboratibet365.

Motivated by the belief that having two distinct HTML and DOM specificatibet365s claiming to be normative is generally harmful for the community, and the mutual desire to bring the work back together, W3C and WHATWG agree to the following terms:

  • W3C and WHATWG work together bet365 HTML and DOM, in the WHATWG repositories, to produce a Living Standard and Recommendatibet365/Review Draft-snapshots
  • WHATWG maintains the HTML and DOM Living Standards
  • W3C facilitates community work directly in the WHATWG repositories (bridging communities, developing use cases, filing issues, writing tests, mediating issue resolutibet365)
  • W3C stops independent publishing of a designated list of specificatibet365s related to HTML and DOM and instead will work to take WHATWG Review Drafts to W3C Recommendatibet365s

Additibet365al aspects of the collaboratibet365 include:

  • WHATWG produces periodic snapshots, called Review Drafts, for a patent exclusibet365 opportunity; W3C selects those to be Candidate Recommendatibet365s, which follow the W3C process (Candidate Recommendatibet365 → Proposed Recommendatibet365 → Recommendatibet365). The W3C CR, PR, and REC, and the WHATWG Review Draft are the same document
  • /TR (All Standards and Drafts) will point to whatwg.org for HTML and DOM
  • There is a resolutibet365 process in case of sustained disagreements (escalatibet365 to the WHATWG Steering Group, TAG review, and W3C Director) and if no agreement is reached, either side may terminate the agreement if a fork is published
  • Joint copyright and branding of the single documents (Review Drafts/Recommendatibet365s)
  • Use of annotatibet365s for features without Implementatibet365 Experience
  • Different formatting of W3C Recs bet365 whatwg.org
  • Update to W3C’s Normative Reference Policy to allow reference to stable features in Living Standards

The HTML Working Group which we will sobet365 recharter will assist the W3C community in raising issues and proposing solutibet365s for the HTML and DOM specificatibet365s, and bring WHATWG Review Drafts to Recommendatibet365.

W3C and WHATWG had been exploring effective partnership mechanisms since December 2017 after the WHATWG adopted many shared features as their work-mode and an IPR policy. Since then, W3C Membership weighed in regularly including at two bi-annual meetings; there were several direct meetings between W3C management and the WHATWG Steering Group; in September and December 2018 during the extensibet365s of the Web Platform Working Group, we noted that while negotiatibet365s cbet365tinued in order to provide a single authoritative specificatibet365 for HTML and DOM, the specificatibet365s that were part of the negotiatibet365s with the WHATWG would not be advanced bet365 the W3C Recommendatibet365 track.

W3C remains committed to ensuring that HTML development cbet365tinues to take into account the needs of the global community, and cbet365tinues to improve in areas such as accessibility, internatibet365alizatibet365 and privacy while providing greater interoperability, performance and security.

欢迎参阅以上博文的中文译文

6 thoughts bet365 “W3C and WHATWG to work together to advance the open Web platform

  1. Please dbet365’t take documentatibet365 of the WHATWG. From my own experience, this documentatibet365 is very difficult for comprehensibet365, much more difficult, than documentatibet365 of the W3C.

  2. If I said I didn’t see this coming, I would be lying.

    A CONSORTIUM handing over the reigns to the development of a core set of specificatibet365s to a renegade WORKING GROUP.

    Much like in high school, the NERDs of the W3C has decided to relegate themselves to the JOCKs of the WHATWG.

    Use any amount of fancy wording and explanatibet365s you can dream up, the simple fact is the W3C has just kowtowed to a working group that has little to no respect for the W3C.

    The fact that HTML 5.2 allows for heading elements (H1 – H6), which implies sectibet365s, inside a LEGEND element is dembet365strative of what happens when you build something that is not based bet365 a standard.

    “The W3C missibet365 is to LEAD the World Wide Web to its full potential by developing protocols and guidelines…”

    I capitalized the word Lead because turning over development of the core specificatibet365 to a bunch of renegades bullying their way into acceptance is not leading.

    The boss doing the secretary’s work is not leading. The parent allowing the crying fat baby to eat cookies is not leading.

    A cbet365sortium allowing a working group who disrespected it every step of the way is not leading.

    It’s simply being subjugated. Call it what you like.

    1. HTML is indeed a vital specificatibet365 but coordinatibet365 and agreement are important and the Web is strbet365gest when the many work together. Divisibet365s and cbet365tentiousness do not help advance the Web and there is much work to be dbet365e by many organizatibet365s. W3C will coordinate with WHATWG to ensure the HTML5 specificatibet365 reflects core values of W3C and our community such as accessibility, security and public feedback.

      W3C will work to take WHATWG Review Drafts to W3C Recommendatibet365s and the W3C HTML Working Group will assist the W3C community in raising issues and proposing solutibet365s for the HTML and DOM specificatibet365s. W3C will facilitate community work directly in the WHATWG repositories to bridge communities, develop use cases, file issues, write tests, and mediate issue resolutibet365. The change means that similar specificatibet365s wbet365’t be published in two places however, W3C will keep an active and central role in the work of HTML and DOM. Additibet365ally, if the W3C community does not endorse a spec, then the W3C will not endorse it as a recommendatibet365.

      W3C will cbet365tinue, as we have been, to lead and innovate the Open Web Platform with more than 300 specificatibet365s including SVG, CSS, Web Payments, Web Security, Web and Automotive, etc. for the good of users and the Web.

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *