0% found this document useful (0 votes)

189 views

XHTML 2

Xhtml 2. Manual downloaded from w3c. Pdf format. 251 pages.

Uploaded by

api-3774955

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

189 views

XHTML 2

Xhtml 2. Manual downloaded from w3c. Pdf format. 251 pages.

Uploaded by

api-3774955

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 251

XHTML™ 2.0 XHTML™ 2.

XHTML™ 2.0
W3C Working Draft 26 July 2006
This version:
http://www.w3.org/TR/2006/WD-xhtml2-20060726
Latest version:
http://www.w3.org/TR/xhtml2
Previous version:
http://www.w3.org/TR/2005/WD-xhtml2-20050527
Diff-marked version:
xhtml2-diff.html
Editors:
Jonny Axelsson, Opera Software
Mark Birbeck, x-port.net
Micah Dubinko, Invited Expert
Beth Epperson, Websense
Masayasu Ishikawa, W3C
Shane McCarron, Applied Testing and Technology
Ann Navarro, WebGeek, Inc.
Steven Pemberton, CWI (HTML Working Group Chair)

This document is also available in these non-normative formats: Single XHTML file [p.1] ,
PostScript version, PDF version, ZIP archive, and Gzip’d TAR archive.

Abstract
XHTML 2 is a general-purpose markup language designed for representing documents for a
wide range of purposes across the World Wide Web. To this end it does not attempt to be all
things to all people, supplying every possible markup idiom, but to supply a generally useful set
of elements.

Status of This Document

This section describes the status of this document at the time of its publication. Other
documents may supersede this document. A list of current W3C publications and the latest
revision of this technical report can be found in the W3C technical reports index at

-1-
Quick Table of Contents XHTML™ 2.0

http://www.w3.org/TR/.

This document is the eighth public Working Draft of this specification. It should in no way be
considered stable, and should not be normatively referenced for any purposes whatsoever. This
version includes an early implementation of XHTML 2.0 in RELAX NG [RELAXNG [p.247] ], but
does not include the implementations in DTD or XML Schema form. Those will be included in
subsequent versions, once the content of this language stabilizes.

Formal issues and error reports on this specification shall be submitted to

[email protected] (archive). It is inappropriate to send discussion email to this address.
Public discussion may take place on [email protected] (archive). To subscribe send an email
to [email protected] with the word subscribe in the subject line.

This document has been produced by the W3C HTML Working Group (members only) as part of
the W3C HTML Activity. The goals of the HTML Working Group are discussed in the HTML
Working Group charter.

This document was produced by a group operating under the 24 January 2002 CPP as
amended by the W3C Patent Policy Transition Procedure. W3C maintains a public list of any
patent disclosures made in connection with the deliverables of the group; that page also
includes instructions for disclosing a patent. An individual who has actual knowledge of a patent
which the individual believes contains Essential Claim(s) must disclose the information in
accordance with section 6 of the W3C Patent Policy.

Publication as a Working Draft does not imply endorsement by the W3C Membership. This is a
draft document and may be updated, replaced or obsoleted by other documents at any time. It is
inappropriate to cite this document as other than work in progress.

Quick Table of Contents

1. Introduction
2. Terms and Definitions . . . . . . . . . . . . . . . 17
.
3. Conformance Definition
4. The XHTML 2.0 Document Type . . . . . . . . . . . . . 25
.
5. Module Definition Conventions . . . . . . . . . . . . . 27
.
6. XHTML Attribute Collections . . . . . . . . . . . . . . 33
.
7. XHTML Document Module . . . . . . . . . . . . . . 37
.
8. XHTML Structural Module . . . . . . . . . . . . . . 41
.
9. XHTML Text Module . . . . . . . . . . . . . . . . 51
.
10. XHTML Hypertext Module . . . . . . . . . . . . . . 59
.
11. XHTML List Module . . . . . . . . . . . . . . . . 61
.
12. XHTML Core Attributes Module . . . . . . . . . . . . . 67
.
13. XHTML Hypertext Attributes Module . . . . . . . . . . . . 71
.
14. XHTML I18N Attribute Module . . . . . . . . . . . . . 77
.
15. XHTML Access Module . . . . . . . . . . . . . . . 79
.

-2-
XHTML™ 2.0 List of Issues

16. XHTML Bi-directional Text Attribute Module . . . . . . . . . . 81

.
17. XHTML Edit Attributes Module . . . . . . . . . . . . . 85
.
18. XHTML Embedding Attributes Module . . . . . . . . . . . 87
.
19. XHTML Handler Module . . . . . . . . . . . . . . . 91
.
20. XHTML Image Module . . . . . . . . . . . . . . . 93
.
21. XHTML Image Map Attributes Module . . . . . . . . . . . 95
.
22. XHTML Media Attribute Module . . . . . . . . . . . . . 99
.
23. XHTML Metainformation Module . . . . . . . . . . . . 101
.
24. XHTML Metainformation Attributes Module . . . . . . . . . . 113
.
25. XHTML Object Module . . . . . . . . . . . . . . . 121
.
26. XHTML Role Attribute Module . . . . . . . . . . . . . 131
.
27. Ruby Module . . . . . . . . . . . . . . . . . 133
.
28. XHTML Style Attribute Module . . . . . . . . . . . . . 135
.
29. XHTML Style Sheet Module . . . . . . . . . . . . . . 137
.
30. XHTML Tables Module . . . . . . . . . . . . . . . 141
.
31. XForms Module . . . . . . . . . . . . . . . . . 163
.
32. XML Events Module . . . . . . . . . . . . . . . . 167
.
A. Changes from XHTML 1.1 . . . . . . . . . . . . . . 169
.
B. XHTML 2.0 RELAX NG Definition . . . . . . . . . . . . 171
.
C. XHTML RELAX NG Module Implementations . . . . . . . . . . 175
.
D. XHTML 2.0 Schema . . . . . . . . . . . . . . . . 227
.
E. XHTML Schema Module Implementations . . . . . . . . . . 229
.
F. XHTML 2.0 Document Type Definition . . . . . . . . . . . 231
.
G. XHTML DTD Module Implementations . . . . . . . . . . . 233
.
H. Style sheet for XHTML 2 . . . . . . . . . . . . . . . 235
.
I. Example RDF Specification for Roles . . . . . . . . . . . . 239
.
J. List of Elements . . . . . . . . . . . . . . . . . 241
.
K. List of Attributes . . . . . . . . . . . . . . . . . 243
.
L. Cross-reference Index . . . . . . . . . . . . . . . 245
.
M. References . . . . . . . . . . . . . . . . . . 247
.
N. Acknowledgements . . . . . . . . . . . . . . . . 251
.

List of Issues
1. [PR #7759] [XHTML2] Spirit of "1.1.3. XHTML 2 and Presentation"
2. [PR #7723] On introducing a fallback attribute
3. [PR #7777] [XHTML 2] Conforming documents and meta properties
4. [PR #7791] Fw: [XHTML 2] Section 3.1.1
5. [PR #7804] Comments on XHTML 2.0 document conformance requirements
6. [PR #7808] Change XHTML 2.0 namespace to http://www.w3.org/1999/xhtml
7. [PR #7818] Namespace versioning problem in XHTML 2
8. [PR #7819] Referance XML 1.1 and example with XML 1.1 declaration
9. [PR #7336] Identifying XHTML version in ansence of DTDs

-3-
List of Issues XHTML™ 2.0

10. [PR #7799] Fw: [XHTML 2] Section 5.5 quality values.

11. [PR #7800] Fw: [XHTML 2] Section 5.5 intersection of mime-types
12. [PR #7661] [XHTML2] Constraining attribute relationship
13. Need a normative definition for the version attribute
14. [PR #7820] [XHTML2] How are UAs to interpret <h> and <hx> elements?
15. [PR #7830] [XHTML2] How are UAs to interpret <h> and <hx> elements?
16. [PR #7874] block@kind vs elt@structure
17. [PR #7875] redundant content model
18. [PR #7877] headings -- numbered vs bare
19. [PR #7876] PCData not in Text
20. [PR #7882] XHTML 2.0: Text Module/<l> vs. <br /> element
21. [PR #7885] RE: [ off list ] XHTML 2.0 - dfn : Content model and usability
22. [PR #7663] [XHTML2] 11.3. The ol , and ul elements
23. [PR #7867] Re: WD-xhtml2-20040722: Some navigation list requirements (IMHO)
24. [PR #7872] attributes with no values
25. [PR #7792] Fw: [XHTML 2] 13.1 Hypertext Attributes Module - nextfocus
26. [PR #7883] Internationalization: translate attribute
27. [PR #7783] [XHTML 2] 15 Bi-directional text collection and embedded attributes?
28. [PR #7724] Re: Formal Response to My issue on styling embedding attributes.
29. [PR #7730] 17 Embedding Attributes User aborted downloads.
30. [PR #7731] 17 Embedding Attributes - Invalid XHTML 2 documents
31. [PR #7732] [XHTML 2] 17.1 Encoding attribute
32. [PR #7733] [XHTML 2] Embedding attributes and nextFocus
33. [PR #7734] 17 Embedding Attributes Success/Failure status codes.
34. [PR #7735] [XHTML 2] 17 Embedding Attributes - srcType
35. [PR #7736] [XHTML 2] Embedding XHTML Resources Linking.
36. [PR #7737] [XHTML 2] Embedded Resources containing links
37. [PR #7738] [XHTML 2] Embedding Attributes Examples
38. [PR #7739] [XHTML 2] 17 Clipping of embedded documents to viewport.
39. [PR #7774] [XHTML 2] 17 Embedding Attributes
40. [PR #7892] xhtml2 attributes type, srctype and hreftype
41. [PR #7869] rebuild link element: chapter, section / subsection
42. [PR #7870] RE: [BULK] - Re: [XHTML2] Spirit of "1.1.3. XHTML 2 and Presentation"
43. [PR #7871] Re: [BULK] - Re: [XHTML2] Spirit of "1.1.3. XHTML 2 and Presentation"
44. [PR #7828] Why no nested colgroup or rowgroup?
45. [PR #7878] What is the scope of a header?
46. [PR #7879] td/th scope attribute - rowgroup == (tbody, thead, tfoot)
47. [PR #7881] nesting colgroup and rowgroups
48. [PR #7826] [XHTML2] exclude switch and case as presentational
49. [PR #7838] autocomplete attribute
50. [PR #670] Entity management: do we still need it?
51. [PR #671] Character entities: do we still need them?

-4-
XHTML™ 2.0 Full Table of Contents

Full Table of Contents

1. Introduction
1.1. What is XHTML 2?
1.1.1. Design Aims
1.1.2. Backwards compatibility
1.1.3. XHTML 2 and Presentation
1.1.4. XHTML 2 and Linking
1.2. Major Differences with XHTML 1
1.3. What are the XHTML 2 Modules?
1.4. Issues
2. Terms and Definitions . . . . . . . . . . . . . . . 17
.
3. Conformance Definition
3.1. Document Conformance
3.1.1. Strictly Conforming Documents
3.2. XHTML 2 User Agent Conformance
3.3. Issues
4. The XHTML 2.0 Document Type . . . . . . . . . . . . . 25
.
4.1. Issues . . . . . . . . . . . . . . . . . . 26
.
5. Module Definition Conventions . . . . . . . . . . . . . 27
.
5.1. Module Structure . . . . . . . . . . . . . . . 27
.
5.2. Abstract Module Definitions . . . . . . . . . . . . 27
.
5.3. Syntactic Conventions . . . . . . . . . . . . . . 27
.
5.4. Content Models . . . . . . . . . . . . . . . 28
.
5.5. Attribute Types . . . . . . . . . . . . . . . 29
.
5.6. Issues . . . . . . . . . . . . . . . . . . 31
.
6. XHTML Attribute Collections . . . . . . . . . . . . . . 33
.
6.1. Issues . . . . . . . . . . . . . . . . . . 35
.
7. XHTML Document Module . . . . . . . . . . . . . . 37
.
7.1. The html element . . . . . . . . . . . . . . . 38
.
7.2. The head element . . . . . . . . . . . . . . . 38
.
7.3. The title element . . . . . . . . . . . . . . . 39
.
7.4. The body element . . . . . . . . . . . . . . . 39
.
8. XHTML Structural Module . . . . . . . . . . . . . . 41
.
8.1. The address element . . . . . . . . . . . . . . 43
.
8.2. The blockcode element . . . . . . . . . . . . . 43
.
8.3. The blockquote element . . . . . . . . . . . . . 44
.
8.4. The div element . . . . . . . . . . . . . . . 44
.
8.5. The heading elements . . . . . . . . . . . . . . 45
.
8.6. The p element . . . . . . . . . . . . . . . . 46
.
8.7. The pre element . . . . . . . . . . . . . . . 47
.
8.8. The section element . . . . . . . . . . . . . . 47
.
8.9. The separator element . . . . . . . . . . . . . . 48
.

-5-
Full Table of Contents XHTML™ 2.0

8.10. Issues . . . . . . . . . . . . . . . . . 49
.
9. XHTML Text Module . . . . . . . . . . . . . . . . 51
.
9.1. The abbr element . . . . . . . . . . . . . . . 52
.
9.2. The cite element . . . . . . . . . . . . . . . 52
.
9.3. The code element . . . . . . . . . . . . . . . 53
.
9.4. The dfn element . . . . . . . . . . . . . . . 53
.
9.5. The em element . . . . . . . . . . . . . . . 53
.
9.6. The kbd element . . . . . . . . . . . . . . . 54
.
9.7. The l element . . . . . . . . . . . . . . . . 54
.
9.8. The q element . . . . . . . . . . . . . . . . 55
.
9.9. The samp element . . . . . . . . . . . . . . . 55
.
9.10. The span element . . . . . . . . . . . . . . 56
.
9.11. The strong element . . . . . . . . . . . . . . 56
.
9.12. The sub element . . . . . . . . . . . . . . . 56
.
9.13. The sup element . . . . . . . . . . . . . . . 57
.
9.14. The var element . . . . . . . . . . . . . . . 57
.
9.15. Issues . . . . . . . . . . . . . . . . . 58
.
10. XHTML Hypertext Module . . . . . . . . . . . . . . 59
.
10.1. The a element . . . . . . . . . . . . . . . . 59
.
11. XHTML List Module . . . . . . . . . . . . . . . . 61
.
11.1. Definition lists: the dl, di, dt, and dd elements . . . . . . . . 62
.
11.2. The nl element . . . . . . . . . . . . . . . 63
.
11.3. The ol and ul elements . . . . . . . . . . . . . 64
.
11.4. The li element . . . . . . . . . . . . . . . 64
.
11.5. The label element . . . . . . . . . . . . . . 65
.
11.6. Issues . . . . . . . . . . . . . . . . . 65
.
12. XHTML Core Attributes Module . . . . . . . . . . . . . 67
.
12.1. Core Attribute Collection . . . . . . . . . . . . . 67
.
12.2. Issues . . . . . . . . . . . . . . . . . 69
.
13. XHTML Hypertext Attributes Module . . . . . . . . . . . . 71
.
13.1. Hypertext Attribute Collection . . . . . . . . . . . . 71
.
13.2. Issues . . . . . . . . . . . . . . . . . 75
.
14. XHTML I18N Attribute Module . . . . . . . . . . . . . 77
.
14.1. I18N Attribute Collection . . . . . . . . . . . . . 77
.
14.2. Issues . . . . . . . . . . . . . . . . . 78
.
15. XHTML Access Module . . . . . . . . . . . . . . . 79
.
15.1. The access element . . . . . . . . . . . . . . 79
.
16. XHTML Bi-directional Text Attribute Module . . . . . . . . . . 81
.
16.1. Bi-directional Text Collection . . . . . . . . . . . . 81
.
16.1.1. Inheritance of text direction information . . . . . . . . 81
.
16.1.2. The effect of style sheets on bidirectionality . . . . . . . 82
.
16.2. Issues . . . . . . . . . . . . . . . . . 83
.
17. XHTML Edit Attributes Module . . . . . . . . . . . . . 85
.

-6-
XHTML™ 2.0 Full Table of Contents

17.1. Edit Collection . . . . . . . . . . . . . . . . 85

.
18. XHTML Embedding Attributes Module . . . . . . . . . . . 87
.
18.1. Embedding Attribute Collection . . . . . . . . . . . 87
.
18.2. Issues . . . . . . . . . . . . . . . . . 88
.
19. XHTML Handler Module . . . . . . . . . . . . . . . 91
.
19.1. The handler element . . . . . . . . . . . . . . 91
.
19.1.1. Rules for processing handlers . . . . . . . . . . 91
.
19.1.2. Declaration of a handler language . . . . . . . . . 92
.
19.1.3. Dynamic modification of documents . . . . . . . . . 92
.
20. XHTML Image Module . . . . . . . . . . . . . . . 93
.
20.1. The img element . . . . . . . . . . . . . . . 93
.
21. XHTML Image Map Attributes Module . . . . . . . . . . . 95
.
21.1. Image Map Attribute Collection . . . . . . . . . . . 96
.
22. XHTML Media Attribute Module . . . . . . . . . . . . . 99
.
22.1. Media Attribute Collection . . . . . . . . . . . . . 99
.
23. XHTML Metainformation Module . . . . . . . . . . . . 101
.
23.1. The link element . . . . . . . . . . . . . . . 101
.
23.1.1. Forward and reverse links . . . . . . . . . . . 102
.
23.1.2. Links and search engines . . . . . . . . . . . 102
.
23.2. The meta element . . . . . . . . . . . . . . 103
.
23.2.1. meta and search engines . . . . . . . . . . . 104
.
23.3. Literals and Resources . . . . . . . . . . . . . 105
.
23.4. Document Properties . . . . . . . . . . . . . . 105
.
23.4.1. Literals . . . . . . . . . . . . . . . . 105
.
23.4.2. Resources . . . . . . . . . . . . . . . 107
.
23.4.3. Making Use of External Lists of Properties . . . . . . . 107
.
23.5. Properties of Other Resources . . . . . . . . . . . 108
.
23.5.1. Resources Within the Containing Document . . . . . . . 108
.
23.5.2. External Resources . . . . . . . . . . . . . 109
.
23.6. Chaining Metadata . . . . . . . . . . . . . . 109
.
23.7. Issues . . . . . . . . . . . . . . . . . 111
.
24. XHTML Metainformation Attributes Module . . . . . . . . . . 113
.
24.1. Metadata Attribute Collection . . . . . . . . . . . . 113
.
24.2. Meta and RDF . . . . . . . . . . . . . . . 118
.
24.3. Metadata as Content . . . . . . . . . . . . . . 118
.
24.4. Mapping Lexical Content . . . . . . . . . . . . . 120
.
25. XHTML Object Module . . . . . . . . . . . . . . . 121
.
25.1. The object element . . . . . . . . . . . . . . 121
.
25.1.1. Defining terminology . . . . . . . . . . . . 122
.
25.1.2. Basic Information for Object Handlers . . . . . . . . 122
.
25.1.3. Rules for processing objects . . . . . . . . . . . 123
.
25.2. The param element . . . . . . . . . . . . . . 126
.
25.2.1. Referencing object data . . . . . . . . . . . 128
.

-7-
Full Table of Contents XHTML™ 2.0

25.2.2. Object element declarations and instantiations . . . . . . 129

.
25.3. The standby element . . . . . . . . . . . . . . 130
.
26. XHTML Role Attribute Module . . . . . . . . . . . . . 131
.
26.1. Role Attribute Collection . . . . . . . . . . . . . 131
.
27. Ruby Module . . . . . . . . . . . . . . . . . 133
.
28. XHTML Style Attribute Module . . . . . . . . . . . . . 135
.
28.1. Style Attribute Collection . . . . . . . . . . . . . 135
.
28.2. Issues . . . . . . . . . . . . . . . . . 135
.
29. XHTML Style Sheet Module . . . . . . . . . . . . . . 137
.
29.1. The style element . . . . . . . . . . . . . . . 137
.
29.1.1. External style sheets . . . . . . . . . . . . 138
.
29.1.2. Preferred and alternate style sheets . . . . . . . . . 138
.
29.1.3. Specifying external style sheets . . . . . . . . . . 138
.
30. XHTML Tables Module . . . . . . . . . . . . . . . 141
.
30.1. The caption element . . . . . . . . . . . . . . 142
.
30.2. The col and colgroup elements . . . . . . . . . . . 142
.
30.2.1. Calculating the number of columns in a table . . . . . . . 144
.
30.3. The summary element . . . . . . . . . . . . . 145
.
30.4. The table element . . . . . . . . . . . . . . 145
.
30.4.1. Visual Rendering . . . . . . . . . . . . . 146
.
30.4.2. Table directionality . . . . . . . . . . . . . 146
.
30.4.3. Table rendering by non-visual user agents . . . . . . . 147
.
30.5. The tbody element . . . . . . . . . . . . . . 155
.
30.6. The td and th elements . . . . . . . . . . . . . 155
.
30.6.1. Cells that span several rows or columns . . . . . . . . 157
.
30.7. The thead and tfoot elements . . . . . . . . . . . . 160
.
30.8. The tr element . . . . . . . . . . . . . . . 161
.
30.9. Issues . . . . . . . . . . . . . . . . . 161
.
31. XForms Module . . . . . . . . . . . . . . . . . 163
.
31.1. Core XForms . . . . . . . . . . . . . . . . 163
.
31.2. XForms Actions . . . . . . . . . . . . . . . 163
.
31.3. Form Controls . . . . . . . . . . . . . . . 163
.
31.4. Group . . . . . . . . . . . . . . . . . 164
.
31.5. Switch . . . . . . . . . . . . . . . . . 164
.
31.6. Repeat . . . . . . . . . . . . . . . . . 164
.
31.7. XForms Repeat Attribute Collection . . . . . . . . . . 164
.
31.8. Other Attribute Collections . . . . . . . . . . . . 165
.
31.9. Issues . . . . . . . . . . . . . . . . . 165
.
32. XML Events Module . . . . . . . . . . . . . . . . 167
.
32.1. Events . . . . . . . . . . . . . . . . . 167
.
A. Changes from XHTML 1.1 . . . . . . . . . . . . . . 169
.
B. XHTML 2.0 RELAX NG Definition . . . . . . . . . . . . 171
.

-8-
XHTML™ 2.0 Full Table of Contents

B.0.1. RELAX NG XHTML 2.0 Driver . . . . . . . . . . 171

.
C. XHTML RELAX NG Module Implementations . . . . . . . . . . 175
.
C.1. XHTML Module Implementations . . . . . . . . . . . 175
.
C.1.1. Attribute Collections . . . . . . . . . . . . . 175
.
C.1.2. Document . . . . . . . . . . . . . . . 176
.
C.1.3. Structural . . . . . . . . . . . . . . . 178
.
C.1.4. Text . . . . . . . . . . . . . . . . 184
.
C.1.5. Hypertext . . . . . . . . . . . . . . . 188
.
C.1.6. List . . . . . . . . . . . . . . . . . 189
.
C.1.7. Core Attributes . . . . . . . . . . . . . . 193
.
C.1.8. Hypertext Attributes . . . . . . . . . . . . . 194
.
C.1.9. I18N Attribute . . . . . . . . . . . . . . 196
.
C.1.10. Access . . . . . . . . . . . . . . . 196
.
C.1.11. Bi-directional Text Attribute . . . . . . . . . . . 197
.
C.1.12. Edit Attributes . . . . . . . . . . . . . . 198
.
C.1.13. Embedding Attributes . . . . . . . . . . . . 198
.
C.1.14. Handler . . . . . . . . . . . . . . . 199
.
C.1.15. Image . . . . . . . . . . . . . . . . 200
.
C.1.16. Image Map Attributes . . . . . . . . . . . . 201
.
C.1.17. Media Attribute . . . . . . . . . . . . . . 202
.
C.1.18. Metainformation Attributes . . . . . . . . . . . 202
.
C.1.19. Metainformation . . . . . . . . . . . . . 203
.
C.1.20. Object . . . . . . . . . . . . . . . . 204
.
C.1.21. Role Access . . . . . . . . . . . . . . 206
.
C.1.22. Style Attribute . . . . . . . . . . . . . . 206
.
C.1.23. Style Sheet . . . . . . . . . . . . . . 207
.
C.1.24. Tables . . . . . . . . . . . . . . . . 207
.
C.2. XHTML RELAX NG Support Modules . . . . . . . . . . 212
.
C.2.1. Datatypes . . . . . . . . . . . . . . . 212
.
C.2.2. Events . . . . . . . . . . . . . . . . 216
.
C.2.3. Param . . . . . . . . . . . . . . . . 218
.
C.2.4. Caption . . . . . . . . . . . . . . . . 219
.
C.2.5. Role Attribute . . . . . . . . . . . . . . 219
.
C.3. RELAX NG External Modules . . . . . . . . . . . . 219
.
C.3.1. Ruby . . . . . . . . . . . . . . . . 220
.
C.3.2. Ruby Driver for Full Ruby Markup . . . . . . . . . 223
.
C.3.3. XML Events . . . . . . . . . . . . . . . 223
.
C.3.4. XML Schema instance . . . . . . . . . . . . 225
.
D. XHTML 2.0 Schema . . . . . . . . . . . . . . . . 227
.
E. XHTML Schema Module Implementations . . . . . . . . . . 229
.
F. XHTML 2.0 Document Type Definition . . . . . . . . . . . 231
.
F.1. Issues . . . . . . . . . . . . . . . . . . 231
.
G. XHTML DTD Module Implementations . . . . . . . . . . . 233
.

-9-
Full Table of Contents XHTML™ 2.0

G.1. XHTML Modular Framework . . . . . . . . . . . . 233

.
G.2. XHTML Module Implementations . . . . . . . . . . . 233
.
G.3. XHTML DTD Support Modules . . . . . . . . . . . . 233
.
H. Style sheet for XHTML 2 . . . . . . . . . . . . . . . 235
.
I. Example RDF Specification for Roles . . . . . . . . . . . . 239
.
J. List of Elements . . . . . . . . . . . . . . . . . 241
.
K. List of Attributes . . . . . . . . . . . . . . . . . 243
.
L. Cross-reference Index . . . . . . . . . . . . . . . 245
.
M. References . . . . . . . . . . . . . . . . . . 247
.
M.1. Normative References . . . . . . . . . . . . . . 247
.
M.2. Informative References . . . . . . . . . . . . . 249
.
N. Acknowledgements . . . . . . . . . . . . . . . . 251
.

- 10 -
XHTML™ 2.0 1. Introduction

1. Introduction
This section is informative.

1.1. What is XHTML 2?

XHTML 2 is a general purpose markup language designed for representing documents for a
wide range of purposes across the World Wide Web. To this end it does not attempt to be all
things to all people, supplying every possible markup idiom, but to supply a generally useful set
of elements, with the possibility of extension using the class and role attributes on the span
and div elements in combination with style sheets, and attributes from the metadata attributes
collection.

1.1.1. Design Aims

In designing XHTML 2, a number of design aims were kept in mind to help direct the design.
These included:

As generic XML as possible: if a facility exists in XML, try to use that rather than duplicating
it.
Less presentation, more structure: use style sheets for defining presentation.
More usability: within the constraints of XML, try to make the language easy to write, and
make the resulting documents easy to use.
More accessibility: some call it ’designing for our future selves’ – the design should be as
inclusive as possible.
Better internationalization: since it is a World Wide Web.
More device independence: new devices coming online, such as telephones, PDAs, tablets,
televisions and so on mean that it is imperative to have a design that allows you to author
once and render in different ways on different devices, rather than authoring new versions
of the document for each type of device.
Less scripting: achieving functionality through scripting is difficult for the author and restricts
the type of user agent you can use to view the document. We have tried to identify current
typical usage, and include those usages in markup.
Integration with the Semantic Web: make XHTML2 amenable for processing with semantic
web tools.

1.1.2. Backwards compatibility

Because earlier versions of HTML were special-purpose languages, it was necessary to ensure
a level of backwards compatibility with new versions so that new documents would still be
usable in older browsers. However, thanks to XML and style sheets, such strict element-wise
backwards compatibility is no longer necessary, since an XML-based browser, of which at the
time of writing means more than 95% of browsers in use, can process new markup languages
without having to be updated. Much of XHTML 2 works already in existing browsers; much, but
not all: just as when forms and tables were added to HTML, and people had to wait for new

- 11 -
1.2. Major Differences with XHTML 1 XHTML™ 2.0

version of browsers before being able to use the new facilities, some parts of XHTML 2,
principally XForms and XML Events, still require user agents that understand that functionality.

1.1.3. XHTML 2 and Presentation

The very first version of HTML was designed to represent the structure of a document, not its
presentation. Even though presentation-oriented elements were later added to the language by
browser manufacturers, HTML is at heart a document structuring language. XHTML 2 takes
HTML back to these roots, by removing all presentation elements, and subordinating all
presentation to style sheets. This gives greater flexibility, greater accessibility, more device
independence, and more powerful presentation possibilities, since style sheets can do more
than the presentational elements of HTML ever did.

1.1.4. XHTML 2 and Linking

The original versions of HTML relied upon built-in knowledge on the part of User Agents and
other document processors. While much of this knowledge had to do with presentation (see
above), the bulk of the remainder had to do with the relationships between documents — so
called "linking".

A variety of W3C and other efforts, most notably [XLINK [p.249] ], attempted to create a
grammar for defining the characteristings of linking. Unfortunately, these grammars all fall short
of the requirements of XHTML. The community is continuing in its efforts to create a
comprehensive grammar that describes link characteristics.

The HTML Working Group has determined that such a grammar, while generally useful, is not
required for the definition of XHTML 2. Instead, this document is explicit in the characteristics of
the elements and attributes that are used to connect to other resources. The Working Group has
taken this course because 1) the problem with XHTML 2 is well bounded, 2) the general solution
is slow in coming, and 3) it will be easier for implementors to support and users to rely upon.

1.2. Major Differences with XHTML 1

XHTML 2 is designed to be recognizable to the HTML and XHTML 1 author, while correcting
errors and insufficiencies identified in earlier versions of the HTML family, and taking the
opportunity to make improvements.

The most visible changes are the following:

More structuring possibilities:

Sections and headings: in previous versions of HTML a document’s structure had to be
inferred from the various levels of headings in the document; this was particularly a
problem when authors misused the heading elements for visual effects. XHTML 2 lets
you explicitly markup the document structure with the section [p.47] element, and its
related header element h [p.45] .
Separators: in previous versions of HTML, the hr element was used to separate

- 12 -
XHTML™ 2.0 1.2. Major Differences with XHTML 1

sections of a text from each other. In retrospect, the name hr (for horizontal rule) was
misleading, because an hr was neither necessarily horizontal (in vertical text it was
vertical), nor necessarily a rule (books often use other typographical methods such as a
line of three asterisks to represent separators, and style sheets can be used to give you
this freedom). In order to emphasize its structuring nature, to make it more widely
usable, and to make it clearer that it has no essential directionality, hr has been
renamed separator [p.48] .
Line breaks: in previous versions of HTML, the br element was used to add
micro-structure to text, essentially breaking a piece of text into several ’lines’. This
micro-structure is now made explicit in XHTML 2 with the l [p.54] element, which
encloses the text to be broken. Amongst other advantages, this gives more
presentational opportunities, such as the ability to automatically number lines, or to
color alternate lines differently.
Paragraph structure: in earlier versions of HTML, a p [p.46] element could only contain
simple text. It has been improved to bring it closer to what people perceive as a
paragraph, now being allowed to include such things as lists and tables.
Navigation lists: Part of the design of XHTML 2 has been to observe existing use of HTML
and identify what is perceived as missing, for instance by use of scripting to achieve ends
not supported directly in HTML. One obvious component of very many HTML pages is the
’navigation list’, consisting of a collection of links to other parts of the site, presented
vertically, horizontally, or as a drop-down menu. To support this type of usage, XHTML 2
introduces the navigation list element nl [p.63] , which codifies such parts of documents,
and allows different presentational idioms to be applied. An additional advantage is for
assistive technologies, that can allow the user to skip such elements.
Images: the HTML img element has many shortcomings: it only allows you to specify a
single resource for an image, rather than offering the fallback opportunities of the object
[p.121] element; the only fallback option it gives is the alt text, which can only be plain text,
and not marked up in any way; the longdesc attribute which allows you to provide a long
description of the image is difficult to author and seldom supported.

XHTML 2 takes a completely different approach, by taking the premise that all images have
a long description and treating the image and the text as equivalents. In XHTML 2 any
element may have a src [p.88] attribute, which specifies a resource (such as an image) to
load instead of the element. If the resource is unavailable (because of network failure,
because it is of a type that the browser can’t handle, or because images have been turned
off) then the element is used instead. Essentially the longdesc has been moved into the
document, though this behavior also mimicks the fallback behavior of the object [p.121]
element. (To achieve the tooltip effect that some browsers gave with the alt attribute, as in
HTML 4 you use the title [p.69] attribute).

Type: in HTML 4, the srctype [p.88] attribute when referring to an external resource was
purely a hint to the user agent. In XHTML 2 it is no longer a hint, but specifies the type(s) of
resource the user agent must accept.
Tables: the content model of tables has been cleaned up and simplified, while still allowing
the same functionality.
Bi-directional text: rather than use an explicit element to describe bi-directional override,

- 13 -
1.2. Major Differences with XHTML 1 XHTML™ 2.0

new values have been added to the dir [p.81] attribute that allow bi-directional override on
any element.
Edit: rather than use explicit ins and del elements to mark changes in a document, an
attribute edit [p.85] may be used on any element for the same purpose.
Linking: In HTML 3, only a [p.59] elements could be the source and target of hyperlinks. In
HTML 4 and XHTML 1, any element could be the target of a hyperlink, but still only a [p.59]
elements could be the source. In XHTML 2 any element can now also be the source of a
hyperlink, since href [p.71] and its associated attributes may now appear on any element.
So for instance, instead of <li><a href="home.html">Home</a></li>, you can now
write <li href="home.html">Home</li>. Even though this means that the a [p.59]
element is now strictly-speaking unnecessary, it has been retained.
Metadata: the meta [p.103] and link [p.101] elements have been generalized, and their
relationship to RDF [RDF [p.249] ] described. Furthermore, the attributes on these two
elements can be more generally applied across the language.
Role: in order to aid adding semantics to documents, the role attribute has been added,
along with an initial set of useful values, in order to classify the use of a particular element.
For instance a paragraph may play the role of a note, and so may be marked up <p
role="note">.

Events: event handling in HTML was restricted in several ways: since the event names
were hard-wired in the language (such as onclick), the only way to add new events was
to change the language; many of the events (such as click) were device-specific, rather
than referring to the intent of the event (such as activating a link); you could only handle an
event in one scripting language — it was not possible to supply event handlers in the same
document for several different scripting languages.

XHTML 2 uses XML Events [XMLEVENTS [p.249] ] to specify event handling, giving greater
freedom in the ability to handle events. Along with this, the script element has been
renamed handler to indicate its different semantics.

Forms: HTML Forms were introduced in 1993, before the advent of the e-commerce
revolution. Now with more than a decade of experience with their use, they have been
thoroughly overhauled and updated to meet the needs of modern forms, in the shape of
XForms [XFORMS [p.248] ], which are an integral part of XHTML 2.
Ownership where due: since HTML 4 was a standalone application, it defined many things
which no longer need to be defined now that it is an XML application. For instance the
definitions of whitespace are given by XML for input, and CSS for output; similarly, the
definition of values of the media [p.137] attribute are relegated to the relevant style sheet
language.
Frames and Framesets: In HTML 4 multi-panel "pages" could be described using the
frameset and frame elements. The Frames model is no longer defined in XHTML.
Instead, if is defined through the separate [XFRAMES [p.249] ] specification.

- 14 -
XHTML™ 2.0 1.3. What are the XHTML 2 Modules?

1.3. What are the XHTML 2 Modules?

XHTML 2 is a member of the XHTML Family of markup languages. It is an XHTML Host
Language as defined in XHTML Modularization. As such, it is made up of a set of XHTML
Modules that together describe the elements and attributes of the language, and their content
model. XHTML 2 updates many of the modules defined in XHTML Modularization 1.0
[XHTMLMOD [p.248] ], and includes the updated versions of all those modules and their
semantics. XHTML 2 also uses modules from Ruby [RUBY [p.248] ], XML Events [XMLEVENTS
[p.249] ], and XForms [XFORMS [p.248] ].

The modules defined in this specification are largely extensions of the modules defined in
XHTML Modularization 1.0. This specification also defines the semantics of the modules it
includes. So, that means that unlike earlier versions of XHTML that relied upon the semantics
defined in HTML 4 [HTML4 [p.249] ], all of the semantics for XHTML 2 are defined either in this
specification or in the specifications that it normatively references.

Even though the XHTML 2 modules are defined in this specification, they are available for use in
other XHTML family markup languages. Over time, it is possible that the modules defined in this
specification will migrate into the XHTML Modularization specification.

1.4. Issues
[XHTML2] Spirit of "1.1.3. XHTML 2 and Presentation" PR #7759
State: Suspended
Resolution: None
User: None

Notes:
Suspended until last call

- 15 -
1.4. Issues XHTML™ 2.0

- 16 -
XHTML™ 2.0 2. Terms and Definitions

2. Terms and Definitions

This section is normative.

While some terms are defined in place, the following definitions are used throughout this
document. Familiarity with the W3C XML 1.0 Recommendation [XML [p.248] ] is highly
recommended.

abstract module
a unit of document type specification corresponding to a distinct type of content,
corresponding to a markup construct reflecting this distinct type.
content model
the declared markup structure allowed within instances of an element type. XML 1.0
differentiates two types: elements containing only element content (no character data) and
mixed content (elements that may contain character data optionally interspersed with child
elements). The latter are characterized by a content specification beginning with the
"#PCDATA" string (denoting character data).
deprecated
a feature marked as deprecated is in the process of being removed from this
recommendation. Portable documents should not use features marked as deprecated.
document model
the effective structure and constraints of a given document type. The document model
constitutes the abstract representation of the physical or semantic structures of a class of
documents.
document type
a class of documents sharing a common abstract structure. The ISO 8879 [SGML [p.248] ]
definition is as follows: "a class of documents having similar characteristics; for example,
journal, article, technical manual, or memo. (4.102)"
document type definition (DTD)
a formal, machine-readable expression of the XML structure and syntax rules to which a
document instance of a specific document type must conform; the schema type used in
XML 1.0 to validate conformance of a document instance to its declared document type.
The same markup model may be expressed by a variety of DTDs.
driver
a generally short file used to declare and instantiate the modules of a DTD. A good rule of
thumb is that a DTD driver contains no markup declarations that comprise any part of the
document model itself.
element
an instance of an element type.
element type
the definition of an element, that is, a container for a distinct semantic class of document
content.
entity
an entity is a logical or physical storage unit containing document content. Entities may be
composed of parseable XML markup or character data, or unparsed (i.e., non-XML,
possibly non-textual) content. Entity content may be either defined entirely within the

- 17 -
2. Terms and Definitions XHTML™ 2.0

document entity ("internal entities") or external to the document entity ("external entities"). In
parsed entities, the replacement text may include references to other entities.
entity reference
a mnemonic string used as a reference to the content of a declared entity (e.g., "&" for
"&", "<" for "<", "©" for "©".)
facilities
Facilities are elements, attributes, and the semantics associated with those elements and
attributes.
focusable
Elements are considered "focusable" if they are visible (e.g., have the equivalent of the
[CSS2 [p.247] ] property of "display" with a value other than none) not disabled (see
[XFORMS [p.248] ]), and either 1) have an href [p.71] attribute or 2) are considered a form
control as defined in [XFORMS [p.248] ].
fragment identifier
A portion of a [URI [p.248] ] as defined in RFC 3986.
generic identifier
the name identifying the element type of an element. Also, element type name.
hybrid document
A hybrid document is a document that uses more than one XML namespace. Hybrid
documents may be defined as documents that contain elements or attributes from hybrid
document types.
instantiate
to replace an entity reference with an instance of its declared content.
markup declaration
a syntactical construct within a DTD declaring an entity or defining a markup structure.
Within XML DTDs, there are four specific types: entity declaration defines the binding
between a mnemonic symbol and its replacement content; element declaration constrains
which element types may occur as descendants within an element (see also content
model); attribute definition list declaration defines the set of attributes for a given element
type, and may also establish type constraints and default values; notation declaration
defines the binding between a notation name and an external identifier referencing the
format of an unparsed entity.
markup model
the markup vocabulary (i.e., the gamut of element and attribute names, notations, etc.) and
grammar (i.e., the prescribed use of that vocabulary) as defined by a document type
definition (i.e., a schema) The markup model is the concrete representation in markup
syntax of the document model, and may be defined with varying levels of strict conformity.
The same document model may be expressed by a variety of markup models.
module
an abstract unit within a document model expressed as a DTD fragment, used to
consolidate markup declarations to increase the flexibility, modifiability, reuse and
understanding of specific logical or semantic structures.
modularization
an implementation of a modularization model; the process of composing or de-composing a
DTD by dividing its markup declarations into units or groups to support specific goals.
Modules may or may not exist as separate file entities (i.e., the physical and logical

- 18 -
XHTML™ 2.0 2. Terms and Definitions

structures of a DTD may mirror each other, but there is no such requirement).
modularization model
the abstract design of the document type definition (DTD) in support of the modularization
goals, such as reuse, extensibility, expressiveness, ease of documentation, code size,
consistency and intuitiveness of use. It is important to note that a modularization model is
only orthogonally related to the document model it describes, so that two very different
modularization models may describe the same document type.
parameter entity
an entity whose scope of use is within the document prolog (i.e., the external subset/DTD or
internal subset). Parameter entities are disallowed within the document instance.
parent document type
A parent document type of a hybrid document is the document type of the root element.
tag
descriptive markup delimiting the start and end (including its generic identifier and any
attributes) of an element.
unavailable resource
any resource that is referenced as a URI in an attribute, but that cannot be accessed for any
reason, is considered unavailable. Example reasons include, but are not limited to: network
unavailable, no resource available at the URI given, inability of the user agent to process
the type of resource, etc.
user agent
any software that retrieves and renders Strictly Conforming Documents for users. This may
include browsers, media players, plug-ins, and other programs — including assistive
technologies — that help in retrieving and rendering such documents. See also Conforming
User Agent.

- 19 -
2. Terms and Definitions XHTML™ 2.0

- 20 -
XHTML™ 2.0 3. Conformance Definition

3. Conformance Definition
This section is normative.

The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD",
"RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as
described in [RFC2119 [p.248] ].

3.1. Document Conformance

In this document, the use of the word ’schema’ refers to any definition of the syntax of XHTML 2,
regardless of the definition language used.

3.1.1. Strictly Conforming Documents

A strictly conforming XHTML 2.0 document is a document that requires only the facilities
described as mandatory in this specification. Such a document must meet all the following
criteria:

1. The document must conform to the constraints expressed in the schemas in Appendix B -
XHTML 2.0 RELAX NG Definition [p.171] , Appendix D - XHTML 2.0 Schema [p.227] and
Appendix F - XHTML 2.0 Document Type Definition [p.231] .

2. The local part of the root element of the document must be html.

3. The start tag of the root element of the document must explicitly contain an xmlns
declaration for the XHTML 2.0 namespace [XMLNS [p.249] ]. The namespace URI for
XHTML 2.0 is defined to be http://www.w3.org/2002/06/xhtml2/.

The start tag may also contain an xsi:schemaLocation [p.38] attribute that associates this
namespace with the XML Schema at the URI
http://www.w3.org/MarkUp/SCHEMA/xhtml2.xsd.

Sample root element

4. There should be a DOCTYPE declaration in the document prior to the root element. If
present, the public identifier included in the DOCTYPE declaration must reference the DTD
found in Appendix F [p.233] using its Public Identifier. The system identifier may be modified
appropriately.

- 21 -
3.2. XHTML 2 User Agent Conformance XHTML™ 2.0

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 2.0//EN"

"http://www.w3.org/MarkUp/DTD/xhtml2.dtd">

Example of an XHTML 2.0 document

<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/css"
href="http://www.w3.org/MarkUp/style/xhtml2.css"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 2.0//EN"
"http://www.w3.org/MarkUp/DTD/xhtml2.dtd">
<html xmlns="http://www.w3.org/2002/06/xhtml2/" xml:lang="en"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.w3.org/2002/06/xhtml2/
http://www.w3.org/MarkUp/SCHEMA/xhtml2.xsd"
>
<head>
<title>Virtual Library</title>
</head>
<body>
<p>Moved to <a href="http://example.org/">example.org</a>.</p>
</body>
</html>

Note that in this example, the XML declaration is included. An XML declaration like the one
above is not required in all XML documents. XHTML document authors should use XML
declarations in all their documents. XHTML document authors must use an XML declaration
when the character encoding of the document is other than the default UTF-8 or UTF-16 and no
encoding is specified by a higher-level protocol.

3.2. XHTML 2 User Agent Conformance

A conforming user agent must meet all of the following criteria, as well as other requirements
found throughout this specification:

1. The user agent must parse and evaluate an XHTML 2 document for well-formedness. If the
user agent claims to be a validating user agent, it must also validate documents against a
referenced schema according to [XML [p.248] ].

2. When the user agent claims to support facilities defined within this specification or required
by this specification through normative reference, it must do so in ways consistent with the
facilities’ definition.

3. A user agent must only recognize attributes of type ID (e.g., the id or xml:id attribute on
most XHTML 2 elements) as fragment identifiers.

4. If a user agent encounters an element it does not recognize, it must continue to process the
content of that element. If this "unrecognized" element uses recognized attributes, those
attributes must be processed with their usual semantics.

- 22 -
XHTML™ 2.0 3.3. Issues

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

6. If a user agent encounters an attribute value it doesn’t recognize, it must use the default
attribute value.

7. When rendering content, user agents that encounter characters or character entity
references that are recognized but not renderable should display the document in such a
way that it is obvious to the user that normal rendering has not taken place.

8. White space must be handled according to the rules of [XML [p.248] ]. All XHTML 2
elements preserve whitespace.

The user agent must use the definition from CSS for processing white space characters
[CSS3-TEXT [p.247] ].

9. In the absence of a style-sheet, including user agents that do not process style sheets, the
default visual presentation should be as if the user agent used the CSS style sheet
specified in Appendix H.

Note that this specification does not generally specify the behavior of conforming
implementations when presented with non-conforming documents. This is either defined by an
underlying specification (e.g., [XML [p.248] ]) or left to the implementor.

3.3. Issues
On introducing a fallback attribute PR #7723
State: Open
Resolution: None
User: None

Notes:

[XHTML 2] Conforming documents and meta properties PR #7777

State: Open
Resolution: None
User: None

Notes:

Fw: [XHTML 2] Section 3.1.1 PR #7791

State: Open
Resolution: None
User: None

Notes:

- 23 -
3.3. Issues XHTML™ 2.0

Comments on XHTML 2.0 document conformance requirements PR #7804

State: Open
Resolution: None
User: None

Notes:

Change XHTML 2.0 namespace to http://www.w3.org/1999/xhtml PR #7808

State: Open
Resolution: None
User: None

Notes:

Namespace versioning problem in XHTML 2 PR #7818

State: Open
Resolution: None
User: None

Notes:

Referance XML 1.1 and example with XML 1.1 declaration PR #7819
State: Open
Resolution: None
User: None

Notes:

- 24 -
XHTML™ 2.0 4. The XHTML 2.0 Document Type

4. The XHTML 2.0 Document Type

This section is normative.

The XHTML 2.0 document type is a fully functional document type with rich semantics. It is a
collection of XHTML-conforming modules (most of which are defined in this specification). The
Modules and their elements are listed here for information purposes, but the definitions in their
base documents should be considered authoritative. In the on-line version of this document, the
module names in the list below link into the definitions of the modules within the relevant version
of the authoritative specification.

Document Module [p.37]

body, head, html, title
Structural Module [p.41]
address, blockcode, blockquote, div, h, h1, h2, h3, h4, h5, h6, p,
pre, section, separator
Text Module [p.51]
abbr, cite, code, dfn, em, kbd, l, q, samp, span, strong, sub, sup,
var
Hypertext Module [p.59]
a
List Module [p.61]
dl, dt, dd, label, nl, ol, ul, li
Core Attributes Module [p.67]
class, id, and title attributes
Hypertext Attributes Module [p.71]
href, hreftype, cite, target, rel, rev, access, nextfocus, prevfocus, and
xml:base attributes
Internationalization Attribute Module [p.77]
xml:lang attribute
Bi-directional Text Module [p.81]
dir attribute
Edit Attributes Module [p.85]
edit and datetime attributes
Embedding Attributes Module [p.87]
src and type attributes
Handler Module [p.91]
handler
Image Map Attributes Module [p.95]
usemap, ismap, shape, and coords attributes
Media Attribute Module [p.99]
media attribute
Metainformation Attributes Module [p.101]
about, content, datatype, property, rel, resource, restype, and rev attributes

- 25 -
4.1. Issues XHTML™ 2.0

Metainformation Module [p.101]

meta, link
Object Module [p.121]
object, param, standby
Style Attribute Module [p.135]
style attribute
Stylesheet Module [p.137]
style element
Tables Module [p.141]
caption, col, colgroup, summary, table, tbody, td, tfoot, th,
thead, tr

XHTML 2.0 also uses the following externally defined modules:

Ruby Annotation Module [RUBY [p.248] ]

ruby, rbc, rtc, rb, rt, rp
XForms Module [p.163] [XFORMS [p.248] ]
action, alert, bind, case, choices, copy, delete, dispatch,
extension, filename, group, help, hint, input, insert, instance,
item, itemset, label, load, mediatype, message, model, output,
range, rebuild, recalculate, refresh, repeat, reset, revalidate,
secret, select, select1, send, setfocus, setindex, setvalue,
submission, submit, switch, textarea, toggle, trigger, upload, and
value elements, and repeat-model, repeat-bind, repeat-nodeset,
repeat-startindex, and repeat-number attributes
XML Events Module [p.167] [XMLEVENTS [p.249] ]
listener element, and defaultAction, event, handler, objserver, phase,
propagate, and target attributes in the [XMLEVENTS [p.249] ] namespace

An implementation of this document type as a RELAX NG grammar is defined in Appendix B

[p.171] , as an XML Schema in Appendix D [p.227] , and as a DTD in Appendix F [p.231] .

4.1. Issues
Identifying XHTML version in ansence of DTDs PR #7336
State: Suspended
Resolution: Defer
User: None

Notes:
BAE F2F: for the present DTD’s are required for entity resolution. This is a tricky issue, and the
working group needs to resolve it quickly. We are asking for input from the Hypertext
Coordination Group and others in our quest to sort it out.

- 26 -
XHTML™ 2.0 5. Module Definition Conventions

5. Module Definition Conventions

This section is normative.

This document defines a variety of XHTML modules and the semantics of those modules. This
section describes the conventions used in those module definitions.

5.1. Module Structure

Each module in this document is structured in the following way:

An abstract definition [p.27] of the module’s elements, attributes, and content models, as
appropriate.
A sub-section for each element in the module; These sub-sections contain the following
components:
A brief description of the element,
A definition of each attribute or attribute collection [p.33] usable with the element, and
A detailed description of the behavior of the element, if appropriate.

Note that attributes are fully defined only the first time they are used in each module. After
that, only a brief description of the attribute is provided, along with a link back to the primary
definition.

5.2. Abstract Module Definitions

An abstract module is a definition of an XHTML module using prose text and some informal
markup conventions. While such a definition is not generally useful in the machine processing of
document types, it is critical in helping people understand what is contained in a module. This
section defines the way in which XHTML abstract modules are defined. An XHTML-conforming
module is not required to provide an abstract module definition. However, anyone developing an
XHTML module is encouraged to provide an abstraction to ease in the use of that module.

5.3. Syntactic Conventions

The abstract modules are not defined in a formal grammar. However, the definitions do adhere
to the following syntactic conventions. These conventions are similar to those of XML DTDs, and
should be familiar to XML DTD authors. Each discrete syntactic element can be combined with
others to make more complex expressions that conform to the algebra defined here.

element name
When an element is included in a content model, its explicit name will be listed.
content set
Some modules define lists of explicit element names called content sets. When a content
set is included in a content model, its name will be listed.

- 27 -
5.4. Content Models XHTML™ 2.0

expr ?
Zero or one instances of expr are permitted.
expr +
One or more instances of expr are required.
expr *
Zero or more instances of expr are permitted.
a , b
Expression a is required, followed by expression b.
a | b
Either expression a or expression b is required.
a - b
Expression a is permitted, omitting elements in expression b.
parentheses
When an expression is contained within parentheses, evaluation of any subexpressions
within the parentheses take place before evaluation of expressions outside of the
parentheses (starting at the deepest level of nesting first).
extending pre-defined elements
In some instances, a module adds attributes to an element. In these instances, the element
name is followed by an ampersand (&).
defining required attributes
When an element requires the definition of an attribute, that attribute name is followed by an
asterisk (*).
defining the type of attribute values
When a module defines the type of an attribute value, it does so by listing the type in
parentheses after the attribute name.
defining the legal values of attributes
When a module defines the legal values for an attribute, it does so by listing the explicit
legal values (enclosed in quotation marks), separated by vertical bars (|), inside of
parentheses following the attribute name. If the attribute has a default value, that value is
followed by an asterisk (*). If the attribute has a fixed value, the attribute name is followed
by an equals sign (=) and the fixed value enclosed in quotation marks.

5.4. Content Models

Abstract module definitions define minimal, atomic content models for each module. These
minimal content models reference the elements in the module itself. They may also reference
elements in other modules upon which the abstract module depends. Finally, the content model
in many cases requires that text be permitted as content to one or more elements. In these
cases, the symbol used for text is PCDATA (parsed characted data). This is a term, defined in
the XML 1.0 Recommendation, that refers to processed character data. A content type can also
be defined as EMPTY, meaning the element has no content in its minimal content model.

- 28 -
XHTML™ 2.0 5.5. Attribute Types

5.5. Attribute Types

In some instances, it is necessary to define the types of attribute values or the explicit set of
permitted values for attributes. The following attribute types (defined in the XML 1.0
Recommendation) are used in the definitions of the abstract modules:

Attribute Type Definition

CDATA Character data
ID A document-unique identifier
IDREF A reference to a document-unique identifier
IDREFS A space-separated list of references to document-unique identifiers
NMTOKEN A name composed of only name tokens as defined in XML 1.0 [XML [p.248] ].
NMTOKENS One or more white space separated NMTOKEN values
NUMBER Sequence of one or more digits ([0-9])

In addition to these pre-defined data types, XHTML Modularization defines the following data
types and their semantics (as appropriate):

Data type Description

Character A single character, as per section 2.2 of [XML [p.248] ].
A comma-separated list of ’charset’s with optional q parameters, as defined
Encodings in section 14.2 of [RFC2616 [p.248] ] as the field value of the
Accept-Charset request header.
ContentType A media type, as per [RFC2045 [p.248] ].

- 29 -
5.5. Attribute Types XHTML™ 2.0

Attributes of this type identify the allowable content type(s) of an associated

URI [p.31] (usually a value of another attribute on the same element). At its
most general, it is a comma-separated list of media ranges with optional
accept parameters, as defined in section 14.1 of [RFC2616 [p.248] ] as the
field value of the accept request header.

In its simplest case, this is just a media type, such as "image/png" or

"application/xml", but it may also contain asterisks, such as "image/*" or "*/*",
or lists of acceptable media types, such as "image/png, image/gif,
image/jpeg".

The user agent must combine this list with its own list of acceptable media
types by taking the intersection, and then use the resulting list as the field
value of the accept request header when requesting the resource using
ContentTypes HTTP.

For instance, if the attribute specifies the value "image/png, image/gif,

image/jpeg", but the user agent does not accept images of type "image/gif"
then the resultant accept header would contain "image/png, image/jpeg".

A user agent must imitate similar behavior when using other methods than
HTTP. For instance, when accessing files in a local filestore, <p
src="logo" srctype="image/png, image/jpeg"> might cause the
user agent first to look for a file logo.png, and then for logo.jpg.

If a value for the content type is not given, "*/*" must be used for its value.

For the current list of registered content types, please consult [MIMETYPES
[p.247] ].
Coordinates Comma separated list of Length [p.30] s used in defining areas.
Date and time information, as defined by the type dateTime in
Datetime
[XMLSCHEMA [p.249] ] except that the timezone part is required.
Name used as destination for results of certain actions, with legal values as
HrefTarget
defined by NMTOKEN [p.29] .
A language code. The values should conform to [RFC3066 [p.248] ] or its
LanguageCode
successors.
A comma-separated list of language ranges with optional q parameters, as
defined in section 14.4 of [RFC2616 [p.248] ] as the field value of the
LanguageCodes
Accept-Language request header. Individual language codes should
conform to [RFC3066 [p.248] ] or its successors.
Either a number, representing a number of pixels, or a percentage,
Length representing a percentage of the available horizontal or vertical space. Thus,
the value "50%" means half of the available space.

- 30 -
XHTML™ 2.0 5.6. Issues

LocationPath A location path as defined in [XPATH [p.250] ].

A comma-separated list of media descriptors as described by [CSS2 [p.247]
MediaDesc
]. The default is all.
Number One or more digits
QName An [XMLNS [p.249] ]-qualified name. See QName for a formal definition.
QNames One or more white space separated QName [p.31] values
Text A character string.
An Internationalized Resource Identifier Reference, as defined by [IRI
URI
[p.247] ].
URIs A space-separated list of URIs as defined above.

5.6. Issues
Fw: [XHTML 2] Section 5.5 quality values. PR #7799
State: Open
Resolution: None
User: None

Notes:

Fw: [XHTML 2] Section 5.5 intersection of mime-types PR #7800

State: Open
Resolution: None
User: None

Notes:

- 31 -
5.6. Issues XHTML™ 2.0

- 32 -
XHTML™ 2.0 6. XHTML Attribute Collections

6. XHTML Attribute Collections

This section is normative.

Many of the modules in this document define the required attributes for their elements. The
elements in those modules may also reference zero or more attribute collections. Attribute
collections are defined in their own modules, but the meta collection "Common" is defined in this
section. The table below summarizes the attribute collections available.

- 33 -
6. XHTML Attribute Collections XHTML™ 2.0

Collection Module Description

Core Attributes Basic attributes used to identify and classify
Core [p.67]
Module [p.67] elements and their content.
Internationalization
Attribute to identify the language of an element and
I18N [p.77] Attribute Module
its contents.
[p.77]
Bi-directional Bi-directional Text
Attributes used to manage bi-directional text.
[p.81] Collection [p.81]
Edit Attributes Attributes used to annotate when and how an
Edit [p.85]
Module [p.85] element’s content was edited.
Embedding Embedding Attributes Attributes used to embed content from other
[p.87] Module [p.87] resources within the current element.
XML Events Module Attributes that allow associating of events and event
Events [p.167]
[p.167] processing with an element and its contents.
XForms Module Attributes that designate provide a mechanism of
Forms [p.164]
[p.163] repeating table rows within a form.
Hyptertext Attributes Attributes that designate characteristics of links
Hypertext [p.71]
Module [p.71] within and among documents.
Image Map Attributes Attributes for defining and referencing client-side
Map [p.96]
Module [p.95] image maps.
Media Attribute Attribute for performing element selection based
Media [p.99]
Module [p.99] upon media type as defined in MediaDesc [p.31]
Metainformation Metainformation Attributes that allow associating of elements with
[p.113] Attributes [p.113] metainformation about those elements
Role Attribute Module Attribute for the specification of the "role" of an
Role [p.131]
[p.131] element.
Style Attribute Attribute for associating style information with an
Style [p.135]
Module [p.135] element and its contents.
A meta-collection of all the other collections,
including the Core [p.67] , Bi-directional [p.81] ,
Attribute Collections Events [p.167] , Edit [p.85] , Embedding [p.87] ,
Common
Module [p.33] Forms [p.164] , Hypertext [p.71] , I18N [p.77] , Map
[p.96] , Media [p.99] , Metainformation [p.113] , Role
[p.131] , and Style [p.135] attribute collections.

- 34 -
XHTML™ 2.0 6.1. Issues

Implementation: RELAX NG [p.175]

Each of the attributes defined in an XHTML attribute collection is available when its
corresponding module is included in an XHTML Host Language or an XHTML Integration Set
(see [XHTMLMOD [p.248] ]). In such a situation, the attributes are available for use on elements
that are NOT in the XHTML namespace when they are referenced using their
namespace-qualified identifier (e.g., xhtml:id). The semantics of the attributes remain the
same regardless of whether they are referenced using their qualified identifier or not. If both the
qualified and non-qualified identifier for an attribute are used on the same XHTML namespace
element, the behavior is unspecified.

6.1. Issues
[XHTML2] Constraining attribute relationship PR #7661
State: Suspended
Resolution: Defer
User: None

Notes:

- 35 -
6.1. Issues XHTML™ 2.0

- 36 -
XHTML™ 2.0 7. XHTML Document Module

7. XHTML Document Module

This section is normative.

The Document Module defines the major structural elements for XHTML. These elements
effectively act as the basis for the content model of many XHTML family document types. The
elements and attributes included in this module are:

Elements Attributes Content Model

Common [p.34] , version [p.38] (CDATA [p.29] ), xmlns (URI
[p.31] = "http://www.w3.org/2002/06/xhtml2/"),
html head [p.38] , body
xsi:schemaLocation [p.38] (URIs [p.31] =
[p.38] [p.39]
"http://www.w3.org/2002/06/xhtml2/
http://www.w3.org/MarkUp/SCHEMA/xhtml2.xsd")
title [p.39] , (
access [p.79] |
handler [p.91] |
head link [p.101] |
Common [p.34]
[p.38] ev:listener [p.167]
| model [p.163] |
meta [p.103] |
style [p.137] ) *

title [p.39] Common [p.34] PCDATA*

( Heading [p.43] |
body
Common [p.34] Structural [p.43] |
[p.39]
List [p.61] )*

This module is the basic structural definition for XHTML content. The html element acts as the
root element for all XHTML Family Document Types.

Note that the value of the xmlns declaration is defined to be

"http://www.w3.org/2002/06/xhtml2/". Also note that because the xmlns declaration is treated
specially by XML namespace-aware parsers [XMLNS [p.249] ], it is legal to have it present as an
attribute of each element. However, any time the xmlns declaration is used in the context of an
XHTML module, whether with a prefix or not, the value of the declaration must be
http://www.w3.org/2002/06/xhtml2/.

Implementation: RELAX NG [p.176]

- 37 -
7.1. The html element XHTML™ 2.0

7.1. The html element

The html [p.38] element is the root element for all XHTML Family Document Types. The
xml:lang [p.77] attribute is required on this element.

Attributes

The Common [p.34] collection

A collection of other attribute collections, including: Bi-directional [p.81] , Core [p.67] , Edit
[p.85] , Embedding [p.87] , Events [p.167] , Forms [p.164] , Hypertext [p.71] , I18N [p.77] ,
Map [p.96] , and Metainformation [p.113] .

version = CDATA [p.29]

The value of this attribute specifies which XHTML Family document type governs the
current document. The format of this attribute value is unspecified. However, all values
beginning with the character sequence xhtml are reserved for use by XHTML Family
Document Types.

Need a normative definition for the version attribute

The version attribute needs a machine processable format so that document processors
can reliably determine that the document is an XHTML Family conforming document.

xsi:schemaLocation = URIs [p.31]

This attribute allows the specification of a location where an XML Schema [XMLSCHEMA
[p.249] ] for the document can be found. The syntax of this attribute is defined in
xsi_schemaLocation. The behavior of this attribute in XHTML documents is defined in
Strictly Conforming Documents.

7.2. The head element

The head [p.38] element contains information about the current document, such as its title, that
is not considered document content. The default presentation of the head is not to display it;
however that can be overridden with a style sheet for special purpose use. User agents may
however make information in the head [p.38] available to users through other mechanisms.

Attributes

The Common [p.34] collection

Example

- 38 -
XHTML™ 2.0 7.3. The title element

7.3. The title element

Every XHTML document must have a title [p.39] element in the head [p.38] section.

Attributes

The Common [p.34] collection

The title [p.39] element is used to identify the document. Since documents are often consulted
out of context, authors should provide context-rich titles. Thus, instead of a title such as
"Introduction", which doesn’t provide much contextual background, authors should supply a title
such as "Introduction to Medieval Bee-Keeping" instead.

For reasons of accessibility, user agents must always make the content of the title [p.39]
element available to users. The mechanism for doing so depends on the user agent (e.g., as a
caption, spoken).

Example
<title>A study of population dynamics</title>

The title of a document is metadata about the document, and so a title like <title>About
W3C</title> is equivalent to <meta about="" property="title">About
W3C</meta>.

7.4. The body element

The body of a document contains the document’s content. The content may be processed by a
user agent in a variety of ways. For example by visual browsers it can be presented as text,
images, colors, graphics, etc., an audio user agent may speak the same content, and a search
engine may create an index prioritized according to properties of the text.

Attributes

The Common [p.34] collection

- 39 -
7.4. The body element XHTML™ 2.0

Example
<body id="theBody">
<p>A paragraph</p>
</body>

- 40 -
XHTML™ 2.0 8. XHTML Structural Module

8. XHTML Structural Module

This section is normative.

This module defines all of the basic text container elements, attributes, and their content models
that are structural in nature.

- 41 -
8. XHTML Structural Module XHTML™ 2.0

Element Attributes Content Model

Common
address [p.43] [p.34] (PCDATA | Text [p.51] )*

The content model for this module defines some content sets:

- 42 -
XHTML™ 2.0 8.1. The address element

Implementation: RELAX NG [p.178]

8.1. The address element

The address [p.43] element may be used by authors to supply contact information for a
document or a major part of a document such as a form.

Attributes

The Common [p.34] collection

Example
<address href="mailto:[email protected]">Webmaster</address>

8.2. The blockcode element

This element indicates that its contents are a block of "code" (see the code [p.53] element). This
element is similar to the pre [p.47] element, in that whitespace in the enclosed text has semantic
relevance. As a result, the default value of the layout [p.68] attribute is relevant.

Attributes

The Common [p.34] collection

Example of a code fragment:

<blockcode class="Perl">
sub squareFn {
my $var = shift;

return $var * $var ;

}
</blockcode>

- 43 -
8.3. The blockquote element XHTML™ 2.0

Here is how this might be rendered:

sub squareFn {
my $var = shift;

return $var * $var ;

}

8.3. The blockquote element

This element designates a block of quoted text.

Attributes

The Common [p.34] collection

An excerpt from ’The Two Towers’, by J.R.R. Tolkien, as a blockquote

<blockquote cite="http://www.example.com/tolkien/twotowers.html">
<p>They went in single file, running like hounds on a strong scent,
and an eager light was in their eyes. Nearly due west the broad
swath of the marching Orcs tramped its ugly slot; the sweet grass
of Rohan had been bruised and blackened as they passed.</p>
</blockquote>

8.4. The div element

The div [p.44] element, in conjunction with the id [p.67] , class [p.67] and role [p.131] attributes,
offers a generic mechanism for adding extra structure to documents. This element defines no
presentational idioms on the content. Thus, authors may use this element in conjunction with
style sheets [p.137] , the xml:lang [p.77] attribute, etc., to tailor XHTML to their own needs and
tastes.

Attributes

The Common [p.34] collection

For example, suppose you wish to make a presentation in XHTML, where each slide is enclosed
in a separate element. You could use a div [p.44] element, with a class [p.67] of slide:

div with a class of slide

- 44 -
XHTML™ 2.0 8.5. The heading elements

<body>
<h>The meaning of life</h>
<p>By Huntington B. Snark</p>
<div class="slide">
<h>What do I mean by "life"</h>
<p>....</p>
</div>
<div class="slide">
<h>What do I mean by "mean"?</h>
...
</div>
...
</body>

8.5. The heading elements

A heading element briefly describes the topic of the section it introduces. Heading information
may be used by user agents, for example, to construct a table of contents for a document
automatically.

Attributes

The Common [p.34] collection

There are two styles of headings in XHTML: the numbered versions h1 [p.45] , h2 [p.45] etc.,
and the structured version h [p.45] , which is used in combination with the section [p.47]
element.

There are six levels of numbered headings in XHTML with h1 [p.45] as the most important and
h6 [p.45] as the least.

Structured headings use the single h element, in combination with the section [p.47] element to
indicate the structure of the document, and the nesting of the sections indicates the importance
of the heading. The heading for the section is the one that is a child of the section element.

Example
<body>
<h>This is a top level heading</h>
<p>....</p>
<section>
<p>....</p>
<h>This is a second-level heading</h>
<p>....</p>
<h>This is another second-level heading</h>
<p>....</p>
</section>
<section>
<p>....</p>

- 45 -
8.6. The p element XHTML™ 2.0

<h>This is another second-level heading</h>

<p>....</p>
<section>
<h>This is a third-level heading</h>
<p>....</p>
</section>
</section>
</body>

Sample style sheet for section levels

h {font-family: sans-serif; font-weight: bold; font-size: 200%}
section h {font-size: 150%} /* A second-level heading */
section section h {font-size: 120%} /* A third-level heading */

Numbered sections and references

XHTML does not itself cause section numbers to be generated from headings. Style sheet
languages such as CSS however allow authors to control the generation of section numbers.

The practice of skipping heading levels is considered to be bad practice. The series h1 h2 h1
is acceptable, while h1 h3 h1 is not, since the heading level h2 has been skipped.

8.6. The p element

The p [p.46] element represents a paragraph.

In comparison with earlier versions of HTML, where a paragraph could only contain inline text,
XHTML2’s paragraphs represent the conceptual idea of a paragraph, and so may contain lists,
blockquotes, pre’s and tables as well as inline text. Note however that they may not contain
directly nested p [p.46] elements.

Attributes

The Common [p.34] collection

Example
<p>Payment options include:
<ul>
<li>cash</li>
<li>credit card</li>
<li>luncheon vouchers.</li>
</ul>
</p>

- 46 -
XHTML™ 2.0 8.7. The pre element

8.7. The pre element

The pre [p.47] element indicates that whitespace in the enclosed text has semantic relevance.
As such, the default value of the layout [p.68] attribute is relevant.

Note that all elements in the XHTML family preserve their whitespace in the document, which is
only removed on rendering, via a style sheet, according to the rules of CSS [CSS3-TEXT [p.247]
]. This means that in principle any elements may preserve or collapse whitespace on rendering,
under control of a style sheet.

Attributes

The Common [p.34] collection

A bad poem where whitespace matters

<pre>
If
I had
any talent
I would
be a

poet
</pre>

Here is how this might be rendered:

If
I had
any talent
I would
be a

poet

Note that while historically one use of the pre [p.47] element has been as a container for source
code, the blockcode [p.43] element is intended for that.

8.8. The section element

The section [p.47] element, in conjunction with the h [p.45] element, offers a mechanism for
structuring documents into sections. This element defines content to be block-level but imposes
no other presentational idioms on the content, which may otherwise be controlled from a style
sheet.

- 47 -
8.9. The separator element XHTML™ 2.0

Attributes

The Common [p.34] collection

By representing the structure of documents explicitly using the section [p.47] and h [p.45]
elements gives the author greater control over presentation possibilities than the traditional
implicit structuring using numbered levels of headings. For instance, it is then possible to
indicate the nesting of sections by causing a border to be displayed to the left of sections.

Example
<body>
<h>Events</h>
<section>
<h>Introduction</h>
<p>....</p>
<h>Specifying events</h>
<p>...</p>
<section>
<h>Attaching events to the handler</h>
<p>...</p>
</section>
<section>
<h>Attaching events to the listener</h>
<p>...</p>
</section>
<section>
<h>Specifying the binding elsewhere</h>
<p>...</p>
</section>
</section>
</body>

8.9. The separator element

The separator [p.48] element separates parts of the document from each other.

Attributes

The Common [p.34] collection

Example

- 48 -
XHTML™ 2.0 8.10. Issues

<p>This is some lead in text</p>

<separator />
<p>This is some additional, but separate text.</p>

Example
<nl>
<lable>Navigation</label>
<li href="/">Home</li>
<li><separator/></li>
<li href="prev">Previous</li>
<li href="..">Up</li>
<li href="next">Next</li>
</nl>

8.10. Issues
[XHTML2] How are UAs to interpret <h> and <hx> elements? PR #7820
State: Open
Resolution: None
User: None

Notes:

[XHTML2] How are UAs to interpret <h> and <hx> elements? PR #7830
State: Open
Resolution: None
User: None

Notes:

block@kind vs elt@structure PR #7874

State: Open
Resolution: None
User: None

Notes:

redundant content model PR #7875

State: Open
Resolution: None
User: None

Notes:
Agreed - should change these to be Flow.

headings -- numbered vs bare PR #7877

State: Open
Resolution: None
User: None

- 49 -
8.10. Issues XHTML™ 2.0

Notes:
You are correct - there is nothing but good taste to prevent people doing silly things. However,
we need better wording to clarify that the content model does indeed support bad taste.

- 50 -
XHTML™ 2.0 9. XHTML Text Module

9. XHTML Text Module

This section is normative.

This module defines all of the basic text container elements, attributes, and their content models
that are "inline level". Note that while the concept of "inline level" can be construed as a
presentation aspect, in this case it is intended to only have a semantic meaning.

Element Attributes Content Model

The content model for this module defines a content set:

Implementation: RELAX NG [p.184]

- 51 -
9.1. The abbr element XHTML™ 2.0

9.1. The abbr element

The abbr [p.52] element indicates that a text fragment is an abbreviation (e.g., W3C, XML, Inc.,
Ltd., Mass., etc.); this includes acronyms.

Attributes

The Common [p.34] collection

full = IDREF [p.29]

This attribute locates an element that defines the full expansion of an abbreviation. The
referenced element must be in the same document as the abbreviation.

The content of the abbr [p.52] element specifies the abbreviated expression itself, as it would
normally appear in running text. The title [p.69] or full [p.52] attributes may be used to provide
the full or expanded form of the expression. Such an attribute should be repeated each time the
abbreviation is defined in the document.

Examples
<abbr title="Limited">Ltd.</abbr>
<abbr title="Abbreviation">abbr.</abbr>
<p>The <span id="w3c">World Wide Web Consortium</span> (<abbr full="#w3c">W3C</abbr>)
develops interoperable technologies (specifications, guidelines, software, and tools)
to lead the Web to its full potential. <abbr full="#w3c">W3C</abbr> is a forum for
information, commerce, communication, and collective understanding.</p>

9.2. The cite element

The cite [p.52] element contains a citation or a reference to other sources.

Attributes

The Common [p.34] collection

In the following example, the cite [p.52] element is used to reference the book from which the
quotation is taken:

cite as book reference

As Gandalf the White said in
<cite cite="http://www.example.com/books/the_two_towers">The Two Towers</cite>,
<quote xml:lang="en">"The hospitality of
your hall is somewhat lessened of late, Theoden King."</quote>

- 52 -
XHTML™ 2.0 9.3. The code element

cite to reference another specification

More information can be found in
<cite cite="http://www.w3.org/TR/REC-xml">[XML]</cite>.

9.3. The code element

The code [p.53] element contains a fragment of computer code.

Attributes

The Common [p.34] collection

Example
The Pascal statement <code>i := 1;</code> assigns the
literal value one to the variable <var>i</var>.

9.4. The dfn element

The dfn [p.53] element contains the defining instance of the enclosed term.

Attributes

The Common [p.34] collection

Example
<p role="definition">
An <dfn id="def-acronym">acronym</dfn> is a word
formed from the initial letters or groups of letters of words in a
set phrase or series of words.
</p>

9.5. The em element

The em [p.53] element indicates emphasis for its contents.

Attributes

- 53 -
9.6. The kbd element XHTML™ 2.0

The Common [p.34] collection

Example
Do <em>not</em> phone before 9 a.m.

9.6. The kbd element

The kbd [p.54] element indicates input to be entered by the user.

Attributes

The Common [p.34] collection

Example
To exit, type <kbd>QUIT</kbd>.

9.7. The l element

The l [p.54] element represents a semantic line of text (e.g., a line of verse or a line of computer
code).

Attributes

The Common [p.34] collection

By retaining structure in text that has to be broken over lines, you retain essential information
about its makeup. This gives you greater freedom with styling the content. For instance, line
numbers can be generated automatically from the style sheet if needed.

Sample program listing

<blockcode class="program">
<l>program p(input, output);</l>
<l>begin</l>
<l> writeln("Hello world");</l>
<l>end.</l>
</blockcode>

- 54 -
XHTML™ 2.0 9.8. The q element

CSS Style sheet to number each line

.program { counter-reset: linenumber }

l:before {
position: relative;
left: -1em;
counter-increment: linenumber;
content: counter(linenumber);
}

9.8. The q element

This element designates an inline text fragment of quoted text.

Attributes

The Common [p.34] collection

Visual user agents must not by default add delimiting quotation marks (as was the case for the q
element in earlier versions of XHTML and HTML). It is the responsibility of the document author
to add any required quotation marks, either directly in the text, or via a style sheet.

Nested quotations using q

<p>John said, <q>"I saw Lucy at lunch, she told me
<q>’Mary wants you
to get some ice cream on your way home.’</q> I think I will get
some at Jen and Berry’s, on Gloucester Road."</q></p>

q with a cite attribute

Steven replied:
<q cite="http://lists.example.org/2002/01.html">We quite agree</q>

9.9. The samp element

The samp [p.55] element designates sample output from programs, scripts, etc.

Attributes

The Common [p.34] collection

- 55 -
9.10. The span element XHTML™ 2.0

Example
On starting, you will see the prompt <samp>$ </samp>.

9.10. The span element

The span [p.56] element, in conjunction with the id [p.67] , class [p.67] and role [p.131]
attributes, offers a generic mechanism for adding structure to documents. This element imposes
no presentational idioms on the content. Thus, authors may use this element in conjunction with
style sheets [p.137] , the xml:lang [p.77] attribute, the dir [p.81] attribute etc., to tailor XHTML to
their own needs and tastes.

Attributes

The Common [p.34] collection

Example of span for cross references

<p>This operation is called
the <span class="xref">transpose</span>
or <span class="xref">inverse</span>.</p>

9.11. The strong element

The strong [p.56] element indicates higher importance for its contents than that of the
surrounding content.

Attributes

The Common [p.34] collection

Example
On <strong>Monday</strong> please put the rubbish out,
but <em>not</em> before nightfall!

9.12. The sub element

The sub [p.56] element indicates that its contents should regarded as a subscript.

- 56 -
XHTML™ 2.0 9.13. The sup element

Attributes

The Common [p.34] collection

Example
H<sub >2</sub>O

9.13. The sup element

The sup [p.57] element indicates that its contents should be regarded as a super-script.

Attributes

The Common [p.34] collection

Many scripts (e.g., French) require superscripts or subscripts for proper rendering. The sub
[p.56] and sup [p.57] elements should be used to markup text in these cases.

Example
E = mc<sup>2</sup>
<span xml:lang="fr">M<sup>lle</sup> Dupont</span>

9.14. The var element

The var [p.57] element indicates an instance of a variable or program argument.

Attributes

The Common [p.34] collection

Example
The parameter <var>ncols</var> represents
the number of colors to use.

- 57 -
9.15. Issues XHTML™ 2.0

9.15. Issues
PCData not in Text PR #7876
State: Open
Resolution: None
User: None

Notes:
The group agrees that we should change the abstract module definitions such that PCDATA is
just included in Text.

XHTML 2.0: Text Module/<l> vs. <br /> element PR #7882

State: Open
Resolution: None
User: None

Notes:
The working group cannot come up with an example. Requesting one from the submitter.

RE: [ off list ] XHTML 2.0 - dfn : Content model and usability PR #7885
State: Open
Resolution: None
User: None

Notes:

- 58 -
XHTML™ 2.0 10. XHTML Hypertext Module

10. XHTML Hypertext Module

This section is normative.

The Hypertext Module provides an element that traditionally has been used in HTML to define
hypertext links to other resources. Although all elements may now play the role of a hyperlink
(using the href [p.71] attribute) or hyperlink anchor (using the id [p.67] attribute), this element
remains for explicit markup of links, though is otherwise identical in semantics to the span [p.56]
element.

This module supports the following element:

Element Attributes Content Model

a [p.59] Common [p.34] (PCDATA | Text [p.51] )*

Implementation: RELAX NG [p.188]

10.1. The a element

An a [p.59] element defines an anchor. Since hypertext attributes such as href [p.71] may be
applied to any element, this element is not strictly necessary, being equivalent to a span [p.56] ,
but has been retained to allow the expression of explicit links.

Attributes

The Common [p.34] collection

Example
<a href="http://www.w3.org/">The W3C Home Page</a>

- 59 -
10.1. The a element XHTML™ 2.0

- 60 -
XHTML™ 2.0 11. XHTML List Module

11. XHTML List Module

This section is normative.

As its name suggests, the List Module provides list-oriented elements. Specifically, the List
Module supports the following elements and attributes:

Elements Attributes Content Model

dl [p.62] Common [p.34] label [p.65] ?, (( dt [p.62] | dd [p.62] )+ | di [p.62] +)
di [p.62] Common [p.34] ( dt [p.62] +, dd [p.62] *)
dt [p.62] Common [p.34] (PCDATA | Text [p.51] )*
dd [p.62] Common [p.34] (PCDATA | Flow [p.43] )*

label [p.65] Common [p.34] (PCDATA | Text [p.51] )*

nl [p.63] Common [p.34] label [p.65] , li [p.64] +
ol [p.64] Common [p.34] label [p.65] ?, li [p.64] +
ul [p.64] Common [p.34] label [p.65] ?, li [p.64] +
li [p.64] Common [p.34] , value [p.65] (PCDATA | Flow [p.43] )*

This module also defines the content set List with the content model (dl | nl | ol | ul)+ and adds
this set to the Flow [p.43] content set of the Structural [p.41] Module.

Implementation: RELAX NG [p.189]

XHTML offers authors several mechanisms for specifying lists of information. Lists may contain:

Unordered information.
Ordered information.
Navigation information.
Definitions.

The previous list, for example, is an unordered list, created with the ul [p.64] element:

Example
<ul>
<li>Unordered information. </li>
<li>Ordered information. </li>
<li>Navigation information. </li>
<li>Definitions. </li>
</ul>

- 61 -
11.1. Definition lists: the dl , di , dt , and dd elements XHTML™ 2.0

An ordered list, created using the ol [p.64] element, contains information where order is
important, as in a recipe:

1. Mix dry ingredients thoroughly.

2. Pour in wet ingredients.
3. Mix for 10 minutes.
4. Bake for one hour at 300 degrees.

Definition lists, created using the dl [p.62] element, generally consist of a series of term/definition
pairs (although definition lists may have other applications). Thus, when advertising a product,
one might use a definition list:

Lower cost
The new version of this product costs significantly less than the previous one!
Easier to use
We’ve changed the product so that it’s much easier to use!
Safe for kids
You can leave your kids alone in a room with this product and they won’t get hurt (not a
guarantee).

defined in XHTML as:

Example
<dl>
<dt>Lower cost</dt>
<dd>The new version of this product costs significantly less than the
previous one!</dd>
<dt>Easier to use</dt>
<dd>We’ve changed the product so that it’s much easier to
use!</dd>
<dt>Safe for kids</dt>
<dd>You can leave your kids alone in a room with this product and
they won’t get hurt (not a guarantee).</dd>
</dl>

11.1. Definition lists: the dl , di , dt , and dd elements

Attributes

The Common [p.34] collection

Definition lists vary only slightly from other types of lists in that list items consist of two parts: a
term and a description. The term is given by the dt [p.62] element. The description is given with
a dd [p.62] element. The term and its definition can be grouped within a di [p.62] element to help
clarify the relationship between a term and its definition(s).

- 62 -
XHTML™ 2.0 11.2. The nl element

Example
<dl>
<di>
<dt>Dweeb</dt>
<dd>young excitable person who may mature
into a <em>Nerd</em> or <em>Geek</em></dd>
</di>

<di>
<dt>Hacker</dt>
<dd>a clever programmer</dd>
</di>

<di>
<dt>Nerd</dt>
<dd>technically bright but socially inept person</dd>
</di>

</dl>

Here is an example with multiple terms and descriptions:

Example
<dl>
<dt>Center</dt>
<dt>Centre</dt>
<dd> A point equidistant from all points
on the surface of a sphere.</dd>
<dd> In some field sports, the player who
holds the middle position on the field, court,
or forward line.</dd>
</dl>

11.2. The nl element

Attributes

The Common [p.34] collection

Navigation lists are intended to be used to define lists of selectable items for ordered
presentation. These may be presented in a number of ways, for instance as a navigation bar, or
as a menu. Note that a navigation list always starts with a label [p.65] element that defines the
label for the list.

Basic navigation list structure

- 63 -
11.3. The ol and ul elements XHTML™ 2.0

<nl>
<label>Contents </label>
<li href="#introduction">Introduction</li>
<li>
<nl>
<label>Terms</label>
<li href="#may">May</li>
<li href="#must">Must</li>
<li href="#should">Should</li>
</nl>
</li>
<li href="#conformance">Conformance</li>
<li href="#references">References</li>
...
</nl>

11.3. The ol and ul elements

Attributes

The Common [p.34] collection

Both types of lists are made up of sequences of list items defined by the li [p.64] element. The
difference is that ol [p.64] lists represent lists of items that are essentially ordered (such as the
steps of a recipe), while ul [p.64] lists represent lists of items that are essentially unordered
(such as shopping lists).

Basic list structure

<ol>
<li>Spring</li>
<li>Summer</li>
<li>Autumn</li>
<li>Winter</li>
</ol>

11.4. The li element

Attributes

The Common [p.34] collection

- 64 -
XHTML™ 2.0 11.5. The label element

value = NUMBER [p.29]

This attribute specifies the value to be used when determining the value of the enumerator
on a list item within an ol [p.64] .

The li [p.64] element defines a list item within an ordered, unordered, or navigation list.

Within a list, each li element has an associated number, which is used for numbering list items
in ordered lists:

If the li element has a value attribute, the associated number is the value of that attribute;
otherwise, if the li element is the first in the list, then the number has the value 1;
otherwise the number is one higher than the number of the preceding li in the same list.

11.5. The label element

Attributes

The Common [p.34] collection

The label [p.65] element is used to define a label for a list. The contents of the label element
represent the title of a list (or sublist).

11.6. Issues
[XHTML2] 11.3. The ol , and ul elements PR #7663
State: Open
Resolution: None
User: None

Notes:
The working group is not in favor or the definition of a "continueFrom" attribute that would allow
continuation of list numbering, simply because there is no way to describe the behavior in
current styling languages. However, there is a usecase for being able to define groups of list
items and label them.... The working group is continuing to discuss this issue. To be *really* fair
to the required structure in his use case ... you really want something like this: <ol> <group>
<li>.. <li>... <li>... </group> <group> <label>... <li>... <li>... </group> </ol> The use case has two
different structures imposed on top of each other A bit like <label for=""> in HTML4

Re: WD-xhtml2-20040722: Some navigation list requirements (IMHO) PR #7867

State: Open
Resolution: None
User: None

- 65 -
11.6. Issues XHTML™ 2.0

Notes:

- 66 -
XHTML™ 2.0 12. XHTML Core Attributes Module

12. XHTML Core Attributes Module

This section is normative.

This module defines the Core [p.67] attribute collection.

12.1. Core Attribute Collection

class = NMTOKENS [p.29]
This attribute assigns one or more class names to an element; the element may be said to
belong to these classes. A class name may be shared by several element instances.

The class [p.67] attribute can be used for different purposes in XHTML, for instance as a
style sheet [p.137] selector (when an author wishes to assign style information to a set of
elements), and for general purpose processing by user agents.

For instance in the following example, the p [p.46] element is used in conjunction with the
class [p.67] attribute to identify a particular type of paragraph.

Example
<p class="note">
These programs are only available if you have purchased
the advanced professional suite.
</p>

Style sheet rules can then be used to render the paragraph appropriately, for instance by
putting a border around it, giving it a different background color, or where necessary by not
displaying it at all.

It is good style to use names that represent the purpose of the element rather than the
visual presentation to be used. For instance don’t use class="red", but rather
class="urgent", or similar.

id = ID [p.29]
The id [p.67] attribute assigns an identifier to an element. The value of this attribute must be
unique within a document. This attribute MUST NOT be specified on an element in
conjunction with the xml:id [p.68] attribute.

The id [p.67] attribute has several roles in XHTML:

As a style sheet [p.137] selector.

As a target anchor [p.59] for hypertext links.
As the name of a declared object [p.121] element.
For general purpose processing by user agents (e.g. for identifying fields when
extracting data from XHTML pages into a database, translating XHTML documents into
other formats, etc.).

- 67 -
12.1. Core Attribute Collection XHTML™ 2.0

As an example, the following headings are distinguished by their id [p.67] values:

Example
<h id="introduction">Introduction</h>
<p>...</p>
<h id="events">The Events Module</h>
<p>...</p>

xml:id = ID [p.29]
The xml:id [p.68] attribute assigns an identifier to an element. The value of this attribute
must be unique within a document. This attrinute MUST NOT be specified on an element in
conjunction with the id [p.67] attribute.

The xml:id [p.68] attribute has several roles in XHTML:

As a style sheet [p.137] selector.

As an example, the following headings are distinguished by their xml:id [p.68] values:

Example
<h xml:id="introduction">Introduction</h>
<p>...</p>
<h xml:id="events">The Events Module</h>
<p>...</p>

layout = irrelevant*|relevant
This attribute allows authors to indicate whether the whitespace within an element is
relevant to the meaning of the content or not; for instance, visual user agents could display
the whitespace. The default is that it is irrelevant. Some elements, notably pre [p.47]
override this default. See whitespace handling in the section on XHTML Family User Agent
Conformance for more information.

Example
<p class="poem" layout="relevant">
(with wee ears and see?

tail frisks)
(gonE)
</p>

- 68 -
XHTML™ 2.0 12.2. Issues

title = Text [p.31]

This attribute defines meta-information about the element on which it is set.

Example
<a href="Jakob.html" title="Author biography">Jakob Nielsen</a>’s
Alertbox for January 11, 1998

Implementation: RELAX NG [p.193]

12.2. Issues
attributes with no values PR #7872
State: Open
Resolution: None
User: None

Notes:
The working group intended this be NMTOKENS, and that an empty value be not permitted.

- 69 -
12.2. Issues XHTML™ 2.0

- 70 -
XHTML™ 2.0 13. XHTML Hypertext Attributes Module

13. XHTML Hypertext Attributes Module

This section is normative.

The Hypertext Attributes Module defines the Hypertext [p.71] attribute collection. This collection
allows an element to be the start point of a hypertext link to a remote resource.

13.1. Hypertext Attribute Collection

cite = URI [p.31]
The value of this attribute is a URI [p.31] that designates a source document or message.
This attribute is intended to give further information about the element’s contents (e.g., the
source from which a quotation was borrowed, or the reason text was inserted or deleted).
User Agents MUST provide a means for the user to actuate the link.

Example
cite="comments.html"

href = URI [p.31]

This attribute specifies a URI that is actuated when the element is activated.

Actuation occurs as the default action of a [DOM [p.247] ] DOMActivate event for the
element on which the attribute occurs (for instance as the result of the user clicking on the
associated element). If elements contained within an element using an href [p.71] also use
an href [p.71] attribute, the User Agent must provide a mechanism for actuating any of
these "nested" URIs.

Example
<abbr href="http://www.w3.org/" title="World Wide Web">WWW</abbr>
<li href="contents.xhtml">contents</li>
<a href="http://www.cwi.nl/~steven/amsterdam.html">Amsterdam</a>
<quote href="hamlet.xhtml#p2435">To be or not to be</quote>
<var href="#index_ninc">ninc</var>

hreflang = LanguageCodes [p.30]

This attribute specifies the primary language of the resource designated by href [p.71] . At
its most general, it is a comma-separated list of language ranges with optional accept
parameters, as defined in section 14.4 of [RFC2616 [p.248] ] as the field value of the
Accept-Language request header.

In its simplest case, this is just a language code, such as "nl", but it may also contain variant
specifications such as "en-gb".

- 71 -
13.1. Hypertext Attribute Collection XHTML™ 2.0

The user agent must use this list as the field value of the accept-language request
header when requesting the resource using HTTP.

If this attribute is not present, the user agent must use its default value of the
accept-language request header.

Example
<p href="http://www.w3.org/2003/06/semantictour-pressrelease"
hreflang="fr">
The press release in French
</p>

hrefmedia = MediaDesc [p.31]

This attribute indicates the type(s) of media to which to make available the content
referenced by the associated href [p.71] URI.

Example
<p href="http://www.example.com/forPrinters.html"
hrefmedia="print">
A printable version of this page.
</p>

hreftype = ContentTypes [p.30]

This attribute specifies the allowable content types of the relevant href [p.71] URI. See the
definition of type ContentTypes [p.30] for details of how it is used.

Example
<p href="http://www.w3.org"
hreftype="text/html,application/xhtml+xml">
The W3C Home Page
</p>

nextfocus = IDREF [p.29]

This attribute specifies an IDREF of an element in the current document that will receive
focus when the user requests that the user agent navigate to the next element that can
receive focus.

The sequence of focusable [p.18] elements is called the document’s navigation order. The
navigation order defines the order in which elements will receive focus when navigated by
the user. The navigation order may include elements nested within other elements.

When a document is first loaded, a user agent must do the following:

1. If a document is loaded using a URI that includes a reference to a fragment identifier

(such as book.html#chapter5)
1. If the fragment reference identifies an element in the document, the user agent
must ensure that navigation starts at the beginning of that element.
2. If the referenced element is focusable, that element receives focus.

- 72 -
XHTML™ 2.0 13.1. Hypertext Attribute Collection

3. If the fragment reference does not resolve in the document, the user agent must
ensure navigation starts at the beginning of the document.
2. If there is no reference to a fragment identifier when the document is loaded:
1. If the root element of the document has a nextfocus [p.72] attribute, and the
element referred to by the attribute is focusable, the element must receive focus.
The user agent must ensure the beginning of the element is visible on the display.
2. If the root element has no nextfocus [p.72] attribute, no element receives initial
focus. The user agent must ensure navigation starts at the beginning of the
document.
3. If the user has moved away from the initial navigation point of a document (e.g.,
through using page up and page down or by changing focus), refreshing the document
should result in the user’s navigation location being preserved.

In the event no element in the document has focus, when the user requests the next
focusable element, that element must be the next focusable element forward from the
current navigation point in document order. If there are no focusable elements before the
end of the document, focus shifts to the first focusable element in document order. If a
document has no focusable elements, then no element receives focus.

Once a focusable element in the document has focus, upon requesting that focus change to
the next focusable element, the user agent MUST follow these rules when determining
where focus is next set:

1. The next focus of an element without a nextfocus [p.72] attribute is the next focusable
[p.18] element in document order. If there are no remaining focusable [p.18] elements
in document order, the next focus must be on the first focusable [p.18] element in
document order.
2. The next focus of an element with a nextfocus [p.72] attribute is the element referenced
by that attribute if it is focusable [p.18] , otherwise the next focus of that element.

Regardless of the way in which an element receives focus, if the element is not currently
visible on the user agent’s display, the display must be updated so that the element is
visible.

The following example would allow the links to be navigated in column order (without the
use of nextfocus they would be navigated in document, i.e. row, order):

Example
<table>
<tr><td id="a" href="nw" nextfocus="b">NW</td>
<td id="c" href="ne" nextfocus="d">NE</td></tr>
<tr><td id="b" href="sw" nextfocus="c">SW</td>
<td id="d" href="se">SE</td></tr>
</table>

- 73 -
13.1. Hypertext Attribute Collection XHTML™ 2.0

Navigation keys. The actual key sequence that causes navigation or element activation
depends on the configuration of the user agent (e.g., the "tab" key might be used for
navigation and the "enter" key or "space" key used to activate a selected element).

prevfocus = IDREF [p.29]

This attribute specifies an IDREF of an element in the current document that will receive
focus when the user requests that user agent navigate to the previous element that can
receive focus.

In the event no element in the document has focus, when the user requests the previous
focusable [p.18] element, that element must be the next focusable element backward from
the current navigation point in document order. If there is no such focusable element back
to the start of the document, focus shifts to the last focusable element in document order. If
a document has no focusable elements, the behavior is unspecified.

Once a focusable element in the document has focus, upon requesting that focus change to
the previous focusable element, the user agent must do the following:

1. If the focused element has a prevfocus [p.74] attribute that references a focusable
element, focus is moved to that element.
2. Otherwise, focus shifts to the previous focusable element in document order.
3. If there are no previous focusable elements in document order, focus shifts to the last
focusable element in document order.

Regardless of the way in which an element receives focus, for visual user agents, if the
element is not currently visible on the user agent’s display, the display must be updated so
that the element is visible.

target = HrefTarget [p.30]

This attribute identifies an environment that will act as the destination for a resource
identified by a hyperlink when it is activated.

This specification does not define how this attribute gets used, since that is defined by the
environment that the hyperlink is actuated in. See for instance XFrames [XFRAMES [p.249]
]. However, values of this attribute that begin with the character ’_’ are reserved.

Example
<a href="home.html" target="main">Home</a>

xml:base = URI [p.31]

This attribute specifies the base URI from which to resolve relative URIs. It is normatively
defined in [XMLBASE [p.248] ]. Any relative URI used on an element that uses this attribute,
or on an element contained within an element that uses this attribute, must be resolved
relative to the base URI defined by this attribute.

- 74 -
XHTML™ 2.0 13.2. Issues

An element inherits URI base information according to the following order of precedence
(highest to lowest):

1. The xml:base [p.74] attribute set for the element itself.

2. The closest parent element that has the xml:base [p.74] attribute set (i.e., the xml:base
[p.74] attribute is inherited).
3. The HTTP "Content-Location" header (which may be configured in a server).
4. The location of the document itself.

Example
See:
<ul xml:base="http://www.w3.org">
<li href="/" src="Icons/w3c_home">The W3C home page</li>
<li href="/TR">The W3C Technical Reports page</li>
<li href="/Markup">The HTML home page</li>
<li href="/Markup/Forms">The XForms home page</li>
</ul>

Implementation: RELAX NG [p.194]

13.2. Issues
Fw: [XHTML 2] 13.1 Hypertext Attributes Module - nextfocus PR #7792
State: Approved
Resolution: None
User: None

Notes:
It is up to the document author to ensure that anchors in a document are appropriate for the
document’s audience. It would be inappropriate for a user agent to second guess the author’s
intent by adjusting focus to some parent element of the target. With regard to form fields and
incrementally loading user agents, the working group feels that it is unlikely a document’s fields
should be active before the document is done loading. Loading is complete when the DOMload
event fires - before that the user should not be able to interact with the document’s content - the
content may not have been properly prepared / initialized until after that.

- 75 -
13.2. Issues XHTML™ 2.0

- 76 -
XHTML™ 2.0 14. XHTML I18N Attribute Module

14. XHTML I18N Attribute Module

This section is normative.

This module defines the I18N [p.77] attribute collection.

14.1. I18N Attribute Collection

xml:lang = LanguageCode [p.30]
This attribute indicates the language of an element’s attribute values and text content, and
of all elements it contains, unless overridden. It is defined normatively in [XML [p.248] ]
section 2.12. The default value of this attribute is unspecified.

An element inherits language code information according to the following order of

precedence (highest to lowest):

1. The xml:lang [p.77] attribute set for the element itself.

2. The closest parent element that has the xml:lang [p.77] attribute set (i.e., the xml:lang
[p.77] attribute is inherited).

In this example, the default text-processing language of the document is French ("fr").
Within the first paragraph a single word is declared to be in English ("en"), after which the
primary language returns to French. The following paragraph is declared to be in English
and includes an embedded French word.

Example
<html xmlns="http://www.w3.org/2002/06/xhtml2" xml:lang="fr" ...>
<head>
<title>Un document multilingue</title>
</head>
<body>
<p>En janvier, toutes les boutiques de Londres
affichent des panneaux <span xml:lang="en">SALE</span>,
mais en fait ces magasins sont bien propres!</p>
<p xml:lang="en">Everwhere I went in France
the bakeries had signs up saying <em xml:lang="fr">PAIN</em>,
but despite that the bakers seemed quite happy.
</p>
</body>
</html>

Implementation: RELAX NG [p.196]

- 77 -
14.2. Issues XHTML™ 2.0

14.2. Issues
Internationalization: translate attribute PR #7883
State: Open
Resolution: None
User: None

Notes:

- 78 -
XHTML™ 2.0 15. XHTML Access Module

15. XHTML Access Module

This section is normative.

This module defines the access [p.79] element.

Element Attributes Content Model

access [p.79] Common [p.34] , key [p.79] , targetid [p.80] , targetrole [p.80] EMPTY

Implementation: RELAX NG [p.196]

15.1. The access element

The access [p.79] element assigns an accessibility mapping to elements within a document.
Actuating the shortcut results in the element gaining focus.

Attributes

The Common [p.34] collection

key = Character [p.29]

This attribute assigns a key mapping to an access shortcut. An access key is a single
character from the document character set. Note: Authors should consider the input method
of the expected reader when specifying an accesskey.

Triggering an access key defined in an access element gives focus to the next element in
navigation order from the current focus that has the referenced role or id value. Note that it
is possible to associate additional event handlers with target which might then perform
additional actions once focus is changed.

The invocation of access keys depends on the implementation. For instance, on some
systems one may have to press the "alt" key in addition to the access key. On other
systems, one generally has to press the "cmd" key in addition to the access key.

The rendering of access keys depends on the user agent. We recommend that authors
include the access key in label text or wherever the access key is to apply. User agents
should render the value of an access key in such a way as to emphasize its role and to
distinguish it from other characters (e.g., by underlining it).

The Character assigned to a key, and its relationship to a role [p.131] or id [p.67] attribute,
are a suggestion of the author. User agents may provide mechanisms for overriding,
disabling, or re-assigning keys. In such user agents, user-specified assignments must take
precendence.

- 79 -
15.1. The access element XHTML™ 2.0

targetid = IDREF [p.29]

The targetid [p.80] attribute specifies an IDREF [p.29] of the target element for the
associated event (i.e., the node to which the event should be delivered).

targetrole = QNames [p.31]

The targetrole [p.80] attribute specifies space separated list if QNames [p.31] that maps to
an element with a role [p.131] attribute with the same value.

If no key attribute is specified, the user agent may assign an appropriate device mapping.

If a targetid [p.80] and a targetrole [p.80] are both specified for an element, the targetid [p.80]
attribute value must take precedence.

Access element that focuses into a field

Accessing a table of contents

Access that moves to the main content

Access element that goes to a specific element

Access element with no specific key mapping

- 80 -
XHTML™ 2.0 16. XHTML Bi-directional Text Attribute Module

16. XHTML Bi-directional Text Attribute Module

This section is normative.

The Bi-directional Text module defines the Bi-directional [p.81] attribute collection.

16.1. Bi-directional Text Collection

dir = "ltr|rtl|lro|rlo"
This attribute allows the author to specify the direction of the element’s text content. This
direction affects the display of characters as defined in Unicode Standard Annex #9: The
Bidirectional Algorithm [UAX9 [p.248] ], and defines directional properties of text as defined
by CSS2 [CSS2 [p.247] ]. The default value of this attribute is ltr. Possible values are:
ltr: Left-to-right text. The effect of this attribute is defined by the CSS2 rule:
*[dir="ltr"] { unicode-bidi: embed; direction: ltr}

rtl: Right-to-left text. The effect of this attribute is defined by the CSS2 rule:
*[dir="rtl"] { unicode-bidi: embed; direction: rtl}

lro: Left-to-right override. The effect of this attribute is defined by the CSS2 rule:
*[dir="lro"] { unicode-bidi: bidi-override; direction: ltr}

rlo: Right-to-left override. The effect of this attribute is defined by the CSS2 rule:
*[dir="rlo"] { unicode-bidi: bidi-override; direction: rtl}

Example
<p>
The Hebrew word for "Hebrew" is
<span xml:lang="he">עברית</span>,
but since Hebrew letters have intrinsic right-to-left directionality,
I had to type the word starting from the letter "ע",
i.e. <span xml:lang="he" dir="lro">עברית</span>.
</p>

This might display as .

16.1.1. Inheritance of text direction information

The Unicode bidirectional algorithm requires a base text direction for text blocks. To specify the
base direction of a block-level element, set the element’s dir [p.81] attribute. The default value of
the dir [p.81] attribute is ltr (left-to-right text).

- 81 -
16.1.2. The effect of style sheets on bidirectionality XHTML™ 2.0

When the dir [p.81] attribute is set for a block-level element, it remains in effect for the duration
of the element and any nested block-level elements. Setting the dir [p.81] attribute on a nested
element overrides the inherited value.

To set the base text direction for an entire document, set the dir [p.81] attribute on the html
[p.38] element.

Example
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 2.0//EN"
"http://www.w3.org/MarkUp/DTD/xhtml2.dtd">
<html xmlns="http://www.w3.org/2002/06/xhtml2/" dir="rtl">
<head>
<title><em>...a right-to-left title...</em></title>
</head>
<body>
<em>...right-to-left text...</em>
<p dir="ltr"><em>...left-to-right text...</em></p>
<p><em>...right-to-left text again...</em></p>
</body>
</html>

Inline-level elements, on the other hand, do not inherit the dir [p.81] attribute. This means that an
inline element without a dir [p.81] attribute does not open an additional level of embedding with
respect to the bidirectional algorithm.

An element is considered to be block-level if its presentation, when expressed in [CSS2 [p.247]

], is display: block and inline-level if its presentation, when expressed in [CSS2 [p.247] ], is
display: inline.

16.1.2. The effect of style sheets on bidirectionality

In general, using style sheets (such as [CSS2 [p.247] ] to change an element’s visual rendering
from the equivalent of display: block to display: inline or vice-versa is
straightforward. However, because the bidirectional algorithm relies on the inline/block-level
distinction, special care must be taken during the transformation.

When an inline-level element that does not have a dir [p.81] attribute is transformed to a
block-level element by a style sheet, it inherits the dir [p.81] attribute from its closest parent
block-level element to define the base direction of the block.

When a block-level element that does not have a dir [p.81] attribute is transformed to an
inline-level element by a style sheet, the resulting presentation should be equivalent, in terms of
bidirectional formatting, to the formatting obtained by explicitly adding a dir [p.81] attribute
(assigned the inherited value) to the transformed element.

Implementation: RELAX NG [p.197]

- 82 -
XHTML™ 2.0 16.2. Issues

16.2. Issues
[XHTML 2] 15 Bi-directional text collection and embedded attributes? PR #7783
State: Open
Resolution: None
User: None

Notes:

- 83 -
16.2. Issues XHTML™ 2.0

- 84 -
XHTML™ 2.0 17. XHTML Edit Attributes Module

17. XHTML Edit Attributes Module

This section is normative.

This module defines the Edit [p.85] attribute collection.

17.1. Edit Collection

edit = "inserted|deleted|changed|moved"
This attribute allows elements to carry information indicating how content has changed.
Possible values:
inserted: the content has been inserted
deleted: the content has been deleted
changed: the content has changed considerably, therefore making it not worth being
marked up with values of inserted and deleted
moved: the content has been moved from some other part of the document.

Example
<p>I will do it
next <span edit="deleted">week</span><span edit="inserted">month</span>.</p>

datetime = Datetime [p.30]

The value of this attribute specifies the date and time when a change was made.

Example
datetime="2003-01-13T13:15:30Z"

Implementation: RELAX NG [p.198]

- 85 -
17.1. Edit Collection XHTML™ 2.0

- 86 -
XHTML™ 2.0 18. XHTML Embedding Attributes Module

18. XHTML Embedding Attributes Module

This section is normative.

The Embedding Attributes module defines the Embedding [p.87] attribute collection.

This collection causes the contents of a remote resource to be embedded in the document in
place of the element’s content. If accessing the remote resource fails, for whatever reason
(network unavailable, no resource available at the URI given, inability of the user agent to
process the type of resource) or an associated ismap [p.96] attribute fails, the content of the
element must be processed instead.

Note that this behavior makes documents far more robust, and gives much better opportunities
for accessible documents than the longdesc attribute present in earlier versions of XHTML,
since it allows the description of the resource to be included in the document itself, rather than in
a separate document.

Example
<p src="holiday.png" srctype="image/png">
<span src="holiday.gif" srctype="image/gif">
An image of us on holiday.
</span>
</p>

<table src="temperature-graph.png" srctype="image/png">

<caption>Average monthly temperature over the last 20 years</caption>
<tr><th>Jan</th><th>Feb</th><th>Mar</th><th>Apr</th><th>May</th><th>Jun</th>
<th>Jul</th><th>Aug</th><th>Sep</th><th>Oct</th><th>Nov</th><th>Dec</th>
</tr>
<tr><td> 4</td><td> 2</td><td> 7</td><td> 9</td><td>13</td><td>16</td>
<td>17</td><td>17</td><td>14</td><td>11</td><td> 7</td><td> 4</td>
</tr>
</table>

18.1. Embedding Attribute Collection

encoding = Encodings [p.29]
This attribute specifies the allowable encoding of the external resource referenced by the
src [p.88] attribute. At its most general, it is a comma-separated list of encodings, such as
"utf-8", "utf8, utf-16", or "utf-8, utf-16, *".

The user agent must use this list as the field value of the accept-charset request header
when requesting the resource using HTTP.

If this attribute is not present, the user agent must use its default value of the accept-charset
request header.

- 87 -
18.2. Issues XHTML™ 2.0

User agents should use a similar technique when using other protocols that allow encoding
negotation

When using protocols that do not allow encoding negotiation to retrieve resources whose
encodings are not self-identifying, the user agent should use the first encoding in the
attribute’s value as the indication of the resource.

Example
<style type="text/css" src="style/home" encoding="utf-8" />

src = URI [p.31]

This attribute specifies the location of an external source for the contents of the element.
Actuation occurs as the default action of a [DOM [p.247] ] load event for the element that
the attribute occurs on.

srctype = ContentTypes [p.30]

This attribute specifies the allowable content types of the resource referenced by the
relevant src [p.88] URI.

Example
<handler src="pop" srctype="application/x-javascript, text/x-newspeak" />

<style src="midnight" srctype="text/css, text/x-mystyle" />

<p src="w3c-logo" srctype="image/png, image/jpeg;q=0.2">W3C logo</p>

<span src="logo.png">Our logo</span>

<span src="theme.mp3" srctype="audio/x-mpeg">Our theme jingle</span>

Implementation: RELAX NG [p.198]

18.2. Issues
Re: Formal Response to My issue on styling embedding attributes. PR #7724
State: Open
Resolution: None
User: None

Notes:
Original message at: http://lists.w3.org/Archives/Public/www-html-editor/2005AprJun/0064 This
is a reply to issue 7655, where SP also replied

17 Embedding Attributes User aborted downloads. PR #7730

State: Open
Resolution: None
User: None

- 88 -
XHTML™ 2.0 18.2. Issues

Notes:

17 Embedding Attributes - Invalid XHTML 2 documents PR #7731

State: Open
Resolution: None
User: None

Notes:

[XHTML 2] 17.1 Encoding attribute PR #7732

State: Open
Resolution: None
User: None

Notes:

[XHTML 2] Embedding attributes and nextFocus PR #7733

State: Open
Resolution: None
User: None

Notes:

17 Embedding Attributes Success/Failure status codes. PR #7734

State: Open
Resolution: None
User: None

Notes:
The 200 codes are classified as SUCCESS, so there should be no doubt. An empty document is
perfectly acceptable, so 204 is also a success 400 are all failures. 401: the HTTP req says the
reply SHOULD be shown to the user. It doesn’t say it has to be shown by embedding it at the
position where the URL was. It could be shown in a dialogue box, or a separate window.

[XHTML 2] 17 Embedding Attributes - srcType PR #7735

State: Approved
Resolution: None
User: None

Notes:
Add note to section that effect is defined in the datatype definition.

[XHTML 2] Embedding XHTML Resources Linking. PR #7736

State: Open
Resolution: None
User: None

- 89 -
18.2. Issues XHTML™ 2.0

Notes:

[XHTML 2] Embedded Resources containing links PR #7737

State: Open
Resolution: None
User: None

Notes:

[XHTML 2] Embedding Attributes Examples PR #7738

State: Open
Resolution: None
User: None

Notes:

[XHTML 2] 17 Clipping of embedded documents to viewport. PR #7739

State: Open
Resolution: None
User: None

Notes:

[XHTML 2] 17 Embedding Attributes PR #7774

State: Open
Resolution: None
User: None

Notes:

xhtml2 attributes type, srctype and hreftype PR #7892

State: Open
Resolution: None
User: None

Notes:

- 90 -
XHTML™ 2.0 19. XHTML Handler Module

19. XHTML Handler Module

This section is normative.

The Handler Module defines elements that are used to contain information pertaining to event
handler implementations, usually defined in a scripting language. Elements and attributes
included in this module are:

Elements Attributes Content Model

handler [p.91] Common [p.34] , type [p.91] PCDATA | handler [p.91]

When this module is used, the handler [p.91] element is added to the Structural [p.43] and Text
[p.51] content sets of the Structural [p.41] and Text [p.51] Modules. In addition, the handler
[p.91] element is added to the content model of the head [p.38] element defined in the
Document [p.37] Module.

Implementation: RELAX NG [p.199]

19.1. The handler element

Attributes

The Common [p.34] collection

type = ContentType [p.29]

This attribute specifies the type of the content within the element.

The handler [p.91] element places one or more event handlers within a document. This element
may appear any number of times in the head [p.38] or body [p.39] of an XHTML document.

The handler may be defined within the contents of the handler [p.91] element or in an external
resource. If the src [p.88] attribute is not set, user agents must interpret the contents of the
element as the handler. If the src [p.88] has a URI value, user agents must ignore the element’s
contents and retrieve the handler via the URI. Note that the encoding [p.87] attribute refers to
the character encoding [p.29] of the handler designated by the src [p.88] attribute; it does not
concern the content of the handler [p.91] element.

19.1.1. Rules for processing handlers

Handlers are evaluated by handler engines that must be known to a user agent.

- 91 -
19.1.2. Declaration of a handler language XHTML™ 2.0

A user agent must interpret a handler [p.91] element according to the following precedence
rules:

1. The user agent must first try to process the handler element, but not the embedded content.
2. If the user agent is not able to process the handler for any reason (configured not to, no
support of the indicated handler type, no access to an external resource, etc.), it must try to
process its contents.
3. If the content is a handler [p.91] element, its content should be processed according to
these rules.
4. Otherwise, it is evaluated as data of the handler type of the containing handler element.

The syntax of handler data depends on the handler implementation language.

19.1.2. Declaration of a handler language

The type [p.91] attribute must be specified for each handler [p.91] element instance in a
document.

In this example, we include one handler [p.91] in the header, whose handler is located in an
external file and is in the handler language "text/x-vbscript". The JavaScript code contained in
the inner handler [p.91] will be evaluated if and only if the user agent isn’t evaluating the outer
handler [p.91] . We also include one handler [p.91] in the body, which contains its own handler
written in "text/x-perl".

Example
<html xmlns="http://www.w3.org/2002/06/xhtml2" xml:lang="en">
<head>
<title>A document with a handler</title>
<handler type="text/x-vbscript" src="http://example.org/progs/vbcalc">
<handler type="text/javascript">
...some inline JavaScript...
</handler>
</handler>
</head>
<body>
<handler type="text/x-perl">
... some Perl script ...
</handler>
</body>
</html>

19.1.3. Dynamic modification of documents

Note that the processing model of XML means that the [DOM [p.247] ] method
document.write cannot be used in XHTML2. To dynamically generate content in XHTML you
have to add elements to the DOM tree using DOM calls [DOM [p.247] ] rather than using
document.write to generate text that then gets parsed.

- 92 -
XHTML™ 2.0 20. XHTML Image Module

20. XHTML Image Module

This section is normative.

The Image Module provides basic image embedding, and may be used in some
implementations independently of client side image maps. The Image Module supports the
following element and attributes:

Elements Attributes Content Model

img Common [p.34] (PCDATA | Text [p.51] )*

Implementation: RELAX NG [p.200]

20.1. The img element

Attributes

The Common [p.34] collection

The img [p.93] element is a holder for embedding attributes such as src [p.88] . Since these
attributes may be applied to any element, the img [p.93] element is not strictly necessary, but is
included to ease the transition to XHTML2. Like the object [p.121] element, this element’s
content is only presented if the referenced resource is unavailable.

In the following example, the W3C logo would be presented if it were available. If it were
unavailable, then the enclosed text would be presented.

Example
<img src="W3C.png">W3C</img>

- 93 -
20.1. The img element XHTML™ 2.0

- 94 -
XHTML™ 2.0 21. XHTML Image Map Attributes Module

21. XHTML Image Map Attributes Module

This section is normative.

This collection adds attributes that specify that an embedded image may be used as an image
map, so that clicking on different parts of the image causes different hyperlinks to be activated.

Note that in the following example, if the image is unavailable for any reason, the fallback
properties of the src [p.88] attribute mean that the nl element will be displayed instead of the
image, thus making the page still useful:

Example
<html xmlns="http://www.w3.org/2002/06/xhtml2">
<head>
<title>The cool site!</title>
</head>
<body>
<p src="navbar1.png" srctype="image/png" usemap="#map1">
<nl id="map1">
<label>Navigate the site:</label>
<li href="guide.html" shape="rect"
coords="0,0,118,28">
Access Guide
</li>
<li href="shortcut.html" shape="rect"
coords="118,0,184,28">
Go
</li>
<li href="search.html" shape="circle"
coords="184,200,60">
Search
</li>
<li href="top10.html" shape="poly"
coords="276,0,276,28,100,200,50,50,276,0">
Top Ten
</li>
</nl>
</p>
</body>
</html>

Note that an li [p.64] in an nl [p.63] is not required to have an href [p.71] attribute. In that case,
the relevant region of the image is inactive.

Example

- 95 -
21.1. Image Map Attribute Collection XHTML™ 2.0

<p src="image.png" srctype="image/png" usemap="#map1">

<nl id="map1">
<label>Navigation that has an inactive ring</label>
<li shape="circle" coords="100,200,50">I’m inactive.</li>
<li href="outer-ring-link.html" shape="circle"
coords="100,200,250">
I’m active.
</li>
</nl>
</p>

Note that W3C is working on profiles of XHTML that include versions of SVG [SVG [p.249] ],
which include more structured ways of creating imagemap-like behavior.

21.1. Image Map Attribute Collection

usemap = URI [p.31]

This attribute associates an image map with an nl [p.63] element. The value of usemap
should match the value of the id [p.67] attribute of an nl [p.63] element that contains one or
more li [p.64] elements with shape [p.97] and coords [p.97] attributes.

If accessing the URI fails or the referenced element is not an nl [p.63] element, then the
associated src [p.88] attribute is considered to have failed as well, so that the nested
content will be processed instead.

ismap = "ismap"

This attribute indicates that the associated embedded resource is to be treated as a

"server-side image map". When selected, the coordinates within the element that the user
selected are sent to the server where the document resides. Coordinates are expressed as
pixel values relative to the embedded resource, and start at (0,0) at the top left corner.

When an ismap attribute is specified, click events are not delivered to the embedded
resource, regardless of its type.

In the following example, the active region defines a server-side image map. A click
anywhere on the image will cause the click’s coordinates to be sent to the server.
<p href="http://www.example.com/cgi-bin/map"
src="map.png" ismap="ismap">
Our location.
</p>

The location clicked is passed to the server as follows. The user agent derives a new URI
from the URI specified by the href [p.71] attribute of the element, by appending ‘?’ followed
by the x and y coordinates, separated by a comma. The link is then actuated using the new
URI. For instance, in the given example, if the user clicks at the location x=10, y=27 then
the derived URI is "http://www.example.com/cgi-bin/map?10,27".

- 96 -
XHTML™ 2.0 21.1. Image Map Attribute Collection

User agents that do not offer the user a means to select specific coordinates (e.g.,
non-graphical user agents that rely on keyboard input, speech-based user agents, etc.)
must send the coordinates "0,0" to the server when the link is activated.

shape = "default|rect|circle|poly"
This attribute specifies the shape of a region. Possible values:
default: Specifies the entire region.
rect: Define a rectangular region.
circle: Define a circular region.
poly: Define a polygonal region.

coords = Coordinates [p.30]

This attribute specifies the position and shape of the area. The number and order of values
depends on the value of the shape [p.97] attribute. Possible combinations:
rect: left-x, top-y, right-x, bottom-y.
circle: center-x, center-y, radius. When the radius value is a percentage, the actual
radius value is calculated using the associated image’s width and height. The radius is
then the smaller value of the two.
poly: x1, y1, x2, y2, ..., xN, yN. If the first and last x and y coordinate pairs are not the
same, user agents must infer an additional coordinate pair to close the polygon.

Coordinates are relative to the top, left corner of the object. All values are of type Length
[p.30] . All values are separated by commas. The coordinates of the top, left corner of an
area are 0, 0.

Implementation: RELAX NG [p.201]

- 97 -
21.1. Image Map Attribute Collection XHTML™ 2.0

- 98 -
XHTML™ 2.0 22. XHTML Media Attribute Module

22. XHTML Media Attribute Module

This section is normative.

The Media Attribute Module defines the media attribute.

22.1. Media Attribute Collection

media = MediaDesc [p.31]
The value of this attribute specifies the types of media for which the element is intended.
When the value of this attribute matches the current processing media, the element is
processed as normal; otherwise it is ignored. The default value for this attribute is all.

Example
<style src="style.css" type="text/css" media="screen" />
<span src="photo.jpg" media="screen">Me at work</span>
<span src="photo-hires.jpg" media="print">Me at work</span>

Implementation: RELAX NG [p.202]

- 99 -
22.1. Media Attribute Collection XHTML™ 2.0

- 100 -
XHTML™ 2.0 23. XHTML Metainformation Module

23. XHTML Metainformation Module

This section is normative.

The Metainformation Module defines elements that allow the definition of relationships. These
may relate to:

the document itself,

items external to the document, or
other items of metadata within the document.

Note that this module is dependent upon the Metainformation Attributes [p.113] module. The
attributes defined therein are available on the elements defined in this module, and their
semantics are the essential part of how these elements behave.

Elements and attributes in this module are:

Elements Attributes Content Model

link Common [p.34] ( link | meta )*
meta Common [p.34] ( PCDATA | Text [p.51] )*

Implementation: RELAX NG [p.203]

23.1. The link element

Attributes

The Common [p.34] collection

This element defines a link. Link [p.101] conveys relationship information that may be rendered
by user agents in a variety of ways (e.g., a tool-bar with a drop-down menu of links). User
agents should enable activation of links and the retrieval of link targets. Since link [p.101]
elements may have no content, information from the rel [p.115] and title [p.69] attributes should
be used when labelling links.

This example illustrates how several link [p.101] definitions may appear in the head [p.38]
section of a document. The current document is "Chapter2.html". The rel [p.115] attribute
specifies the relationship of the linked document with the current document. The values "Index",
"Next", and "Prev" are explained in the section on the attribute rel [p.115] .

- 101 -
23.1.1. Forward and reverse links XHTML™ 2.0

<head>
<title>Chapter 2</title>
<link rel="index" href="../index.html"/>
<link rel="next" href="Chapter3.html"/>
<link rel="prev" href="Chapter1.html"/>
</head>

23.1.1. Forward and reverse links

While the rel [p.115] attribute specifies a relationship from this document to another resource,
the rev [p.117] attribute specifies the reverse relationship.

Consider two documents A and B.

Document A: <link href="docB" rel="index"/>

Has exactly the same meaning as:

Document B: <link href="docA" rev="index"/>

namely that document B is the index for document A.

Both the rel [p.115] and rev [p.117] attributes may be specified simultaneously.

23.1.2. Links and search engines

Authors may use the link [p.101] element to provide a variety of information to search engines,
including:

Links to alternate versions of a document, written in another human language.

Links to alternate versions of a document, designed for different media, for instance a
version especially suited for printing.
Links to the starting page of a collection of documents.

The examples below illustrate how language information, media types, and link types may be
combined to improve document handling by search engines.

The following example shows how to use the hreflang [p.71] attribute to indicate to a search
engine where to find other language versions of a document. Note that for the sake of the
example the xml:lang [p.77] attribute has been used to indicate that the value of the title [p.69]
attribute for the link [p.101] element designating the French manual is in French.
<html ... xml:lang="en">
<head>
<title>The manual in English</title>
<link title="The manual in Dutch"
rel="alternate"
hreflang="nl"
href="http://example.com/manual/dutch.html"/>
<link title="La documentation en Français"

- 102 -
XHTML™ 2.0 23.2. The meta element

rel="alternate"
hreflang="fr" xml:lang="fr"
href="http://example.com/manual/french.html"/>
</head>

In the following example, we tell search engines where to find the printed version of a manual.
<head>
<title>Reference manual</title>
<link media="print"
title="The manual in PostScript"
hreftype="application/postscript"
rel="alternate"
href="http://example.com/manual/postscript.ps"/>
</head>

In the following example, we tell search engines where to find the front page of a collection of
documents.
<head>
<title>Reference manual -- Chapter 5</title>
<link rel="start" title="The first chapter of the manual"
hreftype="application/xhtml+xml"
href="http://example.com/manual/start.html"/>
</head>

23.2. The meta element

Attributes

The Common [p.34] collection

The meta [p.103] element can be used to identify properties of a document (e.g., author,
expiration date, a list of key words, etc.) and assign values to those properties. This specification
defines a small normative set of properties, but users may extend this set as described for the
property [p.113] attribute.

Each meta [p.103] element specifies a property/value pair. The property [p.113] attribute
identifies the property and the content of the element or the value of the content [p.113] attribute
specifies the property’s value.

For example, the following declaration sets a value for the Author property:

Example
<meta property="dc:creator">Steven Pemberton</meta>

- 103 -
23.2.1. meta and search engines XHTML™ 2.0

Note. The meta [p.103] element is a generic mechanism for specifying metadata. However,
some XHTML elements and attributes already handle certain pieces of metadata and may be
used by authors instead of meta [p.103] to specify those pieces: the title [p.39] element, the
address [p.43] element, the edit [p.85] and related attributes, the title [p.69] attribute, and the cite
[p.71] attribute.

Note. When a property specified by a meta [p.103] element takes a value that is a URI [p.31] ,
some authors prefer to specify the metadata via the link [p.101] element. Thus, the following
metadata declaration:

Example
<meta property="dc:identifier">
http://www.rfc-editor.org/rfc/rfc3236.txt
</meta>

might also be written:

Example
<link rel="dc:identifier"
href="http://www.rfc-editor.org/rfc/rfc3236.txt" />

23.2.1. meta and search engines

A common use for meta [p.103] is to specify keywords that a search engine may use to improve
the quality of search results. When several meta [p.103] elements provide language-dependent
information about a document, search engines may filter on the xml:lang [p.77] attribute to
display search results using the language preferences of the user. For example,

Example

<meta property="keywords"
xml:lang="en-us">vacation, Greece, sunshine</meta>

<meta property="keywords"
xml:lang="en">holiday, Greece, sunshine</meta>

<meta property="keywords"
xml:lang="fr">vacances, Grèce, soleil</meta>

The effectiveness of search engines can also be increased by using the link [p.101] element to
specify links to translations of the document in other languages, links to versions of the
document in other media (e.g., PDF), and, when the document is part of a collection, links to an
appropriate starting point for browsing the collection.

- 104 -
XHTML™ 2.0 23.3. Literals and Resources

23.3. Literals and Resources

There are two types of properties that some item can have. The first is a simple string value,
which is useful for specifying properties such as dates, names, numbers and so on:

Example
this document was written on "March 21st, 2004"

This is not so useful though when trying to uniquely identify items that could occur in other
places. Take the example of the document’s author being "Mark Birbeck":

Example
this document was written by "Mark Birbeck"

Since there are other people called Mark Birbeck, then we won’t know which of them wrote
what. We get round this problem by allowing the value referred to, to be a URI. For example:

Example
this document was written by
<http://example.com/people/MarkBirbeck/654>

We distinguish these two types of properties by calling the first a ’string literal’ and the second a
’resource’.

NOTE: Of course there is nothing to stop two people from using this URI to identify two
completely different people. But in general URIs are accepted as a convenient way to identify a
specific item.

23.4. Document Properties

23.4.1. Literals
23.4.1.1. String Literals
The simplest piece of metadata is a string literal attached to the containing document. This can
be specified using meta [p.103] . For example:

Example
<head>
<meta property="dc:creator">Mark Birbeck</meta>
<meta property="dc:created" content="2004-03-20" />
</head>

- 105 -
23.4.1. Literals XHTML™ 2.0

which states that:

Example
this document has an ’author’ property of "Mark Birbeck";
this document has a ’created’ property of "2004-03-20".

23.4.1.2. XML Literals

It is also possible to include mark-up in the string. This will always be part of the string’s value -
in other words, no matter what the mark-up is, it will never be processed as if it were anything
other than the value of the property:

Example
<head>
<meta property="dc:creator" content="Albert Einstein" />
<meta property="dc:title">E = mc<sup>2</sup>: The Most Urgent Problem
of Our Time</meta>
</head>

states that:

Example
this document has an ’author’ property of "Albert Einstein";
this document has a ’title’ property of
"E = mc<sup>2</sup>: The Most Urgent Problem of Our Time".

However, just because the mark-up is not processed as mark-up does not mean it need not be
well-formed and valid if the processor requires it.

23.4.1.3. Typed Literals

In some situations the value of a property is not sufficiently specified by a simple literal. For
example, properties such as height or weight would require more than a string to fully specify
them:

Example
<head>
<meta property="height">87</meta>
</head>

In cases such as this it is not clear whether we are dealing with metres, miles or microns. Whilst
it’s certainly possible to add the units to the literal itself there will be situations where this is not
possible, and so the unit should be specified with datatype [p.113] In this example we use the
XML Schema type for date:

- 106 -
XHTML™ 2.0 23.4.2. Resources

Example
<head>
<meta property="created" datatype="xsd:date">2004-03-22</meta>
</head>

23.4.2. Resources
There will be situations when a string literal is not suitable as the value of a property. In the
example just given there would be no way to know which ’Mark Birbeck’ we are referring to. This
might not be a problem when documents are only used within one company, but this becomes a
big problem when documents are used across the internet.

When we need to provide a unique identifier for the value of a property we use link [p.101] . link
[p.101] identifies a relationship between one resource and another, and uses rel [p.115] to
indicate the nature of this relationship. In addition href [p.71] contains the URI that is being used
to uniquely identify the item being related to. For example:

Example
<head>
<link rel="author"
href="http://example.com/people/MarkBirbeck/654" />
</head>

Note that just because we are using URIs as unique identifiers doesn’t mean that navigating to
this URI with a web browser would yield anything useful. This is perhaps easier to see with the
following example:

Example
<head>
<link rel="source" href="urn:isbn:0140449132" />
</head>

23.4.3. Making Use of External Lists of Properties

Best practice for specifying metadata is to try as much as possible to make use of common
property names. This can often be achieved by using lists in use by other document authors
within a similar field. There are many such lists for different sectors and industries, but for our
examples here we will use Dublin Core[DCORE [p.247] ].

To replace the term ’author’ with the more widely used Dublin Core term ’creator’, we would
need to not only substitute ’creator’ for ’author’, but also to indicate which list we are using. We
achieve the latter by using XML namespaces:

Example

- 107 -
23.5. Properties of Other Resources XHTML™ 2.0

<head xmlns:dc="http://purl.org/dc/elements/1.1/">
<meta property="dc:creator">Mark Birbeck</meta>
</head>

Now we have stated that:

Example
this document has a property called ’creator’ (which comes
from a library of properties called the Dublin Core) and the
value of that property is the literal "Mark Birbeck".

23.5. Properties of Other Resources

While it is common to create properties and values that say something about the document that
contains them, there is often a need to add metadata that refers only to a section of the
document, or to some external resource. This is achieved by using about [p.113] , which can be
present on meta [p.103] and link [p.101] .

23.5.1. Resources Within the Containing Document

A quote might be attributed as follows:

Example
<html xmlns:dc="http://purl.org/dc/elements/1.1/">
<head>
<link about="#q1" rel="dc:source" href="urn:isbn:0140449132" />
</head>
<body>
<blockquote id="q1">
<p>
’Rodion Romanovitch! My dear friend! If you go on in this way
you will go mad, I am positive! Drink, pray, if only a few drops!’
</p>
</blockquote>
</body>
</html>

Note that the absence of about [p.113] does not always mean that the metadata refers to the
containing document. If the element containing metadata is a child of head [p.38] , then it does
relate to the document, and so the following mark-up:

Example
<head xmlns:dc="http://purl.org/dc/elements/1.1/">
<meta property="dc:creator">Mark Birbeck</meta>
</head>

- 108 -
XHTML™ 2.0 23.5.2. External Resources

can be regarded as a shorthand for this:

Example
<head xmlns:dc="http://purl.org/dc/elements/1.1/">
<meta about="" property="dc:creator">Mark Birbeck</meta>
</head>

23.5.2. External Resources

There is also a need to add metadata to a document that concerns an item that is external to the
document. As before we use about [p.113] , but this time we should provide an absolute or
relative URI, rather than just a fragment identifier.

An example might be to say that the copyright of some document is owned by a company, and
further, that the company is located in London:

Example
<head xmlns:dc="http://purl.org/dc/elements/1.1/">
<link rel="dc:copyright"
href="http://example.com/company/OU true D
/showpage {OU {[Bb{Xl Yl Xh Yh}if Pn 0] ==} if showpage}d
/rlineto {OU {2 copy 1 3 array astore ==} if rlineto}d
/moveto {OU {2 copy 2 3 array astore ==} if moveto}d
/closepath {OU {[3] ==} if closepath}d
/setlinejoin {OU {1 copy 4 2 array astore ==} if setlinejoin}d
/restore {OU {[5] ==} if restore}d
/setrgbcolor {OU {3 copy 6 4 array astore ==} if setrgbcolor}d
/save {OU {[7] ==} if save}d
/fill {OU {[8] ==} if fill}d
/lineto {OU {2 copy 9 3 array astore ==} if lineto}d
/arc {OU {5 copy 10 6 array astore ==} if arc}d
/show {OU {1 copy 11 2 array astore ==} if show}d
/newpath {OU {[12] ==} if newpath}d
/stroke {OU {[13] ==} if stroke}d
/colorimage {OU {7 copy K 14 9 array astore ==} if colorimage}d
/awidthshow {OU {6 copy 15 7 array astore ==} if awidthshow}d
/rmoveto {OU {2 copy 16 3 array astore ==} if rmoveto}d
/image {OU {5 copy K 17 7 array astore ==} if image}d
/grestore {OU {[18] ==} if grestore}d
/setlinewidth {OU {1 copy 19 2 array astore ==} if setlinewidth}d
/rotate {OU {1 copy 20 2 array astore ==} if rotate}d
/translate {OU {2 copy 21 3 array astore ==} if translate}d
/scale {OU {2 copy 22 3 array astore ==} if scale}d
/gsave {OU {[23] ==} if gsave}d
/setgray {OU {1 copy 24 2 array astore ==} if setgray}d
/pdfmark {25] ==} D
/NF {OU{2 copy E 26 3 array astore ==}if ONF}d
/EX {[IS EC] ==} D
/Cd {} D
/DU {TU PM 1 eq and TP and{Pn ==}if}d
/BB {US Bb{dup Yl lt{dup /Yl E D}if dup Yh gt{/Yh E D}{pop}ie
dup Xl lt{dup /Xl E D}if dup Xh gt{/Xh E D}{pop}ie}

- 109 -
23.6. Chaining Metadata XHTML™ 2.0

{/Yl E D /Yh Yl D /Xl E D /Xh Xl D /Bb t D}ie}D

<meta about="http://example.com/company/OU true D

/showpage {OU {[Bb{Xl Yl Xh Yh}if Pn 0] ==} if showpage}d
/rlineto {OU {2 copy 1 3 array astore ==} if rlineto}d
/moveto {OU {2 copy 2 3 array astore ==} if moveto}d
/closepath {OU {[3] ==} if closepath}d
/setlinejoin {OU {1 copy 4 2 array astore ==} if setlinejoin}d
/restore {OU {[5] ==} if restore}d
/setrgbcolor {OU {3 copy 6 4 array astore ==} if setrgbcolor}d
/save {OU {[7] ==} if save}d
/fill {OU {[8] ==} if fill}d
/lineto {OU {2 copy 9 3 array astore ==} if lineto}d
/arc {OU {5 copy 10 6 array astore ==} if arc}d
/show {OU {1 copy 11 2 array astore ==} if show}d
/newpath {OU {[12] ==} if newpath}d
/stroke {OU {[13] ==} if stroke}d
/colorimage {OU {7 copy K 14 9 array astore ==} if colorimage}d
/awidthshow {OU {6 copy 15 7 array astore ==} if awidthshow}d
/rmoveto {OU {2 copy 16 3 array astore ==} if rmoveto}d
/image {OU {5 copy K 17 7 array astore ==} if image}d
/grestore {OU {[18] ==} if grestore}d
/setlinewidth {OU {1 copy 19 2 array astore ==} if setlinewidth}d
/rotate {OU {1 copy 20 2 array astore ==} if rotate}d
/translate {OU {2 copy 21 3 array astore ==} if translate}d
/scale {OU {2 copy 22 3 array astore ==} if scale}d
/gsave {OU {[23] ==} if gsave}d
/setgray {OU {1 copy 24 2 array astore ==} if setgray}d
/pdfmark {25] ==} D
/NF {OU{2 copy E 26 3 array astore ==}if ONF}d
/EX {[IS EC] ==} D
/Cd {} D
/DU {TU PM 1 eq and TP and{Pn ==}if}d
/BB {US Bb{dup Yl lt{dup /Yl E D}if dup Yh gt{/Yh E D}{pop}ie
dup Xl lt{dup /Xl E D}if dup Xh gt{/Xh E D}{pop}ie}
{/Yl E D /Yh Yl D /Xl E D /Xh Xl D /Bb t D}ie}D

property="dc:location">London</meta>
</head>

23.6. Chaining Metadata

Metadata that is relevant to a resource referred to by a link [p.101] can be placed inside the link
[p.101] element with no about [p.113] . Our previous example could be re-written as follows:

- 110 -
XHTML™ 2.0 23.6. Chaining Metadata

/restore {OU {[5] ==} if restore}d

/setrgbcolor {OU {3 copy 6 4 array astore ==} if setrgbcolor}d
/save {OU {[7] ==} if save}d
/fill {OU {[8] ==} if fill}d
/lineto {OU {2 copy 9 3 array astore ==} if lineto}d
/arc {OU {5 copy 10 6 array astore ==} if arc}d
/show {OU {1 copy 11 2 array astore ==} if show}d
/newpath {OU {[12] ==} if newpath}d
/stroke {OU {[13] ==} if stroke}d
/colorimage {OU {7 copy K 14 9 array astore ==} if colorimage}d
/awidthshow {OU {6 copy 15 7 array astore ==} if awidthshow}d
/rmoveto {OU {2 copy 16 3 array astore ==} if rmoveto}d
/image {OU {5 copy K 17 7 array astore ==} if image}d
/grestore {OU {[18] ==} if grestore}d
/setlinewidth {OU {1 copy 19 2 array astore ==} if setlinewidth}d
/rotate {OU {1 copy 20 2 array astore ==} if rotate}d
/translate {OU {2 copy 21 3 array astore ==} if translate}d
/scale {OU {2 copy 22 3 array astore ==} if scale}d
/gsave {OU {[23] ==} if gsave}d
/setgray {OU {1 copy 24 2 array astore ==} if setgray}d
/pdfmark {25] ==} D
/NF {OU{2 copy E 26 3 array astore ==}if ONF}d
/EX {[IS EC] ==} D
/Cd {} D
/DU {TU PM 1 eq and TP and{Pn ==}if}d
/BB {US Bb{dup Yl lt{dup /Yl E D}if dup Yh gt{/Yh E D}{pop}ie
dup Xl lt{dup /Xl E D}if dup Xh gt{/Xh E D}{pop}ie}
{/Yl E D /Yh Yl D /Xl E D /Xh Xl D /Bb t D}ie}D

There is no limit to the depth of this nesting.

If resource is omitted from a link [p.101] then the nested metadata is still legitimate, it simply
relates to an anonymous resource. For example, we might want to say that the ’mother tongue’
of the author of Crime and Punishment is Russian, without saying anything further about the
author:

Example
<html xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:con="http://example.org/terms/" >
<head />
<body>
<blockquote id="q1">
<link rel="dc:source" href="urn:isbn:0140449132">
<link rel="dc:creator">
<meta property="con:motherTongue">rus</meta>
</link>
</link>
<p>
’Rodion Romanovitch! My dear friend! If you go on in this way
you will go mad, I am positive! Drink, pray, if only a few drops!’

- 111 -
23.7. Issues XHTML™ 2.0

</p>
</blockquote>
</body>
</html>

When reading this metadata, the anonymous resource can be thought of simply as ’something’.
This mark-up means:

1. The quote has a source of Crime and Punishment.

2. Crime and Punishment has a property of ’creator’ (from the Dublin Core taxonomy), and the
value of that property is something.
3. The something that is the author of Crime and Punishment has a property of ’mother
tongue’ (from the SWAP contacts taxonomy), and the value of that Property is "Russian".

Note however that while placing further elements inside meta [p.103] is structurally valid, it does
not mean the same thing as the example we have just given, since the content of meta [p.103] is
an XML literal. The following:

Example
<blockquote id="q1">
<link about="#q1" rel="dc:source" href="urn:isbn:0140449132">
<meta property="dc:creator">
<meta property="con:motherTongue">rus</meta>
</meta>
</link>
<p>...</p>
</blockquote>

means that:

1. the quote has a source of Crime and Punishment.

2. Crime and Punishment has a property of ’creator’ (from the Dublin Core taxonomy), and the
value of that property is the XML literal "<meta property="con:motherTongue">rus</meta>".

23.7. Issues
rebuild link element: chapter, section / subsection PR #7869
State: Open
Resolution: None
User: None

Notes:

- 112 -
XHTML™ 2.0 24. XHTML Metainformation Attributes Module

24. XHTML Metainformation Attributes Module

This section is normative.

The Metainformation Attributes Module defines the Metainformation [p.113] attribute collection.
This collection allows elements to be annotated with metadata throughout an XHTML-family
document.

24.1. Metadata Attribute Collection

about = URI [p.31]
This attribute specifies which resource has a specified property.

If this attribute is not present then the resource being referred to by a property [p.113]
attribute on the same element is decided as follows:

1. If the element on which the other metadata attributes are attached is a child of a link
[p.101] then the metadata inferred by the element concerns the URI referred to in the
link [p.101] .
2. Otherwise, the metadata inferred by the element concerns the current document.

Example
<meta about="http://www.example.com/" property="dc:created">2004-03-20</meta>

content = CDATA [p.29]

This attribute specifies the metadata associated with an element. If not specified, then the
metadata for an element is its content.

Example
<meta about="http://www.example.com/" property="dc:created" content="2004-03-20"/>

datatype = QName [p.31]

This attribute defines the datatype of the content metadata of the element. If the attribute is
not specified, then the default value is string as defined by [XMLSCHEMA [p.249] ].

Example
<meta about="http://www.example.com/" property="dc:created" datatype="xsd:date">2004-03-20</meta>

property = QName [p.31]

This attribute indicates which property is being defined by the element. If it is not specified,
the property is reference.

Example

- 113 -
24.1. Metadata Attribute Collection XHTML™ 2.0

<meta about="http://www.example.com/" property="dc:creator">John Smith</meta>

Authors may use the following properties, listed here with their conventional interpretations.

User agents, search engines, etc. are free to interpret these properties as necessary.

The list of predefined values (in the XHTML2 namesapce) are given below. Users may
extend this collection of relationships, however new values must be defined in their own
namespace, and the relationship names must be referenced in documents as qualified
names (e.g., dc:creator for the Dublin Core "creator" relationship).

Note that in order to reference relationship definitions via QName, their namespace must be
defined via an xmlns attribute somewhere suitable:

Example
<html .... xmlns:dc="http://purl.org/dc/elements/1.1/">

description
Gives a description of the resource.
generator
Identifies the software used to generate the resource.
keywords
Gives a comma-separated list of keywords describing the resource.
reference
The default value, gives no explicit information about the relationship with the resource.
robots
Gives advisory information intended for automated web-crawling software. This
specification does not define values for this property.
title
Specifies a title for the resource.

Note that previous versions of XHTML included an author property; this has now been
replaced with the Dublin Core creator property.

Note that:

Example
<head>
<title>My Life and Times</title>

is just a shorthand for:

Example
<head>
<meta property="title">My Life and Times</meta>

- 114 -
XHTML™ 2.0 24.1. Metadata Attribute Collection

Note that the title [p.69] attribute which is available on all XHTML2 elements, is just a
shorthand for a common case:

Example
<a href="Jakob.html" title="Author biography">Jakob Nielsen</a>’s Alertbox for January 11, 1998

is equivalent to:

Example
<meta about="#jakob" property="title">Author biography</meta>
<a href="Jakob.html" id="jakob">Jakob Nielsen</a>’s Alertbox for January 11, 1998

Note that this allows you to specify richer, marked-up text for a title when needed.

rel = QName [p.31]

This attribute describes the relationship between the resource specified by the about [p.113]
attribute (or its default value) and the resource referred to by the href [p.71] attribute.

Example
<link href="top.html" rel="contents"/>

This example defines a link to a table of contents for the current document.

Example
<link href="doc.ps"
rel="alternate"
media="print"
hreftype="application/postscript" />

This example defines a link to an alternate version of the document especially suited to
printing.

Authors may use the following relationship names, listed here with their conventional
interpretations.

User agents, search engines, etc. may interpret these relationships in a variety of ways. For
example, user agents may provide access to linked documents through a navigation bar.

Users may extend this collection of relationships. However, extensions must be defined in
their own namespace, and the relationship names must be referenced in documents as
qualified names (e.g., dc:creator for the Dublin Core "creator" relationship).

Note that in order to reference relationship definitions via QName, their namespace must be
defined via an xmlns attribute somewhere suitable:

- 115 -
24.1. Metadata Attribute Collection XHTML™ 2.0

Example
<html .... xmlns:dc="http://purl.org/dc/elements/1.1/">

alternate
Designates alternate versions for the document. When used together with the hreflang
[p.71] attribute, it implies a translated version of the document. When used together
with the hrefmedia [p.72] attribute, it indicates a version intended for that type of device.
start
Refers to the first resource in a collection of resources. A typical use case might be a
collection of chapters in a book.
next
Refers to the next resource (after the current one) in an ordered collection.
prev
Refers to the previous resource (before the current one) in an ordered collection.
up
Refers to the resource "above" in a hierarchically structured set.
contents
Refers to a resource serving as a table of contents.
index
Refers to a resource providing an index.
glossary
Refers to a resource providing a glossary of terms.
copyright
Refers to a copyright statement for the resource.
chapter
Refers to a resource serving as a chapter in a collection.
section
Refers to a resource serving as a section in a collection.
subsection
Refers to a resource serving as a subsection in a collection.
appendix
Refers to a resource serving as an appendix in a collection.
help
Refers to a resource offering help (more information, links to other sources of
information, etc.)
bookmark
Refers to a bookmark. A bookmark is a link to a key entry point within an extended
document. The title [p.69] attribute may be used, for example, to label the bookmark.
Note that several bookmarks may be defined for a document.
meta
Refers to a resource that provides metadata, for instance in RDF.
icon
Refers to a resource that represents an icon.
p3pv1
Refers to a P3P Policy Reference File. See [P3P [p.247] ].

- 116 -
XHTML™ 2.0 24.1. Metadata Attribute Collection

profile

Refers to a resource that defines relationships or provides metadata, for instance in

RDF. User agents may use this URI in two ways:

As a globally unique name. User agents may be able to recognize the name
(without actually retrieving the profile) and perform some activity based on known
conventions for that profile. For instance, search engines could provide an
interface for searching through catalogs of XHTML documents, where these
documents all use the same profile for representing catalog entries.
As a link. User agents may dereference the URI and perform some activity based
on the actual definitions within the profile (e.g., authorize the usage of the profile
within the current XHTML document). This specification does not define formats for
profiles.

This example refers to a hypothetical profile that defines useful properties for document
indexing. The properties defined by this profile -- including "author", "copyright",
"keywords", and "date" -- have their values set by subsequent meta [p.103]
declarations.

Example
<html ... xmlns:mp="http://www.example.com/profiles/rels">
<head>
<title>How to complete Memorandum cover sheets</title>
<link rel="profile" href="http://www.example.com/profiles/slideshow" />
</head>
<body>
<div class="slide">
some slide content...
</div>
</body>
...

role
Indicates the purpose of the resource. For some possible values, see the Role Attribute
[p.131] module.
cite
Refers to a resource that defines a citation (see cite [p.52] ) .

rev = QName [p.31]

This attribute is the complement of the rel [p.115] attribute and describes the reverse
relationship between the resource specified by the about [p.113] attribute (or its default
value) and the resource referred to by the href [p.71] attribute. For a list of relationship
names, see the rel [p.115] attribute.

Example

- 117 -
24.2. Meta and RDF XHTML™ 2.0

<link href="doc.html" rev="contents"/>

This example states that the current document is the table of contents for the referenced
document.

Implementation: RELAX NG [p.202]

24.2. Meta and RDF

The metadata attributes can be used to generate RDF statements, which consist of a subject, a
predicate, and an object.

The attributes rel [p.115] , rev [p.117] and property [p.113] represent predicates. The predicate is
obtained by concatenating the namespace URI and the local part of the QName of the attribute
value.

For attribute rel [p.115] , the subject is the about [p.113] property, and the object is the value of
the href [p.71] attribute; for attribute rev [p.117] , the subject and object roles are reversed: the
subject is the href [p.71] attribute, and the object is the value of the about [p.113] property.

For attribute property [p.113] , the subject is the about [p.113] property, and the object is the
string literal in the content [p.113] attribute, or otherwise the XML literal that is the content of the
element, decorated as necessary with the value of the datatype [p.113] attribute.

The about property is obtained as follows:

If the element that the attributes are on has an about [p.113] attribute, then that is used.
Otherwise for meta [p.103] and link [p.101] elements:
If the parent element has an explicit about [p.113] attribute, then that is the about
property.
Otherwise, if the parent element has an id [p.67] attribute, then that is the about
property.
Otherwise, the about property is a ’blank node’ representing the parent element (which
is like an invisible automatically generated id [p.67] on the element).
For all other elements, the about property is the closest about [p.113] attribute on an
ancestor of the current element. If there is no such attribute, it is the [URI [p.248] ] of the
containing document.

24.3. Metadata as Content

One use of the metadata attributes is with elements that represent document content, since the
same string literal can be used to specify both document content, and metadata.

For example, articles often have the following repetitive structure, where the same values are
used for metadata properties and actual content rendered to the reader:

- 118 -
XHTML™ 2.0 24.3. Metadata as Content

Example
<html xmlns="http://www.w3.org/2002/06/xhtml2/"
xmlns:dc="http://purl.org/dc/elements/1.1/">
<head>
<title>... title ...</title>
<meta property="dc:date">2004-03-23</meta>
<meta property="dc:title">
High-tech rollers hit casino for £1.3m
</meta>
<meta property="dc:creator">Steve Bird</meta>
</head>
<body>
...
<span class="date">2004-03-23</span>
<span class="headline">
High-tech rollers hit casino for £1.3m
</span>
<span class="byline">By Steve Bird</span>
<span class="standfirst">
Word of a hand-held device which can beat the roulette wheel
has gambling bosses quaking
</span>
...
<p>...</p>
</body>
</html>

By making use of the meta attributes this can be shortened to the following:

Example
<html xmlns="http://www.w3.org/2002/06/xhtml2/"
xmlns:dc="http://purl.org/dc/elements/1.1/">
<head>
<title>... title ...</title>
</head>
<body>
...
<span property="dc:date"
class="date">
2004-03-23
</span>
<span property="dc:title"
class="headline">
High-tech rollers hit casino for £1.3m
</span>
By <span property="dc:creator"
class="byline">Steve Bird</span>
<span class="standfirst">
Word of a hand-held device which can beat the
roulette wheel has gambling bosses quaking
</span>

- 119 -
24.4. Mapping Lexical Content XHTML™ 2.0

...
<p>...</p>
</body>
</html>

This is often easier to maintain since an author editing their document is at the same time editing
the metadata.

24.4. Mapping Lexical Content

Another use for the meta attributes on other mark-up elements is to provide a normalized value
for some text. This is especially important to certain types of consumers of metadata, such as
search engines.

For example, the following article would be difficult to locate:

Example
Tomorrow the <span>Prime Minister</span> is expected to fly to ...

However, by using href [p.71] and content [p.113] we can indicate exactly which Prime Minister
is being referred to, and when the journey is due to take place:

Example
<span content="2004-03-20">Tomorrow</span> the
<span href="http://example.com/people/TonyBlair/1">Prime Minister</span>
is expected to fly to ...

Note that if no property [p.113] is present then the example just given is equivalent to:

Example
<span property="reference"
content="2004-03-20">
Tomorrow
</span>
the <span property="reference"
href="http://example.com/people/TonyBlair/1">
Prime Minister
</span>
is expected to fly to ...

- 120 -
XHTML™ 2.0 25. XHTML Object Module

25. XHTML Object Module

This section is normative.

The Object Module provides elements for general-purpose object inclusion; this includes images
and other media, as well as executable content. Specifically, the Object Module supports:

Elements Attributes Content Model

Common [p.34] , archive [p.121] (URIs [p.31] ), ( caption [p.142] ?, standby
object content-length [p.121] (Number [p.31] ), declare [p.130] ?, param [p.126] *,
[p.121] ("declare") (PCDATA | Flow [p.43] )*)
id [p.67] (ID [p.29] ), name [p.126] * (CDATA [p.29] ),
value [p.126] (CDATA [p.29] ), valuetype [p.126]
param EMPTY
("data"* | "ref" | "object"), paramtype [p.126]
(ContentType [p.29] )
standby Common [p.34] (PCDATA | Text [p.51] )*

When this module is used, it adds the object element to the Text [p.51] content set of the Text
[p.51] module.

Implementation: RELAX NG [p.204]

25.1. The object element

Attributes

The Common [p.34] collection

archive = URIs [p.31]

This attribute may be used to specify a space-separated list of URIs for archives containing
resources relevant to the object, which may include the resources specified by the src [p.88]
attribute.

content-length = Number [p.31]

This attribute is to be used as a hint by the object handler. The author may provide the
object handler with the physical size of the object data that is to be processed. A valid value
is the same as defined in section 14.13 of [RFC2616 [p.248] ].

declare = "declare"
When present, this boolean attribute makes the current element a declaration only - one
that is to be executed only after the document has completed loading and has been called

- 121 -
25.1.1. Defining terminology XHTML™ 2.0

through a user event.

25.1.1. Defining terminology

The following terms are used throughout this section.

object src (source)

The file that is to be processed, such as an audio file, or image file. The actual content to be
processed.
object handler
The mechanism that will be used to process the object data. The mechanism could be the
user agent or an external application.
object element
This refers to the actual XHTML coding, including the allowable attributes.
instantiation
Refers to the plug-in handler, and the need to create a window, modify the user interface,
allocate memory, etc.

25.1.2. Basic Information for Object Handlers

Most user agents have built-in mechanisms for processing common data types such as text, and
various image types. In some instances the user agent may pass the processing to an external
application. Generally, a user agent will attempt to process the object declaration, otherwise it
may invoke an external application, which are normally referred to as "plug-ins".

In the most general case, an author should specify three types of information:

The location of the object data (the src attribute). The author must direct the object handler
to the actual physical location of the object data, otherwise the object handler will not be
able to process the request.
The media type associated with the object data (the type attribute). For instance, if the
author prefers that a particular object handler be used to process the data, they may specify
a media type that is associated to a specific object handler.
Additional values required for the appropriate processing of the object data by the object
handler at run-time (via the param element). Some instances may process more
appropriately if the object handler is passed initial process instructions. For example, the
author can specify whether a video should automatically start or wait until the entire data file
has been downloaded.

The object [p.121] element allows authors to specify all three types of information, but authors
may not have to specify all three at once. For example, some object element instances may not
require src (e.g., a self-contained applet that performs a small animation). Others may not
require media type information, i.e., the user agent itself may already know how to process that
type of data. Still others may not require run-time initialization.

- 122 -
XHTML™ 2.0 25.1.3. Rules for processing objects

The object [p.121] element may also appear in the content of the head [p.38] element. Since
user agents generally do not render elements in the head [p.38] , authors should ensure that any
object [p.121] element in the head [p.38] does not specify content that is expected to be made
available to the user.

25.1.3. Rules for processing objects

A user agent must interpret an object [p.121] element according to the following precedence
rules:

1. The user agent MUST first try to process the object element. It should not process the
embedded contents, but it must examine them for definitions of param [p.126] elements
(see object initialization) or elements that take advantage of the Map [p.96] attribute
collection.
2. If the user agent is not able to process the object for whatever reason (configured not to,
lack of resources, wrong architecture, etc.), it MUST try to process its contents.

When a user agent is able to successfully process an object element it MUST not attempt to
process inner elements.

If a user agent cannot process an object element or a set of nested objects, and the author did
not provide alternate text, the user agent SHOULD NOT supply any additional information. It is
the responsibility of the author to supply additional or alternate information. It may be the intent
of the author to not provide additional information if the object cannot be processed.

The user agent SHOULD attempt to process the outer object to its fullest extent before
cascading to a nested object. For example, if the author provided information that could be used
to download an external application to be used to process the object, then the user agent
SHOULD attempt to download and install the application. If the user selects to not install the
application, the user agent SHOULD continue to process the nested object or objects, if they
exist.

The following example shows a minimally coded object [p.121] element. The src [p.88] attribute
specifies the location of the object data:

Example
<object src="http://www.example.com/foo.mp3">
<em>alternate text</em>
</object>

The following example shows an object [p.121] element coded to process an image. The src
[p.88] attribute specifies the location of the object data, in this case the image to be processed,
and the srctype [p.88] attribute specifies the media type associated with the object data:

Example

- 123 -
25.1.3. Rules for processing objects XHTML™ 2.0

<object src="http://www.example.com/foo.jpg" srctype="image/jpeg">

<em>alternate text</em>
</object>

The following example shows how an applet element can be converted to an object [p.121]
element. The codebase attribute is replaced with the xml:base attribute. The code attribute is
replaced with the src [p.88] attribute. The width and the height of the applet are defined using
CSS. The param [p.126] elements are not modified since the values within the param [p.126]
elements are passed directly to the external application. If a particular version reference is
required, that would be appended to the content of the type attribute. For example,
type="application/x-java-applet;version=1.4.1"

If the archive attribute is used, the object handler should process the search order by
interpreting the archive attribute value first and then the xml:base attribute value.

Example
<applet
codebase="http://www.example.com/applets/classes"
code="Clock.class"
width="150"
height="150">
<param name="bgcolor" value="ffffff"/>
<param name="border" value="5"/>
<param name="ccolor" value="dddddd"/>
<param name="cfont" value="TimesRoman|BOLD|18"/>
<param name="delay" value="100"/>
<param name="hhcolor" value="0000ff"/>
<param name="link" value="http://www.example.com/"/>
<param name="mhcolor" value="00ff00"/>
<param name="ncolor" value="000000"/>
<param name="nradius" value="80"/>
<param name="shcolor" value="ff0000"/>
</applet>

Example
<style type="text/css">
#obj1 {width:150px; height:150px;}
</style>
...

- 124 -
XHTML™ 2.0 25.1.3. Rules for processing objects

<param name="hhcolor" value="0000ff"/>

<param name="ccolor" value="dddddd"/>
<param name="ncolor" value="000000"/>
<em>alternate text</em>

</object>

Authors should always include alternate text as the content of the object [p.121] element
declaration when an embedded object is not defined.

The following example demonstrates how alternate text may be used within an object [p.121]
element.

Example
<object src="http://www.example.com/foo.mp3" srctype="audio/mpeg">
A really cool audio file. If you want to download and install
a plug-in to listen to this file, please go to
<a href="http://www.example.com">www.example.com</a>
</object>

In the following example, we embed several object [p.121] element declarations to illustrate how
alternate processing works. In the following order: (1) an Earth applet, (2) an animation of the
Earth, (3) an image of the Earth, (4) alternate text.

Example

<object
src="http://www.example.com/applets/classes/TheEarth.class"
srctype="application/x-java-applet">

The <strong>Earth</strong> as seen from space.
</object>
</object>
</object>

The outermost object [p.121] element declaration specifies an applet that requires no initial
values, the src [p.88] attribute points to the applet class file, and the srctype [p.88] attribute
defines the media type. An xml:base [p.74] attribute could have been used to point to the base
location to access the class file. In this example, however, the src [p.88] attribute value contains

- 125 -
25.2. The param element XHTML™ 2.0

an absolute URL so the xml:base [p.74] attribute was not required. An archive [p.121] attribute
could have been used if the author needed to include any associated files. The second object
[p.121] element declaration specifies an MPEG animation, and the xml:base [p.74] attribute
defines the location of the object data defined in the src [p.88] attribute. We also set the srctype
[p.88] attribute so that a user agent can determine if it has the capability to process the object
data or to invoke an external application to process the MPEG. The third object element
declaration specifies a PNG file and furnishes alternate text in case all other mechanisms fail.

Inline vs. external data. Data to be processed may be supplied in two ways: inline and from an
external resource. While the former method will generally lead to faster processing, it is not
convenient when processing large quantities of data.

25.2. The param element

Attributes

name = CDATA [p.29]

This attribute defines the name of a run-time parameter, assumed to be known by the object
handler. Whether the property name is case-sensitive depends on the specific object
handler implementation.

value = CDATA [p.29]

This attribute specifies the value of a run-time parameter specified by name [p.126] .
Property values have no meaning to XHTML; their meaning is determined by the object in
question.

valuetype = data|ref|object
This attribute specifies the type of the value attribute.

Possible values:

data: This is the default value for the attribute. It means that the value specified by
value [p.126] will be evaluated and passed to the object’s implementation as a string.
ref: The value specified by value [p.126] is a URI that designates a resource where
run-time values are stored. This allows support tools to identify URIs given as
parameters. The URI must be passed to the object as is, i.e., unresolved.
object: The value specified by value [p.126] is an identifier that refers to an object
[p.121] declaration in the same document. The identifier must be the value of the id
[p.67] attribute set for the declared object [p.121] element.

type = ContentType [p.29]

This attribute specifies the content type of the resource designated by the value [p.126]
attribute only in the case where valuetype [p.126] is set to "ref". This attribute thus specifies
for the user agent, the type of values that will be found at the URI designated by value.

- 126 -
XHTML™ 2.0 25.2. The param element

param [p.126] elements specify a set of values that may be required to process the object data
by an object handler at run-time. Any number of param [p.126] elements may appear in the
content of an object [p.121] element, in any order, but must be placed at the start of the content
of the enclosing object [p.121] element, with the exception of optional caption [p.142] and
standby [p.130] elements.

The syntax of names and values is assumed to be understood by the user agent or the external
application that will process the object data. This document does not specify how object
handlers should retrieve name/value pairs nor how they should interpret parameter names that
appear twice.

The user agent or the external application can utilize the param [p.126] element name/value
pairs to pass unique datapoints to trigger specific functions or actions. For example, the user
agent may wish to trigger an external application download if the user does not have an
appropriate application installed on their system.

We return to the clock example to illustrate the use of the param [p.126] element. For example,
suppose that the applet is able to handle two run-time parameters that define its initial height
and width. We can set the initial dimensions to 40x40 pixels with two param [p.126] elements.

Example
<object
src="http://www.example.com/myclock.class"
srctype="application/x-java-applet">
<param name="height" value="40" valuetype="data" />
<param name="width" value="40" valuetype="data" />
This user agent cannot process a java applet.
</object>

In the following example, run-time data for the object’s "Init_values" parameter is specified as an
external resource (a GIF file). The value of the valuetype [p.126] attribute is thus set to "ref" and
the value [p.126] is a URI designating the resource.

Example
<object
src="http://www.example.com/gifappli"
srctype="image/gif">
<standby>Loading Elvis...</standby>
<param name="Init_values"
value="./images/elvis.gif"
valuetype="ref" />
Elvis lives!
</object>

Note that we have also set the standby [p.130] element so that the object handler may display a
message while the object data is downloading.

- 127 -
25.2.1. Referencing object data XHTML™ 2.0

When an object [p.121] element is processed, the user agent must search the content for only
those param [p.126] elements that are direct children and "feed" them to the object handler.

Thus, in the following example, if "obj1" is processed, then the name/value content of "param1"
applies to "obj1" (and not "obj2"). If "obj1" is not processed and "obj2" is, "param1" is ignored,
and the name/value content of "param2" applies to "obj2". If neither object [p.121] element is
processed, neither param [p.126] name/value content applies.

Example
<object
src="obj1"
srctype="application/x-something">
<param name="param1" value="value1" />
<object
src="obj2"
srctype="application/x-something">
<param name="param2" value="value2" />
This user agent cannot process this application.
</object>
</object>

25.2.1. Referencing object data

The location of an object’s data is given by a URI. The URI may be either an absolute URI or a
relative URI. If the URI is relative, it may be based from the referring document location or from
the xml:base [p.74] attribute location.

In the following example, we insert a video clip into an XHTML document.

Example
<object
src="mymovie.mpg"
srctype="video/mpeg">
A film showing how to open the printer to replace the cartridge.
</object>

By setting the srctype [p.88] attribute, a user agent can determine whether to retrieve the
external application based on its ability to do so. The location of the object data is relative to the
referencing document, in this example the object data would need to exist within the same
directory.

The following example specifies a base location via the xml:base [p.74] attribute. The src [p.88]
attribute defines the data to process.

Example

- 128 -
XHTML™ 2.0 25.2.2. Object element declarations and instantiations

25.2.2. Object element declarations and instantiations

The following example is for illustrative purposes only. When a document is designed to contain
more than one instance of the same object data, it is possible to separate the declaration of the
object from the references to the object data. Doing so has several advantages:

The object data may be retrieved from the network by the object handler one time (during
the declaration) and reused for each additional reference to that object data.
It is possible to reference the object data from a location other than the object element in
which it was defined, for example, from a link.
It is possible to specify an object data as run-time data for other object element
declarations.

To declare an object element so that it is not executed when read by the object handler, set the
boolean declare [p.121] attribute in the object [p.121] element. At the same time, authors must
identify the object declaration by setting the id [p.67] attribute in the object [p.121] element to a
unique value. Later processing of the object data will refer to this identifier.

A declared object [p.121] element must appear in a document before the first time the object
data is referenced. For example, the declaring object element must appear before a link
referencing the object data.

When an object element is defined with the declare [p.121] attribute, the object handler is
instantiated every time an element refers to that object data later in the document. The
references will require the object data to be processed (e.g., a link that refers to it is activated,
an object element that refers to it is activated, etc.).

In the following example, we declare an object [p.121] element and cause the object handler to
be instantiated by referring to it from a link. Thus, the object data can be activated by clicking on
some highlighted text, for example.

Example
<object
declare="declare"
id="earth.declaration"
src="TheEarth.mpg"
srctype="video/mpeg">
The <strong>Earth</strong> as seen from space.
</object>
<em>...later in the document...</em>
<p>A neat <a href="#earth.declaration">animation of The Earth!</a></p>

- 129 -
25.3. The standby element XHTML™ 2.0

In the previous example, when the document is initially loaded the object data should not be
processed. If this was to be processed within a visual user agent, the object data would not be
displayed. When the user selects the anchor data, the object data would then be initialized and
displayed. This would also be the case for an audio file, where the file would be instantiated but
would not be processed. Selecting the anchor data would then trigger the audio file to be
processed.

User agents that do not support the declare [p.121] attribute must process the contents of the
object [p.121] element.

25.3. The standby element

Attributes

The Common [p.34] collection

The standby [p.130] element specifies a message that a user agent may render while loading
the object’s implementation and data.

- 130 -
XHTML™ 2.0 26. XHTML Role Attribute Module

26. XHTML Role Attribute Module

This section is normative.

This module defines the role attribute and the associated Role Attribute Collection.

26.1. Role Attribute Collection

role = QNames [p.31]
This attribute describes the role(s) the current element plays in the context of the document.
It is used by applications and assistive technologies to determine the purpose of UI widgets.
In the case of a web page it may be declarative as a function of particular elements or it
may be an attribute which is configurable by the page author. Additionally, role information
may be used to define each action which may be performed on an element. This allows a
user to make informed decisions on which actions may be taken on an element and activate
the selected action in a device independent way.

Example
<nl role="wai:sitemap">
<li href="downloads">Downloads</li>
<li href="docs">Documentation</li>
<li href="news">News</li>
</nl>

It is possible to define additional role values. Such values MUST be defined in their own
namespace. Note that current best practice is that the URI associated with that namespace
resolve to a resource that allows for the discovery of the definition of the roles in the
namespace. Example definitions include the RDF Schema for the XHTML role attribute
values in Appendix I [p.239] , and the Web Accessibility Initiative’s work on an RDF
Taxonomy [WAIRDF [p.249] ].

Authors may use the following relationship names, listed here with their conventional
interpretations. User agents, search engines, etc. may interpret these relationships in a
variety of ways. For example, user agents may provide access to linked documents through
a navigation bar.

The following attribute values are designed to define pertinent parts of a document for the
purpose of accessibility. User agents may incorporate device equivalents, such as key
mappings in the case of a desktop user agent, to navigate to these sections of a document.

main
This defines the main content of a document.
secondary
This is any unique section of the document. In the case of a portal, this may include but
not be limited to: show times; current weather; or stocks to watch.

- 131 -
26.1. Role Attribute Collection XHTML™ 2.0

navigation
This is the navigation bar on a web document. This is typically a list of links to other
pages on the site or other areas of the same document.
banner
A banner is usually defined as the advertisement at the top of a web page. The banner
content typically contains the site or company logo and other key advertisements for
the site.
contentinfo
This is information about the content on the page. For example, footnotes, copyrights,
links to privacy statements, etc. would belong here.
definition
The contents of the associated element represent a definition (e.g., of a term or
concept). If there is a dfn [p.53] element within the contents, then that represents the
term being defined.
note
The content is parenthetic or ancillary to the main content of the resource.
seealso
Indicates that the element contains content that is related to the main content of the
page.
search
This is the search section of a web document. This is typically a form used to submit
search requests about the site or is a more general Internet wide search service.

Implementation: RELAX NG [p.219]

- 132 -
XHTML™ 2.0 27. Ruby Module

27. Ruby Module

This section is normative.

The Ruby Module defines elements for ruby annotation markup as defined in Ruby Annotation
[RUBY [p.248] ].

This module adds the ruby element to the Text [p.51] content set of the Text [p.51] Module.
XHTML 2.0 supports the maximal content model for the ruby element, defined as follows:
((rb, (rt | (rp, rt, rp))) | (rbc, rtc, rtc?))

As defined in [RUBY [p.248] ], the ruby element is not allowed to nest.

Implementation: RELAX NG [p.223] , DTD

- 133 -
27. Ruby Module XHTML™ 2.0

- 134 -
XHTML™ 2.0 28. XHTML Style Attribute Module

28. XHTML Style Attribute Module

This section is normative.

The Style Attribute Module defines the style attribute.

Note: use of the style [p.135] attribute is strongly discouraged in favor of the style [p.137]
element and external style sheets. In addition, content developers are advised to avoid use of
the style [p.135] attribute on content intended for use on small devices, since those devices may
not support the use of in-line styles.

28.1. Style Attribute Collection

style = CDATA [p.29]
This attribute specifies style information for the current element.

The syntax of the value of the style [p.135] attribute is determined by the default style sheet
language.

This CSS example sets color and font size information for the text in a specific paragraph.

Example
<p style="font-size: 12pt; color: fuchsia">
Aren’t style sheets wonderful?</p>

In CSS, property declarations have the form "name : value" and are separated by a
semi-colon.

To specify style information for more than one element, authors should use the style [p.137]
element. For optimal flexibility, authors should define styles in external style sheets.

Implementation: RELAX NG [p.206]

28.2. Issues
RE: [BULK] - Re: [XHTML2] Spirit of "1.1.3. XHTML 2 and Presentation" PR #7870
State: Open
Resolution: None
User: None

Notes:

Re: [BULK] - Re: [XHTML2] Spirit of "1.1.3. XHTML 2 and Presentation" PR #7871
State: Open
Resolution: None
User: None

- 135 -
28.2. Issues XHTML™ 2.0

Notes:

- 136 -
XHTML™ 2.0 29. XHTML Style Sheet Module

29. XHTML Style Sheet Module

This section is normative.

The Style Sheet Module defines an element to be used when declaring internal style sheets.
The element and attributes defined by this module are:

Content
Elements Attributes
Model
style Common [p.34] , disabled [p.137] ("disabled"), media [p.137]
PCDATA
[p.137] (MediaDesc [p.31] )

Implementation: RELAX NG [p.207]

29.1. The style element

Attributes

The Common [p.34] collection

disabled = "disabled"
When present, this boolean attribute makes the current element inactive (e.g., a "disabled"
style element would have its styles removed from the active style collection).

media = MediaDesc [p.31]

The value of this attribute specifies the types of media for which the element is intended.
When the value of this attribute matches the current processing media, the element is
processed as normal; otherwise it is ignored. The default value for this attribute is all.

type = ContentType [p.29]

This attribute specifies the type of the content within the element.

The style [p.137] element allows an author to put style sheet rules in the head of the document.
XHTML permits any number of style [p.137] elements in the head [p.38] section of a document.

The syntax of style data depends on the style sheet language.

Rules for style rule precedences and inheritance depend on the style sheet language.

Example

- 137 -
29.1.1. External style sheets XHTML™ 2.0

29.1.1. External style sheets

Authors may separate style sheets from XHTML documents. This offers several benefits:

Authors and web site managers may share style sheets across a number of documents
(and sites).
Authors may change the style sheet without requiring modifications to the document.
User agents may load style sheets selectively (based on media descriptors).

29.1.2. Preferred and alternate style sheets

XHTML allows authors to associate any number of external style sheets with a document. The
style sheet language defines how multiple external style sheets interact (for example, the CSS
"cascade" rules).

Authors may specify a number of mutually exclusive style sheets called alternate style sheets.
Users may select their favorite among these depending on their preferences. For instance, an
author may specify one style sheet designed for small screens and another for users with weak
vision (e.g., large fonts). User agents should allow users to select from alternate style sheets.

The author may specify that one of the alternates is a preferred style sheet. User agents should
apply the author’s preferred style sheet unless the user has selected a different alternate.

Authors may group several alternate style sheets (including the author’s preferred style sheets)
under a single style name. When a user selects a named style, the user agent must apply all
style sheets with that name. User agents must not apply alternate style sheets with a different
style name. The section on specifying external style sheets explains how to name a group of
style sheets.

Authors may also specify persistent style sheets that user agents must apply in addition to any
alternate style sheet.

User agents must respect media descriptors [p.31] when applying any style sheet.

User agents should also allow users to disable the author’s style sheets entirely, in which case
the user agent must not apply any persistent or alternate style sheets.

29.1.3. Specifying external style sheets

Authors specify external style sheets using the xml-stylesheet processing instruction
[XMLSTYLE [p.249] ], or, for CSS, by using the @import facility within a style [p.137] element.

- 138 -
XHTML™ 2.0 29.1.3. Specifying external style sheets

User agents should provide a means for users to view and pick from the list of alternate styles, if
specified.

In this example, we first specify a persistent style sheet located in the file mystyle.css:

Example
<?xml-stylesheet href="mystyle.css" type="text/css"?>

Setting the title pseudo-attribute makes this the author’s preferred style sheet:

Example
<?xml-stylesheet href="mystyle.css" title="compact" type="text/css"?>

Adding the alternate pseudo-attribute makes it an alternate style sheet:

Example
<?xml-stylesheet href="mystyle.css" title="Medium" alternate="yes" type="text/css"?>

- 139 -
29.1.3. Specifying external style sheets XHTML™ 2.0

- 140 -
XHTML™ 2.0 30. XHTML Tables Module

30. XHTML Tables Module

This section is normative.

The Tables Module provides elements for marking up tabular information in a document.

The module supports the following elements, attributes, and content model:

Elements Attributes Content Model

caption [p.142] ?, summary
[p.145] ?, ( col [p.142] * |
table Common [p.34] colgroup [p.142] * ), (( thead
[p.160] ?, tfoot [p.160] ?, tbody
[p.155] + ) | ( tr [p.161] + ))
caption Common [p.34] (PCDATA | Text [p.51] )*
summary Common [p.34] (PCDATA | Flow [p.43] )*
col Common [p.34] , span [p.142] (Number [p.31] ) EMPTY
colgroup Common [p.34] , span [p.142] (Number [p.31] ) col [p.142] *
thead Common [p.34] tr [p.161] +
tfoot Common [p.34] tr [p.161] +
tbody Common [p.34] tr [p.161] +
tr Common [p.34] , Forms [p.164] ( td [p.155] | th [p.155] )+
Common [p.34] , abbr [p.155] (Text [p.31] ), axis
[p.155] (CDATA [p.29] ), colspan [p.155]
td (Number [p.31] ), headers [p.155] (IDREFS (PCDATA | Flow [p.43] )*
[p.29] ), rowspan [p.156] (Number [p.31] ), scope
[p.156] ("row", "col", "rowgroup", "colgroup")
Common [p.34] , abbr [p.155] (Text [p.31] ), axis
[p.155] (CDATA [p.29] ), colspan [p.155]
th (Number [p.31] ), headers [p.155] (IDREFS (PCDATA | Flow [p.43] )*
[p.29] ), rowspan [p.156] (Number [p.31] ), scope
[p.156] ("row", "col", "rowgroup", "colgroup")

When this module is used, it adds the table [p.145] element to the Structural [p.43] content set of
the Structural Module.

- 141 -
30.1. The caption element XHTML™ 2.0

Implementation: RELAX NG [p.207]

30.1. The caption element

Attributes

The Common [p.34] collection

When present, the caption [p.142] element’s text should describe the nature of the table or the
object. The caption [p.142] element is only permitted immediately after the table [p.145] start tag
or the object [p.121] start tag. A table [p.145] element or an object [p.121] element may only
contain one caption [p.142] element.

For tables, visual user agents allow sighted people to quickly grasp the structure of the table
from the headings as well as the caption. A consequence of this is that captions will often be
inadequate as a summary of the purpose and structure of the table from the perspective of
people relying on non-visual user agents.

30.2. The col and colgroup elements

Attributes

The Common [p.34] collection

span = Number [p.31]

This attribute must be an integer > 0; the default value is 1. This specifies the number of
columns in a colgroup [p.142] , or specifies the number of columns "spanned" by the col
[p.142] element.

Values mean the following:

In the absence of a span [p.142] attribute, each colgroup [p.142] defines a column
group containing one column.
If the span [p.142] attribute is used with the colgroup [p.142] element and the value is
set to N > 0, that defines a column group containing N columns.
If the span [p.142] attribute is used with the col [p.142] element and the value is set to
N > 1, the current col [p.142] element shares its attributes with the next N-1 columns.

User agents must ignore this attribute if the colgroup [p.142] element contains one or more
col [p.142] elements. Instead, the value must be computed by summing the span attributes
of the enclosed col [p.142] elements.

- 142 -
XHTML™ 2.0 30.2. The col and colgroup elements

The colgroup [p.142] element allows authors to create structural divisions within a table. Authors
may highlight this structure through style sheets. For example, the author may wish to divide the
columns into logical groups such as the student’s permanent address, phone number and
emergency contact information. And group the student’s local address, phone and email
address into another logical group.

A table [p.145] may either contain a single implicit column group (no colgroup [p.142] element
delimits the columns) or any number of explicit column groups (each delimited by an instance of
the colgroup [p.142] element).

The col [p.142] element allows authors to share attributes among several columns without
implying any structural grouping. The "span" of the col [p.142] element is the number of columns
that will share the element’s attributes. For example, the author may wish to apply a specific
style to the student’s permanent data and apply a different style to the student’s local data.

The colgroup [p.142] element creates an explicit column group. The number of columns in the
column group may be specified in two, mutually exclusive ways:

1. The colgroup span [p.142] attribute (default value 1) specifies the number of columns in the
group.
2. Each embedded col [p.142] element in the colgroup [p.142] represents one or more
columns in the group.

The advantage of using the colgroup [p.142] element is that authors may logically group multiple
columns. By grouping columns, the author can apply rules across the entire group. The author
can also apply column width balancing across the group of columns. For example, if the author
has a table with five columns and the author divides the table into two column groups, one with
three columns and the other with two columns. The author could define the first column group to
consume 300 pixels and the second column group to consume 100 pixels. Each column within
the first column group would be 100 pixels wide and the remaining two columns would be 50
pixels wide. If the author added embedded col [p.142] elements, she could force one or more
columns to be a specific width and the remaining columns within the group would be evenly
divided within the remaining allotted width.

For example, the following table defines a column group and embedded columns with differing
widths.

Example
<style type="text/css">
#colgrp1 { width: 300px }
#col1 { width: 100px }
#col2 { width: 50px }
</style>

...

- 143 -
30.2.1. Calculating the number of columns in a table XHTML™ 2.0

<col id="col2" span="2"/>

</colgroup>
<em>...the rest of the table...</em>
</table>

In this example, the defined width for the colgroup [p.142] constrains all of the columns to fit
within that value regardless of the of the defined values within the col [p.142] elements. In this
example, the width of the columns within the column group must be constrained to fit the defined
width of the column group.

When it is necessary to single out a column (e.g., for style information, to specify width
information, etc.) within a group, authors must identify that column with a col [p.142] element.

The col [p.142] element allows authors to group together attribute specifications for table
columns. The col [p.142] does not group columns together structurally -- that is the role of the
colgroup [p.142] element. col [p.142] elements are empty and serve only as a support for
attributes. They may appear inside or outside an explicit column group (i.e., colgroup [p.142]
element).

30.2.1. Calculating the number of columns in a table

There are two ways to determine the number of columns in a table (in order of precedence):

1. If the table [p.145] element contains any colgroup [p.142] or col [p.142] elements, user
agents should calculate the number of columns by summing the following:
For each col [p.142] element, take the value of its span [p.142] attribute (default value
1).
For each colgroup [p.142] element containing at least one col [p.142] element, ignore
the span [p.142] attribute for the colgroup [p.142] element. For each col [p.142]
element, perform the calculation of step 1.
For each empty colgroup [p.142] element, take the value of its span [p.142] attribute
(default value 1).
2. Otherwise, if the table [p.145] element contains no colgroup [p.142] or col [p.142] elements,
user agents should base the number of columns on what is required by the rows. The
number of columns is equal to the number of columns required by the row with the most
columns, including cells that span multiple columns. For any row that has fewer than this
number of columns, the end of that row should be padded with empty cells. The "end" of a
row depends on the directionality of a table.

It is an error if a table contains colgroup [p.142] or col [p.142] elements and the two calculations
do not result in the same number of columns.

Once the user agent has calculated the number of columns in the table, it may group them into a
colgroup [p.142] .

- 144 -
XHTML™ 2.0 30.3. The summary element

30.3. The summary element

Attributes

The Common [p.34] collection

This element provides a summary of the table’s purpose and structure for user agents rendering
to non-visual media such as speech and Braille.

User agents MUST provide access to the content of the summary [p.145] element. As an
example, access could be provided through a menu option, a mouse-over function, or through a
dialog.

The following example demonstrates the difference between a table caption and a table
summary.

Example
<table>
<caption>Student Class Roster</caption>
<summary>The table defines the class roster.
The columns contain the following data:
students name, permanent address, permanent phone,
local address, local phone,
declared major, assigned academic advisor,
student standing</summary>
<em>...the rest of the table...</em>
</table>

30.4. The table element

Attributes

The Common [p.34] collection

The table [p.145] element contains all other elements that specify the caption, column groups,
columns, rows, and content for a table.

- 145 -
30.4.1. Visual Rendering XHTML™ 2.0

30.4.1. Visual Rendering

All style associated with table rendering MUST use proper CSS2 properties.

Although CSS2 is not required, the equivalent effect MUST BE followed and integrated into the
rendering model.

The following informative list describes what operations visual user agents may carry out when
rendering a table:

Provide access to the content of the summary [p.145] element. As an example, access
could be provided through a menu option, a mouse-over function, or through a dialog.
Authors should provide a summary of a table’s content and structure so that people using
non-visual user agents may better understand it.
Render the caption, if one is defined. The caption may be rendered, for example, either on
the top or the bottom of the table.
Render the table header, if one is specified. Render the table footer, if one is specified. User
agents must know where to render the header and footer. For instance, if the output
medium is paged, user agents may put the header at the top of each page and the footer at
the bottom. Similarly, if the user agent provides a mechanism to scroll the rows, the header
may appear at the top of the scrolled area and the footer at the bottom.
Calculate the number of columns [p.144] in the table. Note that the number of rows in a
table is equal to the number of tr [p.161] elements contained by the table [p.145] element.
Group the columns according to any column groups [p.142] specifications.
Render the cells, row by row and grouped in appropriate columns, between the header and
footer. Visual user agents should format the table according to XHTML attributes and style
sheet specification.

30.4.2. Table directionality

The directionality of a table is either the inherited directionality (the default is left-to-right) or that
specified by the dir [p.81] attribute for the table [p.145] element.

For a left-to-right table, column zero is on the left side and row zero is at the top. For a
right-to-left table, column zero is on the right side and row zero is at the top.

When a user agent allots extra cells to a row, extra row cells are added to the right of the table
for left-to-right tables and to the left side for right-to-left tables.

Note that table [p.145] is the only element on which dir [p.81] reverses the visual order of the
columns; a single table row ( tr [p.161] ) or a group of columns ( colgroup [p.142] ) cannot be
independently reversed.

When set for or inherited by the table [p.145] element, the dir [p.81] attribute also affects the
direction of text within table cells (since the dir [p.81] attribute is inherited by block-level
elements).

- 146 -
XHTML™ 2.0 30.4.3. Table rendering by non-visual user agents

To specify a right-to-left table, set the dir [p.81] attribute as follows:

Example
<table dir="rtl">
<em>...the rest of the table...</em>
</table>

The direction of text in individual cells can be changed by setting the dir [p.81] attribute in an
element that defines the cell.

30.4.3. Table rendering by non-visual user agents

This section provides more detailed discussion on cell header data and how non-visual agents
may utilize that information.

30.4.3.1. Associating header information with data cells

Non-visual user agents such as speech synthesizers and Braille-based devices may use the
following td [p.155] and th [p.155] element attributes to render table cells more intuitively:

For a given data cell, the headers [p.155] attribute lists which cells provide pertinent header
information. For this purpose, each header cell must be named using the id [p.67] attribute.
Note that it’s not always possible to make a clean division of cells into headers or data. You
should use the td [p.155] element for such cells together with the id [p.67] or scope [p.156]
attributes as appropriate.
For a given header cell, the scope [p.156] attribute tells the user agent the data cells for
which this header provides information. Authors may choose to use this attribute instead of
headers [p.155] according to which is more convenient; the two attributes fulfill the same
function. The headers [p.155] attribute is generally needed when headers are placed in
irregular positions with respect to the data they apply to.
The abbr [p.155] attribute specifies an abbreviated header for header cells so that user
agents may render header information more rapidly.

In the following example, we assign header information to cells by setting the headers [p.155]
attribute. Each cell in the same column refers to the same header cell (via the id [p.67] attribute).

Example
<table>
<caption>Cups of coffee consumed by each senator</caption>
<summary>This table charts the number of cups
of coffee consumed by each senator, the type
of coffee (decaf or regular), and whether
taken with sugar.</summary>
<tbody>
<tr>
<th id="t1">Name</th>
<th id="t2">Cups</th>
<th id="t3" abbr="Type">Type of Coffee</th>

- 147 -
30.4.3. Table rendering by non-visual user agents XHTML™ 2.0

<th id="t4">Sugar?</th>
</tr>
<tr>
<td headers="t1">T. Sexton</td>
<td headers="t2">10</td>
<td headers="t3">Espresso</td>
<td headers="t4">No</td>
</tr>
<tr>
<td headers="t1">J. Dinnen</td>
<td headers="t2">5</td>
<td headers="t3">Decaf</td>
<td headers="t4">Yes</td>
</tr>
</tbody>
</table>

A speech synthesizer might render this table as follows:

Example
Caption: Cups of coffee consumed by each senator
Summary: This table charts the number of cups
of coffee consumed by each senator, the type
of coffee (decaf or regular), and whether
taken with sugar.
Name: T. Sexton, Cups: 10, Type: Espresso, Sugar: No
Name: J. Dinnen, Cups: 5, Type: Decaf, Sugar: Yes

Note how the header "Type of Coffee" is abbreviated to "Type" using the abbr [p.155] attribute.

Here is the same example substituting the scope [p.156] attribute for the headers [p.155]
attribute. Note the value "col" for the scope [p.156] attribute, meaning "all cells in the current
column":

Example
<table>
<caption>Cups of coffee consumed by each senator</caption>
<summary>
This table charts the number of cups
of coffee consumed by each senator, the type
of coffee (decaf or regular), and whether
taken with sugar.
</summary>
<tbody>
<tr>
<th scope="col">Name</th>
<th scope="col">Cups</th>
<th scope="col" abbr="Type">Type of Coffee</th>
<th scope="col">Sugar?</th>
</tr>
<tr>
<td>T. Sexton</td>
<td>10</td>

- 148 -
XHTML™ 2.0 30.4.3. Table rendering by non-visual user agents

<td>Espresso</td>
<td>No</td>
</tr>
<tr>
<td>J. Dinnen</td>
<td>5</td>
<td>Decaf</td>
<td>Yes</td>
</tr>
</tbody>
</table>

Here’s a somewhat more complex example illustrating other values for the scope [p.156]
attribute:

Example
<table>
<summary>
History courses offered in the community of
Bath arranged by course name, tutor, summary,
code, and fee
</summary>
<thead>
<tr>
<th colspan="5" scope="colgroup">Community Courses -- Bath Autumn 1997</th>
</tr>
</thead>
<tbody>
<tr>
<th scope="col" abbr="Name">Course Name</th>
<th scope="col" abbr="Tutor">Course Tutor</th>
<th scope="col">Summary</th>
<th scope="col">Code</th>
<th scope="col">Fee</th>
</tr>
<tr>
<td scope="row">After the Civil War</td>
<td>Dr. John Wroughton</td>
<td>
The course will examine the turbulent years in England
after 1646. <em>6 weekly meetings starting Monday 13th
October.</em>
</td>
<td>H27</td>
<td>&pound;32</td>
</tr>
<tr>
<td scope="row">An Introduction to Anglo-Saxon England</td>
<td>Mark Cottle</td>
<td>
One day course introducing the early medieval
period reconstruction the Anglo-Saxons and
their society. <em>Saturday 18th October.</em>
</td>
<td>H28</td>

- 149 -
30.4.3. Table rendering by non-visual user agents XHTML™ 2.0

<td>&pound;18</td>
</tr>
<tr>
<td scope="row">The Glory that was Greece</td>
<td>Valerie Lorenz</td>
<td>
Birthplace of democracy, philosophy, heartland of theater, home of
argument. The Romans may have done it but the Greeks did it
first. <em>Saturday day school 25th October 1997</em>
</td>
<td>H30</td>
<td>&pound;18</td>
</tr>
</tbody>
</table>

A graphical user agent might render this as:

Note the use of the scope [p.156] attribute with the "row" value. Although the first cell in each
row contains data, not header information, the scope [p.156] attribute makes the data cell
behave like a row header cell. This allows speech synthesizers to provide the relevant course
name upon request or to state it immediately before each cell’s content.

30.4.3.2. Categorizing cells

Users browsing a table with a speech-based user agent may wish to hear an explanation of a
cell’s contents in addition to the contents themselves. One way the user might provide an
explanation is by speaking associated header information before speaking the data cell’s
contents (see the section on associating header information with data cells [p.147] ).

- 150 -
XHTML™ 2.0 30.4.3. Table rendering by non-visual user agents

Users may also want information about more than one cell, in which case header information
provided at the cell level (by headers [p.155] , scope [p.156] , and abbr [p.155] ) may not provide
adequate context. Consider the following table, which classifies expenses for meals, hotels, and
transport in two locations (San Jose and Seattle) over several days:

Users might want to extract information from the table in the form of queries:

"What did I spend for all my meals?"

"What did I spend for meals on 25 August?"
"What did I spend for all expenses in San Jose?"

Each query involves a computation by the user agent that may involve zero or more cells. In
order to determine, for example, the costs of meals on 25 August, the user agent must know
which table cells refer to "Meals" (all of them) and which refer to "Dates" (specifically, 25
August), and find the intersection of the two sets.

To accommodate this type of query, the table model allows authors to place cell headers and
data into categories. For example, for the travel expense table, an author could group the
header cells "San Jose" and "Seattle" into the category "Location", the headers "Meals",
"Hotels", and "Transport" in the category "Expenses", and the four days into the category "Date".
The previous three questions would then have the following meanings:

"What did I spend for all my meals?" means "What are all the data cells in the
"Expenses=Meals" category?
"What did I spend for meals on 25 August?" means "What are all the data cells in the
"Expenses=Meals" and "Date=Aug-25-1997" categories?
"What did I spend for all expenses in San Jose?" means "What are all the data cells in the
"Expenses=Meals, Hotels, Transport" and "Location=San Jose" categories?

Authors categorize a header or data cell by setting the axis [p.155] attribute for the cell. For
instance, in the travel expense table, the cell containing the information "San Jose" could be
placed in the "Location" category as follows:

- 151 -
30.4.3. Table rendering by non-visual user agents XHTML™ 2.0

Example
<th id="a6" axis="location">San Jose</th>

Any cell containing information related to "San Jose" should refer to this header cell via either
the headers [p.155] or the scope [p.156] attribute. Thus, meal expenses for 25-Aug-1997 should
be marked up to refer to id [p.67] attribute (whose value here is "a6") of the "San Jose" header
cell:

Example
<td headers="a6">37.74</td>

Each headers [p.155] attribute provides a list of id [p.67] references. Authors may thus
categorize a given cell in any number of ways (or, along any number of "headers", hence the
name).

Below we mark up the travel expense table with category information:

Example
<table>
<caption>Travel Expense Report</caption>
<summary>
This table summarizes travel expenses
incurred during August trips to
San Jose and Seattle
</summary>
<tbody>
<tr>
<th></th>
<th id="a2" axis="expenses">Meals</th>
<th id="a3" axis="expenses">Hotels</th>
<th id="a4" axis="expenses">Transport</th>
<td>subtotals</td>
</tr>
<tr>
<th id="a6" axis="location">San Jose</th>
<th></th>
<th></th>
<th></th>
<td></td>
</tr>
<tr>
<td id="a7" axis="date">25-Aug-97</td>
<td headers="a6 a7 a2">37.74</td>
<td headers="a6 a7 a3">112.00</td>
<td headers="a6 a7 a4">45.00</td>
<td></td>
</tr>
<tr>
<td id="a8" axis="date">26-Aug-97</td>
<td headers="a6 a8 a2">27.28</td>
<td headers="a6 a8 a3">112.00</td>

- 152 -
XHTML™ 2.0 30.4.3. Table rendering by non-visual user agents

<td headers="a6 a8 a4">45.00</td>

<td></td>
</tr>
<tr>
<td>subtotals</td>
<td>65.02</td>
<td>224.00</td>
<td>90.00</td>
<td>379.02</td>
</tr>
<tr>
<th id="a10" axis="location">Seattle</th>
<th></th>
<th></th>
<th></th>
<td></td>
</tr>
<tr>
<td id="a11" axis="date">27-Aug-97</td>
<td headers="a10 a11 a2">96.25</td>
<td headers="a10 a11 a3">109.00</td>
<td headers="a10 a11 a4">36.00</td>
<td></td>
</tr>
<tr>
<td id="a12" axis="date">28-Aug-97</td>
<td headers="a10 a12 a2">35.00</td>
<td headers="a10 a12 a3">109.00</td>
<td headers="a10 a12 a4">36.00</td>
<td></td>
</tr>
<tr>
<td>subtotals</td>
<td>131.25</td>
<td>218.00</td>
<td>72.00</td>
<td>421.25</td>
</tr>
<tr>
<th>Totals</th>
<td>196.27</td>
<td>442.00</td>
<td>162.00</td>
<td>800.27</td>
</tr>
</tbody>
</table>

Note that marking up the table this way also allows user agents to avoid confusing the user with
unwanted information. For instance, if a speech synthesizer were to speak all of the figures in
the "Meals" column of this table in response to the query "What were all my meal expenses?", a
user would not be able to distinguish a day’s expenses from subtotals or totals. By carefully
categorizing cell data, authors allow user agents to make important semantic distinctions when
rendering.

- 153 -
30.4.3. Table rendering by non-visual user agents XHTML™ 2.0

Of course, there is no limit to how authors may categorize information in a table. In the travel
expense table, for example, we could add the additional categories "subtotals" and "totals".

This specification does not require user agents to handle information provided by the axis
[p.155] attribute, nor does it make any recommendations about how user agents may present
axis [p.155] information to users or how users may query the user agent about this information.

However, user agents, particularly speech synthesizers, may want to factor out information
common to several cells that are the result of a query. For instance, if the user asks "What did I
spend for meals in San Jose?", the user agent would first determine the cells in question
(25-Aug-1997: 37.74, 26-Aug-1997:27.28), then render this information. A user agent speaking
this information might read it:

Example
Location: San Jose. Date: 25-Aug-1997. Expenses, Meals: 37.74
Location: San Jose. Date: 26-Aug-1997. Expenses, Meals: 27.28

or, more compactly:

Example
San Jose, 25-Aug-1997, Meals: 37.74
San Jose, 26-Aug-1997, Meals: 27.28

An even more economical rendering would factor the common information and reorder it:

Example
San Jose, Meals, 25-Aug-1997: 37.74
26-Aug-1997: 27.28

User agents that support this type of rendering should allow authors a means to customize
rendering (e.g., through style sheets).

30.4.3.3. Algorithm to find heading information

In the absence of header information from either the scope [p.156] or headers [p.155] attribute,
user agents may construct header information according to the following algorithm. The goal of
the algorithm is to find an ordered list of headers. (In the following description of the algorithm
the table directionality [p.146] is assumed to be left-to-right.)

First, search left from the cell’s position to find row header cells. Then search upwards to
find column header cells. The search in a given direction stops when the edge of the table is
reached or when a data cell is found after a header cell.
Row headers are inserted into the list in the order they appear in the table. For left-to-right
tables, headers are inserted from left to right.
Column headers are inserted after row headers, in the order they appear in the table, from
top to bottom.

- 154 -
XHTML™ 2.0 30.5. The tbody element

If a header cell has the headers [p.155] attribute set, then the headers referenced by this
attribute are inserted into the list and the search stops for the current direction.
td [p.155] cells that set the axis [p.155] attribute are also treated as header cells.

30.5. The tbody element

Attributes

The Common [p.34] collection

The tbody [p.155] element contains rows of table data. In tables that also contain thead [p.160]
or tfoot [p.160] elements, all of these sections must contain the same number of columns.

30.6. The td and th elements

Attributes

The Common [p.34] collection

abbr = Text [p.31]

This attribute should be used to provide an abbreviated form of the cell’s content, and may
be rendered by user agents when appropriate in place of the cell’s content. Abbreviated
names should be short since user agents may render them repeatedly. For instance,
speech synthesizers may render the abbreviated headers relating to a particular cell before
rendering that cell’s content.

axis = CDATA [p.29]

This attribute may be used to place a cell into conceptual categories that can be considered
to form axes in an n-dimensional space. User agents may give users access to these
categories (e.g., the user may query the user agent for all cells that belong to certain
categories, the user agent may present a table in the form of a table of contents, etc.).
Please consult the section on categorizing cells [p.150] for more information. The value of
this attribute is a comma-separated list of category names.

colspan = Number [p.31]

This attribute specifies the number of columns spanned by the current cell. The default
value of this attribute is one ("1"). The value zero ("0") means that the cell spans all columns
from the current column to the last column of the column group ( colgroup [p.142] ) in which
the cell is defined.

- 155 -
30.6. The td and th elements XHTML™ 2.0

headers = IDREFS [p.29]

This attribute specifies the list of header cells that provide header information for the current
data cell. The value of this attribute is a space-separated list of cell names; those cells must
be named by setting their id [p.67] attribute. Authors generally use the headers [p.156]
attribute to help non-visual user agents render header information about data cells (e.g.,
header information is spoken prior to the cell data), but the attribute may also be used in
conjunction with style sheets. See also the scope [p.156] attribute.

rowspan = Number [p.31]

This attribute specifies the number of rows spanned by the current cell. The default value of
this attribute is one ("1"). The value zero ("0") means that the cell spans all rows from the
current row to the last row of the current table section (rowgroup) in which the cell is
defined. thead [p.160] , tbody [p.155] , and tfoot [p.160] elements are rowgroups.

scope = row|col|rowgroup|colgroup
This attribute specifies the set of data cells for which the current header cell provides
header information. This attribute may be used in place of the headers [p.156] attribute,
particularly for simple tables. When specified, this attribute must have one of the following
values:
row: The current cell provides header information for the rest of the row that contains it
(see also the section on table directionality [p.146] ).
col: The current cell provides header information for the rest of the column that
contains it.
rowgroup: The header cell provides header information for the rest of the row group
that contains it.
colgroup: The header cell provides header information for the rest of the column group
[p.142] that contains it.

Table cells may contain two types of information: header information and data. This distinction
enables user agents to render header and data cells distinctly, even in the absence of style
sheets. For example, visual user agents may present header cell text with a bold font. Speech
synthesizers may render header information with a distinct voice inflection.

The th [p.155] element defines a cell that contains header information. User agents have two
pieces of header information available: the contents of the th [p.155] element and the value of
the abbr [p.155] attribute. User agents must render either the contents of the cell or the value of
the abbr [p.155] attribute. For visual media, the latter may be appropriate when there is
insufficient space to render the full contents of the cell. For non-visual media abbr [p.155] may
be used as an abbreviation for table headers when these are rendered along with the contents
of the cells to which they apply.

The headers [p.156] and scope [p.156] attributes also allow authors to help non-visual user
agents process header information. Please consult the section on labeling cells for non-visual
user agents [p.147] for information and examples.

- 156 -
XHTML™ 2.0 30.6.1. Cells that span several rows or columns

The td [p.155] element defines a cell that contains data.

Cells may be empty (i.e., contain no data).

30.6.1. Cells that span several rows or columns

Cells may span several rows or columns. The number of rows or columns spanned by a cell is
set by the rowspan [p.156] and colspan [p.155] attributes for the th [p.155] and td [p.155]
elements.

In this table definition, we specify that the cell in row four, column two should span a total of
three columns, including the current column.
<table>
<caption>Cups of coffee consumed by each senator</caption>
<tbody>
<tr>
<th>Name</th>
<th>Cups</th>
<th>Type of Coffee</th>
<th>Sugar?</th>
</tr>
<tr>
<td>T. Sexton</td>
<td>10</td>
<td>Espresso</td>
<td>No</td>
</tr>
<tr>
<td>J. Dinnen</td>
<td>5</td>
<td>Decaf</td>
<td>Yes</td>
</tr>
<tr>
<td>A. Soria</td>
<td colspan="3"><em>Not available</em></td>
</tr>
</tbody>
</table>

This table might be rendered on a tty device by a visual user agent as follows:
Cups of coffee consumed by each senator
--------------------------------------
| Name |Cups|Type of Coffee|Sugar?|
--------------------------------------
|T. Sexton|10 |Espresso |No |
--------------------------------------
|J. Dinnen|5 |Decaf |Yes |
--------------------------------------
|A. Soria |Not available |
--------------------------------------

- 157 -
30.6.1. Cells that span several rows or columns XHTML™ 2.0

The next example illustrates (with the help of table borders) how cell definitions that span more
than one row or column affect the definition of later cells. Consider the following table definition:
<table>
<tbody>
<tr>
<td>1</td>
<td rowspan="2">2</td>
<td>3</td>
</tr>
<tr>
<td>4</td>
<td>6</td>
</tr>
<tr>
<td>7</td>
<td>8</td>
<td>9</td>
<td></td>
</tr>
</tbody>
</table>

As cell "2" spans the first and second rows, the definition of the second row will take it into
account. Thus, the second td [p.155] in row two actually defines the row’s third cell. Visually, the
table might be rendered to a tty device as:
-------------
| 1 | 2 | 3 |
----| |----
| 4 | | 6 |
----|---|----
| 7 | 8 | 9 |
-------------

while a graphical user agent might render this as:

Note that if the td [p.155] defining cell "6" had been omitted, an extra empty cell would have
been added by the user agent to complete the row.

Similarly, in the following table definition:

- 158 -
XHTML™ 2.0 30.6.1. Cells that span several rows or columns

cell "4" spans two columns, so the second td [p.155] in the row actually defines the third cell
("6"):
-------------
| 1 | 2 | 3 |
--------|----
| 4 | 6 |
--------|----
| 7 | 8 | 9 |
-------------

A graphical user agent might render this as:

Defining overlapping cells is an error. User agents may vary in how they handle this error (e.g.,
rendering may vary).

The following illegal example illustrates how one might create overlapping cells. In this table, cell
"5" spans two rows and cell "7" spans two columns, so there is overlap in the cell between "7"
and "9":
<table>
<tbody>
<tr>
<td>1</td>
<td>2</td>
<td>3</td>
</tr>
<tr>
<td>4</td>
<td rowspan="2">5</td>
<td>6</td>
</tr>

- 159 -
30.7. The thead and tfoot elements XHTML™ 2.0

30.7. The thead and tfoot elements

Attributes

The Common [p.34] collection

Table rows may be grouped into a table head, table foot, and one or more table body sections,
using the thead [p.160] , tfoot [p.160] and tbody [p.155] elements, respectively. This division
enables user agents to support scrolling of table bodies independently of the table head and
foot. When long tables are printed, the table head and foot information may be repeated on each
page that contains table data.

The table head and table foot should contain information about the table’s columns. The table
body must contain rows of table data.

When present, each thead [p.160] , tfoot [p.160] , and tbody [p.155] creates a row group. Each
row group must contain at least one row, defined by the tr [p.161] element.

If the thead [p.160] , tfoot [p.160] , and tbody [p.155] elements are used, and a rowspan attribute
is used within a group, the rowspan must remain within the group boundaries of which it is
defined.

This example illustrates the order and structure of the table head, foot, and bodies.

Example
<table>
<thead>
<tr> <em>...header information...</em></tr>
</thead>
<tfoot>
<tr> <em>...footer information...</em></tr>
</tfoot>
<tbody>
<tr> <em>...first row of block one data...</em></tr>
<tr> <em>...second row of block one data...</em></tr>
</tbody>
<tbody>
<tr> <em>...first row of block two data...</em></tr>

- 160 -
XHTML™ 2.0 30.8. The tr element

<tr> <em>...second row of block two data...</em></tr>

<tr> <em>...third row of block two data...</em></tr>
</tbody>
</table>

tfoot [p.160] must appear before tbody [p.155] within a table [p.145] definition so that user
agents can render the foot before receiving all of the (potentially numerous) rows of data.

30.8. The tr element

Attributes

The Common [p.34] collection

The tr [p.161] elements acts as a container for a row of table cells.

This sample table contains three rows, each begun by the tr [p.161] element:
<table>
<caption>Cups of coffee consumed by each senator</caption>
<summary>This table charts the number of cups
of coffee consumed by each senator, the type
of coffee (decaf or regular), and whether
taken with sugar.</summary>
<tbody>
<tr> ...A header row...</tr>
<tr> ...First row of data...</tr>
<tr> ...Second row of data...</tr>
</tbody>
</table>

30.9. Issues
Why no nested colgroup or rowgroup? PR #7828
State: Open
Resolution: None
User: None

Notes:

What is the scope of a header? PR #7878

State: Open
Resolution: None
User: None

- 161 -
30.9. Issues XHTML™ 2.0

Notes:
Group agress that the scope needs a better explanation.

td/th scope attribute - rowgroup == (tbody, thead, tfoot) PR #7879

State: Open
Resolution: None
User: None

Notes:
Agree that we need to tighten up the terminology.

nesting colgroup and rowgroups PR #7881

State: Open
Resolution: None
User: None

Notes:
While there are notional "rowgroups" there are no explicit arbitrary rowgroups in HTML nor in
XHTML because rows are explicit in tables. colgroups, on the other hand, exist because HTML /
XHTML needs a way of referring to columns. Asked the submitter for more information and an
example including a description of what the advantages would be.

- 162 -
XHTML™ 2.0 31. XForms Module

31. XForms Module

This section is normative for purposes of defining the integration of XForms into XHTML 2.0.
The XForms language itself is normatively defined in [XFORMS [p.248] ].

The XForms Module provides a rich collection of forms features within the XHTML namespace.

The content model for XForms defines several content sets:

31.1. Core XForms

When this module is included, the XForms Core content set is added to the content model of the
head [p.38] element in the Document [p.37] module, to the Structural [p.43] content set of the
Structural Module., and to the Text [p.51] content set of the Text module.

31.2. XForms Actions

When this module is included, the XForms Actions content set is added to the content model of
the head [p.38] element in the Document [p.37] module, to the Structural [p.43] content set, and
to the Text [p.51] content set.

31.3. Form Controls

When this module is included, the XForms Form Controls content set is added to the Structural
[p.43] content set, and to the Text [p.51] content set.

The Text [p.51] content set is added to the XForms UI Inline content set, allowing various
XHTML elements inside form control labels.

- 163 -
31.4. Group XHTML™ 2.0

31.4. Group
When this module is included, the XForms Group content set is added to the Structural [p.43]
content set, and to the Text [p.51] content set.

group [p.163] elements can freely nest.

The Structural [p.43] content set is added to the XForms Group content set.

31.5. Switch
When this module is included, the XForms Switch content set is added to the Structural [p.43]
content set, and to the Text [p.51] content set.

Alternating switch [p.163] and case elements can freely nest.

The Structural [p.43] content set is added to the content model of case, after an optional label
element.

31.6. Repeat
When this module is included, the XForms Repeat content set is added to the Structural [p.43]
content set, and to the Text [p.51] content set.

repeat [p.163] elements can freely nest.

The Structural [p.43] content set is added to the content model of case, after an optional label
element.

31.7. XForms Repeat Attribute Collection

This module also includes the XForms Repeat Attribute Collection via attributes from [XFORMS
[p.248] ]. The normative definition of those attributes and their semantics is included in that
specification. They are described briefly below:

repeat-model = IDREF [p.29]

This attribute defines the XForms model to be associated with the element.

repeat-bind = IDREF [p.29]

This attribute provides a reference to an XForms bind element.

repeat-nodeset = LocationPath [p.31]

This attribute defines an XPath LocationPath that maps to an XForms bind element.

- 164 -
XHTML™ 2.0 31.8. Other Attribute Collections

repeat-startindex = Number [p.31]

XForms hint to the processor as to which item from the collection to display first.

repeat-number = Number [p.31]

XForms hint to the processor as to how many items from the collection to display at a time.

When this module is included, the XForms Repeat Attribute collection is included on all elements
that can validly appear twice or more as sibling elements.

31.8. Other Attribute Collections

XHTML 2 adds the Common [p.34] attribute group to the XForms Common Attribute Group.

The Linking Attribute Group is allowed on all elements, including instance.

The XForms Attribute Groups for single-node binding and Nodeset binding are allowed only on
the XForms elements they are defined for.

Implementation: XML Schema

31.9. Issues
[XHTML2] exclude switch and case as presentational PR #7826
State: Open
Resolution: None
User: None

Notes:

autocomplete attribute PR #7838

State: Open
Resolution: None
User: None

Notes:

- 165 -
31.9. Issues XHTML™ 2.0

- 166 -
XHTML™ 2.0 32. XML Events Module

32. XML Events Module

This section is normative.

The XML Events Module defines a linkage between XHTML and the XML Document Object
Model [DOM [p.247] ]. XML Events are defined in [XMLEVENTS [p.249] ], and all XML Event
elements and attributes are in their own namespace.

This module includes the ev:listener as defined in [XMLEVENTS [p.249] ].

32.1. Events
This module also defines the Events Attribute Collection via the global attributes from
[XMLEVENTS [p.249] ]. The normative definition of those attributes and their semantics is
included in that specification. They are described briefly below:

defaultAction = "cancel|perform"
This attribute defines whether or not the default action associated with the event should be
processed. The default value is perform

event = CDATA [p.29]

This attribute defines the event type that is being listened for. The set of legal names for
XHTML 2 is to be defined.

handler = IDREF [p.29]

This attribute specifies the ID of a handler element that defines the action that should be
performed if the event reaches the observer.

observer = IDREF [p.29]

This attribute specifies an ID for an observer element for which the listener is to be
registered.

phase = "capture|default"
This attribute specifies the phase of event propagation in which to process the event. If not
specified, the default value of this attribute is default.

propagate = "stop|continue"
This attribute specifies whether an event should stop propagating after this observer
processes it, or continue for possible further processing. The default value of this attribute is
continue.

target = IDREF [p.29]

This attribute specifies the id of the target element of the event (i.e., the node that caused
the event). If not specified, the default value of this attribute is the element on which the
event attribute is specified.

- 167 -
32.1. Events XHTML™ 2.0

Note that these attributes are not in the XHTML namespace but in the XML Events namespace.
The XHTML namespace is the default namespace for XHTML documents, so XHTML elements
and attributes may be expressed without namespace prefixes (although they are permitted on
elements). XML Events attributes MUST use a prefix, since they are not in the default
namespace of the document.

Implementation: RELAX NG [p.223] , XML Schema, DTD

- 168 -
XHTML™ 2.0 A. Changes from XHTML 1.1

A. Changes from XHTML 1.1

This appendix is informative.

This Appendix describes the differences between XHTML 2.0 and XHTML 1.1.

- 169 -
A. Changes from XHTML 1.1 XHTML™ 2.0

- 170 -
XHTML™ 2.0 B. XHTML 2.0 RELAX NG Definition

B. XHTML 2.0 RELAX NG Definition

This appendix is normative.

This appendix contains the implementation of the XHTML 2.0 RELAX NG driver file.

B.0.1. RELAX NG XHTML 2.0 Driver

<?xml version="1.0" encoding="UTF-8"?>
<grammar ns="http://www.w3.org/2002/06/xhtml2/"
xmlns="http://relaxng.org/ns/structure/1.0"
xmlns:x="http://www.w3.org/1999/xhtml">

<x:h1>RELAX NG schema for XHTML 2.0</x:h1>

<x:pre>
Copyright Â©2003-2005 W3CÂ® (MIT, ERCIM, Keio), All Rights Reserved.

Editor: Masayasu Ishikawa <[email protected]>

Revision: $Id: xhtml2.rng,v 1.42 2005/07/27 13:36:09 mimasa Exp $

Permission to use, copy, modify and distribute this RELAX NG schema

for XHTML 2.0 and its accompanying documentation for any purpose and
without fee is hereby granted in perpetuity, provided that the above
copyright notice and this paragraph appear in all copies. The copyright
holders make no representation about the suitability of this RELAX NG
schema for any purpose.

It is provided "as is" without expressed or implied warranty.

For details, please refer to the W3C software license at:

<x:a href="http://www.w3.org/Consortium/Legal/copyright-software"
>http://www.w3.org/Consortium/Legal/copyright-software</x:a>
</x:pre>

<div>
<x:h2>XHTML 2.0 modules</x:h2>

<x:h3>Attribute Collections Module</x:h3>

<x:h3>Document Module</x:h3>
<include href="xhtml-document-2.rng"/>

<x:h3>Structural Module</x:h3>
<include href="xhtml-structural-2.rng"/>

<x:h3>Text Module</x:h3>
<include href="xhtml-text-2.rng"/>

<x:h3>Hypertext Module</x:h3>
<include href="xhtml-hypertext-2.rng"/>

<x:h3>List Module</x:h3>
<include href="xhtml-list-2.rng"/>

- 171 -
B.0.1. RELAX NG XHTML 2.0 Driver XHTML™ 2.0

<x:h3>Handler Module</x:h3>
<include href="xhtml-handler-2.rng"/>

<x:h3>Image Module</x:h3>
<include href="xhtml-image-2.rng"/>

<x:h3>Metainformation Module</x:h3>
<include href="xhtml-meta-2.rng"/>

<x:h3>Object Module</x:h3>
<include href="xhtml-object-2.rng"/>

<x:h3>Access Module</x:h3>
<include href="xhtml-access-2.rng"/>

<x:h3>Style Sheet Module</x:h3>

<x:h3>Tables Module</x:h3>
<include href="xhtml-table-2.rng"/>

<x:h3>Support Modules</x:h3>

<x:h4>Datatypes Module</x:h4>
<include href="xhtml-datatypes-2.rng"/>

<x:h4>Param Module</x:h4>
<include href="xhtml-param-2.rng"/>

<x:h4>Caption Module</x:h4>
<include href="xhtml-caption-2.rng"/>
</div>

<div>
<x:h2>XML Events module</x:h2>
<include href="xml-events-1.rng"/>
</div>

<div>
<x:h2>Ruby module</x:h2>

</include>

- 172 -
XHTML™ 2.0 B.0.1. RELAX NG XHTML 2.0 Driver

</define>

<define name="Text.class" combine="choice">

<div>
<x:h2>XForms module</x:h2>

<define name="head.misc" combine="choice">

<define name="Misc.class" combine="choice">

<define name="XFORMS.UI.Inline.class" combine="choice">

<div>
<x:h2>XML Schema instance module</x:h2>
<include href="XMLSchema-instance.rng"/>
</div>

</grammar>

- 173 -
B.0.1. RELAX NG XHTML 2.0 Driver XHTML™ 2.0

- 174 -
XHTML™ 2.0 C. XHTML RELAX NG Module Implementations

C. XHTML RELAX NG Module Implementations

This appendix is normative.

This appendix contains implementations of the modules defined in this specification. These
module implementations can be used in other XHTML Family Document Types.

C.1. XHTML Module Implementations

This section contains the formal definition of each of the XHTML Abstract Modules as a RELAX
NG module.

C.1.1. Attribute Collections

<?xml version="1.0" encoding="UTF-8"?>
<grammar xmlns="http://relaxng.org/ns/structure/1.0"
xmlns:x="http://www.w3.org/1999/xhtml">

<x:h1>Attribute Collections Module</x:h1>

<div>
<x:h2>Core Attributes Module</x:h2>
<include href="xhtml-core-attrib-2.rng"/>
</div>

<div>
<x:h2>Internationalization Attribute Module</x:h2>
<include href="xhtml-i18n-attrib-2.rng"/>
</div>

<div>
<x:h2>Bi-directional Text Collection</x:h2>
<include href="xhtml-bidi-attrib-2.rng"/>
</div>

<div>
<x:h2>Edit Attributes Module</x:h2>
<include href="xhtml-edit-attrib-2.rng"/>
</div>

<div>
<x:h2>Embedding Attributes Module</x:h2>
<include href="xhtml-embed-attrib-2.rng"/>
</div>

<div>
<x:h2>Events Module</x:h2>
<include href="xhtml-events-2.rng"/>
</div>

<div>
<x:h2>XForms Repeat Attribute Collection</x:h2>
<include href="xforms-repeat-attrib.rng"/>

- 175 -
C.1.2. Document XHTML™ 2.0

<define name="Common.attrib" combine="interleave">

<div>
<x:h2>Hypertext Attributes Module</x:h2>
<include href="xhtml-hypertext-attrib-2.rng"/>
</div>

<div>
<x:h2>Image Map Attributes Module</x:h2>
<include href="xhtml-imagemap-attrib-2.rng"/>
</div>

<div>
<x:h2>Media Attribute Module</x:h2>
<include href="xhtml-media-attrib-2.rng"/>
</div>

<div>
<x:h2>Metainformation Attributes Module</x:h2>
<include href="xhtml-meta-attrib-2.rng"/>
</div>

<div>
<x:h2>Role Attribute Module</x:h2>
<include href="xhtml-role-attrib-2.rng"/>
</div>

<div>
<x:h2>Style Attribute Module</x:h2>
<include href="xhtml-inlstyle-2.rng"/>
</div>

</grammar>

C.1.2. Document
<?xml version="1.0" encoding="UTF-8"?>
<grammar xmlns="http://relaxng.org/ns/structure/1.0"
xmlns:x="http://www.w3.org/1999/xhtml">

<x:h1>Document Module</x:h1>

- 176 -
XHTML™ 2.0 C.1.2. Document

</start>

<div>
<x:h2>The html element</x:h2>

<div>
<x:h2>The head element</x:h2>

- 177 -
C.1.3. Structural XHTML™ 2.0

<div>
<x:h2>The title element</x:h2>

<div>
<x:h2>The body element</x:h2>

</grammar>

C.1.3. Structural
<?xml version="1.0" encoding="UTF-8"?>
<grammar xmlns="http://relaxng.org/ns/structure/1.0"
xmlns:x="http://www.w3.org/1999/xhtml">

<x:h1>Structural Module</x:h1>

<div>
<x:h2>The address element</x:h2>

- 178 -
XHTML™ 2.0 C.1.3. Structural

<div>
<x:h2>The blockcode element</x:h2>

<div>
<x:h2>The blockquote element</x:h2>

<div>
<x:h2>The div element</x:h2>

<div>
<x:h2>The heading elements</x:h2>

- 179 -
C.1.3. Structural XHTML™ 2.0

- 180 -
XHTML™ 2.0 C.1.3. Structural

<div>
<x:h2>The p element</x:h2>

<div>
<x:h2>The pre element</x:h2>

<div>
<x:h2>The section element</x:h2>

<div>
<x:h2>The separator element</x:h2>

- 181 -
C.1.3. Structural XHTML™ 2.0

<div>
<x:h2>Content Model</x:h2>

- 182 -
XHTML™ 2.0 C.1.3. Structural

</choice>
</zeroOrMore>
</define>

</grammar>

- 183 -
C.1.4. Text XHTML™ 2.0

C.1.4. Text
<?xml version="1.0" encoding="UTF-8"?>
<grammar xmlns="http://relaxng.org/ns/structure/1.0"
xmlns:x="http://www.w3.org/1999/xhtml">

<x:h1>Text Module</x:h1>

<div>
<x:h2>The abbr element</x:h2>

<div>
<x:h2>The cite element</x:h2>

<div>
<x:h2>The code element</x:h2>

- 184 -
XHTML™ 2.0 C.1.4. Text

</div>

<div>
<x:h2>The dfn element</x:h2>

<div>
<x:h2>The em element</x:h2>

<div>
<x:h2>The kbd element</x:h2>

<div>
<x:h2>The l element</x:h2>

- 185 -
C.1.4. Text XHTML™ 2.0

<div>
<x:h2>The quote element</x:h2>

<div>
<x:h2>The samp element</x:h2>

<div>
<x:h2>The span element</x:h2>

<div>
<x:h2>The strong element</x:h2>

- 186 -
XHTML™ 2.0 C.1.4. Text

</element>
</define>

<div>
<x:h2>The sub element</x:h2>

<div>
<x:h2>The sup element</x:h2>

<div>
<x:h2>The var element</x:h2>

<div>
<x:p>these can occur at Structural or Text level</x:p>

- 187 -
C.1.5. Hypertext XHTML™ 2.0

<div>
<x:h2>Content Model</x:h2>

</grammar>

C.1.5. Hypertext
<?xml version="1.0" encoding="UTF-8"?>
<grammar xmlns="http://relaxng.org/ns/structure/1.0"
xmlns:x="http://www.w3.org/1999/xhtml">

<x:h1>Hypertext Module</x:h1>

<div>
<x:h2>The a element</x:h2>

- 188 -
XHTML™ 2.0 C.1.6. List

<define name="Text.class" combine="choice">

</grammar>

C.1.6. List
<?xml version="1.0" encoding="UTF-8"?>
<grammar xmlns="http://relaxng.org/ns/structure/1.0"
xmlns:x="http://www.w3.org/1999/xhtml">

<x:h1>List Module</x:h1>

<div>
<x:h2>The dl element</x:h2>

<div>
<x:h2>The di element</x:h2>

- 189 -
C.1.6. List XHTML™ 2.0

</oneOrMore>
<zeroOrMore>
<ref name="dd"/>
</zeroOrMore>
</element>
</define>

<div>
<x:h2>The dt element</x:h2>

<div>
<x:h2>The dd element</x:h2>

<div>
<x:h2>The label element</x:h2>

- 190 -
XHTML™ 2.0 C.1.6. List

<div>
<x:h2>The nl element</x:h2>

<div>
<x:h2>The ol element</x:h2>

<div>
<x:h2>The ul element</x:h2>

- 191 -
C.1.6. List XHTML™ 2.0

<div>
<x:h2>The li element</x:h2>

<div>
<x:h2>List Content Set</x:h2>

</grammar>

- 192 -
XHTML™ 2.0 C.1.7. Core Attributes

C.1.7. Core Attributes

<?xml version="1.0" encoding="UTF-8"?>
<grammar xmlns="http://relaxng.org/ns/structure/1.0"
xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0"
xmlns:x="http://www.w3.org/1999/xhtml">

<x:h1>Core Attributes Module</x:h1>

<div>
<x:h2>Core Attribute Collection</x:h2>

<define name="layout.attrib">
<optional>
<attribute name="layout" a:defaultValue="irrelevant">
<choice>
<value>irrelevant</value>
<value>relevant</value>
</choice>
</attribute>
</optional>
</define>

<define name="Common.attrib" combine="interleave">

- 193 -
C.1.8. Hypertext Attributes XHTML™ 2.0

</grammar>

C.1.8. Hypertext Attributes

<?xml version="1.0" encoding="UTF-8"?>
<grammar xmlns="http://relaxng.org/ns/structure/1.0"
xmlns:x="http://www.w3.org/1999/xhtml">

<x:h1>Hypertext Attributes Module</x:h1>

<div>
<x:h2>Hypertext Attributes Collection</x:h2>

- 194 -
XHTML™ 2.0 C.1.8. Hypertext Attributes

<define name="Common.attrib" combine="interleave">

</grammar>

- 195 -
C.1.9. I18N Attribute XHTML™ 2.0

C.1.9. I18N Attribute

<?xml version="1.0" encoding="UTF-8"?>
<grammar xmlns="http://relaxng.org/ns/structure/1.0"
xmlns:x="http://www.w3.org/1999/xhtml">

<x:h1>I18N Attribute Module</x:h1>

<div>
<x:h2>I18N Attribute Collection</x:h2>

<define name="Common.attrib" combine="interleave">

</grammar>

C.1.10. Access
<?xml version="1.0" encoding="UTF-8"?>
<grammar xmlns="http://relaxng.org/ns/structure/1.0"
xmlns:x="http://www.w3.org/1999/xhtml">

<x:h1>Access Module</x:h1>

<div>
<x:h2>The access element</x:h2>

- 196 -
XHTML™ 2.0 C.1.11. Bi-directional Text Attribute

<define name="head.misc" combine="choice">

</grammar>

C.1.11. Bi-directional Text Attribute

<x:h1>Bi-directional Text Attribute Module</x:h1>

<div>
<x:h2>Bi-directional Text Collection</x:h2>

<define name="Common.attrib" combine="interleave">

</grammar>

- 197 -
C.1.12. Edit Attributes XHTML™ 2.0

C.1.12. Edit Attributes

<?xml version="1.0" encoding="UTF-8"?>
<grammar xmlns="http://relaxng.org/ns/structure/1.0"
xmlns:x="http://www.w3.org/1999/xhtml">

<x:h1>Edit Attribute Module</x:h1>

<div>
<x:h2>Edit Collection</x:h2>

<define name="edit.attrib">
<optional>
<attribute name="edit">
<choice>
<value>inserted</value>
<value>deleted</value>
<value>changed</value>
<value>moved</value>
</choice>
</attribute>
</optional>
</define>

<define name="Common.attrib" combine="interleave">

</grammar>

C.1.13. Embedding Attributes

<?xml version="1.0" encoding="UTF-8"?>
<grammar xmlns="http://relaxng.org/ns/structure/1.0"
xmlns:x="http://www.w3.org/1999/xhtml">

<x:h1>Embedding Attributes Module</x:h1>

<div>
<x:h2>Embedding Attributes Collection</x:h2>

- 198 -
XHTML™ 2.0 C.1.14. Handler

</grammar>

C.1.14. Handler
<?xml version="1.0" encoding="UTF-8"?>
<grammar xmlns="http://relaxng.org/ns/structure/1.0"
xmlns:x="http://www.w3.org/1999/xhtml">

<x:h1>Handler Module</x:h1>

<div>
<x:h2>The handler element</x:h2>

- 199 -
C.1.15. Image XHTML™ 2.0

<define name="head.misc" combine="choice">

<define name="Misc.class" combine="choice">

</grammar>

C.1.15. Image
<?xml version="1.0" encoding="UTF-8"?>
<grammar xmlns="http://relaxng.org/ns/structure/1.0"
xmlns:x="http://www.w3.org/1999/xhtml">

<x:h1>Image Module</x:h1>

<div>
<x:h2>The img element</x:h2>

<define name="Text.class" combine="choice">

</grammar>

- 200 -
XHTML™ 2.0 C.1.16. Image Map Attributes

C.1.16. Image Map Attributes

<?xml version="1.0" encoding="UTF-8"?>
<grammar xmlns="http://relaxng.org/ns/structure/1.0"
xmlns:x="http://www.w3.org/1999/xhtml">

<x:h1>Image Map Attributes Module</x:h1>

<div>
<x:h2>Image Map Attributes Collection</x:h2>

<define name="ismap.attrib">
<optional>
<attribute name="ismap">
<value>ismap</value>
</attribute>
</optional>
</define>

<define name="Common.attrib" combine="interleave">

</grammar>

- 201 -
C.1.17. Media Attribute XHTML™ 2.0

C.1.17. Media Attribute

<x:h1>Media Attribute Module</x:h1>

<define name="Common.attrib" combine="interleave">

</grammar>

C.1.18. Metainformation Attributes

<x:h1>Metainformation Attributes Module</x:h1>

<div>
<x:h2>Metadata Attribute Collection</x:h2>

- 202 -
XHTML™ 2.0 C.1.19. Metainformation

</optional>
</define>

<define name="Common.attrib" combine="interleave">

</grammar>

C.1.19. Metainformation
<?xml version="1.0" encoding="UTF-8"?>
<grammar xmlns="http://relaxng.org/ns/structure/1.0"
xmlns:x="http://www.w3.org/1999/xhtml">

<x:h1>Metainformation Module</x:h1>

<div>
<x:h2>The link element</x:h2>

- 203 -
C.1.20. Object XHTML™ 2.0

<define name="head.misc" combine="choice">

<define name="Misc.class" combine="choice">

<div>
<x:h2>The meta element</x:h2>

<define name="head.misc" combine="choice">

<define name="Misc.class" combine="choice">

</grammar>

C.1.20. Object
<?xml version="1.0" encoding="UTF-8"?>
<grammar xmlns="http://relaxng.org/ns/structure/1.0"
xmlns:x="http://www.w3.org/1999/xhtml">

<x:h1>Object Module</x:h1>

- 204 -
XHTML™ 2.0 C.1.20. Object

<x:p>Note. Also include the Caption Module when this module is used.</x:p>

<div>
<x:h2>The object element</x:h2>

<define name="object.attlist">
<ref name="Common.attrib"/>
<optional>
<attribute name="archive">
<ref name="URIs.datatype"/>
</attribute>
</optional>
<optional>
<attribute name="content-length">
<ref name="Number.datatype"/>
</attribute>
</optional>
<optional>
<attribute name="declare">
<value>declare</value>
</attribute>
</optional>
</define>
</div>

<div>
<x:h2>The standby element</x:h2>

<define name="Text.class" combine="choice">

- 205 -
C.1.21. Role Access XHTML™ 2.0

</grammar>

C.1.21. Role Access

<?xml version="1.0" encoding="UTF-8"?>
<grammar xmlns="http://relaxng.org/ns/structure/1.0"
xmlns:x="http://www.w3.org/1999/xhtml">

<x:h1>Access Module</x:h1>

<div>
<x:h2>The access element</x:h2>

<define name="head.misc" combine="choice">

</grammar>

C.1.22. Style Attribute

<?xml version="1.0" encoding="UTF-8"?>
<grammar xmlns="http://relaxng.org/ns/structure/1.0"
xmlns:x="http://www.w3.org/1999/xhtml">

<x:h1>Style Attribute Module</x:h1>

- 206 -
XHTML™ 2.0 C.1.23. Style Sheet

<define name="Common.attrib" combine="interleave">

</grammar>

C.1.23. Style Sheet

<?xml version="1.0" encoding="UTF-8"?>
<grammar xmlns="http://relaxng.org/ns/structure/1.0"
xmlns:x="http://www.w3.org/1999/xhtml">

<x:h1>Style Module</x:h1>

<div>
<x:h2>The style element</x:h2>

<define name="style.attlist">
<ref name="Common.attrib"/>
<optional>
<attribute name="disabled">
<value>disabled</value>
</attribute>
</optional>
</define>
</div>

<define name="head.misc" combine="choice">

</grammar>

C.1.24. Tables
<?xml version="1.0" encoding="UTF-8"?>
<grammar xmlns="http://relaxng.org/ns/structure/1.0"
xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0"
xmlns:x="http://www.w3.org/1999/xhtml">

<x:h1>Tables Module</x:h1>

<x:p>Note. Also include the Caption Module when this module is used.</x:p>

- 207 -
C.1.24. Tables XHTML™ 2.0

<div>
<x:h2>The table element</x:h2>

<div>
<x:h2>The summary element</x:h2>

- 208 -
XHTML™ 2.0 C.1.24. Tables

</define>
</div>

<div>
<x:h2>The col element</x:h2>

<div>
<x:h2>The colgroup element</x:h2>

<div>
<x:h2>The thead element</x:h2>

<div>
<x:h2>The tfoot element</x:h2>

- 209 -
C.1.24. Tables XHTML™ 2.0

<div>
<x:h2>The tbody element</x:h2>

<div>
<x:h2>The tr element</x:h2>

<div>
<x:h2>The th element</x:h2>

- 210 -
XHTML™ 2.0 C.1.24. Tables

</element>
</define>

<div>
<x:h2>The td element</x:h2>

<div>
<x:h2>Attribute definitions</x:h2>

- 211 -
C.2. XHTML RELAX NG Support Modules XHTML™ 2.0

</attribute>
</optional>
<ref name="scope.attrib"/>
</define>

<define name="scope.attrib">
<optional>
<attribute name="scope">
<choice>
<value>row</value>
<value>col</value>
<value>rowgroup</value>
<value>colgroup</value>
</choice>
</attribute>
</optional>
</define>
</div>

<define name="Structural.class" combine="choice">

</grammar>

C.2. XHTML RELAX NG Support Modules

The modules in this section are elements and attributes of the XHTML RELAX NG
implementation that, while hidden from casual users, are important to understand when creating
derivative markup languages using the Modularization architecture.

C.2.1. Datatypes
<?xml version="1.0" encoding="UTF-8"?>
<grammar xmlns="http://relaxng.org/ns/structure/1.0"
xmlns:x="http://www.w3.org/1999/xhtml"
datatypeLibrary="http://www.w3.org/2001/XMLSchema-datatypes">

<x:h1>Datatypes Module</x:h1>

<div>
<x:h2>Datatypes defined in XML 1.0</x:h2>

- 212 -
XHTML™ 2.0 C.2.1. Datatypes

<div>
<x:h2>Additional Datatypes</x:h2>

<define name="Character.datatype">
<x:p>A single character, as per section 2.2 of [XML].</x:p>
<data type="string">
<param name="length">1</param>
</data>
</define>

<define name="Encodings.datatype">
<x:p>A comma-separated list of ’charset’s with optional q parameters,
as defined in section 14.2 of [RFC2616] as the field value of
the Accept-Charset request header.</x:p>
<text/>
</define>

<define name="ContentTypes.datatype">
<x:p>A list of media ranges with optional accept parameters,
as defined in section 14.1 of [RFC2616] as the field value
of the accept request header.</x:p>
<text/>
</define>

<define name="Coordinates.datatype">
<x:p>Comma separated list of Lengths used in defining areas.</x:p>
<data type="string">
<param name="pattern">(\d+|\d+(\.\d+)?%)(,\s*(\d+|\d+(\.\d+)?%))*</param>
</data>
</define>

<define name="Datetime.datatype">
<x:p>Date and time information, as defined by the type dateTime
in [XMLSCHEMA].</x:p>
<data type="dateTime"/>
</define>

<define name="HrefTarget.datatype">
<x:p>Name used as destination for results of certain actions.</x:p>

- 213 -
C.2.1. Datatypes XHTML™ 2.0

<define name="LanguageCode.datatype">
<x:p>A language code, as per [RFC3066].</x:p>
<data type="language"/>
</define>

<define name="LanguageCodes.datatype">
<x:p>A comma-separated list of language ranges.</x:p>
<text/>
</define>

<define name="Length.datatype">
<x:p>The value may be either in pixels or a percentage of the available
horizontal or vertical space. Thus, the value "50%" means half of
the available space.</x:p>
<data type="string">
<param name="pattern">(\d+|\d+(\.\d+)?%)</param>
</data>
</define>

<define name="LocationPath.datatype">
<x:p>A location path as defined in [XPATH].</x:p>
<text/>
</define>

<define name="LinkTypes.datatype">
<x:p>The value is a QName.</x:p>
<choice>
<value>alternate</value>
<value>start</value>
<value>next</value>
<value>prev</value>
<value>up</value>
<value>contents</value>
<value>index</value>
<value>glossary</value>
<value>copyright</value>
<value>chapter</value>
<value>section</value>
<value>subsection</value>
<value>appendix</value>
<value>help</value>
<value>bookmark</value>
<value>meta</value>
<value>icon</value>
<value>p3pv1</value>
<value>profile</value>
<value>role</value>
<value>cite</value>
<ref name="QName.datatype"/>
</choice>
</define>

<define name="MediaDesc.datatype">
<x:p>A comma-separated list of media descriptors as described by [CSS].

- 214 -
XHTML™ 2.0 C.2.1. Datatypes

The default is all.</x:p>

<define name="Number.datatype">
<x:p>One or more digits (NUMBER).</x:p>
<data type="nonNegativeInteger">
<param name="pattern">[0-9]+</param>
</data>
</define>

<define name="spanNumber.datatype">
<x:p>span: this attribute value must be an integer > 0;
the default value is 1.</x:p>
<data type="positiveInteger">
<param name="pattern">[0-9]+</param>
</data>
</define>

<define name="QName.datatype">
<x:p>An [XMLNS]-qualified name.</x:p>
<data type="QName"/>
</define>

<define name="QNames.datatype">
<x:p>One or more white space separated QName values.</x:p>
<list>
<oneOrMore>
<data type="QName"/>
</oneOrMore>
</list>
</define>

<define name="prefixedQName.datatype">
<x:p>An [XMLNS]-qualified name.</x:p>
<data type="QName">
<param name="pattern">[\i-[:]][\c-[:]]*:[\i-[:]][\c-[:]]*</param>
</data>
</define>

<define name="Property.datatype">
<x:p>The value is a QName.</x:p>
<choice>
<value>reference</value>
<value>description</value>
<value>generator</value>
<value>keywords</value>
<value>robots</value>
<value>title</value>
<ref name="prefixedQName.datatype"/>
</choice>
</define>

<define name="Role.datatype">
<x:p>The value is a list of QNames.</x:p>

- 215 -
C.2.2. Events XHTML™ 2.0

<list>
<oneOrMore>
<choice>
<value>main</value>
<value>secondary</value>
<value>navigation</value>
<value>banner</value>
<value>contentinfo</value>
<value>note</value>
<value>seealso</value>
<value>search</value>
<ref name="prefixedQName.datatype"/>
</choice>
</oneOrMore>
</list>
</define>

<define name="Shape.datatype">
<x:p>The shape of a region.</x:p>
<choice>
<value>default</value>
<value>rect</value>
<value>circle</value>
<value>poly</value>
</choice>
</define>

<define name="Text.datatype">
<x:p>Arbitrary textual data, likely meant to be human-readable.</x:p>
<text/>
</define>

<define name="URI.datatype">
<x:p>A Uniform Resource Identifier Reference, as defined by the type
anyURI in [XMLSCHEMA].</x:p>
<data type="anyURI"/>
</define>

<define name="URIs.datatype">
<x:p>A space-separated list of URIs as defined above.</x:p>
<list>
<oneOrMore>
<data type="anyURI"/>
</oneOrMore>
</list>
</define>
</div>

</grammar>

C.2.2. Events
<?xml version="1.0" encoding="UTF-8"?>
<grammar xmlns="http://relaxng.org/ns/structure/1.0"
xmlns:ev="http://www.w3.org/2001/xml-events"
xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0"

- 216 -
XHTML™ 2.0 C.2.2. Events

xmlns:x="http://www.w3.org/1999/xhtml">

<x:h1>Events Attribute Collection Module</x:h1>

<define name="Events.attrib">
<optional>
<attribute name="ev:event">
<ref name="NMTOKEN.datatype"/>
</attribute>
</optional>
<optional>
<attribute name="ev:observer">
<ref name="IDREF.datatype"/>
</attribute>
</optional>
<optional>
<attribute name="ev:target">
<ref name="IDREF.datatype"/>
</attribute>
</optional>
<optional>
<attribute name="ev:handler">
<ref name="URI.datatype"/>
</attribute>
</optional>
<optional>
<attribute name="ev:phase" a:defaultValue="default">
<choice>
<value>capture</value>
<value>default</value>
</choice>
</attribute>
</optional>
<optional>
<attribute name="ev:propagate" a:defaultValue="continue">
<choice>
<value>stop</value>
<value>continue</value>
</choice>
</attribute>
</optional>
<optional>
<attribute name="ev:defaultAction" a:defaultValue="perform">
<choice>
<value>cancel</value>
<value>perform</value>
</choice>
</attribute>
</optional>
</define>

<define name="Common.attrib" combine="interleave">

<define name="head.misc" combine="choice">

- 217 -
C.2.3. Param XHTML™ 2.0

</define>

</grammar>

C.2.3. Param
<?xml version="1.0" encoding="UTF-8"?>
<grammar xmlns="http://relaxng.org/ns/structure/1.0"
xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0"
xmlns:x="http://www.w3.org/1999/xhtml">

<x:h1>Param Module</x:h1>

<div>
<x:h2>The param element</x:h2>

<define name="param.attlist">
<optional>
<ref name="id.attrib"/>
</optional>
<attribute name="name"/>
<optional>
<attribute name="value"/>
</optional>
<optional>
<attribute name="valuetype" a:defaultValue="data">
<choice>
<value>data</value>
<value>ref</value>
<value>object</value>
</choice>
</attribute>
</optional>
<optional>
<attribute name="type">
<ref name="ContentTypes.datatype"/>
</attribute>
</optional>
</define>
</div>

</grammar>

- 218 -
XHTML™ 2.0 C.3. RELAX NG External Modules

C.2.4. Caption
<?xml version="1.0" encoding="UTF-8"?>
<grammar xmlns="http://relaxng.org/ns/structure/1.0"
xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0"
xmlns:x="http://www.w3.org/1999/xhtml">

<x:h1>Caption Module</x:h1>

<div>
<x:h2>The caption element</x:h2>

</grammar>

C.2.5. Role Attribute

<?xml version="1.0" encoding="UTF-8"?>
<grammar xmlns="http://relaxng.org/ns/structure/1.0"
xmlns:x="http://www.w3.org/1999/xhtml">

<x:h1>Role Attribute Module</x:h1>

<define name="Common.attrib" combine="interleave">

</grammar>

C.3. RELAX NG External Modules

These modules are not defined by XHTML, but these definitions are included here for
completeness.

- 219 -
C.3.1. Ruby XHTML™ 2.0

C.3.1. Ruby
<?xml version="1.0" encoding="UTF-8"?>
<grammar xmlns="http://relaxng.org/ns/structure/1.0"
xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0"
xmlns:x="http://www.w3.org/1999/xhtml"
datatypeLibrary="http://www.w3.org/2001/XMLSchema-datatypes">

<x:h1>Ruby Module in RELAX NG</x:h1>

<x:pre>
Ruby Elements

ruby, rbc, rtc, rb, rt, rp

This module defines grammars to support ruby annotation markup.

This module is based on the W3C Ruby Annotation Specification:

http://www.w3.org/TR/ruby

Editor: Masayasu Ishikawa <[email protected]>

Revision: $Id: ruby-1.rng,v 1.9 2004/07/21 09:46:41 mimasa Exp $

Permission to use, copy, modify and distribute this RELAX NG schema

for Ruby Annotation and its accompanying documentation for any purpose
and without fee is hereby granted in perpetuity, provided that the above
copyright notice and this paragraph appear in all copies. The copyright
holders make no representation about the suitability of this RELAX NG
schema for any purpose.

It is provided "as is" without expressed or implied warranty.

For details, please refer to the W3C software license at:

<x:a href="http://www.w3.org/Consortium/Legal/copyright-software"
>http://www.w3.org/Consortium/Legal/copyright-software</x:a>
</x:pre>

<div>
<x:h2>patterns for the content model of the ruby element</x:h2>

<define name="Ruby.content.simple">
<x:p>Content model of simple ruby</x:p>
<group>
<ref name="rb"/>
<choice>
<ref name="rt-simple"/>
<group>
<ref name="rp"/>
<ref name="rt-simple"/>
<ref name="rp"/>
</group>
</choice>
</group>
</define>

- 220 -
XHTML™ 2.0 C.3.1. Ruby

<define name="Ruby.content.complex">
<x:p>Content model of complex ruby</x:p>
<group>
<ref name="rbc"/>
<ref name="rtc"/>
<optional>
<ref name="rtc"/>
</optional>
</group>
</define>

<define name="Ruby.content">
<x:p>Simple ruby is used by default</x:p>
<ref name="Ruby.content.simple"/>
</define>
</div>

<div>
<x:h2>Ruby Elements</x:h2>

<x:h3>ruby element</x:h3>

<x:h3>rbc (ruby base component) element</x:h3>

<x:h3>rtc (ruby text component) element</x:h3>

<x:h3>rb (ruby base) element</x:h3>

- 221 -
C.3.1. Ruby XHTML™ 2.0

<x:h3>rt (ruby text) element</x:h3>

<define name="rt-simple">
<x:p>grammar for simple ruby</x:p>
<x:p>rbspan attribute is not allowed in simple ruby</x:p>
<element name="rt">
<ref name="NoRuby.content"/>
<ref name="Ruby.common.attrib"/>
</element>
</define>

<define name="rt-complex">
<x:p>grammar for complex ruby</x:p>
<element name="rt">
<ref name="NoRuby.content"/>
<ref name="Ruby.common.attrib"/>
<optional>
<attribute name="rbspan" a:defaultValue="1">
<data type="positiveInteger">
<param name="pattern">[1-9][0-9]*</param>
</data>
</attribute>
</optional>
</element>
</define>

<x:h3>rp (ruby parenthesis) element</x:h3>

<div>
<x:h2>Ruby Common Attributes</x:h2>

<x:p>Ruby elements are intended to have common attributes of its

parent markup language. The pattern "Common.attrib" MUST be
defined to integrate this module.</x:p>

<div>
<x:p>Content models of the rb and the rt elements are intended to
allow other inline-level elements of its parent markup language,
but it should not include ruby descendent elements. This RELAX NG
module itself doesn’t check nesting of ruby elements.

- 222 -
XHTML™ 2.0 C.3.2. Ruby Driver for Full Ruby Markup

The patterns "Inline.class" and "Inline.model" MUST be defined

to integrate this module.</x:p>

<define name="Inline.class" combine="choice">

</grammar>

C.3.2. Ruby Driver for Full Ruby Markup

<?xml version="1.0" encoding="UTF-8"?>
<grammar xmlns="http://relaxng.org/ns/structure/1.0"
xmlns:x="http://www.w3.org/1999/xhtml">

<x:h1>Ruby Module in RELAX NG for full ruby markup</x:h1>

Editor: Masayasu Ishikawa <[email protected]>

Revision: $Id: full-ruby-1.rng,v 1.4 2003/04/30 06:50:03 mimasa Exp $
</x:pre>

<define name="Ruby.content" combine="choice">

<x:p>Allow complex ruby markup in addition to simple ruby markup</x:p>
<ref name="Ruby.content.complex"/>
</define>

</grammar>

C.3.3. XML Events

<?xml version="1.0" encoding="UTF-8"?>
<grammar ns="http://www.w3.org/2001/xml-events"
xmlns="http://relaxng.org/ns/structure/1.0"
xmlns:ev="http://www.w3.org/2001/xml-events"
xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0"
xmlns:x="http://www.w3.org/1999/xhtml"
datatypeLibrary="http://www.w3.org/2001/XMLSchema-datatypes">

<x:h1>XML Events Module in RELAX NG</x:h1>

Editor: Masayasu Ishikawa <[email protected]>

Revision: $Id: xml-events-1.rng,v 1.6 2003/04/30 06:50:03 mimasa Exp $

- 223 -
C.3.3. XML Events XHTML™ 2.0

Permission to use, copy, modify and distribute this RELAX NG schema

for XML Events and its accompanying documentation for any purpose and
without fee is hereby granted in perpetuity, provided that the above
copyright notice and this paragraph appear in all copies. The copyright
holders make no representation about the suitability of this RELAX NG
schema for any purpose.

It is provided "as is" without expressed or implied warranty.

For details, please refer to the W3C software license at:

<x:a href="http://www.w3.org/Consortium/Legal/copyright-software"
>http://www.w3.org/Consortium/Legal/copyright-software</x:a>
</x:pre>

<define name="listener.attlist">
<optional>
<attribute name="event">
<data type="NMTOKEN"/>
</attribute>
</optional>
<optional>
<attribute name="observer">
<data type="IDREF"/>
</attribute>
</optional>
<optional>
<attribute name="target">
<data type="IDREF"/>
</attribute>
</optional>
<optional>
<attribute name="handler">
<data type="anyURI"/>
</attribute>
</optional>
<optional>
<attribute name="phase" a:defaultValue="default">
<choice>
<value>capture</value>
<value>default</value>
</choice>
</attribute>
</optional>
<optional>
<attribute name="propagate" a:defaultValue="continue">
<choice>
<value>stop</value>
<value>continue</value>
</choice>
</attribute>
</optional>

- 224 -
XHTML™ 2.0 C.3.4. XML Schema instance

<optional>
<attribute name="defaultAction" a:defaultValue="perform">
<choice>
<value>cancel</value>
<value>perform</value>
</choice>
</attribute>
</optional>
<optional>
<attribute name="id">
<data type="ID"/>
</attribute>
</optional>
</define>

</grammar>

C.3.4. XML Schema instance

<?xml version="1.0" encoding="UTF-8"?>
<grammar xmlns="http://relaxng.org/ns/structure/1.0"
ns="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
datatypeLibrary="http://www.w3.org/2001/XMLSchema-datatypes">

</grammar>

- 225 -
C.3.4. XML Schema instance XHTML™ 2.0

- 226 -
XHTML™ 2.0 D. XHTML 2.0 Schema

D. XHTML 2.0 Schema

This appendix is normative.

This appendix will contain the implementation of the XHTML 2.0 Schema driver file and content
model file.

- 227 -
D. XHTML 2.0 Schema XHTML™ 2.0

- 228 -
XHTML™ 2.0 E. XHTML Schema Module Implementations

E. XHTML Schema Module Implementations

This appendix is normative.

This appendix will contain implementations of the modules defined in this specification via XML
Schema [XMLSCHEMA [p.249] ].

- 229 -
E. XHTML Schema Module Implementations XHTML™ 2.0

- 230 -
XHTML™ 2.0 F. XHTML 2.0 Document Type Definition

F. XHTML 2.0 Document Type Definition

This appendix is normative.

This appendix will contain the implementation of the XHTML 2.0 DTD driver file and content
model file.

F.1. Issues
Entity management: do we still need it? PR #670
State: Approved
Resolution: Accepted
User: Agree

Notes:
We will support both XML Catalogs and SGML Open Catalogs for XHTML 2.

Character entities: do we still need them? PR #671

State: Approved
Resolution: Accepted
User: None

Notes:
The WG believes that there’s still a need for character entities. We need to find a solution. On 9
September 2003, the WG agrees to retain character entities; DTDs therefore still necessary; it
might be possible to supply a DTD that only provides the entities.

- 231 -
F.1. Issues XHTML™ 2.0

- 232 -
XHTML™ 2.0 G. XHTML DTD Module Implementations

G. XHTML DTD Module Implementations

This appendix is normative.

This appendix will contain implementations of the modules defined in this specification. These
module implementations can be used in other XHTML Family Document Types.

G.1. XHTML Modular Framework

In order to take advantage of the XHTML DTD Modules, DTD authors need to define the content
model for their DTD. XHTML provides a variety of tools to ease this effort. They are defined in a
set of support modules, instantiated by a main Framework module:

Note that the module above references a content model module. This module is defined on a
per-document type basis in addition to the document type driver file.

G.2. XHTML Module Implementations

This section will contain the formal definition of each of the XHTML Abstract Modules as a DTD
module.

G.3. XHTML DTD Support Modules

The modules in this section are elements of the XHTML DTD implementation that, while hidden
from casual users, are important to understand when creating derivative markup languages
using the Modularization architecture.

- 233 -
G.3. XHTML DTD Support Modules XHTML™ 2.0

- 234 -
XHTML™ 2.0 H. Style sheet for XHTML 2

H. Style sheet for XHTML 2

This appendix is normative.

This Appendix defines a normative [CSS2 [p.247] ] style sheet for XHTML 2. While visual user
agents implementing XHTML 2 are not required to support CSS2, their default behavior should
be as if the following CSS2 styles are in effect. Note that this default behavior can be overridden
by any number of things - including, for example, user-defined preferences.
@namespace url("http://www.w3.org/2002/06/xhtml2/");

/* A sample style sheet for XHTML 2.0

This style sheet describes a very incomplete, sample rendering of

XHTML 2.0 elements.

Editor: Masayasu Ishikawa <[email protected]>

Revision: $Id: xhtml2.css,v 1.1.2.13 2006/01/13 15:06:29 ahby Exp $
*/

/* new elements */

section, h, nl, label, l, blockcode, separator, di

{ display: block; }
section, h, nl, label, l, blockcode, di
{ unicode-bidi: embed }
nl { margin: 1.33em 0 }
summary, standby, handler
{ display: none }
blockcode { font-family: monospace; white-space: pre }
separator { border-bottom: thin black solid; border: 1px;
inset; width 100%}
h { display: block; font-weight: bolder; font-family: sans-serif }
h1, h2, h3, h4, h5, h6
{ font-family: sans-serif; font-weight: bolder }
body h, h1 {
font-size: 2em;
margin: .67em 0;
}

section h, h2 {
font-size: 1.5em;
margin: .83em 0;
}

section section h, h3 {
font-size: 1.17em;
margin: 1em 0;
}

section section section h, h4, p, blockquote, ul, ol, dl

{ margin: 1.33em 0; }

section section section section h, h5 {

font-size: .83em;

- 235 -
H. Style sheet for XHTML 2 XHTML™ 2.0

line-height: 1.17em;
margin: 1.67em 0;
}

section section section section section h, h6 {

font-size: .67em;
margin: 2.33em 0;
}

*[edit="deleted"] { display: none }

/* no special presentation by default
*[edit="inserted"] { }
*[edit="changed"] { }
*[edit="moved"] { }
*/

/* experimental navigation list style */

nl {
height: 1.5em;
overflow: hidden;
margin: 0;
line-height: normal !important;
white-space: nowrap;
text-align: start;
cursor: default;
border-width: 2px !important;
border-style: inset !important;
vertical-align: baseline;
padding: 0;
}

nl:hover { height: auto; overflow: visible; }

nl > li, nl > label {

display: block;
min-height: 1em;
line-height: normal !important;
}
nl > li, nl > label {
padding: 0 5px 0 3px;
}
nl > li {
margin-left: 1em;
}
nl > label {
font-weight: bold;
}

nl > nl > label {

display: block;
line-height: normal !important;
font-style: italic;
font-weight: bold;
}

nl > nl > li {

- 236 -
XHTML™ 2.0 H. Style sheet for XHTML 2

padding-left: 2em;
font-style: normal;
font-weight: normal;
}

/* inherited elements */

html, body, div, p, h1, h2, h3, h4, h5, h6,

address, blockquote, pre, ol, ul, dl, dt, dd
{ display: block }
li { display: list-item }
head, style, link, meta
{ display: none }
table { display: table;
border-spacing: 0;
border-top: thin black solid;
border-left: thin black solid }
tr { display: table-row }
thead { display: table-header-group }
tbody { display: table-row-group }
tfoot { display: table-footer-group }
col { display: table-column }
colgroup { display: table-column-group }
td, th { display: table-cell;
border-right: thin black solid;
border-bottom: thin black solid;
padding 2px }
caption { display: table-caption }
table:hover summary { display: block }
th { font-weight: bolder; text-align: center }
caption { text-align: center }
body { padding: 8px; line-height: 1.2 }
strong { font-weight: bolder }
blockquote { margin-left: 4em; margin-right: 4em }
cite, em, q, var, address
{ font-style: italic }
pre code, kbd, samp
{ font-family: monospace }
pre { white-space: pre }
sub, sup { font-size: smaller }
sub { vertical-align: sub }
sup { vertical-align: super }
ol, ul, dd { margin-left: 4em }
ol { list-style-type: decimal }
ol ul, ul ol, ul ul, ol ol
{ margin-top: 0; margin-bottom: 0 }

abbr[title] { border-bottom: dotted 1px }

:link { text-decoration: underline; color: blue; }
:focus { outline: thin dotted invert }

/* Hover effects should be default */

:link:hover,:link:visited { color: #b7f }

/* begin bidirectionality settings (do not change) */

- 237 -
H. Style sheet for XHTML 2 XHTML™ 2.0

*[dir="ltr"] { direction: ltr; unicode-bidi: embed }

*[dir="rtl"] { direction: rtl; unicode-bidi: embed }
*[dir="lro"] { direction: ltr; unicode-bidi: bidi-override }
*[dir="rlo"] { direction: rtl; unicode-bidi: bidi-override }

/* block-level elements */
body, div, p, hr, h1, h2, h3, h4, h5, h6,
address, blockquote, pre, ol, ul, li, di, dt, dd,
table, thead, tbody, tfoot, tr, td, th,
col, colgroup, caption, object, summary, standby, blockcode
{ unicode-bidi: embed }
/* end bidi settings */

/* end xhtml2.css */

- 238 -
XHTML™ 2.0 I. Example RDF Specification for Roles

I. Example RDF Specification for Roles

This appendix is informative.

This Appendix will define an example RDF specification for the XHTML 2 namespace role
attribute values.

- 239 -
I. Example RDF Specification for Roles XHTML™ 2.0

- 240 -
XHTML™ 2.0 J. List of Elements

J. List of Elements
This appendix is informative.

This appendix will contain a list of elements defined in this specification, sorted in alphabetical
order, with some other relevant information and links to the element definitions.

Element Name Module Description

- 241 -
J. List of Elements XHTML™ 2.0

- 242 -
XHTML™ 2.0 K. List of Attributes

K. List of Attributes
This appendix is informative.

Attribute Name Module Description

- 243 -
K. List of Attributes XHTML™ 2.0

- 244 -
XHTML™ 2.0 L. Cross-reference Index

L. Cross-reference Index
This appendix is informative.

This appendix will contain a detailed index of this document, with links to the indexed terms.

- 245 -
L. Cross-reference Index XHTML™ 2.0

- 246 -
XHTML™ 2.0 M. References

M. References
This appendix is normative.

M.1. Normative References

[CSS2]
"Cascading Style Sheets, level 2 (CSS2) Specification", W3C Recommendation, B. Bos et
al., eds., 12 May 1998.
Available at: http://www.w3.org/TR/1998/REC-CSS2-19980512
[CSS3-TEXT]
"CSS3 Text Effects Module", W3C Working Draft, E. J. Etemad, ed., 27 June 2005, work in
progress.
Available at: http://www.w3.org/TR/2005/WD-css3-text-20050627/
The latest version is available at: http://www.w3.org/TR/css3-text/
[DCORE]
"DCMI Metadata Terms", 13 June 2005.
Available at: http://dublincore.org/documents/dcmi-terms/
[DOM]
"Document Object Model (DOM) Level 2 Core Specification", W3C Recommendation, A.
Le Hors et al., eds., 13 November 2000.
Available at: http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113
A list of DOM Level 2 specifications can be found at:
http://www.w3.org/DOM/DOMTR#dom2
[DOMEVENTS]
"Document Object Model (DOM) Level 2 Events Specification", W3C Recommendation, T.
Pixley, ed., 13 November 2000.
Available at: http://www.w3.org/TR/2000/REC-DOM-Level-2-Events-20001113
A list of DOM Level 2 specifications can be found at:
http://www.w3.org/DOM/DOMTR#dom2
[IRI]
"Internationalized Resource Identifiers (IRIs)", RFC 3987, M. Dürst and M. Suignard,
January 2005.
Available at: http://www.rfc-editor.org/rfc/rfc3987.txt
[MIMETYPES]
List of registered content types (MIME media types). Download a list of registered content
types from http://www.iana.org/assignments/media-types/.
[P3P]
"The Platform for Privacy Preferences 1.0 (P3P1.0) Specification", W3C Recommendation,
L. Cranor et al., 16 April 2002.
Available at: http://www.w3.org/TR/2002/REC-P3P-20020416/
[RELAXNG]
"RELAX NG Specification", OASIS Committee Specification, J. Clark, Murata M., eds., 3
December 2001.
Available at: http://relaxng.org/spec-20011203.html
RELAX NG has been standardized as part of ISO/IEC 19757 - Document Schema

- 247 -
M.1. Normative References XHTML™ 2.0

Definition Languages (DSDL), as ISO/IEC 19757-2:2003 "Information technology --

Document Schema Definition Language (DSDL) -- Part 2: Regular-grammar-based
validation -- RELAX NG". See home page for Document Schema Definition Languages at
http://dsdl.org/ for details.
[RFC2045]
"Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message
Bodies", RFC 2045, N. Freed and N. Borenstein, November 1996.
Available at: http://www.rfc-editor.org/rfc/rfc2045.txt
[RFC2119]
"Key words for use in RFCs to indicate requirement levels", RFC 2119, S. Bradner, March
1997.
Available at: http://www.rfc-editor.org/rfc/rfc2119.txt
[RFC2616]
"Hypertext Transfer Protocol -- HTTP/1.1", RFC 2616, R. Fielding et al., June 1999.
Available at: http://www.rfc-editor.org/rfc/rfc2616.txt
[RFC3066]
"Tags for the Identification of Languages", RFC 3066, H. Alvestrand, January 2001.
Available at: http://www.rfc-editor.org/rfc/rfc3066.txt
[RUBY]
"Ruby Annotation", W3C Recommendation, M. Sawicki et al., eds., 31 May 2001.
Available at: http://www.w3.org/TR/2001/REC-ruby-20010531
[SGML]
"Information Processing -- Text and Office Systems -- Standard Generalized Markup
Language (SGML)", ISO 8879:1986.
Please consult the ISO Web site at http://www.iso.org/ for information about the standard, or
http://www.oasis-open.org/cover/general.html#overview about SGML.
[UAX9]
"Unicode Standard Annex #9: The Bidirectional Algorithm", M. Davis, 25 March 2005.
Available at: http://www.unicode.org/reports/tr9/tr9-15.html
The latest version of UAX #9 is available at: http://www.unicode.org/reports/tr9/
[URI]
"Uniform Resource Identifiers (URI): Generic Syntax", RFC 3986, T. Berners-Lee et al.,
January 2005.
Available at: http://www.rfc-editor.org/rfc/rfc3986.txt.
[XFORMS]
"XForms 1.1", W3C Working Draft, M. Dubinko et al., eds., 15 November 2004.
Available at: http://www.w3.org/TR/2004/WD-xforms11-20041115/
[XHTMLMOD]
"Modularization of XHTML", W3C Recommendation, M. Altheim et al., eds., 10 April 2001
Available at: http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410
[XML]
"Extensible Markup Language (XML) 1.0 (Third Edition)", W3C Recommendation, T. Bray et
al., eds., 4 February 2004.
Available at: http://www.w3.org/TR/2004/REC-xml-20040204
[XMLBASE]
"XML Base", W3C Recommendation, J. Marsh, ed., 27 June 2001.

- 248 -
XHTML™ 2.0 M.2. Informative References

Available at: http://www.w3.org/TR/2001/REC-xmlbase-20010627/

[XMLEVENTS]
"XML Events", W3C Recommendation, S. McCarron et al., eds., 14 October 2003.
Available at: http://www.w3.org/TR/2003/REC-xml-events-20031014
[XMLID]
"xml:id Version 1.0", W3C Recommendation, J. Marsh, D. Veillard, N. Walsh, eds., 9
September 2005.
Available at: http://www.w3.org/TR/2005/REC-xml-id-20050909/
[XMLNS]
"Namespaces in XML", W3C Recommendation, T. Bray et al., eds., 14 January 1999.
Available at: http://www.w3.org/TR/1999/REC-xml-names-19990114
[XMLSCHEMA]
"XML Schema Part 1: Structures Second Edition", W3C Recommendation, H. S. Thompson
et al., eds., 28 October 2004.
Available at: http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/
"XML Schema Part 2: Datatypes Second Edition", W3C Recommendation, P. V. Biron, A.
Malhotra, eds., 28 October 2004.
Available at: http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/

M.2. Informative References

[HTML4]
"HTML 4.01 Specification", W3C Recommendation, D. Raggett et al., eds., 24 December
1999.
Available at: http://www.w3.org/TR/1999/REC-html401-19991224
[RDF]
"Resource Description Framework (RDF): Concepts and Abstract Syntax ", W3C
Recommendation, G. Klyne, J. Carrol, ed., 10 February 2004.
Available at: http://www.w3.org/TR/2004/REC-rdf-concepts-20040210/
[SVG]
"Scalable Vector Graphics (SVG) 1.1 Specification", Jon Ferraiolo et al.
Available at: http://www.w3.org/TR/SVG/
[WAIRDF]
"Role Taxonomy for Accessible Adaptable Applications". L. Seeman, 8 May 2006.
Available at: http://www.w3.org/WAI/PF/GUI/roleTaxonomy-20060508.html
The latest version is available at: http://www.w3.org/WAI/PF/GUI/
[XFRAMES]
"XFrames", W3C Working Draft, S. Pemberton, ed., 6 August 2002, work in progress.
Available at: http://www.w3.org/TR/2002/WD-xframes-20020806
[XLINK]
"XML Linking Language (XLink) Version 1.0", W3C Recommendation, S. DeRose et al.,
eds., 27 June 2001.
Available at: http://www.w3.org/TR/2001/REC-xlink-20010627/
[XMLSTYLE]
"Associating Style Sheets with XML documents Version 1.0", W3C Recommendation, J.
Clark, ed., 29 June 1999.

- 249 -
M.2. Informative References XHTML™ 2.0

Available at: http://www.w3.org/1999/06/REC-xml-stylesheet-19990629

[XPATH]
"XML Path Language (XPath) Version 1.0", W3C Recommendation, J. Clark et al., eds., 16
November 1999.
Available at: http://www.w3.org/TR/1999/REC-xpath-19991116

- 250 -
XHTML™ 2.0 N. Acknowledgements

N. Acknowledgements
This appendix is informative.

This specification was prepared by the W3C HTML Working Group. The participants at the time
of publication were:

This section will be updated at publication time.

The HTML Working Group would like to acknowledge the great many people outside of the
HTML Working Group who help with the process of developing the XHTML 2.0 specification.
These people are too numerous to list individually. They include but are not limited to people
who have contributed on the [email protected] mailing list, other Working Groups at the W3C,
and the W3C Team. XHTML 2.0 is truly a cooperative effort between the HTML Working Group,
the rest of the W3C, and the public.

- 251 -

6th Central Pay Commission Salary Calculator
100% (436)
6th Central Pay Commission Salary Calculator
15 pages
Typography After Modernism
100% (2)
Typography After Modernism
34 pages
IS221 Week2 Lecture
No ratings yet
IS221 Week2 Lecture
9 pages
Advanced Concepts in HTML 1
No ratings yet
Advanced Concepts in HTML 1
30 pages
Why XHTML?: Your Webpages Can Be Easily Parsed and Processed by Present and Future Web Browsers
No ratings yet
Why XHTML?: Your Webpages Can Be Easily Parsed and Processed by Present and Future Web Browsers
14 pages
XHTML
No ratings yet
XHTML
15 pages
Markup Languages: XHTML 1.0
No ratings yet
Markup Languages: XHTML 1.0
172 pages
Chapte 2 HTML 2021 V-F
No ratings yet
Chapte 2 HTML 2021 V-F
179 pages
The Most Important Differences:: What Is XHTML?
No ratings yet
The Most Important Differences:: What Is XHTML?
5 pages
XHTML
No ratings yet
XHTML
19 pages
Presentation Technologies
No ratings yet
Presentation Technologies
9 pages
Java Script
No ratings yet
Java Script
136 pages
Why HTML5? Why Not XHTML2?: Learning From History How To Drive The Future of The Web
No ratings yet
Why HTML5? Why Not XHTML2?: Learning From History How To Drive The Future of The Web
62 pages
XHTML Extensible Markup Language
No ratings yet
XHTML Extensible Markup Language
98 pages
Mark Up Languages 07022024
No ratings yet
Mark Up Languages 07022024
104 pages
Module-1: Introduction To HTML and Introduction To Css 1.1. What Is HTML and Where Did It Come From?
No ratings yet
Module-1: Introduction To HTML and Introduction To Css 1.1. What Is HTML and Where Did It Come From?
41 pages
HTML Mastery Semantics Standards And Styling 1st Edition Paul Haine - The latest ebook version is now available for instant access
100% (3)
HTML Mastery Semantics Standards And Styling 1st Edition Paul Haine - The latest ebook version is now available for instant access
48 pages
1.1 Introduction To HTML (Hypertext Markup Language)
No ratings yet
1.1 Introduction To HTML (Hypertext Markup Language)
19 pages
2.1 - The Overview and Comparation of HTML and XHTML
No ratings yet
2.1 - The Overview and Comparation of HTML and XHTML
33 pages
Chapter2 Introduction To XHTML
No ratings yet
Chapter2 Introduction To XHTML
42 pages
HTML Mastery Semantics Standards And Styling 1st Edition Paul Haine - Download the ebook today and own the complete content
100% (3)
HTML Mastery Semantics Standards And Styling 1st Edition Paul Haine - Download the ebook today and own the complete content
54 pages
XHTML and CSS: Rick Ells UW Technology
No ratings yet
XHTML and CSS: Rick Ells UW Technology
45 pages
Lecture16-XHTML Damir Cecil 4
No ratings yet
Lecture16-XHTML Damir Cecil 4
9 pages
XHTML
No ratings yet
XHTML
28 pages
Tutorial 1 Developing A Basic Web Page
No ratings yet
Tutorial 1 Developing A Basic Web Page
62 pages
Web Programming: Introduction To HTML and XHTML
No ratings yet
Web Programming: Introduction To HTML and XHTML
28 pages
22PLC15A - Module 1 - 2022-23
No ratings yet
22PLC15A - Module 1 - 2022-23
60 pages
HTML and XHTML-Unit2 (2nd Part)
No ratings yet
HTML and XHTML-Unit2 (2nd Part)
50 pages
Unit 2,2.2a
No ratings yet
Unit 2,2.2a
56 pages
BPLCK105A - Module 1 - Final
100% (2)
BPLCK105A - Module 1 - Final
54 pages
Unit 1.2.1 XHTML
No ratings yet
Unit 1.2.1 XHTML
48 pages
WT-II-HTML & XHTML-Basic Tags 02
No ratings yet
WT-II-HTML & XHTML-Basic Tags 02
38 pages
03 XHTML
No ratings yet
03 XHTML
14 pages
Markup Languages
No ratings yet
Markup Languages
10 pages
It8078 Web Design and Management
0% (1)
It8078 Web Design and Management
35 pages
Developing Web Applications With XHTML:: Problems and Benefits
No ratings yet
Developing Web Applications With XHTML:: Problems and Benefits
35 pages
Module 1
No ratings yet
Module 1
74 pages
Internet 2nd Notes
No ratings yet
Internet 2nd Notes
15 pages
What Is XML?: Example
No ratings yet
What Is XML?: Example
33 pages
XHTML Basics
No ratings yet
XHTML Basics
46 pages
Wek 1-8 Web System and Technologies
No ratings yet
Wek 1-8 Web System and Technologies
65 pages
0 The story of HTML5
No ratings yet
0 The story of HTML5
4 pages
XHTML: Ewebtech Website Development
No ratings yet
XHTML: Ewebtech Website Development
5 pages
HTML Slides
100% (3)
HTML Slides
104 pages
Web Technologies Upto II Unit
No ratings yet
Web Technologies Upto II Unit
65 pages
HTML Lab1
No ratings yet
HTML Lab1
20 pages
WT M1 - HTML & CSS
No ratings yet
WT M1 - HTML & CSS
140 pages
18CS63 Mod-1
No ratings yet
18CS63 Mod-1
33 pages
19cse71 PDF
No ratings yet
19cse71 PDF
574 pages
XHTML (Extensible Hyper Text Markup Language)
No ratings yet
XHTML (Extensible Hyper Text Markup Language)
14 pages
VTU Exam Question Paper With Solution of 20MCA23 Web Technologies July-2022-Ashwini
No ratings yet
VTU Exam Question Paper With Solution of 20MCA23 Web Technologies July-2022-Ashwini
41 pages
What You Should Already Know: HTML Tutorial
No ratings yet
What You Should Already Know: HTML Tutorial
13 pages
HTML5 Specification
No ratings yet
HTML5 Specification
768 pages
CSC336-WT Lec3 Slides
No ratings yet
CSC336-WT Lec3 Slides
25 pages
HTML
No ratings yet
HTML
22 pages
Web Services II NOTES For ASP Beginners
No ratings yet
Web Services II NOTES For ASP Beginners
18 pages
Lesson 1 HTML
No ratings yet
Lesson 1 HTML
7 pages
1 Html5: Wai-Aria Landmark Roles Apis For Making It Easier To Create Web Applications
No ratings yet
1 Html5: Wai-Aria Landmark Roles Apis For Making It Easier To Create Web Applications
32 pages
HTML5 Ibm
No ratings yet
HTML5 Ibm
22 pages
Learn complete HTML and CSS in 7 days | "HTML & CSS Masterclass: Unleash Your Web Design Skills"
From Everand
Learn complete HTML and CSS in 7 days | "HTML & CSS Masterclass: Unleash Your Web Design Skills"
Prajwal
No ratings yet
Plain JavaScript: Learning the Front-End
From Everand
Plain JavaScript: Learning the Front-End
Roger Beans-Rivet
No ratings yet
Comprehensive Hyper Text Markup Language (HTML): A Tutorial Guide to Editing and Developing a responsive and Dynamic Website for Beginners.
From Everand
Comprehensive Hyper Text Markup Language (HTML): A Tutorial Guide to Editing and Developing a responsive and Dynamic Website for Beginners.
Ibrahim Nugwa Abdulrazak
No ratings yet
The Big Softice Howto: A Step by Step Guide
100% (1)
The Big Softice Howto: A Step by Step Guide
24 pages
Page Rank
No ratings yet
Page Rank
21 pages
User Guide Solaris 10
No ratings yet
User Guide Solaris 10
166 pages
Switch SMC
No ratings yet
Switch SMC
26 pages
Using Flash
100% (23)
Using Flash
678 pages
Fs726tp User Manual
No ratings yet
Fs726tp User Manual
46 pages
gsm7224 Manual 7200
No ratings yet
gsm7224 Manual 7200
228 pages
National Security Agency Ft. George G. Meade, MD
100% (1)
National Security Agency Ft. George G. Meade, MD
24 pages
817 1812 PDF
No ratings yet
817 1812 PDF
508 pages
NSA IT Security Guide
No ratings yet
NSA IT Security Guide
244 pages
First Responders Guide To Computer Forensics
100% (1)
First Responders Guide To Computer Forensics
169 pages
Fl8 Learning As2
100% (1)
Fl8 Learning As2
830 pages
HTML 40
No ratings yet
HTML 40
389 pages
Cisco Switch Security Configuration Guide
No ratings yet
Cisco Switch Security Configuration Guide
86 pages
A_Funeral_by_E_V_Lucas
No ratings yet
A_Funeral_by_E_V_Lucas
2 pages
BCCS NOTES UNIT-I - Nature and Scope of Communication
No ratings yet
BCCS NOTES UNIT-I - Nature and Scope of Communication
13 pages
Instant download (Ebook) BDD in Action: Behavior-Driven Development for the whole software lifecycle, 2nd Edition by John Ferguson Smart ISBN 9781617291654, 161729165X pdf all chapter
100% (8)
Instant download (Ebook) BDD in Action: Behavior-Driven Development for the whole software lifecycle, 2nd Edition by John Ferguson Smart ISBN 9781617291654, 161729165X pdf all chapter
81 pages
Speech On Teachers Day
No ratings yet
Speech On Teachers Day
2 pages
Continuous Integration With Jenkins ANT and
No ratings yet
Continuous Integration With Jenkins ANT and
51 pages
Wa0001.
No ratings yet
Wa0001.
4 pages
What Is A Technical Manual
No ratings yet
What Is A Technical Manual
5 pages
Home Assignment 21-1-6
No ratings yet
Home Assignment 21-1-6
6 pages
Shakespeare Guardian Article - D Patterson
No ratings yet
Shakespeare Guardian Article - D Patterson
13 pages
Final DCCN Practical File
No ratings yet
Final DCCN Practical File
14 pages
Observational Report 8607
No ratings yet
Observational Report 8607
4 pages
@DSATuz -- NEW DSAT practice test
No ratings yet
@DSATuz -- NEW DSAT practice test
13 pages
Hall 2020 Language and Gender
No ratings yet
Hall 2020 Language and Gender
22 pages
English Expose: Direct and Indirect Speech 1.
No ratings yet
English Expose: Direct and Indirect Speech 1.
7 pages
Wu et al. - 2022 - AI-assisted Synthesis in Next Generation EDA Promises, Challenges, and Prospects
No ratings yet
Wu et al. - 2022 - AI-assisted Synthesis in Next Generation EDA Promises, Challenges, and Prospects
8 pages
Story Analysis
No ratings yet
Story Analysis
5 pages
Vocabulary Check A: 1.1 Clothes and Accessories, Describing Clothes A
100% (1)
Vocabulary Check A: 1.1 Clothes and Accessories, Describing Clothes A
1 page
The Laburnum Top
No ratings yet
The Laburnum Top
9 pages
1historical Development of Philippine Literature
No ratings yet
1historical Development of Philippine Literature
53 pages
Python Unit 2
No ratings yet
Python Unit 2
13 pages
Active Voice
No ratings yet
Active Voice
9 pages
How To Prepare For The Illumination of Consciense
No ratings yet
How To Prepare For The Illumination of Consciense
44 pages
Glorious Institution - The Church in History (3&4 - 1517-1900s)
No ratings yet
Glorious Institution - The Church in History (3&4 - 1517-1900s)
171 pages
Malick (Bataan)
No ratings yet
Malick (Bataan)
1 page
Aquino Not So Deadly Words A Desciptive
No ratings yet
Aquino Not So Deadly Words A Desciptive
9 pages
COA Seminar Report
No ratings yet
COA Seminar Report
8 pages
LTTN 4-dịch kinh tế-tài chính
No ratings yet
LTTN 4-dịch kinh tế-tài chính
10 pages
All InRoads Tips and Tricks
No ratings yet
All InRoads Tips and Tricks
61 pages
modelcv
No ratings yet
modelcv
1 page