Background: Process Requirements
According to the W3C Process, as part of the approval process for a specification to enter Candidate Recommendation (PR), the Working Group must:
- Show that the specification has met all Working Group requirements, or explain why the requirements have changed or been deferred
- Explain how the group proposes to demonstrate broad implementation experience.
- Show the document has received wide review.
The review period for CR
must be at least four weeks after publication, and should
be longer for complex documents
Adequate implementation experience, described as
the specification is sufficiently clear, complete, and relevant to market needs, to ensure that independent interoperable implementations of each feature of the specification will be realized
- The document has received wide review.
The deadline for Advisory Committee review of a Proposed Recommendation
must be at least
28 days after the publication of the Proposed Recommendation and should be at least 10 days after the end
of the last Exclusion Opportunity.
HTML 5.0 and HTML 5.1 have already been accepted by the W3C Director as meeting these requirements.
Meeting our requirements
There is not a formal requirements document for HTML 5.2. HTML is an extremely widely implemented and widely-used technology, and we consider the requirements for this group to be documenting what is interoperable among the things considered "HTML" to enable implementers of user agents, developers of content creation and management tools, and producers of Web content to implement and use HTML interoperably with confidence.
HTML has continued to develop over the last 25 years, and we expect that process to continue. Therefore, rather than finishing "the HTML specification" we take as our task to regularly produce a W3C Recommendation that achieves the goal of documenting HTML more accurately and usefully than its predecessor, taking into account both changes in HTML and where possible improving the quality of the documentation itself.
The HTML 5 specification is perhaps the most widely reviewed product of W3C. We believe that the implementation in software, and concomitant use, generally constitutes sufficient review.
We also publicise changes to the specification, and produce drafts with changelogs enabling the general public to understand the changes.
Finally, while it does not apply to all changes, a substantial proportion of the changes made to HTML5 have either been copied from, or independently reviewed by WHATWG, effectively ensuring that two independent groups working on defining the fundamentals of the Web Platform have at least considered them.
Since HTML 5.0 has been accepted as showing implementation experience, we propose that no substantive changes that add features or requirements will be accepted unless they are implemented interoperably by at least 2 independent shipping products. Similarly, if a feature in the specification is identified as not having at least two interoperable shipping implementations
There is no requirement that all features must be implemented by a single product.
For the purposes of this criterion, we define the following terms:
- Each feature or requirement implementation must be developed by a different party, and shipped as part of a different product. In particular, two products that re-use the same codebase to implement a particular feature or requirement will not be considered independent.
- Features coded according to the specification must work "the same way" in different implementations. A test or test suite may be used to demonstrate this.
- Shipping product
- One which:
- Implements the relevant conformance class of the specification, typically "web browsers and other interactive user agents" .
- Is available to the general public. The implementation may be a shipping product or other publicly available version (for example a beta version, preview release or nightly build), endorsed by those who produced it as sufficiently stable.
- Is intended for general public use, i.e. is not an experimental demonstration.
Entering and exiting CR
If the group meets these requirements for changes made to the specification, we believe that to enter Candidate Recommendation we will specifically need to show a group decision that the current Working Draft for HTML 5.2 is a notable improvement on the HTML 5.1 Recommendation, has received sufficient review of changes, and is therefore ready to be proposed as a Recommendation.
Given the implementation-driven model for changes, that much of HTML 5 has already been reviewed before we began the work, and that major features have been widely reviewed and implemented, the formal review period will be four weeks.
To exit Candidate Recommendation, we believe that we will similarly need to address comments received during the CR period, and the Working Group reach a decision that it has indeed met its working criteria, and addressed comments raised as per the Process.