W3C home > Mailing lists > Public > www-style@w3.org > March 2008

Re: [css3-namespace] 4. CSS Qualified Names

From: fantasai <fantasai.lists@inkedblade.net>
Date: Mon, 10 Mar 2008 10:38:02 -0700
Message-ID: <47D571FA.20806@inkedblade.net>
To: Erik Dahlström <ed@opera.com>
CC: "www-style@w3.org" <www-style@w3.org>, www-svg@w3.org

Erik Dahlström wrote:
> 
> Dear CSS WG,
> 
> This is a last call comment from the SVG WG on the CSS Namespaces 
> Module, W3C Working Draft 15 February 2008, 
> http://www.w3.org/TR/2008/WD-css3-namespace-20080215/. Please let us 
> know if you have any questions by CC:ing your responses to www-svg@w3.org.
> 
>> Some contexts may allow the use of an asterisk (*, U+002A) as a
>> wildcard prefix to indicate a name in any namespace, including no
>> namespace.
> 
> What exactly does "contexts" mean here? Perhaps an example of a context
> that allows asterisks, and one that doesn't would make it easier to
> understand. If this is defined by the host language, please say so 
> explicitly.

David Baron gave a good example here:
   http://lists.w3.org/Archives/Public/www-style/2008Mar/0134.html

Clarified the spec by adding "(as defined by the host language)" after
"Some contexts".

>> Those modules must define handling of namespace prefixes that have not 
>> been properly declared.
> 
> Please add informative references to modules that define this.

Added
     For example, the Selectors module [[SELECT]] defines a type selector with
     an undeclared namespace prefix to be an invalid selector, and CSS
     [[CSS21]] requires rule sets with an invalid selector to be completely
     ignored.

>> Such handling should treat undeclared namespace prefixes as a parsing
>> error that will cause the selector or declaration (etc.) to be considered
>> invalid and, in CSS, ignored.
> 
> Please explain the rationale for why this is not a MUST requirement, for
> example by citing a use-case for allowing the stylerule to not be ignored
> in this context.

This is a SHOULD requirement because it is vague and cannot be more precise:
it is not possible in this module to define exactly what portion of the host
language is invalid and how it is ignored.

~fantasai
Received on Monday, 10 March 2008 18:37:41 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:55:02 GMT