Choice developing item multiple test validating
Everyone benefits from having well-written specifications. Editors may have less rework and thus, fewer issues raised during the development of the specification, and fewer errata once it is finished.
Implementers can implement sooner and have a better chance to conform to the specification.
A [WEB-ARCH]) where conformance is not an issue (e.g., no normative content), the conformance clause may be an explanation of why there is no “conformance to this document” and may be presented in another section rather than in a separate conformance section.
The topics presented herein are inclusive (self-contained) and provide information needed to understand and successfully apply the Requirement or Good Practice, although related information and advanced topics may be referenced.
These topics are not directly in the scope of this document, but are evoked in section 3.3.
The primary audience of this document is editors; however, it is applicable to a broader audience including: This document makes no distinction between the terms editors and authors and refers to them collectively as editors.
This document has been produced by the QA Working Group, as part of the QA Activity.
The English version of this specification is the only normative version. If you have any comments on this document, send them to [email protected], a mailing list with a public archives. This document only had minor editorial corrections since it was published as a Proposed Recommendation.
This section describes the status of this document at the time of its publication. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at It has been reviewed by W3C Members and other interested parties and has been endorsed by the Director.
It is a stable document and may be used as reference material or cited as a normative reference from another document.It provides guidelines for improving conformance-related characteristics.