- From: <karl@w3.org>
- Date: Tue, 05 Sep 2006 05:56:52 -0000
- To: www-style@w3.org
Hi,
This is a QA Review comment for "CSS Module: Namespaces"
http://www.w3.org/TR/2006/WD-css3-namespace-20060828/
2006-08-28
2nd WD
About http://www.w3.org/TR/2006/WD-css3-namespace-20060828/#css-qnames
[[[
CSS qualified names can be used in (for example)
selectors and property values as described in
other modules. Those modules should define the use
of a namespace prefix that has not been properly
declared as a parsing error that will cause the
selector or declaration (etc.) to be considered
invalid and ignored.
]]]
Why a "SHOULD" here? Let's imagine that two modules define two contradictory behavior for handling namespaces not "properly declared". It will be lead to difficulties in implementations if not total incompatibilities. The modules should not define anything and rely on the rules defined in this module.
What should do an authoring tool? It seems in this case that it should not ignore at all the error and pop up a message to fix it. The spec must define the class of products and apply requirements depending on the products.
--
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:24 UTC