- From: Thomas Roessler <tlr@w3.org>
- Date: Mon, 4 Jun 2007 11:56:01 +0100
- To: public-wsc-wg@w3.org
Per ACTION-245, I've drafted a conformance clause for the specification. We might tinker further and embellish it as is, e.g., done in [1], but I think the current text is enough for the FPWD. Here's the text: | Conformance with this Specification | | The conformance requirements of this document are found in its | Requirements and Good Practices. The Requirements are written in the | imperative voice and denote mandatory conformance requirements. They | are equivalent to the familiar MUST statements in the RFC2119 [RFC | 2119] style. In addition to Requirements, this document contains | Good Practices. Good Practices use the same imperative voice, but | are optional. They are equivalent to SHOULD or RECOMMENDED | statements in the RFC2119 style. | | Requirements and Good Practices are scoped by Applicability clauses: | These clauses characterize the products that can claim conformance | to a given Requirement or Good Practice. Relevant product classes | include Web Sites and Web User Agents. The Applicability clauses | identify further constraints, e.g. on the interaction modalities | exposed by a Web User Agent. | | For a product to claim conformance with this specification, all | Requirements whose Applicability clauses are fulfilled must be | implemented. | | One way to satisfy the Requirements and Good Practices is to | implement one or more of the suggested techniques given for each | Requirement and Good Practice. Note that this is not the only way to | satisfy the Requirement or Good Practice. -- http://www.w3.org/2006/WSC/wiki/ConformanceClause 1. http://www.w3.org/TR/qaframe-spec/#conformance -- Thomas Roessler, W3C <tlr@w3.org>
Received on Monday, 4 June 2007 10:56:05 UTC