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.

Structure Module*
body, head, html, title
Block Text Module*
address, blockcode, blockquote, div, h, h1, h2, h3, h4, h5, h6, hr, p, pre, section
Inline Text Module*
abbr, cite, code, dfn, em, kbd, l, quote, samp, span, strong, sub, sup, var
Hypertext Module*
List Module*
dl, dt, dd, label, nl, ol, ul, li
Link Module
Metainformation Module
Object Module
object, param, standby
Scripting Module
noscript, script
Style Attribute Module
style attribute
Stylesheet Module
style element
Tables Module
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]
ruby, rbc, rtc, rb, rt, rp
XML Events Module [XMLEVENTS]
XForms Module [XFORMS]
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, value

Need a cohesive XHTML 2 content model definition

Currently the content model of XHTML 2 must be determined through a trolling of all the included modules. This section should define the members of the content model sets, and show the content model of each element. This will make it easier for consumers of this document to determine how things should hang together, and should serve as a normative guide for the development of implementations.

There are no additional definitions required by this document type. An implementation of this document type as a RELAX NG grammar is defined in Appendix B, as an XML Schema in Appendix D, and as a DTD in Appendix F.