Skip to content

Commit 0e4279b

Browse files
fantasaifantasai
committed
SVG issues
1 parent fcf0ee8 commit 0e4279b

3 files changed

Lines changed: 132 additions & 27 deletions

File tree

‎css3-namespace/Overview.html‎

Lines changed: 69 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -15,11 +15,11 @@
1515

1616
<h1 id=css-namespaces>CSS Namespaces Module</h1>
1717

18-
<h2 class="no-num no-toc" id=longstatus>Editor's Draft 19 February 2008</h2>
18+
<h2 class="no-num no-toc" id=longstatus>Editor's Draft 10 March 2008</h2>
1919

2020
<dl>
2121
<dt>This version:</dt>
22-
<!-- <dd><a href="http://www.w3.org/TR/2008/WD-css3-namespace-20080219/">http://www.w3.org/TR/2008/WD-css3-namespace-20080219/</a></dd> -->
22+
<!-- <dd><a href="http://www.w3.org/TR/2008/WD-css3-namespace-20080310/">http://www.w3.org/TR/2008/WD-css3-namespace-20080310/</a></dd> -->
2323

2424
<dd><a
2525
href="http://dev.w3.org/csswg/css3-namespace/">http://dev.w3.org/csswg/css3-namespace/</a>
@@ -101,7 +101,12 @@ <h2 class="no-num no-toc" id=status>Status of this document</h2>
101101
Policy</a>. W3C maintains a <a href="/2004/01/pp-impl/32061/status"
102102
rel=disclosure>public list of any patent disclosures</a> made in
103103
connection with the deliverables of the group; that page also includes
104-
instructions for disclosing a patent.</p>
104+
instructions for disclosing a patent. An individual who has actual
105+
knowledge of a patent which the individual believes contains <a
106+
href="/Consortium/Patent-Policy-20040205/#def-essential">Essential
107+
Claim(s)</a> must disclose the information in accordance with <a
108+
href="/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 6 of the
109+
W3C Patent Policy</a>.</p>
105110
<!--end-status-->
106111

107112
<p>This specification is a <strong>Last Call Working Draft</strong>. All
@@ -269,6 +274,24 @@ <h2 id=declaration><span class=secno>3. </span>Declaring namespaces: the
269274
of the namespace prefixes used in the markup and whether these are
270275
defaulted or not.</p>
271276

277+
<div class=example>
278+
<p>For example, given the following XML document:</p>
279+
280+
<pre><!--
281+
-->&lt;qml:elem xmlns:qml="http://example.com/q-markup">&lt;/qml:elem><!--
282+
--></pre>
283+
284+
<p>and the following <code>@namespace</code> declarations:</p>
285+
286+
<pre><!--
287+
-->@namespace Q "http://example.com/q-markup";
288+
<!---->@namespace lq "http://example.com/q-markup";<!--
289+
--></pre>
290+
291+
<p>The selectors <code>Q|elem</code> and <code>lq|elem</code> will both
292+
match the element <code>qml:elem</code>.</p>
293+
</div>
294+
272295
<h3 id=syntax><span class=secno>3.1 </span>Syntax</h3>
273296

274297
<p>The syntax for the @namespace rule is as follows (using the notation
@@ -321,10 +344,10 @@ <h3 id=prefixes><span class=secno>3.3 </span>Declaring Prefixes</h3>
321344

322345
<p>If in the namespace declaration the namespace prefix is omitted, then
323346
the namespace so declared is the default namespace. The <dfn
324-
id=default>default namespace</dfn> applies to names that have no explicit
325-
namespace prefix. Modules that employ namespace prefixes must define in
326-
which contexts the default namespace applies. For example, following <a
327-
href="#REC-XML-NAMES"
347+
id=default>default namespace</dfn> may apply to names that have no
348+
explicit namespace prefix: modules that employ namespace prefixes must
349+
define in which contexts the default namespace applies. For example,
350+
following <a href="#REC-XML-NAMES"
328351
rel=biblioentry>[REC-XML-NAMES]<!--{{!REC-XML-NAMES}}--></a>, in
329352
Selectors <a href="#SELECT" rel=biblioentry>[SELECT]<!--{{SELECT}}--></a>
330353
the default namespace applies to type selectors&#8212;but it does not
@@ -352,9 +375,10 @@ <h2 id=css-qnames><span class=secno>4. </span>CSS Qualified Names</h2>
352375
representing the namespace for which it has been declared, indicates the
353376
namespace of the local name. The prefix of a qualified name may be
354377
omitted to indicate that the name belongs to no namespace, i.e. that the
355-
namespace name part of the expanded name has no value. Some contexts may
356-
allow the use of an asterisk (<code>*</code>, U+002A) as a wildcard
357-
prefix to indicate a name in any namespace, including no namespace.</p>
378+
namespace name part of the expanded name has no value. Some contexts (as
379+
defined by the host language) may allow the use of an asterisk
380+
(<code>*</code>, U+002A) as a wildcard prefix to indicate a name in any
381+
namespace, including no namespace.</p>
358382

359383
<div class=example>
360384
<p>Given the namespace declarations:</p>
@@ -394,6 +418,14 @@ <h2 id=css-qnames><span class=secno>4. </span>CSS Qualified Names</h2>
394418
CSS, <a
395419
href="http://www.w3.org/TR/CSS21/conform.html#ignore">ignored</a>.</p>
396420

421+
<div class=example>
422+
<p>For example, the Selectors module <a href="#SELECT"
423+
rel=biblioentry>[SELECT]<!--{{SELECT}}--></a> defines a type selector
424+
with an undeclared namespace prefix to be an invalid selector, and CSS
425+
<a href="#CSS21" rel=biblioentry>[CSS21]<!--{{CSS21}}--></a> requires
426+
rule sets with an invalid selector to be completely ignored.</p>
427+
</div>
428+
397429
<p>In a CSS qualified name, a prefix that is declared to represent the
398430
empty string namespace (<code>""</code>) is interpreted as representing
399431
no namespace.</p>
@@ -422,25 +454,28 @@ <h3 class=no-num id=normative-references>Normative references</h3>
422454

423455
<dt id=CSS21>[CSS21]
424456

425-
<dd>Bert Bos; et al. <cite>Cascading Style Sheets, level 2 revision
426-
1.</cite> 19 July 2007. W3C Candidate Recommendation. (Work in progress.)
427-
URL: <a
457+
<dd>Bert Bos; et al. <a
458+
href="http://www.w3.org/TR/2007/CR-CSS21-20070719"><cite>Cascading Style
459+
Sheets, level 2 revision 1.</cite></a> 19 July 2007. W3C Candidate
460+
Recommendation. (Work in progress.) URL: <a
428461
href="http://www.w3.org/TR/2007/CR-CSS21-20070719">http://www.w3.org/TR/2007/CR-CSS21-20070719</a>
429462
</dd>
430463
<!---->
431464

432465
<dt id=REC-XML-NAMES>[REC-XML-NAMES]
433466

434-
<dd>Tim Bray; et al. <cite>Namespaces in XML.</cite> 16 August 2006. W3C
435-
Recommendation. URL: <a
467+
<dd>Tim Bray; et al. <a
468+
href="http://www.w3.org/TR/2006/REC-xml-names-20060816"><cite>Namespaces
469+
in XML.</cite></a> 16 August 2006. W3C Recommendation. URL: <a
436470
href="http://www.w3.org/TR/2006/REC-xml-names-20060816">http://www.w3.org/TR/2006/REC-xml-names-20060816</a>
437471
</dd>
438472
<!---->
439473

440474
<dt id=RFC2119>[RFC2119]
441475

442-
<dd>S. Bradner. <cite>Key words for use in RFCs to Indicate Requirement
443-
Levels.</cite> Internet RFC 2119. URL: <a
476+
<dd>S. Bradner. <a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>Key
477+
words for use in RFCs to Indicate Requirement Levels.</cite></a> Internet
478+
RFC 2119. URL: <a
444479
href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a>
445480
</dd>
446481
<!---->
@@ -455,20 +490,31 @@ <h3 class=no-num id=informative-references>Informative references</h3>
455490
<dt style="display: none"><!-- keeps the doc valid if the DL is empty -->
456491
<!---->
457492

493+
<dt id=CSS21>[CSS21]
494+
495+
<dd>Bert Bos; et al. <a
496+
href="http://www.w3.org/TR/2007/CR-CSS21-20070719"><cite>Cascading Style
497+
Sheets, level 2 revision 1.</cite></a> 19 July 2007. W3C Candidate
498+
Recommendation. (Work in progress.) URL: <a
499+
href="http://www.w3.org/TR/2007/CR-CSS21-20070719">http://www.w3.org/TR/2007/CR-CSS21-20070719</a>
500+
</dd>
501+
<!---->
502+
458503
<dt id=CSS3VAL>[CSS3VAL]
459504

460-
<dd>H&#229;kon Wium Lie; Chris Lilley. <cite>CSS3 module: Values and
461-
Units.</cite> 19 September 2006. W3C Working Draft. (Work in progress.)
462-
URL: <a
505+
<dd>H&#229;kon Wium Lie; Chris Lilley. <a
506+
href="http://www.w3.org/TR/2006/WD-css3-values-20060919"><cite>CSS3
507+
module: Values and Units.</cite></a> 19 September 2006. W3C Working
508+
Draft. (Work in progress.) URL: <a
463509
href="http://www.w3.org/TR/2006/WD-css3-values-20060919">http://www.w3.org/TR/2006/WD-css3-values-20060919</a>
464510
</dd>
465511
<!---->
466512

467513
<dt id=SELECT>[SELECT]
468514

469-
<dd>Daniel Glazman; Tantek &#199;elik; Ian Hickson (eds).
470-
<cite>Selectors.</cite> 15 December 2005. W3C Working Draft. (Work in
471-
progress.) URL: <a
515+
<dd>Daniel Glazman; Tantek &#199;elik; Ian Hickson (eds). <a
516+
href="http://www.w3.org/TR/2005/WD-css3-selectors-20051215"><cite>Selectors.</cite></a>
517+
15 December 2005. W3C Working Draft. (Work in progress.) URL: <a
472518
href="http://www.w3.org/TR/2005/WD-css3-selectors-20051215">http://www.w3.org/TR/2005/WD-css3-selectors-20051215</a>
473519
</dd>
474520
<!---->

‎css3-namespace/Overview.src.html‎

Lines changed: 26 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -169,6 +169,20 @@ <h2 id="declaration">Declaring namespaces: the <code>@namespace</code> rule</h2>
169169
defaulted or not, are independent of the namespace prefixes used in the
170170
markup and whether these are defaulted or not.</p>
171171

172+
<div class="example">
173+
<p>For example, given the following XML document:</p>
174+
<pre><!--
175+
-->&lt;qml:elem xmlns:qml="http://example.com/q-markup">&lt;/qml:elem><!--
176+
--></pre>
177+
<p>and the following <code>@namespace</code> declarations:</p>
178+
<pre><!--
179+
-->@namespace Q "http://example.com/q-markup";
180+
<!---->@namespace lq "http://example.com/q-markup";<!--
181+
--></pre>
182+
<p>The selectors <code>Q|elem</code> and <code>lq|elem</code> will both
183+
match the element <code>qml:elem</code>.</p>
184+
</div>
185+
172186
<h3 id="syntax">Syntax</h3>
173187
<p>The syntax for the @namespace rule is as follows (using the notation from
174188
the <a href="http://www.w3.org/TR/CSS21/grammar.html">Grammar appendix of
@@ -218,8 +232,8 @@ <h3 id="prefixes">Declaring Prefixes</h3>
218232

219233
<p>If in the namespace declaration the namespace prefix is omitted, then the
220234
namespace so declared is the default namespace. The <dfn>default
221-
namespace</dfn> applies to names that have no explicit namespace prefix.
222-
Modules that employ namespace prefixes must define in which contexts the
235+
namespace</dfn> may apply to names that have no explicit namespace prefix:
236+
modules that employ namespace prefixes must define in which contexts the
223237
default namespace applies. For example, following [[!REC-XML-NAMES]], in
224238
Selectors [[SELECT]] the default namespace applies to type
225239
selectors&#8212;but it does not apply to attribute selectors. There is no
@@ -246,8 +260,9 @@ <h2 id="css-qnames">CSS Qualified Names</h2>
246260
The prefix of a qualified name may be omitted to indicate that the name
247261
belongs to no namespace, i.e. that the namespace name part of the expanded
248262
name has no value.
249-
Some contexts may allow the use of an asterisk (<code>*</code>, U+002A) as a
250-
wildcard prefix to indicate a name in any namespace, including no namespace.</p>
263+
Some contexts (as defined by the host language) may allow the use of an asterisk
264+
(<code>*</code>, U+002A) as a wildcard prefix to indicate a name in any namespace,
265+
including no namespace.</p>
251266

252267
<div class="example">
253268
<p>Given the namespace declarations:</p>
@@ -279,6 +294,13 @@ <h2 id="css-qnames">CSS Qualified Names</h2>
279294
cause the selector or declaration (etc.) to be considered invalid and, in
280295
CSS, <a href="http://www.w3.org/TR/CSS21/conform.html#ignore">ignored</a>.</p>
281296

297+
<div class="example">
298+
<p>For example, the Selectors module [[SELECT]] defines a type selector with
299+
an undeclared namespace prefix to be an invalid selector, and CSS
300+
[[CSS21]] requires rule sets with an invalid selector to be completely
301+
ignored.</p>
302+
</div>
303+
282304
<p>In a CSS qualified name, a prefix that is declared to represent the
283305
empty string namespace (<code>""</code>) is interpreted as representing
284306
no namespace.</p>

‎css3-namespace/issues-2.txt‎

Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -14,3 +14,40 @@ Comment: http://lists.w3.org/Archives/Public/www-style/2008Feb/0148.html
1414
Response: http://lists.w3.org/Archives/Public/www-style/2008Feb/0199.html
1515
Closed: Accepted
1616
----
17+
Issue 3.
18+
Summary: Example numbering off
19+
From: Erik Dahlstrom, on behalf of SVGWG
20+
Comment: http://lists.w3.org/Archives/Public/www-style/2008Mar/0128.html
21+
Response: http://lists.w3.org/Archives/Public/www-style/2008Mar/0135.html
22+
Closed: Accepted
23+
----
24+
Issue 4.
25+
Summary: Change order requirements for @namespace
26+
From: Erik Dahlstrom, on behalf of SVGWG
27+
Comment: http://lists.w3.org/Archives/Public/www-style/2008Mar/0129.html
28+
Response: http://lists.w3.org/Archives/Public/www-style/2008Mar/0133.html
29+
Response: http://lists.w3.org/Archives/Public/www-style/2008Mar/0136.html
30+
Closed: Rejected
31+
----
32+
Issue 5.
33+
Summary: Concerns about asterisk definitions
34+
From: Erik Dahlstrom, on behalf of SVGWG
35+
Comment: http://lists.w3.org/Archives/Public/www-style/2008Mar/0130.html
36+
Response: http://lists.w3.org/Archives/Public/www-style/2008Mar/0134.html
37+
Response: http://lists.w3.org/Archives/Public/www-style/2008Mar/0139.html
38+
Closed: Accepted
39+
----
40+
Issue 6.
41+
Summary: Conflict in application of default namespace
42+
From: Erik Dahlstrom, on behalf of SVGWG
43+
Comment: http://lists.w3.org/Archives/Public/www-style/2008Mar/0131.html
44+
Response: http://lists.w3.org/Archives/Public/www-style/2008Mar/0141.html
45+
Closed: Accepted
46+
----
47+
Issue 7.
48+
Summary: Add example of non-matching prefixes denoting the same expanded name
49+
From: Erik Dahlstrom, on behalf of SVGWG
50+
Comment: http://lists.w3.org/Archives/Public/www-style/2008Mar/0132.html
51+
Response:
52+
Closed: Accepted
53+
----

0 commit comments

Comments
 (0)