- From: Karl Dubost <karl@w3.org>
- Date: Tue, 14 Dec 2004 15:56:34 -0500
- To: www-qa@w3.org
- Message-Id: <A375E3E8-4E12-11D9-AE12-000A95718F82@w3.org>
Review of HTML 4.01, Version 1999-12-24 http://www.w3.org/TR/1999/REC-html401-19991224/ Against SpecGL Last Call, 22 November 2004 http://www.w3.org/TR/2004/WD-qaframe-spec-20041122/ HTML 4.01 is an old specification, but it's interesting exactly for this point, because it contains things which are handled in the right and others which are not applicable or shows that SpecGL could have helped to ask the right questions. Good Practices: "YES/NO/Not Applicable" might not enough, there's a kind of hidden profile for Good Practices. Two users profiles: - WG Participants: who can access the good practice. - External Reviewer: who can't answer to some questions. Important to keep in mind: Another thing which is clear "Specification Guidelines" is not a tool to review a specification, it's a tool to write a good specification. Even if right now we are using it for that purpose, it's not the main goal of SpecGL. =============================== * 13 Requirements (Normative) * =============================== 1.1.A: Include a conformance clause. http://www.w3.org/TR/2004/WD-qaframe-spec-20041122/#include- conformance-clause-principle YES. But could be improved. 2.1.A: Define the scope. http://www.w3.org/TR/2004/WD-qaframe-spec-20041122/#define-scope- principle YES 2.2.A: Identify who or what will implement the specification. http://www.w3.org/TR/2004/WD-qaframe-spec-20041122/#implement-principle NO. We can understand who will implement the specification, but the topic is not completely addressed. 2.3.A: Make a list of normative references. http://www.w3.org/TR/2004/WD-qaframe-spec-20041122/#ref-norm-principle YES 3.1.A: Define the terms used in the normative parts of the specification. http://www.w3.org/TR/2004/WD-qaframe-spec-20041122/#define-terms- principle YES. There are defined in the conformance Section. 3.1.B: Create conformance labels for each part of the conformance model. http://www.w3.org/TR/2004/WD-qaframe-spec-20041122/#conf-label-principle NO There are 3 levels of HTML but there are no specific conformance labels for implementations. 3.2.A: Use a consistent style for conformance requirements and explain how to distinguish them. http://www.w3.org/TR/2004/WD-qaframe-spec-20041122/#consistent-style- principle YES. 3.2.B: Indicate which conformance requirements are mandatory, which are recommended and which are optional. http://www.w3.org/TR/2004/WD-qaframe-spec-20041122/#req-opt-conf- principle YES 4.1.B: If the technology is subdivided, then indicate which subdivisions are mandatory for conformance. http://www.w3.org/TR/2004/WD-qaframe-spec-20041122/#subdivide- mandatory-principle Not Applicable 4.1.C: If the technology is subdivided, then address subdivision constraints. http://www.w3.org/TR/2004/WD-qaframe-spec-20041122/#subdiv-constraints- principle Not Applicable 4.3.A: Address Extensibility. http://www.w3.org/TR/2004/WD-qaframe-spec-20041122/#likehood-extension- principle NO 4.4.A: Identify deprecated features. http://www.w3.org/TR/2004/WD-qaframe-spec-20041122/#deprecated-feature- principle YES 4.4.B: Define how deprecated feature is handled by each class of product. http://www.w3.org/TR/2004/WD-qaframe-spec-20041122/#degree-support- principle YES ===================================== * 25 Good Practices (Not normative) * ===================================== 1.1.B: Define the specification's conformance model in the conformance clause. http://www.w3.org/TR/2004/WD-qaframe-spec-20041122/#conformance-model-gp NO 1.1.C: Specify in the conformance clause how to distinguish normative from informative content. http://www.w3.org/TR/2004/WD-qaframe-spec-20041122/#norm-informative-gp NO 1.2.A: Provide the wording for conformance claims. http://www.w3.org/TR/2004/WD-qaframe-spec-20041122/#conformance-claim-gp NO 1.2.B: Provide an Implementation Conformance Statement proforma. http://www.w3.org/TR/2004/WD-qaframe-spec-20041122/#ics-gp NO 1.2.C: Require an Implementation Conformance Statement as part of valid conformance claims. http://www.w3.org/TR/2004/WD-qaframe-spec-20041122/#ics-claim-gp NO 2.1.B: Provide examples, use cases, and graphics. http://www.w3.org/TR/2004/WD-qaframe-spec-20041122/#use-example-gp YES 2.3.B: Do systematic reviews of normative references and their implications. http://w3c.test.site/TR/2004/WD-qaframe-spec-20041122/#ref-define- practice Can't answer 3.1.C: Define the unfamiliar terms in-line, and consolidate the definitions in a glossary section. http://www.w3.org/TR/2004/WD-qaframe-spec-20041122/#define-terms- inline-gp YES (kind of) 3.1.D: Use terms already defined without changing their definition. http://www.w3.org/TR/2004/WD-qaframe-spec-20041122/#reuse-terms-gp YES 4.1.A: Create subdivisions of the technology when warranted. http://www.w3.org/TR/2004/WD-qaframe-spec-20041122/#subdivide-foster-gp Not Applicable 4.1.D: If the technology is profiled, define rules for creating new profiles. http://www.w3.org/TR/2004/WD-qaframe-spec-20041122/#rules-profiles-gp Not Applicable 4.2.A: Make sure there is a need for the optional feature. http://www.w3.org/TR/2004/WD-qaframe-spec-20041122/#need-option-gp Not Applicable 4.2.B: Clearly identify optional features. http://www.w3.org/TR/2004/WD-qaframe-spec-20041122/#label-options-gp Not Applicable 4.2.C: Indicate any limitations or constraints on optional features. http://www.w3.org/TR/2004/WD-qaframe-spec-20041122/#constraints-gp Not Applicable 4.3.B: If extensibility is allowed, define an extension mechanism. http://www.w3.org/TR/2004/WD-qaframe-spec-20041122/#extensions- prohibited-gp Not Applicable 4.3.C: Warn implementers to create extensions that do not interfere with conformance. http://www.w3.org/TR/2004/WD-qaframe-spec-20041122/#breaking- conformance-gp Not Applicable 4.3.D: Define error handling for unknown extensions. http://www.w3.org/TR/2004/WD-qaframe-spec-20041122/#define-error-gp YES 4.4.C: Explain how to avoid using a deprecated feature. http://www.w3.org/TR/2004/WD-qaframe-spec-20041122/#workaround-gp YES 4.4.D: Identify obsolete features. http://www.w3.org/TR/2004/WD-qaframe-spec-20041122/#obsolete-gp YES 4.5.A: Define an error handling mechanism. http://www.w3.org/TR/2004/WD-qaframe-spec-20041122/#error-handling-gp YES 5.A: Define an internal publication and review process. http://www.w3.org/TR/2004/WD-qaframe-spec-20041122/#practice-principle Can't say. External review. 5.B: Do a systematic and thorough review. http://www.w3.org/TR/2004/WD-qaframe-spec-20041122/#review-gp Can't say. External review. 5.C: Write sample code or tests. http://www.w3.org/TR/2004/WD-qaframe-spec-20041122/#write-sample-gp Can't say. External review. 5.D: Write Test Assertions. http://www.w3.org/TR/2004/WD-qaframe-spec-20041122/#write-assertion-gp NO 5.E: Use formal languages and define which from prose and formal languages has priority. http://www.w3.org/TR/2004/WD-qaframe-spec-20041122/#formal-language-gp NO -- Karl Dubost - http://www.w3.org/People/karl/ W3C Conformance Manager *** Be Strict To Be Cool ***
Received on Wednesday, 15 December 2004 00:19:49 UTC