1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
|
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html lang="en" xml:lang="en" xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta name="generator" content="HTML Tidy, see www.w3.org" />
<title>XHTML 1.0 - Normative Definition of XHTML 1.0</title>
<link rel="stylesheet" type="text/css" media="screen" href="xhtml.css" />
<link rel="stylesheet" type="text/css" media="screen" href="W3C-REC.css" />
</head>
<body>
<div class="navbar">[<a href="definitions.html">previous</a>]   [<a href="diffs.html">next</a>]   [<a href="Cover.html#toc">table of contents</a>]
<hr />
</div>
<h1><a name="normative" id="normative">3.</a> Normative Definition of XHTML 1.0</h1>
<div class='subtoc'>
<p><strong>Contents</strong></p>
<ul class='toc'>
<li class='tocline'>3.1. <a href="#docconf" class="tocxref">Document Conformance</a>
<ul class="toc">
<li class='tocline'>3.1.1. <a href="#strict" class="tocxref">Strictly Conforming Documents</a></li>
<li class='tocline'>3.1.2. <a href="#well-formed" class="tocxref">Using XHTML with other namespaces</a></li>
</ul>
</li>
<li class='tocline'>3.2. <a href="#uaconf" class="tocxref">User Agent Conformance</a></li>
</ul>
</div>
<p><strong>This section is normative.</strong></p>
<h2><a name="docconf" id="docconf">3.1.</a> Document Conformance</h2>
<p>This version of XHTML provides a definition of strictly conforming XHTML 1.0 documents, which are restricted to elements and attributes from the XML and XHTML 1.0 namespaces. See <a href=
"#well-formed">Section 3.1.2</a> for information on using XHTML with other namespaces, for instance, to include metadata expressed in <abbr title="Resource Description Format">RDF</abbr> within XHTML
documents.</p>
<h3><a name="strict" id="strict">3.1.1.</a> Strictly Conforming Documents</h3>
<p>A Strictly Conforming XHTML Document is an XML document that requires only the facilities described as mandatory in this specification. Such a document must meet all of the following criteria:</p>
<ol>
<li>
<p>It must conform to the constraints expressed in one of the three DTDs found in <a href="dtds.html#dtds">DTDs</a> and in <a href="prohibitions.html#prohibitions">Appendix B</a>.</p>
</li>
<li>
<p>The root element of the document must be <code>html</code>.</p>
</li>
<li>
<p>The root element of the document must contain an <code>xmlns</code> declaration for the XHTML namespace [<a class="nref" href="references.html#ref-xmlns">XMLNS</a>]. The namespace for XHTML is
defined to be <code>http://www.w3.org/1999/xhtml</code>. An example root element might look like:</p>
<div class="good">
<pre>
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
</pre>
</div>
</li>
<li>
<p>There must be a DOCTYPE declaration in the document prior to the root element. The public identifier included in the DOCTYPE declaration must reference one of the three DTDs found in <a href=
"dtds.html#dtds">DTDs</a> using the respective Formal Public Identifier. The system identifier may be changed to reflect local system conventions.</p>
<pre>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Frameset//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-frameset.dtd">
</pre>
</li>
<li>
<p>The DTD subset must not be used to override any parameter entities in the DTD.</p>
</li>
</ol>
<p>An XML declaration is not required in all XML documents; however XHTML document authors are strongly encouraged to use XML declarations in all their documents. Such a declaration is required when
the character encoding of the document is other than the default UTF-8 or UTF-16 and no encoding was determined by a higher-level protocol. Here is an example of an XHTML document. In this example,
the XML declaration is included.</p>
<div class="good">
<pre>
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<title>Virtual Library</title>
</head>
<body>
<p>Moved to <a href="http://example.org/">example.org</a>.</p>
</body>
</html>
</pre>
</div>
<h3><a name="well-formed" id="well-formed">3.1.2.</a> Using XHTML with other namespaces</h3>
<p>The XHTML namespace may be used with other XML namespaces as per [<a class="nref" href="references.html#ref-xmlns">XMLNS</a>], although such documents are not strictly conforming XHTML 1.0
documents as defined above. Work by W3C is addressing ways to specify conformance for documents involving multiple namespaces. For an example, see [<a class="nref" href=
"references.html#ref-xhtml-mathml">XHTML+MathML</a>].</p>
<p>The following example shows the way in which XHTML 1.0 could be used in conjunction with the MathML Recommendation:</p>
<div class="good">
<pre>
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<title>A Math Example</title>
</head>
<body>
<p>The following is MathML markup:</p>
<math xmlns="http://www.w3.org/1998/Math/MathML">
<apply> <log/>
<logbase>
<cn> 3 </cn>
</logbase>
<ci> x </ci>
</apply>
</math>
</body>
</html>
</pre>
</div>
<p>The following example shows the way in which XHTML 1.0 markup could be incorporated into another XML namespace:</p>
<div class="good">
<pre>
<?xml version="1.0" encoding="UTF-8"?>
<!-- initially, the default namespace is "books" -->
<book xmlns='urn:loc.gov:books'
xmlns:isbn='urn:ISBN:0-395-36341-6' xml:lang="en" lang="en">
<title>Cheaper by the Dozen</title>
<isbn:number>1568491379</isbn:number>
<notes>
<!-- make HTML the default namespace for a hypertext commentary -->
<p xmlns='http://www.w3.org/1999/xhtml'>
This is also available <a href="http://www.w3.org/">online</a>.
</p>
</notes>
</book>
</pre>
</div>
<h2><a name="uaconf" id="uaconf">3.2.</a> User Agent Conformance</h2>
<p>A conforming user agent must meet all of the following criteria:</p>
<ol>
<li>In order to be consistent with the XML 1.0 Recommendation [<a class="nref" href="references.html#ref-xml">XML</a>], the user agent must parse and evaluate an XHTML document for well-formedness.
If the user agent claims to be a validating user agent, it must also validate documents against their referenced DTDs according to [<a class="nref" href="references.html#ref-xml">XML</a>].</li>
<li>When the user agent claims to support <a href="definitions.html#facilities">facilities</a> defined within this specification or required by this specification through normative reference, it must
do so in ways consistent with the facilities' definition.</li>
<li>When a user agent processes an XHTML document as generic XML, it shall only recognize attributes of type <code>ID</code> (i.e. the <code>id</code> attribute on most XHTML elements) as fragment
identifiers.</li>
<li>If a user agent encounters an element it does not recognize, it must process the element's content.</li>
<li>If a user agent encounters an attribute it does not recognize, it must ignore the entire attribute specification (i.e., the attribute and its value).</li>
<li>If a user agent encounters an attribute value it does not recognize, it must use the default attribute value.</li>
<li>If it encounters an entity reference (other than one of the entities defined in this recommendation or in the XML recommendation) for which the user agent has processed no declaration (which
could happen if the declaration is in the external subset which the user agent hasn't read), the entity reference should be processed as the characters (starting with the ampersand and ending with
the semi-colon) that make up the entity reference.</li>
<li>When processing content, user agents that encounter characters or character entity references that are recognized but not renderable may substitute another rendering that gives the same meaning,
or must display the document in such a way that it is obvious to the user that normal rendering has not taken place.</li>
<li>
<p>White space is handled according to the following rules. The following characters are defined in [<a class="nref" href="references.html#ref-xml">XML</a>] white space characters:</p>
<ul>
<li>SPACE (&#x0020;)</li>
<li>HORIZONTAL TABULATION (&#x0009;)</li>
<li>CARRIAGE RETURN (&#x000D;)</li>
<li>LINE FEED (&#x000A;)</li>
</ul>
<p>The XML processor normalizes different systems' line end codes into one single LINE FEED character, that is passed up to the application.</p>
<p>The user agent must use the definition from CSS for processing whitespace characters [<a class="nref" href="references.html#ref-css2">CSS2</a>]. <em>Note that the CSS2 recommendation does not
explicitly address the issue of whitespace handling in non-Latin character sets. This will be addressed in a future version of CSS, at which time this reference will be updated.</em></p>
</li>
</ol>
<p>Note that in order to produce a Canonical XHTML document, the rules above must be applied and the rules in [<a class="nref" href="references.html#ref-xmlc14n">XMLC14N</a>] must also be applied to
the document.</p>
<hr />
<div class="navbar">[<a href="definitions.html">previous</a>]   [<a href="diffs.html">next</a>]   [<a href="Cover.html#toc">table of contents</a>]</div>
</body>
</html>
|
