W3C home > Mailing lists > Public > www-style@w3.org > September 2006

[css3-namespace] Conformance rules.

From: <karl@w3.org>
Date: Tue, 05 Sep 2006 05:56:25 -0000
To: www-style@w3.org
Message-Id: <20060905055651.D09AC4F065@homer.w3.org>

This is a QA Review comment for "CSS Module: Namespaces"
2nd WD

About http://www.w3.org/TR/2006/WD-css3-namespace-20060828/#intro

In the Conformance section, define first RFC 2119. It defines the way that the people must read the document. Then define the conformance rules applied to each class of products in *clear terms*.

	A document or implementation cannot conform to this 
	specification alone, but can claim conformance to 
	this specification if it satisfies the conformance 
	requirements in this specification when implementing 
	CSS or another host language that normatively references 
	this specification.

The sentence is too long and then difficult to understand. Reading the paragraph, CSS Namespaces seems to define two classes of products.

	- document
	- implementation

implementation is vague and not explaining what the CSS Namespaces is supposed to conform to, plus the fact that "document" is an implementation of the technology.
Define the [classes of products][1]. There might be things like:

	- document (content)
	- specification
	- parser (agent)
	- renderer (player)
	- authoring tool (producer of content)

It seems that the module can't be implemented by itself. So it means that it is implemented by references from another technology, be it CSS or something else. Express it in clear terms, and if conformance is claimed to this specification, how it must be done.

[1]: http://www.w3.org/TR/qaframe-spec/#implement-principle

Karl Dubost - http://www.w3.org/People/karl/
W3C Conformance Manager, QA Activity Lead
   QA Weblog - http://www.w3.org/QA/
      *** Be Strict To Be Cool ***
Received on Tuesday, 5 September 2006 05:57:13 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:27:26 UTC