W3C

XHTML 1.1 - Module-based XHTML

W3C Working Draft 5 January 2000

This version:
http://www.w3.org/TR/2000/WD-xhtml11-20000105
( Single file version , Postscript version , PDF version , ZIP archive , or Gzip'd TAR archive )
Latest version:
http://www.w3.org/TR/xhtml11
Previous version:
http://www.w3.org/TR/1999/WD-xhtml11-19990910
Diff-marked version:
xhtml11-diff-20000105.html
Editors:
Murray Altheim , Sun Microsystems
Shane McCarron , Applied Testing and Technology

Abstract

This working draft defines a new XHTML document type that is based solely upon the module framework defined in Building XHTML Modules [ BUILDING ] and the modules defined in Modularization of XHTML [ XHTMLMOD ]. The purpose of this document type is to serve as the basis for future extended XHTML 'family' document types, and to provide a consistent, forward-looking document type cleanly separated from the deprecated, legacy functionality of HTML 4 [ HTML4 ] that was brought forward into XHTML 1.0 [ XHTML1 ] document types. Note that the materials in this document were formerly part of the Modularization of XHTML document, but have been separated out for editorial purposes.

Status of this document

This section describes the status of this document at the time of its publication. Other documents may supersede this document. The latest status of this document series is maintained at the W3C.

This is the "Last Call Working Draft" of "XHTML 1.1". The Last Call review period ends at 2359Z on 1 Feburary 2000. Please send review comments before the review period ends to www-html-editor@w3.org .

The Working Group anticipates asking the W3C Director to advance this document to Proposed Recommendation after the Working Group processes Last Call review comments and incorporates resolutions into the Guidelines.

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

This is a W3C Working Draft for review by W3C Members and other interested parties. It is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to use W3C Working Drafts as reference material or to cite them as other than "work in progress". This is work in progress and does not imply endorsement by, or the consensus of, either W3C or participants of the HTML WG Group.

A list of current W3C Recommendations and other technical documents can be found at http://www.w3.org/TR .

Quick Table of Contents

Full Table of Contents

1. Introduction

This section is normative .

With the introduction of the XHTML family of modules and document types, the W3C has helped move the Internet content-development community from the days of malformed, non-standard markup into the well formed, valid world of XML. In XHTML 1.0, this move was moderated by a goal of providing for easy migration of existing, HTML 4.0 (or earlier) based content to XHTML and XML. With the advent of the XHTML modules defined in Modularization of XHTML, the W3C has removed support for deprecated elements and attributes from the XHTML family. These elements and attributes were largely presentation oriented functionality that is better handled via style-sheets or client-specific default behavior.

Going forward, XHTML family document types will be based upon this new, more structural functional collection. In this specification, the W3C's HTML Working Group has defined an initial document type based solely upon modules. This document type is designed to be portable to a broad collection of client devices, and applicable to the majority of Internet content. Content developers who base their content upon the functionality expressed in this specification can be confident that it will be consistently portable across XHTML family conforming user agents.

2. Conformance Definition

This section is normative .

2.1. Document Conformance

This version of XHTML provides a definition of strictly conforming XHTML documents, which are restricted to elements and attributes from the XHTML 1.1 namespace.

2.1.1. Strictly Conforming Documents

A Strictly Conforming XHTML 1.1 Document is a document that requires only the facilities described as mandatory in this specification. Such a document must meet all of the following criteria:

  1. It must validate against the DTD found in Appendix C .

  2. The root element of the document must be <html> .

  3. The root element of the document must designate the XHTML namespace using the xmlns attribute [XMLNAMES] . The namespace designator for XHTML is " http://www.w3.org/1999/xhtml ".

  4. There must 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 C using its Formal Public Identifier. The system identifier may be modified appropriately.

    <!DOCTYPE
     html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
     "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
    

Here is an example of a minimal XHTML 1.1 document.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
    "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">


<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" >


  <head>
    <title>Virtual Library</title>
  </head>
  <body>
    <p>Moved to <a href="http://vlib.org/">vlib.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 are strongly encouraged to use XML declarations in all their documents. Such a declaration is required when the character encoding of the document is other than the default UTF-8 or UTF-16.

2.2. User Agent Conformance

A conforming user agent must meet all user agent conformance requirements defined in [ XHTMLMOD ].

3. The XHTML 1.1 Document Type

This section is normative .

The XHTML 1.1 document type is a fully functional document type with rich semantics. It is not, however, as varied in functionality as the XHTML 1.0 Transitional or Frameset document types. These document types defined many presentational components that are better handled through style sheets or other similar mechanisms. Moreover, since the XHTML 1.1 document type is based exclusively upon the facilities defined in the XHTML Modules, it does not contain any of the deprecated functionality of XHTML 1.0 nor of HTML 4.0. Despite these exceptions, or perhaps because of them, the XHTML 1.1 document type is a solid basis for future document types that are targeted at varied user agent environments.

The XHTML 1.1 document type is made up of the following abstract modules: Structure, Basic Text, Hypertext, List, Applet, Presentation, Edit, BDO, Forms, Tables, Image, Image Map, Intrinsic Events, Metainformation, Scripting, Stylesheet, and Link as defined in [ XHTMLMOD ], and the Ruby Annotation module as defined in [ RUBY ]. There are no additional definitions required by this document type. An implementation of this document type as an XML DTD is defined in Appendix C .

A. Changes from XHTML 1.0

This appendix is informative .

This Appendix describes the differences between XHTML 1.1 and XHTML 1.0. XHTML 1.1 represents a departure from both HTML 4.0 and XHTML 1.0. Most significant is the removal of features that were deprecated. In addition, some features that were available have been removed. In general, the strategy is to define a markup language that is rich in structural functionality, but that relies upon style sheets for presentation.

In the table below, each element present in XHTML 1.0 is listed. For each element the table indicates whether it is supported, and if so whether the contant model has changed and whether the available attributes have changed.

Element Changes
ALL -lang
a -accesskey, -name, -tabindex, -target
abbr No change
acronym No change
address No change
applet No change
area -target
b No change
base Unsupported
basefont Unsupported
bdo No change
big No change
blockquote No change
body -background, -bgcolor, -text, -link, -vlink, -alink
br -clear
button No change
caption -align
center Unsupported
cite No change
code No change
col No change
colgroup No change
dd No change
del No change
dfn No change
dir No change
div -align
dl No change
dt No change
em No change
fieldset No change
font Unsupported
form No change
frame Unsupported
frameset Unsupported
h1 -align
h2 -align
h3 -align
h4 -align
h5 -align
h6 -align
head No change
hr -align, -noshade, -size, -width
html No change
i No change
iframe Unsupported
img -align, -border, -hspace, -vspace
input -align
ins No change
isindex Unsupported
kbd No change
label No change
legend -align
li -type, -value
link -target
map -name
menu Unsupported
meta No change
noframes Unsupported
noscript No change
object Unsupported
ol -compact, -start, -type
optgroup No change
option No change
p -align
param No change
pre -width
q No change
s Unsupported
samp No change
script -language
select No change
small No change
span No change
strike Unsupported
strong No change
style No change
sub No change
sup No change
table -align, -bgcolor
tbody No change
td -bgcolor, -height, -nowrap, -width
textarea No change
tfoot No change
th -bgcolor, -height, -nowrap, -width
thead No change
title No change
tr -bgcolor
tt No change
u Unsupported
ul -compact, -type
var No change

B. References

This appendix is normative .

B.1. Normative References

[HTML4]
HTML 4.01 Specification: W3C Recommendation , Dave Raggett, Arnaud Le Hors, Ian Jacobs, 24 December 1999.
See: http://www.w3.org/TR/1999/REC-html401-19991224
[XHTML1]
XHTML 1.0: The Extensible HyperText Markup Language , Steven Pemberton, et. al., 10 December 1999.
See: http://www.w3.org/TR/xhtml1
[XHTMLMOD]
Modularization of XHTML , Shane P. McCarron, et. al., 5 January 2000
See: http://www.w3.org/TR/2000/WD-xhtml-modularization-20000105
[XML]
Extensible Markup Language (XML) 1.0: W3C Recommendation , Tim Bray, Jean Paoli, C. M. Sperberg-McQueen, 10 February 1998.
See: http://www.w3.org/TR/REC-xml
[BUILDING]
Building XHTML Modules , Murray Altheim, Shane P. McCarron, 5 January 2000.
See: http://www.w3.org/TR/2000/WD-xhtml-building-20000105
[RUBY]
Ruby Annotation , Marcin Sawicki, et. al., 17 December 1999.
See: http://www.w3.org/TR/ruby
[SGML]
Information Processing -- Text and Office Systems -- Standard Generalized Markup Language (SGML) , ISO 8879:1986.
Please consult http://www.iso.ch/cate/d16387.html for information about the standard, or http://www.oasis-open.org/cover/general.html#overview about SGML.

B.2. Informative References

[CATALOG]
Entity Management: OASIS Technical Resolution 9401:1997 (Amendment 2 to TR 9401) Paul Grosso, Chair, Entity Management Subcommittee, SGML Open, 10 September 1997.
See: http://www.oasis-open.org/html/a401.htm
[DEVDTD]
Developing SGML DTDs: From Text to Model to Markup , Eve Maler and Jeanne El Andaloussi.
Prentice Hall PTR, 1996, ISBN 0-13-309881-8.
[STRUCTXML]
Structuring XML Documents , David Megginson. Part of the Charles Goldfarb Series on Information Management.
Prentice Hall PTR, 1998, ISBN 0-13-642299-3.
[DOCBOOK]
DocBook DTD , Eve Maler and Terry Allen.
Originally created under the auspices of the Davenport Group, DocBook is now maintained by OASIS. The Customizer's Guide for the DocBook DTD V2.4.1 is available from this site.
See: http://www.oasis-open.org/docbook/index.html
[DUBLIN]
The Dublin Core: A Simple Content Description Model for Electronic Resources , The Dublin Core Metadata Initiative.
See: http://purl.oclc.org/dc/
[SMIL]
Synchronized Multimedia Integration Language (SMIL) 1.0 Specification , Philipp Hoschka, 15 June 1998.
See: http://www.w3.org/TR/REC-smil
[TEI]
The Text Encoding Initiative (TEI)
See: http://www.uic.edu/orgs/tei/
[URI]
Uniform Resource Identifiers (URI): Generic Syntax , T. Berners-Lee, R. Fielding, L. Masinter, August 1998.
See: http://www.ietf.org/rfc/rfc2396.txt . This RFC updates RFC 1738 [URL] and [RFC1808] .
[URL]
IETF RFC 1738, Uniform Resource Locators (URL) , T. Berners-Lee, L. Masinter, M. McCahill.
See: http://www.ietf.org/rfc/rfc1738.txt
[RFC-1808]
Relative Uniform Resource Locators , R. Fielding.
See: http://www.ietf.org/rfc/rfc1808.txt
[CSS2]
"Cascading Style Sheets, level 2 (CSS2) Specification", B. Bos, H. W. Lie, C. Lilley, I. Jacobs, 12 May 1998.
Available at: http://www.w3.org/TR/REC-CSS2
[DOM]
"Document Object Model (DOM) Level 1 Specification", Lauren Wood et al. , 1 October 1998.
Available at: http://www.w3.org/TR/REC-DOM-Level-1
[RFC2119]
"RFC2119: Key words for use in RFCs to Indicate Requirement Levels", S. Bradner, March 1997.
Available at: http://www.ietf.org/rfc/rfc2119.txt
[RFC2376]
"RFC2376: XML Media Types", E. Whitehead, M. Murata, July 1998.
Available at: http://www.ietf.org/rfc/rfc2376.txt
[TIDY]
"HTML Tidy" is a tool for detecting and correcting a wide range of markup errors prevalent in HTML. It can also be used as a tool for converting existing HTML content to be well formed XML. Tidy is being made available on the same terms as other W3C sample code, i.e. free for any purpose, and entirely at your own risk.
It is available from: http://www.w3.org/Status.html#TIDY
[XMLNAMES]
"Namespaces in XML", T. Bray, D. Hollander, A. Layman, 14 January 1999.
XML namespaces provide a simple method for qualifying names used in XML documents by associating them with namespaces identified by URI.
Available at: http://www.w3.org/TR/REC-xml-names
[XMLSTYLE]
"Associating stylesheets with XML documents Version 1.0", J. Clark, 14 January 1999.
This document describes a means for a stylesheet to be associated with an XML document by including one or more processing instructions with a target of xml-stylesheet in the document's prolog.
Available at: http://www.w3.org/TR/PR-xml-stylesheet

C. XHTML 1.1 Document Type Definition

This appendix is normative .

C.1. SGML Open Catalog Entry for XHTML 1.1

This section contains the SGML Open Catalog-format definition of the XHTML 1.1 FPI.

-- .......................................................................... --
-- File catalog  ............................................................ --

--  XHTML 1.1 Catalog Data File

    Revision:  @(#)xhtml11.cat 1.8 99/08/26 SMI

    See "Entity Management", SGML Open Technical Resolution 9401 for detailed
    information on supplying and using catalog data. This document is available
    from OASIS at URL:

        <http://www.oasis-open.org/cover/tr9401.html>
--

-- .......................................................................... --
-- SGML declaration associated with XHTML  .................................. --

OVERRIDE YES

-- SGMLDECL "xml1.dcl" --

-- for use with non-Unicode compatible parsers: --
SGMLDECL "xml1n.dcl"

-- :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: --

-- XHTML 1.1 DTD modular driver file  ....................................... --

PUBLIC "-//W3C//DTD XHTML 1.1//EN"                                "xhtml11.dtd"

-- XHTML 1.1 framework modules .............................................. --

PUBLIC "-//W3C//ENTITIES XHTML 1.1 Document Model 1.0//EN"        "xhtml11-model-1.mod"


-- End of catalog data  ..................................................... --
-- .......................................................................... --


C.2. XHTML 1.1 Driver

This section contains the driver for the XHTML 1.1 document type implementation as an XML DTD. It relies upon XHTML module implementations defined in [ XHTMLMOD ] and in [ RUBY ].

<!-- ....................................................................... -->
<!-- XHTML 1.1 DTD  ........................................................ -->
<!-- file: xhtml11.dtd
-->

<!-- XHTML 1.1 DTD

     This is XHTML 1.1, a modular variant of XHTML 1.0.



     Copyright 1998-2000 World Wide Web Consortium


        (Massachusetts Institute of Technology, Institut National de
         Recherche en Informatique et en Automatique, Keio University).
         All Rights Reserved.

     Permission to use, copy, modify and distribute the XHTML 1.1 DTD 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 the DTD for any purpose.

     It is provided "as is" without expressed or implied warranty.

        Author:     Murray M. Altheim <altheim@eng.sun.com>


        Revision:   $Id: xhtml11.dtd,v 1.5 2000/01/04 19:50:19 ahby Exp $ SMI



-->
<!-- This is the driver file for version 1.1 of the XHTML DTD.

     Please use this formal public identifier to identify it:

         "-//W3C//DTD XHTML 1.1//EN"


-->
<!ENTITY % XHTML.version  "-//W3C//DTD XHTML 1.1//EN" >





<!-- Use this URI to identify the default namespace:





         "http://www.w3.org/1999/xhtml"
-->
<!ENTITY % XHTML.ns  "http://www.w3.org/1999/xhtml" >





<!-- Reserved for use with the XLink namespace:
-->
<!ENTITY % XLINK.ns "" >
<!ENTITY % XLinkns.attrib "" >

<!-- For example, if you are using XHTML 1.1 directly, use the FPI


     in the DOCTYPE declaration, with the xmlns attribute on the
     document element to identify the default namespace:

         <?xml version="1.0"?>
         <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" 
                               "xhtml11.dtd" >


         <html xmlns="http://www.w3.org/TR/xhtml"


               xmlns:xlink="http://www.w3.org/XML/XLink/0.9"
               xml:lang="en" >
         ...
         </html>

     Revisions:
     (none)
-->

<!-- reserved for future use with document profiles -->


<!ENTITY % XHTML.profile  "" >



<!-- Internationalization features
     This feature-test entity is used to declare elements
     and attributes used for internationalization support.
-->


<!ENTITY % XHTML.I18n  "INCLUDE" >



<!-- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: -->



<!ENTITY % xhtml-events.module "INCLUDE" >





<!-- Define the Content Model -->
<!ENTITY % xhtml-model.mod
     PUBLIC "-//W3C//ENTITIES XHTML 1.1 Document Model 1.0//EN"
     SYSTEM "xhtml11-model-1.mod" >

<!-- Pre-Framework Redeclaration placeholder  .................... -->
<!-- this serves as a location to insert markup declarations
     into the DTD prior to the framework declarations.
-->
<!ENTITY % xhtml-prefw-redecl.module "IGNORE" >
<![%xhtml-prefw-redecl.module;[
%xhtml-prefw-redecl.mod;
<!-- end of xhtml-prefw-redecl.module -->]]>



<!-- Modular Framework Module  ................................... -->


<!ENTITY % xhtml-framework.module "INCLUDE" >
<![%xhtml-framework.module;[
<!ENTITY % xhtml-framework.mod


     PUBLIC "-//W3C//ENTITIES XHTML 1.1 Modular Framework 1.0//EN"
            "xhtml11-framework-1.mod" >


%xhtml-framework.mod;]]>

<!-- Post-Framework Redeclaration placeholder  ................... -->
<!-- this serves as a location to insert markup declarations 
     into the DTD following the framework declarations.
-->
<!ENTITY % xhtml-postfw-redecl.module "IGNORE" >
<![%xhtml-postfw-redecl.module;[
%xhtml-postfw-redecl.mod;
<!-- end of xhtml-postfw-redecl.module -->]]>



<!-- Basic Text Module (Required)  ............................... -->


<!ENTITY % xhtml-text.module "INCLUDE" >
<![%xhtml-text.module;[
<!ENTITY % xhtml-text.mod


     PUBLIC "-//W3C//ELEMENTS XHTML 1.1 Basic Text 1.0//EN"
            "xhtml11-text-1.mod" >


%xhtml-text.mod;]]>



<!-- Hypertext Module (required) ................................. -->


<!ENTITY % xhtml-hypertext.module "INCLUDE" >
<![%xhtml-hypertext.module;[
<!ENTITY % xhtml-hypertext.mod


     PUBLIC "-//W3C//ELEMENTS XHTML 1.1 Hypertext 1.0//EN"
            "xhtml11-hypertext-1.mod" >


%xhtml-hypertext.mod;]]>



<!-- Lists Module (required)  .................................... -->


<!ENTITY % xhtml-list.module "INCLUDE" >
<![%xhtml-list.module;[
<!ENTITY % xhtml-list.mod


     PUBLIC "-//W3C//ELEMENTS XHTML 1.1 Lists 1.0//EN"
            "xhtml11-list-1.mod" >


%xhtml-list.mod;]]>

<!-- Document Structure Module (required)  ....................... -->
<!ENTITY % xhtml-struct.module "INCLUDE" >
<![%xhtml-struct.module;[
<!ENTITY % xhtml-struct.mod
     PUBLIC "-//W3C//ELEMENTS XHTML 1.1 Document Structure 1.0//EN"
            "xhtml11-struct-1.mod" >
%xhtml-struct.mod;]]>

<!-- end of required section ::::::::::::::::::::::::::::::::::::::::::::::: -->

<!-- Ruby Module  ................................................ -->
<!ENTITY % Ruby.fallback "INCLUDE" >
<!ENTITY % Ruby.common.attlists "INCLUDE" >
<!ENTITY % Ruby.common.attrib "%Common.attrib;" >

<!ENTITY % xhtml-ruby.module "INCLUDE" >
<![%xhtml-ruby.module;[
<!ENTITY % xhtml-ruby.mod
     PUBLIC "-//W3C//ELEMENTS Ruby 1.0//EN"
            "ruby-1.mod" >
%xhtml-ruby.mod;]]>



<!-- Edit Module  ................................................ -->


<!ENTITY % xhtml-edit.module "INCLUDE" >
<![%xhtml-edit.module;[
<!ENTITY % xhtml-edit.mod


     PUBLIC "-//W3C//ELEMENTS XHTML 1.1 Editing Elements 1.0//EN"
            "xhtml11-edit-1.mod" >


%xhtml-edit.mod;]]>



<!-- Presentation Module  ........................................ -->


<!ENTITY % xhtml-pres.module "INCLUDE" >
<![%xhtml-pres.module;[
<!ENTITY % xhtml-pres.mod


     PUBLIC "-//W3C//ELEMENTS XHTML 1.1 Presentation 1.0//EN"
            "xhtml11-pres-1.mod" >


%xhtml-pres.mod;]]>



<!-- Java Applet Element Module  ................................. -->


<!ENTITY % xhtml-applet.module "INCLUDE" >
<![%xhtml-applet.module;[
<!ENTITY % xhtml-applet.mod


     PUBLIC "-//W3C//ELEMENTS XHTML 1.1 Java Applets 1.0//EN"
            "xhtml11-applet-1.mod" >


%xhtml-applet.mod;]]>

<!-- Param Element Module  ....................................... -->
<!ENTITY % xhtml-param.module "INCLUDE" >
<![%xhtml-param.module;[
<!ENTITY % xhtml-param.mod
     PUBLIC "-//W3C//ELEMENTS XHTML 1.1 Param Element 1.0//EN"
            "xhtml11-param-1.mod" >
%xhtml-param.mod;]]>



<!-- BIDI Override Module  ....................................... -->


<!ENTITY % xhtml-bdo.module "INCLUDE" >
<![%xhtml-bdo.module;[
<!ENTITY % xhtml-bdo.mod


     PUBLIC "-//W3C//ELEMENTS XHTML 1.1 BIDI Override Element 1.0//EN"
            "xhtml11-bdo-1.mod" >


%xhtml-bdo.mod;]]>



<!-- Forms Module  ............................................... -->


<!ENTITY % xhtml-form.module "INCLUDE" >
<![%xhtml-form.module;[
<!ENTITY % xhtml-form.mod


     PUBLIC "-//W3C//ELEMENTS XHTML 1.1 Forms 1.0//EN"
            "xhtml11-form-1.mod" >


%xhtml-form.mod;]]>



<!-- Tables Module ............................................... -->


<!ENTITY % xhtml-table.module "INCLUDE" >
<![%xhtml-table.module;[
<!ENTITY % xhtml-table.mod


     PUBLIC "-//W3C//ELEMENTS XHTML 1.1 Tables 1.0//EN"
            "xhtml11-table-1.mod" >


%xhtml-table.mod;]]>



<!-- Image Module  ............................................... -->


<!ENTITY % xhtml-image.module "INCLUDE" >
<![%xhtml-image.module;[
<!ENTITY % xhtml-image.mod


     PUBLIC "-//W3C//ELEMENTS XHTML 1.1 Images 1.0//EN"
            "xhtml11-image-1.mod" >


%xhtml-image.mod;]]>



<!-- Client-side Image Map Module  ............................... -->


<!ENTITY % xhtml-csismap.module "INCLUDE" >
<![%xhtml-csismap.module;[
<!ENTITY % xhtml-csismap.mod


     PUBLIC "-//W3C//ELEMENTS XHTML 1.1 Client-side Image Maps 1.0//EN"
            "xhtml11-csismap-1.mod" >


%xhtml-csismap.mod;]]>



<!-- Server-side Image Map Module  ............................... -->


<!ENTITY % xhtml-ssismap.module "INCLUDE" >
<![%xhtml-ssismap.module;[
<!ENTITY % xhtml-ssismap.mod


     PUBLIC "-//W3C//ELEMENTS XHTML 1.1 Server-side Image Maps 1.0//EN"
            "xhtml11-ssismap-1.mod" >


%xhtml-ssismap.mod;]]>



<!-- Document Metainformation Module  ............................ -->


<!ENTITY % xhtml-meta.module "INCLUDE" >
<![%xhtml-meta.module;[
<!ENTITY % xhtml-meta.mod


     PUBLIC "-//W3C//ELEMENTS XHTML 1.1 Metainformation 1.0//EN"
            "xhtml11-meta-1.mod" >


%xhtml-meta.mod;]]>



<!-- Scripting Module  ........................................... -->


<!ENTITY % xhtml-script.module "INCLUDE" >
<![%xhtml-script.module;[
<!ENTITY % xhtml-script.mod


     PUBLIC "-//W3C//ELEMENTS XHTML 1.1 Scripting 1.0//EN"
            "xhtml11-script-1.mod" >


%xhtml-script.mod;]]>



<!-- Stylesheets Module  ......................................... -->


<!ENTITY % xhtml-style.module "INCLUDE" >
<![%xhtml-style.module;[
<!ENTITY % xhtml-style.mod


     PUBLIC "-//W3C//ELEMENTS XHTML 1.1 Stylesheets 1.0//EN"
            "xhtml11-style-1.mod" >


%xhtml-style.mod;]]>



<!-- Link Element Module  ........................................ -->


<!ENTITY % xhtml-link.module "INCLUDE" >
<![%xhtml-link.module;[
<!ENTITY % xhtml-link.mod


     PUBLIC "-//W3C//ELEMENTS XHTML 1.1 Link Element 1.0//EN"
            "xhtml11-link-1.mod" >


%xhtml-link.mod;]]>



<!-- Base Element Module  ........................................ -->


<!ENTITY % xhtml-base.module "INCLUDE" >
<![%xhtml-base.module;[
<!ENTITY % xhtml-base.mod


     PUBLIC "-//W3C//ELEMENTS XHTML 1.1 Base Element 1.0//EN"
            "xhtml11-base-1.mod" >


%xhtml-base.mod;]]>



<!-- end of XHTML 1.1 DTD  ................................................. -->
<!-- ....................................................................... -->

C.3. XHTML 1.1 Customizations

An XHTML 1.1 Family Document Type (such as XHTML 1.1) must define the content model that it uses. This is done through a separate content model module that is instantiated by the XHTML Modular Framework. The content model module and the XHTML 1.1 Driver (above) work together to customize the module implementations to the document type's specific requirements. The content model module for XHTML 1.1 is defined below:

<!-- ....................................................................... -->
<!-- XHTML 1.1 Document Model Module  ...................................... -->
<!-- file: xhtml11-model-1.mod

     This is XHTML 1.1, a modular variant of XHTML 1.0.


     Copyright 1998-2000 W3C (MIT, INRIA, Keio), All Rights Reserved.
     Revision: $Id: xhtml11-model-1.mod,v 1.5 2000/01/05 13:26:27 ahby Exp $ SMI



     This DTD module is identified by the PUBLIC and SYSTEM identifiers:

     PUBLIC "-//W3C//ENTITIES XHTML 1.1 Document Model 1.0//EN"
     SYSTEM "xhtml11-model-1.mod"

     Revisions:
     (none)
     ....................................................................... -->

<!-- Document Model

     This module describes the groupings of elements that make up
     common content models for XHTML elements.

     XHTML has three basic content models:



         %Inline.mix;  character-level elements
         %Block.mix;   block-like elements, eg., paragraphs and lists
         %Flow.mix;    any block or inline elements



     Any parameter entities declared in this module may be used
     to create element content models, but the above three are
     considered 'global' (insofar as that term applies here).

     The reserved word '#PCDATA' (indicating a text string) is now
     included explicitly with each element declaration that is
     declared as mixed content, as XML requires that this token
     occur first in a content model specification.
-->
<!-- Extending the Model

     While in some cases this module may need to be rewritten to
     accommodate changes to the document model, minor extensions
     may be accomplished by redeclaring any of the three *.extra;
     parameter entities to contain extension element types as follows:



         %Misc.extra;    whose parent may be any block or


                         inline element.



         %Inline.extra;  whose parent may be any inline element.





         %Block.extra;   whose parent may be any block element.



     If used, these parameter entities must be an OR-separated
     list beginning with an OR separator ("|"), eg., "| a | b | c"

     All block and inline *.class parameter entities not part
     of the *struct.class classes begin with "| " to allow for
     exclusion from mixes.
-->

<!-- ..............  Optional Elements in head  .................. -->



<!ENTITY % Head-opts.mix  "( script | style | meta | link )*" >



<!-- .................  Miscellaneous Elements  .................. -->

<!-- ins and del are used to denote editing changes
-->


<!ENTITY % Edit.class "| ins | del" >



<!-- script and noscript are used to contain scripts
     and alternative content
-->



<!ENTITY % Misc.extra "| script | noscript" >



<!-- These elements are neither block nor inline, and can
     essentially be used anywhere in the document body.
-->


<!ENTITY % Misc.class
     "%Edit.class;
      %Misc.extra;"


>

<!-- ....................  Inline Elements  ...................... -->



<!ENTITY % Inlstruct.class "br | span" >





<!ENTITY % Inlphras.class


     "| em | strong | dfn | code | samp | kbd | var | cite | abbr | acronym | q" >



<!ENTITY % Inlpres.class


     "| tt | i | b | big | small | sub | sup" >



<!ENTITY % I18n.class "| bdo" >





<!ENTITY % Anchor.class "| a" >





<!ENTITY % Inlspecial.class "| img | map | applet" >





<!ENTITY % Inline.extra 


     "| input | select | textarea | label | button" >



<!ENTITY % Ruby.class "| ruby" >





<!-- %Inline.class; includes all inline elements,


     used as a component in mixes
-->


<!ENTITY % Inline.class
     "%Inlstruct.class;
      %Inlphras.class;
      %Inlpres.class;
      %I18n.class;
      %Anchor.class;
      %Inlspecial.class;
      %Ruby.class;
      %Inline.extra;"


>



<!-- %Inline-noruby.class; includes all inline elements 
     except ruby, used as a component in mixes


-->


<!ENTITY % Inline-noruby.class
     "%Inlstruct.class;
      %Inlphras.class;
      %Inlpres.class;
      %I18n.class;
      %Anchor.class;
      %Inlspecial.class;
      %Inline.extra;"


>



<!-- %Noruby.content; includes all inlines except ruby


-->


<!ENTITY % Noruby.content


     "( #PCDATA 


      | %Inline-noruby.class;
      %Misc.class; )*"


>



<!-- %Inline-noa.class; includes all non-anchor inlines,
     used as a component in mixes


-->


<!ENTITY % Inline-noa.class
     "%Inlstruct.class;
      %Inlphras.class;
      %Inlpres.class;
      %I18n.class;
      %Inlspecial.class;
      %Ruby.class;
      %Inline.extra;"


>



<!-- %Inline-noa.mix; includes all non-anchor inlines


-->


<!ENTITY % Inline-noa.mix
     "%Inline-noa.class;
      %Misc.class;"


>



<!-- %Inline.mix; includes all inline elements, including %Misc.class;


-->


<!ENTITY % Inline.mix
     "%Inline.class;
      %Misc.class;"


>



<!-- .....................  Block Elements  ...................... -->





<!-- In the HTML 4.0 DTD, heading and list elements were included
     in the % block; parameter entity. The % Heading.class; and
     % List.class; parameter entities must now be included explicitly
     on element declarations where desired.


-->



<!ENTITY % Heading.class "h1 | h2 | h3 | h4 | h5 | h6" >





<!ENTITY % List.class "ul | ol | dl" >





<!ENTITY % Blkstruct.class "p | div" >





<!ENTITY % Blkphras.class "| pre | blockquote | address" >





<!ENTITY % Blkpres.class "| hr" >





<!ENTITY % Block.extra "| table | form | fieldset" >





<!-- %Block.class; includes all block elements,
     used as an component in mixes


-->


<!ENTITY % Block.class
     "%Blkstruct.class;
      %Blkphras.class;
      %Blkpres.class;
      %Block.extra;"


>



<!-- %Block.mix; includes all block elements plus %Misc.class;


-->


<!ENTITY % Block.mix
     "%Heading.class;
      | %List.class;
      | %Block.class;
      %Misc.class;"


>



<!-- ................  All Content Elements  .................. -->





<!-- %Flow.mix; includes all text content, block and inline


-->


<!ENTITY % Flow.mix
     "%Heading.class;
      | %List.class;
      | %Block.class;
      | %Inline.class;
      %Misc.class;"


>



<!-- end of xhtml11-model-1.mod -->