Contents
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.
body, head, html, titleaddress, blockcode, blockquote, div, h, h1, h2, h3, h4, h5, h6, p, pre, section, separatorabbr, cite, code, dfn, em, kbd, l, quote, samp, span, strong, sub, sup, varadl, dt, dd, label, nl, ol, ul, liclass, id, and title attributeshref, hreftype, cite, target, rel, rev, access, nextfocus, prevfocus, and
xml:base attributesxml:lang attributedir attributeedit, and datetime attributessrc, and type attributesusemap, ismap, shape, and coords attributesabout, content, datatype, property, rel, resource, restype, and rev attributesmeta, linkobject, param, standbynoscript, scriptstyle attributestyle elementcaption, col, colgroup, summary, table, tbody, td, tfoot, th, thead, trXHTML 2.0 also uses the following externally defined modules:
ruby, rbc, rtc, rb, rt, rpaction, 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 attributeslistener element, and defaultAction, event, handler, objserver, phase, propagate, and target attributes in the [XMLEVENTS] namespaceAn 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.
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.