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

Re: [css3-namespace] Abstract section clarity

From: Karl Dubost <karl@w3.org>
Date: Sun, 17 Sep 2006 06:03:43 +0200
Message-Id: <ED5EBD67-50B7-4E1E-A50F-5B525274CCA6@w3.org>
Cc: www-style@w3.org
To: fantasai <fantasai.lists@inkedblade.net>

Le 16 sept. 06 à 12:28, fantasai a écrit :

> karl@w3.org wrote:
>> 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/#abstract
>> The Abstract section mentions namespaces, but it is not said that  
>> it is XML namespaces.
> This specification isn't about XML namespaces. It's about  
> namespaces in general.
> They could be XML namespaces used in selectors in CSS, or event  
> namespaces used
> in property values in some "scripting sheets" language. It doesn't  
> matter; the
> spec only
>   a) defines syntax to bind prefixes to namespaces
>   b) defines syntax to represent namespace-qualified names
> It doesn't define the semantics of the names. That depends on the  
> context, and
> is defined by a host language (such as CSS Selectors) that uses the  
> syntax
> defined in this module.

Agreed. Then define it clearly in the specification, which is not the  
case right now. Stress out the differences, gives the general concept  
about namespaces.

>> CSS is having its own mechanism for namespaces as well (aka -moz-  
>> for example.) It would be better to really define which one the  
>> specification is talking about.
> -moz- is a vendor extension. It's not a namespace, it's just a  
> naming convention
> to avoid clashes in vendor-specific CSS properties and values.  
> While these
> properties and values conform to the core parsing grammar, they are  
> not actually
> valid CSS.

As you have written just above:
> This specification isn't about XML namespaces. It's about  
> namespaces in general.

-moz- is a kind of namespace to "avoid clashes in vendor-specific CSS  
properties and values". This is another mechanism of namespace. It is  
specifically what a namespace is. A mechanism to avoid name clashes  
and create a particular space.

Then it is really necessary to explain the way Namespaces are defined  
in this specification, more than at initially thought.

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 Sunday, 17 September 2006 04:10:21 UTC

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