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

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

From: Erik Dahlström <ed@opera.com>
Date: Tue, 11 Mar 2008 16:05:52 +0100
To: fantasai <fantasai.lists@inkedblade.net>
Cc: "www-style@w3.org" <www-style@w3.org>, www-svg@w3.org
Message-ID: <op.t7uxj2r3gqiacl@gnorps.palace.opera.no>

On Mon, 10 Mar 2008 18:38:02 +0100, fantasai  
<fantasai.lists@inkedblade.net> wrote:

> 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.

Thank you, with those two changes we consider this comment resolved to our  
satisfaction.

>>> 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.

Fair enough, thanks for the explanation.

Regards
/Erik, on behalf of the SVG WG

-- 
Erik Dahlstrom, Core Technology Developer, Opera Software
Co-Chair, W3C SVG Working Group
Personal blog: http://my.opera.com/macdev_ed
Received on Tuesday, 11 March 2008 15:06:12 GMT

This archive was generated by hypermail 2.3.1 : Friday, 8 March 2013 15:54:38 GMT