- From: fantasai <fantasai.lists@inkedblade.net>
- Date: Wed, 23 Apr 2008 10:22:38 -0700
- To: www-style@w3.org
fantasai wrote:
>
> Proposed changes:
>
> Change #2: Add to section 3.3: Declaring prefixes
>
> | Where the empty string is not recognized as a possible namespace,
> | local names associated with an empty string default namespace
> | must be interpreted as being associated with no namespace.
>
> to define what the empty string means as a default namespace.
>
> Change #3: Replace in section 4: CSS Qualified Names
>
> | In a CSS qualified name, a prefix that is declared to represent the
> | empty string namespace ("") is interpreted as representing no
> namespace.
>
> with
>
> | When a CSS qualified name is used in a context (such as Selectors
> | [[SELECT]]) that does not recognize association with the empty
> | string namespace and lack of a namespace as two distinct, valid
> | possibilities, prefixes representing the empty string namespace
> | and no namespace must be treated as equivalent.
Anne and I decided to instead remove the above sentence in section 4
and add the following sentence (and the new example below) to Section 2.1
instead:
| In CSS Namespaces a namespace name consisting of the empty string
| is taken to represent the null namespace or lack of a namespace.
> | For example, given the namespace declarations:
> |
> | @namespace empty "";
> | @namespace "";
> |
> | The type selectors elem, |elem, and empty|elem are equivalent.
The edits are in this version of the Editor's draft:
http://dev.w3.org/cvsweb/~checkout~/csswg/css3-namespace/Overview.html?rev=1.35
~fantasai
Received on Wednesday, 23 April 2008 17:23:20 UTC