Abstract
This
document
is
the
second
edition
of
version
1.1
of
XHTML
Modularization,
an
abstract
modularization
of
XHTML
and
implementations
of
the
abstraction
using
XML
Document
Type
Definitions
(DTDs)
and
XML
Schemas.
This
modularization
provides
a
means
for
subsetting
and
extending
XHTML,
a
feature
needed
for
extending
XHTML's
reach
onto
emerging
platforms.
This
specification
is
intended
for
use
by
language
designers
as
they
construct
new
XHTML
Family
Markup
Languages.
This
specification
does
not
define
the
semantics
of
elements
and
attributes,
only
how
those
elements
and
attributes
are
assembled
into
modules,
and
from
those
modules
into
markup
languages.
This
update
includes
several
minor
updates
to
provide
clarifications
and
address
errors
found
in
version
1.1.
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
http://www.w3.org/TR/.
This
document
is
a
W3C
Recommendation.
It
supersedes
the
previous
edition
of
XHTML
Modularization
1.1.
It
reflects
minor
corrections
to
ensure
consistency
among
various
markup
languages
that
rely
upon
XHTML
Modularization.
Most
significant
among
these
are:
-
Changing
the
datatype
of
the
class
attribute
so
that
it
permits
an
empty
value
-
historically
the
class
attribute
was
permitted
to
be
empty.
-
Moving
the
name
attribute
for
the
form
and
img
elements
out
of
the
legacy
module
and
into
their
base
modules
-
this
attribute
is
required
for
some
scripting
constructs.
-
Changing
the
datatype
for
the
usemap
attribute
from
IDREF
to
URIREF
-
most
user
agents
require
that
map
references
be
relative
URIs
that
are
local
to
the
document.
Due
to
the
nature
of
XHTML
Modularization,
the
decision
to
advance
to
Proposed
Edited
Recommendation
did
not
involve
new
implementation
information.
Previous
implementation
experience
is
documented
at
http://www.w3.org/MarkUp/2008/xhtml-m12n-11-implementation.html
.
A
version
that
shows
the
specific
changes
from
that
Recommendation
is
available
in
diff-marked
form
.
A
disposition
of
comments
document
is
available.
This
document
has
been
reviewed
by
W3C
Members,
by
software
developers,
and
by
other
W3C
groups
and
interested
parties,
and
is
endorsed
by
the
Director
as
a
W3C
Recommendation.
It
is
a
stable
document
and
may
be
used
as
reference
material
or
cited
from
another
document.
W3C's
role
in
making
the
Recommendation
is
to
draw
attention
to
the
specification
and
to
promote
its
widespread
deployment.
This
enhances
the
functionality
and
interoperability
of
the
Web.
Members
of
the
public
are
invited
to
send
comments
on
this
Recommendation
to
www-html-editor@w3.org
(
archive
).
It
is
inappropriate
to
send
discussion
email
to
this
address.
Public
discussion
may
take
place
on
www-html@w3.org
(
archive
).
This
document
has
been
produced
by
the
W3C
XHTML
2
Working
Group
as
part
of
the
HTML
Activity
.
The
goals
of
the
XHTML
2
Working
Group
are
discussed
in
the
XHTML
2
Working
Group
charter
.
This
document
was
produced
by
a
group
operating
under
the
5
February
2004
W3C
Patent
Policy
.
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.
Quick
Table
of
Contents
Full
Table
of
Contents
1.
Introduction
This
section
is
informative
.
1.1.
What
is
XHTML?
XHTML
is
the
reformulation
of
HTML
4
as
an
application
of
XML.
XHTML
1.0
[XHTML1]
specifies
three
XML
document
types
that
correspond
to
the
three
HTML
4
DTDs:
Strict,
Transitional,
and
Frameset.
XHTML
1.0
is
the
basis
for
a
family
of
document
types
that
subset
and
extend
HTML.
1.2.
What
is
XHTML
Modularization?
XHTML
Modularization
is
a
decomposition
of
XHTML
1.0,
and
by
reference
HTML
4,
into
a
collection
of
abstract
modules
that
provide
specific
types
of
functionality.
These
abstract
modules
are
implemented
in
this
specification
using
the
XML
Schema
and
XML
Document
Type
Definition
languages.
The
rules
for
defining
the
abstract
modules,
and
for
implementing
them
using
XML
Schemas
and
XML
DTDs,
are
also
defined
in
this
document.
These
modules
may
be
combined
with
each
other
and
with
other
modules
to
create
XHTML
subset
and
extension
document
types
that
qualify
as
members
of
the
XHTML-family
of
document
types.
Note
that
while
this
specification
only
contains
trivial
examples
of
combining
these
modules
into
markup
languages.
For
more
complete
examples,
see
[
XHTMLBASIC
]
or
[
XHTML11
].
1.3.
Why
Modularize
XHTML?
The
modularization
of
XHTML
refers
to
the
task
of
specifying
well-defined
sets
of
XHTML
elements
that
can
be
combined
and
extended
by
document
authors,
document
type
architects,
other
XML
standards
specifications,
and
application
and
product
designers
to
make
it
economically
feasible
for
content
developers
to
deliver
content
on
a
greater
number
and
diversity
of
platforms.
Over
the
last
couple
of
years,
many
specialized
markets
have
begun
looking
to
HTML
as
a
content
language.
There
is
a
great
movement
toward
using
HTML
across
increasingly
diverse
computing
platforms.
Currently
there
is
activity
to
move
HTML
onto
mobile
devices
(hand
held
computers,
portable
phones,
etc.),
television
devices
(digital
televisions,
TV-based
Web
browsers,
etc.),
and
appliances
(fixed
function
devices).
Each
of
these
devices
has
different
requirements
and
constraints.
Modularizing
XHTML
provides
a
means
for
product
designers
to
specify
which
elements
are
supported
by
a
device
using
standard
building
blocks
and
standard
methods
for
specifying
which
building
blocks
are
used.
These
modules
serve
as
"points
of
conformance"
for
the
content
community.
The
content
community
can
now
target
the
installed
base
that
supports
a
certain
collection
of
modules,
rather
than
worry
about
the
installed
base
that
supports
this
or
that
permutation
of
XHTML
elements.
The
use
of
standards
is
critical
for
modularized
XHTML
to
be
successful
on
a
large
scale.
It
is
not
economically
feasible
for
content
developers
to
tailor
content
to
each
and
every
permutation
of
XHTML
elements.
By
specifying
a
standard,
either
software
processes
can
autonomously
tailor
content
to
a
device,
or
the
device
can
automatically
load
the
software
required
to
process
a
module.
Modularization
also
allows
for
the
extension
of
XHTML's
layout
and
presentation
capabilities,
using
the
extensibility
of
XML,
without
breaking
the
XHTML
standard.
This
development
path
provides
a
stable,
useful,
and
implementable
framework
for
content
developers
and
publishers
to
manage
the
rapid
pace
of
technological
change
on
the
Web.
1.3.1.
Abstract
modules
An
XHTML
document
type
is
defined
as
a
set
of
abstract
modules.
A
abstract
module
defines
one
kind
of
data
that
is
semantically
different
from
all
others.
Abstract
modules
can
be
combined
into
document
types
without
a
deep
understanding
of
the
underlying
schemas
that
define
the
modules.
1.3.2.
Module
implementations
A
module
implementation
consists
of
a
set
of
element
types,
a
set
of
attribute-list
declarations,
and
a
set
of
content
model
declarations,
where
any
of
these
three
sets
may
be
empty.
An
attribute-list
declaration
in
a
module
may
modify
an
element
type
outside
the
element
types
defined
in
the
module,
and
a
content
model
declaration
may
modify
an
element
type
outside
the
element
type
set
of
the
module.
One
implementation
mechanism
is
XML
DTDs.
An
XML
DTD
is
a
means
of
describing
the
structure
of
a
class
of
XML
documents,
collectively
known
as
an
XML
document
type.
XML
DTDs
are
described
in
the
XML
1.0
Recommendation
[XML]
.
Another
implementation
mechanism
is
XML
Schema
[XMLSCHEMA]
.
For
purposes
of
discussion
in
this
document,
we
refer
to
the
various
implementations
of
XHTML
Modularization
as
"schema".
1.3.3.
Hybrid
document
types
A
hybrid
document
type
is
an
document
type
composed
from
a
collection
of
XML
document
types
or
Modules.
The
primary
purpose
of
the
modularization
framework
described
in
this
document
is
to
allow
a
document
type
author
to
combine
elements
from
multiple
abstract
modules
into
a
hybrid
document
type,
develop
documents
against
that
hybrid
document
type,
and
to
validate
that
document
against
the
associated
hybrid
schema.
One
of
the
most
valuable
benefits
of
XML
over
SGML
is
that
XML
reduces
the
barrier
to
entry
for
standardization
of
element
sets
that
allow
communities
to
exchange
data
in
an
interoperable
format.
However,
the
relatively
static
nature
of
HTML
as
the
content
language
for
the
Web
has
meant
that
any
one
of
these
communities
have
previously
held
out
little
hope
that
their
XML
document
types
would
be
able
to
see
widespread
adoption
as
part
of
Web
standards.
The
modularization
framework
allows
for
the
dynamic
incorporation
of
these
diverse
document
types
within
the
XHTML-family
of
document
types,
further
reducing
the
barriers
to
the
incorporation
of
these
domain-specific
vocabularies
in
XHTML
documents.
1.3.4.
Validation
The
use
of
well-formed,
but
not
valid,
documents
is
an
important
benefit
of
XML.
In
the
process
of
developing
a
document
type,
however,
the
additional
leverage
provided
by
a
validating
parser
for
error
checking
is
important.
The
same
statement
applies
to
XHTML
document
types
with
elements
from
multiple
abstract
modules.
An
XHTML-family
document
is
an
instance
of
one
particular
document
type
as
specified
by
the
document's
author,
either
in
the
document's
prologue
or
through
some
other
mechanism
(e.g.,
the
schemaLocation
attribute).
Validating
the
document
is
the
process
of
testing
whether
the
document
complies
with
the
rules
in
the
associated
schema.
One
document
can
consist
of
multiple
document
fragments.
Validating
only
fragments
of
a
document,
where
each
fragment
is
of
a
different
document
type
than
the
other
fragments
in
the
document,
is
beyond
the
scope
of
this
framework
-
since
it
would
require
technology
that
is
not
yet
defined.
However,
the
modularization
framework
allows
multiple
schema
to
be
integrated
and
form
a
new
document
type
(e.g.
SVG
integrated
into
XHTML).
The
new
schema
can
be
used
for
normal
XML
1.0
validation.
Earlier
versions
of
HTML
attempted
to
define
parts
of
the
model
that
user
agents
are
required
to
use
when
formatting
a
document.
With
the
advent
of
HTML
4,
the
W3C
started
the
process
of
divorcing
presentation
from
structure.
XHTML
1.0
maintained
this
separation,
and
this
document
continues
moving
HTML
and
its
descendants
down
this
path.
Consequently,
this
document
makes
no
requirements
on
the
formatting
model
associated
with
the
presentation
of
documents
marked
up
with
XHTML
Family
document
types.
Instead,
this
document
recommends
that
content
authors
rely
upon
style
mechanisms
such
as
CSS
to
define
the
formatting
model
for
their
content.
When
user
agents
support
the
style
mechanisms,
documents
will
format
as
expected.
When
user
agents
do
not
support
the
style
mechanisms,
documents
will
format
as
appropriate
for
that
user
agent.
This
permits
XHTML
Family
user
agents
to
support
rich
formatting
models
on
devices
where
that
is
appropriate,
and
lean
formatting
models
on
devices
where
that
is
appropriate.
2.
Terms
and
Definitions
This
section
is
informative
.
While
some
terms
are
defined
in
place,
the
following
definitions
are
used
throughout
this
document.
Familiarity
with
the
W3C
XML
1.0
Recommendation
[XML]
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).
-
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]
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
parse-able
XML
markup
or
character
data,
or
unparsed
(i.e.,
non-XML,
possibly
non-textual)
content.
Entity
content
may
be
either
defined
entirely
within
the
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
(eg.,
"&"
for
"&",
"<"
for
"<",
"©"
for
"©".)
-
facilities
-
elements
,
attributes
,
and
the
semantics
associated
with
those
elements
and
attributes
.
-
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
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.
This
section
is
normative
.
In
order
to
ensure
that
XHTML-family
documents
are
maximally
portable
among
XHTML-family
user
agents,
this
specification
rigidly
defines
conformance
requirements
for
both
of
these
and
for
XHTML-family
document
types.
While
the
conformance
definitions
can
be
found
in
this
section,
they
necessarily
reference
normative
text
within
this
document,
within
the
base
XHTML
specification
[XHTML1]
,
and
within
other
related
specifications.
It
is
only
possible
to
fully
comprehend
the
conformance
requirements
of
XHTML
through
a
complete
reading
of
all
normative
references.
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]
.
It
is
possible
to
modify
existing
document
types
and
define
wholly
new
document
types
using
both
modules
defined
in
this
specification
and
other
modules.
Such
a
document
type
is
"XHTML
Host
Language
Conforming"
when
it
meets
the
following
criteria:
-
The
document
type
MUST
be
defined
using
one
of
the
implementation
methods
defined
by
the
W3C.
Currently
this
is
limited
to
XML
DTDs
and
XML
Schema.
-
The
schema
which
defines
the
document
type
MUST
have
a
unique
identifier
as
defined
in
Naming
Rules
that
begins
with
the
character
sequence
"
XHTML
".
-
The
schema
which
defines
the
document
type
must
include,
at
a
minimum,
the
Structure,
Hypertext,
Text,
and
List
modules
defined
in
this
specification.
-
For
each
of
the
W3C-defined
modules
that
are
included,
all
of
the
elements,
attributes,
types
of
attributes
(including
any
required
enumerated
value
lists),
and
any
required
minimal
content
models
must
be
included
(and
optionally
extended)
in
the
document
type's
content
model.
When
content
models
are
extended,
all
of
the
elements
and
attributes
(along
with
their
types
or
any
required
enumerated
value
lists)
required
in
the
original
content
model
must
continue
to
be
required.
-
The
schema
that
defines
the
document
type
may
define
additional
elements
and
attributes.
However,
these
MUST
be
in
their
own
XML
namespace
[XMLNAMES]
.
If
additional
elements
are
defined
by
a
module,
the
attributes
defined
in
included
XHTML
modules
are
available
for
use
on
those
elements,
but
SHOULD
be
referenced
using
their
namespace-qualified
identifier
(e.g.,
xhtml:class).
The
semantics
of
the
attributes
remain
the
same
as
when
used
on
an
XHTML-namespace
element.
3.2.
XHTML
Integration
Set
Document
Type
Conformance
It
is
also
possible
to
define
document
types
that
are
based
upon
XHTML,
but
do
not
adhere
to
its
structure.
Such
a
document
type
is
"XHTML
Integration
Set
Conforming"
when
it
meets
the
following
criteria:
-
The
document
type
MUST
be
defined
using
one
of
the
implementation
methods
defined
by
the
W3C.
Currently
this
is
limited
to
XML
DTDs
and
XML
Schemas.
-
The
schema
that
defines
the
document
type
MUST
have
a
unique
identifier
as
defined
in
Naming
Rules
.
This
identifier
MUST
contain
the
character
sequence
"XHTML",
but
MUST
NOT
start
with
that
character
sequence.
-
The
schema
which
defines
the
document
type
MUST
include,
at
a
minimum,
the
Hypertext,
Text,
and
List
modules
defined
in
this
specification.
-
For
each
of
the
W3C-defined
modules
that
are
included,
all
of
the
elements,
attributes,
types
of
attributes
(including
any
required
enumerated
lists),
and
any
required
minimal
content
models
MUST
be
included
(and
optionally
extended)
in
the
document
type's
content
model.
When
content
models
are
extended,
all
of
the
elements
and
attributes
(along
with
their
types
or
any
required
enumerated
value
lists)
required
in
the
original
content
model
MUST
continue
to
be
required.
-
The
schema
that
defines
the
document
type
MAY
define
additional
elements
and
attributes.
However,
these
MUST
be
in
their
own
XML
namespace
[XMLNAMES]
.
If
additional
elements
are
defined
by
a
module,
the
attributes
defined
in
included
XHTML
modules
are
available
for
use
on
those
elements,
but
SHOULD
be
referenced
using
their
namespace-qualified
identifier
(e.g.,
xhtml:class).
The
semantics
of
the
attributes
remain
the
same
as
when
used
on
an
XHTML-namespace
element.
This
specification
defines
a
method
for
defining
XHTML-conforming
modules.
A
module
conforms
to
this
specification
when
it
meets
all
of
the
following
criteria:
-
The
document
type
MUST
be
defined
using
one
of
the
implementation
methods
defined
by
the
W3C.
Currently
this
is
limited
to
XML
DTDs
and
XML
Schemas.
-
The
schema
that
defines
the
module
MUST
have
a
unique
identifier
as
defined
in
Naming
Rules
.
-
When
the
module
is
defined
using
an
XML
DTD,
the
module
MUST
isolate
its
parameter
entity
names
through
the
use
of
unique
prefixes
or
other,
similar
methods.
-
The
module
definition
MUST
have
a
prose
definition
that
describes
the
syntactic
and
semantic
requirements
of
the
elements,
attributes,
and/or
content
models
that
it
declares.
For
the
avoidance
of
doubt,
if
there
is
any
discrepancy
between
the
prose
definition
of
a
module
and
its
schema
implementation(s),
the
prose
definition
MUST
take
precedence.
-
The
module
definition
MUST
NOT
reuse
any
element
names
that
are
defined
in
other
W3C-defined
modules,
except
when
the
content
model
and
semantics
of
those
elements
are
either
identical
to
the
original
or
an
extension
of
the
original,
or
when
the
reused
element
names
are
within
their
own
XML
namespace
(see
below).
-
The
module
definition's
elements
and
attributes
MUST
be
part
of
an
XML
namespace
[XMLNAMES]
.
If
the
module
is
defined
by
an
organization
other
than
the
W3C,
this
namespace
MUST
NOT
be
the
same
as
the
namespace
in
which
other
W3C
modules
are
defined.
A
conforming
XHTML
family
document
is
a
valid
instance
of
an
XHTML
Host
Language
Conforming
Document
Type.
For
the
avoidance
of
doubt,
the
behavior
of
User
Agents
in
the
presence
of
invalid
documents
is
undefined.
A
conforming
user
agent
must
meet
all
of
the
following
criteria
(as
defined
in
[XHTML1]
):
-
In
order
to
be
consistent
with
the
XML
1.0
Recommendation
[XML]
,
the
user
agent
MUST
parse
and
evaluate
an
XHTML
document
for
well-formedness.
If
the
user
agent
claims
to
be
a
validating
user
agent,
it
MUST
also
validate
documents
against
their
referenced
schemas.
-
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.
-
When
a
user
agent
processes
an
XHTML
document
as
generic
[XML]
,
it
MUST
recognize
only
attributes
of
type
ID
(e.g.,
the
id
attribute
on
most
XHTML
elements)
as
fragment
identifiers.
-
If
a
user
agent
encounters
an
element
it
does
not
recognize,
it
MUST
continue
to
process
the
children
of
that
element.
-
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).
-
If
it
encounters
an
entity
reference
(other
than
one
of
the
predefined
entities)
for
which
the
user
agent
has
processed
no
declaration
(which
could
happen
if
the
declaration
is
in
the
external
subset
which
the
user
agent
hasn't
read),
the
entity
reference
SHOULD
be
rendered
as
the
characters
(starting
with
the
ampersand
and
ending
with
the
semi-colon)
that
make
up
the
entity
reference.
-
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.
-
Whitespace
is
defined
as
in
[XML]
.
On
input
all
whitespace
is
preserved
-
this
is
exactly
as
if
the
value
of
xml:space
,
as
defined
in
[XML]
,
is
set
to
"preserve".
If
the
value
of
that
attribute
is
set
to
"default",
that
is
the
same
as
if
it
were
set
to
"preserve".
On
rendering,
whitespace
is
processed
according
to
the
rules
of
[CSS2]
.
XHTML
Host
Language
document
types
must
adhere
to
strict
naming
conventions
so
that
it
is
possible
for
software
and
users
to
readily
determine
the
relationship
of
document
types
to
XHTML.
The
names
for
document
types
implemented
as
XML
Document
Type
Definitions
are
defined
through
Formal
Public
Identifiers
(FPIs).
Within
FPIs,
fields
are
separated
by
double
slash
character
sequences
(
//
).
The
various
fields
must
be
composed
as
follows:
-
The
leading
field
must
be
"-"
to
indicate
a
privately
defined
resource.
-
The
second
field
must
contain
the
name
of
the
organization
responsible
for
maintaining
the
named
item.
There
is
no
formal
registry
for
these
organization
names.
Each
organization
should
define
a
name
that
is
unique.
The
name
used
by
the
W3C
is,
for
example,
W3C
.
-
The
third
field
contains
two
constructs:
the
public
text
class
followed
by
the
public
text
description.
The
first
token
in
the
third
field
is
the
public
text
class
which
should
adhere
to
ISO
8879
Clause
10.2.2.1
Public
Text
Class.
Only
XHTML
Host
Language
conforming
documents
should
begin
the
public
text
description
with
the
token
XHTML.
The
public
text
description
should
contain
the
string
XHTML
if
the
document
type
is
Integration
Set
conforming.
The
field
must
also
contain
an
organization-defined
unique
identifier
(e.g.,
MyML
1.0).
This
identifier
should
be
composed
of
a
unique
name
and
a
version
identifier
that
can
be
updated
as
the
document
type
evolves.
-
The
fourth
field
defines
the
language
in
which
the
item
is
developed
(e.g.,
EN
).
Using
these
rules,
the
name
for
an
XHTML
Host
Language
conforming
document
type
might
be
-//MyCompany//DTD
XHTML
MyML
1.0//EN
.
The
name
for
an
XHTML
family
conforming
module
might
be
-//MyCompany//ELEMENTS
XHTML
MyElements
1.0//EN
.
The
name
for
an
XHTML
Integration
Set
conforming
document
type
might
be
-//MyCompany//DTD
Special
Markup
with
XHTML//EN
.
Each
module
defined
in
this
specification
is
given
a
unique
identifier
that
adheres
to
the
naming
rules
in
the
previous
section.
Over
time,
a
module
may
evolve.
A
logical
ramification
of
such
evolution
may
be
that
some
aspects
of
the
module
are
no
longer
compatible
with
its
previous
definition.
To
help
ensure
that
document
types
defined
against
modules
defined
in
this
specification
continue
to
operate,
the
identifiers
associated
with
a
module
that
changes
will
be
updated.
Specifically,
the
Formal
Public
Identifier
and
System
Identifier
of
the
module
will
be
changed
by
modifying
the
version
identifier
included
in
each.
Document
types
that
wish
to
incorporate
the
updated
functionality
will
need
to
be
similarly
updated.
In
addition,
the
earlier
version(s)
of
the
module
will
continue
to
be
available
via
its
earlier,
unique
identifier(s).
In
this
way,
document
types
developed
using
XHTML
modules
will
continue
to
function
seamlessly
using
their
original
definitions
even
as
the
collection
expands
and
evolves.
Similarly,
document
instances
written
against
such
document
types
will
continue
to
validate
using
the
earlier
module
definitions.
Other
XHTML
Family
Module
and
Document
Type
authors
are
encouraged
to
adopt
a
similar
strategy
to
ensure
the
continued
functioning
of
document
types
based
upon
those
modules
and
document
instances
based
upon
those
document
types.
4.
Defining
Abstract
Modules
This
section
is
normative
.
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.
4.1.
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.
-
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.
4.2.
Content
Types
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
;
this
is
short
for
"parsed
character
data",
denoting
sequences
of
characters
which
are
to
be
parsed
for
markup
by
an
XML
processor
.(processed
character
data).
A
content
type
can
also
be
defined
as
EMPTY
,
meaning
the
element
has
no
content
in
its
minimal
content
model.
4.3.
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
|
|
NAME
|
A
name
with
the
same
character
constraints
as
ID
above
|
|
NMTOKEN
|
A
name
composed
of
only
name
tokens
as
defined
in
XML
1.0
[XML]
|
|
NMTOKENS
|
One
or
more
white
space
separated
NMTOKEN
values
|
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
from
[ISO10646]
.
|
|
Charset
|
A
character
encoding,
as
per
[RFC2045]
.
|
|
Charsets
|
A
space-separated
list
of
character
encodings,
as
per
[RFC2045]
.
|
|
Color
|
The
attribute
value
type
"Color"
refers
to
color
definitions
as
specified
in
[SRGB]
.
A
color
value
may
either
be
a
hexadecimal
number
(prefixed
by
a
hash
mark)
or
one
of
the
following
sixteen
color
names.
The
color
names
are
case-insensitive.
Color
names
and
sRGB
values
|
Black
=
"#000000"
|
|
Green
=
"#008000"
|
|
Silver
=
"#C0C0C0"
|
|
Lime
=
"#00FF00"
|
|
Gray
=
"#808080"
|
|
Olive
=
"#808000"
|
|
White
=
"#FFFFFF"
|
|
Yellow
=
"#FFFF00"
|
|
Maroon
=
"#800000"
|
|
Navy
=
"#000080"
|
|
Red
=
"#FF0000"
|
|
Blue
=
"#0000FF"
|
|
Purple
=
"#800080"
|
|
Teal
=
"#008080"
|
|
Fuchsia
=
"#FF00FF"
|
|
Aqua
=
"#00FFFF"
|
Thus,
the
color
values
"#800080"
and
"Purple"
both
refer
to
the
color
purple.
|
|
ContentType
|
A
media
type,
as
per
[RFC2045]
.
|
|
ContentTypes
|
A
comma-separated
list
of
media
types,
as
per
[RFC2045]
.
|
|
Coords
|
Comma
separated
list
of
coordinates
to
use
in
defining
areas.
|
|
Datetime
|
Date
and
time
information.
|
|
FPI
|
A
character
string
representing
an
SGML
Formal
Public
Identifier.
|
|
FrameTarget
|
Frame
name
used
as
destination
for
results
of
certain
actions.
|
|
LanguageCode
|
A
language
code,
as
per
[BCP47]
.
|
|
LanguageCodes
|
A
comma-separated
list
of
language
ranges
with
optional
q
parameters,
as
defined
in
section
14.4
of
[
RFC2616
]
as
the
field
value
of
the
Accept-Language
request
header.
Individual
language
codes
should
conform
to
[
BCP47
].
|
|
Length
|
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.
|
|
LinkTypes
|
Authors
may
use
the
following
recognized
link
types,
listed
here
with
their
conventional
interpretations.
A
LinkTypes
value
refers
to
a
space-separated
list
of
link
types.
White
space
characters
are
not
permitted
within
link
types.
These
link
types
are
case-insensitive,
i.e.,
"Alternate"
has
the
same
meaning
as
"alternate".
User
agents,
search
engines,
etc.
may
interpret
these
link
types
in
a
variety
of
ways.
For
example,
user
agents
may
provide
access
to
linked
documents
through
a
navigation
bar.
-
Alternate
-
Designates
substitute
versions
for
the
document
in
which
the
link
occurs.
When
used
together
with
the
hreflang
attribute,
it
implies
a
translated
version
of
the
document.
When
used
together
with
the
media
attribute,
it
implies
a
version
designed
for
a
different
medium
(or
media).
-
Stylesheet
-
Refers
to
an
external
style
sheet.
See
the
Style
Module
for
details.
This
is
used
together
with
the
link
type
"Alternate"
for
user-selectable
alternate
style
sheets.
-
Start
-
Refers
to
the
first
document
in
a
collection
of
documents.
This
link
type
tells
search
engines
which
document
is
considered
by
the
author
to
be
the
starting
point
of
the
collection.
-
Next
-
Refers
to
the
next
document
in
a
linear
sequence
of
documents.
User
agents
may
choose
to
pre-load
the
"next"
document,
to
reduce
the
perceived
load
time.
-
Prev
-
Refers
to
the
previous
document
in
an
ordered
series
of
documents.
Some
user
agents
also
support
the
synonym
"Previous".
-
Contents
-
Refers
to
a
document
serving
as
a
table
of
contents.
Some
user
agents
also
support
the
synonym
ToC
(from
"Table
of
Contents").
-
Index
-
Refers
to
a
document
providing
an
index
for
the
current
document.
-
Glossary
-
Refers
to
a
document
providing
a
glossary
of
terms
that
pertain
to
the
current
document.
-
Copyright
-
Refers
to
a
copyright
statement
for
the
current
document.
-
Chapter
-
Refers
to
a
document
serving
as
a
chapter
in
a
collection
of
documents.
-
Section
-
Refers
to
a
document
serving
as
a
section
in
a
collection
of
documents.
-
Subsection
-
Refers
to
a
document
serving
as
a
subsection
in
a
collection
of
documents.
-
Appendix
-
Refers
to
a
document
serving
as
an
appendix
in
a
collection
of
documents.
-
Help
-
Refers
to
a
document
offering
help
(more
information,
links
to
other
sources
information,
etc.)
-
Bookmark
-
Refers
to
a
bookmark.
A
bookmark
is
a
link
to
a
key
entry
point
within
an
extended
document.
The
title
attribute
may
be
used,
for
example,
to
label
the
bookmark.
Note
that
several
bookmarks
may
be
defined
in
each
document.
Authors
may
wish
to
define
additional
link
types
not
described
in
this
specification.
If
they
do
so,
they
should
use
a
profile
to
cite
the
conventions
used
to
define
the
link
types.
Please
see
the
profile
attribute
of
the
head
element
for
more
information.
|
|
MediaDesc
|
The
MediaDesc
attribute
is
a
comma-separated
list
of
media
descriptors.
The
following
is
a
list
of
recognized
media
descriptors:
-
screen
-
Intended
for
non-paged
computer
screens.
-
tty
-
Intended
for
media
using
a
fixed-pitch
character
grid,
such
as
teletypes,
terminals,
or
portable
devices
with
limited
display
capabilities.
-
tv
-
Intended
for
television-type
devices
(low
resolution,
color,
limited
scrollability).
-
projection
-
Intended
for
projectors.
-
handheld
-
Intended
for
handheld
devices
(small
screen,
monochrome,
bitmapped
graphics,
limited
bandwidth).
-
print
-
Intended
for
paged,
opaque
material
and
for
documents
viewed
on
screen
in
print
preview
mode.
-
braille
-
Intended
for
braille
tactile
feedback
devices.
-
aural
-
Intended
for
speech
synthesizers.
-
all
-
Suitable
for
all
devices.
Future
versions
of
XHTML
may
introduce
new
values
and
may
allow
parameterized
values.
To
facilitate
the
introduction
of
these
extensions,
conforming
user
agents
must
be
able
to
parse
the
media
attribute
value
as
follows:
-
The
value
is
a
comma-separated
list
of
entries.
For
example,
media="screen, 3d-glasses, print and resolution > 90dpi"
is
mapped
to:
"screen"
"3d-glasses"
"print and resolution > 90dpi"
-
Each
entry
is
truncated
just
before
the
first
character
that
isn't
a
US
ASCII
letter
[a-zA-Z]
(ISO
10646
hex
41-5a,
61-7a),
digit
[0-9]
(hex
30-39),
or
hyphen-minus
(hex
2d).
In
the
example,
this
gives:
"screen"
"3d-glasses"
"print"
-
A
case-insensitive
match
is
then
made
with
the
set
of
media
types
defined
above.
User
agents
may
ignore
entries
that
don't
match.
In
the
example
we
are
left
with
screen
and
print
.
Note.
Style
sheets
may
include
media-dependent
variations
within
them
(e.g.,
the
CSS
@media
construct).
In
such
cases
it
may
be
appropriate
to
use
"
media
=all"
.
|
|
MultiLength
|
The
value
may
be
a
Length
or
a
relative
length.
A
relative
length
has
the
form
"i*",
where
"i"
is
an
integer.
When
allotting
space
among
elements
competing
for
that
space,
user
agents
allot
pixel
and
percentage
lengths
first,
then
divide
up
remaining
available
space
among
relative
lengths.
Each
relative
length
receives
a
portion
of
the
available
space
that
is
proportional
to
the
integer
preceding
the
"*".
The
value
"*"
is
equivalent
to
"1*".
Thus,
if
60
pixels
of
space
are
available
after
the
user
agent
allots
pixel
and
percentage
space,
and
the
competing
relative
lengths
are
1*,
2*,
and
3*,
the
1*
will
be
allotted
10
pixels,
the
2*
will
be
allotted
20
pixels,
and
the
3*
will
be
allotted
30
pixels.
|
|
MultiLengths
|
A
comma
separated
list
of
items
of
type
MultiLength
.
|
|
Number
|
One
or
more
digits
|
|
Pixels
|
The
value
is
an
integer
that
represents
the
number
of
pixels
of
the
canvas
(screen,
paper).
Thus,
the
value
"50"
means
fifty
pixels.
For
normative
information
about
the
definition
of
a
pixel,
please
consult
[CSS2]
|
|
QName
|
An
[
XMLNS
]-qualified
name.
See
QName
for
a
formal
definition.
|
|
QNames
|
A
space-separated
list
of
QNames,
as
defined
above.
|
|
Script
|
Script
data
can
be
the
content
of
the
"script"
element
and
the
value
of
intrinsic
event
attributes.
User
agents
must
not
evaluate
script
data
as
HTML
markup
but
instead
must
pass
it
on
as
data
to
a
script
engine.
The
case-sensitivity
of
script
data
depends
on
the
scripting
language.
Please
note
that
script
data
that
is
element
content
may
not
contain
character
references,
but
script
data
that
is
the
value
of
an
attribute
may
contain
them.
|
|
Shape
|
The
shape
of
a
region.
|
|
Text
|
Arbitrary
textual
data,
likely
meant
to
be
human-readable.
|
|
URI
|
A
Uniform
Resource
Identifier
Reference,
as
defined
by
the
type
anyURI
in
XMLSCHEMA
.
|
|
URIs
|
A
space-separated
list
of
URIs
as
defined
above.
|
|
URIREF
|
A
relative
URI
consisting
of
only
an
initial
'#'
and
a
fragment
identifier.
|
4.4.
An
Example
Abstract
Module
Definition
This
section
is
informative
This
section
defines
a
sample
abstract
module
as
an
example
of
how
to
take
advantage
of
the
syntax
rules
defined
above.
Since
this
example
is
trying
to
use
all
of
the
various
syntactic
elements
defined,
it
is
pretty
complicated.
Typical
module
definitions
would
be
much
simpler
than
this.
Finally,
note
that
this
module
references
the
attribute
collection
Common.
This
is
a
collection
defined
in
the
XHTML
Modularization
specification
that
includes
all
of
the
basic
attributes
that
most
elements
need.
4.4.1.
XHTML
Skiing
Module
The
XHTML
Skiing
Module
defines
markup
used
when
describing
aspects
of
a
ski
lodge.
The
elements
and
attributes
defined
in
this
module
are:
|
Elements
|
Attributes
|
Minimal
Content
Model
|
|
resort
|
Common,
href
(CDATA)
|
description,
Aspen+
|
|
lodge
|
Common
|
description,
(Aspen
-
lift)+
|
|
lift
|
Common,
href
|
description?
|
|
chalet
|
Common,
href
|
description?
|
|
room
|
Common,
href
|
description?
|
|
lobby
|
Common,
href
|
description?
|
|
fireplace
|
Common,
href
|
description?
|
|
description
|
Common
|
PCDATA*
|
This
module
also
defines
the
content
set
Aspen
with
the
minimal
content
model
lodge
|
lift
|
chalet
|
room
|
lobby
|
fireplace
.
5.
XHTML
Abstract
Modules
This
section
is
normative
.
This
section
specifies
the
contents
of
the
XHTML
abstract
modules.
These
modules
are
abstract
definitions
of
collections
of
elements,
attributes,
and
their
content
models.
These
abstract
modules
can
be
mapped
onto
any
appropriate
specification
mechanism.
XHTML
DTD
Module
Implementations
,
for
example,
maps
these
modules
onto
DTDs
as
described
in
[XML]
.
Content
developers
and
device
designers
should
view
this
section
as
a
guide
to
the
definition
of
the
functionality
provided
by
the
various
XHTML-defined
modules.
When
developing
documents
or
defining
a
profile
for
a
class
of
documents,
content
developers
can
determine
which
of
these
modules
are
essential
for
conveying
their
message.
When
designing
clients,
device
designers
should
develop
their
device
profiles
by
choosing
from
among
the
abstract
modules
defined
here.
Except
when
overridden
in
this
document,
the
semantics
of
these
elements
and
attributes
are
defined
in
[HTML4]
.
5.1.
Attribute
Collections
Many
of
the
abstract
modules
in
this
section
define
the
required
attributes
for
elements.
The
table
below
defines
some
collections
of
attributes
that
are
referenced
throughout
the
modules.
These
expressions
should
in
no
way
be
considered
normative
or
mandatory.
They
are
an
editorial
convenience
for
this
document.
When
used
in
the
remainder
of
this
section,
it
is
the
expansion
of
the
term
that
is
normative,
not
the
term
itself.
The
following
basic
attribute
sets
are
used
on
many
elements.
In
each
case
where
they
are
used,
their
use
is
identified
via
their
collection
name
rather
than
enumerating
the
list.
Each
of
the
attributes
defined
in
an
XHTML
attribute
collection
is
available
for
use
when
their
corresponding
module
is
included
in
an
XHTML
Host
Language
or
an
XHTML
Integration
Set.
In
such
a
situation,
the
attributes
are
available
for
use
in
the
definition
of
elements
that
are
NOT
in
the
XHTML
namespace
when
they
are
referenced
using
their
namespace-qualified
identifier
(e.g.,
xhtml:class
).
The
semantics
of
the
attributes
remain
the
same
regardless
of
whether
they
are
referenced
using
their
qualified
identifier
or
not.
It
is
an
error
to
use
an
XHTML
namespace-qualified
attribute
on
elements
from
the
XHTML
Namespace.
For
the
avoidance
of
doubt,
if
an
attribute
collection
is
referenced
by
an
element's
definition,
and
an
attribute
in
that
collection
is
also
explicitly
referenced
by
that
element's
definition,
this
does
NOT
cause
a
conflict.
It
is
up
to
the
markup
language
schema
implementation
to
update
the
content
models
accordingly.
|
Collection
Name
|
Attributes
in
Collection
|
|
Core
|
xml:space
("default"*
|
"preserve"),
class
(
CDATA
),
id
(
ID
),
title
(
CDATA
)
|
|
I18N
|
dir
("ltr"
|
"rtl"),
xml:lang
(
CDATA
)
|
|
Events
|
onclick
(
Script
),
ondblclick
(
Script
),
onmousedown
(
Script
),
onmouseup
(
Script
),
onmouseover
(
Script
),
onmousemove
(
Script
),
onmouseout
(
Script
),
onkeypress
(
Script
),
onkeydown
(
Script
),
onkeyup
(
Script
)
|
|
Style
|
style
(
CDATA
)
|
|
Common
|
Core
+
Events
+
I18N
+
Style
|
Note
that
the
Events
collection
is
only
defined
when
the
Intrinsic
Events
Module
is
selected.
Otherwise,
the
Events
collection
is
empty.
Also
note
that
the
Style
collection
is
only
defined
when
the
Style
Attribute
Module
is
selected.
Otherwise,
the
Style
collection
is
empty.
Finally,
note
that
the
I18N
collection
only
contains
the
xml:lang
attribute
unless
the
Bi-directional
Text
Module
module
is
selected.
5.2.
Core
Modules
The
core
modules
are
modules
that
are
required
to
be
present
in
any
XHTML
Family
Conforming
Document
Type
.
5.2.1.
Structure
Module
The
Structure
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:
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
attribute
is
defined
to
be
"http://www.w3.org/1999/xhtml".
Also
note
that
because
the
xmlns
attribute
is
treated
specially
by
XML
namespace-aware
parsers
[
XMLNAMES
],
it
is
legal
to
have
it
present
as
an
attribute
of
each
element.
However,
any
time
the
xmlns
attribute
is
used
in
the
context
of
an
XHTML
module,
whether
with
a
prefix
or
not,
the
value
of
the
attribute
shall
be
the
XHTML
namespace
defined
here.
See
Defining
the
Namespace
of
a
Module
for
more
on
rules
regarding
namespace
usage
with
XHTML
family
modules.
Implementations:
DTD
,
XML
Schema
5.2.2.
Text
Module
This
module
defines
all
of
the
basic
text
container
elements,
attributes,
and
their
content
model:
|
Element
|
Attributes
|
Minimal
Content
Model
|
|
abbr
|
Common
|
(PCDATA
|
Inline)*
|
|
acronym
|
Common
|
(PCDATA
|
Inline)*
|
|
address
|
Common
|
(PCDATA
|
Inline)*
|
|
blockquote
|
Common
,
cite
(
URI
)
|
(Heading
|
Block
|
List)*
|
|
br
|
Core
|
EMPTY
|
|
cite
|
Common
|
(PCDATA
|
Inline)*
|
|
code
|
Common
|
(PCDATA
|
Inline)*
|
|
dfn
|
Common
|
(PCDATA
|
Inline)*
|
|
div
|
Common
|
(PCDATA
|
Flow)*
|
|
em
|
Common
|
(PCDATA
|
Inline)*
|
|
h1
|
Common
|
(PCDATA
|
Inline)*
|
|
h2
|
Common
|
(PCDATA
|
Inline)*
|
|
h3
|
Common
|
(PCDATA
|
Inline)*
|
|
h4
|
Common
|
(PCDATA
|
Inline)*
|
|
h5
|
Common
|
(PCDATA
|
Inline)*
|
|
h6
|
Common
|
(PCDATA
|
Inline)*
|
|
kbd
|
Common
|
(PCDATA
|
Inline)*
|
|
p
|
Common
|
(PCDATA
|
Inline)*
|
|
pre
|
Common
|
(PCDATA
|
Inline)*
|
|
q
|
Common
,
cite
(
URI
)
|
(PCDATA
|
Inline)*
|
|
samp
|
Common
|
(PCDATA
|
Inline)*
|
|
span
|
Common
|
(PCDATA
|
Inline)*
|
|
strong
|
Common
|
(PCDATA
|
Inline)*
|
|
var
|
Common
|
(PCDATA
|
Inline)*
|
The
minimal
content
model
for
this
module
defines
some
content
sets:
-
Heading
-
h1
|
h2
|
h3
|
h4
|
h5
|
h6
-
Block
-
address
|
blockquote
|
div
|
p
|
pre
-
Inline
-
abbr
|
acronym
|
br
|
cite
|
code
|
dfn
|
em
|
kbd
|
q
|
samp
|
span
|
strong
|
var
-
Flow
-
Heading
|
Block
|
Inline
Implementations:
DTD
,
XML
Schema
5.2.3.
Hypertext
Module
The
Hypertext
Module
provides
the
element
that
is
used
to
define
hypertext
links
to
other
resources.
This
module
supports
the
following
element
and
attributes:
This
module
adds
the
a
element
to
the
Inline
content
set
of
the
Text
Module.
Implementations:
DTD
,
XML
Schema
5.2.4.
List
Module
As
its
name
suggests,
the
List
Module
provides
list-oriented
elements.
Specifically,
the
List
Module
supports
the
following
elements
and
attributes:
This
module
also
defines
the
content
set
List
with
the
minimal
content
model
(dl
|
ol
|
ul)+
and
adds
this
set
to
the
Flow
content
set
of
the
Text
Module.
Implementations:
DTD
,
XML
Schema
5.3.
Applet
Module
This
module
is
deprecated.
Similar
functionality
can
be
found
in
the
Object
Module
.
The
Applet
Module
provides
elements
for
referencing
external
applications.
Specifically,
the
Applet
Module
supports
the
following
elements
and
attributes:
|
Element
|
Attributes
|
Minimal
Content
Model
|
|
applet
|
Core,
alt*
(
Text
),
archive
(
CDATA
),
code
(
CDATA
),
codebase
(
URI
),
height*
(
Length
),
object
(
CDATA
),
width*
(
Length
)
|
(PCDATA
|
Flow
|
param)*
|
|
param
|
id
(
ID
),
name*
(
CDATA
),
type
(
ContentType
),
value
(
CDATA
),
valuetype
("data"*
|
"ref"
|
"object")
|
EMPTY
|
When
the
Applet
Module
is
used,
it
adds
the
applet
element
to
the
Inline
content
set
of
the
Text
Module.
Implementations:
DTD
,
XML
Schema
5.4.
Text
Extension
Modules
This
section
defines
a
variety
of
additional
textual
markup
modules.
5.4.1.
Presentation
Module
This
module
defines
elements,
attributes,
and
a
minimal
content
model
for
simple
presentation-related
markup:
|
Element
|
Attributes
|
Minimal
Content
Model
|
|
b
|
Common
|
(PCDATA
|
Inline)*
|
|
big
|
Common
|
(PCDATA
|
Inline)*
|
|
hr
|
Common
|
EMPTY
|
|
i
|
Common
|
(PCDATA
|
Inline)*
|
|
small
|
Common
|
(PCDATA
|
Inline)*
|
|
sub
|
Common
|
(PCDATA
|
Inline)*
|
|
sup
|
Common
|
(PCDATA
|
Inline)*
|
|
tt
|
Common
|
(PCDATA
|
Inline)*
|
When
this
module
is
used,
the
hr
element
is
added
to
the
Block
content
set
of
the
Text
Module.
In
addition,
the
b,
big,
i,
small,
sub,
sup,
and
tt
elements
are
added
to
the
Inline
content
set
of
the
Text
Module.
Implementations:
DTD
,
XML
Schema
5.4.2.
Edit
Module
This
module
defines
elements
and
attributes
for
use
in
editing-related
markup:
|
Element
|
Attributes
|
Minimal
Content
Model
|
|
del
|
Common
,
cite
(
URI
),
datetime
(
Datetime
)
|
(PCDATA
|
Flow)*
|
|
ins
|
Common
,
cite
(
URI
),
datetime
(
Datetime
)
|
(PCDATA
|
Flow)*
|
When
this
module
is
used,
the
del
and
ins
elements
are
added
to
the
Inline
content
set
of
the
Text
Module.
Implementations:
DTD
,
XML
Schema
5.4.3.
Bi-directional
Text
Module
The
Bi-directional
Text
module
defines
an
element
that
can
be
used
to
declare
the
bi-directional
rules
for
the
element's
content.
|
Elements
|
Attributes
|
Minimal
Content
Model
|
|
bdo
|
Core
,
dir*
("ltr"
|
"rtl"),
xml:lang
|
(PCDATA
|
Inline)*
|
When
this
module
is
used,
the
bdo
element
is
added
to
the
Inline
content
set
of
the
Text
Module.
Selecting
this
module
also
adds
the
attribute
dir
("ltr"
|
"rtl")
to
the
I18N
attribute
collection.
Implementations:
DTD
,
XML
Schema
The
Basic
Forms
Module
provides
the
form-related
elements,
but
only
in
a
limited
form.
Specifically,
the
Basic
Forms
Module
supports
the
following
elements,
attributes,
and
minimal
content
model:
|
Elements
|
Attributes
|
Minimal
Content
Model
|
|
form
|
Common
,
action*
(
URI
),
enctype
(
ContentType
)
method
("get"*
|
"post"),
name
(
CDATA
)
|
(Heading
|
List
|
Block
-
form)+
|
|
input
|
Common
,
accesskey
(
Character
),
checked
("checked"),
maxlength
(
Number
),
name
(
CDATA
),
size
(
Number
),
src
(
URI
),
tabindex
(
Number
),
type
("text"*
|
"password"
|
"checkbox"
|
"radio"
|
"submit"
|
"reset"
|
"hidden"
),
value
(
CDATA
)
|
EMPTY
|
|
label
|
Common
,
accesskey
(
Character
),
for
(
IDREF
)
|
(PCDATA
|
Inline
-
label)*
|
|
select
|
Common
,
multiple
("multiple"),
name
(
CDATA
),
size
(
Number
),
tabindex
(
Number
)
|
option+
|
|
option
|
Common
,
selected
("selected"),
value
(
CDATA
)
|
PCDATA
|
|
textarea
|
Common
,
accesskey
(
Character
),
cols*
(
Number
),
name
(
CDATA
),
rows*
(
Number
),
tabindex
(
Number
)
|
PCDATA
|
This
module
defines
two
content
sets:
-
Form
-
form
-
Formctrl
-
input
|
label
|
select
|
textarea
When
this
module
is
used,
it
adds
the
Form
content
set
to
the
Block
content
set
and
it
adds
the
Formctrl
content
set
to
the
Inline
content
set
as
these
are
defined
in
the
Text
Module.
The
Basic
Forms
Module
is
a
subset
of
the
Forms
Module.
These
modules
may
not
be
used
together
in
a
single
document
type.
Implementations:
DTD
,
XML
Schema
The
Forms
Module
provides
all
of
the
forms
features
found
in
HTML
4.0.
Specifically,
the
Forms
Module
supports:
|
Elements
|
Attributes
|
Minimal
Content
Model
|
|
form
|
Common
,
accept
(
ContentTypes
),
accept-charset
(
Charsets
),
action*
(
URI
),
method
("get"*
|
"post"),
name
(
CDATA
),
enctype
(
ContentType
)
|
(Heading
|
List
|
Block
-
form
|
fieldset)+
|
|
input
|
Common
,
accept
(
ContentTypes
),
accesskey
(
Character
),
alt
(
Text
),
checked
("checked"),
disabled
("disabled"),
maxlength
(
Number
),
name
(
CDATA
),
readonly
("readonly"),
size
(
Number
),
src
(
URI
),
tabindex
(
Number
),
type
("text"*
|
"password"
|
"checkbox"
|
"button"
|
"radio"
|
"submit"
|
"reset"
|
"file"
|
"hidden"
|
"image"),
value
(
CDATA
)
|
EMPTY
|
|
select
|
Common
,
disabled
("disabled"),
multiple
("multiple"),
name
(
CDATA
),
size
(
Number
),
tabindex
(
Number
)
|
(optgroup
|
option)+
|
|
option
|
Common
,
disabled
("disabled"),
label
(
Text
),
selected
("selected"),
value
(
CDATA
)
|
PCDATA
|
|
textarea
|
Common
,
accesskey
(
Character
),
cols*
(
Number
),
disabled
("disabled"),
name
(
CDATA
),
readonly
("readonly"),
rows*
(
Number
),
tabindex
(
Number
)
|
PCDATA
|
|
button
|
Common
,
accesskey
(
Character
),
disabled
("disabled"),
name
(
CDATA
),
tabindex
(
Number
),
type
("button"
|
"submit"*
|
"reset"),
value
(
CDATA
)
|
(PCDATA
|
Heading
|
List
|
Block
-
Form
|
Inline
-
Formctrl)*
|
|
fieldset
|
Common
|
(PCDATA
|
legend
|
Flow)*
|
|
label
|
Common
,
accesskey
(
Character
),
for
(
IDREF
)
|
(PCDATA
|
Inline
-
label)*
|
|
legend
|
Common
,
accesskey
(
Character
)
|
(PCDATA
|
Inline)*
|
|
optgroup
|
Common
,
disabled
("disabled"),
label*
(
Text
)
|
option+
|
This
module
defines
two
content
sets:
-
Form
-
form
|
fieldset
-
Formctrl
-
input
|
select
|
textarea
|
label
|
button
When
this
module
is
used,
it
adds
the
Form
content
set
to
the
Block
content
set
and
it
adds
the
Formctrl
content
set
to
the
Inline
content
set
as
these
are
defined
in
the
Text
Module.
The
Forms
Module
is
a
superset
of
the
Basic
Forms
Module.
These
modules
may
not
be
used
together
in
a
single
document
type.
Implementations:
DTD
,
XML
Schema
5.6.
Table
Modules
5.6.1.
Basic
Tables
Module
The
Basic
Tables
Module
provides
table-related
elements,
but
only
in
a
limited
form.
Specifically,
the
Basic
Tables
Module
supports:
|
Elements
|
Attributes
|
Minimal
Content
Model
|
|
caption
|
Common
|
(PCDATA
|
Inline)*
|
|
table
|
Common
,
width
(
Length
),
summary
(
Text
)
|
caption?,
tr+
|
|
td
|
Common
,
abbr
(
Text
),
align
("left"
|
"center"
|
"right"),
axis
(
CDATA
),
colspan
(
Number
),
headers
(
IDREFS
),
rowspan
(
Number
),
scope
("row"
|
"col"),
valign
("top"
|
"middle"
|
"bottom")
|
(PCDATA
|
Flow
-
table)*
|
|
th
|
Common
,
abbr
(
Text
),
align
("left"
|
"center"
|
"right"),
axis
(
CDATA
),
colspan
(
Number
),
headers
(
IDREFS
),
rowspan
(
Number
),
scope
("row"
|
"col"
),
valign
("top"
|
"middle"
|
"bottom")
|
(PCDATA
|
Flow
-
table)*
|
|
tr
|
Common
,
align
("left"
|
"center"
|
"right"),
valign
("top"
|
"middle"
|
"bottom")
|
(td
|
th)+
|
When
this
module
is
used,
it
adds
the
table
element
to
the
Block
content
set
as
defined
in
the
Text
Module.
The
Basic
Tables
Module
is
a
subset
of
the
Tables
Module.
These
modules
may
not
be
used
together
in
a
single
document
type.
Implementations:
DTD
,
XML
Schema
5.6.2.
Tables
Module
As
its
name
suggests,
the
Tables
Module
provides
table-related
elements
that
are
better
able
to
be
accessed
by
non-visual
user
agents.
Specifically,
the
Tables
Module
supports
the
following
elements,
attributes,
and
content
model:
|
Elements
|
Attributes
|
Minimal
Content
Model
|
|
caption
|
Common
|
(PCDATA
|
Inline)*
|
|
table
|
Common
,
border
(
Pixels
),
cellpadding
(
Length
),
cellspacing
(
Length
),
frame
("void"
|
"above"
|
"below"
|
"hsides"
|
"lhs"
|
"rhs"
|
"vsides"
|
"box"
|
"border"),
rules
("none"
|
"groups"
|
"rows"
|
"cols"
|
"all"),
summary
(
Text
),
width
(
Length
)
|
caption?,
(
col*
|
colgroup*
),
((
thead?,
tfoot?,
tbody+
)
|
(
tr+
))
|
|
td
|
Common
,
abbr
(
Text
),
align
("left"
|
"center"
|
"right"
|
"justify"
|
"char"),
axis
(
CDATA
),
char
(
Character
),
charoff
(
Length
),
colspan
(
Number
),
headers
(
IDREFS
),
rowspan
(
Number
),
scope
("row"
|
"col"
|
"rowgroup"
|
"colgroup"),
valign
("top"
|
"middle"
|
"bottom"
|
"baseline")
|
(PCDATA
|
Flow)*
|
|
th
|
Common
,
abbr
(
Text
),
align
("left"
|
"center"
|
"right"
|
"justify"
|
"char"),
axis
(
CDATA
),
char
(
Character
),
charoff
(
Length
),
colspan
(
Number
),
headers
(
IDREFS
),
rowspan
(
Number
),
scope
("row"
|
"col"
|
"rowgroup"
|
"colgroup"),
valign
("top"
|
"middle"
|
"bottom"
|
"baseline")
|
(PCDATA
|
Flow)*
|
|
tr
|
Common
,
align
("left"
|
"center"
|
"right"
|
"justify"
|
"char"),
char
(
Character
),
charoff
(
Length
),
valign
("top"
|
"middle"
|
"bottom"
|
"baseline")
|
(td
|
th)+
|
|
col
|
Common
,
align
("left"
|
"center"
|
"right"
|
"justify"
|
"char"),
char
(
Character
),
charoff
(
Length
),
span
(
Number
),
valign
("top"
|
"middle"
|
"bottom"
|
"baseline"),
width
(
MultiLength
)
|
EMPTY
|
|
colgroup
|
Common
,
align
("left"
|
"center"
|
"right"
|
"justify"
|
"char"),
char
(
Character
),
charoff
(
Length
),
span
(
Number
),
valign
("top"
|
"middle"
|
"bottom"
|
"baseline"),
width
(
MultiLength
)
|
col*
|
|
tbody
|
Common
,
align
("left"
|
"center"
|
"right"
|
"justify"
|
"char"),
char
(
Character
),
charoff
(
Length
),
valign
("top"
|
"middle"
|
"bottom"
|
"baseline")
|
tr+
|
|
thead
|
Common
,
align
("left"
|
"center"
|
"right"
|
"justify"
|
"char"),
char
(
Character
),
charoff
(
Length
),
valign
("top"
|
"middle"
|
"bottom"
|
"baseline")
|
tr+
|
|
tfoot
|
Common
,
align
("left"
|
"center"
|
"right"
|
"justify"
|
"char"),
char
(
Character
),
charoff
(
Length
),
valign
("top"
|
"middle"
|
"bottom"
|
"baseline")
|
tr+
|
When
this
module
is
used,
it
adds
the
table
element
to
the
Block
content
set
of
the
Text
Module.
The
Tables
Module
is
a
superset
of
the
Basic
Tables
Module.
These
modules
may
not
be
used
together
in
a
single
document
type.
Implementations:
DTD
,
XML
Schema
5.7.
Image
Module
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:
When
this
module
is
used,
it
adds
the
img
element
to
the
Inline
content
set
of
the
Text
Module.
Implementations:
DTD
,
XML
Schema
5.8.
Client-side
Image
Map
Module
The
Client-side
Image
Map
Module
provides
elements
for
client
side
image
maps.
It
requires
that
the
Image
Module
(or
another
module
that
supports
the
img
element)
be
included.
The
Client-side
Image
Map
Module
supports
the
following
elements:
|
Elements
|
Attributes
|
Minimal
Content
Model
|
|
a&
|
coords
(
CDATA
),
shape
("rect"
|
"circle"
|
"poly"
|
"default")
|
n/a
|
|
area
|
Common
,
accesskey
(
Character
),
alt*
(
Text
),
coords
(
CDATA
),
href
(
URI
),
nohref
("nohref"),
shape
("rect"*
|
"circle"
|
"poly"
|
"default"),
tabindex
(
Number
)
|
EMPTY
|
|
img&
|
usemap
(
URIREF
)
|
n/a
|
|
input&
|
usemap
(
URIREF
)
|
Note:
Only
when
the
Forms
or
Basic
Forms
module
is
included
|
|
map
|
I18N
,
Events
,
class
(
CDATA
),
id*
(
ID
),
title
(
CDATA
)
|
((Heading
|
Block)
|
area)+
|
|
object&
|
usemap
(
URIREF
)
|
Note:
Only
when
the
object
module
is
included
|
When
this
module
is
used,
the
map
element
is
added
to
the
Inline
content
set
of
the
Text
Module.
Implementations:
DTD
,
XML
Schema
5.9.
Server-side
Image
Map
Module
The
Server-side
Image
Map
Module
provides
support
for
image-selection
and
transmission
of
selection
coordinates.
It
requires
that
the
Image
Module
(or
another
module
that
supports
the
img
element)
be
included.
The
Server-side
Image
Map
Module
supports
the
following
attributes:
|
Elements
|
Attributes
|
Minimal
Content
Model
|
Notes
|
|
img&
|
ismap
("ismap")
|
n/a
|
|
|
input&
|
ismap
("ismap")
|
n/a
|
When
the
Forms
or
Basic
Forms
Module
is
selected.
|
Implementations:
DTD
,
XML
Schema
5.10.
Object
Module
The
Object
Module
provides
elements
for
general-purpose
object
inclusion.
Specifically,
the
Object
Module
supports:
|
Elements
|
Attributes
|
Minimal
Content
Model
|
|
object
|
Common
,
archive
(
URIs
),
classid
(
URI
),
codebase
(
URI
),
codetype
(
ContentType
),
data
(
URI
),
declare
("declare"),
height
(
Length
),
name
(
CDATA
),
standby
(
Text
),
tabindex
(
Number
),
type
(
ContentType
),
width
(
Length
)
|
(PCDATA
|
Flow
|
param)*
|
|
param
|
id
(
ID
),
name*
(
CDATA
),
type
(
ContentType
),
value
(
CDATA
),
valuetype
("data"*
|
"ref"
|
"object")
|
EMPTY
|
When
this
module
is
used,
it
adds
the
object
element
to
the
Inline
content
set
of
the
Text
Module.
Implementations:
DTD
,
XML
Schema
5.11.
Frames
Module
As
its
name
suggests,
the
Frames
Module
provides
frame-related
elements.
Specifically,
the
Frames
Module
supports:
|
Elements
|
Attributes
|
Minimal
Content
Model
|
|
frameset
|
Core
,
cols
(
MultiLength
),
rows
(
MultiLength
)
|
(frameset
|
frame)+,
noframes?
|
|
frame
|
Core
,
frameborder
("1"
|
"0"),
longdesc
(
URI
),
marginheight
(
Pixels
),
marginwidth
(
Pixels
),
noresize
("noresize"),
scrolling
("yes"
|
"no"
|
"auto"*),
src
(
URI
)
|
EMPTY
|
|
noframes
|
Common
|
body
|
When
this
module
is
selected,
the
minimal
content
model
of
the
html
element
of
the
Structure
Module
is
changed
to
(head,
frameset)
.
Implementations:
DTD
,
XML
Schema
5.12.
Target
Module
The
content
of
a
frame
can
specify
destination
targets
for
a
selection.
This
module
adds
the
target
attribute
to
the
area
and
link
defining
elements.
This
is
defined
as
a
separate
module
so
it
can
be
included
in
documents
that
will
be
included
in
frames
and
documents
that
use
the
target
feature
to
open
a
new
window.
|
Elements
|
Attributes
|
Notes
|
|
a&
|
target
(
CDATA
)
|
|
|
area&
|
target
(
CDATA
)
|
When
the
Client-side
Image
Map
Module
is
selected.
|
|
base&
|
target
(
CDATA
)
|
When
the
Base
Module
is
selected.
|
|
link&
|
target
(
CDATA
)
|
When
the
Link
Module
is
selected.
|
|
form&
|
target
(
CDATA
)
|
When
the
Basic
Forms
or
Forms
module
is
selected.
|
Implementations:
DTD
,
XML
Schema
5.13.
Iframe
Module
The
Iframe
Module
defines
an
element
for
the
definition
of
inline
frames.
The
element
and
attribute
included
in
this
module
are:
|
Elements
|
Attributes
|
Minimal
Content
Model
|
|
iframe
|
Core
,
frameborder
("1"
|
"0"),
height
(
Length
),
longdesc
(
URI
),
marginheight
(
Pixels
),
marginwidth
(
Pixels
),
scrolling
("yes"
|
"no"
|
"auto"*),
src
(
URI
),
width
(
Length
)
|
(PCDATA
|
Flow)*
|
When
this
module
is
used,
the
iframe
element
is
added
to
the
Inline
content
set
as
defined
by
the
Text
Module.
Implementations:
DTD
,
XML
Schema
5.14.
Intrinsic
Events
Module
Intrinsic
events
are
attributes
that
are
used
in
conjunction
with
elements
that
can
have
specific
events
occur
when
certain
actions
are
performed
by
the
user.
The
attributes
indicated
in
the
following
table
are
added
to
the
attribute
set
for
their
respective
elements
only
when
the
modules
defining
those
elements
are
selected.
Note
also
that
selection
of
this
module
defines
the
attribute
collection
Events
as
described
above.
Attributes
defined
by
this
module
are:
|
Elements
|
Attributes
|
Notes
|
|
a&
|
onblur
(
Script
),
onfocus
(
Script
)
|
|
|
area&
|
onblur
(
Script
),
onfocus
(
Script
)
|
When
the
Client-side
Image
Map
Module
is
also
used
|
|
frameset&
|
onload
(
Script
),
onunload
(
Script
)
|
When
the
Frames
Module
is
also
used.
|
|
form&
|
onreset
(
Script
),
onsubmit
(
Script
)
|
When
the
Basic
Forms
or
Forms
Module
is
used
|
|
body&
|
onload
(
Script
),
onunload
(
Script
)
|
|
|
label&
|
onblur
(
Script
),
onfocus
(
Script
)
|
When
the
Forms
Module
is
used
|
|
input&
|
onblur
(
Script
),
onchange
(
Script
),
onfocus
(
Script
),
onselect
(
Script
)
|
When
the
Basic
Forms
or
Forms
Module
is
used
|
|
select&
|
onblur
(
Script
),
onchange
(
Script
),
onfocus
(
Script
)
|
When
the
Basic
Forms
or
Forms
Module
is
used
|
|
textarea&
|
onblur
(
Script
),
onchange
(
Script
),
onfocus
(
Script
),
onselect
(
Script
)
|
When
the
Basic
Forms
or
Forms
Module
is
used
|
|
button&
|
onblur
(
Script
),
onfocus
(
Script
)
|
When
the
Forms
Module
is
used
|
When
this
module
is
selected,
it
activates
the
Events
Attribute
Collection
.
Implementations:
DTD
,
XML
Schema
The
Metainformation
Module
defines
an
element
that
describes
information
within
the
declarative
portion
of
a
document
(in
XHTML
within
the
head
element).
This
module
includes
the
following
element:
When
this
module
is
selected,
the
meta
element
is
added
to
the
content
model
of
the
head
element
as
defined
in
the
Structure
Module.
Implementations:
DTD
,
XML
Schema
5.16.
Scripting
Module
The
Scripting
Module
defines
elements
that
are
used
to
contain
information
pertaining
to
executable
scripts
or
the
lack
of
support
for
executable
scripts.
Elements
and
attributes
included
in
this
module
are:
When
this
module
is
used,
the
script
and
noscript
elements
are
added
to
the
Block
and
Inline
content
sets
of
the
Text
Module.
In
addition,
the
script
element
is
added
to
the
content
model
of
the
head
element
defined
in
the
Structure
Module.
Implementations:
DTD
,
XML
Schema
5.17.
Style
Sheet
Module
The
Style
Sheet
Module
defines
an
element
to
be
used
when
declaring
internal
style
sheets.
The
element
and
attributes
defined
by
this
module
are:
When
this
module
is
used,
it
adds
the
style
element
to
the
content
model
of
the
head
element
of
the
Structure
Module.
Implementations:
DTD
,
XML
Schema
5.18.
Style
Attribute
Module
The
Style
Attribute
Module
defines
the
style
attribute.
When
this
module
is
selected,
it
activates
the
Style
Attribute
Collection
.
Implementations:
DTD
,
XML
Schema
5.19.
Link
Module
The
Link
Module
defines
an
element
that
can
be
used
to
define
links
to
external
resources.
These
resources
are
often
used
to
augment
the
user
agent's
ability
to
process
the
associated
XHTML
document.
The
element
and
attributes
included
in
this
module
are:
When
this
module
is
used,
it
adds
the
link
element
to
the
content
model
of
the
head
element
as
defined
in
the
Structure
Module.
Implementations:
DTD
,
XML
Schema
5.20.
Base
Module
The
Base
Module
defines
an
element
that
can
be
used
to
define
a
base
URI
against
which
relative
URIs
in
the
document
will
be
resolved.
The
element
and
attribute
included
in
this
module
are:
|
Elements
|
Attributes
|
Minimal
Content
Model
|
|
base
|
href*
(
URI
),
id
(
ID
)
|
EMPTY
|
When
this
module
is
used,
it
adds
the
base
element
to
the
content
model
of
the
head
element
of
the
Structure
Module.
Implementations:
DTD
,
XML
Schema
5.21.
Name
Identification
Module
This
module
is
deprecated.
The
Name
Identification
Module
defines
the
attribute
name
for
a
collection
of
elements.
The
name
attribute
was
used
historically
to
identify
certain
elements
within
HTML
documents.
While
the
name
attribute
has
been
supplanted
by
the
id
attribute
in
all
of
these
elements,
there
may
be
instances
where
markup
languages
will
wish
to
support
both.
Such
markup
languages
may
do
so
by
including
this
module.
Note
that
by
including
this
module,
both
the
name
and
id
attributes
are
defined
for
the
elements
indicated.
In
this
situation,
if
the
name
attribute
is
defined
for
an
element,
the
id
attribute
must
also
be
defined.
Further,
these
attributes
must
both
have
the
same
value.
Finally,
when
documents
that
use
this
attribute
are
served
as
Internet
Media
Type
"text/xml"
or
"application/xml",
the
value
of
the
name
attribute
on
these
elements
shall
not
be
used
as
a
fragment
identifier.
|
Elements
|
Attributes
|
Notes
|
|
a&
|
name
(
CDATA
)
|
|
|
applet&
|
name
(
CDATA
)
|
When
the
Applet
Module
is
selected.
|
|
frame&
|
name
(
CDATA
)
|
When
the
Frames
Module
is
selected.
|
|
iframe&
|
name
(
CDATA
)
|
When
the
Iframe
Module
is
selected.
|
|
map&
|
name
(
CDATA
)
|
When
the
Client-side
Image
Map
Module
is
selected.
|
Implementations:
DTD
,
XML
Schema
5.22.
Legacy
Module
This
module
is
deprecated.
The
Legacy
Module
defines
elements
and
attributes
that
were
already
deprecated
in
previous
versions
of
HTML
and
XHTML,
and
remain
deprecated
in
XHTML
Modularization.
Markup
language
authors
should
no
longer
use
these
elements
and
attributes.
Note:
This
module
is
not
intended
to
reproduce
all
of
the
deprecated
elements,
attributes,
and
content
models.
Just
those
that
were
thought
to
be
of
maximal
use
at
the
time
this
specification
was
written.
The
following
table
defines
the
elements
and
attributes
that
are
defined
when
the
Legacy
Module
is
selected.
|
Elements
|
Attributes
|
Minimal
Content
Model
|
|
basefont
|
color
(
Color
),
face
(
CDATA
),
id
(
ID
),
size
(
CDATA
)
|
EMPTY
|
|
center
|
Common
|
(PCDATA
|
Flow)*
|
|
dir
|
Common
,
compact
("compact")
|
(li)+
|
|
font
|
Core
,
I18N
,
color
(
Color
),
face
(
CDATA
),
size
(
CDATA
)
|
(PCDATA
|
Inline)*
|
|
isindex
|
Core
,
I18N
,
prompt
(
Text
)
|
EMPTY
|
|
menu
|
Common
,
compact
("compact")
|
(li)+
|
|
s
|
Common
|
(PCDATA
|
Inline)*
|
|
strike
|
Common
|
(PCDATA
|
Inline)*
|
|
u
|
Common
|
(PCDATA
|
Inline)*
|
The
following
table
shows
additional
attributes
for
elements
defined
elsewhere
when
the
Legacy
module
is
selected.
|
Elements
|
Attributes
|
Notes
|
|
applet&
|
align
("top"
|
"middle"
|
"bottom"
|
"left"
|
"right"),
hspace
(
Pixels
),
vspace
(
Pixels
)
|
When
then
Applet
Module
is
selected.
|
|
body&
|
alink
(
Color
),
background
(
URI
),
bgcolor
(
Color
),
link
(
Color
),
text
(
Color
),
vlink
(
Color
)
|
|
|
br&
|
clear
("left"
|
"all"
|
"right"
|
"none"*)
|
|
|
caption&
|
align
("top"
|
"bottom"
|
"left"
|
"right")
|
|
|
div&
|
align
("left"
|
"center"
|
"right"
|
"justify")
|
|
|
dl&
|
compact
("compact")
|
|
|
h1-h6&
|
align
("left"
|
"center"
|
"right"
|
"justify")
|
|
|
hr&
|
align
("left"
|
"center"
|
"right"
|
"justify"),
noshade
("noshade"),
size
(
Pixels
),
width
(
Length
),
|
|
|
img&
|
align
("top"
|
"middle"
|
"bottom"
|
"left"
|
"right"),
border
(
Pixels
),
hspace
(
Pixels
),
vspace
(
Pixels
)
|
|
|
input&
|
align
("top"
|
"middle"
|
"bottom"
|
"left"
|
"right")
|
When
the
Basic
Forms
or
Forms
Module
is
selected.
|
|
legend&
|
align
("left"
|
"center"
|
"right"
|
"justify")
|
When
the
Forms
Module
is
selected.
|
|
li&
|
type
(
CDATA
),
value
(
Number
)
|
|
|
object&
|
align
("top"
|
"middle"
|
"bottom"
|
"left"
|
"right"),
border
(
Pixels
),
hspace
(
Pixels
),
vspace
(
Pixels
)
|
When
the
Object
Module
is
selected.
|
|
ol&
|
compact
("compact"),
start
(
Number
),
type
(
CDATA
)
|
|
|
p&
|
align
("left"
|
"center"
|
"right",
"justify")
|
|
|
pre&
|
width
(
Number
)
|
|
|
script&
|
language
(
CDATA
)
|
When
the
Scripting
module
is
selected.
|
|
table&
|
align
("left"
|
"center"
|
"right"),
bgcolor
(
Color
)
|
When
the
Basic
Tables
or
Tables
module
is
selected.
|
|
tr&
|
bgcolor
(
Color
)
|
When
the
Basic
Tables
or
Tables
module
is
selected.
|
|
th&
|
bgcolor
(
Color
),
height
(
Length
),
nowrap
("nowrap"),
width
(
Length
)
|
When
the
Basic
Tables
or
Tables
module
is
selected.
|
|
td&
|
bgcolor
(
Color
),
height
(
Length
),
nowrap
("nowrap"),
width
(
Length
)
|
When
the
Basic
Tables
or
Tables
module
is
selected.
|
|
ul&
|
compact
("compact"),
type
(
CDATA
)
|
|
Implementations:
DTD
,
XML
Schema
A.
Building
Schema
Modules
This
appendix
is
normative
.
XHTML
modules
are
implemented
as
XML
Schemas.
When
these
XML
Schemas
are
assembled
in
a
specific
manner
(described
in
Developing
Schemas
with
defined
and
extended
modules
),
the
resulting
Schema
is
a
representation
of
a
complete
document
type.
This
representation
can
then
be
used
for
validation
of
instances
of
the
document
type.
The
key
to
combining
these
schema
components
into
a
meaningful,
cohesive
schema
is
the
rules
used
to
define
the
individual
XML
Schemas.
This
section
defines
those
rules.
When
these
rules
are
followed,
markup
language
authors
can
be
confident
that
their
modules
will
interface
cleanly
with
other
XHTML-compatible
modules.
Modules
conforming
to
these
rules
also
need
to
satisfy
the
conformance
requirements
defined
in
XHTML
Family
Module
Conformance
in
order
to
be
called
XHTML
Family
Modules
.
This
specification
classifies
named
content
model
into
categories
and
names
them
consistently
using
the
following
suffixes
-
.content
-
model
group
definitions
use
the
suffix
.content
when
they
are
used
to
represent
the
content
model
of
an
element
type.
-
.class
-
model
group
definitions
use
the
suffix
.class
when
they
are
used
to
represent
elements
of
the
same
class.
-
.mix
-
model
group
definitions
use
the
suffix
.mix
when
they
are
used
to
represent
a
collection
of
element
types
from
different
classes.
-
.extra
-
model
group
definitions
use
the
suffix
.extra
when
they
are
used
to
extend
other
groups
above.
-
.export
-
model
group
definitions
add
the
suffix
.export
when
they
are
to
be
used
by
a
host
language
as
the
basis
for
extending
the
related
content
model
(e.g.,
xhtml.Flow.mix
could
have
an
xhtml.Flow.mix.export
that
defines
a
collection
of
elements
that
must
be
included
in
a
redefinition
of
the
xhtml.Flow.mix
by
a
host
language.
-
.type
-
named
complex
type
definitions
use
the
suffix
.type
when
they
are
used
to
represent
type
of
an
element.
Types
usually
include
the
.attlist
and
.content
components.
-
.attlist
-
attribute
groups
use
the
suffix
.attlist
when
they
are
used
to
represent
the
attributes
for
a
specific
element.
-
.attrib
-
attribute
groups
use
the
suffix
.attrib
when
they
are
used
to
represent
a
group
of
tokens
representing
one
or
more
complete
attribute
specifications
within
an
.attlist
declaration.
For
example,
in
HTML
4,
the
%block;
parameter
entity
is
defined
to
represent
the
heterogeneous
collection
of
element
types
that
are
block-level
elements.
In
this
specification,
the
corollary
named
content
model
is
xhtml.Block.mix
.
When
defining
named
content
models
in
the
classes
defined
here,
modules
should
scope
the
names
of
the
model
group
definitions
and
attribute
groups
by
using
unique
prefixes
(this
recommendation
uses
the
prefix
xhtml.
).
For
example,
the
content
model
for
the
element
myelement
in
the
module
mymodule
could
be
named
mymodule.myelement.content
.
Other
schemes
are
possible.
Regardless
of
the
scheme
used,
module
authors
should
strive
to
ensure
that
named
content
model
they
define
are
named
uniquely
so
that
they
do
not
collide
with
other
named
content
model
and
so
that
the
interface
methods
for
the
module
are
obvious
to
its
users.
XHTML
requires
that
the
elements
and
attributes
declared
in
a
module
be
within
a
defined
XML
namespace
[XMLNAMES]
.
The
identification
of
this
namespace
is
an
arbitrary
URI.
XHTML
does
not
require
that
a
module
declare
its
target
namespace
using
the
targetnamespace
attribute.
XHTML
Modularization
using
XML
Schema
has
adopted
a
"late
binding"
approach
to
associating
with
a
namespace.
This
permits
the
development
of
so-called
"chameleon"
modules,
where
the
elements
and
attributes
of
a
module
can
be
incorporated
into
more
than
one
namespace.
While
XML
Schema
allows
an
the
definition
of
global
and
local
element
declarations,
to
be
compatible
with
DTD
definitions
of
XHTML
Modularization
module
implementations
must
not
declare
local
elements.
While
the
approach
defined
here
permits
the
definition
of
global
as
well
as
local
attribute
declarations,
schema
authors
should
consider
the
consequences
of
such
definitions
on
an
document
instance.
Global
attributes
must
always
be
explicitly
prefixed
in
a
instance
document
by
declaring
a
namespace
prefix
xmlns:prefix
,
while
local
attributes
depending
on
the
schema
implementation
may
be
explicitly
prefixed.
An
XML
Schema
provides
definitions
that
belong
to
a
given
target
namespace.
A
schema
must
use
the
import
element
to
include
components
from
an
XML
Schema
that
uses
a
different
target
namespace.
The
import
element
in
XML
Schema
requires
a
namespace
attribute
and
a
optional
schemaLocation
attribute.
Multiple
modules
(included
in
a
document
type)
importing
components
from
the
same
external
namespace
but
providing
different
schema
location
URI
values
will
result
in
invalid
driver
schema.
To
avoid
such
issues
modularization
requires
that
modules
importing
external
schemas
must
not
provide
a
schemaLocation
attribute
so
that
a
document
type's
driver
file
may
import
these
schemas
with
the
schemaLocation
attribute.
While
the
elements
and
attributes
of
a
module
should
NOT
be
in
a
namespace
until
they
are
used
by
a
markup
language,
the
datatypes
that
a
module
relies
upon
may
need
to
be.
This
is
especially
important
if
the
datatypes
are
to
be
shared
with
other
markup
languages.
If
your
module
has
datatypes
that
you
want
to
share
with
other
modules,
you
should
define
a
namespace
for
those
datatypes,
place
the
datatype
definitions
in
a
separate
"module"
and
bind
that
module
to
the
namespace.
In
XHTML
Modularization,
for
example,
we
use
the
namespace
http://www.w3.org/1999/xhtml/datatypes/
.
Quite
often
modules
change
the
content
model
of
elements
defined
by
other
modules.
For
example,
the
XHTML
Events
module
adds
event
attributes
to
elements
defined
by
the
forms
module.
It
is
also
possible
that
multiple
modules
may
change
the
content
model
of
a
single
element
defined
by
a
third
module,
for
example
both
XHTML
Events
Module
and
XHTML
Image
Map
module
add
attributes
to
elements
in
form
module.
XML
Schemas
allows
for
changes
to
a
declared
content
model
using
the
redefine
element.
While
XML
Schema
supports
the
use
of
a
redefine
element
that
redefines
the
named
content
model
and
type
definition,
XML
Schema
does
not
directly
support
redefinition
of
an
element
or
attribute
declaration.
To
support
element
content
model
redefinitions,
all
content
models
are
defined
with
a
.content
identifier.
This
identifier
can
be
easily
redefined
when
creating
a
driver
module.
B.
Developing
Schema
with
defined
and
extended
modules
This
appendix
is
informative
.
The
primary
purpose
of
defining
XHTML
modules
and
a
general
modularization
methodology
is
to
ease
the
development
of
document
types
that
are
based
upon
XHTML
using
XML
Schemas.
These
document
types
may
extend
XHTML
by
integrating
additional
capabilities
(e.g.,
[SMIL]
),
or
they
may
define
a
subset
of
XHTML
for
use
in
a
specialized
device.
This
section
describes
the
techniques
that
document
type
designers
must
use
in
order
to
take
advantage
of
the
XML
Schema
implementation
of
this
modularization
architecture.
It
does
this
by
applying
the
XHTML
Modularization
techniques
in
progressively
more
complex
ways,
culminating
in
the
creation
of
a
complete
document
type
from
disparate
modules.
Note
that
in
no
case
do
these
examples
require
the
modification
of
the
XHTML-provided
module
file
entities
themselves.
The
XHTML
module
file
entities
are
completely
parameterized,
so
that
it
is
possible
through
separate
module
definitions
and
driver
files
to
customize
the
definition
and
the
content
model
of
each
element
and
each
element's
hierarchy.
Finally,
remember
that
most
users
of
XHTML
are
not
expected
to
be
XML
Schema
authors.
XML
Schema
authors
are
generally
people
who
are
defining
specialized
markup
that
will
improve
the
readability,
simplify
the
rendering
of
a
document,
or
ease
machine-processing
of
documents,
or
they
are
client
designers
that
need
to
define
the
specialized
markup
language
for
their
specific
client.
Consider
these
cases:
-
An
organization
is
providing
subscriber's
information
via
a
Web
interface.
The
organization
stores
its
subscriber
information
in
an
XML-based
database.
One
way
to
report
that
information
out
from
the
database
to
the
Web
is
to
embed
the
XML
records
from
the
database
directly
in
the
XHTML
document.
While
it
is
possible
to
merely
embed
the
records,
the
organization
could
define
a
module
that
describes
the
records,
attach
that
module
to
an
XHTML
implementation,
and
thereby
create
a
complete
markup
language
for
the
pages.
The
organization
can
then
access
the
data
within
the
new
elements
via
the
Document
Object
Model
[DOM]
,
validate
the
documents,
provide
style
definitions
for
the
elements
that
cascade
using
Cascading
Style
Sheets
[CSS2]
,
etc.
By
taking
the
time
to
define
the
structure
of
their
data
and
create
a
markup
language
using
the
processes
defined
in
this
section,
the
organization
can
realize
the
full
benefits
of
XML.
-
An
Internet
client
developer
is
designing
a
specialized
device.
That
device
will
only
support
a
subset
of
XHTML,
and
the
devices
will
always
access
the
Internet
via
a
proxy
server
that
validates
content
before
passing
it
on
to
the
client
(to
minimize
error
handling
on
the
client).
In
order
to
ensure
that
the
content
is
valid,
the
developer
creates
a
markup
language
that
is
a
subset
of
XHTML
using
the
processes
defined
in
this
section.
They
then
use
the
new
language
definition
in
their
proxy
server
and
in
their
devices,
and
also
make
the
language
definition
available
to
content
developers
so
that
developers
can
validate
their
content
before
making
it
available.
By
performing
a
few
simple
steps,
the
client
developer
can
use
the
architecture
defined
in
this
document
to
greatly
ease
their
language
development
cost
and
ensure
that
they
are
fully
supporting
the
subset
of
XHTML
that
they
choose
to
include.
In
some
cases,
an
extension
to
XHTML
can
be
as
simple
as
additional
attributes.
Schema
authors
should
an
provide
the
attribute
definitions
for
each
attribute,
for
example:
<xs:attributeGroup name="myattrs.attrib">
<xs:attribute name="myattribute" type="xs:string"/>
</xs:attributeGroup>
would
declare
an
attribute
"myattr"
and
attribute
group
"myattrs.attrib"
in
the
target
namespace
of
the
schema
("xs"
is
the
prefix
for
XML
Schema
Namespace).
Authors
should
note
that
the
attribute
is
created
as
local
attribute
(as
part
attribute
group).
Alternatively,
declaring
an
attribute
by
placing
the
attribute
declaration
as
direct
child
of
schema
element
would
create
a
Global
attribute
(and
document
instances
would
have
to
use
qualified
attribute
name
such
as
xlink:show).
For
a
discussion
of
qualified
names
and
Namespace
prefixes,
see
Defining
the
Namespace
of
a
Module
.
To
add
this
attribute
to
the
content
model
of
an
element,
the
attribute
group
(that
makes
the
content
model
of
the
element)
would
need
to
be
redefined
(by
the
document
type's
driver
file)
to
include
the
new
attribute.
for
example:
<xs:redefine schemaLocation="xhtml-basic10.xsd">
<xs:attributeGroup name="a.attlist">
<xs:attributeGroup ref="a.attlist"/>
<xs:attributeGroup ref="myml:myattrs.attrib"/>
</xs:attributeGroup>
</xs:redefine>
The
target
namespace
of
the
attribute
group
definition
is
not
XHTML
namespace
and
must
be
contained
in
a
separate
XML
schema.
Naturally,
adding
an
attribute
to
a
schema
does
not
mean
that
any
new
behavior
is
defined
for
arbitrary
clients.
However,
a
content
developer
could
use
an
extra
attribute
to
store
information
that
is
accessed
by
associated
scripts
via
the
Document
Object
Model
(for
example).
Defining
additional
elements
is
similar
to
attributes,
but
a
typical
XHTML
module
would
define
the
element
as
a
global
element
(as
a
direct
child
of
schema
element).
Schema
authors
should
first
provide
the
element
declaration
for
each
element:
<!-- In the myml-module-1.xsd -->
<xs:group name="myelement.content">
<xs:choice>
<xs:element name="otherelement"/>
</xs:choice>
</xs:group>
<xs:attributeGroup name="myelement.attlist">
<xs:attribute name="myattribute" type="xs:string"/>
</xs:attributeGroup>
<xs:complexType name="myelement.type" mixed="true">
<xs:choice>
<xs:group ref="myelement.content" minOccurs="0" maxOccurs="1"/>
</xs:choice>
<xs:attributeGroup ref="myelement.attlist"/>
</xs:complexType>
<xs:element name="myelement" type="myelement.type"/>
The
target
namespace
of
"myelement"
declared
is
not
XHTML
namespace,
hence
must
be
contained
in
a
separate
XML
Schema.
"xs"
is
the
prefix
for
XML
Schema
Namespace.
After
the
elements
are
defined,
they
need
to
be
integrated
into
the
content
model.
Strategies
for
integrating
new
elements
or
sets
of
elements
into
the
content
model
are
addressed
in
the
next
section.
Since
the
content
model
of
XHTML
modules
is
fully
parameterized
using
named
content
models,
Schema
authors
may
modify
the
content
model
for
every
element
in
every
module.
The
details
of
the
schema
module
interface
are
defined
in
Building
Schema
Modules
.
Basically
there
are
two
ways
to
approach
this
modification:
-
Re-define
the
named
content
model,
.content
,
for
each
element.
-
Define
one
or
more
of
the
global
named
content
model
entities
to
include
the
element
in
those
named
model
definitions
(normally
via
the
named
content
model,
.extras
).
The
strategy
taken
will
depend
upon
the
nature
of
the
modules
being
combined
and
the
nature
of
the
elements
being
integrated.
The
remainder
of
this
section
describes
techniques
for
integrating
two
different
classes
of
modules.
When
a
module
(and
remember,
a
module
can
be
a
collection
of
other
modules)
contains
elements
that
only
reference
each
other
in
their
content
model,
it
is
said
to
be
"internally
complete".
As
such,
the
module
can
be
used
on
its
own;
(for
example,
you
could
define
a
schema
that
was
just
that
module,
and
use
one
of
its
elements
as
the
root
element).
Integrating
such
a
module
into
XHTML
is
a
three
step
process:
-
Decide
what
element(s)
can
be
thought
of
as
the
root(s)
of
the
new
module.
-
Decide
where
these
elements
need
to
attach
in
the
XHTML
content
tree.
-
Then,
for
each
attachment
point
in
the
content
tree,
add
the
root
element(s)
to
the
content
definition
for
the
XHTML
elements.
Consider
attaching
the
elements
defined
above
.
In
that
example,
the
element
myelement
is
the
root.
To
attach
this
element
under
the
img
element,
and
only
the
img
element,
of
XHTML,
the
following
redefinition
would
work:
<xs:redefine schemaLocation="xhtml-basic10.xsd">
<xs:group name="img.content">
<xs:choice>
<xs:group ref="img.content"/>
<xs:element ref="myml:myelement"/>
</xs:choice>
</xs:group>
</xs:redefine>
Such
redefinition
must
not
be
included
in
the
module
implementation,
but
instead
provided
as
part
of
the
document
type's
driver
implementation.
A
schema
defined
with
this
content
model
would
allow
a
document
like
the
following
fragment:
<img src="http://examples.com/image" alt="alt-text">
<myml:myelement >This is content of a locally defined element</myml:myelement>
</img>
It
is
important
to
note
that
normally
the
img
element
has
a
content
model
of
EMPTY
.
By
adding
myelement
to
that
content
model,
we
are
really
just
replacing
EMPTY
with
myelement
.
In
the
case
of
other
elements
that
already
have
content
models
defined,
the
addition
of
an
element
would
require
the
restating
of
the
existing
content
model
in
addition
to
myelement
.
Extending
the
example
above,
to
attach
this
module
everywhere
that
the
%Flow.mix
content
model
group
is
permitted,
would
require
something
like
the
following
in
the
schema
that
defines
the
document
model
of
the
document
type:
<xs:redefine schemaLocation="xhtml11.xsd">
<xs:group name="Misc.extra">
<xs:choice>
<xs:group ref="Misc.extra"/>
<xs:element ref="myml:myelement"/>
</xs:choice>
</xs:group>
</xs:redefine>
Since
the
Misc.extra
content
model
class
is
used
in
the
content
model
the
named
model
Misc.class,
and
that
named
model
is
used
throughout
the
XHTML
modules,
the
new
module
would
become
available
throughout
an
extended
XHTML
document
type.
So
far
the
examples
in
this
section
have
described
the
methods
of
extending
XHTML
and
XHTML's
content
model.
Once
this
is
done,
the
next
step
is
to
collect
the
modules
that
comprise
the
Document
Type
into
a
schema
driver
and
schema
file
that
provides
the
content
model
redefinitions
of
included
modules,
incorporating
the
new
definitions
so
that
they
override
and
augment
the
basic
XHTML
definitions
as
appropriate.
Using
the
trivial
example
above,
it
is
possible
to
define
a
new
schema
that
uses
and
extends
the
XHTML
modules
pretty
easily.
First,
define
the
new
elements
and
their
content
model
in
a
module:
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/examples/simpleml-module-1.xsd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/examples/simpleml-module-1.xsd
.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://www.example.com/xmlns/simpleml1"
xmlns="http://www.example.com/xmlns/simpleml1">
<xs:annotation>
<xs:documentation>
This is the XML Schema module for module SimpleML
$Id: simpleml-module-1.xsd,v 1.5 2006/06/12 22:38:55 ahby Exp $
</xs:documentation>
<xs:documentation source="http://www.w3.org/MarkUp/SCHEMA/xhtml-copyright-1.xsd"/>
</xs:annotation>
<xs:attributeGroup name="xhtml.Common.attrib">
<xs:attribute name="id" type="xs:ID"/>
</xs:attributeGroup>
<xs:group name="otherelement.content">
<xs:sequence/>
</xs:group>
<xs:attributeGroup name="otherelement.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
</xs:attributeGroup>
<xs:complexType name="otherelement.type">
<xs:group ref="otherelement.content"/>
<xs:attributeGroup ref="otherelement.attlist"/>
</xs:complexType>
<xs:element name="otherelement" type="otherelement.type"/>
<xs:group name="element.content">
<xs:choice>
<xs:element ref="otherelement" minOccurs="0" maxOccurs="unbounded"/>
</xs:choice>
</xs:group>
<xs:attributeGroup name="element.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
</xs:attributeGroup>
<xs:complexType name="element.type" mixed="true">
<xs:group ref="element.content"/>
<xs:attributeGroup ref="element.attlist"/>
</xs:complexType>
<xs:element name="element" type="element.type"/>
<!-- Note: Global attribute -->
<xs:attribute name="myattr" type="xs:string"/>
</xs:schema>
Now,
define
the
schema
driver
for
the
new
language:
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/examples/simpleml-1_0.xsd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/examples/simpleml-1_0.xsd
.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://www.w3.org/1999/xhtml"
xmlns:simpleml="http://www.example.com/xmlns/simpleml1"
xmlns="http://www.w3.org/1999/xhtml"
blockDefault="#all">
<xs:annotation>
<xs:documentation>
This is the XML Schema Driver for new
Document Type XHTML Basic 1.0 + SimpleML
$Id: simpleml-1_0.xsd,v 1.5 2006/06/12 22:38:55 ahby Exp $
</xs:documentation>
<xs:documentation source="http://www.w3.org/MarkUp/SCHEMA/xhtml-copyright-1.xsd"/>
</xs:annotation>
<xs:import namespace="http://www.example.com/xmlns/simpleml1"
schemaLocation="simpleml-module-1.xsd"/>
<xs:redefine schemaLocation="http://www.w3.org/MarkUp/SCHEMA/xhtml-basic10.xsd">
<xs:group name="xhtml.Misc.class">
<xs:choice>
<xs:group ref="xhtml.Misc.class"/>
<xs:element ref="simpleml:element"/>
</xs:choice>
</xs:group>
<xs:attributeGroup name="xhtml.img.attlist">
<xs:attributeGroup ref="xhtml.img.attlist"/>
<xs:attribute ref="simpleml:myattr"/>
</xs:attributeGroup>
</xs:redefine>
</xs:schema>
A
schema
defined
with
this
content
model
would
allow
a
document
like
the
following:
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/examples/simple-prefixed.html
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/examples/simple-prefixed.html
.
<?xml version="1.0" encoding="UTF-8"?>
<html xmlns="http://www.w3.org/1999/xhtml"
xmlns:simpleml="http://www.example.com/xmlns/simpleml1"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.w3.org/1999/xhtml simpleml-1_0.xsd">
<head>
<title>An example using defaults</title>
</head>
<body>
<p>This is content in the XHTML namespace</p>
<simpleml:element>
This is content in the SimpleML namespace.
<simpleml:otherelement/>
</simpleml:element>
<p>
<img src="missing" alt="Missing image" simpleml:myattr="value"/>
</p>
</body>
</html>
Next,
there
is
the
situation
where
a
complete,
additional,
and
complex
module
is
added
to
XHTML
(or
to
a
subset
of
XHTML).
In
essence,
this
is
the
same
as
in
the
example
above,
the
only
difference
being
that
the
module
being
added
is
incorporated
in
the
schema
by
creating
an
new
document
model
schema.
One
such
complex
module
is
the
Schema
for
[MATHML]
.
In
order
to
combine
MathML
and
XHTML
into
a
single
Schema,
an
author
would
just
decide
where
MathML
content
should
be
legal
in
the
document,
and
add
the
MathML
root
element
to
the
content
model
at
that
point.
First,
define
a
new
document
model
that
instantiates
the
MathML
Schema
and
connects
it
to
the
content
XHTML
content
model
by
redefining
the
XHTML
content
model.
Providing
a
redefinition
of
the
XHTML
content
model
by
implication
includes
the
XHTML
content
model
in
the
new
document
content
model
:
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/examples/mathml-model-1.xsd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/examples/mathml-model-1.xsd
.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema targetNamespace="http://www.w3.org/1999/xhtml"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns="http://www.w3.org/1999/xhtml"
xmlns:math="http://www.w3.org/1998/Math/MathML">
<xs:import namespace="http://www.w3.org/1998/Math/MathML"/>
<xs:redefine schemaLocation="http://www.w3.org/MarkUp/SCHEMA/xhtml11-model-1.xsd">
<xs:group name="xhtml.InlSpecial.class">
<xs:choice>
<xs:group ref="xhtml.InlSpecial.class"/>
<xs:element ref="math:math"/>
</xs:choice>
</xs:group>
</xs:redefine>
</xs:schema>
Next,
define
a
Schema
driver
that
includes
our
new
document
content
model
with
XHTML1.1
modules
and
MathML
module
(for
example):
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/examples/xhtml-mathml.xsd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/examples/xhtml-mathml.xsd
.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://www.w3.org/1999/xhtml"
xmlns:simpleml="http://www.example.com/xmlns/simpleml1"
xmlns="http://www.w3.org/1999/xhtml"
blockDefault="#all">
<xs:import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2001/xml.xsd"/>
<xs:import namespace="http://www.w3.org/1998/Math/MathML"
schemaLocation="http://www.w3.org/Math/XMLSchema/mathml2/mathml2.xsd"/>
<xs:include schemaLocation="http://www.w3.org/MarkUp/SCHEMA/xhtml11-modules-1.xsd"/>
<xs:include schemaLocation="mathml-model-1.xsd"/>
</xs:schema>
Another
way
in
which
Schema
authors
may
use
XHTML
modules
is
to
define
a
Schema
that
is
a
subset
of
an
XHTML
family
document
type
(because,
for
example,
they
are
building
devices
or
software
that
only
supports
a
subset
of
XHTML).
To
do
this
simple
create
a
Schema
driver
that
does
not
include
the
relevant
modules.
Schema
author
should
note
that
redefine
in
schema
by
default
includes
all
the
content
model
of
the
referenced
schema,
authors
should
also
not
include
any
redefinitions
of
modules
that
they
do
not
wish
to
include.
The
basic
steps
to
follow
are:
-
Take
an
XHTML
family
Schema
as
the
basis
of
the
new
document
type
(e.g.
XHTML
1.1).
-
Select
the
modules
to
remove
from
that
Schema.
-
Physically,
remove
include
and
redefine
schema
elements
that
include
any
non
relevant
modules
from
the
driver
file.
Also
references
to
schema
components
from
such
modules
used
in
redefinitions
of
other
modules
must
be
deleted.
-
Introduce
some
new
modules
Finally,
some
Schema
authors
may
wish
to
start
from
scratch,
using
the
XHTML
Modularization
framework
as
a
toolkit
for
building
a
new
markup
language.
This
language
must
be
made
up
of
the
minimal,
required
modules
from
XHTML.
It
may
also
contain
other
XHTML-defined
modules
or
any
other
module
that
the
author
wishes
to
employ.
In
this
example,
we
will
take
the
XHTML
required
modules,
add
some
XHTML-defined
modules,
and
also
add
in
the
module
we
defined
above.
The
first
step
is
to
define
a
module
that
defines
the
elements
and
attributes
using
the
provided
template
.
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/examples/myml-module-1.xsd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/examples/myml-module-1.xsd
.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://www.example.com/xmlns/myml"
xmlns:xhtml="http://www.w3.org/1999/xhtml"
xmlns="http://www.example.com/xmlns/myml">
<xs:annotation>
<xs:documentation>
This is XML Schema template for MLML module
$Id: myml-module-1.xsd,v 1.4 2005/10/20 14:14:40 ahby Exp $
</xs:documentation>
<xs:documentation source="http://www.w3.org/MarkUp/SCHEMA/xhtml-copyright-1.xsd"/>
</xs:annotation>
<xs:annotation>
<xs:documentation>
My Elements Module
+ myelement
+ myotherelement
This module has no purpose other than to provide structure for some
PCDATA content.
</xs:documentation>
</xs:annotation>
<xs:import namespace="http://www.w3.org/1999/xhtml"/>
<xs:attributeGroup name="myml.myotherelement.attlist">
<xs:attributeGroup ref="xhtml:xhtml.Global.common.attrib"/>
</xs:attributeGroup>
<xs:group name="myml.myotherelement.content">
<xs:sequence/>
</xs:group>
<xs:complexType name="myml.myotherelement.type">
<xs:group ref="myml.myotherelement.content"/>
<xs:attributeGroup ref="myml.myotherelement.attlist"/>
</xs:complexType>
<xs:element name="myotherelement" type="myml.myotherelement.type"/>
<xs:group name="myml.myelement.content">
<xs:choice>
<xs:element ref="myotherelement"/>
</xs:choice>
</xs:group>
<xs:attributeGroup name="myelement.attlist">
<xs:attribute name="myattribute" type="xs:string"/>
<xs:attributeGroup ref="xhtml:Global.common.attrib"/>
</xs:attributeGroup>
<xs:complexType name="myml.myelement.type" mixed="true">
<xs:choice>
<xs:group ref="myml.myelement.content" minOccurs="0" maxOccurs="1"/>
</xs:choice>
<xs:attributeGroup ref="myml.myelement.attlist"/>
</xs:complexType>
<xs:element name="myelement" type="myml.myelement.type"/>
<!-- Note: Global attribute -->
<xs:attribute name="myattr" type="xs:string"/>
</xs:schema>
Now,
build
a
content
model
description
that
hooks
the
new
elements
and
attributes
into
the
other
XHTML
elements.
The
following
example
is
patterned
after
the
XHTML
Basic
content
model,
but
is
a
complete,
free-standing
content
model
module:
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/examples/myml-model-1.xsd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/examples/myml-model-1.xsd
.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://www.w3.org/1999/xhtml"
xmlns="http://www.w3.org/1999/xhtml"
xmlns:myml="http://www.example.com/xmlns/myml">
<xs:annotation>
<xs:documentation>
This is the XML Schema module of common content models for MyML
$Id: myml-model-1.xsd,v 1.6 2005/10/20 14:14:40 ahby Exp $
</xs:documentation>
<xs:documentation source="http://www.w3.org/MarkUp/SCHEMA/xhtml-copyright-1.xsd"/>
</xs:annotation>
<xs:annotation>
<xs:documentation>
XHTML + MyML Document Model
This module describes the groupings of elements/attributes that make up
common content models for XHTML elements.
XHTML has following basic content models:
Inline.mix; character-level elements
Block.mix; block-like elements, eg., paragraphs and lists
Flow.mix; any block or inline elements
HeadOpts.mix; Head Elements
InlinePre.mix; Special class for pre content model
InlineNoAnchor.mix; Content model for Anchor
Any groups declared in this module may be used
to create element content models, but the above are
considered 'global' (insofar as that term applies here).
XHTML has the following Attribute Groups
Core.extra.attrib
I18n.extra.attrib
Common.extra
The above attribute Groups are considered Global
</xs:documentation>
</xs:annotation>
<xs:import namespace="http://www.example.com/xmlns/myml"/>
<xs:attributeGroup name="xhtml.I18n.extra.attrib">
<xs:annotation>
<xs:documentation>
Extended I18n attribute
</xs:documentation>
</xs:annotation>
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.Core.extra.attrib">
<xs:annotation>
<xs:documentation>
Extended Core Attributes
</xs:documentation>
</xs:annotation>
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.Common.extra">
<xs:annotation>
<xs:documentation>
Extended Common Attributes
</xs:documentation>
</xs:annotation>
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.Global.core.extra.attrib">
<xs:annotation>
<xs:documentation>
Extended Global Core Attributes
</xs:documentation>
</xs:annotation>
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.Global.I18n.extra.attrib">
<xs:annotation>
<xs:documentation>
Extended Global I18n attributes
</xs:documentation>
</xs:annotation>
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.Global.Common.extra">
<xs:annotation>
<xs:documentation>
Extended Global Common Attributes
</xs:documentation>
</xs:annotation>
</xs:attributeGroup>
<xs:group name="xhtml.HeadOpts.mix">
<xs:choice>
<xs:element ref="meta"/>
<xs:element ref="link"/>
<xs:element ref="object"/>
</xs:choice>
</xs:group>
<!--
These elements are neither block nor inline, and can
essentially be used anywhere in the document body.
-->
<xs:group name="xhtml.Misc.class">
<xs:choice>
<xs:element ref="myml:myelement"/>
</xs:choice>
</xs:group>
<!-- Inline Elements -->
<xs:group name="xhtml.InlStruct.class">
<xs:choice>
<xs:element ref="br"/>
<xs:element ref="span"/>
</xs:choice>
</xs:group>
<xs:group name="xhtml.InlPhras.class">
<xs:choice>
<xs:element ref="em"/>
<xs:element ref="strong"/>
<xs:element ref="dfn"/>
<xs:element ref="code"/>
<xs:element ref="samp"/>
<xs:element ref="kbd"/>
<xs:element ref="var"/>
<xs:element ref="cite"/>
<xs:element ref="abbr"/>
<xs:element ref="acronym"/>
<xs:element ref="q"/>
</xs:choice>
</xs:group>
<xs:group name="xhtml.InlPres.class">
<xs:choice/>
</xs:group>
<xs:group name="xhtml.I18n.class">
<xs:sequence/>
</xs:group>
<xs:group name="xhtml.Anchor.class">
<xs:sequence>
<xs:element ref="a"/>
</xs:sequence>
</xs:group>
<xs:group name="xhtml.InlSpecial.class">
<xs:choice>
<xs:element ref="img"/>
<xs:element ref="object"/>
</xs:choice>
</xs:group>
<xs:group name="xhtml.InlForm.class">
<xs:choice>
<xs:element ref="input"/>
<xs:element ref="select"/>
<xs:element ref="textarea"/>
<xs:element ref="label"/>
</xs:choice>
</xs:group>
<xs:group name="xhtml.Inline.extra">
<xs:choice/>
</xs:group>
<!--xs:group name="Ruby.class">
<xs:sequence/>
</xs:group-->
<!--
Inline.class includes all inline elements,
used as a component in mixes
-->
<xs:group name="xhtml.Inline.class">
<xs:choice>
<xs:group ref="xhtml.InlStruct.class"/>
<xs:group ref="xhtml.InlPhras.class"/>
<xs:group ref="xhtml.Anchor.class"/>
<xs:group ref="xhtml.InlSpecial.class"/>
<xs:group ref="xhtml.InlForm.class"/>
<xs:group ref="xhtml.Inline.extra"/>
</xs:choice>
</xs:group>
<!--
InlinePre.class
Used as a component in pre model
-->
<xs:group name="xhtml.InlinePre.mix">
<xs:choice>
<xs:group ref="xhtml.InlStruct.class"/>
<xs:group ref="xhtml.InlPhras.class"/>
<xs:group ref="xhtml.Anchor.class"/>
<xs:group ref="xhtml.Inline.extra"/>
</xs:choice>
</xs:group>
<!--
InlNoAnchor.class includes all non-anchor inlines,
used as a component in mixes
-->
<xs:group name="xhtml.InlNoAnchor.class">
<xs:choice>
<xs:group ref="xhtml.InlStruct.class"/>
<xs:group ref="xhtml.InlPhras.class"/>
<xs:group ref="xhtml.InlSpecial.class"/>
<xs:group ref="xhtml.InlForm.class"/>
<xs:group ref="xhtml.Inline.extra"/>
</xs:choice>
</xs:group>
<!--
InlNoAnchor.mix includes all non-anchor inlines
-->
<xs:group name="xhtml.InlNoAnchor.mix">
<xs:choice>
<xs:group ref="xhtml.InlNoAnchor.class"/>
<xs:group ref="xhtml.Misc.class"/>
</xs:choice>
</xs:group>
<!--
Inline.mix includes all inline elements, including Misc.class
-->
<xs:group name="xhtml.Inline.mix">
<xs:choice>
<xs:group ref="xhtml.Inline.class"/>
<xs:group ref="xhtml.Misc.class"/>
</xs:choice>
</xs:group>
<!--
In the HTML 4 DTD, heading and list elements were included
in the block group. The Heading.class and
List.class groups must now be included explicitly
on element declarations where desired.
-->
<xs:group name="xhtml.Heading.class">
<xs:choice>
<xs:element ref="h1"/>
<xs:element ref="h2"/>
<xs:element ref="h3"/>
<xs:element ref="h4"/>
<xs:element ref="h5"/>
<xs:element ref="h6"/>
</xs:choice>
</xs:group>
<xs:group name="xhtml.List.class">
<xs:choice>
<xs:element ref="ul"/>
<xs:element ref="ol"/>
<xs:element ref="dl"/>
</xs:choice>
</xs:group>
<xs:group name="xhtml.Table.class">
<xs:choice>
<xs:element ref="table"/>
</xs:choice>
</xs:group>
<xs:group name="xhtml.Form.class">
<xs:choice>
<xs:element ref="form"/>
</xs:choice>
</xs:group>
<xs:group name="xhtml.BlkStruct.class">
<xs:choice>
<xs:element ref="p"/>
<xs:element ref="div"/>
</xs:choice>
</xs:group>
<xs:group name="xhtml.BlkPhras.class">
<xs:choice>
<xs:element ref="pre"/>
<xs:element ref="blockquote"/>
<xs:element ref="address"/>
</xs:choice>
</xs:group>
<xs:group name="xhtml.BlkPres.class">
<xs:choice/>
</xs:group>
<xs:group name="xhtml.BlkSpecial.class">
<xs:choice>
<xs:group ref="xhtml.Table.class"/>
<xs:group ref="xhtml.Form.class"/>
</xs:choice>
</xs:group>
<xs:group name="xhtml.Block.extra">
<xs:choice/>
</xs:group>
<!--
Block.class includes all block elements,
used as an component in mixes
-->
<xs:group name="xhtml.Block.class">
<xs:choice>
<xs:group ref="xhtml.BlkStruct.class"/>
<xs:group ref="xhtml.BlkPhras.class"/>
<xs:group ref="xhtml.BlkSpecial.class"/>
<xs:group ref="xhtml.Block.extra"/>
</xs:choice>
</xs:group>
<!--
Block.mix includes all block elements plus %Misc.class;
-->
<xs:group name="xhtml.Block.mix">
<xs:choice>
<xs:group ref="xhtml.Heading.class"/>
<xs:group ref="xhtml.List.class"/>
<xs:group ref="xhtml.Block.class"/>
<xs:group ref="xhtml.Misc.class"/>
</xs:choice>
</xs:group>
<!--
All Content Elements
Flow.mix includes all text content, block and inline
Note that the "any" element included here allows us
to add data from any other namespace, a necessity
for compound document creation.
Note however that it is not possible to add
to any head level element without further
modification. To add RDF metadata to the head
of a document, modify the structure module.
-->
<xs:group name="xhtml.Flow.mix">
<xs:choice>
<xs:group ref="xhtml.Heading.class"/>
<xs:group ref="xhtml.List.class"/>
<xs:group ref="xhtml.Block.class"/>
<xs:group ref="xhtml.Inline.class"/>
<xs:group ref="xhtml.Misc.class"/>
</xs:choice>
</xs:group>
<xs:group name="xhtml.FlowNoTable.mix">
<xs:choice>
<xs:group ref="xhtml.Heading.class"/>
<xs:group ref="xhtml.List.class"/>
<xs:group ref="xhtml.BlkStruct.class"/>
<xs:group ref="xhtml.BlkPhras.class"/>
<xs:group ref="xhtml.Form.class"/>
<xs:group ref="xhtml.Inline.class"/>
<xs:group ref="xhtml.Misc.class"/>
</xs:choice>
</xs:group>
<!--
BlkNoForm.mix includes all non-form block elements,
plus Misc.class
-->
<xs:group name="xhtml.BlkNoForm.mix">
<xs:choice>
<xs:group ref="xhtml.Heading.class"/>
<xs:group ref="xhtml.List.class"/>
<xs:group ref="xhtml.BlkStruct.class"/>
<xs:group ref="xhtml.BlkPhras.class"/>
<xs:group ref="xhtml.BlkPres.class"/>
<xs:group ref="xhtml.Table.class"/>
<xs:group ref="xhtml.Misc.class"/>
</xs:choice>
</xs:group>
<xs:element name="html" type="xhtml.html.type"/>
</xs:schema>
Finally,
build
a
driver
schema.
For
ease
of
extensibility
this
driver
schema
is
split
into
two
XML
Schema
files.
The
first
file
of
driver
schema
collects
(includes)
all
the
modules
needed
for
the
new
document
type.
This
schema
also
provides
the
required
redefinitions
of
schema
components
in
included
modules.(Note:
in
XML
Schema
redefine
includes
the
schema
referenced.
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/examples/myml-modules-1.xsd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/examples/myml-modules-1.xsd
.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema targetNamespace="http://www.w3.org/1999/xhtml"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns="http://www.w3.org/1999/xhtml"
xmlns:myml="http://www.example.com/xmlns/myml"
blockDefault="#all">
<xs:annotation>
<xs:documentation>
This schema includes all modules for XHTML Basic 1.0 + MyML
Document Type.
$Id: myml-modules-1.xsd,v 1.3 2004/01/15 06:01:40 speruvem Exp $
</xs:documentation>
<xs:documentation source="http://www.w3.org/MarkUp/SCHEMA/xhtml-copyright-1.xsd"/>
</xs:annotation>
<xs:annotation>
<xs:documentation>
This schema includes (with component redefinitions as required) all
modules for XHTML Basic 1.0 + MyML Document Type
This Document Type includes the following Modules
XHTML Core modules (Required for XHTML Family Conformance)
+ text
+ hypertext
+ lists
+ structure
Other XHTML modules
+ Link
+ Meta
+ Base
+ Image
+ Object
+ Param
+ Basic forms
+ Basic tables
Other Modules
+ MyML Module
</xs:documentation>
</xs:annotation>
<xs:include schemaLocation="http://www.w3.org/MarkUp/SCHEMA/xhtml-framework-1.xsd">
<xs:annotation>
<xs:documentation>
Schema Framework Component Modules:
+ notations
+ datatypes
+ common attributes
+ character entities
</xs:documentation>
<xs:documentation
source="http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_commonatts"/>
</xs:annotation>
</xs:include>
<xs:include schemaLocation="http://www.w3.org/MarkUp/SCHEMA/xhtml-text-1.xsd">
<xs:annotation>
<xs:documentation>
Text module
The Text module includes declarations for all core
text container elements and their attributes.
+ block phrasal
+ block structural
+ inline phrasal
+ inline structural
Elements defined here:
* address, blockquote, pre, h1, h2, h3, h4, h5, h6
* div, p
* abbr, acronym, cite, code, dfn, em, kbd, q, samp, strong, var
* br, span
</xs:documentation>
<xs:documentation
source="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/abstract_modules.html#s_textmodule"/>
</xs:annotation>
</xs:include>
<xs:include schemaLocation="http://www.w3.org/MarkUp/SCHEMA/xhtml-hypertext-1.xsd">
<xs:annotation>
<xs:documentation>
Hypertext module
Elements defined here:
* a
</xs:documentation>
<xs:documentation
source="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/abstract_modules.html#s_hypertextmodule"/>
</xs:annotation>
</xs:include>
<xs:include schemaLocation="http://www.w3.org/MarkUp/SCHEMA/xhtml-list-1.xsd">
<xs:annotation>
<xs:documentation>
Lists module
Elements defined here:
* dt, dd, dl, ol, ul, li
</xs:documentation>
<xs:documentation
source="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/abstract_modules.html#s_listmodule"/>
</xs:annotation>
</xs:include>
<xs:redefine schemaLocation="http://www.w3.org/MarkUp/SCHEMA/xhtml-struct-1.xsd">
<xs:annotation>
<xs:documentation>
Structural module
Elements defined here:
* title, head, body, html
</xs:documentation>
<xs:documentation
source="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/abstract_modules.html#s_structuremodule"/>
</xs:annotation>
<xs:group name="head.content">
<xs:annotation>
<xs:documentation>
Redefinition by Base module
</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:group ref="HeadOpts.mix" minOccurs="0" maxOccurs="unbounded"/>
<xs:choice>
<xs:sequence>
<xs:group ref="head.content"/>
<xs:group ref="HeadOpts.mix" minOccurs="0" maxOccurs="unbounded"/>
<xs:sequence minOccurs="0">
<xs:element ref="base"/>
<xs:group ref="HeadOpts.mix" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:sequence>
<xs:sequence>
<xs:element ref="base"/>
<xs:group ref="HeadOpts.mix" minOccurs="0" maxOccurs="unbounded"/>
<xs:element ref="title"/>
<xs:group ref="HeadOpts.mix" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:choice>
</xs:sequence>
</xs:group>
<xs:attributeGroup name="version.attrib">
<xs:annotation>
<xs:documentation>
Redefinition by the XHTML11 Markup (for value of version attr)
</xs:documentation>
</xs:annotation>
<xs:attribute name="version" type="FPI" fixed="-//W3C//DTD XHTML Basic 1.0 + MyML//EN"/>
</xs:attributeGroup>
</xs:redefine>
<xs:include schemaLocation="http://www.w3.org/MarkUp/SCHEMA/xhtml-link-1.xsd">
<xs:annotation>
<xs:documentation>
Link module
Elements defined here:
* link
</xs:documentation>
<xs:documentation
source="http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_linkmodule"/>
</xs:annotation>
</xs:include>
<xs:include schemaLocation="http://www.w3.org/MarkUp/SCHEMA/xhtml-meta-1.xsd">
<xs:annotation>
<xs:documentation>
Meta module
Elements defined here:
* meta
</xs:documentation>
<xs:documentation
source="http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_metamodule"/>
</xs:annotation>
</xs:include>
<xs:include schemaLocation="http://www.w3.org/MarkUp/SCHEMA/xhtml-base-1.xsd">
<xs:annotation>
<xs:documentation>
Base module
Elements defined here:
* base
</xs:documentation>
<xs:documentation
source="http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_basemodule"/>
</xs:annotation>
</xs:include>
<xs:redefine schemaLocation="http://www.w3.org/MarkUp/SCHEMA/xhtml-image-1.xsd">
<xs:annotation>
<xs:documentation>
Image module
Elements defined here:
* img
</xs:documentation>
<xs:documentation
source="http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_imagemodule"/>
</xs:annotation>
<xs:attributeGroup name="img.attlist">
<xs:attributeGroup ref="img.attlist"/>
<xs:attribute ref="myml:myattr"/>
</xs:attributeGroup>
</xs:redefine>
<xs:include schemaLocation="http://www.w3.org/MarkUp/SCHEMA/xhtml-object-1.xsd">
<xs:annotation>
<xs:documentation>
Object module
Elements defined here:
* object
</xs:documentation>
<xs:documentation
source="http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_objectmodule"/>
</xs:annotation>
</xs:include>
<xs:include schemaLocation="http://www.w3.org/MarkUp/SCHEMA/xhtml-param-1.xsd">
<xs:annotation>
<xs:documentation>
Param module
Elements defined here:
* param
</xs:documentation>
</xs:annotation>
</xs:include>
<xs:include schemaLocation="http://www.w3.org/MarkUp/SCHEMA/xhtml-basic-form-1.xsd">
<xs:annotation>
<xs:documentation>
Basic Forms module
Note that this module is not used in XHTML 1.1. It is designed
for use with XHTML Basic
Elements defined here:
* form, label, input, select, option, textarea
</xs:documentation>
<xs:documentation
source="http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_sformsmodule"/>
</xs:annotation>
</xs:include>
<xs:include schemaLocation="http://www.w3.org/MarkUp/SCHEMA/xhtml-basic-table-1.xsd">
<xs:annotation>
<xs:documentation>
Basic Tables module
Note that this module is not used in XHTML It is designed
for use with XHTML Basic
Elements defined here:
* table, caption, tr, th, td
</xs:documentation>
<xs:documentation
source="http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_simpletablemodule"/>
</xs:annotation>
</xs:include>
<xs:import namespace="http://www.example.com/xmlns/myml"
schemaLocation="myml-module-1.xsd">
<xs:annotation>
<xs:documentation>
MyML Module
Elements defined here:
* myelement, myotherelement
</xs:documentation>
</xs:annotation>
</xs:import>
</xs:schema>
The
second
file
of
the
driver
schema
builds
new
document
type
based
the
content
model
and
modules.
Also
this
schema
provides
the
schemaLocation
for
all
imported
namespaces
(namespaces
imported
by
the
included
modules)
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/examples/myml-1_0.xsd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/examples/myml-1_0.xsd
.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema targetNamespace="http://www.w3.org/1999/xhtml"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns="http://www.w3.org/1999/xhtml"
blockDefault="#all">
<xs:annotation>
<xs:documentation>
This is the XML Schema driver for XHTML Basic 1.0.
Please use this namespace for XHTML elements:
"http://www.w3.org/1999/xhtml"
$Id: myml-1_0.xsd,v 1.5 2005/04/25 18:53:05 ahby Exp $
</xs:documentation>
</xs:annotation>
<xs:annotation>
<xs:documentation>
This is XHTML, a reformulation of HTML as a modular XML application
The Extensible HyperText Markup Language (XHTML)
Copyright ©1998-2004 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 Schema
modules and their accompanying xs: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
these XML Schema modules for any purpose.
They are provided "as is" without expressed or implied warranty.
</xs:documentation>
</xs:annotation>
<xs:annotation>
<xs:documentation>
This is the Schema Driver file for
XHTML Basic 1.0 + MyML Document Type
This schema includes
+ imports external schemas (xml.xsd)
+ refedines (and include)s schema modules for XHTML
Basic 1.0 + MyML Document Type.
+ includes Schema for Named content model for the
XHTML Basic 1.0 + MyML Document Type
This Document Type includes the following Modules
XHTML Core modules (Required for XHTML Family Conformance)
+ text
+ hypertext
+ lists
+ structure
Other XHTML modules
+ Link
+ Meta
+ Base
+ Image
+ Object
+ Param
+ Basic forms
+ Basic tables
Other Modules
+ MyML Module
</xs:documentation>
</xs:annotation>
<xs:import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2001/xml.xsd">
<xs:annotation>
<xs:documentation>
This import brings in the XML namespace attributes
The XML attributes are used by various modules
</xs:documentation>
</xs:annotation>
</xs:import>
<xs:include schemaLocation="myml-model-1.xsd">
<xs:annotation>
<xs:documentation>
Document Model module for the XHTML Basic 1.0 Document Type
This schema file defines all named models used by XHTML
Modularization Framework for XHTML Basic 1.0 Document Type
</xs:documentation>
</xs:annotation>
</xs:include>
<xs:include schemaLocation="myml-modules-1.xsd">
<xs:annotation>
<xs:documentation>
Schema that includes all modules for XHTML Basic 1.0 + MyML
Document Type.
</xs:documentation>
</xs:annotation>
</xs:include>
</xs:schema>
Once
a
new
SCHEMA
has
been
developed,
it
can
be
used
in
any
document.
Using
the
Schema
is
as
simple
as
just
referencing
it
in
the
schemaLocation
attribute
of
a
document
root
element:
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/examples/myml-prefixed.html
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/examples/myml-prefixed.html
.
<?xml version="1.0" encoding="UTF-8"?>
<html xmlns="http://www.w3.org/1999/xhtml"
xmlns:xhtml="http://www.w3.org/1999/xhtml"
xmlns:myml="http://www.example.com/xmlns/myml"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.w3.org/1999/xhtml myml-1_0.xsd">
<head>
<title>An example using defaults</title>
</head>
<body>
<p>This is content in the XHTML namespace</p>
<myml:myelement xhtml:id="myid" xhtml:class="localElement">
This is content in the myml namespace.
<myml:myotherelement/>
</myml:myelement>
<p>
<img src="missing" alt="Missing image" myml:myattr="value"/>
</p>
</body>
</html>
C.
XHTML
Schema
Module
Implementations
This
appendix
is
normative
.
This
appendix
contains
implementations
of
the
modules
defined
in
XHTML
Abstract
Modules
via
XML
Schemas.
These
module
implementations
can
be
used
by
XHTML
Family
Document
Types.
There
are
direct
links
to
the
various
files,
and
the
files
are
also
contained
in
the
"Gzip'd
TAR"
and
"Zip"
archives
linked
to
at
the
top
of
this
document.
Please
note
that
the
files
targeted
by
the
"latest
version"
links
may
change
slowly
over
time.
See
the
W3C
XHTML2
Working
Group
home
page
for
more
information.
XML
Schema
uses
DTDs
to
support
character
entities.
The
DTD
implementation
of
XHTML
Modularization
[XHTMLMOD]
defines
the
required
character
entities
for
XHTML.
The
schema
implementation
includes
the
set
of
character
entities
for
XHTML,
including
the
Latin
1,
Symbol
and
Special
character
collections
defined
as
part
the
DTD
implementation
of
XHTML
Modularization
[XHTMLMOD].
Even
though
the
named
character
entities
are
defined
using
DTDs
and
included
in
the
Schema
Modularization
Framework,
schema
processors
typically
do
not
expand
the
named
character
entities
in
an
XML
document
instance.
The
html
DOCTYPE
declaration
must
still
be
present
if
one
wishes
to
use
named
entities
defined
by
this
Framework
module
The
Framework
modules
instantiates
a
set
of
support
model
that
define
the
common
Datatypes,
Notations,
Common
attribute
definitions
and
character
entities.
These
are
defined
in
a
set
of
support
modules,
instantiated
by
a
main
Framework
module:
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/xhtml-framework-1.xsd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/xhtml-framework-1.xsd
.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:xh11d="http://www.w3.org/1999/xhtml/datatypes/"
elementFormDefault="qualified"
>
<xs:annotation>
<xs:documentation>
This is the XML Schema Modular Framework support module for XHTML
$Id: xhtml-framework-1.xsd,v 1.5 2005/09/26 23:37:47 ahby Exp $
</xs:documentation>
<xs:documentation source="xhtml-copyright-1.xsd"/>
</xs:annotation>
<xs:annotation>
<xs:documentation>
XHTML Modular Framework
This required module instantiates the necessary modules
needed to support the XHTML modularization framework.
The Schema modules instantiated are:
+ notations
+ datatypes
+ common attributes
+ character entities
</xs:documentation>
<xs:documentation source="http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_commonatts"/>
</xs:annotation>
<!-- xs:include schemaLocation="xhtml-notations-1.xsd">
<xs:annotation>
<xs:documentation>
Notations module
Declares XHTML notations for Attribute data types
</xs:documentation>
</xs:annotation>
</xs:include -->
<xs:import namespace="http://www.w3.org/1999/xhtml/datatypes/" schemaLocation="xhtml-datatypes-1.xsd">
<xs:annotation>
<xs:documentation>
This module defines XHTML Attribute DataTypes
</xs:documentation>
<xs:documentation source="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/abstraction.html#s_common_attrtypes"/>
</xs:annotation>
</xs:import>
<xs:include schemaLocation="xhtml-attribs-1.xsd">
<xs:annotation>
<xs:documentation>
This module defines Common attributes for XHTML
</xs:documentation>
<xs:documentation source="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/abstract_modules.html#s_commonatts"/>
</xs:annotation>
</xs:include>
<!-- xs:include schemaLocation="xhtml-charent-1.xsd">
<xs:annotation>
<xs:documentation>
Character entities module
Note: Entities are not supported in XML Schema
The Schema Module uses DTDs to define Entities
This module defines
+ XHTML Latin 1 Character Entities
+ XHTML Special Characters
+ XHTML Mathematical, Greek, and Symbolic Characters
</xs:documentation>
</xs:annotation>
</xs:include -->
</xs:schema>
The
Modular
Schema
framework
also
relies
upon
the
following
component
modules:
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/xhtml-notations-1.xsd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/xhtml-notations-1.xsd
.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
xmlns:xh11d="http://www.w3.org/1999/xhtml/datatypes/"
>
<xs:import namespace="http://www.w3.org/1999/xhtml/datatypes/"
schemaLocation="xhtml-datatypes-1.xsd" />
<xs:annotation>
<xs:documentation>
Notations module
This is the XML Schema module for data type notations for XHTML
$Id: xhtml-notations-1.xsd,v 1.5 2005/09/26 22:54:53 ahby Exp $
</xs:documentation>
<xs:documentation source="xhtml-copyright-1.xsd"/>
</xs:annotation>
<xs:annotation>
<xs:documentation>
Notations module
Defines the XHTML notations, many of these imported from
other specifications and standards. When an existing FPI is
known, it is incorporated here.
</xs:documentation>
<xs:documentation source="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/abstraction.html#s_common_attrtypes"/>
</xs:annotation>
<!-- W3C XML 1.0 Recommendation -->
<xs:notation name="w3c-xml" public="ISO 8879//NOTATION Extensible Markup Language (XML) 1.0//EN"/>
<!-- XML 1.0 CDATA -->
<xs:notation name="cdata" public="-//W3C//NOTATION XML 1.0: CDATA//EN"/>
<!-- SGML Formal Public Identifiers -->
<xs:notation name="fpi" public="ISO 8879:1986//NOTATION Formal Public Identifier//EN"/>
<!-- XHTML Notations ... -->
<!-- Length defined for cellpadding/cellspacing -->
<!-- nn for pixels or nn% for percentage length -->
<!-- a single character, as per section 2.2 of [XML] -->
<xs:notation name="character" public="-//W3C//NOTATION XHTML Datatype: Character//EN"/>
<!-- a character encoding, as per [RFC2045] -->
<xs:notation name="charset" public="-//W3C//NOTATION XHTML Datatype: Charset//EN"/>
<!-- a space separated list of character encodings, as per [RFC2045] -->
<xs:notation name="charsets" public="-//W3C//NOTATION XHTML Datatype: Charsets//EN"/>
<!-- media type, as per [RFC2045] -->
<xs:notation name="contentType" public="-//W3C//NOTATION XHTML Datatype: ContentType//EN"/>
<!-- comma-separated list of media types, as per [RFC2045] -->
<xs:notation name="contentTypes" public="-//W3C//NOTATION XHTML Datatype: ContentTypes//EN"/>
<!-- date and time information. ISO date format -->
<xs:notation name="datetime" public="-//W3C//NOTATION XHTML Datatype: Datetime//EN"/>
<!-- a language code, as per [RFC3066] -->
<xs:notation name="languageCode" public="-//W3C//NOTATION XHTML Datatype: LanguageCode//EN"/>
<!-- nn for pixels or nn% for percentage length -->
<xs:notation name="length" public="-//W3C//NOTATION XHTML Datatype: Length//EN"/>
<!-- space-separated list of link types -->
<xs:notation name="linkTypes" public="-//W3C//NOTATION XHTML Datatype: LinkTypes//EN"/>
<!-- single or comma-separated list of media descriptors -->
<xs:notation name="mediaDesc" public="-//W3C//NOTATION XHTML Datatype: MediaDesc//EN"/>
<!-- pixel, percentage, or relative -->
<xs:notation name="multiLength" public="-//W3C//NOTATION XHTML Datatype: MultiLength//EN"/>
<!-- one or more digits (NUMBER) -->
<xs:notation name="number" public="-//W3C//NOTATION XHTML Datatype: Number//EN"/>
<!-- one or more digits (NUMBER) -->
<xs:notation name="pixels" public="-//W3C//NOTATION XHTML Datatype: Pixels//EN"/>
<!-- script expression -->
<xs:notation name="script" public="-//W3C//NOTATION XHTML Datatype: Script//EN"/>
<!-- textual content -->
<xs:notation name="text" public="-//W3C//NOTATION XHTML Datatype: Text//EN"/>
<!-- a Uniform Resource Identifier, see [URI] -->
<xs:notation name="uri" public="-//W3C//NOTATION XHTML Datatype: URI//EN"/>
<!-- a space-separated list of Uniform Resource Identifiers, see [URI] -->
<xs:notation name="uris" public="-//W3C//NOTATION XHTML Datatype: URIs//EN"/>
</xs:schema>
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/xhtml-datatypes-1.xsd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/xhtml-datatypes-1.xsd
.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns="http://www.w3.org/1999/xhtml/datatypes/"
xmlns:xh11d="http://www.w3.org/1999/xhtml/datatypes/"
targetNamespace="http://www.w3.org/1999/xhtml/datatypes/"
elementFormDefault="qualified"
>
<xs:annotation>
<xs:documentation>
XHTML Datatypes
This is the XML Schema datatypes module for XHTML
Defines containers for the XHTML datatypes, many of
these imported from other specifications and standards.
$Id: xhtml-datatypes-1.xsd,v 1.12 2009/09/30 15:12:48 ahby Exp $
</xs:documentation>
<xs:documentation source="xhtml-copyright-1.xsd"/>
<xs:documentation source="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/abstraction.html#s_common_attrtypes"/>
</xs:annotation>
<!-- nn for pixels or nn% for percentage length -->
<xs:simpleType name="Length">
<xs:union memberTypes="xs:nonNegativeInteger">
<xs:simpleType>
<xs:restriction base="xs:token">
<xs:pattern value="\d+[%]|\d*\.\d+[%]"/>
</xs:restriction>
</xs:simpleType>
</xs:union>
</xs:simpleType>
<!-- space-separated list of link types -->
<xs:simpleType name="LinkTypes">
<xs:list itemType="xs:NMTOKEN"/>
</xs:simpleType>
<!-- single or comma-separated list of media descriptors -->
<xs:simpleType name="MediaDesc">
<xs:restriction base="xs:string"/>
</xs:simpleType>
<!-- pixel, percentage, or relative -->
<xs:simpleType name="MultiLength">
<xs:union memberTypes="xh11d:Length">
<xs:simpleType>
<xs:restriction base="xs:token">
<xs:pattern value="\d*\*"/>
</xs:restriction>
</xs:simpleType>
</xs:union>
</xs:simpleType>
<!-- one or more digits (NUMBER) -->
<xs:simpleType name="Number">
<xs:restriction base="xs:nonNegativeInteger"/>
</xs:simpleType>
<!-- integer representing length in pixels -->
<xs:simpleType name="Pixels">
<xs:restriction base="xs:nonNegativeInteger"/>
</xs:simpleType>
<!-- script expression -->
<xs:simpleType name="Script">
<xs:restriction base="xs:string"/>
</xs:simpleType>
<!-- sixteen color names or RGB color expression-->
<xs:simpleType name="Color">
<xs:union memberTypes="xs:NMTOKEN">
<xs:simpleType>
<xs:restriction base="xs:token">
<xs:pattern value="#[0-9a-fA-F]{3}([0-9a-fA-F]{3})?"/>
</xs:restriction>
</xs:simpleType>
</xs:union>
</xs:simpleType>
<!-- textual content -->
<xs:simpleType name="Text">
<xs:restriction base="xs:string"/>
</xs:simpleType>
<!-- Imported Datatypes -->
<!-- a single character, as per section 2.2 of [XML] -->
<xs:simpleType name="Character">
<xs:restriction base="xs:string">
<xs:length value="1" fixed="true"/>
</xs:restriction>
</xs:simpleType>
<!-- a character encoding, as per [RFC2045] -->
<xs:simpleType name="Charset">
<xs:restriction base="xs:string"/>
</xs:simpleType>
<!-- a space separated list of character encodings, as per [RFC2045] -->
<xs:simpleType name="Charsets">
<xs:list itemType="Charset"/>
</xs:simpleType>
<!-- media type, as per [RFC2045] -->
<xs:simpleType name="ContentType">
<xs:restriction base="xs:string"/>
</xs:simpleType>
<!-- comma-separated list of media types, as per [RFC2045] -->
<xs:simpleType name="ContentTypes">
<xs:restriction base="xs:string"/>
</xs:simpleType>
<!-- date and time information. ISO date format -->
<xs:simpleType name="Datetime">
<xs:restriction base="xs:dateTime"/>
</xs:simpleType>
<!-- formal public identifier, as per [ISO8879] -->
<xs:simpleType name="FPI">
<xs:restriction base="xs:normalizedString"/>
</xs:simpleType>
<!-- a window name as used in the target attribute -->
<xs:simpleType name="FrameTarget">
<xs:union>
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="_blank"/>
<xs:enumeration value="_self"/>
<xs:enumeration value="_parent"/>
<xs:enumeration value="_top"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:pattern value="[a-zA-Z].*"/>
</xs:restriction>
</xs:simpleType>
</xs:union>
</xs:simpleType>
<!-- a language code, as per [RFC3066] -->
<xs:simpleType name="LanguageCode">
<xs:restriction base="xs:language"/>
</xs:simpleType>
<!-- a comma separated list of language ranges -->
<xs:simpleType name="LanguageCodes">
<xs:restriction base="xs:string"/>
</xs:simpleType>
<!-- a Uniform Resource Identifier, see [URI] -->
<xs:simpleType name="URI">
<xs:restriction base="xs:anyURI"/>
</xs:simpleType>
<!-- a space-separated list of Uniform Resource Identifiers, see [URI] -->
<xs:simpleType name="URIs">
<xs:list itemType="xs:anyURI"/>
</xs:simpleType>
<!-- a relative URI reference to a fragment ID -->
<xs:simpleType name="URIREF">
<xs:restriction base="xs:string">
<xs:pattern value="#\c*" />
<xs:minLength value="1"/>
</xs:restriction>
</xs:simpleType>
<!-- comma-separated list of MultiLength -->
<xs:simpleType name="MultiLengths">
<xs:restriction base="xs:string"/>
</xs:simpleType>
<!-- character Data -->
<xs:simpleType name="CDATA">
<xs:restriction base="xs:string"/>
</xs:simpleType>
<!-- CURIE placeholder datatypes -->
<xs:simpleType name="CURIE">
<xs:restriction base="xs:string">
<xs:pattern value="(([\i-[:]][\c-[:]]*)?:)?.+" />
<xs:minLength value="1"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="CURIEs">
<xs:list itemType="xh11d:CURIE"/>
</xs:simpleType>
<xs:simpleType name="SafeCURIE">
<xs:restriction base="xs:string">
<xs:pattern value="\[(([\i-[:]][\c-[:]]*)?:)?.+\]" />
<xs:minLength value="3"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="SafeCURIEs">
<xs:list itemType="xh11d:SafeCURIE"/>
</xs:simpleType>
<xs:simpleType name="URIorSafeCURIE">
<xs:union memberTypes="xs:anyURI xh11d:SafeCURIE" />
</xs:simpleType>
<xs:simpleType name="URIorSafeCURIEs">
<xs:list itemType="xh11d:URIorSafeCURIE"/>
</xs:simpleType>
</xs:schema>
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/xhtml-attribs-1.xsd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/xhtml-attribs-1.xsd
.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
xmlns:xh11d="http://www.w3.org/1999/xhtml/datatypes/"
>
<xs:import namespace="http://www.w3.org/1999/xhtml/datatypes/"
schemaLocation="xhtml-datatypes-1.xsd" />
<xs:annotation>
<xs:documentation>
This is the XML Schema common attributes module for XHTML
$Id: xhtml-attribs-1.xsd,v 1.9 2009/11/18 17:59:51 ahby Exp $
</xs:documentation>
<xs:documentation source="xhtml-copyright-1.xsd"/>
<xs:documentation source="http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_commonatts"/>
</xs:annotation>
<xs:import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2001/xml.xsd">
<xs:annotation>
<xs:documentation>
This import brings in the XML namespace attributes
The module itself does not provide the schemaLocation
and expects the driver schema to provide the
actual SchemaLocation.
</xs:documentation>
</xs:annotation>
</xs:import>
<xs:attributeGroup name="xhtml.id">
<xs:attribute name="id" type="xs:ID"/>
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.class">
<xs:attribute name="class" type="xs:string"/>
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.title">
<xs:attribute name="title" type="xs:string"/>
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.Core.attrib">
<xs:attribute ref="xml:space" fixed="preserve"/>
<xs:attributeGroup ref="xhtml.id"/>
<xs:attributeGroup ref="xhtml.class"/>
<xs:attributeGroup ref="xhtml.title"/>
<xs:attributeGroup ref="xhtml.Core.extra.attrib"/>
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.I18n.attrib">
<xs:attribute ref="xml:lang" />
<xs:attributeGroup ref="xhtml.I18n.extra.attrib"/>
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.Common.attrib">
<xs:attributeGroup ref="xhtml.Core.attrib"/>
<xs:attributeGroup ref="xhtml.I18n.attrib"/>
<xs:attributeGroup ref="xhtml.Common.extra"/>
</xs:attributeGroup>
<!-- Global attributes -->
<xs:attribute name="id" type="xs:ID"/>
<xs:attribute name="class" type="xs:string"/>
<xs:attribute name="title" type="xs:string"/>
<xs:attributeGroup name="xhtml.Global.core.attrib">
<xs:attribute ref="id"/>
<xs:attribute ref="class"/>
<xs:attribute ref="title"/>
<xs:attributeGroup ref="xhtml.Global.core.extra.attrib" />
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.Global.i18n.attrib">
<xs:attribute ref="xml:lang" />
<xs:attributeGroup ref="xhtml.Global.I18n.extra.attrib"/>
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.Global.common.attrib">
<xs:attributeGroup ref="xhtml.Global.core.attrib"/>
<xs:attributeGroup ref="xhtml.Global.i18n.attrib"/>
<xs:attributeGroup ref="xhtml.Global.Common.extra"/>
</xs:attributeGroup>
</xs:schema>
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/xhtml-charent-1.xsd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/xhtml-charent-1.xsd
.
<?xml version="1.0" encoding="UTF-8"?>
<!--
This schema module includes three named character entity files.
-->
<!DOCTYPE xs:schema [
<!-- These are the entity sets for ISO Latin 1 characters for the XHTML -->
<!ENTITY % HTMLlat1 PUBLIC
"-//W3C//ENTITIES Latin 1 for XHTML//EN"
"http://www.w3.org/MarkUp/DTD/xhtml-lat1.ent">
%HTMLlat1;
<!-- These are the entity sets for special characters for the XHTML -->
<!ENTITY % HTMLsymbol PUBLIC
"-//W3C//ENTITIES Symbols for XHTML//EN"
"http://www.w3.org/MarkUp/DTD/xhtml-symbol.ent">
%HTMLsymbol;
<!-- These are the entity sets for symbol characters for the XHTML -->
<!ENTITY % HTMLspecial PUBLIC
"-//W3C//ENTITIES Special for XHTML//EN"
"http://www.w3.org/MarkUp/DTD/xhtml-special.ent">
%HTMLspecial;
]>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<xs:annotation>
<xs:documentation>
Character Entities for XHTML
This is the XML Schema Character Entities module for XHTML
This module declares the set of character entities for XHTML,
including the Latin 1, Symbol and Special character collections.
XML Schema does not support Entities, hence Entities are enable
through an Internal DTD Subset.
$Id: xhtml-charent-1.xsd,v 1.3 2005/09/26 22:54:53 ahby Exp $
</xs:documentation>
<xs:documentation source="xhtml-copyright-1.xsd"/>
</xs:annotation>
</xs:schema>
This
section
contains
the
formal
definition
of
each
of
the
XHTML
Abstract
Modules
as
a
Schema
module.
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/xhtml-struct-1.xsd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/xhtml-struct-1.xsd
.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
xmlns:xh11d="http://www.w3.org/1999/xhtml/datatypes/">
<xs:import
namespace="http://www.w3.org/1999/xhtml/datatypes/"
schemaLocation="xhtml-datatypes-1.xsd"/>
<xs:annotation>
<xs:documentation>
This is the XML Schema Document Structure module for XHTML
Document Structure
* title, head, body, html
The Structure Module defines the major structural elements and
their attributes.
$Id: xhtml-struct-1.xsd,v 1.11 2009/09/30 14:13:35 ahby Exp $
</xs:documentation>
<xs:documentation source="xhtml-copyright-1.xsd"/>
<xs:documentation source="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/abstract_modules.html#s_structuremodule"/>
</xs:annotation>
<xs:import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2001/xml.xsd">
<xs:annotation>
<xs:documentation>
This import brings in the XML namespace attributes
The module itself does not provide the schemaLocation
and expects the driver schema to provide the
actual SchemaLocation.
</xs:documentation>
</xs:annotation>
</xs:import>
<xs:attributeGroup
name="xhtml.title.attlist">
<xs:attributeGroup
ref="xhtml.I18n.attrib"/>
<xs:attributeGroup ref="xhtml.id"/>
<xs:attribute ref="xml:space"/>
</xs:attributeGroup>
<xs:group
name="xhtml.title.content">
<xs:sequence/>
</xs:group>
<xs:complexType
name="xhtml.title.type"
mixed="true">
<xs:group
ref="xhtml.title.content"/>
<xs:attributeGroup
ref="xhtml.title.attlist"/>
</xs:complexType>
<xs:attributeGroup
name="xhtml.profile.attrib">
<xs:attribute
name="profile"
type="xh11d:URIs"/>
</xs:attributeGroup>
<xs:attributeGroup
name="xhtml.head.attlist">
<xs:attributeGroup
ref="xhtml.profile.attrib"/>
<xs:attributeGroup
ref="xhtml.I18n.attrib"/>
<xs:attributeGroup ref="xhtml.id"/>
<xs:attribute ref="xml:space"/>
</xs:attributeGroup>
<xs:complexType
name="xhtml.head.type">
<xs:group
ref="xhtml.head.content"/>
<xs:attributeGroup
ref="xhtml.head.attlist"/>
</xs:complexType>
<xs:attributeGroup
name="xhtml.body.attlist">
<xs:attributeGroup
ref="xhtml.Common.attrib"/>
</xs:attributeGroup>
<xs:group
name="xhtml.body.content">
<xs:sequence>
<xs:group
ref="xhtml.Block.mix"
minOccurs="0"
maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType
name="xhtml.body.type">
<xs:group
ref="xhtml.body.content"/>
<xs:attributeGroup
ref="xhtml.body.attlist"/>
</xs:complexType>
<xs:attributeGroup
name="xhtml.version.attrib">
<xs:attribute
name="version"
type="xh11d:CDATA"/>
</xs:attributeGroup>
<xs:attributeGroup
name="xhtml.html.attlist">
<xs:attributeGroup
ref="xhtml.version.attrib"/>
<xs:attributeGroup
ref="xhtml.I18n.attrib"/>
<xs:attributeGroup ref="xhtml.id"/>
<xs:attribute ref="xml:space"/>
</xs:attributeGroup>
<xs:group
name="xhtml.html.content">
<xs:sequence>
<xs:element
name="head"
type="xhtml.head.type"/>
<xs:element
name="body"
type="xhtml.body.type"/>
</xs:sequence>
</xs:group>
<xs:complexType
name="xhtml.html.type">
<xs:group
ref="xhtml.html.content"/>
<xs:attributeGroup
ref="xhtml.html.attlist"/>
</xs:complexType>
</xs:schema>
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/xhtml-text-1.xsd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/xhtml-text-1.xsd
.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
xmlns:xh11d="http://www.w3.org/1999/xhtml/datatypes/"
>
<xs:import namespace="http://www.w3.org/1999/xhtml/datatypes/"
schemaLocation="xhtml-datatypes-1.xsd" />
<xs:annotation>
<xs:documentation>
Textual Content
This is the XML Schema Text module for XHTML
The Text module includes declarations for all core
text container elements and their attributes.
+ block phrasal
+ block structural
+ inline phrasal
+ inline structural
$Id: xhtml-text-1.xsd,v 1.2 2005/09/26 22:54:53 ahby Exp $
</xs:documentation>
<xs:documentation source="xhtml-copyright-1.xsd"/>
<xs:documentation source="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/abstract_modules.html#s_textmodule"/>
</xs:annotation>
<xs:include schemaLocation="xhtml-blkphras-1.xsd">
<xs:annotation>
<xs:documentation>
Block Phrasal module
Elements defined here:
* address, blockquote, pre, h1, h2, h3, h4, h5, h6
</xs:documentation>
</xs:annotation>
</xs:include>
<xs:include schemaLocation="xhtml-blkstruct-1.xsd">
<xs:annotation>
<xs:documentation>
Block Structural module
Elements defined here:
* div, p
</xs:documentation>
</xs:annotation>
</xs:include>
<xs:include schemaLocation="xhtml-inlphras-1.xsd">
<xs:annotation>
<xs:documentation>
Inline Phrasal module
Elements defined here:
* abbr, acronym, cite, code, dfn, em, kbd, q, samp, strong, var
</xs:documentation>
</xs:annotation>
</xs:include>
<xs:include schemaLocation="xhtml-inlstruct-1.xsd">
<xs:annotation>
<xs:documentation>
Inline Structural module
Elements defined here:
* br,span
</xs:documentation>
</xs:annotation>
</xs:include>
</xs:schema>
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/xhtml-hypertext-1.xsd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/xhtml-hypertext-1.xsd
.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
xmlns:xh11d="http://www.w3.org/1999/xhtml/datatypes/"
>
<xs:import namespace="http://www.w3.org/1999/xhtml/datatypes/"
schemaLocation="xhtml-datatypes-1.xsd" />
<xs:annotation>
<xs:documentation>
Hypertext Module
This is the XML Schema Hypertext module for XHTML
* a
This module declares the anchor ('a') element type, which
defines the source of a hypertext link. The destination
(or link 'target') is identified via its 'id' attribute
rather than the 'name' attribute as was used in HTML.
$Id: xhtml-hypertext-1.xsd,v 1.4 2005/09/26 23:37:47 ahby Exp $
</xs:documentation>
<xs:documentation source="xhtml-copyright-1.xsd"/>
<xs:documentation source="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/abstract_modules.html#s_hypertextmodule"/>
</xs:annotation>
<xs:attributeGroup name="xhtml.a.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
<xs:attribute name="href" type="xh11d:URI"/>
<xs:attribute name="charset" type="xh11d:Charset"/>
<xs:attribute name="type" type="xh11d:ContentType"/>
<xs:attribute name="hreflang" type="xh11d:LanguageCode"/>
<xs:attribute name="rel" type="xh11d:LinkTypes"/>
<xs:attribute name="rev" type="xh11d:LinkTypes"/>
<xs:attribute name="accesskey" type="xh11d:Character"/>
<xs:attribute name="tabindex" type="xh11d:Number"/>
</xs:attributeGroup>
<xs:group name="xhtml.a.content">
<xs:sequence>
<xs:group ref="xhtml.InlNoAnchor.mix" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.a.type" mixed="true">
<xs:group ref="xhtml.a.content"/>
<xs:attributeGroup ref="xhtml.a.attlist"/>
</xs:complexType>
</xs:schema>
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/xhtml-list-1.xsd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/xhtml-list-1.xsd
.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
xmlns:xh11d="http://www.w3.org/1999/xhtml/datatypes/"
>
<xs:import namespace="http://www.w3.org/1999/xhtml/datatypes/"
schemaLocation="xhtml-datatypes-1.xsd" />
<xs:annotation>
<xs:documentation>
List Module
This is the XML Schema Lists module for XHTML
List Module Elements
* dl, dt, dd, ol, ul, li
This module declares the list-oriented element types
and their attributes.
$Id: xhtml-list-1.xsd,v 1.2 2005/09/26 22:54:53 ahby Exp $
</xs:documentation>
<xs:documentation source="xhtml-copyright-1.xsd"/>
<xs:documentation source="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/abstract_modules.html#s_listmodule"/>
</xs:annotation>
<xs:attributeGroup name="xhtml.dt.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.dt.content">
<xs:sequence>
<xs:group ref="xhtml.Inline.mix" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.dt.type" mixed="true">
<xs:group ref="xhtml.dt.content"/>
<xs:attributeGroup ref="xhtml.dt.attlist"/>
</xs:complexType>
<xs:attributeGroup name="xhtml.dd.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.dd.content">
<xs:sequence>
<xs:group ref="xhtml.Flow.mix" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.dd.type" mixed="true">
<xs:group ref="xhtml.dd.content"/>
<xs:attributeGroup ref="xhtml.dd.attlist"/>
</xs:complexType>
<xs:attributeGroup name="xhtml.dl.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.dl.content">
<xs:sequence>
<xs:choice maxOccurs="unbounded">
<xs:element name="dt" type="xhtml.dt.type"/>
<xs:element name="dd" type="xhtml.dd.type"/>
</xs:choice>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.dl.type">
<xs:group ref="xhtml.dl.content"/>
<xs:attributeGroup ref="xhtml.dl.attlist"/>
</xs:complexType>
<xs:attributeGroup name="xhtml.li.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.li.content">
<xs:sequence>
<xs:group ref="xhtml.Flow.mix" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.li.type" mixed="true">
<xs:group ref="xhtml.li.content"/>
<xs:attributeGroup ref="xhtml.li.attlist"/>
</xs:complexType>
<xs:attributeGroup name="xhtml.ol.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.ol.content">
<xs:sequence>
<xs:element name="li" type="xhtml.li.type" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.ol.type">
<xs:group ref="xhtml.ol.content"/>
<xs:attributeGroup ref="xhtml.ol.attlist"/>
</xs:complexType>
<xs:attributeGroup name="xhtml.ul.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.ul.content">
<xs:sequence>
<xs:element name="li" type="xhtml.li.type" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.ul.type">
<xs:group ref="xhtml.ul.content"/>
<xs:attributeGroup ref="xhtml.ul.attlist"/>
</xs:complexType>
</xs:schema>
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/xhtml-applet-1.xsd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/xhtml-applet-1.xsd
.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
xmlns:xh11d="http://www.w3.org/1999/xhtml/datatypes/"
>
<xs:import namespace="http://www.w3.org/1999/xhtml/datatypes/" schemaLocation="xhtml-datatypes-1.xsd" />
<xs:annotation>
<xs:documentation>
Java Applets
This is the XML Schema module for Java Applets in XHTML
* applet (param)
This module declares the applet element type and its attributes,
used to provide support for Java applets. The 'alt' attribute
is now required (as it is on images). One of either code or
object attributes must be present. In the document, place param
elements before the object elements that require their content.
Note that use of this module also instantiates of the
Param Element Module.
$Id: xhtml-applet-1.xsd,v 1.3 2005/09/26 22:54:52 ahby Exp $
</xs:documentation>
<xs:documentation source="xhtml-copyright-1.xsd"/>
<xs:documentation
source="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/abstract_modules.html#s_appletmodule"/>
</xs:annotation>
<xs:include schemaLocation="xhtml-param-1.xsd">
<xs:annotation>
<xs:documentation>
Param module
Include Param Module
</xs:documentation>
</xs:annotation>
</xs:include>
<xs:attributeGroup name="xhtml.applet.attlist">
<xs:attributeGroup ref="xhtml.Core.attrib"/>
<xs:attribute name="alt" type="xh11d:Text" use="required"/>
<xs:attribute name="archive" type="xh11d:CDATA"/>
<xs:attribute name="code" type="xh11d:CDATA"/>
<xs:attribute name="codebase" type="xh11d:URI"/>
<xs:attribute name="object" type="xh11d:CDATA"/>
<xs:attribute name="width" type="xh11d:Length" use="required"/>
<xs:attribute name="height" type="xh11d:Length" use="required"/>
</xs:attributeGroup>
<xs:group name="xhtml.applet.content">
<xs:sequence>
<xs:choice minOccurs="0" maxOccurs="unbounded">
<xs:element ref="param" />
<xs:group ref="xhtml.Flow.mix"/>
</xs:choice>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.applet.type" mixed="true">
<xs:group ref="xhtml.applet.content"/>
<xs:attributeGroup ref="xhtml.applet.attlist"/>
</xs:complexType>
</xs:schema>
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/xhtml-pres-1.xsd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/xhtml-pres-1.xsd
.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
xmlns:xh11d="http://www.w3.org/1999/xhtml/datatypes/"
>
<xs:import namespace="http://www.w3.org/1999/xhtml/datatypes/"
schemaLocation="xhtml-datatypes-1.xsd" />
<xs:annotation>
<xs:documentation>
This is the XML Schema Presentation module for XHTML
This is a REQUIRED module.
$Id: xhtml-pres-1.xsd,v 1.2 2005/09/26 22:54:53 ahby Exp $
</xs:documentation>
<xs:documentation source="xhtml-copyright-1.xsd"/>
</xs:annotation>
<xs:annotation>
<xs:documentation>
Presentational Elements
This module defines elements and their attributes for
simple presentation-related markup.
Elements defined here:
* hr
* b, big, i, small, sub, sup, tt
</xs:documentation>
<xs:documentation source="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/abstract_modules.html#s_presentationmodule"/>
</xs:annotation>
<xs:include schemaLocation="xhtml-blkpres-1.xsd">
<xs:annotation>
<xs:documentation>
Block Presentational module
Elements defined here:
* hr
</xs:documentation>
</xs:annotation>
</xs:include>
<xs:include schemaLocation="xhtml-inlpres-1.xsd">
<xs:annotation>
<xs:documentation>
Inline Presentational module
Elements defined here:
* b, big, i, small, sub, sup, tt
</xs:documentation>
</xs:annotation>
</xs:include>
</xs:schema>
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/xhtml-edit-1.xsd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/xhtml-edit-1.xsd
.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
xmlns:xh11d="http://www.w3.org/1999/xhtml/datatypes/"
>
<xs:import namespace="http://www.w3.org/1999/xhtml/datatypes/"
schemaLocation="xhtml-datatypes-1.xsd" />
<xs:annotation>
<xs:documentation>
Editing Elements
This is the XML Schema Editing Markup module for XHTML
* ins, del
This module declares element types and attributes used to indicate
inserted and deleted content while editing a document.
$Id: xhtml-edit-1.xsd,v 1.2 2005/09/26 22:54:53 ahby Exp $
</xs:documentation>
<xs:documentation source="xhtml-copyright-1.xsd"/>
<xs:documentation source="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/abstract_modules.html#s_editmodule"/>
</xs:annotation>
<xs:attributeGroup name="xhtml.edit.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
<xs:attribute name="cite" type="xh11d:URI"/>
<xs:attribute name="datetime" type="xh11d:Datetime"/>
</xs:attributeGroup>
<xs:group name="xhtml.edit.content">
<xs:sequence>
<xs:group ref="xhtml.Flow.mix" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.edit.type" mixed="true">
<xs:group ref="xhtml.edit.content"/>
<xs:attributeGroup ref="xhtml.edit.attlist"/>
</xs:complexType>
</xs:schema>
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/xhtml-bdo-1.xsd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/xhtml-bdo-1.xsd
.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
xmlns:xh11d="http://www.w3.org/1999/xhtml/datatypes/"
>
<xs:import namespace="http://www.w3.org/1999/xhtml/datatypes/"
schemaLocation="xhtml-datatypes-1.xsd" />
<xs:annotation>
<xs:documentation>
Bidirectional Override (bdo) Element
This is the XML Schema BDO Element module for XHTML
This modules declares the element 'bdo' and 'dir' attributes,
Used to override the Unicode bidirectional algorithm for selected
fragments of text.
Bidirectional text support includes both the bdo element and
the 'dir' attribute.
$Id: xhtml-bdo-1.xsd,v 1.6 2009/11/18 17:59:51 ahby Exp $
</xs:documentation>
<xs:documentation source="xhtml-copyright-1.xsd"/>
<xs:documentation source="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/abstract_modules.html#s_bdomodule"/>
</xs:annotation>
<xs:import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2001/xml.xsd">
<xs:annotation>
<xs:documentation>
This import brings in the XML namespace attributes
The module itself does not provide the schemaLocation
and expects the driver schema to provide the
actual SchemaLocation.
</xs:documentation>
</xs:annotation>
</xs:import>
<xs:attributeGroup name="xhtml.bdo.attlist">
<xs:attributeGroup ref="xhtml.Core.attrib"/>
<xs:attributeGroup ref="xhtml.I18n.extra.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.bdo.content">
<xs:sequence>
<xs:group ref="xhtml.Inline.mix" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.bdo.type" mixed="true">
<xs:group ref="xhtml.bdo.content"/>
<xs:attributeGroup ref="xhtml.bdo.attlist"/>
</xs:complexType>
<xs:attributeGroup name="xhtml.dir.attrib">
<xs:attribute name="dir">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="ltr"/>
<xs:enumeration value="rtl"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:attributeGroup>
<!-- Global dir attribute -->
<xs:attribute name="dir">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="ltr"/>
<xs:enumeration value="rtl"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attributeGroup name="xhtml.Global.bdo.attrib">
<xs:attribute ref="dir"/>
</xs:attributeGroup>
</xs:schema>
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/xhtml-basic-form-1.xsd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/xhtml-basic-form-1.xsd
.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
xmlns:xh11d="http://www.w3.org/1999/xhtml/datatypes/"
>
<xs:import namespace="http://www.w3.org/1999/xhtml/datatypes/"
schemaLocation="xhtml-datatypes-1.xsd" />
<xs:annotation>
<xs:documentation>
This is the XML Schema Basic Forms module for XHTML
$Id: xhtml-basic-form-1.xsd,v 1.3 2009/09/30 15:22:38 ahby Exp $
</xs:documentation>
<xs:documentation source="xhtml-copyright-1.xsd"/>
</xs:annotation>
<xs:annotation>
<xs:documentation>
Basic Forms
This forms module is based on the HTML 3.2 forms model, with
the WAI-requested addition of the label element. While this
module essentially mimics the content model and attributes of
HTML 3.2 forms, the element types declared herein also include
all HTML 4 common attributes.
Elements defined here:
* form, label, input, select, option, textarea
</xs:documentation>
<xs:documentation source="xhtml-copyright-1.xsd"/>
<xs:documentation
source="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/abstract_modules.html#s_sformsmodule"/>
</xs:annotation>
<xs:attributeGroup name="xhtml.form.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
<xs:attribute name="action" type="xh11d:URI" use="required"/>
<xs:attribute name="method" use="optional" default="get">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="get"/>
<xs:enumeration value="post"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="name" type="xh11d:CDATA"/>
<xs:attribute name="enctype" type="xh11d:ContentType" default="application/x-www-form-urlencoded"/>
</xs:attributeGroup>
<xs:group name="xhtml.form.content">
<xs:sequence>
<xs:group ref="xhtml.BlkNoForm.mix" minOccurs="1" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.form.type">
<xs:group ref="xhtml.form.content"/>
<xs:attributeGroup ref="xhtml.form.attlist"/>
</xs:complexType>
<xs:group name="xhtml.label.content">
<xs:sequence>
<xs:choice minOccurs="0" maxOccurs="unbounded">
<xs:element type="xhtml.input.type" name="input"/>
<xs:element type="xhtml.select.type" name="select"/>
<xs:element type="xhtml.textarea.type" name="textarea"/>
<xs:group ref="xhtml.InlStruct.class"/>
<xs:group ref="xhtml.InlPhras.class"/>
<xs:group ref="xhtml.I18n.class"/>
<xs:group ref="xhtml.InlPres.class"/>
<xs:group ref="xhtml.InlSpecial.class"/>
<xs:group ref="xhtml.Misc.class"/>
</xs:choice>
</xs:sequence>
</xs:group>
<xs:attributeGroup name="xhtml.label.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
<xs:attribute name="for" type="xs:IDREF"/>
<xs:attribute name="accesskey" type="xh11d:Character"/>
</xs:attributeGroup>
<xs:complexType name="xhtml.label.type" mixed="true">
<xs:group ref="xhtml.label.content"/>
<xs:attributeGroup ref="xhtml.label.attlist"/>
</xs:complexType>
<!--
Basic Forms removes button, 'image' and 'file' input types.
-->
<xs:simpleType name="xhtml.InputType.class">
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="text"/>
<xs:enumeration value="password"/>
<xs:enumeration value="checkbox"/>
<xs:enumeration value="radio"/>
<xs:enumeration value="submit"/>
<xs:enumeration value="reset"/>
<xs:enumeration value="hidden"/>
</xs:restriction>
</xs:simpleType>
<xs:attributeGroup name="xhtml.input.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
<xs:attribute name="type" type="xhtml.InputType.class" default="text"/>
<xs:attribute name="name" type="xh11d:CDATA"/>
<xs:attribute name="value" type="xh11d:CDATA"/>
<xs:attribute name="checked">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="checked"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="size" type="xh11d:Number"/>
<xs:attribute name="maxlength" type="xh11d:Number"/>
<xs:attribute name="src" type="xh11d:URI"/>
<xs:attribute name="tabindex" type="xh11d:Number"/>
<xs:attribute name="accesskey" type="xh11d:Character"/>
</xs:attributeGroup>
<xs:group name="xhtml.input.content">
<xs:sequence/>
</xs:group>
<xs:complexType name="xhtml.input.type">
<xs:group ref="xhtml.input.content"/>
<xs:attributeGroup ref="xhtml.input.attlist"/>
</xs:complexType>
<xs:attributeGroup name="xhtml.select.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
<xs:attribute name="name" type="xh11d:CDATA"/>
<xs:attribute name="size" type="xh11d:Number"/>
<xs:attribute name="multiple">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="multiple"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="tabindex" type="xh11d:Number"/>
</xs:attributeGroup>
<xs:group name="xhtml.select.content">
<xs:sequence>
<xs:element name="option" type="xhtml.option.type" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.select.type">
<xs:group ref="xhtml.select.content"/>
<xs:attributeGroup ref="xhtml.select.attlist"/>
</xs:complexType>
<xs:attributeGroup name="xhtml.option.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
<xs:attribute name="selected">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="selected"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="value" type="xh11d:CDATA"/>
<xs:attribute name="tabindex" type="xh11d:Number"/>
</xs:attributeGroup>
<xs:group name="xhtml.option.content">
<xs:sequence/>
</xs:group>
<xs:complexType name="xhtml.option.type" mixed="true">
<xs:group ref="xhtml.option.content"/>
<xs:attributeGroup ref="xhtml.option.attlist"/>
</xs:complexType>
<xs:attributeGroup name="xhtml.textarea.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
<xs:attribute name="name" type="xh11d:CDATA"/>
<xs:attribute name="rows" type="xh11d:Number" use="required"/>
<xs:attribute name="cols" type="xh11d:Number" use="required"/>
<xs:attribute name="accesskey" type="xh11d:Character"/>
</xs:attributeGroup>
<xs:group name="xhtml.textarea.content">
<xs:sequence/>
</xs:group>
<xs:complexType name="xhtml.textarea.type" mixed="true">
<xs:group ref="xhtml.textarea.content"/>
<xs:attributeGroup ref="xhtml.textarea.attlist"/>
</xs:complexType>
</xs:schema>
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/xhtml-form-1.xsd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/xhtml-form-1.xsd
.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
xmlns:xh11d="http://www.w3.org/1999/xhtml/datatypes/"
>
<xs:import namespace="http://www.w3.org/1999/xhtml/datatypes/"
schemaLocation="xhtml-datatypes-1.xsd" />
<xs:annotation>
<xs:documentation>
Forms
This is the XML Schema Forms module for XHTML
* form, label, input, select, optgroup, option,
textarea, fieldset, legend, button
This module declares markup to provide support for online
forms, based on the features found in HTML 4.0 forms.
$Id: xhtml-form-1.xsd,v 1.4 2009/09/30 15:22:38 ahby Exp $
</xs:documentation>
<xs:documentation source="xhtml-copyright-1.xsd"/>
<xs:documentation source="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/abstract_modules.html#s_extformsmodule"/>
</xs:annotation>
<!-- form: Form Element -->
<xs:attributeGroup name="xhtml.form.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
<xs:attribute name="action" type="xh11d:URI" use="required"/>
<xs:attribute name="method" default="get">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="get"/>
<xs:enumeration value="post"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="name" type="xh11d:CDATA"/>
<xs:attribute name="enctype" type="xh11d:ContentType" default="application/x-www-form-urlencoded"/>
<xs:attribute name="accept-charset" type="xh11d:Charsets"/>
<xs:attribute name="accept" type="xh11d:ContentTypes"/>
</xs:attributeGroup>
<xs:group name="xhtml.form.content">
<xs:sequence>
<xs:choice maxOccurs="unbounded">
<xs:group ref="xhtml.BlkNoForm.mix"/>
<xs:element name="fieldset" type="xhtml.fieldset.type"/>
</xs:choice>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.form.type">
<xs:group ref="xhtml.form.content"/>
<xs:attributeGroup ref="xhtml.form.attlist"/>
</xs:complexType>
<!--
label: Form Field Label Text
Note: Each label must not contain more than ONE field
-->
<xs:group name="xhtml.label.content">
<xs:sequence>
<xs:choice minOccurs="0" maxOccurs="unbounded">
<xs:element name="input" type="xhtml.input.type"/>
<xs:element name="select" type="xhtml.select.type"/>
<xs:element name="textarea" type="xhtml.textarea.type"/>
<xs:element name="button" type="xhtml.button.type"/>
<xs:group ref="xhtml.InlStruct.class"/>
<xs:group ref="xhtml.InlPhras.class"/>
<xs:group ref="xhtml.I18n.class"/>
<xs:group ref="xhtml.InlPres.class"/>
<xs:group ref="xhtml.InlSpecial.class"/>
<xs:group ref="xhtml.Inline.extra"/>
<xs:group ref="xhtml.Misc.class"/>
</xs:choice>
</xs:sequence>
</xs:group>
<xs:attributeGroup name="xhtml.label.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
<xs:attribute name="for" type="xs:IDREF"/>
<xs:attribute name="accesskey" type="xh11d:Character"/>
</xs:attributeGroup>
<xs:complexType name="xhtml.label.type" mixed="true">
<xs:group ref="xhtml.label.content"/>
<xs:attributeGroup ref="xhtml.label.attlist"/>
</xs:complexType>
<!-- input: Form Control -->
<xs:simpleType name="xhtml.InputType.class">
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="text"/>
<xs:enumeration value="password"/>
<xs:enumeration value="checkbox"/>
<xs:enumeration value="radio"/>
<xs:enumeration value="submit"/>
<xs:enumeration value="reset"/>
<xs:enumeration value="hidden"/>
<xs:enumeration value="image"/>
<xs:enumeration value="button"/>
<xs:enumeration value="file"/>
</xs:restriction>
</xs:simpleType>
<!--
attribute 'name' required for all but submit & reset
-->
<xs:attributeGroup name="xhtml.input.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
<xs:attribute name="type" type="xhtml.InputType.class" default="text"/>
<xs:attribute name="name" type="xh11d:CDATA"/>
<xs:attribute name="value" type="xh11d:CDATA"/>
<xs:attribute name="checked">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="checked"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="disabled">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="disabled"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="readonly">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="readonly"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="size" type="xh11d:Number"/>
<xs:attribute name="maxlength" type="xh11d:Number"/>
<xs:attribute name="src" type="xh11d:URI"/>
<xs:attribute name="alt" type="xh11d:Text"/>
<xs:attribute name="tabindex" type="xh11d:Number"/>
<xs:attribute name="accesskey" type="xh11d:Character"/>
<xs:attribute name="accept" type="xh11d:ContentTypes"/>
</xs:attributeGroup>
<xs:group name="xhtml.input.content">
<xs:sequence/>
</xs:group>
<xs:complexType name="xhtml.input.type">
<xs:group ref="xhtml.input.content"/>
<xs:attributeGroup ref="xhtml.input.attlist"/>
</xs:complexType>
<!-- select: Option Selector -->
<xs:attributeGroup name="xhtml.select.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
<xs:attribute name="name" type="xh11d:CDATA"/>
<xs:attribute name="size" type="xh11d:Number"/>
<xs:attribute name="multiple">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="multiple"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="disabled">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="disabled"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="tabindex" type="xh11d:Number"/>
</xs:attributeGroup>
<xs:group name="xhtml.select.content">
<xs:sequence>
<xs:choice maxOccurs="unbounded">
<xs:element name="optgroup" type="xhtml.optgroup.type"/>
<xs:element name="option" type="xhtml.option.type"/>
</xs:choice>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.select.type">
<xs:group ref="xhtml.select.content"/>
<xs:attributeGroup ref="xhtml.select.attlist"/>
</xs:complexType>
<!-- optgroup: Option Group -->
<xs:attributeGroup name="xhtml.optgroup.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
<xs:attribute name="disabled">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="disabled"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="label" type="xh11d:Text" use="required"/>
</xs:attributeGroup>
<xs:group name="xhtml.optgroup.content">
<xs:sequence>
<xs:element name="option" type="xhtml.option.type" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.optgroup.type">
<xs:group ref="xhtml.optgroup.content"/>
<xs:attributeGroup ref="xhtml.optgroup.attlist"/>
</xs:complexType>
<!-- option: Selectable Choice -->
<xs:attributeGroup name="xhtml.option.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
<xs:attribute name="selected">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="selected"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="disabled">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="disabled"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="label" type="xh11d:Text"/>
<xs:attribute name="value" type="xh11d:CDATA"/>
</xs:attributeGroup>
<xs:group name="xhtml.option.content">
<xs:sequence/>
</xs:group>
<xs:complexType name="xhtml.option.type" mixed="true">
<xs:group ref="xhtml.option.content"/>
<xs:attributeGroup ref="xhtml.option.attlist"/>
</xs:complexType>
<!-- textarea: Multi-Line Text Field -->
<xs:attributeGroup name="xhtml.textarea.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
<xs:attribute name="name" type="xh11d:CDATA"/>
<xs:attribute name="rows" type="xh11d:Number" use="required"/>
<xs:attribute name="cols" type="xh11d:Number" use="required"/>
<xs:attribute name="disabled">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="disabled"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="readonly">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="readonly"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="tabindex" type="xh11d:Number"/>
<xs:attribute name="accesskey" type="xh11d:Character"/>
</xs:attributeGroup>
<xs:group name="xhtml.textarea.content">
<xs:sequence/>
</xs:group>
<xs:complexType name="xhtml.textarea.type" mixed="true">
<xs:group ref="xhtml.textarea.content"/>
<xs:attributeGroup ref="xhtml.textarea.attlist"/>
</xs:complexType>
<!-- fieldset: Form Control Group -->
<xs:attributeGroup name="xhtml.fieldset.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.fieldset.content">
<xs:sequence>
<xs:choice minOccurs="0" maxOccurs="unbounded">
<xs:element name="legend" type="xhtml.legend.type"/>
<xs:group ref="xhtml.Flow.mix"/>
</xs:choice>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.fieldset.type" mixed="true">
<xs:group ref="xhtml.fieldset.content"/>
<xs:attributeGroup ref="xhtml.fieldset.attlist"/>
</xs:complexType>
<!-- legend: Fieldset Legend -->
<xs:attributeGroup name="xhtml.legend.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
<xs:attribute name="accesskey" type="xh11d:Character"/>
</xs:attributeGroup>
<xs:group name="xhtml.legend.content">
<xs:sequence>
<xs:group ref="xhtml.Inline.mix" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.legend.type" mixed="true">
<xs:group ref="xhtml.legend.content"/>
<xs:attributeGroup ref="xhtml.legend.attlist"/>
</xs:complexType>
<!-- button: Push Button -->
<xs:attributeGroup name="xhtml.button.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
<xs:attribute name="name" type="xh11d:CDATA"/>
<xs:attribute name="value" type="xh11d:CDATA"/>
<xs:attribute name="type" default="submit">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="button"/>
<xs:enumeration value="submit"/>
<xs:enumeration value="reset"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="disabled">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="disabled"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="tabindex" type="xh11d:Number"/>
<xs:attribute name="accesskey" type="xh11d:Character"/>
</xs:attributeGroup>
<xs:group name="xhtml.button.content">
<xs:sequence>
<xs:choice minOccurs="0" maxOccurs="unbounded">
<xs:group ref="xhtml.BlkNoForm.mix"/>
<xs:group ref="xhtml.InlStruct.class"/>
<xs:group ref="xhtml.InlPhras.class"/>
<xs:group ref="xhtml.InlPres.class"/>
<xs:group ref="xhtml.I18n.class"/>
<xs:group ref="xhtml.InlSpecial.class"/>
<xs:group ref="xhtml.Inline.extra"/>
</xs:choice>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.button.type" mixed="true">
<xs:group ref="xhtml.button.content"/>
<xs:attributeGroup ref="xhtml.button.attlist"/>
</xs:complexType>
</xs:schema>
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/xhtml-basic-table-1.xsd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/xhtml-basic-table-1.xsd
.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
xmlns:xh11d="http://www.w3.org/1999/xhtml/datatypes/"
>
<xs:import namespace="http://www.w3.org/1999/xhtml/datatypes/"
schemaLocation="xhtml-datatypes-1.xsd" />
<xs:annotation>
<xs:documentation>
This is the XML Schema Basic Tables module for XHTML
$Id: xhtml-basic-table-1.xsd,v 1.2 2005/09/26 22:54:53 ahby Exp $
</xs:documentation>
<xs:documentation source="xhtml-copyright-1.xsd"/>
</xs:annotation>
<xs:annotation>
<xs:documentation>
Basic Tables
* table, caption, tr, th, td
This table module declares elements and attributes defining
a table model based fundamentally on features found in the
widely-deployed HTML 3.2 table model. While this module
mimics the content model and table attributes of HTML 3.2
tables, the element types declared herein also includes all
HTML 4 common and most of the HTML 4 table attributes.
</xs:documentation>
<xs:documentation
source="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/abstract_modules.html#s_simpletablemodule"/>
</xs:annotation>
<xs:attributeGroup name="xhtml.CellHAlign.attrib">
<xs:attribute name="align">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="left"/>
<xs:enumeration value="center"/>
<xs:enumeration value="right"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.CellVAlign.attrib">
<xs:attribute name="valign">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="top"/>
<xs:enumeration value="middle"/>
<xs:enumeration value="bottom"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.scope.attrib">
<xs:attribute name="scope">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="row"/>
<xs:enumeration value="col"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.table.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
<xs:attribute name="summary" type="xh11d:Text"/>
</xs:attributeGroup>
<xs:group name="xhtml.table.content">
<xs:sequence>
<xs:element name="caption" type="xhtml.caption.type"
minOccurs="0" maxOccurs="1"/>
<xs:element name="tr" type="xhtml.tr.type" maxOccurs="unbounded" />
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.table.type" >
<xs:group ref="xhtml.table.content"/>
<xs:attributeGroup ref="xhtml.table.attlist"/>
</xs:complexType>
<xs:attributeGroup name="xhtml.caption.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.caption.content">
<xs:sequence>
<xs:group ref="xhtml.Inline.mix" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.caption.type" mixed="true" >
<xs:group ref="xhtml.caption.content"/>
<xs:attributeGroup ref="xhtml.caption.attlist"/>
</xs:complexType>
<xs:attributeGroup name="xhtml.tr.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
<xs:attributeGroup ref="xhtml.CellHAlign.attrib"/>
<xs:attributeGroup ref="xhtml.CellVAlign.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.tr.content">
<xs:sequence>
<xs:choice maxOccurs="unbounded">
<xs:element name="th" type="xhtml.th.type"/>
<xs:element name="td" type="xhtml.td.type"/>
</xs:choice>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.tr.type">
<xs:group ref="xhtml.tr.content"/>
<xs:attributeGroup ref="xhtml.tr.attlist"/>
</xs:complexType>
<xs:attributeGroup name="xhtml.th.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
<xs:attribute name="abbr" type="xh11d:Text"/>
<xs:attribute name="axis" type="xh11d:CDATA"/>
<xs:attribute name="headers" type="xs:IDREFS"/>
<xs:attributeGroup ref="xhtml.scope.attrib"/>
<xs:attribute name="rowspan" type="xh11d:Number" default="1"/>
<xs:attribute name="colspan" type="xh11d:Number" default="1"/>
<xs:attributeGroup ref="xhtml.CellHAlign.attrib"/>
<xs:attributeGroup ref="xhtml.CellVAlign.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.th.content">
<xs:sequence>
<xs:group ref="xhtml.FlowNoTable.mix" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.th.type" mixed="true">
<xs:group ref="xhtml.th.content"/>
<xs:attributeGroup ref="xhtml.th.attlist"/>
</xs:complexType>
<xs:attributeGroup name="xhtml.td.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
<xs:attribute name="abbr" type="xh11d:Text"/>
<xs:attribute name="axis" type="xh11d:CDATA"/>
<xs:attribute name="headers" type="xs:IDREFS"/>
<xs:attributeGroup ref="xhtml.scope.attrib"/>
<xs:attribute name="rowspan" type="xh11d:Number" default="1"/>
<xs:attribute name="colspan" type="xh11d:Number" default="1"/>
<xs:attributeGroup ref="xhtml.CellHAlign.attrib"/>
<xs:attributeGroup ref="xhtml.CellVAlign.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.td.content">
<xs:sequence>
<xs:group ref="xhtml.FlowNoTable.mix" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.td.type" mixed="true">
<xs:group ref="xhtml.td.content"/>
<xs:attributeGroup ref="xhtml.td.attlist"/>
</xs:complexType>
</xs:schema>
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/xhtml-table-1.xsd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/xhtml-table-1.xsd
.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
xmlns:xh11d="http://www.w3.org/1999/xhtml/datatypes/"
>
<xs:import namespace="http://www.w3.org/1999/xhtml/datatypes/"
schemaLocation="xhtml-datatypes-1.xsd" />
<xs:annotation>
<xs:documentation>
This is the XML Schema Tables module for XHTML
$Id: xhtml-table-1.xsd,v 1.3 2005/09/26 22:54:53 ahby Exp $
</xs:documentation>
<xs:documentation source="xhtml-copyright-1.xsd"/>
</xs:annotation>
<xs:annotation>
<xs:documentation>
Tables
* table, caption, thead, tfoot, tbody, colgroup, col, tr, th, td
This module declares element types and attributes used to provide
table markup similar to HTML 4.0, including features that enable
better accessibility for non-visual user agents.
</xs:documentation>
<xs:documentation source="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/abstract_modules.html#s_tablemodule"/>
</xs:annotation>
<xs:attributeGroup name="xhtml.frame.attrib">
<xs:attribute name="frame">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="void"/>
<xs:enumeration value="above"/>
<xs:enumeration value="below"/>
<xs:enumeration value="hsides"/>
<xs:enumeration value="lhs"/>
<xs:enumeration value="rhs"/>
<xs:enumeration value="vsides"/>
<xs:enumeration value="box"/>
<xs:enumeration value="border"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.rules.attrib">
<xs:attribute name="rules">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="none"/>
<xs:enumeration value="groups"/>
<xs:enumeration value="rows"/>
<xs:enumeration value="cols"/>
<xs:enumeration value="all"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.CellVAlign.attrib">
<xs:attribute name="valign">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="top"/>
<xs:enumeration value="middle"/>
<xs:enumeration value="bottom"/>
<xs:enumeration value="baseline"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.CellHAlign.attrib">
<xs:attribute name="align">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="left"/>
<xs:enumeration value="center"/>
<xs:enumeration value="right"/>
<xs:enumeration value="justify"/>
<xs:enumeration value="char"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="char" type="xh11d:Character"/>
<xs:attribute name="charoff" type="xh11d:Length"/>
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.scope.attrib">
<xs:attribute name="scope">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="row"/>
<xs:enumeration value="col"/>
<xs:enumeration value="rowgroup"/>
<xs:enumeration value="colgroup"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.td.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
<xs:attribute name="abbr" type="xh11d:Text"/>
<xs:attribute name="axis" type="xh11d:CDATA"/>
<xs:attribute name="headers" type="xs:IDREFS"/>
<xs:attributeGroup ref="xhtml.scope.attrib"/>
<xs:attribute name="rowspan" type="xh11d:Number" default="1"/>
<xs:attribute name="colspan" type="xh11d:Number" default="1"/>
<xs:attributeGroup ref="xhtml.CellHAlign.attrib"/>
<xs:attributeGroup ref="xhtml.CellVAlign.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.td.content">
<xs:sequence>
<xs:group ref="xhtml.Flow.mix" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.td.type" mixed="true">
<xs:group ref="xhtml.td.content"/>
<xs:attributeGroup ref="xhtml.td.attlist"/>
</xs:complexType>
<xs:attributeGroup name="xhtml.th.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
<xs:attribute name="abbr" type="xh11d:Text"/>
<xs:attribute name="axis" type="xh11d:CDATA"/>
<xs:attribute name="headers" type="xs:IDREFS"/>
<xs:attributeGroup ref="xhtml.scope.attrib"/>
<xs:attribute name="rowspan" type="xh11d:Number" default="1"/>
<xs:attribute name="colspan" type="xh11d:Number" default="1"/>
<xs:attributeGroup ref="xhtml.CellHAlign.attrib"/>
<xs:attributeGroup ref="xhtml.CellVAlign.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.th.content">
<xs:sequence>
<xs:group ref="xhtml.Flow.mix" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.th.type" mixed="true">
<xs:group ref="xhtml.th.content"/>
<xs:attributeGroup ref="xhtml.th.attlist"/>
</xs:complexType>
<xs:attributeGroup name="xhtml.tr.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
<xs:attributeGroup ref="xhtml.CellHAlign.attrib"/>
<xs:attributeGroup ref="xhtml.CellVAlign.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.tr.content">
<xs:sequence>
<xs:choice maxOccurs="unbounded">
<xs:element name="th" type="xhtml.th.type"/>
<xs:element name="td" type="xhtml.td.type"/>
</xs:choice>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.tr.type">
<xs:group ref="xhtml.tr.content"/>
<xs:attributeGroup ref="xhtml.tr.attlist"/>
</xs:complexType>
<xs:attributeGroup name="xhtml.col.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
<xs:attribute name="span" type="xh11d:Number" default="1"/>
<xs:attribute name="width" type="xh11d:MultiLength"/>
<xs:attributeGroup ref="xhtml.CellHAlign.attrib"/>
<xs:attributeGroup ref="xhtml.CellVAlign.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.col.content">
<xs:sequence/>
</xs:group>
<xs:complexType name="xhtml.col.type">
<xs:group ref="xhtml.col.content"/>
<xs:attributeGroup ref="xhtml.col.attlist"/>
</xs:complexType>
<xs:attributeGroup name="xhtml.colgroup.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
<xs:attribute name="span" type="xh11d:Number" default="1"/>
<xs:attribute name="width" type="xh11d:MultiLength"/>
<xs:attributeGroup ref="xhtml.CellHAlign.attrib"/>
<xs:attributeGroup ref="xhtml.CellVAlign.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.colgroup.content">
<xs:sequence>
<xs:element name="col" type="xhtml.col.type" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.colgroup.type">
<xs:group ref="xhtml.colgroup.content"/>
<xs:attributeGroup ref="xhtml.colgroup.attlist"/>
</xs:complexType>
<xs:attributeGroup name="xhtml.tbody.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
<xs:attributeGroup ref="xhtml.CellHAlign.attrib"/>
<xs:attributeGroup ref="xhtml.CellVAlign.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.tbody.content">
<xs:sequence>
<xs:element name="tr" type="xhtml.tr.type" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.tbody.type">
<xs:group ref="xhtml.tbody.content"/>
<xs:attributeGroup ref="xhtml.tbody.attlist"/>
</xs:complexType>
<xs:attributeGroup name="xhtml.tfoot.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
<xs:attributeGroup ref="xhtml.CellHAlign.attrib"/>
<xs:attributeGroup ref="xhtml.CellVAlign.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.tfoot.content">
<xs:sequence>
<xs:element name="tr" type="xhtml.tr.type" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.tfoot.type">
<xs:group ref="xhtml.tfoot.content"/>
<xs:attributeGroup ref="xhtml.tfoot.attlist"/>
</xs:complexType>
<xs:attributeGroup name="xhtml.thead.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
<xs:attributeGroup ref="xhtml.CellHAlign.attrib"/>
<xs:attributeGroup ref="xhtml.CellVAlign.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.thead.content">
<xs:sequence>
<xs:element name="tr" type="xhtml.tr.type" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.thead.type">
<xs:group ref="xhtml.thead.content"/>
<xs:attributeGroup ref="xhtml.thead.attlist"/>
</xs:complexType>
<xs:attributeGroup name="xhtml.caption.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.caption.content">
<xs:sequence>
<xs:group ref="xhtml.Inline.mix" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.caption.type" mixed="true">
<xs:group ref="xhtml.caption.content"/>
<xs:attributeGroup ref="xhtml.caption.attlist"/>
</xs:complexType>
<xs:attributeGroup name="xhtml.table.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
<xs:attribute name="summary" type="xh11d:Text"/>
<xs:attribute name="width" type="xh11d:Length"/>
<xs:attribute name="border" type="xh11d:Pixels"/>
<xs:attributeGroup ref="xhtml.frame.attrib"/>
<xs:attributeGroup ref="xhtml.rules.attrib"/>
<xs:attribute name="cellspacing" type="xh11d:Length"/>
<xs:attribute name="cellpadding" type="xh11d:Length"/>
</xs:attributeGroup>
<xs:group name="xhtml.table.content">
<xs:sequence>
<xs:element name="caption" type="xhtml.caption.type" minOccurs="0"/>
<xs:choice>
<xs:element name="col" type="xhtml.col.type" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="colgroup" type="xhtml.colgroup.type" minOccurs="0" maxOccurs="unbounded"/>
</xs:choice>
<xs:choice>
<xs:sequence>
<xs:element name="thead" type="xhtml.thead.type" minOccurs="0"/>
<xs:element name="" type="xhtml.tfoot.type" minOccurs="0"/>
<xs:element name="tbody" type="xhtml.tbody.type" maxOccurs="unbounded"/>
</xs:sequence>
<xs:choice>
<xs:element name="tr" type="xhtml.tr.type" maxOccurs="unbounded"/>
</xs:choice>
</xs:choice>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.table.type">
<xs:group ref="xhtml.table.content"/>
<xs:attributeGroup ref="xhtml.table.attlist"/>
</xs:complexType>
</xs:schema>
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/xhtml-image-1.xsd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/xhtml-image-1.xsd
.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
xmlns:xh11d="http://www.w3.org/1999/xhtml/datatypes/"
>
<xs:import namespace="http://www.w3.org/1999/xhtml/datatypes/"
schemaLocation="xhtml-datatypes-1.xsd" />
<xs:annotation>
<xs:documentation>
Images
This is the XML Schema Images module for XHTML
* img
This module provides markup to support basic image embedding.
To avoid problems with text-only UAs as well as to make
image content understandable and navigable to users of
non-visual UAs, you need to provide a description with
the 'alt' attribute, and avoid server-side image maps.
$Id: xhtml-image-1.xsd,v 1.3 2009/09/30 15:22:38 ahby Exp $
</xs:documentation>
<xs:documentation source="xhtml-copyright-1.xsd"/>
<xs:documentation source="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/abstract_modules.html#s_imagemodule"/>
</xs:annotation>
<xs:attributeGroup name="xhtml.img.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
<xs:attribute name="src" type="xh11d:URI" use="required"/>
<xs:attribute name="alt" type="xh11d:Text" use="required"/>
<xs:attribute name="longdesc" type="xh11d:URI"/>
<xs:attribute name="name" type="xh11d:CDATA"/>
<xs:attribute name="height" type="xh11d:Length"/>
<xs:attribute name="width" type="xh11d:Length"/>
</xs:attributeGroup>
<xs:group name="xhtml.img.content">
<xs:sequence/>
</xs:group>
<xs:complexType name="xhtml.img.type">
<xs:group ref="xhtml.img.content"/>
<xs:attributeGroup ref="xhtml.img.attlist"/>
</xs:complexType>
</xs:schema>
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/xhtml-csismap-1.xsd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/xhtml-csismap-1.xsd
.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
xmlns:xh11d="http://www.w3.org/1999/xhtml/datatypes/"
>
<xs:import namespace="http://www.w3.org/1999/xhtml/datatypes/"
schemaLocation="xhtml-datatypes-1.xsd" />
<xs:annotation>
<xs:documentation>
Client-side Image Maps
This is the XML Schema Client-side Image Maps module for XHTML
* area, map
This module declares elements and attributes to support client-side
image maps.
$Id: xhtml-csismap-1.xsd,v 1.3 2009/09/30 15:12:48 ahby Exp $
</xs:documentation>
<xs:documentation source="xhtml-copyright-1.xsd"/>
<xs:documentation source="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/abstract_modules.html#s_imapmodule"/>
</xs:annotation>
<xs:simpleType name="xhtml.Shape.Datatype">
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="rect"/>
<xs:enumeration value="circle"/>
<xs:enumeration value="poly"/>
<xs:enumeration value="default"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="xhtml.Coords.Datatype">
<xs:restriction base="xh11d:Text"/>
</xs:simpleType>
<!-- modify anchor attribute definition list -->
<xs:attributeGroup name="xhtml.a.csim.attlist">
<xs:attribute name="shape" type="xhtml.Shape.Datatype" default="rect"/>
<xs:attribute name="coords" type="xhtml.Coords.Datatype"/>
</xs:attributeGroup>
<!-- modify img attribute definition list -->
<xs:attributeGroup name="xhtml.img.csim.attlist">
<xs:attribute name="usemap" type="xh11d:URIREF"/>
</xs:attributeGroup>
<!-- modify form input attribute definition list -->
<xs:attributeGroup name="xhtml.input.csim.attlist">
<xs:attribute name="usemap" type="xh11d:URIREF"/>
</xs:attributeGroup>
<!-- modify object attribute definition list -->
<xs:attributeGroup name="xhtml.object.csim.attlist">
<xs:attribute name="usemap" type="xh11d:URIREF"/>
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.area.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
<xs:attribute name="href" type="xh11d:URI"/>
<xs:attribute name="shape" type="xhtml.Shape.Datatype" default="rect"/>
<xs:attribute name="coords" type="xhtml.Coords.Datatype"/>
<xs:attribute name="nohref">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="nohref"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="alt" type="xh11d:Text" use="required"/>
<xs:attribute name="tabindex" type="xh11d:Number"/>
<xs:attribute name="accesskey" type="xh11d:Character"/>
</xs:attributeGroup>
<xs:group name="xhtml.area.content">
<xs:sequence/>
</xs:group>
<xs:complexType name="xhtml.area.type">
<xs:group ref="xhtml.area.content"/>
<xs:attributeGroup ref="xhtml.area.attlist"/>
</xs:complexType>
<!-- map -->
<xs:attributeGroup name="xhtml.map.attlist">
<xs:attribute name="id" type="xs:ID" use="required"/>
<xs:attributeGroup ref="xhtml.class"/>
<xs:attributeGroup ref="xhtml.title"/>
<xs:attributeGroup ref="xhtml.Core.extra.attrib"/>
<xs:attributeGroup ref="xhtml.I18n.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.map.content">
<xs:sequence>
<xs:choice maxOccurs="unbounded">
<xs:group ref="xhtml.Block.mix"/>
<xs:element name="area" type="xhtml.area.type"/>
</xs:choice>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.map.type">
<xs:group ref="xhtml.map.content"/>
<xs:attributeGroup ref="xhtml.map.attlist"/>
</xs:complexType>
</xs:schema>
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/xhtml-ssismap-1.xsd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/xhtml-ssismap-1.xsd
.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
xmlns:xh11d="http://www.w3.org/1999/xhtml/datatypes/"
>
<xs:import namespace="http://www.w3.org/1999/xhtml/datatypes/"
schemaLocation="xhtml-datatypes-1.xsd" />
<xs:annotation>
<xs:documentation>
This is the XML Schema Server-side Image Maps module for XHTML
$Id: xhtml-ssismap-1.xsd,v 1.3 2005/09/26 22:54:53 ahby Exp $
</xs:documentation>
<xs:documentation source="xhtml-copyright-1.xsd"/>
</xs:annotation>
<xs:annotation>
<xs:documentation>
Server-side Image Maps
This adds the 'ismap' attribute to the img element to
support server-side processing of a user selection.
</xs:documentation>
<xs:documentation source="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/abstract_modules.html#s_servermapmodule"/>
</xs:annotation>
<xs:attributeGroup name="xhtml.img.ssimap.attlist">
<xs:attribute name="ismap">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="ismap"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.input.ssimap.attlist">
<xs:attribute name="ismap">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="ismap"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:attributeGroup>
</xs:schema>
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/xhtml-object-1.xsd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/xhtml-object-1.xsd
.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
xmlns:xh11d="http://www.w3.org/1999/xhtml/datatypes/"
>
<xs:import namespace="http://www.w3.org/1999/xhtml/datatypes/"
schemaLocation="xhtml-datatypes-1.xsd" />
<xs:annotation>
<xs:documentation>
This is the XML Schema Embedded Object module for XHTML
$Id: xhtml-object-1.xsd,v 1.2 2005/09/26 22:54:53 ahby Exp $
</xs:documentation>
<xs:documentation source="xhtml-copyright-1.xsd"/>
</xs:annotation>
<xs:annotation>
<xs:documentation>
This module declares the object element type and its attributes,
used to embed external objects as part of XHTML pages. In the
document, place param elements prior to the object elements
that require their content.
Note that use of this module requires instantiation of the
Param Element Module prior to this module.
Elements defined here:
* object (param)
</xs:documentation>
<xs:documentation source="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/abstract_modules.html#s_objectmodule"/>
</xs:annotation>
<xs:include schemaLocation="xhtml-param-1.xsd">
<xs:annotation>
<xs:documentation>
Param module
Elements defined here:
* param
</xs:documentation>
</xs:annotation>
</xs:include>
<xs:attributeGroup name="xhtml.object.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
<xs:attribute name="declare">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="declare"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="classid" type="xh11d:URI"/>
<xs:attribute name="codebase" type="xh11d:URI"/>
<xs:attribute name="data" type="xh11d:URI"/>
<xs:attribute name="type" type="xh11d:ContentType"/>
<xs:attribute name="codetype" type="xh11d:ContentType"/>
<xs:attribute name="archive" type="xh11d:URIs"/>
<xs:attribute name="standby" type="xh11d:Text"/>
<xs:attribute name="height" type="xh11d:Length"/>
<xs:attribute name="width" type="xh11d:Length"/>
<xs:attribute name="name" type="xh11d:CDATA"/>
<xs:attribute name="tabindex" type="xh11d:Number"/>
</xs:attributeGroup>
<xs:group name="xhtml.object.content">
<xs:sequence>
<xs:choice minOccurs="0" maxOccurs="unbounded">
<xs:element name="param" type="xhtml.param.type"/>
<xs:group ref="xhtml.Flow.mix"/>
</xs:choice>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.object.type" mixed="true">
<xs:group ref="xhtml.object.content"/>
<xs:attributeGroup ref="xhtml.object.attlist"/>
</xs:complexType>
</xs:schema>
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/xhtml-frames-1.xsd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/xhtml-frames-1.xsd
.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
xmlns:xh11d="http://www.w3.org/1999/xhtml/datatypes/"
>
<xs:import namespace="http://www.w3.org/1999/xhtml/datatypes/"
schemaLocation="xhtml-datatypes-1.xsd" />
<xs:annotation>
<xs:documentation>
This is the XML Schema Frames module for XHTML
$Id: xhtml-frames-1.xsd,v 1.2 2005/09/26 22:54:53 ahby Exp $
</xs:documentation>
<xs:documentation source="xhtml-copyright-1.xsd"/>
</xs:annotation>
<xs:annotation>
<xs:documentation>
Frames
* frameset, frame, noframes
This module declares frame-related element types and attributes.
</xs:documentation>
<xs:documentation
source="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/abstract_modules.html#s_framesmodule"/>
</xs:annotation>
<xs:attributeGroup name="xhtml.frameset.attlist">
<xs:attributeGroup ref="xhtml.Core.attrib"/>
<xs:attribute name="rows" type="xh11d:MultiLengths"/>
<xs:attribute name="cols" type="xh11d:MultiLengths"/>
</xs:attributeGroup>
<xs:group name="xhtml.frameset.content">
<xs:sequence>
<xs:choice minOccurs="1" maxOccurs="unbounded">
<xs:element ref="frameset"/>
<xs:element ref="frame"/>
</xs:choice>
<xs:element ref="noframes" minOccurs="0" maxOccurs="1"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.frameset.type" mixed="true">
<xs:group ref="xhtml.frameset.content"/>
<xs:attributeGroup ref="xhtml.frameset.attlist"/>
</xs:complexType>
<!--
reserved frame names start with "_"
otherwise starts with letter
-->
<xs:attributeGroup name="xhtml.frame.attlist">
<xs:attributeGroup ref="xhtml.Core.attrib"/>
<xs:attribute name="longdesc" type="xh11d:URI"/>
<xs:attribute name="src" type="xh11d:URI"/>
<xs:attribute name="frameborder" default="1">
<xs:simpleType>
<xs:restriction base="xs:nonNegativeInteger">
<xs:enumeration value="1"/>
<xs:enumeration value="0"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="marginwidth" type="xh11d:Pixels"/>
<xs:attribute name="marginheight" type="xh11d:Pixels"/>
<xs:attribute name="noresize">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="noresize"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="scrolling" default="auto">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="yes"/>
<xs:enumeration value="no"/>
<xs:enumeration value="auto"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:attributeGroup>
<xs:group name="xhtml.frame.content">
<xs:sequence/>
</xs:group>
<xs:complexType name="xhtml.frame.type">
<xs:group ref="xhtml.frame.content"/>
<xs:attributeGroup ref="xhtml.frame.attlist"/>
</xs:complexType>
<!--
noframes
-->
<xs:group name="xhtml.noframes.content">
<xs:sequence>
<xs:element ref="body"/>
</xs:sequence>
</xs:group>
<xs:attributeGroup name="xhtml.noframes.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
</xs:attributeGroup>
<xs:complexType name="xhtml.noframes.type" mixed="true">
<xs:group ref="xhtml.noframes.content"/>
<xs:attributeGroup ref="xhtml.noframes.attlist"/>
</xs:complexType>
</xs:schema>
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/xhtml-target-1.xsd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/xhtml-target-1.xsd
.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
xmlns:xh11d="http://www.w3.org/1999/xhtml/datatypes/"
>
<xs:import namespace="http://www.w3.org/1999/xhtml/datatypes/"
schemaLocation="xhtml-datatypes-1.xsd" />
<xs:annotation>
<xs:documentation>
This is the XML Schema Target module for XHTML
$Id: xhtml-target-1.xsd,v 1.3 2007/04/03 18:27:01 ahby Exp $
</xs:documentation>
<xs:documentation source="xhtml-copyright-1.xsd"/>
</xs:annotation>
<xs:annotation>
<xs:documentation>
Target
* target
This module declares the 'target' attribute used for opening windows
</xs:documentation>
<xs:documentation
source="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/abstract_modules.html#s_targetmodule"/>
</xs:annotation>
<xs:attributeGroup name="xhtml.base.target.attlist">
<xs:attribute name="target" type="xh11d:FrameTarget"/>
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.form.target.attlist">
<xs:attribute name="target" type="xh11d:FrameTarget"/>
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.link.target.attlist">
<xs:attribute name="target" type="xh11d:FrameTarget"/>
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.area.target.attlist">
<xs:attribute name="target" type="xh11d:FrameTarget"/>
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.a.target.attlist">
<xs:attribute name="target" type="xh11d:FrameTarget"/>
</xs:attributeGroup>
</xs:schema>
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/xhtml-iframe-1.xsd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/xhtml-iframe-1.xsd
.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
xmlns:xh11d="http://www.w3.org/1999/xhtml/datatypes/"
>
<xs:import namespace="http://www.w3.org/1999/xhtml/datatypes/"
schemaLocation="xhtml-datatypes-1.xsd" />
<xs:annotation>
<xs:documentation>
This is the XML Schema Inline Frame Element module for XHTML
$Id: xhtml-iframe-1.xsd,v 1.2 2005/09/26 22:54:53 ahby Exp $
</xs:documentation>
<xs:documentation source="xhtml-copyright-1.xsd"/>
</xs:annotation>
<xs:annotation>
<xs:documentation>
Inline Frames
* iframe
This module declares the iframe element type and its attributes,
used to create an inline frame within a document.
</xs:documentation>
<xs:documentation
source="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/abstract_modules.html#s_iframemodule"/>
</xs:annotation>
<xs:attributeGroup name="xhtml.iframe.attlist">
<xs:attributeGroup ref="xhtml.Core.attrib"/>
<xs:attribute name="longdesc" type="xh11d:URI"/>
<xs:attribute name="src" type="xh11d:URI"/>
<xs:attribute name="frameborder" default="1">
<xs:simpleType>
<xs:restriction base="xs:nonNegativeInteger">
<xs:enumeration value="1"/>
<xs:enumeration value="0"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="marginwidth" type="xh11d:Pixels"/>
<xs:attribute name="marginheight" type="xh11d:Pixels"/>
<xs:attribute name="scrolling" default="auto">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="yes"/>
<xs:enumeration value="no"/>
<xs:enumeration value="auto"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="height" type="xh11d:Length"/>
<xs:attribute name="width" type="xh11d:Length"/>
</xs:attributeGroup>
<xs:group name="xhtml.iframe.content">
<xs:sequence>
<xs:group ref="xhtml.Flow.mix" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.iframe.type" mixed="true">
<xs:group ref="xhtml.iframe.content"/>
<xs:attributeGroup ref="xhtml.iframe.attlist"/>
</xs:complexType>
</xs:schema>
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/xhtml-events-1.xsd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/xhtml-events-1.xsd
.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
xmlns:xh11d="http://www.w3.org/1999/xhtml/datatypes/"
>
<xs:import namespace="http://www.w3.org/1999/xhtml/datatypes/"
schemaLocation="xhtml-datatypes-1.xsd" />
<xs:annotation>
<xs:documentation>
This is the XML Schema Intrinsic Events module for XHTML
$Id: xhtml-events-1.xsd,v 1.4 2005/09/26 22:54:53 ahby Exp $
</xs:documentation>
<xs:documentation source="xhtml-copyright-1.xsd"/>
</xs:annotation>
<xs:annotation>
<xs:documentation>
Intrinsic Event Attributes
These are the event attributes defined in HTML 4,
Section 18.2.3 "Intrinsic Events".
</xs:documentation>
<xs:documentation source="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/abstract_modules.html#s_intrinsiceventsmodule"/>
</xs:annotation>
<xs:attributeGroup name="xhtml.Events.attrib">
<xs:attribute name="onclick" type="xh11d:Script"/>
<xs:attribute name="ondblclick" type="xh11d:Script"/>
<xs:attribute name="onmousedown" type="xh11d:Script"/>
<xs:attribute name="onmouseup" type="xh11d:Script"/>
<xs:attribute name="onmouseover" type="xh11d:Script"/>
<xs:attribute name="onmousemove" type="xh11d:Script"/>
<xs:attribute name="onmouseout" type="xh11d:Script"/>
<xs:attribute name="onkeypress" type="xh11d:Script"/>
<xs:attribute name="onkeydown" type="xh11d:Script"/>
<xs:attribute name="onkeyup" type="xh11d:Script"/>
</xs:attributeGroup>
<!--
additional attributes on anchor element
-->
<xs:attributeGroup name="xhtml.a.events.attlist">
<xs:attribute name="onfocus" type="xh11d:Script"/>
<xs:attribute name="onblur" type="xh11d:Script"/>
</xs:attributeGroup>
<!--
additional attributes on form element
-->
<xs:attributeGroup name="xhtml.form.events.attlist">
<xs:attribute name="onsubmit" type="xh11d:Script"/>
<xs:attribute name="onreset" type="xh11d:Script"/>
</xs:attributeGroup>
<!--
additional attributes on label element
-->
<xs:attributeGroup name="xhtml.label.events.attlist">
<xs:attribute name="onfocus" type="xh11d:Script"/>
<xs:attribute name="onblur" type="xh11d:Script"/>
</xs:attributeGroup>
<!--
additional attributes on input element
-->
<xs:attributeGroup name="xhtml.input.events.attlist">
<xs:attribute name="onfocus" type="xh11d:Script"/>
<xs:attribute name="onblur" type="xh11d:Script"/>
<xs:attribute name="onselect" type="xh11d:Script"/>
<xs:attribute name="onchange" type="xh11d:Script"/>
</xs:attributeGroup>
<!--
additional attributes on select element
-->
<xs:attributeGroup name="xhtml.select.events.attlist">
<xs:attribute name="onfocus" type="xh11d:Script"/>
<xs:attribute name="onblur" type="xh11d:Script"/>
<xs:attribute name="onchange" type="xh11d:Script"/>
</xs:attributeGroup>
<!--
additional attributes on textarea element
-->
<xs:attributeGroup name="xhtml.textarea.events.attlist">
<xs:attribute name="onfocus" type="xh11d:Script"/>
<xs:attribute name="onblur" type="xh11d:Script"/>
<xs:attribute name="onselect" type="xh11d:Script"/>
<xs:attribute name="onchange" type="xh11d:Script"/>
</xs:attributeGroup>
<!--
additional attributes on button element
-->
<xs:attributeGroup name="xhtml.button.events.attlist">
<xs:attribute name="onfocus" type="xh11d:Script"/>
<xs:attribute name="onblur" type="xh11d:Script"/>
</xs:attributeGroup>
<!--
additional attributes on body element
-->
<xs:attributeGroup name="xhtml.body.events.attlist">
<xs:attribute name="onload" type="xh11d:Script"/>
<xs:attribute name="onunload" type="xh11d:Script"/>
</xs:attributeGroup>
<!--
additional attributes on area element
-->
<xs:attributeGroup name="xhtml.area.events.attlist">
<xs:attribute name="onfocus" type="xh11d:Script"/>
<xs:attribute name="onblur" type="xh11d:Script"/>
</xs:attributeGroup>
<!--
Global Events Attributes
-->
<xs:attribute name="onclick" type="xh11d:Script"/>
<xs:attribute name="ondblclick" type="xh11d:Script"/>
<xs:attribute name="onmousedown" type="xh11d:Script"/>
<xs:attribute name="onmouseup" type="xh11d:Script"/>
<xs:attribute name="onmouseover" type="xh11d:Script"/>
<xs:attribute name="onmousemove" type="xh11d:Script"/>
<xs:attribute name="onmouseout" type="xh11d:Script"/>
<xs:attribute name="onkeypress" type="xh11d:Script"/>
<xs:attribute name="onkeydown" type="xh11d:Script"/>
<xs:attribute name="onkeyup" type="xh11d:Script"/>
<xs:attributeGroup name="xhtml.Global.events.attrib">
<xs:attribute ref="onclick"/>
<xs:attribute ref="ondblclick"/>
<xs:attribute ref="onmousedown"/>
<xs:attribute ref="onmouseup"/>
<xs:attribute ref="onmouseover"/>
<xs:attribute ref="onmousemove"/>
<xs:attribute ref="onmouseout"/>
<xs:attribute ref="onkeypress"/>
<xs:attribute ref="onkeydown"/>
<xs:attribute ref="onkeyup"/>
</xs:attributeGroup>
</xs:schema>
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/xhtml-meta-1.xsd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/xhtml-meta-1.xsd
.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
xmlns:xh11d="http://www.w3.org/1999/xhtml/datatypes/"
>
<xs:import namespace="http://www.w3.org/1999/xhtml/datatypes/"
schemaLocation="xhtml-datatypes-1.xsd" />
<xs:annotation>
<xs:documentation>
This is the XML Schema Metainformation module for XHTML
$Id: xhtml-meta-1.xsd,v 1.3 2008/07/05 04:11:00 ahby Exp $
</xs:documentation>
<xs:documentation source="xhtml-copyright-1.xsd"/>
</xs:annotation>
<xs:annotation>
<xs:documentation>
Meta Information
* meta
This module declares the meta element type and its attributes,
used to provide declarative document metainformation.
</xs:documentation>
<xs:documentation source="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/abstract_modules.html#s_metamodule"/>
</xs:annotation>
<xs:import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2001/xml.xsd">
<xs:annotation>
<xs:documentation>
This import brings in the XML namespace attributes
The module itself does not provide the schemaLocation
and expects the driver schema to provide the
actual SchemaLocation.
</xs:documentation>
</xs:annotation>
</xs:import>
<xs:attributeGroup name="xhtml.meta.attlist">
<xs:attributeGroup ref="xhtml.I18n.attrib"/>
<xs:attribute ref="xml:space"/>
<xs:attribute name="http-equiv" type="xs:NMTOKEN"/>
<xs:attribute name="name" type="xs:NMTOKEN"/>
<xs:attribute name="content" type="xh11d:CDATA" use="required"/>
<xs:attribute name="scheme" type="xh11d:CDATA"/>
</xs:attributeGroup>
<xs:group name="xhtml.meta.content">
<xs:sequence/>
</xs:group>
<xs:complexType name="xhtml.meta.type">
<xs:group ref="xhtml.meta.content"/>
<xs:attributeGroup ref="xhtml.meta.attlist"/>
</xs:complexType>
</xs:schema>
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/xhtml-script-1.xsd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/xhtml-script-1.xsd
.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
xmlns:xh11d="http://www.w3.org/1999/xhtml/datatypes/"
>
<xs:import namespace="http://www.w3.org/1999/xhtml/datatypes/"
schemaLocation="xhtml-datatypes-1.xsd" />
<xs:annotation>
<xs:documentation>
This is the XML Schema Scripting module for XHTML
$Id: xhtml-script-1.xsd,v 1.5 2006/09/11 08:50:41 ahby Exp $
</xs:documentation>
<xs:documentation source="xhtml-copyright-1.xsd"/>
</xs:annotation>
<xs:annotation>
<xs:documentation>
Scripting
* script, noscript
This module declares element types and attributes used to provide
support for executable scripts as well as an alternate content
container where scripts are not supported.
</xs:documentation>
<xs:documentation source="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/abstract_modules.html#s_scriptmodule"/>
</xs:annotation>
<xs:import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2001/xml.xsd">
<xs:annotation>
<xs:documentation>
This import brings in the XML namespace attributes
The module itself does not provide the schemaLocation
and expects the driver schema to provide the
actual SchemaLocation.
</xs:documentation>
</xs:annotation>
</xs:import>
<xs:attributeGroup name="xhtml.script.attlist">
<xs:attributeGroup ref="xhtml.id"/>
<xs:attribute name="charset" type="xh11d:Charset"/>
<xs:attribute name="type" type="xh11d:ContentType" use="required"/>
<xs:attribute name="src" type="xh11d:URI"/>
<xs:attribute name="defer">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="defer"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:attributeGroup>
<xs:group name="xhtml.script.content">
<xs:sequence/>
</xs:group>
<xs:complexType name="xhtml.script.type" mixed="true">
<xs:group ref="xhtml.script.content"/>
<xs:attributeGroup ref="xhtml.script.attlist"/>
</xs:complexType>
<xs:attributeGroup name="xhtml.noscript.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.noscript.content">
<xs:sequence>
<xs:group ref="xhtml.Block.mix" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.noscript.type">
<xs:group ref="xhtml.noscript.content"/>
<xs:attributeGroup ref="xhtml.noscript.attlist"/>
</xs:complexType>
</xs:schema>
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/xhtml-style-1.xsd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/xhtml-style-1.xsd
.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
xmlns:xh11d="http://www.w3.org/1999/xhtml/datatypes/"
>
<xs:import namespace="http://www.w3.org/1999/xhtml/datatypes/"
schemaLocation="xhtml-datatypes-1.xsd" />
<xs:annotation>
<xs:documentation>
This is the XML Schema Stylesheets module for XHTML
$Id: xhtml-style-1.xsd,v 1.5 2006/09/11 10:14:57 ahby Exp $
</xs:documentation>
<xs:documentation source="xhtml-copyright-1.xsd"/>
</xs:annotation>
<xs:annotation>
<xs:documentation>
Stylesheets
* style
This module declares the style element type and its attributes,
used to embed stylesheet information in the document head element.
</xs:documentation>
<xs:documentation source="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/abstract_modules.html#s_stylemodule"/>
</xs:annotation>
<xs:import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2001/xml.xsd">
<xs:annotation>
<xs:documentation>
This import brings in the XML namespace attributes
The module itself does not provide the schemaLocation
and expects the driver schema to provide the
actual SchemaLocation.
</xs:documentation>
</xs:annotation>
</xs:import>
<xs:attributeGroup name="xhtml.style.attlist">
<xs:attributeGroup ref="xhtml.id"/>
<xs:attributeGroup ref="xhtml.title"/>
<xs:attributeGroup ref="xhtml.I18n.attrib"/>
<xs:attribute name="type" type="xh11d:ContentType" use="required"/>
<xs:attribute name="media" type="xh11d:MediaDesc"/>
</xs:attributeGroup>
<xs:group name="xhtml.style.content">
<xs:sequence/>
</xs:group>
<xs:complexType name="xhtml.style.type" mixed="true">
<xs:group ref="xhtml.style.content"/>
<xs:attributeGroup ref="xhtml.style.attlist"/>
</xs:complexType>
</xs:schema>
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/xhtml-inlstyle-1.xsd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/xhtml-inlstyle-1.xsd
.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
xmlns:xh11d="http://www.w3.org/1999/xhtml/datatypes/"
>
<xs:import namespace="http://www.w3.org/1999/xhtml/datatypes/"
schemaLocation="xhtml-datatypes-1.xsd" />
<xs:annotation>
<xs:documentation>
Inline Style module
This is the XML Schema Inline Style module for XHTML
* styloe attribute
This module declares the 'style' attribute, used to support inline
style markup.
$Id: xhtml-inlstyle-1.xsd,v 1.2 2005/09/26 22:54:53 ahby Exp $
</xs:documentation>
<xs:documentation source="xhtml-copyright-1.xsd"/>
<xs:documentation source="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/abstract_modules.html#s_styleattributemodule"/>
</xs:annotation>
<xs:attributeGroup name="xhtml.style.attrib">
<xs:attribute name="style" type="xh11d:CDATA"/>
</xs:attributeGroup>
</xs:schema>
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/xhtml-link-1.xsd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/xhtml-link-1.xsd
.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
xmlns:xh11d="http://www.w3.org/1999/xhtml/datatypes/"
>
<xs:import namespace="http://www.w3.org/1999/xhtml/datatypes/"
schemaLocation="xhtml-datatypes-1.xsd" />
<xs:annotation>
<xs:documentation>
This is the XML Schema Link Element module for XHTML
$Id: xhtml-link-1.xsd,v 1.2 2005/09/26 22:54:53 ahby Exp $
</xs:documentation>
<xs:documentation source="xhtml-copyright-1.xsd"/>
</xs:annotation>
<xs:annotation>
<xs:documentation>
Link element
* link
This module declares the link element type and its attributes,
which could (in principle) be used to define document-level links
to external resources.
</xs:documentation>
<xs:documentation source="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/abstract_modules.html#s_linkmodule"/>
</xs:annotation>
<xs:attributeGroup name="xhtml.link.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
<xs:attribute name="charset" type="xh11d:Charset"/>
<xs:attribute name="href" type="xh11d:URI"/>
<xs:attribute name="hreflang" type="xh11d:LanguageCode"/>
<xs:attribute name="type" type="xh11d:ContentType"/>
<xs:attribute name="rel" type="xh11d:LinkTypes"/>
<xs:attribute name="rev" type="xh11d:LinkTypes"/>
<xs:attribute name="media" type="xh11d:MediaDesc"/>
</xs:attributeGroup>
<xs:group name="xhtml.link.content">
<xs:sequence/>
</xs:group>
<xs:complexType name="xhtml.link.type">
<xs:group ref="xhtml.link.content"/>
<xs:attributeGroup ref="xhtml.link.attlist"/>
</xs:complexType>
</xs:schema>
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/xhtml-base-1.xsd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/xhtml-base-1.xsd
.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
xmlns:xh11d="http://www.w3.org/1999/xhtml/datatypes/"
>
<xs:import namespace="http://www.w3.org/1999/xhtml/datatypes/"
schemaLocation="xhtml-datatypes-1.xsd" />
<xs:annotation>
<xs:documentation>
Base element
This is the XML Schema Base Element module for XHTML
* base
This module declares the base element type and its attributes,
used to define a base URI against which relative URIs in the
document will be resolved.
$Id: xhtml-base-1.xsd,v 1.2 2005/09/26 22:54:53 ahby Exp $
</xs:documentation>
<xs:documentation source="xhtml-copyright-1.xsd"/>
<xs:documentation source="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/abstract_modules.html#s_basemodule"/>
</xs:annotation>
<xs:attributeGroup name="xhtml.base.attlist">
<xs:attribute name="href" type="xh11d:URI" use="required"/>
</xs:attributeGroup>
<xs:group name="xhtml.base.content">
<xs:sequence/>
</xs:group>
<xs:complexType name="xhtml.base.type">
<xs:group ref="xhtml.base.content"/>
<xs:attributeGroup ref="xhtml.base.attlist"/>
</xs:complexType>
</xs:schema>
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/xhtml-nameident-1.xsd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/xhtml-nameident-1.xsd
.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
xmlns:xh11d="http://www.w3.org/1999/xhtml/datatypes/"
>
<xs:import namespace="http://www.w3.org/1999/xhtml/datatypes/"
schemaLocation="xhtml-datatypes-1.xsd" />
<xs:annotation>
<xs:documentation>
This is the XML Schema Name Identifier module for XHTML
$Id: xhtml-nameident-1.xsd,v 1.3 2009/09/30 15:22:38 ahby Exp $
</xs:documentation>
<xs:documentation source="xhtml-copyright-1.xsd"/>
</xs:annotation>
<xs:annotation>
<xs:documentation>
Name Identifier
* 'name' attribute on form, img, a, map, applet, frame, iframe
This module declares the 'name' attribute on element types when
it is used as a node identifier for legacy linking and scripting
support. This does not include those instances when 'name' is used
as a container for form control, property or metainformation names.
This module should be instantiated following all modules it modifies.
</xs:documentation>
<xs:documentation
source="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/abstract_modules.html#s_nameidentmodule"/>
</xs:annotation>
<xs:attributeGroup name="xhtml.a.name.attlist">
<xs:attribute name="name" type="xh11d:CDATA"/>
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.map.name.attlist">
<xs:attribute name="name" type="xh11d:CDATA"/>
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.applet.name.attlist">
<xs:attribute name="name" type="xh11d:CDATA"/>
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.frame.name.attlist">
<xs:attribute name="name" type="xh11d:CDATA"/>
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.iframe.name.attlist">
<xs:attribute name="name" type="xh11d:CDATA"/>
</xs:attributeGroup>
</xs:schema>
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/xhtml-legacy-1.xsd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/xhtml-legacy-1.xsd
.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
xmlns:xh11d="http://www.w3.org/1999/xhtml/datatypes/"
>
<xs:import namespace="http://www.w3.org/1999/xhtml/datatypes/"
schemaLocation="xhtml-datatypes-1.xsd" />
<xs:annotation>
<xs:documentation>
This is the XML Schema Module for HTML Legacy Markup
font, basefont, center, s, strike, u,
dir, menu, isindex
(plus additional datatypes and legacy attributes)
This optional module declares additional markup for simple
presentation-related markup based on features found in the
HTML 4 Transitional and Frameset DTDs.
The legacy module also include frames module, iframe module
and target module. (Note: This module expects find the schema files
of that declare these module)
Elements/Attributes defined in frame, iframe and target modules are
* frameset, frame, noframes, att:target, iframe
$Id: xhtml-legacy-1.xsd,v 1.3 2009/09/30 15:29:49 ahby Exp $
</xs:documentation>
<xs:documentation source="xhtml-copyright-1.xsd"/>
<xs:documentation
source="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/abstract_modules.html#s_legacymodule"/>
<xs:documentation
source="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/abstract_modules.html#s_framesmodule"/>
<xs:documentation
source="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/abstract_modules.html#s_targetmodule"/>
<xs:documentation
source="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/abstract_modules.html#s_iframemodule"/>
</xs:annotation>
<xs:include schemaLocation="xhtml-misc-1.xsd">
<xs:annotation>
<xs:documentation>
Miscellaneous module
Attributes defined here:
* font, basefont, center, s, strike, u, dir, menu, isindex
(plus additional datatypes and attributes)
</xs:documentation>
</xs:annotation>
</xs:include>
<xs:include schemaLocation="xhtml-frames-1.xsd">
<xs:annotation>
<xs:documentation>
Frames module
Elements defined here:
* frameset, frame, noframes
</xs:documentation>
<xs:documentation
source="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/abstract_modules.html#s_framesmodule"/>
</xs:annotation>
</xs:include>
<xs:include schemaLocation="xhtml-target-1.xsd">
<xs:annotation>
<xs:documentation>
Target module
Attributes defined here:
* target
</xs:documentation>
<xs:documentation
source="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/abstract_modules.html#s_targetmodule"/>
</xs:annotation>
</xs:include>
<xs:include schemaLocation="xhtml-iframe-1.xsd">
<xs:annotation>
<xs:documentation>
Iframe module
Elements defined here:
* iframe
</xs:documentation>
<xs:documentation
source="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/abstract_modules.html#s_iframemodule"/>
</xs:annotation>
</xs:include>
</xs:schema>
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/xhtml-ruby-1.xsd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/xhtml-ruby-1.xsd
.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
xmlns:xh11d="http://www.w3.org/1999/xhtml/datatypes/">
<xs:import
namespace="http://www.w3.org/1999/xhtml/datatypes/"
schemaLocation="xhtml-datatypes-1.xsd"/>
<xs:annotation>
<xs:documentation>
This is the Ruby module for XHTML
$Id: xhtml-ruby-1.xsd,v 1.7 2010/05/02 17:22:08 ahby Exp $
</xs:documentation>
<xs:documentation source="xhtml-copyright-1.xsd"/>
</xs:annotation>
<xs:annotation>
<xs:documentation>
"Ruby" are short runs of text alongside the base text, typically
used in East Asian documents to indicate pronunciation or to
provide a short annotation. The full specification for Ruby is here:
http://www.w3.org/TR/2001/REC-ruby-20010531/
This module defines "Ruby " or "complex Ruby" as described
in the specification:
http://www.w3.org/TR/2001/REC-ruby-20010531/#complex
Simple or Basic Ruby are defined in a separate module.
This module declares the elements and their attributes used to
support complex ruby annotation markup. Elements defined here
* ruby, rbc, rtc, rb, rt, rp
This module expects the document model to define the
following content models
+ InlNoRuby.mix
</xs:documentation>
<xs:documentation
source="http://www.w3.org/TR/2001/REC-ruby-20010531/"/>
</xs:annotation>
<xs:group name="xhtml.ruby.content.simple">
<xs:sequence>
<xs:element name="rb" type="xhtml.rb.type"/>
<xs:choice>
<xs:element name="rt" type="xhtml.rt.type"/>
<xs:sequence>
<xs:element name="rp" type="xhtml.rp.type"/>
<xs:element name="rt" type="xhtml.rt.type"/>
<xs:element name="rp" type="xhtml.rp.type"/>
</xs:sequence>
</xs:choice>
</xs:sequence>
</xs:group>
<xs:group name="xhtml.ruby.content.complex">
<xs:sequence>
<xs:element name="rbc" type="xhtml.rbc.type"/>
<xs:element name="rtc" type="xhtml.rtc.type" maxOccurs="2"/>
</xs:sequence>
</xs:group>
<!--
add to this group any common attributes for all Ruby elements
-->
<xs:attributeGroup name="xhtml.ruby.common.attrib"/>
<xs:group name="xhtml.ruby.content">
<xs:choice>
<xs:group ref="xhtml.ruby.content.simple"/>
<xs:group ref="xhtml.ruby.content.complex"/>
</xs:choice>
</xs:group>
<xs:complexType name="xhtml.ruby.type">
<xs:group ref="xhtml.ruby.content"/>
<xs:attributeGroup ref="xhtml.ruby.common.attrib"/>
</xs:complexType>
<!--
rbc (ruby base component) element
-->
<xs:attributeGroup name="xhtml.rbc.attlist">
<xs:attributeGroup ref="xhtml.ruby.common.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.rbc.content">
<xs:sequence>
<xs:element name="rb" type="xhtml.rb.type" />
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.rbc.type">
<xs:group ref="xhtml.rbc.content"/>
<xs:attributeGroup ref="xhtml.rbc.attlist"/>
</xs:complexType>
<!--
rtc (ruby text component) element
-->
<xs:attributeGroup name="xhtml.rtc.attlist">
<xs:attributeGroup ref="xhtml.ruby.common.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.rtc.content">
<xs:sequence>
<xs:element name="rt" type="xhtml.rt.type" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.rtc.type">
<xs:group ref="xhtml.rt.content"/>
<xs:attributeGroup ref="xhtml.rtc.attlist"/>
</xs:complexType>
<!--
rb (ruby base) element
-->
<xs:attributeGroup name="xhtml.rb.attlist">
<xs:attributeGroup ref="xhtml.ruby.common.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.rb.content">
<xs:sequence>
<xs:group ref="xhtml.InlNoRuby.mix" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.rb.type" mixed="true">
<xs:group ref="xhtml.rb.content"/>
<xs:attributeGroup ref="xhtml.rb.attlist"/>
</xs:complexType>
<!--
rt (ruby text) element
-->
<xs:attributeGroup name="xhtml.rt.attlist">
<xs:attributeGroup ref="xhtml.ruby.common.attrib"/>
<xs:attribute name="rbspan" type="xh11d:Number" default="1"/>
</xs:attributeGroup>
<xs:group name="xhtml.rt.content">
<xs:sequence>
<xs:group ref="xhtml.InlNoRuby.mix" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.rt.type" mixed="true">
<xs:group ref="xhtml.rt.content"/>
<xs:attributeGroup ref="xhtml.rt.attlist"/>
</xs:complexType>
<!-- rp (ruby parenthesis) element -->
<xs:attributeGroup name="xhtml.rp.attlist">
<xs:attributeGroup ref="xhtml.ruby.common.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.rp.content">
<xs:sequence/>
</xs:group>
<xs:complexType name="xhtml.rp.type" mixed="true">
<xs:group ref="xhtml.rp.content"/>
<xs:attributeGroup ref="xhtml.rp.attlist"/>
</xs:complexType>
</xs:schema>
The
modules
in
this
section
are
elements
of
the
XHTML
Schema
implementation
that,
while
hidden
from
casual
users,
are
important
to
understand
when
creating
derivative
markup
languages
using
the
Modularization
architecture.
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/xhtml-blkphras-1.xsd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/xhtml-blkphras-1.xsd
.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
xmlns:xh11d="http://www.w3.org/1999/xhtml/datatypes/"
>
<xs:import namespace="http://www.w3.org/1999/xhtml/datatypes/" schemaLocation="xhtml-datatypes-1.xsd" />
<xs:include schemaLocation="xhtml-attribs-1.xsd" />
<xs:annotation>
<xs:documentation>
This is the XML Schema Block Phrasal support module for XHTML
$Id: xhtml-blkphras-1.xsd,v 1.7 2008/07/05 04:11:00 ahby Exp $
</xs:documentation>
<xs:documentation source="xhtml-copyright-1.xsd"/>
</xs:annotation>
<xs:annotation>
<xs:documentation>
Block Phrasal
This module declares the elements and their attributes used to
support block-level phrasal markup.
This is the XML Schema block phrasal elements module for XHTML
* address, blockquote, pre, h1, h2, h3, h4, h5, h6
</xs:documentation>
<xs:documentation source="http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_textmodule"/>
</xs:annotation>
<xs:import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2001/xml.xsd">
<xs:annotation>
<xs:documentation>
This import brings in the XML namespace attributes
The module itself does not provide the schemaLocation
and expects the driver schema to provide the
actual SchemaLocation.
</xs:documentation>
</xs:annotation>
</xs:import>
<!-- address -->
<xs:attributeGroup name="xhtml.address.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.address.content">
<xs:sequence>
<xs:group ref="xhtml.Inline.mix" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.address.type" mixed="true">
<xs:group ref="xhtml.address.content"/>
<xs:attributeGroup ref="xhtml.address.attlist"/>
</xs:complexType>
<!-- blockquote -->
<xs:attributeGroup name="xhtml.blockquote.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
<xs:attribute name="cite" type="xh11d:URI"/>
</xs:attributeGroup>
<xs:group name="xhtml.blockquote.content">
<xs:sequence>
<xs:group ref="xhtml.Block.mix" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.blockquote.type">
<xs:group ref="xhtml.blockquote.content"/>
<xs:attributeGroup ref="xhtml.blockquote.attlist"/>
</xs:complexType>
<!-- pre -->
<xs:attributeGroup name="xhtml.pre.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.pre.content">
<xs:sequence>
<xs:group ref="xhtml.InlinePre.mix" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.pre.type" mixed="true">
<xs:group ref="xhtml.pre.content"/>
<xs:attributeGroup ref="xhtml.pre.attlist"/>
</xs:complexType>
<!-- Heading Elements -->
<xs:attributeGroup name="xhtml.heading.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
</xs:attributeGroup>
<xs:complexType name="xhtml.heading.type" mixed="true">
<xs:group ref="xhtml.Inline.mix" minOccurs="0" maxOccurs="unbounded"/>
<xs:attributeGroup ref="xhtml.heading.attlist"/>
</xs:complexType>
<xs:attributeGroup name="xhtml.h1.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.h1.content">
<xs:sequence>
<xs:group ref="xhtml.Inline.mix" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.h1.type" mixed="true">
<xs:group ref="xhtml.h1.content"/>
<xs:attributeGroup ref="xhtml.h1.attlist"/>
</xs:complexType>
<xs:attributeGroup name="xhtml.h2.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.h2.content">
<xs:sequence>
<xs:group ref="xhtml.Inline.mix" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.h2.type" mixed="true">
<xs:group ref="xhtml.h2.content"/>
<xs:attributeGroup ref="xhtml.h2.attlist"/>
</xs:complexType>
<xs:attributeGroup name="xhtml.h3.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.h3.content">
<xs:sequence>
<xs:group ref="xhtml.Inline.mix" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.h3.type" mixed="true">
<xs:group ref="xhtml.h3.content"/>
<xs:attributeGroup ref="xhtml.h3.attlist"/>
</xs:complexType>
<xs:attributeGroup name="xhtml.h4.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.h4.content">
<xs:sequence>
<xs:group ref="xhtml.Inline.mix" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.h4.type" mixed="true">
<xs:group ref="xhtml.h4.content"/>
<xs:attributeGroup ref="xhtml.h4.attlist"/>
</xs:complexType>
<xs:attributeGroup name="xhtml.h5.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.h5.content">
<xs:sequence>
<xs:group ref="xhtml.Inline.mix" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.h5.type" mixed="true">
<xs:group ref="xhtml.h5.content"/>
<xs:attributeGroup ref="xhtml.h5.attlist"/>
</xs:complexType>
<xs:attributeGroup name="xhtml.h6.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.h6.content">
<xs:sequence>
<xs:group ref="xhtml.Inline.mix" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.h6.type" mixed="true">
<xs:group ref="xhtml.h6.content"/>
<xs:attributeGroup ref="xhtml.h6.attlist"/>
</xs:complexType>
</xs:schema>
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/xhtml-blkpres-1.xsd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/xhtml-blkpres-1.xsd
.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
xmlns:xh11d="http://www.w3.org/1999/xhtml/datatypes/"
>
<xs:import namespace="http://www.w3.org/1999/xhtml/datatypes/"
schemaLocation="xhtml-datatypes-1.xsd" />
<xs:annotation>
<xs:documentation>
This is the XML SchemaBlock presentation element module for XHTML
$Id: xhtml-blkpres-1.xsd,v 1.2 2005/09/26 22:54:53 ahby Exp $
</xs:documentation>
</xs:annotation>
<xs:annotation>
<xs:documentation>
Block Presentational Elements
* hr
This module declares the elements and their attributes used to
support block-level presentational markup.
</xs:documentation>
<xs:documentation source="xhtml-copyright-1.xsd"/>
<xs:documentation source="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/abstract_modules.html#s_presentationmodule"/>
</xs:annotation>
<xs:attributeGroup name="xhtml.hr.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.hr.content">
<xs:sequence/>
</xs:group>
<xs:complexType name="xhtml.hr.type">
<xs:group ref="xhtml.hr.content"/>
<xs:attributeGroup ref="xhtml.hr.attlist"/>
</xs:complexType>
</xs:schema>
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/xhtml-blkstruct-1.xsd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/xhtml-blkstruct-1.xsd
.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
xmlns:xh11d="http://www.w3.org/1999/xhtml/datatypes/"
>
<xs:import namespace="http://www.w3.org/1999/xhtml/datatypes/"
schemaLocation="xhtml-datatypes-1.xsd" />
<xs:annotation>
<xs:documentation>
Block Structural
* div, p
This module declares the elements and their attributes used to
support block-level structural markup.
This is the XML Schema Block Structural module for XHTML
$Id: xhtml-blkstruct-1.xsd,v 1.3 2005/09/26 22:54:53 ahby Exp $
</xs:documentation>
<xs:documentation source="xhtml-copyright-1.xsd"/>
</xs:annotation>
<!-- div -->
<xs:attributeGroup name="xhtml.div.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.div.content">
<xs:sequence>
<xs:group ref="xhtml.Flow.mix" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.div.type" mixed="true">
<xs:group ref="xhtml.div.content"/>
<xs:attributeGroup ref="xhtml.div.attlist"/>
</xs:complexType>
<!-- p -->
<xs:attributeGroup name="xhtml.p.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.p.content">
<xs:sequence>
<xs:group ref="xhtml.Inline.mix" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.p.type" mixed="true">
<xs:group ref="xhtml.p.content"/>
<xs:attributeGroup ref="xhtml.p.attlist"/>
</xs:complexType>
</xs:schema>
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/xhtml-inlphras-1.xsd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/xhtml-inlphras-1.xsd
.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
xmlns:xh11d="http://www.w3.org/1999/xhtml/datatypes/"
>
<xs:import namespace="http://www.w3.org/1999/xhtml/datatypes/"
schemaLocation="xhtml-datatypes-1.xsd" />
<xs:annotation>
<xs:documentation>
This is the XML Schema Inline Phrasal support module for XHTML
$Id: xhtml-inlphras-1.xsd,v 1.4 2005/09/26 22:54:53 ahby Exp $
</xs:documentation>
<xs:documentation source="xhtml-copyright-1.xsd"/>
</xs:annotation>
<xs:annotation>
<xs:documentation>
Inline Phrasal.
This module declares the elements and their attributes used to
support inline-level phrasal markup.
This is the XML Schema Inline Phrasal module for XHTML
* abbr, acronym, cite, code, dfn, em, kbd, q, samp, strong, var
$Id: xhtml-inlphras-1.xsd,v 1.4 2005/09/26 22:54:53 ahby Exp $
</xs:documentation>
<xs:documentation source="http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_textmodule"/>
</xs:annotation>
<xs:attributeGroup name="xhtml.abbr.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.abbr.content">
<xs:sequence>
<xs:group ref="xhtml.Inline.mix" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.abbr.type" mixed="true">
<xs:group ref="xhtml.abbr.content"/>
<xs:attributeGroup ref="xhtml.abbr.attlist"/>
</xs:complexType>
<xs:attributeGroup name="xhtml.acronym.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.acronym.content">
<xs:sequence>
<xs:group ref="xhtml.Inline.mix" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.acronym.type" mixed="true">
<xs:group ref="xhtml.acronym.content"/>
<xs:attributeGroup ref="xhtml.acronym.attlist"/>
</xs:complexType>
<xs:attributeGroup name="xhtml.cite.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.cite.content">
<xs:sequence>
<xs:group ref="xhtml.Inline.mix" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.cite.type" mixed="true">
<xs:group ref="xhtml.cite.content"/>
<xs:attributeGroup ref="xhtml.cite.attlist"/>
</xs:complexType>
<xs:attributeGroup name="xhtml.code.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.code.content">
<xs:sequence>
<xs:group ref="xhtml.Inline.mix" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.code.type" mixed="true">
<xs:group ref="xhtml.code.content"/>
<xs:attributeGroup ref="xhtml.code.attlist"/>
</xs:complexType>
<xs:attributeGroup name="xhtml.dfn.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.dfn.content">
<xs:sequence>
<xs:group ref="xhtml.Inline.mix" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.dfn.type" mixed="true">
<xs:group ref="xhtml.dfn.content"/>
<xs:attributeGroup ref="xhtml.dfn.attlist"/>
</xs:complexType>
<xs:attributeGroup name="xhtml.em.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.em.content">
<xs:sequence>
<xs:group ref="xhtml.Inline.mix" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.em.type" mixed="true">
<xs:group ref="xhtml.em.content"/>
<xs:attributeGroup ref="xhtml.em.attlist"/>
</xs:complexType>
<xs:attributeGroup name="xhtml.kbd.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.kbd.content">
<xs:sequence>
<xs:group ref="xhtml.Inline.mix" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.kbd.type" mixed="true">
<xs:group ref="xhtml.kbd.content"/>
<xs:attributeGroup ref="xhtml.kbd.attlist"/>
</xs:complexType>
<xs:attributeGroup name="xhtml.samp.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.samp.content">
<xs:sequence>
<xs:group ref="xhtml.Inline.mix" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.samp.type" mixed="true">
<xs:group ref="xhtml.samp.content"/>
<xs:attributeGroup ref="xhtml.samp.attlist"/>
</xs:complexType>
<xs:attributeGroup name="xhtml.strong.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.strong.content">
<xs:sequence>
<xs:group ref="xhtml.Inline.mix" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.strong.type" mixed="true">
<xs:group ref="xhtml.strong.content"/>
<xs:attributeGroup ref="xhtml.strong.attlist"/>
</xs:complexType>
<xs:attributeGroup name="xhtml.var.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.var.content">
<xs:sequence>
<xs:group ref="xhtml.Inline.mix" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.var.type" mixed="true">
<xs:group ref="xhtml.var.content"/>
<xs:attributeGroup ref="xhtml.var.attlist"/>
</xs:complexType>
<xs:attributeGroup name="xhtml.q.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
<xs:attribute name="cite" type="xh11d:URI"/>
</xs:attributeGroup>
<xs:group name="xhtml.q.content">
<xs:sequence>
<xs:group ref="xhtml.Inline.mix" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.q.type" mixed="true">
<xs:group ref="xhtml.q.content"/>
<xs:attributeGroup ref="xhtml.q.attlist"/>
</xs:complexType>
</xs:schema>
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/xhtml-inlpres-1.xsd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/xhtml-inlpres-1.xsd
.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
xmlns:xh11d="http://www.w3.org/1999/xhtml/datatypes/"
>
<xs:import namespace="http://www.w3.org/1999/xhtml/datatypes/"
schemaLocation="xhtml-datatypes-1.xsd" />
<xs:annotation>
<xs:documentation>
This is the XML Schema Inline Presentation element module for XHTML
$Id: xhtml-inlpres-1.xsd,v 1.2 2005/09/26 22:54:53 ahby Exp $
</xs:documentation>
<xs:documentation source="xhtml-copyright-1.xsd"/>
</xs:annotation>
<xs:annotation>
<xs:documentation>
Inline Presentational Elements
* b, big, i, small, sub, sup, tt
This module declares the elements and their attributes used to
support inline-level presentational markup.
</xs:documentation>
<xs:documentation source="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/abstract_modules.html#s_presentationmodule"/>
</xs:annotation>
<xs:attributeGroup name="xhtml.InlPres.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.InlPres.content">
<xs:sequence>
<xs:group ref="xhtml.Inline.mix" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.InlPres.type" mixed="true">
<xs:group ref="xhtml.InlPres.content"/>
<xs:attributeGroup ref="xhtml.InlPres.attlist"/>
</xs:complexType>
</xs:schema>
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/xhtml-inlstruct-1.xsd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/xhtml-inlstruct-1.xsd
.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
xmlns:xh11d="http://www.w3.org/1999/xhtml/datatypes/"
>
<xs:import namespace="http://www.w3.org/1999/xhtml/datatypes/"
schemaLocation="xhtml-datatypes-1.xsd" />
<xs:annotation>
<xs:documentation>
This is the XML Schema Inline Structural support module for XHTML
$Id: xhtml-inlstruct-1.xsd,v 1.4 2005/09/26 22:54:53 ahby Exp $
</xs:documentation>
<xs:documentation source="xhtml-copyright-1.xsd"/>
</xs:annotation>
<xs:annotation>
<xs:documentation>
Inline Structural.
This module declares the elements and their attributes
used to support inline-level structural markup.
This is the XML Schema Inline Structural element module for XHTML
* br, span
</xs:documentation>
<xs:documentation source="http://www.w3.org/TR/xhtml-modularization/abstract_modules.html#s_textmodule"/>
</xs:annotation>
<xs:attributeGroup name="xhtml.br.attlist">
<xs:attributeGroup ref="xhtml.Core.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.br.content">
<xs:sequence/>
</xs:group>
<xs:complexType name="xhtml.br.type">
<xs:group ref="xhtml.br.content"/>
<xs:attributeGroup ref="xhtml.br.attlist"/>
</xs:complexType>
<xs:attributeGroup name="xhtml.span.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.span.content">
<xs:sequence>
<xs:group ref="xhtml.Inline.mix" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.span.type" mixed="true">
<xs:group ref="xhtml.span.content"/>
<xs:attributeGroup ref="xhtml.span.attlist"/>
</xs:complexType>
</xs:schema>
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/xhtml-param-1.xsd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/xhtml-param-1.xsd
.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
xmlns:xh11d="http://www.w3.org/1999/xhtml/datatypes/"
>
<xs:import namespace="http://www.w3.org/1999/xhtml/datatypes/"
schemaLocation="xhtml-datatypes-1.xsd" />
<xs:annotation>
<xs:documentation>
This is the XML Schema Param Element module for XHTML
$Id: xhtml-param-1.xsd,v 1.3 2005/09/26 22:54:53 ahby Exp $
</xs:documentation>
<xs:documentation source="xhtml-copyright-1.xsd"/>
</xs:annotation>
<xs:annotation>
<xs:documentation>
Parameters for Java Applets and Embedded Objects
* param
This module provides declarations for the param element,
used to provide named property values for the applet
and object elements.
</xs:documentation>
<xs:documentation source="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/abstract_modules.html#s_objectmodule"/>
<xs:documentation source="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/abstract_modules.html#s_appletmodule"/>
</xs:annotation>
<xs:attributeGroup name="xhtml.param.attlist">
<xs:attributeGroup ref="xhtml.id"/>
<xs:attribute name="name" type="xh11d:CDATA" use="required"/>
<xs:attribute name="value" type="xh11d:CDATA"/>
<xs:attribute name="valuetype" default="data">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="data"/>
<xs:enumeration value="ref"/>
<xs:enumeration value="object"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="type" type="xh11d:ContentType"/>
</xs:attributeGroup>
<xs:group name="xhtml.param.content">
<xs:sequence/>
</xs:group>
<xs:complexType name="xhtml.param.type">
<xs:group ref="xhtml.param.content"/>
<xs:attributeGroup ref="xhtml.param.attlist"/>
</xs:complexType>
</xs:schema>
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/SCHEMA/xhtml-misc-1.xsd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/SCHEMA/xhtml-misc-1.xsd
.
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
xmlns:xh11d="http://www.w3.org/1999/xhtml/datatypes/"
>
<xs:import namespace="http://www.w3.org/1999/xhtml/datatypes/"
schemaLocation="xhtml-datatypes-1.xsd" />
<xs:annotation>
<xs:documentation>
This is the XML Schema Miscellaneous Legacy
Markup module for XHTML
$Id: xhtml-misc-1.xsd,v 1.2 2005/09/26 22:54:53 ahby Exp $
</xs:documentation>
<xs:documentation source="xhtml-copyright-1.xsd"/>
</xs:annotation>
<xs:annotation>
<xs:documentation>
XHTML Miscellaneous Legacy Markup
font, basefont, center, s, strike, u,
dir, menu, isindex
This is to allow XHTML documents to be transformed for
display on HTML browsers where CSS support is inconsistent
or unavailable.
The module also declares legacy attributes for elements
in other module. Note: This module only declares the
attribute list, and it is up to the document type to
redefine the model of affected modules.
</xs:documentation>
<xs:documentation
source="http://www.w3.org/TR/2001/REC-xhtml-modularization-20010410/abstract_modules.html#s_legacymodule"/>
</xs:annotation>
<xs:attributeGroup name="xhtml.font.attlist">
<xs:attributeGroup ref="xhtml.Core.attrib"/>
<xs:attributeGroup ref="xhtml.I18n.attrib"/>
<xs:attribute name="size" type="xh11d:CDATA"/>
<xs:attribute name="color" type="xh11d:Color"/>
<xs:attribute name="face" type="xh11d:CDATA"/>
</xs:attributeGroup>
<xs:group name="xhtml.font.content">
<xs:sequence>
<xs:group ref="xhtml.Inline.mix" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.font.type" mixed="true">
<xs:group ref="xhtml.font.content"/>
<xs:attributeGroup ref="xhtml.font.attlist"/>
</xs:complexType>
<xs:attributeGroup name="xhtml.basefont.attlist">
<xs:attributeGroup ref="xhtml.id"/>
<xs:attribute name="size" type="xh11d:CDATA" use="required"/>
<xs:attribute name="color" type="xh11d:Color"/>
<xs:attribute name="face" type="xh11d:CDATA"/>
</xs:attributeGroup>
<xs:group name="xhtml.basefont.content">
<xs:sequence/>
</xs:group>
<xs:complexType name="xhtml.basefont.type">
<xs:group ref="xhtml.basefont.content"/>
<xs:attributeGroup ref="xhtml.basefont.attlist"/>
</xs:complexType>
<xs:attributeGroup name="xhtml.center.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.center.content">
<xs:sequence>
<xs:group ref="xhtml.Flow.mix" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.center.type" mixed="true">
<xs:group ref="xhtml.center.content"/>
<xs:attributeGroup ref="xhtml.center.attlist"/>
</xs:complexType>
<xs:attributeGroup name="xhtml.s.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.s.content">
<xs:sequence>
<xs:group ref="xhtml.Inline.mix" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.s.type" mixed="true">
<xs:group ref="xhtml.s.content"/>
<xs:attributeGroup ref="xhtml.s.attlist"/>
</xs:complexType>
<xs:attributeGroup name="xhtml.strike.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.strike.content">
<xs:sequence>
<xs:group ref="xhtml.Inline.mix" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.strike.type" mixed="true">
<xs:group ref="xhtml.strike.content"/>
<xs:attributeGroup ref="xhtml.strike.attlist"/>
</xs:complexType>
<xs:attributeGroup name="xhtml.u.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
</xs:attributeGroup>
<xs:group name="xhtml.u.content">
<xs:sequence>
<xs:group ref="xhtml.Inline.mix" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.u.type" mixed="true">
<xs:group ref="xhtml.u.content"/>
<xs:attributeGroup ref="xhtml.u.attlist"/>
</xs:complexType>
<xs:attributeGroup name="xhtml.dir.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
<xs:attribute name="compact">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="compact"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:attributeGroup>
<xs:group name="xhtml.dir.content">
<xs:sequence>
<xs:element ref="li" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.dir.type" mixed="true">
<xs:group ref="xhtml.dir.content"/>
<xs:attributeGroup ref="xhtml.dir.attlist"/>
</xs:complexType>
<xs:attributeGroup name="xhtml.menu.attlist">
<xs:attributeGroup ref="xhtml.Common.attrib"/>
<xs:attribute name="compact">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="compact"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:attributeGroup>
<xs:group name="xhtml.menu.content">
<xs:sequence>
<xs:element ref="li" maxOccurs="unbounded"/>
</xs:sequence>
</xs:group>
<xs:complexType name="xhtml.menu.type" mixed="true">
<xs:group ref="xhtml.menu.content"/>
<xs:attributeGroup ref="xhtml.menu.attlist"/>
</xs:complexType>
<xs:attributeGroup name="xhtml.isindex.attlist">
<xs:attributeGroup ref="xhtml.Core.attrib"/>
<xs:attributeGroup ref="xhtml.I18n.attrib"/>
<xs:attribute name="prompt" type="xh11d:Text"/>
</xs:attributeGroup>
<xs:group name="xhtml.isindex.content">
<xs:sequence/>
</xs:group>
<xs:complexType name="xhtml.isindex.type">
<xs:group ref="xhtml.isindex.content"/>
<xs:attributeGroup ref="xhtml.isindex.attlist"/>
</xs:complexType>
<xs:annotation>
<xs:documentation>
Attribute redefinitions
</xs:documentation>
</xs:annotation>
<xs:attributeGroup name="xhtml.align.legacy.attlist">
<xs:attribute name="align">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="left"/>
<xs:enumeration value="center"/>
<xs:enumeration value="right"/>
<xs:enumeration value="justify"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:attributeGroup>
<!-- add 'target' attribute to 'a' element -->
<xs:attributeGroup name="xhtml.a.legacy.attlist">
<xs:attribute name="target" type="xh11d:FrameTarget"/>
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.applet.legacy.attlist">
<xs:attribute name="align">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="top"/>
<xs:enumeration value="middle"/>
<xs:enumeration value="bottom"/>
<xs:enumeration value="left"/>
<xs:enumeration value="right"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="hspace" type="xh11d:Pixels"/>
<xs:attribute name="vspace" type="xh11d:Pixels"/>
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.body.legacy.attlist">
<xs:attribute name="background" type="xh11d:URI"/>
<xs:attribute name="bgcolor" type="xh11d:Color"/>
<xs:attribute name="text" type="xh11d:Color"/>
<xs:attribute name="link" type="xh11d:Color"/>
<xs:attribute name="vlinke" type="xh11d:Color"/>
<xs:attribute name="alink" type="xh11d:Color"/>
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.br.legacy.attlist">
<xs:attribute name="clear" default="none">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="left"/>
<xs:enumeration value="all"/>
<xs:enumeration value="right"/>
<xs:enumeration value="none"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.caption.legacy.attlist">
<xs:attributeGroup ref="xhtml.align.legacy.attlist"/>
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.hr.legacy.attlist">
<xs:attribute name="align">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="left"/>
<xs:enumeration value="center"/>
<xs:enumeration value="right"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="noshade">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="noshade"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="size" type="xh11d:Pixels"/>
<xs:attribute name="width" type="xh11d:Length"/>
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.img.legacy.attlist">
<xs:attribute name="align">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="top"/>
<xs:enumeration value="middle"/>
<xs:enumeration value="bottom"/>
<xs:enumeration value="left"/>
<xs:enumeration value="right"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="border" type="xh11d:Pixels"/>
<xs:attribute name="hspace" type="xh11d:Pixels"/>
<xs:attribute name="vspace" type="xh11d:Pixels"/>
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.input.legacy.attlist">
<xs:attribute name="align">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="top"/>
<xs:enumeration value="middle"/>
<xs:enumeration value="bottom"/>
<xs:enumeration value="left"/>
<xs:enumeration value="right"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.legend.legacy.attlist">
<xs:attribute name="align">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="top"/>
<xs:enumeration value="bottom"/>
<xs:enumeration value="left"/>
<xs:enumeration value="right"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.li.legacy.attlist">
<xs:attribute name="type" type="xh11d:CDATA"/>
<xs:attribute name="value" type="xh11d:Number"/>
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.object.legacy.attlist">
<xs:attribute name="align">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="top"/>
<xs:enumeration value="middle"/>
<xs:enumeration value="bottom"/>
<xs:enumeration value="left"/>
<xs:enumeration value="right"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="border" type="xh11d:Pixels"/>
<xs:attribute name="hspace" type="xh11d:Pixels"/>
<xs:attribute name="vspace" type="xh11d:Pixels"/>
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.ol.legacy.attlist">
<xs:attribute name="type" type="xh11d:Text"/>
<xs:attribute name="compact">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="compact"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="start" type="xh11d:Number"/>
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.dl.legacy.attlist">
<xs:attribute name="compact">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="compact"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.div.legacy.attlist">
<xs:attributeGroup ref="xhtml.align.legacy.attlist"/>
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.heading.legacy.attlist">
<xs:attributeGroup ref="xhtml.align.legacy.attlist"/>
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.p.legacy.attlist">
<xs:attributeGroup ref="xhtml.align.legacy.attlist"/>
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.pre.legacy.attlist">
<xs:attribute name="width" type="xh11d:Length"/>
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.script.legacy.attlist">
<xs:attribute name="language" type="xh11d:ContentType"/>
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.table.legacy.attlist">
<xs:attribute name="align">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="left"/>
<xs:enumeration value="center"/>
<xs:enumeration value="right"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="bgcolor" type="xh11d:Color"/>
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.tr.legacy.attlist">
<xs:attribute name="bgcolor" type="xh11d:Color"/>
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.th.legacy.attlist">
<xs:attribute name="nowrap">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="nowrap"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="bgcolor" type="xh11d:Color"/>
<xs:attribute name="width" type="xh11d:Length"/>
<xs:attribute name="height" type="xh11d:Length"/>
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.td.legacy.attlist">
<xs:attribute name="nowrap">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="nowrap"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="bgcolor" type="xh11d:Color"/>
<xs:attribute name="width" type="xh11d:Length"/>
<xs:attribute name="height" type="xh11d:Length"/>
</xs:attributeGroup>
<xs:attributeGroup name="xhtml.ul.legacy.attlist">
<xs:attribute name="type" type="xh11d:CDATA"/>
<xs:attribute name="compact">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="compact"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:attributeGroup>
</xs:schema>
D.
Building
DTD
Modules
This
section
is
normative.
XHTML
modules
are
implemented
as
DTD
fragments.
When
these
fragments
are
assembled
in
a
specific
manner
(described
in
Developing
DTDs
with
defined
and
extended
modules
),
the
resulting
DTD
is
a
representation
of
a
complete
document
type.
This
representation
can
then
be
used
for
validation
of
instances
of
the
document
type.
The
key
to
combining
these
fragments
into
a
meaningful
DTD
is
the
rules
used
to
define
the
fragments.
This
section
defines
those
rules.
When
these
rules
are
followed,
DTD
authors
can
be
confident
that
their
modules
will
interface
cleanly
with
other
XHTML-compatible
modules.
Modules
conforming
to
these
rules
also
need
to
satisfy
the
conformance
requirements
defined
in
XHTML
Family
Module
Conformance
in
order
to
be
called
XHTML
Family
Modules
.
D.1.
Parameter
Entity
Naming
This
specification
classifies
parameter
entities
into
seven
categories
and
names
them
consistently
using
the
following
suffixes:
-
.mod
-
parameter
entities
use
the
suffix
.mod
when
they
are
used
to
represent
a
DTD
module
(a
collection
of
elements,
attributes,
parameter
entities,
etc).
In
this
specification,
each
module
is
an
atomic
unit
and
may
be
represented
as
a
separate
file
entity.
-
.module
-
parameter
entities
use
the
suffix
.module
when
they
are
used
to
control
the
inclusion
of
a
DTD
module
by
containing
either
of
the
conditional
section
keywords
INCLUDE
or
IGNORE
.
-
.qname
-
parameter
entities
use
the
suffix
.qname
when
they
are
used
to
represent
the
qualified
name
of
an
element.
See
Defining
the
Namespace
of
a
Module
for
more
information
on
qualified
names.
-
.content
-
parameter
entities
use
the
suffix
.content
when
they
are
used
to
represent
the
content
model
of
an
element
type.
-
.class
-
parameter
entities
use
the
suffix
.class
when
they
are
used
to
represent
elements
of
the
same
class.
-
.mix
-
parameter
entities
use
the
suffix
.mix
when
they
are
used
to
represent
a
collection
of
element
types
from
different
classes.
-
.attrib
-
parameter
entities
use
the
suffix
.attrib
when
they
are
used
to
represent
a
group
of
tokens
representing
one
or
more
complete
attribute
specifications
within
an
ATTLIST
declaration.
For
example,
in
HTML
4,
the
%block;
parameter
entity
is
defined
to
represent
the
heterogeneous
collection
of
element
types
that
are
block-level
elements.
In
this
specification,
the
corollary
parameter
entity
is
%Block.mix;
.
When
defining
parameter
entities
in
the
classes
defined
here,
modules
should
scope
the
names
of
the
entities
by
using
unique
prefixes.
For
example,
the
content
model
for
the
element
myelement
in
the
module
mymodule
could
be
named
MYMODULE.myelement.content
.
Other
schemes
are
possible.
Regardless
of
the
scheme
used,
module
authors
should
strive
to
ensure
that
parameter
entities
they
define
are
named
uniquely
so
that
they
do
not
collide
with
other
parameter
entities
and
so
that
the
interface
methods
for
the
module
are
obvious
to
its
users.
D.2.
Defining
the
Namespace
of
a
Module
XHTML
requires
that
the
elements
and
attributes
declared
in
a
module
be
within
a
defined
XML
namespace
[XMLNAMES]
.
The
identification
of
this
namespace
is
an
arbitrary
URI.
XHTML
requires
that
when
a
module
is
implemented
using
an
XML
DTD,
the
module
declares
the
namespace
in
a
special
manner.
The
purpose
of
this
is
to
permit
the
selection,
at
document
parse/validation
time,
of
the
use
of
namespace
prefixes
and
of
the
prefix
that
is
used
to
identify
elements
and
attributes
from
the
module.
Content
developers
who
wish
to
develop
documents
based
upon
hybrid
document
types
may
choose
to
use
XML
namespace
prefixes
on
elements
from
the
XHTML
namespace,
on
elements
from
other
namespaces,
or
on
both.
In
order
to
ensure
that
such
documents
are
XHTML
conforming
and
backward
compatible
with
non-namespace
aware
tools,
the
W3C
recommends
that
content
developers
do
not
use
XML
namespace
prefixes
on
elements
from
the
XHTML
namespace.
When
content
developers
are
interested
in
having
their
content
processed
by
namespace-aware
processors,
the
W3C
further
recommends
that
elements
in
non-XHTML
namespaces
be
specified
using
an
XML
namespace
prefix
rather
than
relying
upon
XML
namespace
defaulting
mechanisms.
Each
XHTML-conforming
module
implemented
as
an
XML
DTD
is
required
to
define
a
default
XML
namespace
prefix,
a
method
for
changing
this
prefix
within
a
document
instance,
and
a
marked
section
that
turns
on
the
processing
of
the
prefix.
Note
that
it
is
legal
and
expected
for
multiple
modules
to
be
part
of
the
same
namespace
when
they
are
related.
All
of
the
XHTML
modules,
for
example,
are
part
of
the
same
namespace.
D.2.1.
Qualified
Names
sub-module
First,
you
need
to
define
a
qualified
names
sub-module
(a
sub-module
is
just
a
file
entity
that
is
separated
so
that
it
can
be
incorporated
into
the
ultimate
DTD
at
the
appropriate
point).
The
qualified
names
sub-module
is
built
using
the
following
steps
(where
the
string
MODULE
is
replaced
with
an
appropriate
string
for
the
new
module):
-
Define
a
parameter
entity
MODULE.prefixed
that
announces
whether
the
elements
in
the
module
are
being
used
with
XML
namespace
prefixed
names
or
not.
This
parameter
entity's
default
value
should
be
"%NS.prefixed;".
The
NS.prefixed
parameter
entity
is
defined
by
the
XHTML
framework
to
be
IGNORE
by
default,
and
can
be
used
in
a
document
instance
to
switch
on
prefixing
for
all
included
namespaces
(including
that
of
the
XHTML
modules).
-
Define
a
parameter
entity
MODULE.xmlns
that
contains
the
namespace
identifier
for
this
module.
-
Define
a
parameter
entity
MODULE.prefix
that
contains
the
default
prefix
string
to
use
when
prefixing
is
enabled.
-
Define
a
parameter
entity
MODULE.pfx
that
is
"%MODULE.prefix;:"
when
prefixing
is
enabled,
and
""
when
it
is
not.
-
Define
a
parameter
entity
MODULE.xmlns.extra.attrib
that
contains
the
declaration
of
any
XML
namespace
attributes
for
namespaces
referenced
by
this
module
(e.g.,
xmlns:xlink).
When
%MODULE.prefixed
is
set
to
INCLUDE,
this
attribute
should
include
the
xmlns:%MODULE.prefix;
declaration
as
well.
-
Define
a
parameter
entity
XHTML.xmlns.extra.attrib
as
MODULE.xmlns.extra.attrib.
This
is
usually
overridden
by
the
document
type's
driver
file,
but
if
not
this
definition
will
take
over
as
the
default.
-
For
each
of
the
elements
defined
by
the
module,
create
a
parameter
entity
of
the
form
"MODULE.NAME.qname"
to
hold
its
qualified
name.
The
value
for
this
parameter
entity
must
be
"%MODULE.pfx;NAME".
In
this
way,
the
parsed
value
will
be
"PREFIX:NAME"
when
prefixes
are
enabled,
and
"NAME"
otherwise.
If
the
module
adds
attributes
to
elements
defined
in
modules
that
do
not
share
the
namespace
of
this
module,
declare
those
attributes
so
that
they
use
the
%MODULE.pfx
prefix.
For
example:
<ENTITY % MODULE.img.myattr.qname "%MODULE.pfx;myattr" >
An
example
of
a
qname
sub-module
for
a
hypothetical
Inventory
Module
is
included
below:
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/examples/inventory-qname-1.mod
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/examples/inventory-qname-1.mod
.
<!-- ...................................................................... -->
<!-- Inventory Qname Module ................................................... -->
<!-- file: inventory-qname-1.mod
PUBLIC "-//MY COMPANY//ELEMENTS XHTML Inventory Qnames 1.0//EN"
SYSTEM "http://www.example.com/DTDs/inventory-qname-1.mod"
xmlns:inventory="http://www.example.com/xmlns/inventory"
...................................................................... -->
<!-- Declare the default value for prefixing of this module's elements -->
<!-- Note that the NS.prefixed will get overridden by the XHTML Framework or
by a document instance. -->
<!ENTITY % NS.prefixed "IGNORE" >
<!ENTITY % Inventory.prefixed "%NS.prefixed;" >
<!-- Declare the actual namespace of this module -->
<!ENTITY % Inventory.xmlns "http://www.example.com/xmlns/inventory" >
<!-- Declare the default prefix for this module -->
<!ENTITY % Inventory.prefix "inventory" >
<!-- Declare the prefix for this module -->
<![%Inventory.prefixed;[
<!ENTITY % Inventory.pfx "%Inventory.prefix;:" >
]]>
<!ENTITY % Inventory.pfx "" >
<!-- Declare the xml namespace attribute for this module -->
<![%Inventory.prefixed;[
<!ENTITY % Inventory.xmlns.extra.attrib
"xmlns:%Inventory.prefix; %URI.datatype; #FIXED '%Inventory.xmlns;'" >
]]>
<!ENTITY % Inventory.xmlns.extra.attrib "" >
<!-- Declare the extra namespace that should be included in the XHTML
elements -->
<!ENTITY % XHTML.xmlns.extra.attrib
"%Inventory.xmlns.extra.attrib;" >
<!-- Now declare the qualified names for all of the elements in the
module -->
<!ENTITY % Inventory.shelf.qname "%Inventory.pfx;shelf" >
<!ENTITY % Inventory.item.qname "%Inventory.pfx;item" >
<!ENTITY % Inventory.desc.qname "%Inventory.pfx;desc" >
<!ENTITY % Inventory.sku.qname "%Inventory.pfx;sku" >
<!ENTITY % Inventory.price.qname "%Inventory.pfx;price" >
D.2.2.
Declaration
sub-module(s)
Next,
you
need
to
define
one
or
more
"declaration
sub-modules".
The
purpose
of
these
file
entities
is
to
declare
the
XML
DTD
elements
and
attribute
lists.
An
XHTML
declaration
module
should
be
constructed
using
the
following
process:
-
Define
a
parameter
entity
to
use
within
the
ATTLIST
of
each
declared
element.
This
parameter
entity
should
contain
%NS.decl.attrib;
when
%MODULE.prefixed;
is
set
to
INCLUDE,
and
%NS.decl.attrib;
plus
"xmlns
%URI.datatype;
#FIXED
'%MODULE.xmlns;'"
when
%MODULE.prefixed;
is
set
to
IGNORE.
-
Declare
all
of
the
elements
and
attributes
for
the
module.
Within
each
ATTLIST
for
an
element,
include
the
parameter
entity
defined
above
so
that
all
of
the
required
xmlns
attributes
are
available
on
each
element
in
the
module.
-
If
the
module
adds
attributes
to
elements
defined
in
modules
that
do
not
share
the
namespace
of
this
module,
declare
those
attributes
so
that
they
use
the
%MODULE.pfx
prefix.
For
example:
<ENTITY % MODULE.img.myattr.qname "%MODULE.pfx;myattr" >
<!ATTLIST %img.qname;
%MODULE.img.myattr.qname; CDATA #IMPLIED
>
This
would
add
an
attribute
to
the
img
element
of
the
Image
Module,
but
the
attribute's
name
will
be
the
qualified
name,
including
prefix,
when
prefixes
are
selected
for
a
document
instance.
It
also
adds
the
xmlns:MODULE_PREFIX
attribute
to
the
img
element's
attribute
list
so
that
an
XML
Namespace-aware
parser
would
know
how
to
resolve
the
namespace
based
upon
its
prefix.
The
following
example
shows
a
declaration
sub-module
for
a
hypothetical
Inventory
module.
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/examples/inventory-1.mod
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/examples/inventory-1.mod
.
<!-- ...................................................................... -->
<!-- Inventory Elements Module ................................................... -->
<!-- file: inventory-1.mod
PUBLIC "-//MY COMPANY//ELEMENTS XHTML Inventory Elements 1.0//EN"
SYSTEM "http://www.example.com/DTDs/inventory-1.mod"
xmlns:inventory="http://www.example.com/xmlns/inventory"
...................................................................... -->
<!-- Inventory Module
shelf
item
sku
desc
price
This module defines a simple inventory item structure
-->
<!-- Define the global namespace attributes -->
<![%Inventory.prefixed;[
<!ENTITY % Inventory.xmlns.attrib
"%NS.decl.attrib;"
>
]]>
<!ENTITY % Inventory.xmlns.attrib
"%NS.decl.attrib;
xmlns %URI.datatype; #FIXED '%Inventory.xmlns;'"
>
<!-- Define a common set of attributes for all module elements -->
<!ENTITY % Inventory.Common.attrib
"%Inventory.xmlns.attrib;
id ID #IMPLIED"
>
<!-- Define the elements and attributes of the module -->
<!ELEMENT %Inventory.shelf.qname;
( %Inventory.item.qname; )* >
<!ATTLIST %Inventory.shelf.qname;
location CDATA #IMPLIED
%Inventory.Common.attrib;
>
<!ELEMENT %Inventory.item.qname;
( %Inventory.desc.qname;, %Inventory.sku.qname;, %Inventory.price.qname;) >
<!ATTLIST %Inventory.item.qname;
location CDATA #IMPLIED
%Inventory.Common.attrib;
>
<!ELEMENT %Inventory.desc.qname; ( #PCDATA ) >
<!ATTLIST %Inventory.desc.qname;
%Inventory.Common.attrib;
>
<!ELEMENT %Inventory.sku.qname; ( #PCDATA ) >
<!ATTLIST %Inventory.sku.qname;
%Inventory.Common.attrib;
>
<!ELEMENT %Inventory.price.qname; ( #PCDATA ) >
<!ATTLIST %Inventory.price.qname;
%Inventory.Common.attrib;
>
<!-- end of inventory-1.mod -->
D.2.3.
Using
the
module
as
a
stand-alone
DTD
It
is
sometimes
desirable
to
have
an
XHTML
module
also
usable
as
a
stand
alone
DTD.
A
good
example
of
this
is
our
Inventory
module
above.
These
items
need
to
be
embeddable
in
an
XHTML
document,
and
also
need
to
be
available
as
free-standing
documents
extracted
from
a
database
(for
example).
The
easiest
way
to
accomplish
this
is
to
define
a
DTD
file
that
instantiates
the
components
of
your
module.
Such
a
DTD
would
have
this
structure:
-
Include
the
XHTML
Datatypes
Module
(your
qnames
module
likely
uses
some
of
these
datatypes
-
it
certainly
uses
the
URI
datatype
for
the
xmlns
attribute).
-
Include
the
Qnames
Module
for
your
module.
-
Define
the
parameter
entity
NS.decl.attrib
to
be
%MODULE.xmlns.extra.attrib;.
-
Include
the
Declaration
Module(s)
for
your
module.
An
example
of
this
for
our
Inventory
module
is
included
below:
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/examples/inventory-1.dtd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/examples/inventory-1.dtd
.
<!-- ...................................................................... -->
<!-- Inventory Elements DTD ............................................... -->
<!-- file: inventory-1.dtd
PUBLIC "-//MY COMPANY//DTD XHTML Inventory 1.0//EN"
SYSTEM "http://www.example.com/DTDs/inventory-1.dtd"
xmlns:inventory="http://www.example.com/xmlns/inventory"
...................................................................... -->
<!-- Inventory Module
shelf
item
sku
desc
price
This module defines a simple inventory item structure
-->
<!-- Bring in the datatypes -->
<!ENTITY % xhtml-datatypes.mod
PUBLIC "-//W3C//ENTITIES XHTML Datatypes 1.0//EN"
"http://www.w3.org/MarkUp/DTD/xhtml-datatypes-1.mod" >
%xhtml-datatypes.mod;
<!-- Bring in the qualified names -->
<!ENTITY % Inventory-qname.mod SYSTEM "inventory-qname-1.mod" >
%Inventory-qname.mod;
<!ENTITY % NS.decl.attrib "%Inventory.xmlns.extra.attrib;">
<!ENTITY % Inventory.mod SYSTEM "inventory-1.mod" >
%Inventory.mod;
<!-- end of inventory-1.dtd -->
This
DTD
can
then
be
referenced
by
documents
that
use
only
the
elements
from
your
module:
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/examples/inventory.xml
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/examples/inventory.xml
.
<!DOCTYPE shelf SYSTEM "inventory-1.dtd">
<shelf xmlns="http://www.example.com/xmlns/inventory">
<item>
<desc>
this is a description.
</desc>
<sku>
this is the price.
</sku>
<price>
this is the price.
</price>
</item>
</shelf>
This
method
permits
the
definition
of
elements
and
attributes
that
are
scoped
within
their
own
namespace.
It
also
permits
content
developers
to
use
the
default
prefix
for
the
elements
and
attributes:
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/examples/inventory-prefixed.xml
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/examples/inventory-prefixed.xml
.
<!DOCTYPE inventory:shelf SYSTEM "inventory-1.dtd" [
<!ENTITY % Inventory.prefixed "INCLUDE">
]>
<inventory:shelf xmlns:inventory="http://www.example.com/xmlns/inventory">
<inventory:item>
<inventory:desc>
this is a description.
</inventory:desc>
<inventory:sku>
this is the sku.
</inventory:sku>
<inventory:price>
this is the price.
</inventory:price>
</inventory:item>
</inventory:shelf>
Finally,
a
document
instance
can
use
a
different
XML
namespace
prefix
by
redeclaring
it
in
the
DOCTYPE
header
and
its
internal
subset:
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/examples/inventory-newprefix.xml
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/examples/inventory-newprefix.xml
.
<!DOCTYPE i:shelf SYSTEM "inventory-1.dtd" [
<!ENTITY % Inventory.prefixed "INCLUDE">
<!ENTITY % Inventory.prefix "i">
]>
<i:shelf xmlns:i="http://www.example.com/xmlns/inventory">
<i:item>
<i:desc>
this is a description.
</i:desc>
<i:sku>
this is the price.
</i:sku>
<i:price>
this is the price.
</i:price>
</i:item>
</i:shelf>
D.2.4.
Namespace
Idiosyncrasies
While
the
approach
defined
here
permits
the
definition
of
markup
languages
that
are
XML
and
XML
namespaces
conforming,
some
behaviors
defined
by
the
XML
namespaces
specification
are
not
supported:
-
XML
namespaces
permit
the
redeclaration
of
the
xmlns
attribute
for
a
namespace
at
any
point
in
the
tree.
It
further
permits
this
redeclaration
to
switch
between
namespace
defaulting
and
prefixed
usage,
and
permits
the
changing
of
the
prefix.
The
method
defined
in
this
document
does
not
permit
this.
Throughout
a
document
instance
a
given
namespace
must
continue
to
use
the
same
namespace
prefix
(when
prefixing
is
used),
or
must
continue
to
be
used
in
the
default
scope.
-
When
using
XML
namespace
defaulting,
it
is
legal
to
rely
upon
the
DTD
of
the
document
to
inform
parsers
of
the
namespace
of
elements.
However,
since
namespace
aware
processors
are
not
required
to
include
the
DTD
when
evaluating
a
document,
content
developers
should
declare
the
XML
namespace
of
an
element
whenever
the
namespace
changes:
...
<p>
<myelement xmlns="..." />
</p>
E.
Developing
DTDs
with
defined
and
extended
modules
This
section
is
informative
.
The
primary
purpose
of
defining
XHTML
modules
and
a
general
modularization
methodology
is
to
ease
the
development
of
document
types
that
are
based
upon
XHTML.
These
document
types
may
extend
XHTML
by
integrating
additional
capabilities
(e.g.,
[SMIL]
),
or
they
may
define
a
subset
of
XHTML
for
use
in
a
specialized
device.
This
section
describes
the
techniques
that
document
type
designers
must
use
in
order
to
take
advantage
of
the
XML
DTD
implementation
of
this
modularization
architecture.
It
does
this
by
applying
the
XHTML
Modularization
techniques
in
progressively
more
complex
ways,
culminating
in
the
creation
of
a
complete
document
type
from
disparate
modules.
Note
that
in
no
case
do
these
examples
require
the
modification
of
the
XHTML-provided
module
file
entities
themselves.
The
XHTML
module
file
entities
are
completely
parameterized,
so
that
it
is
possible
through
separate
module
definitions
and
driver
files
to
customize
the
definition
and
the
content
model
of
each
element
and
each
element's
hierarchy.
Finally,
remember
that
most
users
of
XHTML
are
not
expected
to
be
DTD
authors.
DTD
authors
are
generally
people
who
are
defining
specialized
markup
that
will
improve
the
readability,
simplify
the
rendering
of
a
document,
or
ease
machine-processing
of
documents,
or
they
are
client
designers
that
need
to
define
the
specialized
DTD
for
their
specific
client.
Consider
these
cases:
-
An
organization
is
providing
subscriber's
information
via
a
Web
interface.
The
organization
stores
its
subscriber
information
in
an
XML-based
database.
One
way
to
report
that
information
out
from
the
database
to
the
Web
is
to
embed
the
XML
records
from
the
database
directly
in
the
XHTML
document.
While
it
is
possible
to
merely
embed
the
records,
the
organization
could
define
a
DTD
module
that
describes
the
records,
attach
that
module
to
an
XHTML
DTD,
and
thereby
create
a
complete
DTD
for
the
pages.
The
organization
can
then
access
the
data
within
the
new
elements
via
the
Document
Object
Model
[DOM]
,
validate
the
documents,
provide
style
definitions
for
the
elements
that
cascade
using
Cascading
Style
Sheets
[CSS2]
,
etc.
By
taking
the
time
to
define
the
structure
of
their
data
and
create
a
DTD
using
the
processes
defined
in
this
section,
the
organization
can
realize
the
full
benefits
of
XML.
-
An
Internet
client
developer
is
designing
a
specialized
device.
That
device
will
only
support
a
subset
of
XHTML,
and
the
devices
will
always
access
the
Internet
via
a
proxy
server
that
validates
content
before
passing
it
on
to
the
client
(to
minimize
error
handling
on
the
client).
In
order
to
ensure
that
the
content
is
valid,
the
developer
creates
a
DTD
that
is
a
subset
of
XHTML
using
the
processes
defined
in
this
section.
They
then
use
the
new
DTD
in
their
proxy
server
and
in
their
devices,
and
also
make
the
DTD
available
to
content
developers
so
that
developers
can
validate
their
content
before
making
it
available.
By
performing
a
few
simple
steps,
the
client
developer
can
use
the
architecture
defined
in
this
document
to
greatly
ease
their
DTD
development
cost
and
ensure
that
they
are
fully
supporting
the
subset
of
XHTML
that
they
choose
to
include.
E.1.
Defining
additional
attributes
In
some
cases,
an
extension
to
XHTML
can
be
as
simple
as
additional
attributes.
Attributes
can
be
added
to
an
element
just
by
specifying
an
additional
ATTLIST
for
the
element,
for
example:
<!ATTLIST %a.qname;
%MyModule.pfx;myattr CDATA #IMPLIED
%MyModule.xmlns.extras.attrib;
>
would
add
the
"myattr"
attribute,
with
an
optional
prefix
defined
by
"%MyModule.pfx",
with
a
value
type
of
CDATA,
to
the
"a"
element.
This
works
because
XML
permits
the
definition
or
extension
of
the
attribute
list
for
an
element
at
any
point
in
a
DTD.
For
a
discussion
of
qualified
names
and
namespace
prefixes,
see
Defining
the
Namespace
of
a
Module
.
Naturally,
adding
an
attribute
to
a
DTD
does
not
mean
that
any
new
behavior
is
defined
for
arbitrary
clients.
However,
a
content
developer
could
use
an
extra
attribute
to
store
information
that
is
accessed
by
associated
scripts
via
the
Document
Object
Model
(for
example).
E.2.
Defining
additional
elements
Defining
additional
elements
is
only
slightly
more
complicated
than
defining
additional
attributes.
Basically,
DTD
authors
should
write
the
element
declaration
for
each
element:
<!-- In the qname sub-module -->
<!ENTITY % MyModule.myelement.qname "%MyModule.pfx;myelement" >
<!ENTITY % MyModule.myotherelement.qname "%MyModule.pfx;myotherelement" >
<!-- In the declaration sub-module -->
<!ELEMENT %MyModule.myelement.qname;
( #PCDATA | %MyModule.myotherelement.qname; )* >
<!ATTLIST %MyModule.myelement.qname;
myattribute CDATA #IMPLIED
>
<!ELEMENT %MyModule.myotherelement.qname; EMPTY >
After
the
elements
are
defined,
they
need
to
be
integrated
into
the
content
model.
Strategies
for
integrating
new
elements
or
sets
of
elements
into
the
content
model
are
addressed
in
the
next
section.
E.3.
Defining
the
content
model
for
a
collection
of
modules
Since
the
content
model
of
XHTML
modules
is
fully
parameterized,
DTD
authors
may
modify
the
content
model
for
every
element
in
every
module.
The
details
of
the
DTD
module
interface
are
defined
in
Building
DTD
Modules
.
Basically
there
are
two
ways
to
approach
this
modification:
-
Re-define
the
".content"
parameter
entity
for
each
element.
-
Re-define
one
or
more
of
the
global
content
model
entities
(normally
via
the
".extras"
parameter
entity).
The
strategy
taken
will
depend
upon
the
nature
of
the
modules
being
combined
and
the
nature
of
the
elements
being
integrated.
The
remainder
of
this
section
describes
techniques
for
integrating
two
different
classes
of
modules.
E.3.1.
Integrating
a
stand-alone
module
into
XHTML
When
a
module
(and
remember,
a
module
can
be
a
collection
of
other
modules)
contains
elements
that
only
reference
each
other
in
their
content
model,
it
is
said
to
be
"internally
complete".
As
such,
the
module
can
be
used
on
its
own;
(for
example,
you
could
define
a
DTD
that
was
just
that
module,
and
use
one
of
its
elements
as
the
root
element).
Integrating
such
a
module
into
XHTML
is
a
three
step
process:
-
Decide
what
element(s)
can
be
thought
of
as
the
root(s)
of
the
new
module.
-
Decide
where
these
elements
need
to
attach
in
the
XHTML
content
tree.
-
Then,
for
each
attachment
point
in
the
content
tree,
add
the
root
element(s)
to
the
content
definition
for
the
XHTML
elements.
Consider
attaching
the
elements
defined
above
.
In
that
example,
the
element
myelement
is
the
root.
To
attach
this
element
under
the
img
element,
and
only
the
img
element,
of
XHTML,
the
following
would
work:
<!ENTITY % img.content "( %MyModule.myelement.qname; )*">
A
DTD
defined
with
this
content
model
would
allow
a
document
like
the
following
fragment:
<img src="...">
<myml:myelement >This is content of a locally defined element</myml:myelement>
</img>
It
is
important
to
note
that
normally
the
img
element
has
a
content
model
of
EMPTY
.
By
adding
myelement
to
that
content
model,
we
are
really
just
replacing
EMPTY
with
myelement
.
In
the
case
of
other
elements
that
already
have
content
models
defined,
the
addition
of
an
element
would
require
the
restating
of
the
existing
content
model
in
addition
to
myelement
.
E.3.2.
Mixing
a
new
module
throughout
the
modules
in
XHTML
Extending
the
example
above,
to
attach
this
module
everywhere
that
the
%Flow.mix
content
model
group
is
permitted,
would
require
something
like
the
following:
<!ENTITY % Misc.extra
"| %MyModule.myelement.qname;" >
Since
the
%Misc.extra
content
model
class
is
used
in
the
%Misc.class
parameter
entity,
and
that
parameter
entity
is
used
throughout
the
XHTML
modules,
the
new
module
would
become
available
throughout
an
extended
XHTML
document
type.
E.4.
Creating
a
new
DTD
So
far
the
examples
in
this
section
have
described
the
methods
of
extending
XHTML
and
XHTML's
content
model.
Once
this
is
done,
the
next
step
is
to
collect
the
modules
that
comprise
the
DTD
into
a
single
DTD
driver,
incorporating
the
new
definitions
so
that
they
override
and
augment
the
basic
XHTML
definitions
as
appropriate.
E.4.1.
Creating
a
simple
DTD
Using
the
trivial
example
above,
it
is
possible
to
define
a
new
DTD
that
uses
and
extends
the
XHTML
modules
pretty
easily.
First,
define
the
new
elements
and
their
content
model
in
a
module:
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/examples/simpleml-model-1.mod
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/examples/simpleml-model-1.mod
.
<!-- File: simpleml-model-1.mod -->
<!-- Declare a Parameter Entity (PE) that defines any external namespaces
that are used by this module -->
<!-- Set the PE that is used in every ATTLIST in this module
NS.prefixed.attrib is initialized in the xhtml-qname module, and
SimpleML.ns.noprefix.attrib is initialized in the SimpleML DTD driver
file.-->
<!ENTITY % SimpleML.xmlns.attrib
"%NS.decl.attrib;"
>
<!ENTITY % SimpleML.Common.attrib
"%SimpleML.xmlns.attrib;
id ID #IMPLIED"
>
<!ENTITY % SimpleML.element.qname "%SimpleML.pfx;element" >
<!ENTITY % SimpleML.otherelement.qname "%SimpleML.pfx;otherelement" >
<!ELEMENT %SimpleML.element.qname;
( #PCDATA | %SimpleML.otherelement.qname; )* >
<!ATTLIST %SimpleML.element.qname;
myattribute CDATA #IMPLIED
%SimpleML.Common.attrib;
>
<!ELEMENT %SimpleML.otherelement.qname; EMPTY >
<!ATTLIST %SimpleML.otherelement.qname;
%SimpleML.Common.attrib;
>
<!ENTITY % SimpleML.img.myattr.qname "%SimpleML.pfx;myattr" >
<!ATTLIST %img.qname;
%SimpleML.img.myattr.qname; CDATA #IMPLIED
>
<!-- Add our elements to the XHTML content model -->
<!ENTITY % Misc.class
"| %SimpleML.element.qname;" >
<!-- Now bring in the XHTML Basic content model -->
<!ENTITY % xhtml-basic-model.mod
PUBLIC "-//W3C//ENTITIES XHTML Basic 1.0 Document Model 1.0//EN"
"http://www.w3.org/TR/xhtml-basic/xhtml-basic10-model-1.mod" >
%xhtml-basic-model.mod;
Next,
define
the
DTD
driver
for
the
new
language:
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/examples/simpleml-1_0.dtd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/examples/simpleml-1_0.dtd
.
<!-- file: simpleml-1_0.dtd -->
<!-- Bring in the XHTML datatypes -->
<!ENTITY % xhtml-datatypes.mod
PUBLIC "-//W3C//ENTITIES XHTML Datatypes 1.0//EN"
"http://www.w3.org/MarkUp/DTD/xhtml-datatypes-1.mod" >
%xhtml-datatypes.mod;
<!-- Declare the actual namespace of this module -->
<!ENTITY % SimpleML.xmlns "http://www.example.com/xmlns/simpleml1" >
<!-- By default, disable prefixing of new module -->
<!ENTITY % NS.prefixed "IGNORE" >
<!ENTITY % SimpleML.prefixed "%NS.prefixed;" >
<!-- Default prefix for module elements and attributes -->
<!ENTITY % SimpleML.prefix "simpleml" >
<!-- If this module's namespace is prefixed -->
<![%SimpleML.prefixed;[
<!ENTITY % SimpleML.pfx "%SimpleML.prefix;:" >
]]>
<!ENTITY % SimpleML.pfx "" >
<![%SimpleML.prefixed;[
<!ENTITY % SimpleML.xmlns.extra.attrib
"xmlns:%SimpleML.prefix; %URI.datatype; #FIXED '%SimpleML.xmlns;'" >
]]>
<!ENTITY % SimpleML.xmlns.extra.attrib "" >
<!ENTITY % XHTML.xmlns.extra.attrib
"%SimpleML.xmlns.extra.attrib;"
>
<!-- Set the content model for our language -->
<!ENTITY % xhtml-model.mod
SYSTEM "simpleml-model-1.mod" >
<!-- Instantiate xhtml basic's DTD to do all the work -->
<!ENTITY % xhtml-basic.dtd
PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd" >
%xhtml-basic.dtd;
When
using
this
DTD,
it
is
possible
to
enable
the
use
of
XML
namespace
prefixes.
When
so
doing,
the
start
of
a
document
using
this
new
DTD
might
look
like:
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/examples/simple-prefixed.html
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/examples/simple-prefixed.html
.
<!DOCTYPE html SYSTEM "simpleml-1_0.dtd" [
<!ENTITY % SimpleML.prefixed "INCLUDE">
]>
<html xmlns="http://www.w3.org/1999/xhtml"
xmlns:simpleml="http://www.example.com/xmlns/simpleml1" >
<head>
<title>An example using defaults</title>
</head>
<body>
<p>This is content in the XHTML namespace</p>
<simpleml:element>
This is content in the SimpleML namespace.
<simpleml:otherelement />
</simpleml:element>
<p><img src="missing" alt="Missing image" simpleml:myattr="value"/></p>
</body>
</html>
E.4.2.
Creating
a
DTD
by
extending
XHTML
Next,
there
is
the
situation
where
a
complete,
additional,
and
complex
module
is
added
to
XHTML
(or
to
a
subset
of
XHTML).
In
essence,
this
is
the
same
as
in
the
trivial
example
above,
the
only
difference
being
that
the
module
being
added
is
incorporated
in
the
DTD
by
reference
rather
than
explicitly
including
the
new
definitions
in
the
DTD.
One
such
complex
module
is
the
DTD
for
[MATHML]
.
In
order
to
combine
MathML
and
XHTML
into
a
single
DTD,
an
author
would
just
decide
where
MathML
content
should
be
legal
in
the
document,
and
add
the
MathML
root
element
to
the
content
model
at
that
point.
First,
define
a
content
model
module
that
instantiates
the
MathML
DTD
and
connects
it
to
the
content
model:
<!-- File: mathml-model.mod -->
<!ENTITY % XHTML1-math
PUBLIC "-//W3C//DTD MathML 2.0//EN"
"http://www.w3.org/TR/MathML2/dtd/mathml2.dtd" >
%XHTML1-math;
<!ENTITY % Inlspecial.extra
"%a.qname; | %img.qname; | %object.qname; | %map.qname;
| %Mathml.Math.qname;" >
Next,
define
a
DTD
driver
that
identifies
our
new
content
model
module
as
the
content
model
for
the
DTD,
and
hands
off
processing
to
the
XHTML
1.1
driver
(for
example):
<!-- File: xhtml-mathml.dtd -->
<!ENTITY % xhtml-model.mod
SYSTEM "mathml-model.mod" >
<!ENTITY % xhtml11.dtd
PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd" >
%xhtml11.dtd;
E.4.3.
Creating
a
DTD
by
removing
and
replacing
XHTML
modules
Another
way
in
which
DTD
authors
may
use
XHTML
modules
is
to
define
a
DTD
that
is
a
subset
of
an
XHTML
family
document
type
(because,
for
example,
they
are
building
devices
or
software
that
only
supports
a
subset
of
XHTML).
Doing
this
is
only
slightly
more
complex
than
the
previous
example.
The
basic
steps
to
follow
are:
-
Take
an
XHTML
family
DTD
as
the
basis
of
the
new
document
type
(we
will
use
XHTML
1.1).
-
Select
the
modules
to
remove
from
that
DTD.
-
Define
a
new
DTD
that
"IGNOREs"
the
modules.
-
Introduce
some
new
modules.
For
example,
consider
a
device
that
uses
XHTML
modules,
but
without
forms
or
tables.
The
DTD
for
such
a
device
would
look
like
this:
<!-- File: xhtml-simple.dtd -->
<!ENTITY % xhtml-form.module "IGNORE" >
<!ENTITY % xhtml-table.module "IGNORE" >
<!ENTITY % xhtml-table.module "IGNORE" >
<!-- Bring in the basic tables module -->
<!ENTITY % xhtml-basic-table.mod
PUBLIC "-//W3C//ELEMENTS XHTML Basic Tables 1.0//EN"
"http://www.w3.org/MarkUp/DTD/xhtml-basic-table-1.mod"
>
%xhtml-basic-table.mod;
<!ENTITY % xhtml11.mod
PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd" >
%xhtml11.mod;
Note
that
this
does
not
actually
modify
the
content
model
for
the
XHTML
1.1
DTD.
However,
since
XML
ignores
elements
in
content
models
that
are
not
defined,
the
form
and
table
elements
are
dropped
from
the
model
automatically.
E.4.4.
Creating
a
new
DTD
Finally,
some
DTD
authors
may
wish
to
start
from
scratch,
using
the
XHTML
Modularization
framework
as
a
toolkit
for
building
a
new
markup
language.
This
language
must
be
made
up
of
the
minimal,
required
modules
from
XHTML.
It
may
also
contain
other
XHTML-defined
modules
or
any
other
module
that
the
author
wishes
to
employ.
In
this
example,
we
will
take
the
XHTML
required
modules,
add
some
XHTML-defined
modules,
and
also
add
in
the
module
we
defined
above.
The
first
step
is
to
use
the
XHTML-provided
template
for
a
new
qualified
names
module,
modified
to
define
the
qualified
names
and
namespace
for
our
new
elements.
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/examples/myml-qname-1.mod
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/examples/myml-qname-1.mod
.
<!-- file: myml-qname-1.mod -->
<!-- Bring in the datatypes - we use the URI.datatype PE for declaring the
xmlns attributes. -->
<!ENTITY % MyML-datatypes.mod
PUBLIC "-//W3C//ENTITIES XHTML Datatypes 1.0//EN"
"http://www.w3.org/MarkUp/DTD/xhtml-datatypes-1.mod" >
%MyML-datatypes.mod;
<!-- By default, disable prefixing of this module -->
<!ENTITY % NS.prefixed "IGNORE" >
<!ENTITY % MyML.prefixed "%NS.prefixed;" >
<!-- Declare the actual namespace of this module -->
<!ENTITY % MyML.xmlns "http://www.example.com/xmlns/myml" >
<!-- Declare the default prefix for this module -->
<!ENTITY % MyML.prefix "myml" >
<!-- If this module's namespace is prefixed -->
<![%MyML.prefixed;[
<!ENTITY % MyML.pfx "%MyML.prefix;:" >
]]>
<!ENTITY % MyML.pfx "" >
<!-- This entity is ALWAYS prefixed, for use when adding our
attributes to an element in another namespace -->
<!ENTITY % MyML.xmlns.attrib.prefixed
"xmlns:%MyML.prefix; %URI.datatype; #FIXED '%MyML.xmlns;'"
>
<!-- Declare a Parameter Entity (PE) that defines any external namespaces
that are used by this module -->
<!ENTITY % MyML.xmlns.extra.attrib "" >
<!-- If we want to use xhtml namespace attributes on our elements, then
we need a prefix for them; default to xhtml. -->
<!ENTITY % XHTML.prefix "xhtml" >
<!-- Declare a PE that defines the xmlns attributes for use by MyML. -->
<![%MyML.prefixed;[
<!ENTITY % MyML.xmlns.attrib
"%MyML.xmlns.attrib.prefixed;
%MyML.xmlns.extra.attrib;"
>
<!-- Make sure that the MyML namespace attributes are included on the XHTML
attribute set -->
<!ENTITY % XHTML.xmlns.extra.attrib
"xmlns:%XHTML.prefix; %URI.datatype; #FIXED 'http://www.w3.org/1999/xhtml'
%MyML.xmlns.attrib;" >
]]>
<!-- if we are not prefixed, then our elements should have the default
namespace AND the prefixed namespace is added to the XHTML set
because our attributes can be referenced on those elements
-->
<!ENTITY % MyML.xmlns.attrib
"xmlns %URI.datatype; #FIXED '%MyML.xmlns;'
%MyML.xmlns.extra.attrib;"
>
<!ENTITY % XHTML.xmlns.extra.attrib
"xmlns:%XHTML.prefix; %URI.datatype; #FIXED 'http://www.w3.org/1999/xhtml'
%MyML.xmlns.attrib.prefixed;"
>
<!-- Now declare the element names -->
<!ENTITY % MyML.myelement.qname "%MyML.pfx;myelement" >
<!ENTITY % MyML.myotherelement.qname "%MyML.pfx;myotherelement" >
Next,
define
a
module
that
defines
the
elements
and
attributes
using
the
XHTML
provided
template
.
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/examples/myml-elements-1.mod
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/examples/myml-elements-1.mod
.
<!-- ...................................................................... -->
<!-- My Elements Module ................................................... -->
<!-- file: myml-elements-1_0.mod
PUBLIC "-//MY COMPANY//ELEMENTS XHTML MyML Elements 1.0//EN"
SYSTEM "http://example.com/DTDs/myml-elements-1_0.mod"
xmlns:myml="http://example.com/DTDs/myml-1_0.dtd"
...................................................................... -->
<!-- My Elements Module
myelement
myotherelement
This module has no purpose other than to provide structure for some
PCDATA content.
-->
<!ELEMENT %MyML.myelement.qname;
( #PCDATA | %MyML.myotherelement.qname; )* >
<!ATTLIST %MyML.myelement.qname;
myattribute CDATA #IMPLIED
%MyML.xmlns.attrib;
%XHTML.global.common.attrib;
>
<!ELEMENT %MyML.myotherelement.qname; EMPTY >
<!ATTLIST %MyML.myotherelement.qname;
%MyML.xmlns.attrib;
%XHTML.global.common.attrib;
>
<!ENTITY % MyML.img.myattr.qname "%MyML.prefix;:myattr" >
<!ATTLIST %img.qname;
%MyML.img.myattr.qname; CDATA #IMPLIED
%MyML.xmlns.attrib.prefixed;
>
<!-- end of myml-elements-1_0.mod -->
Now,
build
a
content
model
description
that
hooks
the
new
elements
and
attributes
into
the
other
XHTML
elements.
The
following
example
is
patterned
after
the
XHTML
Basic
content
model,
but
is
a
complete,
free-standing
content
model
module:
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/examples/myml-model-1.mod
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/examples/myml-model-1.mod
.
<!-- ...................................................................... -->
<!-- MyML Model Module ................................................... -->
<!-- file: myml-model-1.mod
PUBLIC "-//MY COMPANY//ELEMENTS XHTML MyML Model 1.0//EN"
SYSTEM "http://example.com/DTDs/myml-model-1_0.mod"
xmlns:myml="http://www.example.com/xmlns/myml"
...................................................................... -->
<!-- Define the content model for Misc.extra -->
<!ENTITY % Misc.class
"| %MyML.myelement.qname; ">
<!-- .................... Inline Elements ...................... -->
<!ENTITY % HeadOpts.mix
"( %meta.qname; )*" >
<!ENTITY % I18n.class "" >
<!ENTITY % InlStruct.class "%br.qname; | %span.qname;" >
<!ENTITY % InlPhras.class
"| %em.qname; | %strong.qname; | %dfn.qname; | %code.qname;
| %samp.qname; | %kbd.qname; | %var.qname; | %cite.qname;
| %abbr.qname; | %acronym.qname; | %q.qname;" >
<!ENTITY % InlPres.class
"" >
<!ENTITY % Anchor.class "| %a.qname;" >
<!ENTITY % InlSpecial.class "| %img.qname; " >
<!ENTITY % Inline.extra "" >
<!-- %Inline.class; includes all inline elements,
used as a component in mixes
-->
<!ENTITY % Inline.class
"%InlStruct.class;
%InlPhras.class;
%InlPres.class;
%Anchor.class;
%InlSpecial.class;"
>
<!-- %InlNoAnchor.class; includes all non-anchor inlines,
used as a component in mixes
-->
<!ENTITY % InlNoAnchor.class
"%InlStruct.class;
%InlPhras.class;
%InlPres.class;
%InlSpecial.class;"
>
<!-- %InlNoAnchor.mix; includes all non-anchor inlines
-->
<!ENTITY % InlNoAnchor.mix
"%InlNoAnchor.class;
%Misc.class;"
>
<!-- %Inline.mix; includes all inline elements, including %Misc.class;
-->
<!ENTITY % Inline.mix
"%Inline.class;
%Misc.class;"
>
<!-- ..................... Block Elements ...................... -->
<!ENTITY % Heading.class
"%h1.qname; | %h2.qname; | %h3.qname;
| %h4.qname; | %h5.qname; | %h6.qname;" >
<!ENTITY % List.class "%ul.qname; | %ol.qname; | %dl.qname;" >
<!ENTITY % BlkStruct.class "%p.qname; | %div.qname;" >
<!ENTITY % BlkPhras.class
"| %pre.qname; | %blockquote.qname; | %address.qname;" >
<!ENTITY % BlkPres.class "" >
<!ENTITY % Block.extra "" >
<!-- %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;"
>
<!-- special content model for pre element -->
<!ENTITY % pre.content
"( #PCDATA
| %Inline.class; )*"
>
<!-- end of myml-model-1.mod -->
Finally,
use
the
XHTML-provided
template
for
a
new
DTD,
modified
as
appropriate
for
our
new
markup
language:
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/examples/myml-1_0.dtd
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/examples/myml-1_0.dtd
.
<!-- ....................................................................... -->
<!-- MYML DTD ............................................................. -->
<!-- file: myml-1_0.dtd -->
<!-- This is the DTD driver for myml 1.0.
Please use this formal public identifier to identify it:
"-//MY COMPANY//DTD XHTML MYML 1.0//EN"
And this namespace for myml-unique elements:
xmlns:myml="http://www.example.com/xmlns/myml"
-->
<!ENTITY % XHTML.version "-//MY COMPANY//DTD XHTML MYML 1.0//EN" >
<!-- reserved for use with document profiles -->
<!ENTITY % XHTML.profile "" >
<!-- Tell the framework to use our qualified names module as an extra qname
driver -->
<!ENTITY % xhtml-qname-extra.mod
SYSTEM "myml-qname-1.mod" >
<!-- Define the Content Model for the framework to use -->
<!ENTITY % xhtml-model.mod
SYSTEM "myml-model-1.mod" >
<!-- Disable bidirectional text support -->
<!ENTITY % XHTML.bidi "IGNORE" >
<!-- Bring in the XHTML Framework -->
<!ENTITY % xhtml-framework.mod
PUBLIC "-//W3C//ENTITIES XHTML Modular Framework 1.0//EN"
"http://www.w3.org/MarkUp/DTD/xhtml-framework-1.mod" >
%xhtml-framework.mod;
<!-- Basic Text Module (Required) ............................... -->
<!ENTITY % xhtml-text.mod
PUBLIC "-//W3C//ELEMENTS XHTML Basic Text 1.0//EN"
"http://www.w3.org/MarkUp/DTD/xhtml-text-1.mod" >
%xhtml-text.mod;
<!-- Hypertext Module (required) ................................. -->
<!ENTITY % xhtml-hypertext.mod
PUBLIC "-//W3C//ELEMENTS XHTML Hypertext 1.0//EN"
"http://www.w3.org/MarkUp/DTD/xhtml-hypertext-1.mod" >
%xhtml-hypertext.mod;
<!-- Lists Module (required) .................................... -->
<!ENTITY % xhtml-list.mod
PUBLIC "-//W3C//ELEMENTS XHTML Lists 1.0//EN"
"http://www.w3.org/MarkUp/DTD/xhtml-list-1.mod" >
%xhtml-list.mod;
<!-- My Elements Module ........................................ -->
<!ENTITY % MyML-elements.mod
SYSTEM "myml-elements-1.mod" >
%MyML-elements.mod;
<!-- XHTML Images module ........................................ -->
<!ENTITY % xhtml-image.mod
PUBLIC "-//W3C//ELEMENTS XHTML Images 1.0//EN"
"http://www.w3.org/MarkUp/DTD/xhtml-image-1.mod" >
%xhtml-image.mod;
<!-- Document Metainformation Module ............................ -->
<!ENTITY % xhtml-meta.mod
PUBLIC "-//W3C//ELEMENTS XHTML Metainformation 1.0//EN"
"http://www.w3.org/MarkUp/DTD/xhtml-meta-1.mod" >
%xhtml-meta.mod;
<!-- Document Structure Module (required) ....................... -->
<!ENTITY % xhtml-struct.mod
PUBLIC "-//W3C//ELEMENTS XHTML Document Structure 1.0//EN"
"http://www.w3.org/MarkUp/DTD/xhtml-struct-1.mod" >
%xhtml-struct.mod;
E.5.
Using
the
new
DTD
Once
a
new
DTD
has
been
developed,
it
can
be
used
in
any
document.
Using
the
DTD
is
as
simple
as
just
referencing
it
in
the
DOCTYPE
declaration
of
a
document:
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/examples/myml-noprefix.xhtml
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/examples/myml-noprefix.xhtml
.
<!DOCTYPE html SYSTEM "myml-1_0.dtd" >
<html xmlns="http://www.w3.org/1999/xhtml"
xmlns:xhtml="http://www.w3.org/1999/xhtml"
xmlns:myml="http://www.example.com/xmlns/myml" >
<head>
<title>An example using defaults</title>
</head>
<body>
<p>This is content in the XHTML namespace</p>
<myelement xhtml:id="myid" xhtml:class="localElement">
This is content in the SimpleML namespace.
<myotherelement />
</myelement>
<p><img src="missing" alt="Missing image" myml:myattr="value"/></p>
</body>
</html>
The
document
can
also
use
the
elements
outside
of
the
XHTML
namespace
by
prefixing
them:
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/examples/myml-prefixed.xhtml
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/examples/myml-prefixed.xhtml
.
<!DOCTYPE html SYSTEM "myml-1_0.dtd" [
<!ENTITY % MyML.prefixed "INCLUDE" >
]>
<html xmlns="http://www.w3.org/1999/xhtml"
xmlns:xhtml="http://www.w3.org/1999/xhtml"
xmlns:myml="http://www.example.com/xmlns/myml" >
<head>
<title>An example using defaults</title>
</head>
<body>
<p>This is content in the XHTML namespace</p>
<myml:myelement xhtml:id="myid" xhtml:class="localElement">
This is content in the myml namespace.
<myml:myotherelement />
</myml:myelement>
<p><img src="missing" alt="Missing image" myml:myattr="value" /></p>
</body>
</html>
F.
XHTML
DTD
Module
Implementations
This
appendix
is
normative
.
This
appendix
contains
implementations
of
the
modules
defined
in
XHTML
Abstract
Modules
via
XML
DTDs.
These
module
implementations
can
be
used
by
XHTML
Family
Document
Types.
There
are
direct
links
to
the
various
files,
and
the
files
are
also
contained
in
the
"Gzip'd
TAR"
and
"Zip"
archives
linked
to
at
the
top
of
this
document.
Please
note
that
the
files
targeted
by
the
"latest
version"
links
may
change
slowly
over
time.
See
the
W3C
XHTML2
Working
Group
home
page
for
more
information.
F.1.
XHTML
Character
Entities
XHTML
DTDs
make
available
a
standard
collection
of
named
character
entities.
Those
entities
are
defined
in
this
section.
F.1.1.
XHTML
Latin
1
Character
Entities
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/xhtml-lat1.ent
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/xhtml-lat1.ent
.
<!-- ...................................................................... -->
<!-- XML-compatible ISO Latin 1 Character Entity Set for XHTML ............ -->
<!-- file: xhtml-lat1.ent
Typical invocation:
<!ENTITY % xhtml-lat1
PUBLIC "-//W3C//ENTITIES Latin 1 for XHTML//EN"
"xhtml-lat1.ent" >
%xhtml-lat1;
This DTD module is identified by the PUBLIC and SYSTEM identifiers:
PUBLIC "-//W3C//ENTITIES Latin 1 for XHTML//EN"
SYSTEM "http://www.w3.org/MarkUp/DTD/xhtml-lat1.ent"
Revision: $Id: xhtml-lat1.ent,v 4.1 2001/04/10 09:34:14 altheim Exp $ SMI
Portions (C) International Organization for Standardization 1986:
Permission to copy in any form is granted for use with conforming
SGML systems and applications as defined in ISO 8879, provided
this notice is included in all copies.
-->
<!ENTITY nbsp " " ><!-- no-break space = non-breaking space, U+00A0 ISOnum -->
<!ENTITY iexcl "¡" ><!-- inverted exclamation mark, U+00A1 ISOnum -->
<!ENTITY cent "¢" ><!-- cent sign, U+00A2 ISOnum -->
<!ENTITY pound "£" ><!-- pound sign, U+00A3 ISOnum -->
<!ENTITY curren "¤" ><!-- currency sign, U+00A4 ISOnum -->
<!ENTITY yen "¥" ><!-- yen sign = yuan sign, U+00A5 ISOnum -->
<!ENTITY brvbar "¦" ><!-- broken bar = broken vertical bar, U+00A6 ISOnum -->
<!ENTITY sect "§" ><!-- section sign, U+00A7 ISOnum -->
<!ENTITY uml "¨" ><!-- diaeresis = spacing diaeresis, U+00A8 ISOdia -->
<!ENTITY copy "©" ><!-- copyright sign, U+00A9 ISOnum -->
<!ENTITY ordf "ª" ><!-- feminine ordinal indicator, U+00AA ISOnum -->
<!ENTITY laquo "«" ><!-- left-pointing double angle quotation mark = left pointing guillemet, U+00AB ISOnum -->
<!ENTITY not "¬" ><!-- not sign, U+00AC ISOnum -->
<!ENTITY shy "­" ><!-- soft hyphen = discretionary hyphen, U+00AD ISOnum -->
<!ENTITY reg "®" ><!-- registered sign = registered trade mark sign, U+00AE ISOnum -->
<!ENTITY macr "¯" ><!-- macron = spacing macron = overline = APL overbar, U+00AF ISOdia -->
<!ENTITY deg "°" ><!-- degree sign, U+00B0 ISOnum -->
<!ENTITY plusmn "±" ><!-- plus-minus sign = plus-or-minus sign, U+00B1 ISOnum -->
<!ENTITY sup2 "²" ><!-- superscript two = superscript digit two = squared, U+00B2 ISOnum -->
<!ENTITY sup3 "³" ><!-- superscript three = superscript digit three = cubed, U+00B3 ISOnum -->
<!ENTITY acute "´" ><!-- acute accent = spacing acute, U+00B4 ISOdia -->
<!ENTITY micro "µ" ><!-- micro sign, U+00B5 ISOnum -->
<!ENTITY para "¶" ><!-- pilcrow sign = paragraph sign, U+00B6 ISOnum -->
<!ENTITY middot "·" ><!-- middle dot = Georgian comma = Greek middle dot, U+00B7 ISOnum -->
<!ENTITY cedil "¸" ><!-- cedilla = spacing cedilla, U+00B8 ISOdia -->
<!ENTITY sup1 "¹" ><!-- superscript one = superscript digit one, U+00B9 ISOnum -->
<!ENTITY ordm "º" ><!-- masculine ordinal indicator, U+00BA ISOnum -->
<!ENTITY raquo "»" ><!-- right-pointing double angle quotation mark = right pointing guillemet, U+00BB ISOnum -->
<!ENTITY frac14 "¼" ><!-- vulgar fraction one quarter = fraction one quarter, U+00BC ISOnum -->
<!ENTITY frac12 "½" ><!-- vulgar fraction one half = fraction one half, U+00BD ISOnum -->
<!ENTITY frac34 "¾" ><!-- vulgar fraction three quarters = fraction three quarters, U+00BE ISOnum -->
<!ENTITY iquest "¿" ><!-- inverted question mark = turned question mark, U+00BF ISOnum -->
<!ENTITY Agrave "À" ><!-- latin capital A with grave = latin capital A grave, U+00C0 ISOlat1 -->
<!ENTITY Aacute "Á" ><!-- latin capital A with acute, U+00C1 ISOlat1 -->
<!ENTITY Acirc "Â" ><!-- latin capital A with circumflex, U+00C2 ISOlat1 -->
<!ENTITY Atilde "Ã" ><!-- latin capital A with tilde, U+00C3 ISOlat1 -->
<!ENTITY Auml "Ä" ><!-- latin capital A with diaeresis, U+00C4 ISOlat1 -->
<!ENTITY Aring "Å" ><!-- latin capital A with ring above = latin capital A ring, U+00C5 ISOlat1 -->
<!ENTITY AElig "Æ" ><!-- latin capital AE = latin capital ligature AE, U+00C6 ISOlat1 -->
<!ENTITY Ccedil "Ç" ><!-- latin capital C with cedilla, U+00C7 ISOlat1 -->
<!ENTITY Egrave "È" ><!-- latin capital E with grave, U+00C8 ISOlat1 -->
<!ENTITY Eacute "É" ><!-- latin capital E with acute, U+00C9 ISOlat1 -->
<!ENTITY Ecirc "Ê" ><!-- latin capital E with circumflex, U+00CA ISOlat1 -->
<!ENTITY Euml "Ë" ><!-- latin capital E with diaeresis, U+00CB ISOlat1 -->
<!ENTITY Igrave "Ì" ><!-- latin capital I with grave, U+00CC ISOlat1 -->
<!ENTITY Iacute "Í" ><!-- latin capital I with acute, U+00CD ISOlat1 -->
<!ENTITY Icirc "Î" ><!-- latin capital I with circumflex, U+00CE ISOlat1 -->
<!ENTITY Iuml "Ï" ><!-- latin capital I with diaeresis, U+00CF ISOlat1 -->
<!ENTITY ETH "Ð" ><!-- latin capital ETH, U+00D0 ISOlat1 -->
<!ENTITY Ntilde "Ñ" ><!-- latin capital N with tilde, U+00D1 ISOlat1 -->
<!ENTITY Ograve "Ò" ><!-- latin capital O with grave, U+00D2 ISOlat1 -->
<!ENTITY Oacute "Ó" ><!-- latin capital O with acute, U+00D3 ISOlat1 -->
<!ENTITY Ocirc "Ô" ><!-- latin capital O with circumflex, U+00D4 ISOlat1 -->
<!ENTITY Otilde "Õ" ><!-- latin capital O with tilde, U+00D5 ISOlat1 -->
<!ENTITY Ouml "Ö" ><!-- latin capital O with diaeresis, U+00D6 ISOlat1 -->
<!ENTITY times "×" ><!-- multiplication sign, U+00D7 ISOnum -->
<!ENTITY Oslash "Ø" ><!-- latin capital O with stroke = latin capital O slash, U+00D8 ISOlat1 -->
<!ENTITY Ugrave "Ù" ><!-- latin capital U with grave, U+00D9 ISOlat1 -->
<!ENTITY Uacute "Ú" ><!-- latin capital U with acute, U+00DA ISOlat1 -->
<!ENTITY Ucirc "Û" ><!-- latin capital U with circumflex, U+00DB ISOlat1 -->
<!ENTITY Uuml "Ü" ><!-- latin capital U with diaeresis, U+00DC ISOlat1 -->
<!ENTITY Yacute "Ý" ><!-- latin capital Y with acute, U+00DD ISOlat1 -->
<!ENTITY THORN "Þ" ><!-- latin capital THORN, U+00DE ISOlat1 -->
<!ENTITY szlig "ß" ><!-- latin small sharp s = ess-zed, U+00DF ISOlat1 -->
<!ENTITY agrave "à" ><!-- latin small a with grave = latin small a grave, U+00E0 ISOlat1 -->
<!ENTITY aacute "á" ><!-- latin small a with acute, U+00E1 ISOlat1 -->
<!ENTITY acirc "â" ><!-- latin small a with circumflex, U+00E2 ISOlat1 -->
<!ENTITY atilde "ã" ><!-- latin small a with tilde, U+00E3 ISOlat1 -->
<!ENTITY auml "ä" ><!-- latin small a with diaeresis, U+00E4 ISOlat1 -->
<!ENTITY aring "å" ><!-- latin small a with ring above = latin small a ring, U+00E5 ISOlat1 -->
<!ENTITY aelig "æ" ><!-- latin small ae = latin small ligature ae, U+00E6 ISOlat1 -->
<!ENTITY ccedil "ç" ><!-- latin small c with cedilla, U+00E7 ISOlat1 -->
<!ENTITY egrave "è" ><!-- latin small e with grave, U+00E8 ISOlat1 -->
<!ENTITY eacute "é" ><!-- latin small e with acute, U+00E9 ISOlat1 -->
<!ENTITY ecirc "ê" ><!-- latin small e with circumflex, U+00EA ISOlat1 -->
<!ENTITY euml "ë" ><!-- latin small e with diaeresis, U+00EB ISOlat1 -->
<!ENTITY igrave "ì" ><!-- latin small i with grave, U+00EC ISOlat1 -->
<!ENTITY iacute "í" ><!-- latin small i with acute, U+00ED ISOlat1 -->
<!ENTITY icirc "î" ><!-- latin small i with circumflex, U+00EE ISOlat1 -->
<!ENTITY iuml "ï" ><!-- latin small i with diaeresis, U+00EF ISOlat1 -->
<!ENTITY eth "ð" ><!-- latin small eth, U+00F0 ISOlat1 -->
<!ENTITY ntilde "ñ" ><!-- latin small n with tilde, U+00F1 ISOlat1 -->
<!ENTITY ograve "ò" ><!-- latin small o with grave, U+00F2 ISOlat1 -->
<!ENTITY oacute "ó" ><!-- latin small o with acute, U+00F3 ISOlat1 -->
<!ENTITY ocirc "ô" ><!-- latin small o with circumflex, U+00F4 ISOlat1 -->
<!ENTITY otilde "õ" ><!-- latin small o with tilde, U+00F5 ISOlat1 -->
<!ENTITY ouml "ö" ><!-- latin small o with diaeresis, U+00F6 ISOlat1 -->
<!ENTITY divide "÷" ><!-- division sign, U+00F7 ISOnum -->
<!ENTITY oslash "ø" ><!-- latin small o with stroke, = latin small o slash, U+00F8 ISOlat1 -->
<!ENTITY ugrave "ù" ><!-- latin small u with grave, U+00F9 ISOlat1 -->
<!ENTITY uacute "ú" ><!-- latin small u with acute, U+00FA ISOlat1 -->
<!ENTITY ucirc "û" ><!-- latin small u with circumflex, U+00FB ISOlat1 -->
<!ENTITY uuml "ü" ><!-- latin small u with diaeresis, U+00FC ISOlat1 -->
<!ENTITY yacute "ý" ><!-- latin small y with acute, U+00FD ISOlat1 -->
<!ENTITY thorn "þ" ><!-- latin small thorn with, U+00FE ISOlat1 -->
<!ENTITY yuml "ÿ" ><!-- latin small y with diaeresis, U+00FF ISOlat1 -->
<!-- end of xhtml-lat1.ent -->
F.1.2.
XHTML
Special
Characters
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/xhtml-special.ent
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/xhtml-special.ent
.
<!-- ...................................................................... -->
<!-- XML-compatible ISO Special Character Entity Set for XHTML ............ -->
<!-- file: xhtml-special.ent
Typical invocation:
<!ENTITY % xhtml-special
PUBLIC "-//W3C//ENTITIES Special for XHTML//EN"
"xhtml-special.ent" >
%xhtml-special;
This DTD module is identified by the PUBLIC and SYSTEM identifiers:
PUBLIC "-//W3C//ENTITIES Special for XHTML//EN"
SYSTEM "http://www.w3.org/MarkUp/DTD/xhtml-special.ent"
Revision: $Id: xhtml-special.ent,v 4.1 2001/04/10 09:34:14 altheim Exp $ SMI
Portions (C) International Organization for Standardization 1986:
Permission to copy in any form is granted for use with conforming
SGML systems and applications as defined in ISO 8879, provided
this notice is included in all copies.
Revisions:
2000-10-28: added ' and altered XML Predefined Entities for compatibility
-->
<!-- Relevant ISO entity set is given unless names are newly introduced.
New names (i.e., not in ISO 8879 [SGML] list) do not clash with
any existing ISO 8879 entity names. ISO 10646 [ISO10646] character
numbers are given for each character, in hex. Entity values are
decimal conversions of the ISO 10646 values and refer to the
document character set. Names are Unicode [UNICODE] names.
-->
<!-- C0 Controls and Basic Latin -->
<!ENTITY lt "&#60;" ><!-- less-than sign, U+003C ISOnum -->
<!ENTITY gt ">" ><!-- greater-than sign, U+003E ISOnum -->
<!ENTITY amp "&#38;" ><!-- ampersand, U+0026 ISOnum -->
<!ENTITY apos "'" ><!-- The Apostrophe (Apostrophe Quote, APL Quote), U+0027 ISOnum -->
<!ENTITY quot """ ><!-- quotation mark (Quote Double), U+0022 ISOnum -->
<!-- Latin Extended-A -->
<!ENTITY OElig "Œ" ><!-- latin capital ligature OE, U+0152 ISOlat2 -->
<!ENTITY oelig "œ" ><!-- latin small ligature oe, U+0153 ISOlat2 -->
<!-- ligature is a misnomer, this is a separate character in some languages -->
<!ENTITY Scaron "Š" ><!-- latin capital letter S with caron, U+0160 ISOlat2 -->
<!ENTITY scaron "š" ><!-- latin small letter s with caron, U+0161 ISOlat2 -->
<!ENTITY Yuml "Ÿ" ><!-- latin capital letter Y with diaeresis, U+0178 ISOlat2 -->
<!-- Spacing Modifier Letters -->
<!ENTITY circ "ˆ" ><!-- modifier letter circumflex accent, U+02C6 ISOpub -->
<!ENTITY tilde "˜" ><!-- small tilde, U+02DC ISOdia -->
<!-- General Punctuation -->
<!ENTITY ensp " " ><!-- en space, U+2002 ISOpub -->
<!ENTITY emsp " " ><!-- em space, U+2003 ISOpub -->
<!ENTITY thinsp " " ><!-- thin space, U+2009 ISOpub -->
<!ENTITY zwnj "‌" ><!-- zero width non-joiner, U+200C NEW RFC 2070 -->
<!ENTITY zwj "‍" ><!-- zero width joiner, U+200D NEW RFC 2070 -->
<!ENTITY lrm "‎" ><!-- left-to-right mark, U+200E NEW RFC 2070 -->
<!ENTITY rlm "‏" ><!-- right-to-left mark, U+200F NEW RFC 2070 -->
<!ENTITY ndash "–" ><!-- en dash, U+2013 ISOpub -->
<!ENTITY mdash "—" ><!-- em dash, U+2014 ISOpub -->
<!ENTITY lsquo "‘" ><!-- left single quotation mark, U+2018 ISOnum -->
<!ENTITY rsquo "’" ><!-- right single quotation mark, U+2019 ISOnum -->
<!ENTITY sbquo "‚" ><!-- single low-9 quotation mark, U+201A NEW -->
<!ENTITY ldquo "“" ><!-- left double quotation mark, U+201C ISOnum -->
<!ENTITY rdquo "”" ><!-- right double quotation mark, U+201D ISOnum -->
<!ENTITY bdquo "„" ><!-- double low-9 quotation mark, U+201E NEW -->
<!ENTITY dagger "†" ><!-- dagger, U+2020 ISOpub -->
<!ENTITY Dagger "‡" ><!-- double dagger, U+2021 ISOpub -->
<!ENTITY permil "‰" ><!-- per mille sign, U+2030 ISOtech -->
<!-- lsaquo is proposed but not yet ISO standardized -->
<!ENTITY lsaquo "‹" ><!-- single left-pointing angle quotation mark, U+2039 ISO proposed -->
<!-- rsaquo is proposed but not yet ISO standardized -->
<!ENTITY rsaquo "›" ><!-- single right-pointing angle quotation mark, U+203A ISO proposed -->
<!ENTITY euro "€" ><!-- euro sign, U+20AC NEW -->
<!-- end of xhtml-special.ent -->
F.1.3.
XHTML
Mathematical,
Greek,
and
Symbolic
Characters
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/xhtml-symbol.ent
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/xhtml-symbol.ent
.
<!-- ...................................................................... -->
<!-- ISO Math, Greek and Symbolic Character Entity Set for XHTML .......... -->
<!-- file: xhtml-symbol.ent
Typical invocation:
<!ENTITY % xhtml-symbol
PUBLIC "-//W3C//ENTITIES Symbols for XHTML//EN"
"xhtml-symbol.ent" >
%xhtml-symbol;
This DTD module is identified by the PUBLIC and SYSTEM identifiers:
PUBLIC "-//W3C//ENTITIES Symbols for XHTML//EN"
SYSTEM "http://www.w3.org/MarkUp/DTD/xhtml-symbol.ent"
Revision: $Id: xhtml-symbol.ent,v 4.1 2001/04/10 09:34:14 altheim Exp $ SMI
Portions (C) International Organization for Standardization 1986:
Permission to copy in any form is granted for use with conforming
SGML systems and applications as defined in ISO 8879, provided
this notice is included in all copies.
-->
<!-- Relevant ISO entity set is given unless names are newly introduced.
New names (i.e., not in ISO 8879 [SGML] list) do not clash with
any existing ISO 8879 entity names. ISO 10646 [ISO10646] character
numbers are given for each character, in hex. Entity values are
decimal conversions of the ISO 10646 values and refer to the
document character set. Names are Unicode [UNICODE] names.
-->
<!-- Latin Extended-B -->
<!ENTITY fnof "ƒ" ><!-- latin small f with hook = function
= florin, U+0192 ISOtech -->
<!-- Greek -->
<!ENTITY Alpha "Α" ><!-- greek capital letter alpha, U+0391 -->
<!ENTITY Beta "Β" ><!-- greek capital letter beta, U+0392 -->
<!ENTITY Gamma "Γ" ><!-- greek capital letter gamma, U+0393 ISOgrk3 -->
<!ENTITY Delta "Δ" ><!-- greek capital letter delta, U+0394 ISOgrk3 -->
<!ENTITY Epsilon "Ε" ><!-- greek capital letter epsilon, U+0395 -->
<!ENTITY Zeta "Ζ" ><!-- greek capital letter zeta, U+0396 -->
<!ENTITY Eta "Η" ><!-- greek capital letter eta, U+0397 -->
<!ENTITY Theta "Θ" ><!-- greek capital letter theta, U+0398 ISOgrk3 -->
<!ENTITY Iota "Ι" ><!-- greek capital letter iota, U+0399 -->
<!ENTITY Kappa "Κ" ><!-- greek capital letter kappa, U+039A -->
<!ENTITY Lambda "Λ" ><!-- greek capital letter lambda, U+039B ISOgrk3 -->
<!ENTITY Mu "Μ" ><!-- greek capital letter mu, U+039C -->
<!ENTITY Nu "Ν" ><!-- greek capital letter nu, U+039D -->
<!ENTITY Xi "Ξ" ><!-- greek capital letter xi, U+039E ISOgrk3 -->
<!ENTITY Omicron "Ο" ><!-- greek capital letter omicron, U+039F -->
<!ENTITY Pi "Π" ><!-- greek capital letter pi, U+03A0 ISOgrk3 -->
<!ENTITY Rho "Ρ" ><!-- greek capital letter rho, U+03A1 -->
<!-- there is no Sigmaf, and no U+03A2 character either -->
<!ENTITY Sigma "Σ" ><!-- greek capital letter sigma, U+03A3 ISOgrk3 -->
<!ENTITY Tau "Τ" ><!-- greek capital letter tau, U+03A4 -->
<!ENTITY Upsilon "Υ" ><!-- greek capital letter upsilon,
U+03A5 ISOgrk3 -->
<!ENTITY Phi "Φ" ><!-- greek capital letter phi, U+03A6 ISOgrk3 -->
<!ENTITY Chi "Χ" ><!-- greek capital letter chi, U+03A7 -->
<!ENTITY Psi "Ψ" ><!-- greek capital letter psi, U+03A8 ISOgrk3 -->
<!ENTITY Omega "Ω" ><!-- greek capital letter omega, U+03A9 ISOgrk3 -->
<!ENTITY alpha "α" ><!-- greek small letter alpha, U+03B1 ISOgrk3 -->
<!ENTITY beta "β" ><!-- greek small letter beta, U+03B2 ISOgrk3 -->
<!ENTITY gamma "γ" ><!-- greek small letter gamma, U+03B3 ISOgrk3 -->
<!ENTITY delta "δ" ><!-- greek small letter delta, U+03B4 ISOgrk3 -->
<!ENTITY epsilon "ε" ><!-- greek small letter epsilon, U+03B5 ISOgrk3 -->
<!ENTITY zeta "ζ" ><!-- greek small letter zeta, U+03B6 ISOgrk3 -->
<!ENTITY eta "η" ><!-- greek small letter eta, U+03B7 ISOgrk3 -->
<!ENTITY theta "θ" ><!-- greek small letter theta, U+03B8 ISOgrk3 -->
<!ENTITY iota "ι" ><!-- greek small letter iota, U+03B9 ISOgrk3 -->
<!ENTITY kappa "κ" ><!-- greek small letter kappa, U+03BA ISOgrk3 -->
<!ENTITY lambda "λ" ><!-- greek small letter lambda, U+03BB ISOgrk3 -->
<!ENTITY mu "μ" ><!-- greek small letter mu, U+03BC ISOgrk3 -->
<!ENTITY nu "ν" ><!-- greek small letter nu, U+03BD ISOgrk3 -->
<!ENTITY xi "ξ" ><!-- greek small letter xi, U+03BE ISOgrk3 -->
<!ENTITY omicron "ο" ><!-- greek small letter omicron, U+03BF NEW -->
<!ENTITY pi "π" ><!-- greek small letter pi, U+03C0 ISOgrk3 -->
<!ENTITY rho "ρ" ><!-- greek small letter rho, U+03C1 ISOgrk3 -->
<!ENTITY sigmaf "ς" ><!-- greek small letter final sigma, U+03C2 ISOgrk3 -->
<!ENTITY sigma "σ" ><!-- greek small letter sigma, U+03C3 ISOgrk3 -->
<!ENTITY tau "τ" ><!-- greek small letter tau, U+03C4 ISOgrk3 -->
<!ENTITY upsilon "υ" ><!-- greek small letter upsilon, U+03C5 ISOgrk3 -->
<!ENTITY phi "φ" ><!-- greek small letter phi, U+03C6 ISOgrk3 -->
<!ENTITY chi "χ" ><!-- greek small letter chi, U+03C7 ISOgrk3 -->
<!ENTITY psi "ψ" ><!-- greek small letter psi, U+03C8 ISOgrk3 -->
<!ENTITY omega "ω" ><!-- greek small letter omega, U+03C9 ISOgrk3 -->
<!ENTITY thetasym "ϑ" ><!-- greek small letter theta symbol, U+03D1 NEW -->
<!ENTITY upsih "ϒ" ><!-- greek upsilon with hook symbol, U+03D2 NEW -->
<!ENTITY piv "ϖ" ><!-- greek pi symbol, U+03D6 ISOgrk3 -->
<!-- General Punctuation -->
<!ENTITY bull "•" ><!-- bullet = black small circle, U+2022 ISOpub -->
<!-- bullet is NOT the same as bullet operator, U+2219 -->
<!ENTITY hellip "…" ><!-- horizontal ellipsis = three dot leader, U+2026 ISOpub -->
<!ENTITY prime "′" ><!-- prime = minutes = feet, U+2032 ISOtech -->
<!ENTITY Prime "″" ><!-- double prime = seconds = inches, U+2033 ISOtech -->
<!ENTITY oline "‾" ><!-- overline = spacing overscore, U+203E NEW -->
<!ENTITY frasl "⁄" ><!-- fraction slash, U+2044 NEW -->
<!-- Letterlike Symbols -->
<!ENTITY weierp "℘" ><!-- script capital P = power set = Weierstrass p, U+2118 ISOamso -->
<!ENTITY image "ℑ" ><!-- blackletter capital I = imaginary part, U+2111 ISOamso -->
<!ENTITY real "ℜ" ><!-- blackletter capital R = real part symbol, U+211C ISOamso -->
<!ENTITY trade "™" ><!-- trade mark sign, U+2122 ISOnum -->
<!ENTITY alefsym "ℵ" ><!-- alef symbol = first transfinite cardinal, U+2135 NEW -->
<!-- alef symbol is NOT the same as hebrew letter alef, U+05D0 although
the same glyph could be used to depict both characters -->
<!-- Arrows -->
<!ENTITY larr "←" ><!-- leftwards arrow, U+2190 ISOnum -->
<!ENTITY uarr "↑" ><!-- upwards arrow, U+2191 ISOnum-->
<!ENTITY rarr "→" ><!-- rightwards arrow, U+2192 ISOnum -->
<!ENTITY darr "↓" ><!-- downwards arrow, U+2193 ISOnum -->
<!ENTITY harr "↔" ><!-- left right arrow, U+2194 ISOamsa -->
<!ENTITY crarr "↵" ><!-- downwards arrow with corner leftwards
= carriage return, U+21B5 NEW -->
<!ENTITY lArr "⇐" ><!-- leftwards double arrow, U+21D0 ISOtech -->
<!-- Unicode does not say that lArr is the same as the 'is implied by' arrow
but also does not have any other character for that function. So ? lArr can
be used for 'is implied by' as ISOtech suggests -->
<!ENTITY uArr "⇑" ><!-- upwards double arrow, U+21D1 ISOamsa -->
<!ENTITY rArr "⇒" ><!-- rightwards double arrow, U+21D2 ISOtech -->
<!-- Unicode does not say this is the 'implies' character but does not have
another character with this function so ?
rArr can be used for 'implies' as ISOtech suggests -->
<!ENTITY dArr "⇓" ><!-- downwards double arrow, U+21D3 ISOamsa -->
<!ENTITY hArr "⇔" ><!-- left right double arrow, U+21D4 ISOamsa -->
<!-- Mathematical Operators -->
<!ENTITY forall "∀" ><!-- for all, U+2200 ISOtech -->
<!ENTITY part "∂" ><!-- partial differential, U+2202 ISOtech -->
<!ENTITY exist "∃" ><!-- there exists, U+2203 ISOtech -->
<!ENTITY empty "∅" ><!-- empty set = null set, U+2205 ISOamso -->
<!ENTITY nabla "∇" ><!-- nabla = backward difference, U+2207 ISOtech -->
<!ENTITY isin "∈" ><!-- element of, U+2208 ISOtech -->
<!ENTITY notin "∉" ><!-- not an element of, U+2209 ISOtech -->
<!ENTITY ni "∋" ><!-- contains as member, U+220B ISOtech -->
<!-- should there be a more memorable name than 'ni'? -->
<!ENTITY prod "∏" ><!-- n-ary product = product sign, U+220F ISOamsb -->
<!-- prod is NOT the same character as U+03A0 'greek capital letter pi' though
the same glyph might be used for both -->
<!ENTITY sum "∑" ><!-- n-ary sumation, U+2211 ISOamsb -->
<!-- sum is NOT the same character as U+03A3 'greek capital letter sigma'
though the same glyph might be used for both -->
<!ENTITY minus "−" ><!-- minus sign, U+2212 ISOtech -->
<!ENTITY lowast "∗" ><!-- asterisk operator, U+2217 ISOtech -->
<!ENTITY radic "√" ><!-- square root = radical sign, U+221A ISOtech -->
<!ENTITY prop "∝" ><!-- proportional to, U+221D ISOtech -->
<!ENTITY infin "∞" ><!-- infinity, U+221E ISOtech -->
<!ENTITY ang "∠" ><!-- angle, U+2220 ISOamso -->
<!ENTITY and "∧" ><!-- logical and = wedge, U+2227 ISOtech -->
<!ENTITY or "∨" ><!-- logical or = vee, U+2228 ISOtech -->
<!ENTITY cap "∩" ><!-- intersection = cap, U+2229 ISOtech -->
<!ENTITY cup "∪" ><!-- union = cup, U+222A ISOtech -->
<!ENTITY int "∫" ><!-- integral, U+222B ISOtech -->
<!ENTITY there4 "∴" ><!-- therefore, U+2234 ISOtech -->
<!ENTITY sim "∼" ><!-- tilde operator = varies with = similar to, U+223C ISOtech -->
<!-- tilde operator is NOT the same character as the tilde, U+007E,
although the same glyph might be used to represent both -->
<!ENTITY cong "≅" ><!-- approximately equal to, U+2245 ISOtech -->
<!ENTITY asymp "≈" ><!-- almost equal to = asymptotic to, U+2248 ISOamsr -->
<!ENTITY ne "≠" ><!-- not equal to, U+2260 ISOtech -->
<!ENTITY equiv "≡" ><!-- identical to, U+2261 ISOtech -->
<!ENTITY le "≤" ><!-- less-than or equal to, U+2264 ISOtech -->
<!ENTITY ge "≥" ><!-- greater-than or equal to, U+2265 ISOtech -->
<!ENTITY sub "⊂" ><!-- subset of, U+2282 ISOtech -->
<!ENTITY sup "⊃" ><!-- superset of, U+2283 ISOtech -->
<!-- note that nsup, 'not a superset of, U+2283' is not covered by the Symbol
font encoding and is not included. Should it be, for symmetry?
It is in ISOamsn -->
<!ENTITY nsub "⊄" ><!-- not a subset of, U+2284 ISOamsn -->
<!ENTITY sube "⊆" ><!-- subset of or equal to, U+2286 ISOtech -->
<!ENTITY supe "⊇" ><!-- superset of or equal to, U+2287 ISOtech -->
<!ENTITY oplus "⊕" ><!-- circled plus = direct sum, U+2295 ISOamsb -->
<!ENTITY otimes "⊗" ><!-- circled times = vector product, U+2297 ISOamsb -->
<!ENTITY perp "⊥" ><!-- up tack = orthogonal to = perpendicular, U+22A5 ISOtech -->
<!ENTITY sdot "⋅" ><!-- dot operator, U+22C5 ISOamsb -->
<!-- dot operator is NOT the same character as U+00B7 middle dot -->
<!-- Miscellaneous Technical -->
<!ENTITY lceil "⌈" ><!-- left ceiling = apl upstile, U+2308 ISOamsc -->
<!ENTITY rceil "⌉" ><!-- right ceiling, U+2309 ISOamsc -->
<!ENTITY lfloor "⌊" ><!-- left floor = apl downstile, U+230A ISOamsc -->
<!ENTITY rfloor "⌋" ><!-- right floor, U+230B ISOamsc -->
<!ENTITY lang "〈" ><!-- left-pointing angle bracket = bra, U+2329 ISOtech -->
<!-- lang is NOT the same character as U+003C 'less than'
or U+2039 'single left-pointing angle quotation mark' -->
<!ENTITY rang "〉" ><!-- right-pointing angle bracket = ket, U+232A ISOtech -->
<!-- rang is NOT the same character as U+003E 'greater than'
or U+203A 'single right-pointing angle quotation mark' -->
<!-- Geometric Shapes -->
<!ENTITY loz "◊" ><!-- lozenge, U+25CA ISOpub -->
<!-- Miscellaneous Symbols -->
<!ENTITY spades "♠" ><!-- black spade suit, U+2660 ISOpub -->
<!-- black here seems to mean filled as opposed to hollow -->
<!ENTITY clubs "♣" ><!-- black club suit = shamrock, U+2663 ISOpub -->
<!ENTITY hearts "♥" ><!-- black heart suit = valentine, U+2665 ISOpub -->
<!ENTITY diams "♦" ><!-- black diamond suit, U+2666 ISOpub -->
<!-- end of xhtml-symbol.ent -->
F.2.
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:
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/xhtml-framework-1.mod
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/xhtml-framework-1.mod
.
<!-- ...................................................................... -->
<!-- XHTML Modular Framework Module ...................................... -->
<!-- file: xhtml-framework-1.mod
This is XHTML, a reformulation of HTML as a modular XML application.
Copyright 1998-2005 W3C (MIT, ERCIM, Keio), All Rights Reserved.
Revision: $Id: xhtml-framework-1.mod,v 4.0 2001/04/02 22:42:49 altheim Exp $ SMI
This DTD module is identified by the PUBLIC and SYSTEM identifiers:
PUBLIC "-//W3C//ENTITIES XHTML Modular Framework 1.0//EN"
SYSTEM "http://www.w3.org/MarkUp/DTD/xhtml-framework-1.mod"
Revisions:
(none)
....................................................................... -->
<!-- Modular Framework
This required module instantiates the modules needed
to support the XHTML modularization model, including:
+ datatypes
+ namespace-qualified names
+ common attributes
+ document model
+ character entities
The Intrinsic Events module is ignored by default but
occurs in this module because it must be instantiated
prior to Attributes but after Datatypes.
-->
<!ENTITY % xhtml-arch.module "IGNORE" >
<![%xhtml-arch.module;[
<!ENTITY % xhtml-arch.mod
PUBLIC "-//W3C//ELEMENTS XHTML Base Architecture 1.0//EN"
"xhtml-arch-1.mod" >
%xhtml-arch.mod;]]>
<!ENTITY % xhtml-notations.module "IGNORE" >
<![%xhtml-notations.module;[
<!ENTITY % xhtml-notations.mod
PUBLIC "-//W3C//NOTATIONS XHTML Notations 1.0//EN"
"xhtml-notations-1.mod" >
%xhtml-notations.mod;]]>
<!ENTITY % xhtml-datatypes.module "INCLUDE" >
<![%xhtml-datatypes.module;[
<!ENTITY % xhtml-datatypes.mod
PUBLIC "-//W3C//ENTITIES XHTML Datatypes 1.0//EN"
"xhtml-datatypes-1.mod" >
%xhtml-datatypes.mod;]]>
<!-- placeholder for XLink support module -->
<!ENTITY % xhtml-xlink.mod "" >
%xhtml-xlink.mod;
<!ENTITY % xhtml-qname.module "INCLUDE" >
<![%xhtml-qname.module;[
<!ENTITY % xhtml-qname.mod
PUBLIC "-//W3C//ENTITIES XHTML Qualified Names 1.0//EN"
"xhtml-qname-1.mod" >
%xhtml-qname.mod;]]>
<!ENTITY % xhtml-events.module "IGNORE" >
<![%xhtml-events.module;[
<!ENTITY % xhtml-events.mod
PUBLIC "-//W3C//ENTITIES XHTML Intrinsic Events 1.0//EN"
"xhtml-events-1.mod" >
%xhtml-events.mod;]]>
<!ENTITY % xhtml-attribs.module "INCLUDE" >
<![%xhtml-attribs.module;[
<!ENTITY % xhtml-attribs.mod
PUBLIC "-//W3C//ENTITIES XHTML Common Attributes 1.0//EN"
"xhtml-attribs-1.mod" >
%xhtml-attribs.mod;]]>
<!-- placeholder for content model redeclarations -->
<!ENTITY % xhtml-model.redecl "" >
%xhtml-model.redecl;
<!ENTITY % xhtml-model.module "INCLUDE" >
<![%xhtml-model.module;[
<!-- instantiate the Document Model module declared in the DTD driver
-->
%xhtml-model.mod;]]>
<!ENTITY % xhtml-charent.module "INCLUDE" >
<![%xhtml-charent.module;[
<!ENTITY % xhtml-charent.mod
PUBLIC "-//W3C//ENTITIES XHTML Character Entities 1.0//EN"
"xhtml-charent-1.mod" >
%xhtml-charent.mod;]]>
<!-- end of xhtml-framework-1.mod -->
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.
The
Modular
framework
also
relies
upon
the
following
component
modules:
F.2.1.
XHTML
Base
Architecture
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/xhtml-arch-1.mod
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/xhtml-arch-1.mod
.
<!-- ...................................................................... -->
<!-- XHTML Base Architecture Module ...................................... -->
<!-- file: xhtml-arch-1.mod
This is XHTML, a reformulation of HTML as a modular XML application.
Copyright 1998-2005 W3C (MIT, ERCIM, Keio), All Rights Reserved.
Revision: $Id: xhtml-arch-1.mod,v 4.0 2001/04/02 22:42:49 altheim Exp $ SMI
This DTD module is identified by the PUBLIC and SYSTEM identifiers:
PUBLIC "-//W3C//ELEMENTS XHTML Base Architecture 1.0//EN"
SYSTEM "http://www.w3.org/MarkUp/DTD/xhtml-arch-1.mod"
Revisions:
(none)
....................................................................... -->
<!-- This optional module includes declarations that enable XHTML to be used
as a base architecture according to the 'Architectural Forms Definition
Requirements' (Annex A.3, ISO/IEC 10744, 2nd edition). For more information
on use of architectural forms, see the HyTime web site at:
http://www.hytime.org/
-->
<?IS10744 ArcBase xhtml ?>
<!NOTATION xhtml PUBLIC "-//W3C//NOTATION AFDR ARCBASE XHTML 1.1//EN" >
<!-- Entity declaration for associated Architectural DTD
-->
<!ENTITY xhtml-arch.dtd
PUBLIC "-//W3C//DTD XHTML Architecture 1.1//EN"
"xhtml11-arch.dtd" >
<?IS10744:arch xhtml
public-id = "-//W3C//NOTATION AFDR ARCBASE XHTML 1.1//EN"
dtd-public-id = "-//W3C//DTD XHTML 1.1//EN"
dtd-system-id = "xhtml11.dtd"
doc-elem-form = "html"
form-att = "html"
renamer-att = "htnames"
suppressor-att = "htsupp"
data-ignore-att = "htign"
auto = "ArcAuto"
options = "HtModReq HtModOpt"
HtModReq = "Framework Text Hypertext Lists Structure"
HtModOpt = "Standard"
?>
<!-- end of xhtml-arch-1.mod -->
F.2.2.
XHTML
Notations
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/xhtml-notations-1.mod
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/xhtml-notations-1.mod
.
<!-- ...................................................................... -->
<!-- XHTML Notations Module .............................................. -->
<!-- file: xhtml-notations-1.mod
This is XHTML, a reformulation of HTML as a modular XML application.
Copyright 1998-2005 W3C (MIT, ERCIM, Keio), All Rights Reserved.
Revision: $Id: xhtml-notations-1.mod,v 4.0 2001/04/02 22:42:49 altheim Exp $
This DTD module is identified by the PUBLIC and SYSTEM identifiers:
PUBLIC "-//W3C//NOTATIONS XHTML Notations 1.0//EN"
SYSTEM "http://www.w3.org/MarkUp/DTD/xhtml-notations-1.mod"
Revisions:
(none)
....................................................................... -->
<!-- Notations
defines the following notations, many of these imported from
other specifications and standards. When an existing FPI is
known, it is incorporated here.
-->
<!-- XML Notations ..................................... -->
<!-- SGML and XML Notations ............................ -->
<!-- W3C XML 1.0 Recommendation -->
<!NOTATION w3c-xml
PUBLIC "ISO 8879//NOTATION Extensible Markup Language (XML) 1.0//EN" >
<!-- XML 1.0 CDATA -->
<!NOTATION cdata
PUBLIC "-//W3C//NOTATION XML 1.0: CDATA//EN" >
<!-- SGML Formal Public Identifiers -->
<!NOTATION fpi
PUBLIC "ISO 8879:1986//NOTATION Formal Public Identifier//EN" >
<!-- XHTML Notations ................................... -->
<!-- Length defined for cellpadding/cellspacing -->
<!-- nn for pixels or nn% for percentage length -->
<!NOTATION length
PUBLIC "-//W3C//NOTATION XHTML Datatype: Length//EN" >
<!-- space-separated list of link types -->
<!NOTATION linkTypes
PUBLIC "-//W3C//NOTATION XHTML Datatype: LinkTypes//EN" >
<!-- single or comma-separated list of media descriptors -->
<!NOTATION mediaDesc
PUBLIC "-//W3C//NOTATION XHTML Datatype: MediaDesc//EN" >
<!-- pixel, percentage, or relative -->
<!NOTATION multiLength
PUBLIC "-//W3C//NOTATION XHTML Datatype: MultiLength//EN" >
<!-- one or more digits (NUMBER) -->
<!NOTATION number
PUBLIC "-//W3C//NOTATION XHTML Datatype: Number//EN" >
<!-- integer representing length in pixels -->
<!NOTATION pixels
PUBLIC "-//W3C//NOTATION XHTML Datatype: Pixels//EN" >
<!-- script expression -->
<!NOTATION script
PUBLIC "-//W3C//NOTATION XHTML Datatype: Script//EN" >
<!-- textual content -->
<!NOTATION text
PUBLIC "-//W3C//NOTATION XHTML Datatype: Text//EN" >
<!-- Imported Notations ................................ -->
<!-- a single character from [ISO10646] -->
<!NOTATION character
PUBLIC "-//W3C//NOTATION XHTML Datatype: Character//EN" >
<!-- a character encoding, as per [RFC2045] -->
<!NOTATION charset
PUBLIC "-//W3C//NOTATION XHTML Datatype: Charset//EN" >
<!-- a space separated list of character encodings, as per [RFC2045] -->
<!NOTATION charsets
PUBLIC "-//W3C//NOTATION XHTML Datatype: Charsets//EN" >
<!-- media type, as per [RFC2045] -->
<!NOTATION contentType
PUBLIC "-//W3C//NOTATION XHTML Datatype: ContentType//EN" >
<!-- comma-separated list of media types, as per [RFC2045] -->
<!NOTATION contentTypes
PUBLIC "-//W3C//NOTATION XHTML Datatype: ContentTypes//EN" >
<!-- date and time information. ISO date format -->
<!NOTATION datetime
PUBLIC "-//W3C//NOTATION XHTML Datatype: Datetime//EN" >
<!-- a language code, as per [RFC3066] -->
<!NOTATION languageCode
PUBLIC "-//W3C//NOTATION XHTML Datatype: LanguageCode//EN" >
<!-- a Uniform Resource Identifier, see [URI] -->
<!NOTATION uri
PUBLIC "-//W3C//NOTATION XHTML Datatype: URI//EN" >
<!-- a space-separated list of Uniform Resource Identifiers, see [URI] -->
<!NOTATION uris
PUBLIC "-//W3C//NOTATION XHTML Datatype: URIs//EN" >
<!-- end of xhtml-notations-1.mod -->
F.2.3.
XHTML
Datatypes
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/xhtml-datatypes-1.mod
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/xhtml-datatypes-1.mod
.
<!-- ...................................................................... -->
<!-- XHTML Datatypes Module .............................................. -->
<!-- file: xhtml-datatypes-1.mod
This is XHTML, a reformulation of HTML as a modular XML application.
Copyright 1998-2005 W3C (MIT, ERCIM, Keio), All Rights Reserved.
Revision: $Id: xhtml-datatypes-1.mod,v 4.1 2001/04/06 19:23:32 altheim Exp $ SMI
This DTD module is identified by the PUBLIC and SYSTEM identifiers:
PUBLIC "-//W3C//ENTITIES XHTML Datatypes 1.0//EN"
SYSTEM "http://www.w3.org/MarkUp/DTD/xhtml-datatypes-1.mod"
Revisions:
(none)
....................................................................... -->
<!-- Datatypes
defines containers for the following datatypes, many of
these imported from other specifications and standards.
-->
<!-- Length defined for cellpadding/cellspacing -->
<!-- nn for pixels or nn% for percentage length -->
<!ENTITY % Length.datatype "CDATA" >
<!-- space-separated list of link types -->
<!ENTITY % LinkTypes.datatype "NMTOKENS" >
<!-- single or comma-separated list of media descriptors -->
<!ENTITY % MediaDesc.datatype "CDATA" >
<!-- pixel, percentage, or relative -->
<!ENTITY % MultiLength.datatype "CDATA" >
<!-- one or more digits (NUMBER) -->
<!ENTITY % Number.datatype "CDATA" >
<!-- integer representing length in pixels -->
<!ENTITY % Pixels.datatype "CDATA" >
<!-- script expression -->
<!ENTITY % Script.datatype "CDATA" >
<!-- textual content -->
<!ENTITY % Text.datatype "CDATA" >
<!-- Placeholder Compact URI-related types -->
<!ENTITY % CURIE.datatype "CDATA" >
<!ENTITY % CURIEs.datatype "CDATA" >
<!ENTITY % SafeCURIE.datatype "CDATA" >
<!ENTITY % SafeCURIEs.datatype "CDATA" >
<!ENTITY % URIorSafeCURIE.datatype "CDATA" >
<!ENTITY % URIorSafeCURIEs.datatype "CDATA" >
<!-- Imported Datatypes ................................ -->
<!-- a single character from [ISO10646] -->
<!ENTITY % Character.datatype "CDATA" >
<!-- a character encoding, as per [RFC2045] -->
<!ENTITY % Charset.datatype "CDATA" >
<!-- a space separated list of character encodings, as per [RFC2045] -->
<!ENTITY % Charsets.datatype "CDATA" >
<!-- Color specification using color name or sRGB (#RRGGBB) values -->
<!ENTITY % Color.datatype "CDATA" >
<!-- media type, as per [RFC2045] -->
<!ENTITY % ContentType.datatype "CDATA" >
<!-- comma-separated list of media types, as per [RFC2045] -->
<!ENTITY % ContentTypes.datatype "CDATA" >
<!-- date and time information. ISO date format -->
<!ENTITY % Datetime.datatype "CDATA" >
<!-- formal public identifier, as per [ISO8879] -->
<!ENTITY % FPI.datatype "CDATA" >
<!-- a language code, as per [RFC3066] or its successor -->
<!ENTITY % LanguageCode.datatype "CDATA" >
<!-- a comma separated list of language code ranges -->
<!ENTITY % LanguageCodes.datatype "CDATA" >
<!-- a qualified name , as per [XMLNS] or its successor -->
<!ENTITY % QName.datatype "CDATA" >
<!ENTITY % QNames.datatype "CDATA" >
<!-- a Uniform Resource Identifier, see [URI] -->
<!ENTITY % URI.datatype "CDATA" >
<!-- a space-separated list of Uniform Resource Identifiers, see [URI] -->
<!ENTITY % URIs.datatype "CDATA" >
<!-- a relative URI reference consisting of an initial '#' and a fragment ID -->
<!ENTITY % URIREF.datatype "CDATA" >
<!-- end of xhtml-datatypes-1.mod -->
F.2.4.
XHTML
Common
Attribute
Definitions
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/xhtml-attribs-1.mod
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/xhtml-attribs-1.mod
.
<!-- ...................................................................... -->
<!-- XHTML Common Attributes Module ...................................... -->
<!-- file: xhtml-attribs-1.mod
This is XHTML, a reformulation of HTML as a modular XML application.
Copyright 1998-2005 W3C (MIT, ERCIM, Keio), All Rights Reserved.
Revision: $Id: xhtml-attribs-1.mod,v 4.0 2001/04/02 22:42:49 altheim Exp $ SMI
This DTD module is identified by the PUBLIC and SYSTEM identifiers:
PUBLIC "-//W3C//ENTITIES XHTML Common Attributes 1.0//EN"
SYSTEM "http://www.w3.org/MarkUp/DTD/xhtml-attribs-1.mod"
Revisions:
(none)
....................................................................... -->
<!-- Common Attributes
This module declares many of the common attributes for the XHTML DTD.
%NS.decl.attrib; is declared in the XHTML Qname module.
Note that this file was extended in XHTML Modularization 1.1 to
include declarations of "global" versions of the attribute collections.
The global versions of the attributes are for use on elements in other
namespaces. The global version of "common" includes the xmlns declaration
for the prefixed version of the xhtml namespace. If you are only using a
specific attribute or an individual attribute collection, you must also
include the XHTML.xmlns.attrib.prefixed PE on your elements.
-->
<!ENTITY % id.attrib
"id ID #IMPLIED"
>
<![%XHTML.global.attrs.prefixed;[
<!ENTITY % XHTML.global.id.attrib
"%XHTML.prefix;:id ID #IMPLIED"
>
]]>
<!ENTITY % class.attrib
"class CDATA #IMPLIED"
>
<![%XHTML.global.attrs.prefixed;[
<!ENTITY % XHTML.global.class.attrib
"%XHTML.prefix;:class CDATA #IMPLIED"
>
]]>
<!ENTITY % title.attrib
"title %Text.datatype; #IMPLIED"
>
<![%XHTML.global.attrs.prefixed;[
<!ENTITY % XHTML.global.title.attrib
"%XHTML.prefix;:title %Text.datatype; #IMPLIED"
>
]]>
<!ENTITY % Core.extra.attrib "" >
<!ENTITY % Core.attrib
"%XHTML.xmlns.attrib;
%id.attrib;
%class.attrib;
%title.attrib;
xml:space ( preserve ) #FIXED 'preserve'
%Core.extra.attrib;"
>
<!ENTITY % XHTML.global.core.extra.attrib "" >
<![%XHTML.global.attrs.prefixed;[
<!ENTITY % XHTML.global.core.attrib
"%XHTML.global.id.attrib;
%XHTML.global.class.attrib;
%XHTML.global.title.attrib;
%XHTML.global.core.extra.attrib;"
>
]]>
<!ENTITY % XHTML.global.core.attrib "" >
<!ENTITY % lang.attrib
"xml:lang %LanguageCode.datatype; #IMPLIED"
>
<![%XHTML.bidi;[
<!ENTITY % dir.attrib
"dir ( ltr | rtl ) #IMPLIED"
>
<!ENTITY % I18n.attrib
"%dir.attrib;
%lang.attrib;"
>
<![%XHTML.global.attrs.prefixed;[
<!ENTITY XHTML.global.i18n.attrib
"%XHTML.prefix;:dir ( ltr | rtl ) #IMPLIED
%lang.attrib;"
>
]]>
<!ENTITY XHTML.global.i18n.attrib "" >
]]>
<!ENTITY % I18n.attrib
"%lang.attrib;"
>
<!ENTITY % XHTML.global.i18n.attrib
"%lang.attrib;"
>
<!ENTITY % Common.extra.attrib "" >
<!ENTITY % XHTML.global.common.extra.attrib "" >
<!-- intrinsic event attributes declared previously
-->
<!ENTITY % Events.attrib "" >
<!ENTITY % XHTML.global.events.attrib "" >
<!ENTITY % Common.attrib
"%Core.attrib;
%I18n.attrib;
%Events.attrib;
%Common.extra.attrib;"
>
<!ENTITY % XHTML.global.common.attrib
"%XHTML.xmlns.attrib.prefixed;
%XHTML.global.core.attrib;
%XHTML.global.i18n.attrib;
%XHTML.global.events.attrib;
%XHTML.global.common.extra.attrib;"
>
<!-- end of xhtml-attribs-1.mod -->
F.2.5.
XHTML
Qualified
Names
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/xhtml-qname-1.mod
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/xhtml-qname-1.mod
.
<!-- ....................................................................... -->
<!-- XHTML Qname Module ................................................... -->
<!-- file: xhtml-qname-1.mod
This is XHTML, a reformulation of HTML as a modular XML application.
Copyright 1998-2005 W3C (MIT, ERCIM, Keio), All Rights Reserved.
Revision: $Id: xhtml-qname-1.mod,v 4.0 2001/04/02 22:42:49 altheim Exp $ SMI
This DTD module is identified by the PUBLIC and SYSTEM identifiers:
PUBLIC "-//W3C//ENTITIES XHTML Qualified Names 1.0//EN"
SYSTEM "http://www.w3.org/MarkUp/DTD/xhtml-qname-1.mod"
Revisions:
#2000-10-22: added qname declarations for ruby elements
....................................................................... -->
<!-- XHTML Qname (Qualified Name) Module
This module is contained in two parts, labeled Section 'A' and 'B':
Section A declares parameter entities to support namespace-
qualified names, namespace declarations, and name prefixing
for XHTML and extensions.
Section B declares parameter entities used to provide
namespace-qualified names for all XHTML element types:
%applet.qname; the xmlns-qualified name for <applet>
%base.qname; the xmlns-qualified name for <base>
...
XHTML extensions would create a module similar to this one.
Included in the XHTML distribution is a template module
('template-qname-1.mod') suitable for this purpose.
-->
<!-- Section A: XHTML XML Namespace Framework :::::::::::::::::::: -->
<!-- 1. Declare a %XHTML.prefixed; conditional section keyword, used
to activate namespace prefixing. The default value should
inherit '%NS.prefixed;' from the DTD driver, so that unless
overridden, the default behaviour follows the overall DTD
prefixing scheme.
-->
<!ENTITY % NS.prefixed "IGNORE" >
<!ENTITY % XHTML.prefixed "%NS.prefixed;" >
<!-- By default, we always permit XHTML attribute collections to have
namespace-qualified prefixes as well.
-->
<!ENTITY % XHTML.global.attrs.prefixed "INCLUDE" >
<!-- By default, we allow the XML Schema attributes on the root
element.
-->
<!ENTITY % XHTML.xsi.attrs "INCLUDE" >
<!-- 2. Declare a parameter entity (eg., %XHTML.xmlns;) containing
the URI reference used to identify the XHTML namespace:
-->
<!ENTITY % XHTML.xmlns "http://www.w3.org/1999/xhtml" >
<!-- 3. Declare parameter entities (eg., %XHTML.prefix;) containing
the default namespace prefix string(s) to use when prefixing
is enabled. This may be overridden in the DTD driver or the
internal subset of an document instance. If no default prefix
is desired, this may be declared as an empty string.
NOTE: As specified in [XMLNAMES], the namespace prefix serves
as a proxy for the URI reference, and is not in itself significant.
-->
<!ENTITY % XHTML.prefix "xhtml" >
<!-- 4. Declare parameter entities (eg., %XHTML.pfx;) containing the
colonized prefix(es) (eg., '%XHTML.prefix;:') used when
prefixing is active, an empty string when it is not.
-->
<![%XHTML.prefixed;[
<!ENTITY % XHTML.pfx "%XHTML.prefix;:" >
]]>
<!ENTITY % XHTML.pfx "" >
<!-- declare qualified name extensions here ............ -->
<!ENTITY % xhtml-qname-extra.mod "" >
%xhtml-qname-extra.mod;
<!-- 5. The parameter entity %XHTML.xmlns.extra.attrib; may be
redeclared to contain any non-XHTML namespace declaration
attributes for namespaces embedded in XHTML. The default
is an empty string. XLink should be included here if used
in the DTD.
-->
<!ENTITY % XHTML.xmlns.extra.attrib "" >
<!-- The remainder of Section A is only followed in XHTML, not extensions. -->
<!-- Declare a parameter entity %NS.decl.attrib; containing
all XML Namespace declarations used in the DTD, plus the
xmlns declaration for XHTML, its form dependent on whether
prefixing is active.
-->
<!ENTITY % XHTML.xmlns.attrib.prefixed
"xmlns:%XHTML.prefix; %URI.datatype; #FIXED '%XHTML.xmlns;'"
>
<![%XHTML.prefixed;[
<!ENTITY % NS.decl.attrib
"%XHTML.xmlns.attrib.prefixed;
%XHTML.xmlns.extra.attrib;"
>
]]>
<!ENTITY % NS.decl.attrib
"%XHTML.xmlns.extra.attrib;"
>
<!-- Declare a parameter entity %XSI.prefix as a prefix to use for XML
Schema Instance attributes.
-->
<!ENTITY % XSI.prefix "xsi" >
<!ENTITY % XSI.xmlns "http://www.w3.org/2001/XMLSchema-instance" >
<!-- Declare a parameter entity %XSI.xmlns.attrib as support for the
schemaLocation attribute, since this is legal throughout the DTD.
-->
<!ENTITY % XSI.xmlns.attrib
"xmlns:%XSI.prefix; %URI.datatype; #FIXED '%XSI.xmlns;'" >
<!-- This is a placeholder for future XLink support.
-->
<!ENTITY % XLINK.xmlns.attrib "" >
<!-- This is the attribute for the XML Schema namespace - XHTML
Modularization is also expressed in XML Schema, and it needs to
be legal to declare the XML Schema namespace and the
schemaLocation attribute on the root element of XHTML family
documents.
-->
<![%XHTML.xsi.attrs;[
<!ENTITY % XSI.prefix "xsi" >
<!ENTITY % XSI.pfx "%XSI.prefix;:" >
<!ENTITY % XSI.xmlns "http://www.w3.org/2001/XMLSchema-instance" >
<!ENTITY % XSI.xmlns.attrib
"xmlns:%XSI.prefix; %URI.datatype; #FIXED '%XSI.xmlns;'"
>
]]>
<!ENTITY % XSI.prefix "" >
<!ENTITY % XSI.pfx "" >
<!ENTITY % XSI.xmlns.attrib "" >
<!-- Declare a parameter entity %NS.decl.attrib; containing all
XML namespace declaration attributes used by XHTML, including
a default xmlns attribute when prefixing is inactive.
-->
<![%XHTML.prefixed;[
<!ENTITY % XHTML.xmlns.attrib
"%NS.decl.attrib;
%XSI.xmlns.attrib;
%XLINK.xmlns.attrib;"
>
]]>
<!ENTITY % XHTML.xmlns.attrib
"xmlns %URI.datatype; #FIXED '%XHTML.xmlns;'
%NS.decl.attrib;
%XSI.xmlns.attrib;
%XLINK.xmlns.attrib;"
>
<!-- placeholder for qualified name redeclarations -->
<!ENTITY % xhtml-qname.redecl "" >
%xhtml-qname.redecl;
<!-- Section B: XHTML Qualified Names ::::::::::::::::::::::::::::: -->
<!-- 6. This section declares parameter entities used to provide
namespace-qualified names for all XHTML element types.
-->
<!-- module: xhtml-applet-1.mod -->
<!ENTITY % applet.qname "%XHTML.pfx;applet" >
<!-- module: xhtml-base-1.mod -->
<!ENTITY % base.qname "%XHTML.pfx;base" >
<!-- module: xhtml-bdo-1.mod -->
<!ENTITY % bdo.qname "%XHTML.pfx;bdo" >
<!-- module: xhtml-blkphras-1.mod -->
<!ENTITY % address.qname "%XHTML.pfx;address" >
<!ENTITY % blockquote.qname "%XHTML.pfx;blockquote" >
<!ENTITY % pre.qname "%XHTML.pfx;pre" >
<!ENTITY % h1.qname "%XHTML.pfx;h1" >
<!ENTITY % h2.qname "%XHTML.pfx;h2" >
<!ENTITY % h3.qname "%XHTML.pfx;h3" >
<!ENTITY % h4.qname "%XHTML.pfx;h4" >
<!ENTITY % h5.qname "%XHTML.pfx;h5" >
<!ENTITY % h6.qname "%XHTML.pfx;h6" >
<!-- module: xhtml-blkpres-1.mod -->
<!ENTITY % hr.qname "%XHTML.pfx;hr" >
<!-- module: xhtml-blkstruct-1.mod -->
<!ENTITY % div.qname "%XHTML.pfx;div" >
<!ENTITY % p.qname "%XHTML.pfx;p" >
<!-- module: xhtml-edit-1.mod -->
<!ENTITY % ins.qname "%XHTML.pfx;ins" >
<!ENTITY % del.qname "%XHTML.pfx;del" >
<!-- module: xhtml-form-1.mod -->
<!ENTITY % form.qname "%XHTML.pfx;form" >
<!ENTITY % label.qname "%XHTML.pfx;label" >
<!ENTITY % input.qname "%XHTML.pfx;input" >
<!ENTITY % select.qname "%XHTML.pfx;select" >
<!ENTITY % optgroup.qname "%XHTML.pfx;optgroup" >
<!ENTITY % option.qname "%XHTML.pfx;option" >
<!ENTITY % textarea.qname "%XHTML.pfx;textarea" >
<!ENTITY % fieldset.qname "%XHTML.pfx;fieldset" >
<!ENTITY % legend.qname "%XHTML.pfx;legend" >
<!ENTITY % button.qname "%XHTML.pfx;button" >
<!-- module: xhtml-hypertext-1.mod -->
<!ENTITY % a.qname "%XHTML.pfx;a" >
<!-- module: xhtml-image-1.mod -->
<!ENTITY % img.qname "%XHTML.pfx;img" >
<!-- module: xhtml-inlphras-1.mod -->
<!ENTITY % abbr.qname "%XHTML.pfx;abbr" >
<!ENTITY % acronym.qname "%XHTML.pfx;acronym" >
<!ENTITY % cite.qname "%XHTML.pfx;cite" >
<!ENTITY % code.qname "%XHTML.pfx;code" >
<!ENTITY % dfn.qname "%XHTML.pfx;dfn" >
<!ENTITY % em.qname "%XHTML.pfx;em" >
<!ENTITY % kbd.qname "%XHTML.pfx;kbd" >
<!ENTITY % q.qname "%XHTML.pfx;q" >
<!ENTITY % samp.qname "%XHTML.pfx;samp" >
<!ENTITY % strong.qname "%XHTML.pfx;strong" >
<!ENTITY % var.qname "%XHTML.pfx;var" >
<!-- module: xhtml-inlpres-1.mod -->
<!ENTITY % b.qname "%XHTML.pfx;b" >
<!ENTITY % big.qname "%XHTML.pfx;big" >
<!ENTITY % i.qname "%XHTML.pfx;i" >
<!ENTITY % small.qname "%XHTML.pfx;small" >
<!ENTITY % sub.qname "%XHTML.pfx;sub" >
<!ENTITY % sup.qname "%XHTML.pfx;sup" >
<!ENTITY % tt.qname "%XHTML.pfx;tt" >
<!-- module: xhtml-inlstruct-1.mod -->
<!ENTITY % br.qname "%XHTML.pfx;br" >
<!ENTITY % span.qname "%XHTML.pfx;span" >
<!-- module: xhtml-ismap-1.mod (also csismap, ssismap) -->
<!ENTITY % map.qname "%XHTML.pfx;map" >
<!ENTITY % area.qname "%XHTML.pfx;area" >
<!-- module: xhtml-link-1.mod -->
<!ENTITY % link.qname "%XHTML.pfx;link" >
<!-- module: xhtml-list-1.mod -->
<!ENTITY % dl.qname "%XHTML.pfx;dl" >
<!ENTITY % dt.qname "%XHTML.pfx;dt" >
<!ENTITY % dd.qname "%XHTML.pfx;dd" >
<!ENTITY % ol.qname "%XHTML.pfx;ol" >
<!ENTITY % ul.qname "%XHTML.pfx;ul" >
<!ENTITY % li.qname "%XHTML.pfx;li" >
<!-- module: xhtml-meta-1.mod -->
<!ENTITY % meta.qname "%XHTML.pfx;meta" >
<!-- module: xhtml-param-1.mod -->
<!ENTITY % param.qname "%XHTML.pfx;param" >
<!-- module: xhtml-object-1.mod -->
<!ENTITY % object.qname "%XHTML.pfx;object" >
<!-- module: xhtml-script-1.mod -->
<!ENTITY % script.qname "%XHTML.pfx;script" >
<!ENTITY % noscript.qname "%XHTML.pfx;noscript" >
<!-- module: xhtml-struct-1.mod -->
<!ENTITY % html.qname "%XHTML.pfx;html" >
<!ENTITY % head.qname "%XHTML.pfx;head" >
<!ENTITY % title.qname "%XHTML.pfx;title" >
<!ENTITY % body.qname "%XHTML.pfx;body" >
<!-- module: xhtml-style-1.mod -->
<!ENTITY % style.qname "%XHTML.pfx;style" >
<!-- module: xhtml-table-1.mod -->
<!ENTITY % table.qname "%XHTML.pfx;table" >
<!ENTITY % caption.qname "%XHTML.pfx;caption" >
<!ENTITY % thead.qname "%XHTML.pfx;thead" >
<!ENTITY % tfoot.qname "%XHTML.pfx;tfoot" >
<!ENTITY % tbody.qname "%XHTML.pfx;tbody" >
<!ENTITY % colgroup.qname "%XHTML.pfx;colgroup" >
<!ENTITY % col.qname "%XHTML.pfx;col" >
<!ENTITY % tr.qname "%XHTML.pfx;tr" >
<!ENTITY % th.qname "%XHTML.pfx;th" >
<!ENTITY % td.qname "%XHTML.pfx;td" >
<!-- module: xhtml-ruby-1.mod -->
<!ENTITY % ruby.qname "%XHTML.pfx;ruby" >
<!ENTITY % rbc.qname "%XHTML.pfx;rbc" >
<!ENTITY % rtc.qname "%XHTML.pfx;rtc" >
<!ENTITY % rb.qname "%XHTML.pfx;rb" >
<!ENTITY % rt.qname "%XHTML.pfx;rt" >
<!ENTITY % rp.qname "%XHTML.pfx;rp" >
<!-- Provisional XHTML 2.0 Qualified Names ...................... -->
<!-- module: xhtml-image-2.mod -->
<!ENTITY % alt.qname "%XHTML.pfx;alt" >
<!-- end of xhtml-qname-1.mod -->
F.2.6.
XHTML
Character
Entities
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/xhtml-charent-1.mod
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/xhtml-charent-1.mod
.
<!-- ...................................................................... -->
<!-- XHTML Character Entities Module ......................................... -->
<!-- file: xhtml-charent-1.mod
This is XHTML, a reformulation of HTML as a modular XML application.
Copyright 1998-2005 W3C (MIT, ERCIM, Keio), All Rights Reserved.
Revision: $Id: xhtml-charent-1.mod,v 4.0 2001/04/02 22:42:49 altheim Exp $ SMI
This DTD module is identified by the PUBLIC and SYSTEM identifiers:
PUBLIC "-//W3C//ENTITIES XHTML Character Entities 1.0//EN"
SYSTEM "http://www.w3.org/MarkUp/DTD/xhtml-charent-1.mod"
Revisions:
(none)
....................................................................... -->
<!-- Character Entities for XHTML
This module declares the set of character entities for XHTML,
including the Latin 1, Symbol and Special character collections.
-->
<!ENTITY % xhtml-lat1
PUBLIC "-//W3C//ENTITIES Latin 1 for XHTML//EN"
"xhtml-lat1.ent" >
%xhtml-lat1;
<!ENTITY % xhtml-symbol
PUBLIC "-//W3C//ENTITIES Symbols for XHTML//EN"
"xhtml-symbol.ent" >
%xhtml-symbol;
<!ENTITY % xhtml-special
PUBLIC "-//W3C//ENTITIES Special for XHTML//EN"
"xhtml-special.ent" >
%xhtml-special;
<!-- end of xhtml-charent-1.mod -->
F.3.
XHTML
Module
Implementations
This
section
contains
the
formal
definition
of
each
of
the
XHTML
Abstract
Modules
as
a
DTD
module.
F.3.1.
XHTML
Core
Modules
F.3.1.1.
Structure
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/xhtml-struct-1.mod
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/xhtml-struct-1.mod
.
<!-- ...................................................................... -->
<!-- XHTML Structure Module .............................................. -->
<!-- file: xhtml-struct-1.mod
This is XHTML, a reformulation of HTML as a modular XML application.
Copyright 1998-2005 W3C (MIT, ERCIM, Keio), All Rights Reserved.
Revision: $Id: xhtml-struct-1.mod,v 4.0 2001/04/02 22:42:49 altheim Exp $ SMI
This DTD module is identified by the PUBLIC and SYSTEM identifiers:
PUBLIC "-//W3C//ELEMENTS XHTML Document Structure 1.0//EN"
SYSTEM "http://www.w3.org/MarkUp/DTD/xhtml-struct-1.mod"
Revisions:
(none)
....................................................................... -->
<!-- Document Structure
title, head, body, html
The Structure Module defines the major structural elements and
their attributes.
Note that the content model of the head element type is redeclared
when the Base Module is included in the DTD.
The parameter entity containing the XML namespace URI value used
for XHTML is '%XHTML.xmlns;', defined in the Qualified Names module.
-->
<!-- title: Document Title ............................. -->
<!-- The title element is not considered part of the flow of text.
It should be displayed, for example as the page header or
window title. Exactly one title is required per document.
-->
<!ENTITY % title.element "INCLUDE" >
<![%title.element;[
<!ENTITY % title.content "( #PCDATA )" >
<!ENTITY % title.qname "title" >
<!ELEMENT %title.qname; %title.content; >
<!-- end of title.element -->]]>
<!ENTITY % title.attlist "INCLUDE" >
<![%title.attlist;[
<!ATTLIST %title.qname;
%XHTML.xmlns.attrib;
%I18n.attrib;
>
<!-- end of title.attlist -->]]>
<!-- head: Document Head ............................... -->
<!ENTITY % head.element "INCLUDE" >
<![%head.element;[
<!ENTITY % head.content
"( %HeadOpts.mix;, %title.qname;, %HeadOpts.mix; )"
>
<!ENTITY % head.qname "head" >
<!ELEMENT %head.qname; %head.content; >
<!-- end of head.element -->]]>
<!ENTITY % head.attlist "INCLUDE" >
<![%head.attlist;[
<!-- reserved for future use with document profiles
-->
<!ENTITY % profile.attrib
"profile %URIs.datatype; #IMPLIED"
>
<!ATTLIST %head.qname;
%XHTML.xmlns.attrib;
%I18n.attrib;
%profile.attrib;
%id.attrib;
>
<!-- end of head.attlist -->]]>
<!-- body: Document Body ............................... -->
<!ENTITY % body.element "INCLUDE" >
<![%body.element;[
<!ENTITY % body.content
"( %Block.mix; )*"
>
<!ENTITY % body.qname "body" >
<!ELEMENT %body.qname; %body.content; >
<!-- end of body.element -->]]>
<!ENTITY % body.attlist "INCLUDE" >
<![%body.attlist;[
<!ATTLIST %body.qname;
%Common.attrib;
>
<!-- end of body.attlist -->]]>
<!-- html: XHTML Document Element ...................... -->
<!ENTITY % html.element "INCLUDE" >
<![%html.element;[
<!ENTITY % html.content "( %head.qname;, %body.qname; )" >
<!ENTITY % html.qname "html" >
<!ELEMENT %html.qname; %html.content; >
<!-- end of html.element -->]]>
<![%XHTML.xsi.attrs;[
<!-- define a parameter for the XSI schemaLocation attribute -->
<!ENTITY % XSI.schemaLocation.attrib
"%XSI.pfx;schemaLocation %URIs.datatype; #IMPLIED"
>
]]>
<!ENTITY % XSI.schemaLocation.attrib "">
<!ENTITY % html.attlist "INCLUDE" >
<![%html.attlist;[
<!-- version attribute value defined in driver
-->
<!ENTITY % XHTML.version.attrib
"version CDATA #FIXED '%XHTML.version;'"
>
<!-- see the Qualified Names module for information
on how to extend XHTML using XML namespaces
-->
<!ATTLIST %html.qname;
%XHTML.xmlns.attrib;
%XSI.schemaLocation.attrib;
%XHTML.version.attrib;
%I18n.attrib;
%id.attrib;
>
<!-- end of html.attlist -->]]>
<!-- end of xhtml-struct-1.mod -->
F.3.1.2.
Text
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/xhtml-text-1.mod
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/xhtml-text-1.mod
.
<!-- ...................................................................... -->
<!-- XHTML Text Module ................................................... -->
<!-- file: xhtml-text-1.mod
This is XHTML, a reformulation of HTML as a modular XML application.
Copyright 1998-2005 W3C (MIT, ERCIM, Keio), All Rights Reserved.
Revision: $Id: xhtml-text-1.mod,v 4.0 2001/04/02 22:42:49 altheim Exp $ SMI
This DTD module is identified by the PUBLIC and SYSTEM identifiers:
PUBLIC "-//W3C//ELEMENTS XHTML Text 1.0//EN"
SYSTEM "http://www.w3.org/MarkUp/DTD/xhtml-text-1.mod"
Revisions:
(none)
....................................................................... -->
<!-- Textual Content
The Text module includes declarations for all core
text container elements and their attributes.
-->
<!ENTITY % xhtml-inlstruct.module "INCLUDE" >
<![%xhtml-inlstruct.module;[
<!ENTITY % xhtml-inlstruct.mod
PUBLIC "-//W3C//ELEMENTS XHTML Inline Structural 1.0//EN"
"xhtml-inlstruct-1.mod" >
%xhtml-inlstruct.mod;]]>
<!ENTITY % xhtml-inlphras.module "INCLUDE" >
<![%xhtml-inlphras.module;[
<!ENTITY % xhtml-inlphras.mod
PUBLIC "-//W3C//ELEMENTS XHTML Inline Phrasal 1.0//EN"
"xhtml-inlphras-1.mod" >
%xhtml-inlphras.mod;]]>
<!ENTITY % xhtml-blkstruct.module "INCLUDE" >
<![%xhtml-blkstruct.module;[
<!ENTITY % xhtml-blkstruct.mod
PUBLIC "-//W3C//ELEMENTS XHTML Block Structural 1.0//EN"
"xhtml-blkstruct-1.mod" >
%xhtml-blkstruct.mod;]]>
<!ENTITY % xhtml-blkphras.module "INCLUDE" >
<![%xhtml-blkphras.module;[
<!ENTITY % xhtml-blkphras.mod
PUBLIC "-//W3C//ELEMENTS XHTML Block Phrasal 1.0//EN"
"xhtml-blkphras-1.mod" >
%xhtml-blkphras.mod;]]>
<!-- end of xhtml-text-1.mod -->
F.3.1.3.
Hypertext
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/xhtml-hypertext-1.mod
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/xhtml-hypertext-1.mod
.
<!-- ...................................................................... -->
<!-- XHTML Hypertext Module .............................................. -->
<!-- file: xhtml-hypertext-1.mod
This is XHTML, a reformulation of HTML as a modular XML application.
Copyright 1998-2005 W3C (MIT, ERCIM, Keio), All Rights Reserved.
Revision: $Id: xhtml-hypertext-1.mod,v 4.0 2001/04/02 22:42:49 altheim Exp $ SMI
This DTD module is identified by the PUBLIC and SYSTEM identifiers:
PUBLIC "-//W3C//ELEMENTS XHTML Hypertext 1.0//EN"
SYSTEM "http://www.w3.org/MarkUp/DTD/xhtml-hypertext-1.mod"
Revisions:
(none)
....................................................................... -->
<!-- Hypertext
a
This module declares the anchor ('a') element type, which
defines the source of a hypertext link. The destination
(or link 'target') is identified via its 'id' attribute
rather than the 'name' attribute as was used in HTML.
-->
<!-- ............ Anchor Element ............ -->
<!ENTITY % a.element "INCLUDE" >
<![%a.element;[
<!ENTITY % a.content
"( #PCDATA | %InlNoAnchor.mix; )*"
>
<!ENTITY % a.qname "a" >
<!ELEMENT %a.qname; %a.content; >
<!-- end of a.element -->]]>
<!ENTITY % a.attlist "INCLUDE" >
<![%a.attlist;[
<!ATTLIST %a.qname;
%Common.attrib;
href %URI.datatype; #IMPLIED
charset %Charset.datatype; #IMPLIED
type %ContentType.datatype; #IMPLIED
hreflang %LanguageCode.datatype; #IMPLIED
rel %LinkTypes.datatype; #IMPLIED
rev %LinkTypes.datatype; #IMPLIED
accesskey %Character.datatype; #IMPLIED
tabindex %Number.datatype; #IMPLIED
>
<!-- end of a.attlist -->]]>
<!-- end of xhtml-hypertext-1.mod -->
F.3.1.4.
Lists
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/xhtml-list-1.mod
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/xhtml-list-1.mod
.
<!-- ...................................................................... -->
<!-- XHTML Lists Module .................................................. -->
<!-- file: xhtml-list-1.mod
This is XHTML, a reformulation of HTML as a modular XML application.
Copyright 1998-2005 W3C (MIT, ERCIM, Keio), All Rights Reserved.
Revision: $Id: xhtml-list-1.mod,v 4.0 2001/04/02 22:42:49 altheim Exp $ SMI
This DTD module is identified by the PUBLIC and SYSTEM identifiers:
PUBLIC "-//W3C//ELEMENTS XHTML Lists 1.0//EN"
SYSTEM "http://www.w3.org/MarkUp/DTD/xhtml-list-1.mod"
Revisions:
(none)
....................................................................... -->
<!-- Lists
dl, dt, dd, ol, ul, li
This module declares the list-oriented element types
and their attributes.
-->
<!ENTITY % dl.qname "dl" >
<!ENTITY % dt.qname "dt" >
<!ENTITY % dd.qname "dd" >
<!ENTITY % ol.qname "ol" >
<!ENTITY % ul.qname "ul" >
<!ENTITY % li.qname "li" >
<!-- dl: Definition List ............................... -->
<!ENTITY % dl.element "INCLUDE" >
<![%dl.element;[
<!ENTITY % dl.content "( %dt.qname; | %dd.qname; )+" >
<!ELEMENT %dl.qname; %dl.content; >
<!-- end of dl.element -->]]>
<!ENTITY % dl.attlist "INCLUDE" >
<![%dl.attlist;[
<!ATTLIST %dl.qname;
%Common.attrib;
>
<!-- end of dl.attlist -->]]>
<!-- dt: Definition Term ............................... -->
<!ENTITY % dt.element "INCLUDE" >
<![%dt.element;[
<!ENTITY % dt.content
"( #PCDATA | %Inline.mix; )*"
>
<!ELEMENT %dt.qname; %dt.content; >
<!-- end of dt.element -->]]>
<!ENTITY % dt.attlist "INCLUDE" >
<![%dt.attlist;[
<!ATTLIST %dt.qname;
%Common.attrib;
>
<!-- end of dt.attlist -->]]>
<!-- dd: Definition Description ........................ -->
<!ENTITY % dd.element "INCLUDE" >
<![%dd.element;[
<!ENTITY % dd.content
"( #PCDATA | %Flow.mix; )*"
>
<!ELEMENT %dd.qname; %dd.content; >
<!-- end of dd.element -->]]>
<!ENTITY % dd.attlist "INCLUDE" >
<![%dd.attlist;[
<!ATTLIST %dd.qname;
%Common.attrib;
>
<!-- end of dd.attlist -->]]>
<!-- ol: Ordered List (numbered styles) ................ -->
<!ENTITY % ol.element "INCLUDE" >
<![%ol.element;[
<!ENTITY % ol.content "( %li.qname; )+" >
<!ELEMENT %ol.qname; %ol.content; >
<!-- end of ol.element -->]]>
<!ENTITY % ol.attlist "INCLUDE" >
<![%ol.attlist;[
<!ATTLIST %ol.qname;
%Common.attrib;
>
<!-- end of ol.attlist -->]]>
<!-- ul: Unordered List (bullet styles) ................ -->
<!ENTITY % ul.element "INCLUDE" >
<![%ul.element;[
<!ENTITY % ul.content "( %li.qname; )+" >
<!ELEMENT %ul.qname; %ul.content; >
<!-- end of ul.element -->]]>
<!ENTITY % ul.attlist "INCLUDE" >
<![%ul.attlist;[
<!ATTLIST %ul.qname;
%Common.attrib;
>
<!-- end of ul.attlist -->]]>
<!-- li: List Item ..................................... -->
<!ENTITY % li.element "INCLUDE" >
<![%li.element;[
<!ENTITY % li.content
"( #PCDATA | %Flow.mix; )*"
>
<!ELEMENT %li.qname; %li.content; >
<!-- end of li.element -->]]>
<!ENTITY % li.attlist "INCLUDE" >
<![%li.attlist;[
<!ATTLIST %li.qname;
%Common.attrib;
>
<!-- end of li.attlist -->]]>
<!-- end of xhtml-list-1.mod -->
F.3.2.
Applet
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/xhtml-applet-1.mod
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/xhtml-applet-1.mod
.
<!-- ...................................................................... -->
<!-- XHTML Java Applet Module ............................................ -->
<!-- file: xhtml-applet-1.mod
This is XHTML, a reformulation of HTML as a modular XML application.
Copyright 1998-2005 W3C (MIT, ERCIM, Keio), All Rights Reserved.
Revision: $Id: xhtml-applet-1.mod,v 4.0 2001/04/02 22:42:49 altheim Exp $ SMI
This DTD module is identified by the PUBLIC and SYSTEM identifiers:
PUBLIC "-//W3C//ELEMENTS XHTML Java Applets 1.0//EN"
SYSTEM "http://www.w3.org/MarkUp/DTD/xhtml-applet-1.mod"
Revisions:
#2001-02-20: added PCDATA to content model of applet
....................................................................... -->
<!-- Java Applets
applet
This module declares the applet element type and its attributes,
used to provide support for Java applets. The 'alt' attribute is
now required (as it is on images). One of either code or object
attributes must be present. In the document, place param elements
before other content within the <applet> element.
Note that use of this module requires instantiation of the Param
Element Module.
-->
<!-- applet: Java Applet ............................... -->
<!ENTITY % applet.element "INCLUDE" >
<![%applet.element;[
<!ENTITY % applet.content
"( #PCDATA | %param.qname; | %Flow.mix; )*"
>
<!ENTITY % applet.qname "applet" >
<!ELEMENT %applet.qname; %applet.content; >
<!-- end of applet.element -->]]>
<!ENTITY % applet.attlist "INCLUDE" >
<![%applet.attlist;[
<!ATTLIST %applet.qname;
%Core.attrib;
alt %Text.datatype; #REQUIRED
archive CDATA #IMPLIED
code CDATA #IMPLIED
codebase %URI.datatype; #IMPLIED
object CDATA #IMPLIED
width %Length.datatype; #REQUIRED
height %Length.datatype; #REQUIRED
>
<!-- end of applet.attlist -->]]>
<!-- end of xhtml-applet-1.mod -->
F.3.3.
Text
Modules
F.3.3.1.
Presentation
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/xhtml-pres-1.mod
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/xhtml-pres-1.mod
.
<!-- ...................................................................... -->
<!-- XHTML Presentation Module ............................................ -->
<!-- file: xhtml-pres-1.mod
This is XHTML, a reformulation of HTML as a modular XML application.
Copyright 1998-2005 W3C (MIT, ERCIM, Keio), All Rights Reserved.
Revision: $Id: xhtml-pres-1.mod,v 4.0 2001/04/02 22:42:49 altheim Exp $ SMI
This DTD module is identified by the PUBLIC and SYSTEM identifiers:
PUBLIC "-//W3C//ELEMENTS XHTML Presentation 1.0//EN"
SYSTEM "http://www.w3.org/MarkUp/DTD/xhtml-pres-1.mod"
Revisions:
(none)
....................................................................... -->
<!-- Presentational Elements
This module defines elements and their attributes for
simple presentation-related markup.
-->
<!ENTITY % xhtml-inlpres.module "INCLUDE" >
<![%xhtml-inlpres.module;[
<!ENTITY % xhtml-inlpres.mod
PUBLIC "-//W3C//ELEMENTS XHTML Inline Presentation 1.0//EN"
"xhtml-inlpres-1.mod" >
%xhtml-inlpres.mod;]]>
<!ENTITY % xhtml-blkpres.module "INCLUDE" >
<![%xhtml-blkpres.module;[
<!ENTITY % xhtml-blkpres.mod
PUBLIC "-//W3C//ELEMENTS XHTML Block Presentation 1.0//EN"
"xhtml-blkpres-1.mod" >
%xhtml-blkpres.mod;]]>
<!-- end of xhtml-pres-1.mod -->
F.3.3.2.
Edit
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/xhtml-edit-1.mod
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/xhtml-edit-1.mod
.
<!-- ...................................................................... -->
<!-- XHTML Editing Elements Module ....................................... -->
<!-- file: xhtml-edit-1.mod
This is XHTML, a reformulation of HTML as a modular XML application.
Copyright 1998-2005 W3C (MIT, ERCIM, Keio), All Rights Reserved.
Revision: $Id: xhtml-edit-1.mod,v 4.0 2001/04/02 22:42:49 altheim Exp $ SMI
This DTD module is identified by the PUBLIC and SYSTEM identifiers:
PUBLIC "-//W3C//ELEMENTS XHTML Editing Markup 1.0//EN"
SYSTEM "http://www.w3.org/MarkUp/DTD/xhtml-edit-1.mod"
Revisions:
(none)
....................................................................... -->
<!-- Editing Elements
ins, del
This module declares element types and attributes used to indicate
inserted and deleted content while editing a document.
-->
<!-- ins: Inserted Text ............................... -->
<!ENTITY % ins.element "INCLUDE" >
<![%ins.element;[
<!ENTITY % ins.content
"( #PCDATA | %Flow.mix; )*"
>
<!ENTITY % ins.qname "ins" >
<!ELEMENT %ins.qname; %ins.content; >
<!-- end of ins.element -->]]>
<!ENTITY % ins.attlist "INCLUDE" >
<![%ins.attlist;[
<!ATTLIST %ins.qname;
%Common.attrib;
cite %URI.datatype; #IMPLIED
datetime %Datetime.datatype; #IMPLIED
>
<!-- end of ins.attlist -->]]>
<!-- del: Deleted Text ................................ -->
<!ENTITY % del.element "INCLUDE" >
<![%del.element;[
<!ENTITY % del.content
"( #PCDATA | %Flow.mix; )*"
>
<!ENTITY % del.qname "del" >
<!ELEMENT %del.qname; %del.content; >
<!-- end of del.element -->]]>
<!ENTITY % del.attlist "INCLUDE" >
<![%del.attlist;[
<!ATTLIST %del.qname;
%Common.attrib;
cite %URI.datatype; #IMPLIED
datetime %Datetime.datatype; #IMPLIED
>
<!-- end of del.attlist -->]]>
<!-- end of xhtml-edit-1.mod -->
F.3.3.3.
Bi-directional
Text
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/xhtml-bdo-1.mod
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/xhtml-bdo-1.mod
.
<!-- ...................................................................... -->
<!-- XHTML BDO Element Module ............................................. -->
<!-- file: xhtml-bdo-1.mod
This is XHTML, a reformulation of HTML as a modular XML application.
Copyright 1998-2005 W3C (MIT, ERCIM, Keio), All Rights Reserved.
Revision: $Id: xhtml-bdo-1.mod,v 4.0 2001/04/02 22:42:49 altheim Exp $ SMI
This DTD module is identified by the PUBLIC and SYSTEM identifiers:
PUBLIC "-//W3C//ELEMENTS XHTML BDO Element 1.0//EN"
SYSTEM "http://www.w3.org/MarkUp/DTD/xhtml-bdo-1.mod"
Revisions:
(none)
....................................................................... -->
<!-- Bidirectional Override (bdo) Element
This modules declares the element 'bdo', used to override the
Unicode bidirectional algorithm for selected fragments of text.
DEPENDENCIES:
Relies on the conditional section keyword %XHTML.bidi; declared
as "INCLUDE". Bidirectional text support includes both the bdo
element and the 'dir' attribute.
-->
<!ENTITY % bdo.element "INCLUDE" >
<![%bdo.element;[
<!ENTITY % bdo.content
"( #PCDATA | %Inline.mix; )*"
>
<!ENTITY % bdo.qname "bdo" >
<!ELEMENT %bdo.qname; %bdo.content; >
<!-- end of bdo.element -->]]>
<!ENTITY % bdo.attlist "INCLUDE" >
<![%bdo.attlist;[
<!ATTLIST %bdo.qname;
%Core.attrib;
%lang.attrib;
dir ( ltr | rtl ) #REQUIRED
>
]]>
<!-- end of xhtml-bdo-1.mod -->
F.3.4.
Forms
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/xhtml-basic-form-1.mod
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/xhtml-basic-form-1.mod
.
<!-- ...................................................................... -->
<!-- XHTML Simplified Forms Module ....................................... -->
<!-- file: xhtml-basic-form-1.mod
This is XHTML Basic, a proper subset of XHTML.
Copyright 1998-2005 W3C (MIT, ERCIM, Keio), All Rights Reserved.
Revision: $Id: xhtml-basic-form-1.mod,v 4.1 2001/04/05 06:57:40 altheim Exp $ SMI
This DTD module is identified by the PUBLIC and SYSTEM identifiers:
PUBLIC "-//W3C//ELEMENTS XHTML Basic Forms 1.0//EN"
SYSTEM "http://www.w3.org/MarkUp/DTD/xhtml-basic-form-1.mod"
Revisions:
(none)
....................................................................... -->
<!-- Basic Forms
This forms module is based on the HTML 3.2 forms model, with
the WAI-requested addition of the label element. While this
module essentially mimics the content model and attributes of
HTML 3.2 forms, the element types declared herein also include
all HTML 4 common attributes.
form, label, input, select, option, textarea
-->
<!-- declare qualified element type names:
-->
<!ENTITY % form.qname "form" >
<!ENTITY % label.qname "label" >
<!ENTITY % input.qname "input" >
<!ENTITY % select.qname "select" >
<!ENTITY % option.qname "option" >
<!ENTITY % textarea.qname "textarea" >
<!-- %BlkNoForm.mix; includes all non-form block elements,
plus %Misc.class;
-->
<!ENTITY % BlkNoForm.mix
"%Heading.class;
| %List.class;
| %BlkStruct.class;
%BlkPhras.class;
%BlkPres.class;
| %table.qname;
%Block.extra;
%Misc.class;"
>
<!-- form: Form Element ................................ -->
<!ENTITY % form.element "INCLUDE" >
<![%form.element;[
<!ENTITY % form.content
"( %BlkNoForm.mix; )+"
>
<!ELEMENT %form.qname; %form.content; >
<!-- end of form.element -->]]>
<!ENTITY % form.attlist "INCLUDE" >
<![%form.attlist;[
<!ATTLIST %form.qname;
%Common.attrib;
action %URI.datatype; #REQUIRED
method ( get | post ) 'get'
name CDATA #IMPLIED
enctype %ContentType.datatype; 'application/x-www-form-urlencoded'
>
<!-- end of form.attlist -->]]>
<!-- label: Form Field Label Text ...................... -->
<!ENTITY % label.element "INCLUDE" >
<![%label.element;[
<!-- Each label must not contain more than ONE field
-->
<!ENTITY % label.content
"( #PCDATA
| %input.qname; | %select.qname; | %textarea.qname;
| %InlStruct.class;
%InlPhras.class;
%I18n.class;
%InlPres.class;
%InlSpecial.class;
%Misc.class; )*"
>
<!ELEMENT %label.qname; %label.content; >
<!-- end of label.element -->]]>
<!ENTITY % label.attlist "INCLUDE" >
<![%label.attlist;[
<!ATTLIST %label.qname;
%Common.attrib;
for IDREF #IMPLIED
accesskey %Character.datatype; #IMPLIED
>
<!-- end of label.attlist -->]]>
<!-- input: Form Control ............................... -->
<!ENTITY % input.element "INCLUDE" >
<![%input.element;[
<!ENTITY % input.content "EMPTY" >
<!ELEMENT %input.qname; %input.content; >
<!-- end of input.element -->]]>
<!-- Basic Forms removes 'button', 'image' and 'file' input types.
-->
<!ENTITY % input.attlist "INCLUDE" >
<![%input.attlist;[
<!ENTITY % InputType.class
"( text | password | checkbox | radio
| submit | reset | hidden )"
>
<!-- attribute name required for all but submit & reset
-->
<!ATTLIST %input.qname;
%Common.attrib;
type %InputType.class; 'text'
name CDATA #IMPLIED
value CDATA #IMPLIED
checked ( checked ) #IMPLIED
size %Number.datatype; #IMPLIED
maxlength %Number.datatype; #IMPLIED
src %URI.datatype; #IMPLIED
tabindex %Number.datatype; #IMPLIED
accesskey %Character.datatype; #IMPLIED
>
<!-- end of input.attlist -->]]>
<!-- select: Option Selector ........................... -->
<!ENTITY % select.element "INCLUDE" >
<![%select.element;[
<!ENTITY % select.content "( %option.qname; )+" >
<!ELEMENT %select.qname; %select.content; >
<!-- end of select.element -->]]>
<!ENTITY % select.attlist "INCLUDE" >
<![%select.attlist;[
<!ATTLIST %select.qname;
%Common.attrib;
name CDATA #IMPLIED
size %Number.datatype; #IMPLIED
multiple ( multiple ) #IMPLIED
tabindex %Number.datatype; #IMPLIED
>
<!-- end of select.attlist -->]]>
<!-- option: Selectable Choice ......................... -->
<!ENTITY % option.element "INCLUDE" >
<![%option.element;[
<!ENTITY % option.content "( #PCDATA )" >
<!ELEMENT %option.qname; %option.content; >
<!-- end of option.element -->]]>
<!ENTITY % option.attlist "INCLUDE" >
<![%option.attlist;[
<!ATTLIST %option.qname;
%Common.attrib;
selected ( selected ) #IMPLIED
value CDATA #IMPLIED
>
<!-- end of option.attlist -->]]>
<!-- textarea: Multi-Line Text Field ................... -->
<!ENTITY % textarea.element "INCLUDE" >
<![%textarea.element;[
<!ENTITY % textarea.content "( #PCDATA )" >
<!ELEMENT %textarea.qname; %textarea.content; >
<!-- end of textarea.element -->]]>
<!ENTITY % textarea.attlist "INCLUDE" >
<![%textarea.attlist;[
<!ATTLIST %textarea.qname;
%Common.attrib;
name CDATA #IMPLIED
rows %Number.datatype; #REQUIRED
cols %Number.datatype; #REQUIRED
tabindex %Number.datatype; #IMPLIED
accesskey %Character.datatype; #IMPLIED
>
<!-- end of textarea.attlist -->]]>
<!-- end of xhtml-basic-form-1.mod -->
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/xhtml-form-1.mod
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/xhtml-form-1.mod
.
<!-- ...................................................................... -->
<!-- XHTML Forms Module .................................................. -->
<!-- file: xhtml-form-1.mod
This is XHTML, a reformulation of HTML as a modular XML application.
Copyright 1998-2005 W3C (MIT, ERCIM, Keio), All Rights Reserved.
Revision: $Id: xhtml-form-1.mod,v 4.1 2001/04/10 09:42:30 altheim Exp $ SMI
This DTD module is identified by the PUBLIC and SYSTEM identifiers:
PUBLIC "-//W3C//ELEMENTS XHTML Forms 1.0//EN"
SYSTEM "http://www.w3.org/MarkUp/DTD/xhtml-form-1.mod"
Revisions:
(none)
....................................................................... -->
<!-- Forms
form, label, input, select, optgroup, option,
textarea, fieldset, legend, button
This module declares markup to provide support for online
forms, based on the features found in HTML 4 forms.
-->
<!-- declare qualified element type names:
-->
<!ENTITY % form.qname "form" >
<!ENTITY % label.qname "label" >
<!ENTITY % input.qname "input" >
<!ENTITY % select.qname "select" >
<!ENTITY % optgroup.qname "optgroup" >
<!ENTITY % option.qname "option" >
<!ENTITY % textarea.qname "textarea" >
<!ENTITY % fieldset.qname "fieldset" >
<!ENTITY % legend.qname "legend" >
<!ENTITY % button.qname "button" >
<!-- %BlkNoForm.mix; includes all non-form block elements,
plus %Misc.class;
-->
<!ENTITY % BlkNoForm.mix
"%Heading.class;
| %List.class;
| %BlkStruct.class;
%BlkPhras.class;
%BlkPres.class;
%Table.class;
%Block.extra;
%Misc.class;"
>
<!-- form: Form Element ................................ -->
<!ENTITY % form.element "INCLUDE" >
<![%form.element;[
<!ENTITY % form.content
"( %BlkNoForm.mix;
| %fieldset.qname; )+"
>
<!ELEMENT %form.qname; %form.content; >
<!-- end of form.element -->]]>
<!ENTITY % form.attlist "INCLUDE" >
<![%form.attlist;[
<!ATTLIST %form.qname;
%Common.attrib;
action %URI.datatype; #REQUIRED
method ( get | post ) 'get'
name CDATA #IMPLIED
enctype %ContentType.datatype; 'application/x-www-form-urlencoded'
accept-charset %Charsets.datatype; #IMPLIED
accept %ContentTypes.datatype; #IMPLIED
>
<!-- end of form.attlist -->]]>
<!-- label: Form Field Label Text ...................... -->
<!-- Each label must not contain more than ONE field
-->
<!ENTITY % label.element "INCLUDE" >
<![%label.element;[
<!ENTITY % label.content
"( #PCDATA
| %input.qname; | %select.qname; | %textarea.qname; | %button.qname;
| %InlStruct.class;
%InlPhras.class;
%I18n.class;
%InlPres.class;
%Anchor.class;
%InlSpecial.class;
%Inline.extra;
%Misc.class; )*"
>
<!ELEMENT %label.qname; %label.content; >
<!-- end of label.element -->]]>
<!ENTITY % label.attlist "INCLUDE" >
<![%label.attlist;[
<!ATTLIST %label.qname;
%Common.attrib;
for IDREF #IMPLIED
accesskey %Character.datatype; #IMPLIED
>
<!-- end of label.attlist -->]]>
<!-- input: Form Control ............................... -->
<!ENTITY % input.element "INCLUDE" >
<![%input.element;[
<!ENTITY % input.content "EMPTY" >
<!ELEMENT %input.qname; %input.content; >
<!-- end of input.element -->]]>
<!ENTITY % input.attlist "INCLUDE" >
<![%input.attlist;[
<!ENTITY % InputType.class
"( text | password | checkbox | radio | submit
| reset | file | hidden | image | button )"
>
<!-- attribute 'name' required for all but submit & reset
-->
<!ATTLIST %input.qname;
%Common.attrib;
type %InputType.class; 'text'
name CDATA #IMPLIED
value CDATA #IMPLIED
checked ( checked ) #IMPLIED
disabled ( disabled ) #IMPLIED
readonly ( readonly ) #IMPLIED
size %Number.datatype; #IMPLIED
maxlength %Number.datatype; #IMPLIED
src %URI.datatype; #IMPLIED
alt %Text.datatype; #IMPLIED
tabindex %Number.datatype; #IMPLIED
accesskey %Character.datatype; #IMPLIED
accept %ContentTypes.datatype; #IMPLIED
>
<!-- end of input.attlist -->]]>
<!-- select: Option Selector ........................... -->
<!ENTITY % select.element "INCLUDE" >
<![%select.element;[
<!ENTITY % select.content
"( %optgroup.qname; | %option.qname; )+"
>
<!ELEMENT %select.qname; %select.content; >
<!-- end of select.element -->]]>
<!ENTITY % select.attlist "INCLUDE" >
<![%select.attlist;[
<!ATTLIST %select.qname;
%Common.attrib;
name CDATA #IMPLIED
size %Number.datatype; #IMPLIED
multiple ( multiple ) #IMPLIED
disabled ( disabled ) #IMPLIED
tabindex %Number.datatype; #IMPLIED
>
<!-- end of select.attlist -->]]>
<!-- optgroup: Option Group ............................ -->
<!ENTITY % optgroup.element "INCLUDE" >
<![%optgroup.element;[
<!ENTITY % optgroup.content "( %option.qname; )+" >
<!ELEMENT %optgroup.qname; %optgroup.content; >
<!-- end of optgroup.element -->]]>
<!ENTITY % optgroup.attlist "INCLUDE" >
<![%optgroup.attlist;[
<!ATTLIST %optgroup.qname;
%Common.attrib;
disabled ( disabled ) #IMPLIED
label %Text.datatype; #REQUIRED
>
<!-- end of optgroup.attlist -->]]>
<!-- option: Selectable Choice ......................... -->
<!ENTITY % option.element "INCLUDE" >
<![%option.element;[
<!ENTITY % option.content "( #PCDATA )" >
<!ELEMENT %option.qname; %option.content; >
<!-- end of option.element -->]]>
<!ENTITY % option.attlist "INCLUDE" >
<![%option.attlist;[
<!ATTLIST %option.qname;
%Common.attrib;
selected ( selected ) #IMPLIED
disabled ( disabled ) #IMPLIED
label %Text.datatype; #IMPLIED
value CDATA #IMPLIED
>
<!-- end of option.attlist -->]]>
<!-- textarea: Multi-Line Text Field ................... -->
<!ENTITY % textarea.element "INCLUDE" >
<![%textarea.element;[
<!ENTITY % textarea.content "( #PCDATA )" >
<!ELEMENT %textarea.qname; %textarea.content; >
<!-- end of textarea.element -->]]>
<!ENTITY % textarea.attlist "INCLUDE" >
<![%textarea.attlist;[
<!ATTLIST %textarea.qname;
%Common.attrib;
name CDATA #IMPLIED
rows %Number.datatype; #REQUIRED
cols %Number.datatype; #REQUIRED
disabled ( disabled ) #IMPLIED
readonly ( readonly ) #IMPLIED
tabindex %Number.datatype; #IMPLIED
accesskey %Character.datatype; #IMPLIED
>
<!-- end of textarea.attlist -->]]>
<!-- fieldset: Form Control Group ...................... -->
<!-- #PCDATA is to solve the mixed content problem,
per specification only whitespace is allowed
-->
<!ENTITY % fieldset.element "INCLUDE" >
<![%fieldset.element;[
<!ENTITY % fieldset.content
"( #PCDATA | %legend.qname; | %Flow.mix; )*"
>
<!ELEMENT %fieldset.qname; %fieldset.content; >
<!-- end of fieldset.element -->]]>
<!ENTITY % fieldset.attlist "INCLUDE" >
<![%fieldset.attlist;[
<!ATTLIST %fieldset.qname;
%Common.attrib;
>
<!-- end of fieldset.attlist -->]]>
<!-- legend: Fieldset Legend ........................... -->
<!ENTITY % legend.element "INCLUDE" >
<![%legend.element;[
<!ENTITY % legend.content
"( #PCDATA | %Inline.mix; )*"
>
<!ELEMENT %legend.qname; %legend.content; >
<!-- end of legend.element -->]]>
<!ENTITY % legend.attlist "INCLUDE" >
<![%legend.attlist;[
<!ATTLIST %legend.qname;
%Common.attrib;
accesskey %Character.datatype; #IMPLIED
>
<!-- end of legend.attlist -->]]>
<!-- button: Push Button ............................... -->
<!ENTITY % button.element "INCLUDE" >
<![%button.element;[
<!ENTITY % button.content
"( #PCDATA
| %BlkNoForm.mix;
| %InlStruct.class;
%InlPhras.class;
%InlPres.class;
%I18n.class;
%InlSpecial.class;
%Inline.extra; )*"
>
<!ELEMENT %button.qname; %button.content; >
<!-- end of button.element -->]]>
<!ENTITY % button.attlist "INCLUDE" >
<![%button.attlist;[
<!ATTLIST %button.qname;
%Common.attrib;
name CDATA #IMPLIED
value CDATA #IMPLIED
type ( button | submit | reset ) 'submit'
disabled ( disabled ) #IMPLIED
tabindex %Number.datatype; #IMPLIED
accesskey %Character.datatype; #IMPLIED
>
<!-- end of button.attlist -->]]>
<!-- end of xhtml-form-1.mod -->
F.3.5.
Tables
F.3.5.1.
Basic
Tables
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/xhtml-basic-table-1.mod
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/xhtml-basic-table-1.mod
.
<!-- ....................................................................... -->
<!-- XHTML Basic Table Module ............................................. -->
<!-- file: xhtml-basic-table-1.mod
This is XHTML Basic, a proper subset of XHTML.
Copyright 1998-2005 W3C (MIT, ERCIM, Keio), All Rights Reserved.
Revision: $Id: xhtml-basic-table-1.mod,v 4.0 2001/04/02 22:42:49 altheim Exp $ SMI
This DTD module is identified by the PUBLIC and SYSTEM identifiers:
PUBLIC "-//W3C//ELEMENTS XHTML Basic Tables 1.0//EN"
SYSTEM "http://www.w3.org/MarkUp/DTD/xhtml-basic-table-1.mod"
Revisions:
(none)
....................................................................... -->
<!-- Basic Tables
table, caption, tr, th, td
This table module declares elements and attributes defining
a table model based fundamentally on features found in the
widely-deployed HTML 3.2 table model. While this module
mimics the content model and table attributes of HTML 3.2
tables, the element types declared herein also includes all
HTML 4 common and most of the HTML 4 table attributes.
-->
<!-- declare qualified element type names:
-->
<!ENTITY % table.qname "table" >
<!ENTITY % caption.qname "caption" >
<!ENTITY % tr.qname "tr" >
<!ENTITY % th.qname "th" >
<!ENTITY % td.qname "td" >
<!-- horizontal alignment attributes for cell contents
-->
<!ENTITY % CellHAlign.attrib
"align ( left
| center
| right ) #IMPLIED"
>
<!-- vertical alignment attributes for cell contents
-->
<!ENTITY % CellVAlign.attrib
"valign ( top
| middle
| bottom ) #IMPLIED"
>
<!-- scope is simpler than axes attribute for common tables
-->
<!ENTITY % scope.attrib
"scope ( row | col ) #IMPLIED"
>
<!-- table: Table Element .............................. -->
<!ENTITY % table.element "INCLUDE" >
<![%table.element;[
<!ENTITY % table.content
"( %caption.qname;?, %tr.qname;+ )"
>
<!ELEMENT %table.qname; %table.content; >
<!-- end of table.element -->]]>
<!ENTITY % table.attlist "INCLUDE" >
<![%table.attlist;[
<!ATTLIST %table.qname;
%Common.attrib;
summary %Text.datatype; #IMPLIED
width %Length.datatype; #IMPLIED
>
<!-- end of table.attlist -->]]>
<!-- caption: Table Caption ............................ -->
<!ENTITY % caption.element "INCLUDE" >
<![%caption.element;[
<!ENTITY % caption.content
"( #PCDATA | %Inline.mix; )*"
>
<!ELEMENT %caption.qname; %caption.content; >
<!-- end of caption.element -->]]>
<!ENTITY % caption.attlist "INCLUDE" >
<![%caption.attlist;[
<!ATTLIST %caption.qname;
%Common.attrib;
>
<!-- end of caption.attlist -->]]>
<!-- tr: Table Row ..................................... -->
<!ENTITY % tr.element "INCLUDE" >
<![%tr.element;[
<!ENTITY % tr.content "( %th.qname; | %td.qname; )+" >
<!ELEMENT %tr.qname; %tr.content; >
<!-- end of tr.element -->]]>
<!ENTITY % tr.attlist "INCLUDE" >
<![%tr.attlist;[
<!ATTLIST %tr.qname;
%Common.attrib;
%CellHAlign.attrib;
%CellVAlign.attrib;
>
<!-- end of tr.attlist -->]]>
<!-- th: Table Header Cell ............................. -->
<!-- th is for header cells, td for data,
but for cells acting as both use td
-->
<!ENTITY % th.element "INCLUDE" >
<![%th.element;[
<!ENTITY % th.content
"( #PCDATA | %FlowNoTable.mix; )*"
>
<!ELEMENT %th.qname; %th.content; >
<!-- end of th.element -->]]>
<!ENTITY % th.attlist "INCLUDE" >
<![%th.attlist;[
<!ATTLIST %th.qname;
%Common.attrib;
abbr %Text.datatype; #IMPLIED
axis CDATA #IMPLIED
headers IDREFS #IMPLIED
%scope.attrib;
rowspan %Number.datatype; '1'
colspan %Number.datatype; '1'
%CellHAlign.attrib;
%CellVAlign.attrib;
>
<!-- end of th.attlist -->]]>
<!-- td: Table Data Cell ............................... -->
<!ENTITY % td.element "INCLUDE" >
<![%td.element;[
<!ENTITY % td.content
"( #PCDATA | %FlowNoTable.mix; )*"
>
<!ELEMENT %td.qname; %td.content; >
<!-- end of td.element -->]]>
<!ENTITY % td.attlist "INCLUDE" >
<![%td.attlist;[
<!ATTLIST %td.qname;
%Common.attrib;
abbr %Text.datatype; #IMPLIED
axis CDATA #IMPLIED
headers IDREFS #IMPLIED
%scope.attrib;
rowspan %Number.datatype; '1'
colspan %Number.datatype; '1'
%CellHAlign.attrib;
%CellVAlign.attrib;
>
<!-- end of td.attlist -->]]>
<!-- end of xhtml-basic-table-1.mod -->
F.3.5.2.
Tables
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/xhtml-table-1.mod
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/xhtml-table-1.mod
.
<!-- ...................................................................... -->
<!-- XHTML Table Module .................................................. -->
<!-- file: xhtml-table-1.mod
This is XHTML, a reformulation of HTML as a modular XML application.
Copyright 1998-2005 W3C (MIT, ERCIM, Keio), All Rights Reserved.
Revision: $Id: xhtml-table-1.mod,v 4.1 2001/04/10 09:42:30 altheim Exp $ SMI
This DTD module is identified by the PUBLIC and SYSTEM identifiers:
PUBLIC "-//W3C//ELEMENTS XHTML Tables 1.0//EN"
SYSTEM "http://www.w3.org/MarkUp/DTD/xhtml-table-1.mod"
Revisions:
(none)
....................................................................... -->
<!-- Tables
table, caption, thead, tfoot, tbody, colgroup, col, tr, th, td
This module declares element types and attributes used to provide
table markup similar to HTML 4, including features that enable
better accessibility for non-visual user agents.
-->
<!-- declare qualified element type names:
-->
<!ENTITY % table.qname "table" >
<!ENTITY % caption.qname "caption" >
<!ENTITY % thead.qname "thead" >
<!ENTITY % tfoot.qname "tfoot" >
<!ENTITY % tbody.qname "tbody" >
<!ENTITY % colgroup.qname "colgroup" >
<!ENTITY % col.qname "col" >
<!ENTITY % tr.qname "tr" >
<!ENTITY % th.qname "th" >
<!ENTITY % td.qname "td" >
<!-- The frame attribute specifies which parts of the frame around
the table should be rendered. The values are not the same as
CALS to avoid a name clash with the valign attribute.
-->
<!ENTITY % frame.attrib
"frame ( void
| above
| below
| hsides
| lhs
| rhs
| vsides
| box
| border ) #IMPLIED"
>
<!-- The rules attribute defines which rules to draw between cells:
If rules is absent then assume:
"none" if border is absent or border="0" otherwise "all"
-->
<!ENTITY % rules.attrib
"rules ( none
| groups
| rows
| cols
| all ) #IMPLIED"
>
<!-- horizontal alignment attributes for cell contents
-->
<!ENTITY % CellHAlign.attrib
"align ( left
| center
| right
| justify
| char ) #IMPLIED
char %Character.datatype; #IMPLIED
charoff %Length.datatype; #IMPLIED"
>
<!-- vertical alignment attribute for cell contents
-->
<!ENTITY % CellVAlign.attrib
"valign ( top
| middle
| bottom
| baseline ) #IMPLIED"
>
<!-- scope is simpler than axes attribute for common tables
-->
<!ENTITY % scope.attrib
"scope ( row
| col
| rowgroup
| colgroup ) #IMPLIED"
>
<!-- table: Table Element .............................. -->
<!ENTITY % table.element "INCLUDE" >
<![%table.element;[
<!ENTITY % table.content
"( %caption.qname;?, ( %col.qname;* | %colgroup.qname;* ),
(( %thead.qname;?, %tfoot.qname;?, %tbody.qname;+ ) | ( %tr.qname;+ )))"
>
<!ELEMENT %table.qname; %table.content; >
<!-- end of table.element -->]]>
<!ENTITY % table.attlist "INCLUDE" >
<![%table.attlist;[
<!ATTLIST %table.qname;
%Common.attrib;
summary %Text.datatype; #IMPLIED
width %Length.datatype; #IMPLIED
border %Pixels.datatype; #IMPLIED
%frame.attrib;
%rules.attrib;
cellspacing %Length.datatype; #IMPLIED
cellpadding %Length.datatype; #IMPLIED
>
<!-- end of table.attlist -->]]>
<!-- caption: Table Caption ............................ -->
<!ENTITY % caption.element "INCLUDE" >
<![%caption.element;[
<!ENTITY % caption.content
"( #PCDATA | %Inline.mix; )*"
>
<!ELEMENT %caption.qname; %caption.content; >
<!-- end of caption.element -->]]>
<!ENTITY % caption.attlist "INCLUDE" >
<![%caption.attlist;[
<!ATTLIST %caption.qname;
%Common.attrib;
>
<!-- end of caption.attlist -->]]>
<!-- thead: Table Header ............................... -->
<!-- Use thead to duplicate headers when breaking table
across page boundaries, or for static headers when
tbody sections are rendered in scrolling panel.
-->
<!ENTITY % thead.element "INCLUDE" >
<![%thead.element;[
<!ENTITY % thead.content "( %tr.qname; )+" >
<!ELEMENT %thead.qname; %thead.content; >
<!-- end of thead.element -->]]>
<!ENTITY % thead.attlist "INCLUDE" >
<![%thead.attlist;[
<!ATTLIST %thead.qname;
%Common.attrib;
%CellHAlign.attrib;
%CellVAlign.attrib;
>
<!-- end of thead.attlist -->]]>
<!-- tfoot: Table Footer ............................... -->
<!-- Use tfoot to duplicate footers when breaking table
across page boundaries, or for static footers when
tbody sections are rendered in scrolling panel.
-->
<!ENTITY % tfoot.element "INCLUDE" >
<![%tfoot.element;[
<!ENTITY % tfoot.content "( %tr.qname; )+" >
<!ELEMENT %; %tfoot.content; >
<!-- end of tfoot.element -->]]>
<!ENTITY % tfoot.attlist "INCLUDE" >
<![%tfoot.attlist;[
<!ATTLIST %tfoot.qname;
%Common.attrib;
%CellHAlign.attrib;
%CellVAlign.attrib;
>
<!-- end of tfoot.attlist -->]]>
<!-- tbody: Table Body ................................. -->
<!-- Use multiple tbody sections when rules are needed
between groups of table rows.
-->
<!ENTITY % tbody.element "INCLUDE" >
<![%tbody.element;[
<!ENTITY % tbody.content "( %tr.qname; )+" >
<!ELEMENT %tbody.qname; %tbody.content; >
<!-- end of tbody.element -->]]>
<!ENTITY % tbody.attlist "INCLUDE" >
<![%tbody.attlist;[
<!ATTLIST %tbody.qname;
%Common.attrib;
%CellHAlign.attrib;
%CellVAlign.attrib;
>
<!-- end of tbody.attlist -->]]>
<!-- colgroup: Table Column Group ...................... -->
<!-- colgroup groups a set of col elements. It allows you
to group several semantically-related columns together.
-->
<!ENTITY % colgroup.element "INCLUDE" >
<![%colgroup.element;[
<!ENTITY % colgroup.content "( %col.qname; )*" >
<!ELEMENT %colgroup.qname; %colgroup.content; >
<!-- end of colgroup.element -->]]>
<!ENTITY % colgroup.attlist "INCLUDE" >
<![%colgroup.attlist;[
<!ATTLIST %colgroup.qname;
%Common.attrib;
span %Number.datatype; '1'
width %MultiLength.datatype; #IMPLIED
%CellHAlign.attrib;
%CellVAlign.attrib;
>
<!-- end of colgroup.attlist -->]]>
<!-- col: Table Column ................................. -->
<!-- col elements define the alignment properties for
cells in one or more columns.
The width attribute specifies the width of the
columns, e.g.
width="64" width in screen pixels
width="0.5*" relative width of 0.5
The span attribute causes the attributes of one
col element to apply to more than one column.
-->
<!ENTITY % col.element "INCLUDE" >
<![%col.element;[
<!ENTITY % col.content "EMPTY" >
<!ELEMENT %col.qname; %col.content; >
<!-- end of col.element -->]]>
<!ENTITY % col.attlist "INCLUDE" >
<![%col.attlist;[
<!ATTLIST %col.qname;
%Common.attrib;
span %Number.datatype; '1'
width %MultiLength.datatype; #IMPLIED
%CellHAlign.attrib;
%CellVAlign.attrib;
>
<!-- end of col.attlist -->]]>
<!-- tr: Table Row ..................................... -->
<!ENTITY % tr.element "INCLUDE" >
<![%tr.element;[
<!ENTITY % tr.content "( %th.qname; | %td.qname; )+" >
<!ELEMENT %tr.qname; %tr.content; >
<!-- end of tr.element -->]]>
<!ENTITY % tr.attlist "INCLUDE" >
<![%tr.attlist;[
<!ATTLIST %tr.qname;
%Common.attrib;
%CellHAlign.attrib;
%CellVAlign.attrib;
>
<!-- end of tr.attlist -->]]>
<!-- th: Table Header Cell ............................. -->
<!-- th is for header cells, td for data,
but for cells acting as both use td
-->
<!ENTITY % th.element "INCLUDE" >
<![%th.element;[
<!ENTITY % th.content
"( #PCDATA | %Flow.mix; )*"
>
<!ELEMENT %th.qname; %th.content; >
<!-- end of th.element -->]]>
<!ENTITY % th.attlist "INCLUDE" >
<![%th.attlist;[
<!ATTLIST %th.qname;
%Common.attrib;
abbr %Text.datatype; #IMPLIED
axis CDATA #IMPLIED
headers IDREFS #IMPLIED
%scope.attrib;
rowspan %Number.datatype; '1'
colspan %Number.datatype; '1'
%CellHAlign.attrib;
%CellVAlign.attrib;
>
<!-- end of th.attlist -->]]>
<!-- td: Table Data Cell ............................... -->
<!ENTITY % td.element "INCLUDE" >
<![%td.element;[
<!ENTITY % td.content
"( #PCDATA | %Flow.mix; )*"
>
<!ELEMENT %td.qname; %td.content; >
<!-- end of td.element -->]]>
<!ENTITY % td.attlist "INCLUDE" >
<![%td.attlist;[
<!ATTLIST %td.qname;
%Common.attrib;
abbr %Text.datatype; #IMPLIED
axis CDATA #IMPLIED
headers IDREFS #IMPLIED
%scope.attrib;
rowspan %Number.datatype; '1'
colspan %Number.datatype; '1'
%CellHAlign.attrib;
%CellVAlign.attrib;
>
<!-- end of td.attlist -->]]>
<!-- end of xhtml-table-1.mod -->
F.3.6.
Image
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/xhtml-image-1.mod
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/xhtml-image-1.mod
.
<!-- ...................................................................... -->
<!-- XHTML Images Module ................................................. -->
<!-- file: xhtml-image-1.mod
This is XHTML, a reformulation of HTML as a modular XML application.
Copyright 1998-2005 W3C (MIT, ERCIM, Keio), All Rights Reserved.
Rovision: $Id: xhtml-image-1.mod,v 4.0 2001/04/02 22:42:49 altheim Exp $ SMI
This DTD module is identified by the PUBLIC and SYSTEM identifiers:
PUBLIC "-//W3C//ELEMENTS XHTML Images 1.0//EN"
SYSTEM "http://www.w3.org/MarkUp/DTD/xhtml-image-1.mod"
Revisions:
(none)
....................................................................... -->
<!-- Images
img
This module provides markup to support basic image embedding.
-->
<!-- To avoid problems with text-only UAs as well as to make
image content understandable and navigable to users of
non-visual UAs, you need to provide a description with
the 'alt' attribute, and avoid server-side image maps.
-->
<!ENTITY % img.element "INCLUDE" >
<![%img.element;[
<!ENTITY % img.content "EMPTY" >
<!ENTITY % img.qname "img" >
<!ELEMENT %img.qname; %img.content; >
<!-- end of img.element -->]]>
<!ENTITY % img.attlist "INCLUDE" >
<![%img.attlist;[
<!ATTLIST %img.qname;
%Common.attrib;
src %URI.datatype; #REQUIRED
alt %Text.datatype; #REQUIRED
longdesc %URI.datatype; #IMPLIED
name CDATA #IMPLIED
height %Length.datatype; #IMPLIED
width %Length.datatype; #IMPLIED
>
<!-- end of img.attlist -->]]>
<!-- end of xhtml-image-1.mod -->
F.3.7.
Client-side
Image
Map
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/xhtml-csismap-1.mod
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/xhtml-csismap-1.mod
.
<!-- ...................................................................... -->
<!-- XHTML Client-side Image Map Module .................................. -->
<!-- file: xhtml-csismap-1.mod
This is XHTML, a reformulation of HTML as a modular XML application.
Copyright 1998-2005 W3C (MIT, ERCIM, Keio), All Rights Reserved.
Revision: $Id: xhtml-csismap-1.mod,v 4.0 2001/04/02 22:42:49 altheim Exp $ SMI
This DTD module is identified by the PUBLIC and SYSTEM identifiers:
PUBLIC "-//W3C//ELEMENTS XHTML Client-side Image Maps 1.0//EN"
SYSTEM "http://www.w3.org/MarkUp/DTD/xhtml-csismap-1.mod"
Revisions:
(none)
....................................................................... -->
<!-- Client-side Image Maps
area, map
This module declares elements and attributes to support client-side
image maps. This requires that the Image Module (or a module
declaring the img element type) be included in the DTD.
These can be placed in the same document or grouped in a
separate document, although the latter isn't widely supported
-->
<!ENTITY % area.element "INCLUDE" >
<![%area.element;[
<!ENTITY % area.content "EMPTY" >
<!ENTITY % area.qname "area" >
<!ELEMENT %area.qname; %area.content; >
<!-- end of area.element -->]]>
<!ENTITY % Shape.datatype "( rect | circle | poly | default )">
<!ENTITY % Coords.datatype "CDATA" >
<!ENTITY % area.attlist "INCLUDE" >
<![%area.attlist;[
<!ATTLIST %area.qname;
%Common.attrib;
href %URI.datatype; #IMPLIED
shape %Shape.datatype; 'rect'
coords %Coords.datatype; #IMPLIED
nohref ( nohref ) #IMPLIED
alt %Text.datatype; #REQUIRED
tabindex %Number.datatype; #IMPLIED
accesskey %Character.datatype; #IMPLIED
>
<!-- end of area.attlist -->]]>
<!-- modify anchor attribute definition list
to allow for client-side image maps
-->
<!ATTLIST %a.qname;
shape %Shape.datatype; 'rect'
coords %Coords.datatype; #IMPLIED
>
<!-- modify img attribute definition list
to allow for client-side image maps
-->
<!ATTLIST %img.qname;
usemap %URIREF.datatype; #IMPLIED
>
<!-- modify form input attribute definition list
to allow for client-side image maps
-->
<!ATTLIST %input.qname;
usemap %URIREF.datatype; #IMPLIED
>
<!-- modify object attribute definition list
to allow for client-side image maps
-->
<!ATTLIST %object.qname;
usemap %URIREF.datatype; #IMPLIED
>
<!-- 'usemap' points to the 'id' attribute of a <map> element,
which must be in the same document; support for external
document maps was not widely supported in HTML and is
eliminated in XHTML.
It is considered an error for the element pointed to by
a usemap URIREF to occur in anything but a <map> element.
-->
<!ENTITY % map.element "INCLUDE" >
<![%map.element;[
<!ENTITY % map.content
"(( %Block.mix; ) | %area.qname; )+"
>
<!ENTITY % map.qname "map" >
<!ELEMENT %map.qname; %map.content; >
<!-- end of map.element -->]]>
<!ENTITY % map.attlist "INCLUDE" >
<![%map.attlist;[
<!ATTLIST %map.qname;
%XHTML.xmlns.attrib;
id ID #REQUIRED
%class.attrib;
%title.attrib;
%Core.extra.attrib;
%I18n.attrib;
%Events.attrib;
>
<!-- end of map.attlist -->]]>
<!-- end of xhtml-csismap-1.mod -->
F.3.8.
Server-side
Image
Map
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/xhtml-ssismap-1.mod
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/xhtml-ssismap-1.mod
.
<!-- ...................................................................... -->
<!-- XHTML Server-side Image Map Module .................................. -->
<!-- file: xhtml-ssismap-1.mod
This is XHTML, a reformulation of HTML as a modular XML application.
Copyright 1998-2005 W3C (MIT, ERCIM, Keio), All Rights Reserved.
Revision: $Id: xhtml-ssismap-1.mod,v 4.0 2001/04/02 22:42:49 altheim Exp $ SMI
This DTD module is identified by the PUBLIC and SYSTEM identifiers:
PUBLIC "-//W3C//ELEMENTS XHTML Server-side Image Maps 1.0//EN"
SYSTEM "http://www.w3.org/MarkUp/DTD/xhtml-ssismap-1.mod"
Revisions:
#2000-10-22: added declaration for 'ismap' on <input>
....................................................................... -->
<!-- Server-side Image Maps
This adds the 'ismap' attribute to the img and input elements
to support server-side processing of a user selection.
-->
<!ATTLIST %img.qname;
ismap ( ismap ) #IMPLIED
>
<!ATTLIST %input.qname;
ismap ( ismap ) #IMPLIED
>
<!-- end of xhtml-ssismap-1.mod -->
F.3.9.
Object
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/xhtml-object-1.mod
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/xhtml-object-1.mod
.
<!-- ...................................................................... -->
<!-- XHTML Embedded Object Module ........................................ -->
<!-- file: xhtml-object-1.mod
This is XHTML, a reformulation of HTML as a modular XML application.
Copyright 1998-2005 W3C (MIT, ERCIM, Keio), All Rights Reserved.
Revision: $Id: xhtml-object-1.mod,v 4.0 2001/04/02 22:42:49 altheim Exp $ SMI
This DTD module is identified by the PUBLIC and SYSTEM identifiers:
PUBLIC "-//W3C//ELEMENTS XHTML Embedded Object 1.0//EN"
SYSTEM "http://www.w3.org/MarkUp/DTD/xhtml-object-1.mod"
Revisions:
(none)
....................................................................... -->
<!-- Embedded Objects
object
This module declares the object element type and its attributes, used
to embed external objects as part of XHTML pages. In the document,
place param elements prior to other content within the object element.
Note that use of this module requires instantiation of the Param
Element Module.
-->
<!-- object: Generic Embedded Object ................... -->
<!ENTITY % object.element "INCLUDE" >
<![%object.element;[
<!ENTITY % object.content
"( #PCDATA | %Flow.mix; | %param.qname; )*"
>
<!ENTITY % object.qname "object" >
<!ELEMENT %object.qname; %object.content; >
<!-- end of object.element -->]]>
<!ENTITY % object.attlist "INCLUDE" >
<![%object.attlist;[
<!ATTLIST %object.qname;
%Common.attrib;
declare ( declare ) #IMPLIED
classid %URI.datatype; #IMPLIED
codebase %URI.datatype; #IMPLIED
data %URI.datatype; #IMPLIED
type %ContentType.datatype; #IMPLIED
codetype %ContentType.datatype; #IMPLIED
archive %URIs.datatype; #IMPLIED
standby %Text.datatype; #IMPLIED
height %Length.datatype; #IMPLIED
width %Length.datatype; #IMPLIED
name CDATA #IMPLIED
tabindex %Number.datatype; #IMPLIED
>
<!-- end of object.attlist -->]]>
<!-- end of xhtml-object-1.mod -->
F.3.10.
Frames
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/xhtml-frames-1.mod
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/xhtml-frames-1.mod
.
<!-- ...................................................................... -->
<!-- XHTML Frames Module ................................................. -->
<!-- file: xhtml-frames-1.mod
This is XHTML, a reformulation of HTML as a modular XML application.
Copyright 1998-2005 W3C (MIT, ERCIM, Keio), All Rights Reserved.
Revision: $Id: xhtml-frames-1.mod,v 4.0 2001/04/02 22:42:49 altheim Exp $ SMI
This DTD module is identified by the PUBLIC and SYSTEM identifiers:
PUBLIC "-//W3C//ELEMENTS XHTML Frames 1.0//EN"
SYSTEM "http://www.w3.org/MarkUp/DTD/xhtml-frames-1.mod"
Revisions:
(none)
....................................................................... -->
<!-- Frames
frameset, frame, noframes
This module declares frame-related element types and attributes.
-->
<!ENTITY % frameset.qname "frameset" >
<!ENTITY % frame.qname "frame" >
<!ENTITY % noframes.qname "noframes" >
<!-- comma-separated list of MultiLength -->
<!ENTITY % MultiLengths.datatype "CDATA" >
<!-- The content model for XHTML documents depends on whether
the <head> is followed by a <frameset> or <body> element.
-->
<!ENTITY % frameset.element "INCLUDE" >
<![%frameset.element;[
<!ENTITY % frameset.content
"(( %frameset.qname; | %frame.qname; )+, %noframes.qname;? )" >
<!ELEMENT %frameset.qname; %frameset.content; >
<!-- end of frameset.element -->]]>
<!ENTITY % frameset.attlist "INCLUDE" >
<![%frameset.attlist;[
<!ATTLIST %frameset.qname;
%Core.attrib;
rows %MultiLengths.datatype; #IMPLIED
cols %MultiLengths.datatype; #IMPLIED
>
<!-- end of frameset.attlist -->]]>
<![%xhtml-events.module;[
<!ATTLIST %frameset.qname;
onload %Script.datatype; #IMPLIED
onunload %Script.datatype; #IMPLIED
>
]]>
<!-- reserved frame names start with "_" otherwise starts with letter -->
<!ENTITY % frame.element "INCLUDE" >
<![%frame.element;[
<!ENTITY % frame.content "EMPTY" >
<!ELEMENT %frame.qname; %frame.content; >
<!-- end of frame.element -->]]>
<!ENTITY % frame.attlist "INCLUDE" >
<![%frame.attlist;[
<!ATTLIST %frame.qname;
%Core.attrib;
longdesc %URI.datatype; #IMPLIED
src %URI.datatype; #IMPLIED
frameborder ( 1 | 0 ) '1'
marginwidth %Pixels.datatype; #IMPLIED
marginheight %Pixels.datatype; #IMPLIED
noresize ( noresize ) #IMPLIED
scrolling ( yes | no | auto ) 'auto'
>
<!-- end of frame.attlist -->]]>
<!-- changes to other declarations .................... -->
<!-- redefine content model for html element,
substituting frameset for body -->
<!ENTITY % html.content
"( %head.qname;, %frameset.qname; )"
>
<!-- alternate content container for non frame-based rendering -->
<!ENTITY % noframes.element "INCLUDE" >
<![%noframes.element;[
<!ENTITY % noframes.content "( %body.qname; )">
<!ELEMENT %noframes.qname; %noframes.content; >
<!-- end of noframes.element -->]]>
<!ENTITY % noframes.attlist "INCLUDE" >
<![%noframes.attlist;[
<!ATTLIST %noframes.qname;
%Common.attrib;
>
<!-- end of noframes.attlist -->]]>
<!-- end of xhtml-frames-1.mod -->
F.3.11.
Target
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/xhtml-target-1.mod
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/xhtml-target-1.mod
.
<!-- ...................................................................... -->
<!-- XHTML Target Module ................................................. -->
<!-- file: xhtml-target-1.mod
This is XHTML, a reformulation of HTML as a modular XML application.
Copyright 1998-2005 W3C (MIT, ERCIM, Keio), All Rights Reserved.
Revision: $Id: xhtml-target-1.mod,v 4.0 2001/04/02 22:42:49 altheim Exp $ SMI
This DTD module is identified by the PUBLIC and SYSTEM identifiers:
PUBLIC "-//W3C//ELEMENTS XHTML Target 1.0//EN"
SYSTEM "http://www.w3.org/MarkUp/DTD/xhtml-target-1.mod"
Revisions:
(none)
....................................................................... -->
<!-- Target
target
This module declares the 'target' attribute used for opening windows
-->
<!-- render in this frame -->
<!ENTITY % FrameTarget.datatype "CDATA" >
<!-- add 'target' attribute to 'a' element -->
<!ATTLIST %a.qname;
target %FrameTarget.datatype; #IMPLIED
>
<!-- add 'target' attribute to 'area' element -->
<!ATTLIST %area.qname;
target %FrameTarget.datatype; #IMPLIED
>
<!-- add 'target' attribute to 'link' element -->
<!ATTLIST %link.qname;
target %FrameTarget.datatype; #IMPLIED
>
<!-- add 'target' attribute to 'form' element -->
<!ATTLIST %form.qname;
target %FrameTarget.datatype; #IMPLIED
>
<!-- add 'target' attribute to 'base' element -->
<!ATTLIST %base.qname;
target %FrameTarget.datatype; #IMPLIED
>
<!-- end of xhtml-target-1.mod -->
F.3.12.
Iframe
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/xhtml-iframe-1.mod
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/xhtml-iframe-1.mod
.
<!-- ...................................................................... -->
<!-- XHTML IFrame Module ................................................. -->
<!-- file: xhtml-iframe-1.mod
This is XHTML, a reformulation of HTML as a modular XML application.
Copyright 1998-2005 W3C (MIT, ERCIM, Keio), All Rights Reserved.
Revision: $Id: xhtml-iframe-1.mod,v 4.0 2001/04/02 22:42:49 altheim Exp $ SMI
This DTD module is identified by the PUBLIC and SYSTEM identifiers:
PUBLIC "-//W3C//ELEMENTS XHTML Inline Frame Element 1.0//EN"
SYSTEM "http://www.w3.org/MarkUp/DTD/xhtml-iframe-1.mod"
Revisions:
#2000-10-22: added #PCDATA to <iframe> content model as per HTML 4
....................................................................... -->
<!-- Inline Frames
iframe
This module declares the iframe element type and its attributes,
used to create an inline frame within a document.
-->
<!-- Inline Frames .................................... -->
<!ENTITY % iframe.content "( #PCDATA | %Flow.mix; )*" >
<!ENTITY % iframe.qname "iframe" >
<!ELEMENT %iframe.qname; %iframe.content; >
<!ATTLIST %iframe.qname;
%Core.attrib;
longdesc %URI.datatype; #IMPLIED
src %URI.datatype; #IMPLIED
frameborder ( 1 | 0 ) '1'
marginwidth %Pixels.datatype; #IMPLIED
marginheight %Pixels.datatype; #IMPLIED
scrolling ( yes | no | auto ) 'auto'
height %Length.datatype; #IMPLIED
width %Length.datatype; #IMPLIED
>
<!-- end of xhtml-iframe-1.mod -->
F.3.13.
Intrinsic
Events
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/xhtml-events-1.mod
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/xhtml-events-1.mod
.
<!-- ...................................................................... -->
<!-- XHTML Intrinsic Events Module ....................................... -->
<!-- file: xhtml-events-1.mod
This is XHTML, a reformulation of HTML as a modular XML application.
Copyright 1998-2005 W3C (MIT, ERCIM, Keio), All Rights Reserved.
Revision: $Id: xhtml-events-1.mod,v 4.1 2001/04/10 09:42:30 altheim Exp $ SMI
This DTD module is identified by the PUBLIC and SYSTEM identifiers:
PUBLIC "-//W3C//ENTITIES XHTML Intrinsic Events 1.0//EN"
SYSTEM "http://www.w3.org/MarkUp/DTD/xhtml-events-1.mod"
Revisions:
(none)
....................................................................... -->
<!-- Intrinsic Event Attributes
These are the event attributes defined in HTML 4,
Section 18.2.3 "Intrinsic Events". This module must be
instantiated prior to the Attributes Module but after
the Datatype Module in the Modular Framework module.
"Note: Authors of HTML documents are advised that changes
are likely to occur in the realm of intrinsic events
(e.g., how scripts are bound to events). Research in
this realm is carried on by members of the W3C Document
Object Model Working Group (see the W3C Web site at
http://www.w3.org/ for more information)."
-->
<!-- NOTE: Because the ATTLIST declarations in this module occur
before their respective ELEMENT declarations in other
modules, there may be a dependency on this module that
should be considered if any of the parameter entities used
for element type names (eg., %a.qname;) are redeclared.
-->
<!ENTITY % Events.attrib
"onclick %Script.datatype; #IMPLIED
ondblclick %Script.datatype; #IMPLIED
onmousedown %Script.datatype; #IMPLIED
onmouseup %Script.datatype; #IMPLIED
onmouseover %Script.datatype; #IMPLIED
onmousemove %Script.datatype; #IMPLIED
onmouseout %Script.datatype; #IMPLIED
onkeypress %Script.datatype; #IMPLIED
onkeydown %Script.datatype; #IMPLIED
onkeyup %Script.datatype; #IMPLIED"
>
<![%XHTML.global.attrs.prefixed;[
<!ENTITY % XHTML.global.events.attrib
"%XHTML.prefix;:onclick %Script.datatype; #IMPLIED
%XHTML.prefix;:ondblclick %Script.datatype; #IMPLIED
%XHTML.prefix;:onmousedown %Script.datatype; #IMPLIED
%XHTML.prefix;:onmouseup %Script.datatype; #IMPLIED
%XHTML.prefix;:onmouseover %Script.datatype; #IMPLIED
%XHTML.prefix;:onmousemove %Script.datatype; #IMPLIED
%XHTML.prefix;:onmouseout %Script.datatype; #IMPLIED
%XHTML.prefix;:onkeypress %Script.datatype; #IMPLIED
%XHTML.prefix;:onkeydown %Script.datatype; #IMPLIED
%XHTML.prefix;:onkeyup %Script.datatype; #IMPLIED"
>
]]>
<!-- additional attributes on anchor element
-->
<!ATTLIST %a.qname;
onfocus %Script.datatype; #IMPLIED
onblur %Script.datatype; #IMPLIED
>
<!-- additional attributes on form element
-->
<!ATTLIST %form.qname;
onsubmit %Script.datatype; #IMPLIED
onreset %Script.datatype; #IMPLIED
>
<!-- additional attributes on label element
-->
<!ATTLIST %label.qname;
onfocus %Script.datatype; #IMPLIED
onblur %Script.datatype; #IMPLIED
>
<!-- additional attributes on input element
-->
<!ATTLIST %input.qname;
onfocus %Script.datatype; #IMPLIED
onblur %Script.datatype; #IMPLIED
onselect %Script.datatype; #IMPLIED
onchange %Script.datatype; #IMPLIED
>
<!-- additional attributes on select element
-->
<!ATTLIST %select.qname;
onfocus %Script.datatype; #IMPLIED
onblur %Script.datatype; #IMPLIED
onchange %Script.datatype; #IMPLIED
>
<!-- additional attributes on textarea element
-->
<!ATTLIST %textarea.qname;
onfocus %Script.datatype; #IMPLIED
onblur %Script.datatype; #IMPLIED
onselect %Script.datatype; #IMPLIED
onchange %Script.datatype; #IMPLIED
>
<!-- additional attributes on button element
-->
<!ATTLIST %button.qname;
onfocus %Script.datatype; #IMPLIED
onblur %Script.datatype; #IMPLIED
>
<!-- additional attributes on body element
-->
<!ATTLIST %body.qname;
onload %Script.datatype; #IMPLIED
onunload %Script.datatype; #IMPLIED
>
<!-- additional attributes on area element
-->
<!ATTLIST %area.qname;
onfocus %Script.datatype; #IMPLIED
onblur %Script.datatype; #IMPLIED
>
<!-- end of xhtml-events-1.mod -->
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/xhtml-meta-1.mod
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/xhtml-meta-1.mod
.
<!-- ...................................................................... -->
<!-- XHTML Document Metainformation Module ............................... -->
<!-- file: xhtml-meta-1.mod
This is XHTML, a reformulation of HTML as a modular XML application.
Copyright 1998-2005 W3C (MIT, ERCIM, Keio), All Rights Reserved.
Revision: $Id: xhtml-meta-1.mod,v 4.0 2001/04/02 22:42:49 altheim Exp $ SMI
This DTD module is identified by the PUBLIC and SYSTEM identifiers:
PUBLIC "-//W3C//ELEMENTS XHTML Metainformation 1.0//EN"
SYSTEM "http://www.w3.org/MarkUp/DTD/xhtml-meta-1.mod"
Revisions:
(none)
....................................................................... -->
<!-- Meta Information
meta
This module declares the meta element type and its attributes,
used to provide declarative document metainformation.
-->
<!-- meta: Generic Metainformation ..................... -->
<!ENTITY % meta.element "INCLUDE" >
<![%meta.element;[
<!ENTITY % meta.content "EMPTY" >
<!ENTITY % meta.qname "meta" >
<!ELEMENT %meta.qname; %meta.content; >
<!-- end of meta.element -->]]>
<!ENTITY % meta.attlist "INCLUDE" >
<![%meta.attlist;[
<!ATTLIST %meta.qname;
%XHTML.xmlns.attrib;
%I18n.attrib;
http-equiv NMTOKEN #IMPLIED
name NMTOKEN #IMPLIED
content CDATA #REQUIRED
scheme CDATA #IMPLIED
>
<!-- end of meta.attlist -->]]>
<!-- end of xhtml-meta-1.mod -->
F.3.15.
Scripting
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/xhtml-script-1.mod
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/xhtml-script-1.mod
.
<!-- ...................................................................... -->
<!-- XHTML Document Scripting Module ..................................... -->
<!-- file: xhtml-script-1.mod
This is XHTML, a reformulation of HTML as a modular XML application.
Copyright 1998-2005 W3C (MIT, ERCIM, Keio), All Rights Reserved.
Revision: $Id: xhtml-script-1.mod,v 4.0 2001/04/02 22:42:49 altheim Exp $ SMI
This DTD module is identified by the PUBLIC and SYSTEM identifiers:
PUBLIC "-//W3C//ELEMENTS XHTML Scripting 1.0//EN"
SYSTEM "http://www.w3.org/MarkUp/DTD/xhtml-script-1.mod"
Revisions:
(none)
....................................................................... -->
<!-- Scripting
script, noscript
This module declares element types and attributes used to provide
support for executable scripts as well as an alternate content
container where scripts are not supported.
-->
<!-- script: Scripting Statement ....................... -->
<!ENTITY % script.element "INCLUDE" >
<![%script.element;[
<!ENTITY % script.content "( #PCDATA )" >
<!ENTITY % script.qname "script" >
<!ELEMENT %script.qname; %script.content; >
<!-- end of script.element -->]]>
<!ENTITY % script.attlist "INCLUDE" >
<![%script.attlist;[
<!ATTLIST %script.qname;
%XHTML.xmlns.attrib;
%id.attrib;
xml:space ( preserve ) #FIXED 'preserve'
charset %Charset.datatype; #IMPLIED
type %ContentType.datatype; #REQUIRED
src %URI.datatype; #IMPLIED
defer ( defer ) #IMPLIED
>
<!-- end of script.attlist -->]]>
<!-- noscript: No-Script Alternate Content ............. -->
<!ENTITY % noscript.element "INCLUDE" >
<![%noscript.element;[
<!ENTITY % noscript.content
"( %Block.mix; )+"
>
<!ENTITY % noscript.qname "noscript" >
<!ELEMENT %noscript.qname; %noscript.content; >
<!-- end of noscript.element -->]]>
<!ENTITY % noscript.attlist "INCLUDE" >
<![%noscript.attlist;[
<!ATTLIST %noscript.qname;
%Common.attrib;
>
<!-- end of noscript.attlist -->]]>
<!-- end of xhtml-script-1.mod -->
F.3.16.
Style
Sheet
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/xhtml-style-1.mod
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/xhtml-style-1.mod
.
<!-- ...................................................................... -->
<!-- XHTML Document Style Sheet Module ................................... -->
<!-- file: xhtml-style-1.mod
This is XHTML, a reformulation of HTML as a modular XML application.
Copyright 1998-2005 W3C (MIT, ERCIM, Keio), All Rights Reserved.
Revision: $Id: xhtml-style-1.mod,v 4.1 2001/04/05 06:57:40 altheim Exp $ SMI
This DTD module is identified by the PUBLIC and SYSTEM identifiers:
PUBLIC "-//W3C//DTD XHTML Style Sheets 1.0//EN"
SYSTEM "http://www.w3.org/MarkUp/DTD/xhtml-style-1.mod"
Revisions:
(none)
....................................................................... -->
<!-- Style Sheets
style
This module declares the style element type and its attributes,
used to embed style sheet information in the document head element.
-->
<!-- style: Style Sheet Information .................... -->
<!ENTITY % style.element "INCLUDE" >
<![%style.element;[
<!ENTITY % style.content "( #PCDATA )" >
<!ENTITY % style.qname "style" >
<!ELEMENT %style.qname; %style.content; >
<!-- end of style.element -->]]>
<!ENTITY % style.attlist "INCLUDE" >
<![%style.attlist;[
<!ATTLIST %style.qname;
%XHTML.xmlns.attrib;
%id.attrib;
%title.attrib;
%I18n.attrib;
xml:space ( preserve ) #FIXED 'preserve'
type %ContentType.datatype; #REQUIRED
media %MediaDesc.datatype; #IMPLIED
>
<!-- end of style.attlist -->]]>
<!-- end of xhtml-style-1.mod -->
F.3.17.
Style
Attribute
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/xhtml-inlstyle-1.mod
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/xhtml-inlstyle-1.mod
.
<!-- ...................................................................... -->
<!-- XHTML Inline Style Module ........................................... -->
<!-- file: xhtml-inlstyle-1.mod
This is XHTML, a reformulation of HTML as a modular XML application.
Copyright 1998-2005 W3C (MIT, ERCIM, Keio), All Rights Reserved.
Revision: $Id: xhtml-inlstyle-1.mod,v 4.0 2001/04/02 22:42:49 altheim Exp $
This DTD module is identified by the PUBLIC and SYSTEM identifiers:
PUBLIC "-//W3C//ENTITIES XHTML Inline Style 1.0//EN"
SYSTEM "http://www.w3.org/MarkUp/DTD/xhtml-inlstyle-1.mod"
Revisions:
(none)
....................................................................... -->
<!-- Inline Style
This module declares the 'style' attribute, used to support inline
style markup. This module must be instantiated prior to the XHTML
Common Attributes module in order to be included in %Core.attrib;.
-->
<!ENTITY % style.attrib
"style CDATA #IMPLIED"
>
<!ENTITY % Core.extra.attrib
"%style.attrib;"
>
<!-- end of xhtml-inlstyle-1.mod -->
F.3.18.
Link
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/xhtml-link-1.mod
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/xhtml-link-1.mod
.
<!-- ...................................................................... -->
<!-- XHTML Link Element Module ........................................... -->
<!-- file: xhtml-link-1.mod
This is XHTML, a reformulation of HTML as a modular XML application.
Copyright 1998-2005 W3C (MIT, ERCIM, Keio), All Rights Reserved.
Revision: $Id: xhtml-link-1.mod,v 4.1 2001/04/05 06:57:40 altheim Exp $ SMI
This DTD module is identified by the PUBLIC and SYSTEM identifiers:
PUBLIC "-//W3C//ELEMENTS XHTML Link Element 1.0//EN"
SYSTEM "http://www.w3.org/MarkUp/DTD/xhtml-link-1.mod"
Revisions:
(none)
....................................................................... -->
<!-- Link element
link
This module declares the link element type and its attributes,
which could (in principle) be used to define document-level links
to external resources such as:
a) for document specific toolbars/menus, e.g. start, contents,
previous, next, index, end, help
b) to link to a separate style sheet (rel="stylesheet")
c) to make a link to a script (rel="script")
d) by style sheets to control how collections of html nodes are
rendered into printed documents
e) to make a link to a printable version of this document
e.g. a postscript or pdf version (rel="alternate" media="print")
-->
<!-- link: Media-Independent Link ...................... -->
<!ENTITY % link.element "INCLUDE" >
<![%link.element;[
<!ENTITY % link.content "EMPTY" >
<!ENTITY % link.qname "link" >
<!ELEMENT %link.qname; %link.content; >
<!-- end of link.element -->]]>
<!ENTITY % link.attlist "INCLUDE" >
<![%link.attlist;[
<!ATTLIST %link.qname;
%Common.attrib;
charset %Charset.datatype; #IMPLIED
href %URI.datatype; #IMPLIED
hreflang %LanguageCode.datatype; #IMPLIED
type %ContentType.datatype; #IMPLIED
rel %LinkTypes.datatype; #IMPLIED
rev %LinkTypes.datatype; #IMPLIED
media %MediaDesc.datatype; #IMPLIED
>
<!-- end of link.attlist -->]]>
<!-- end of xhtml-link-1.mod -->
F.3.19.
Base
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/xhtml-base-1.mod
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/xhtml-base-1.mod
.
<!-- ...................................................................... -->
<!-- XHTML Base Element Module ........................................... -->
<!-- file: xhtml-base-1.mod
This is XHTML, a reformulation of HTML as a modular XML application.
Copyright 1998-2005 W3C (MIT, ERCIM, Keio), All Rights Reserved.
Revision: $Id: xhtml-base-1.mod,v 4.0 2001/04/02 22:42:49 altheim Exp $ SMI
This DTD module is identified by the PUBLIC and SYSTEM identifiers:
PUBLIC "-//W3C//ELEMENTS XHTML Base Element 1.0//EN"
SYSTEM "http://www.w3.org/MarkUp/DTD/xhtml-base-1.mod"
Revisions:
(none)
....................................................................... -->
<!-- Base element
base
This module declares the base element type and its attributes,
used to define a base URI against which relative URIs in the
document will be resolved.
Note that this module also redeclares the content model for
the head element to include the base element.
-->
<!-- base: Document Base URI ........................... -->
<!ENTITY % base.element "INCLUDE" >
<![%base.element;[
<!ENTITY % base.content "EMPTY" >
<!ENTITY % base.qname "base" >
<!ELEMENT %base.qname; %base.content; >
<!-- end of base.element -->]]>
<!ENTITY % base.attlist "INCLUDE" >
<![%base.attlist;[
<!ATTLIST %base.qname;
%XHTML.xmlns.attrib;
href %URI.datatype; #REQUIRED
>
<!-- end of base.attlist -->]]>
<!ENTITY % head.content
"( %HeadOpts.mix;,
( ( %title.qname;, %HeadOpts.mix;, ( %base.qname;, %HeadOpts.mix; )? )
| ( %base.qname;, %HeadOpts.mix;, ( %title.qname;, %HeadOpts.mix; ))))"
>
<!-- end of xhtml-base-1.mod -->
F.3.20.
Name
Identification
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/xhtml-nameident-1.mod
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/xhtml-nameident-1.mod
.
<!-- ...................................................................... -->
<!-- XHTML Name Identifier Module ........................................ -->
<!-- file: xhtml-nameident-1.mod
This is XHTML, a reformulation of HTML as a modular XML application.
Copyright 1998-2005 W3C (MIT, ERCIM, Keio), All Rights Reserved.
Revision: $Id: xhtml-nameident-1.mod,v 4.0 2001/04/02 22:42:49 altheim Exp $
This DTD module is identified by the PUBLIC and SYSTEM identifiers:
PUBLIC "-//W3C//ELEMENTS XHTML Name Identifier 1.0//EN"
SYSTEM "http://www.w3.org/MarkUp/DTD/xhtml-nameident-1.mod"
Revisions:
(none)
....................................................................... -->
<!-- Name Identifier
'name' attribute on form, img, a, map, applet, frame, iframe
This module declares the 'name' attribute on element types when
it is used as a node identifier for legacy linking and scripting
support. This does not include those instances when 'name' is used
as a container for form control, property or metainformation names.
This module should be instantiated following all modules it modifies.
-->
<!ENTITY % a.attlist "IGNORE" >
<![%a.attlist;[
<!ATTLIST %a.qname;
name CDATA #IMPLIED
>
<!-- end of a.attlist -->]]>
<!ENTITY % map.attlist "IGNORE" >
<![%map.attlist;[
<!ATTLIST %map.qname;
name CDATA #IMPLIED
>
<!-- end of map.attlist -->]]>
<!ENTITY % applet.attlist "IGNORE" >
<![%applet.attlist;[
<!ATTLIST %applet.qname;
name CDATA #IMPLIED
>
<!-- end of applet.attlist -->]]>
<!ENTITY % frame.attlist "IGNORE" >
<![%frame.attlist;[
<!ATTLIST %frame.qname;
name CDATA #IMPLIED
>
<!-- end of frame.attlist -->]]>
<!ENTITY % iframe.attlist "IGNORE" >
<![%iframe.attlist;[
<!ATTLIST %iframe.qname;
name CDATA #IMPLIED
>
<!-- end of iframe.attlist -->]]>
<!-- end of xhtml-nameident.mod -->
F.3.21.
Legacy
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/xhtml-legacy-1.mod
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/xhtml-legacy-1.mod
.
<!-- ...................................................................... -->
<!-- XHTML Legacy Markup Module ........................................... -->
<!-- file: xhtml-legacy-1.mod
This is an extension of XHTML, a reformulation of HTML as a modular XML application.
Copyright 1998-2005 W3C (MIT, ERCIM, Keio), All Rights Reserved.
Revision: $Id: xhtml-legacy-1.mod,v 4.1 2001/04/10 09:42:30 altheim Exp $ SMI
This DTD module is identified by the PUBLIC and SYSTEM identifiers:
PUBLIC "-//W3C//ELEMENTS XHTML Legacy Markup 1.0//EN"
SYSTEM "http://www.w3.org/MarkUp/DTD/xhtml-legacy-1.mod"
Revisions:
(none)
....................................................................... -->
<!-- HTML Legacy Markup
font, basefont, center, s, strike, u, dir, menu, isindex
(plus additional datatypes and attributes)
This optional module declares additional markup for simple
presentation-related markup based on features found in the
HTML 4 Transitional and Frameset DTDs. This relies on
inclusion of the Legacy Redeclarations module. This module
also declares the frames, inline frames and object modules.
This is to allow XHTML 1.1 documents to be transformed for
display on HTML browsers where CSS support is inconsistent
or unavailable.
-->
<!-- Constructing a Legacy DTD
To construct a DTD driver obtaining a close approximation
of the HTML 4 Transitional and Frameset DTDs, declare the
Legacy Redeclarations module as the pre-framework redeclaration
parameter entity (%xhtml-prefw-redecl.mod;) and INCLUDE its
conditional section:
...
<!ENTITY % xhtml-prefw-redecl.module "INCLUDE" >
<![%xhtml-prefw-redecl.module;[
<!ENTITY % xhtml-prefw-redecl.mod
PUBLIC "-//W3C//ELEMENTS XHTML Legacy Redeclarations 1.0//EN"
"xhtml-legacy-redecl-1.mod" >
%xhtml-prefw-redecl.mod;]]>
Such a DTD should be named with a variant FPI and redeclare
the value of the %XHTML.version; parameter entity to that FPI:
"-//Your Name Here//DTD XHTML Legacy 1.1//EN"
IMPORTANT: see also the notes included in the Legacy Redeclarations
Module for information on how to construct a DTD using this module.
-->
<!-- Additional Element Types .................................... -->
<!-- font: Local Font Modifier ........................ -->
<!ENTITY % font.element "INCLUDE" >
<![%font.element;[
<!ENTITY % font.content
"( #PCDATA | %Inline.mix; )*"
>
<!ENTITY % font.qname "font" >
<!ELEMENT %font.qname; %font.content; >
<!-- end of font.element -->]]>
<!ENTITY % font.attlist "INCLUDE" >
<![%font.attlist;[
<!ATTLIST %font.qname;
%Core.attrib;
%I18n.attrib;
size CDATA #IMPLIED
color %Color.datatype; #IMPLIED
face CDATA #IMPLIED
>
<!-- end of font.attlist -->]]>
<!-- basefont: Base Font Size ......................... -->
<!ENTITY % basefont.element "INCLUDE" >
<![%basefont.element;[
<!ENTITY % basefont.content "EMPTY" >
<!ENTITY % basefont.qname "basefont" >
<!ELEMENT %basefont.qname; %basefont.content; >
<!-- end of basefont.element -->]]>
<!ENTITY % basefont.attlist "INCLUDE" >
<![%basefont.attlist;[
<!ATTLIST %basefont.qname;
%id.attrib;
size CDATA #REQUIRED
color %Color.datatype; #IMPLIED
face CDATA #IMPLIED
>
<!-- end of basefont.attlist -->]]>
<!-- center: Center Alignment ......................... -->
<!ENTITY % center.element "INCLUDE" >
<![%center.element;[
<!ENTITY % center.content
"( #PCDATA | %Flow.mix; )*"
>
<!ENTITY % center.qname "center" >
<!ELEMENT %center.qname; %center.content; >
<!-- end of center.element -->]]>
<!ENTITY % center.attlist "INCLUDE" >
<![%center.attlist;[
<!ATTLIST %center.qname;
%Common.attrib;
>
<!-- end of center.attlist -->]]>
<!-- s: Strike-Thru Text Style ........................ -->
<!ENTITY % s.element "INCLUDE" >
<![%s.element;[
<!ENTITY % s.content
"( #PCDATA | %Inline.mix; )*"
>
<!ENTITY % s.qname "s" >
<!ELEMENT %s.qname; %s.content; >
<!-- end of s.element -->]]>
<!ENTITY % s.attlist "INCLUDE" >
<![%s.attlist;[
<!ATTLIST %s.qname;
%Common.attrib;
>
<!-- end of s.attlist -->]]>
<!-- strike: Strike-Thru Text Style ....................-->
<!ENTITY % strike.element "INCLUDE" >
<![%strike.element;[
<!ENTITY % strike.content
"( #PCDATA | %Inline.mix; )*"
>
<!ENTITY % strike.qname "strike" >
<!ELEMENT %strike.qname; %strike.content; >
<!-- end of strike.element -->]]>
<!ENTITY % strike.attlist "INCLUDE" >
<![%strike.attlist;[
<!ATTLIST %strike.qname;
%Common.attrib;
>
<!-- end of strike.attlist -->]]>
<!-- u: Underline Text Style ...........................-->
<!ENTITY % u.element "INCLUDE" >
<![%u.element;[
<!ENTITY % u.content
"( #PCDATA | %Inline.mix; )*"
>
<!ENTITY % u.qname "u" >
<!ELEMENT %u.qname; %u.content; >
<!-- end of u.element -->]]>
<!ENTITY % u.attlist "INCLUDE" >
<![%u.attlist;[
<!ATTLIST %u.qname;
%Common.attrib;
>
<!-- end of u.attlist -->]]>
<!-- dir: Directory List .............................. -->
<!-- NOTE: the content model for <dir> in HTML 4 excluded %Block.mix;
-->
<!ENTITY % dir.element "INCLUDE" >
<![%dir.element;[
<!ENTITY % dir.content
"( %li.qname; )+"
>
<!ENTITY % dir.qname "dir" >
<!ELEMENT %dir.qname; %dir.content; >
<!-- end of dir.element -->]]>
<!ENTITY % dir.attlist "INCLUDE" >
<![%dir.attlist;[
<!ATTLIST %dir.qname;
%Common.attrib;
compact ( compact ) #IMPLIED
>
<!-- end of dir.attlist -->]]>
<!-- menu: Menu List .................................. -->
<!-- NOTE: the content model for <menu> in HTML 4 excluded %Block.mix;
-->
<!ENTITY % menu.element "INCLUDE" >
<![%menu.element;[
<!ENTITY % menu.content
"( %li.qname; )+"
>
<!ENTITY % menu.qname "menu" >
<!ELEMENT %; %menu.content; >
<!-- end of menu.element -->]]>
<!ENTITY % menu.attlist "INCLUDE" >
<![%menu.attlist;[
<!ATTLIST %menu.qname;
%Common.attrib;
compact ( compact ) #IMPLIED
>
<!-- end of menu.attlist -->]]>
<!-- isindex: Single-Line Prompt ...................... -->
<!ENTITY % isindex.element "INCLUDE" >
<![%isindex.element;[
<!ENTITY % isindex.content "EMPTY" >
<!ENTITY % isindex.qname "isindex" >
<!ELEMENT %isindex.qname; %isindex.content; >
<!-- end of isindex.element -->]]>
<!ENTITY % isindex.attlist "INCLUDE" >
<![%isindex.attlist;[
<!ATTLIST %isindex.qname;
%Core.attrib;
%I18n.attrib;
prompt %Text.datatype; #IMPLIED
>
<!-- end of isindex.attlist -->]]>
<!-- Additional Attributes ....................................... -->
<!-- Alignment attribute for Transitional use in HTML browsers
(this functionality is generally well-supported in CSS,
except within some contexts)
-->
<!ENTITY % align.attrib
"align ( left | center | right | justify ) #IMPLIED"
>
<!ATTLIST %applet.qname;
align ( top | middle | bottom | left | right ) #IMPLIED
hspace %Pixels.datatype; #IMPLIED
vspace %Pixels.datatype; #IMPLIED
>
<!ATTLIST %body.qname;
background %URI.datatype; #IMPLIED
bgcolor %Color.datatype; #IMPLIED
text %Color.datatype; #IMPLIED
link %Color.datatype; #IMPLIED
vlink %Color.datatype; #IMPLIED
alink %Color.datatype; #IMPLIED
>
<!ATTLIST %br.qname;
clear ( left | all | right | none ) 'none'
>
<!ATTLIST %caption.qname;
align ( top | bottom | left | right ) #IMPLIED
>
<!ATTLIST %div.qname;
%align.attrib;
>
<!ATTLIST %h1.qname;
%align.attrib;
>
<!ATTLIST %h2.qname;
%align.attrib;
>
<!ATTLIST %h3.qname;
%align.attrib;
>
<!ATTLIST %h4.qname;
%align.attrib;
>
<!ATTLIST %h5.qname;
%align.attrib;
>
<!ATTLIST %h6.qname;
%align.attrib;
>
<!ATTLIST %hr.qname;
align ( left | center | right ) #IMPLIED
noshade ( noshade ) #IMPLIED
size %Pixels.datatype; #IMPLIED
width %Length.datatype; #IMPLIED
>
<!ATTLIST %img.qname;
align ( top | middle | bottom | left | right ) #IMPLIED
border %Pixels.datatype; #IMPLIED
hspace %Pixels.datatype; #IMPLIED
vspace %Pixels.datatype; #IMPLIED
>
<!ATTLIST %input.qname;
align ( top | middle | bottom | left | right ) #IMPLIED
>
<!ATTLIST %legend.qname;
align ( top | bottom | left | right ) #IMPLIED
>
<!ATTLIST %li.qname;
type CDATA #IMPLIED
value %Number.datatype; #IMPLIED
>
<!ATTLIST %object.qname;
align ( top | middle | bottom | left | right ) #IMPLIED
border %Pixels.datatype; #IMPLIED
hspace %Pixels.datatype; #IMPLIED
vspace %Pixels.datatype; #IMPLIED
>
<!ATTLIST %dl.qname;
compact ( compact ) #IMPLIED
>
<!ATTLIST %ol.qname;
type CDATA #IMPLIED
compact ( compact ) #IMPLIED
start %Number.datatype; #IMPLIED
>
<!ATTLIST %p.qname;
%align.attrib;
>
<!ATTLIST %pre.qname;
width %Length.datatype; #IMPLIED
>
<!ATTLIST %script.qname;
language %ContentType.datatype; #IMPLIED
>
<!ATTLIST %table.qname;
align ( left | center | right ) #IMPLIED
bgcolor %Color.datatype; #IMPLIED
>
<!ATTLIST %tr.qname;
bgcolor %Color.datatype; #IMPLIED
>
<!ATTLIST %th.qname;
nowrap ( nowrap ) #IMPLIED
bgcolor %Color.datatype; #IMPLIED
width %Length.datatype; #IMPLIED
height %Length.datatype; #IMPLIED
>
<!ATTLIST %td.qname;
nowrap ( nowrap ) #IMPLIED
bgcolor %Color.datatype; #IMPLIED
width %Length.datatype; #IMPLIED
height %Length.datatype; #IMPLIED
>
<!ATTLIST %ul.qname;
type CDATA #IMPLIED
compact ( compact ) #IMPLIED
>
<!-- Frames Module ............................................... -->
<!ENTITY % xhtml-frames.module "IGNORE" >
<![%xhtml-frames.module;[
<!ENTITY % xhtml-frames.mod
PUBLIC "-//W3C//ELEMENTS XHTML Frames 1.0//EN"
"xhtml-frames-1.mod" >
%xhtml-frames.mod;]]>
<!-- Inline Frames Module ........................................ -->
<!ENTITY % xhtml-iframe.module "INCLUDE" >
<![%xhtml-iframe.module;[
<!ATTLIST %iframe.qname;
align ( top | middle | bottom | left | right ) #IMPLIED
>
<!ENTITY % xhtml-iframe.mod
PUBLIC "-//W3C//ELEMENTS XHTML Inline Frame Element 1.0//EN"
"xhtml-iframe-1.mod" >
%xhtml-iframe.mod;]]>
<!-- end of xhtml-legacy-1.mod -->
F.4.
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.
F.4.1.
Block
Phrasal
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/xhtml-blkphras-1.mod
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/xhtml-blkphras-1.mod
.
<!-- ...................................................................... -->
<!-- XHTML Block Phrasal Module .......................................... -->
<!-- file: xhtml-blkphras-1.mod
This is XHTML, a reformulation of HTML as a modular XML application.
Copyright 1998-2005 W3C (MIT, ERCIM, Keio), All Rights Reserved.
Revision: $Id: xhtml-blkphras-1.mod,v 4.0 2001/04/02 22:42:49 altheim Exp $ SMI
This DTD module is identified by the PUBLIC and SYSTEM identifiers:
PUBLIC "-//W3C//ELEMENTS XHTML Block Phrasal 1.0//EN"
SYSTEM "http://www.w3.org/MarkUp/DTD/xhtml-blkphras-1.mod"
Revisions:
(none)
....................................................................... -->
<!-- Block Phrasal
address, blockquote, pre, h1, h2, h3, h4, h5, h6
This module declares the elements and their attributes used to
support block-level phrasal markup.
-->
<!ENTITY % address.element "INCLUDE" >
<![%address.element;[
<!ENTITY % address.content
"( #PCDATA | %Inline.mix; )*" >
<!ENTITY % address.qname "address" >
<!ELEMENT %address.qname; %address.content; >
<!-- end of address.element -->]]>
<!ENTITY % address.attlist "INCLUDE" >
<![%address.attlist;[
<!ATTLIST %address.qname;
%Common.attrib;
>
<!-- end of address.attlist -->]]>
<!ENTITY % blockquote.element "INCLUDE" >
<![%blockquote.element;[
<!ENTITY % blockquote.content
"( %Block.mix; )*"
>
<!ENTITY % blockquote.qname "blockquote" >
<!ELEMENT %blockquote.qname; %blockquote.content; >
<!-- end of blockquote.element -->]]>
<!ENTITY % blockquote.attlist "INCLUDE" >
<![%blockquote.attlist;[
<!ATTLIST %blockquote.qname;
%Common.attrib;
cite %URI.datatype; #IMPLIED
>
<!-- end of blockquote.attlist -->]]>
<!ENTITY % pre.element "INCLUDE" >
<![%pre.element;[
<!ENTITY % pre.content
"( #PCDATA
| %InlStruct.class;
%InlPhras.class;
| %tt.qname; | %i.qname; | %b.qname;
%I18n.class;
%Anchor.class;
| %map.qname;
%Misc.class;
%Inline.extra; )*"
>
<!ENTITY % pre.qname "pre" >
<!ELEMENT %pre.qname; %pre.content; >
<!-- end of pre.element -->]]>
<!ENTITY % pre.attlist "INCLUDE" >
<![%pre.attlist;[
<!ATTLIST %pre.qname;
%Common.attrib;
>
<!-- end of pre.attlist -->]]>
<!-- ................... Heading Elements ................... -->
<!ENTITY % Heading.content "( #PCDATA | %Inline.mix; )*" >
<!ENTITY % h1.element "INCLUDE" >
<![%h1.element;[
<!ENTITY % h1.qname "h1" >
<!ELEMENT %h1.qname; %Heading.content; >
<!-- end of h1.element -->]]>
<!ENTITY % h1.attlist "INCLUDE" >
<![%h1.attlist;[
<!ATTLIST %h1.qname;
%Common.attrib;
>
<!-- end of h1.attlist -->]]>
<!ENTITY % h2.element "INCLUDE" >
<![%h2.element;[
<!ENTITY % h2.qname "h2" >
<!ELEMENT %h2.qname; %Heading.content; >
<!-- end of h2.element -->]]>
<!ENTITY % h2.attlist "INCLUDE" >
<![%h2.attlist;[
<!ATTLIST %h2.qname;
%Common.attrib;
>
<!-- end of h2.attlist -->]]>
<!ENTITY % h3.element "INCLUDE" >
<![%h3.element;[
<!ENTITY % h3.qname "h3" >
<!ELEMENT %h3.qname; %Heading.content; >
<!-- end of h3.element -->]]>
<!ENTITY % h3.attlist "INCLUDE" >
<![%h3.attlist;[
<!ATTLIST %h3.qname;
%Common.attrib;
>
<!-- end of h3.attlist -->]]>
<!ENTITY % h4.element "INCLUDE" >
<![%h4.element;[
<!ENTITY % h4.qname "h4" >
<!ELEMENT %h4.qname; %Heading.content; >
<!-- end of h4.element -->]]>
<!ENTITY % h4.attlist "INCLUDE" >
<![%h4.attlist;[
<!ATTLIST %h4.qname;
%Common.attrib;
>
<!-- end of h4.attlist -->]]>
<!ENTITY % h5.element "INCLUDE" >
<![%h5.element;[
<!ENTITY % h5.qname "h5" >
<!ELEMENT %h5.qname; %Heading.content; >
<!-- end of h5.element -->]]>
<!ENTITY % h5.attlist "INCLUDE" >
<![%h5.attlist;[
<!ATTLIST %h5.qname;
%Common.attrib;
>
<!-- end of h5.attlist -->]]>
<!ENTITY % h6.element "INCLUDE" >
<![%h6.element;[
<!ENTITY % h6.qname "h6" >
<!ELEMENT %h6.qname; %Heading.content; >
<!-- end of h6.element -->]]>
<!ENTITY % h6.attlist "INCLUDE" >
<![%h6.attlist;[
<!ATTLIST %h6.qname;
%Common.attrib;
>
<!-- end of h6.attlist -->]]>
<!-- end of xhtml-blkphras-1.mod -->
F.4.2.
Block
Presentational
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/xhtml-blkpres-1.mod
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/xhtml-blkpres-1.mod
.
<!-- ...................................................................... -->
<!-- XHTML Block Presentation Module ..................................... -->
<!-- file: xhtml-blkpres-1.mod
This is XHTML, a reformulation of HTML as a modular XML application.
Copyright 1998-2005 W3C (MIT, ERCIM, Keio), All Rights Reserved.
Revision: $Id: xhtml-blkpres-1.mod,v 4.0 2001/04/02 22:42:49 altheim Exp $ SMI
This DTD module is identified by the PUBLIC and SYSTEM identifiers:
PUBLIC "-//W3C//ELEMENTS XHTML Block Presentation 1.0//EN"
SYSTEM "http://www.w3.org/MarkUp/DTD/xhtml-blkpres-1.mod"
Revisions:
(none)
....................................................................... -->
<!-- Block Presentational Elements
hr
This module declares the elements and their attributes used to
support block-level presentational markup.
-->
<!ENTITY % hr.element "INCLUDE" >
<![%hr.element;[
<!ENTITY % hr.content "EMPTY" >
<!ENTITY % hr.qname "hr" >
<!ELEMENT %hr.qname; %hr.content; >
<!-- end of hr.element -->]]>
<!ENTITY % hr.attlist "INCLUDE" >
<![%hr.attlist;[
<!ATTLIST %hr.qname;
%Common.attrib;
>
<!-- end of hr.attlist -->]]>
<!-- end of xhtml-blkpres-1.mod -->
F.4.3.
Block
Structural
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/xhtml-blkstruct-1.mod
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/xhtml-blkstruct-1.mod
.
<!-- ...................................................................... -->
<!-- XHTML Block Structural Module ....................................... -->
<!-- file: xhtml-blkstruct-1.mod
This is XHTML, a reformulation of HTML as a modular XML application.
Copyright 1998-2005 W3C (MIT, ERCIM, Keio), All Rights Reserved.
Revision: $Id: xhtml-blkstruct-1.mod,v 4.0 2001/04/02 22:42:49 altheim Exp $ SMI
This DTD module is identified by the PUBLIC and SYSTEM identifiers:
PUBLIC "-//W3C//ELEMENTS XHTML Block Structural 1.0//EN"
SYSTEM "http://www.w3.org/MarkUp/DTD/xhtml-blkstruct-1.mod"
Revisions:
(none)
....................................................................... -->
<!-- Block Structural
div, p
This module declares the elements and their attributes used to
support block-level structural markup.
-->
<!ENTITY % div.element "INCLUDE" >
<![%div.element;[
<!ENTITY % div.content
"( #PCDATA | %Flow.mix; )*"
>
<!ENTITY % div.qname "div" >
<!ELEMENT %div.qname; %div.content; >
<!-- end of div.element -->]]>
<!ENTITY % div.attlist "INCLUDE" >
<![%div.attlist;[
<!ATTLIST %div.qname;
%Common.attrib;
>
<!-- end of div.attlist -->]]>
<!ENTITY % p.element "INCLUDE" >
<![%p.element;[
<!ENTITY % p.content
"( #PCDATA | %Inline.mix; )*" >
<!ENTITY % p.qname "p" >
<!ELEMENT %p.qname; %p.content; >
<!-- end of p.element -->]]>
<!ENTITY % p.attlist "INCLUDE" >
<![%p.attlist;[
<!ATTLIST %p.qname;
%Common.attrib;
>
<!-- end of p.attlist -->]]>
<!-- end of xhtml-blkstruct-1.mod -->
F.4.4.
Inline
Phrasal
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/xhtml-inlphras-1.mod
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/xhtml-inlphras-1.mod
.
<!-- ...................................................................... -->
<!-- XHTML Inline Phrasal Module ......................................... -->
<!-- file: xhtml-inlphras-1.mod
This is XHTML, a reformulation of HTML as a modular XML application.
Copyright 1998-2005 W3C (MIT, ERCIM, Keio), All Rights Reserved.
Revision: $Id: xhtml-inlphras-1.mod,v 4.0 2001/04/02 22:42:49 altheim Exp $ SMI
This DTD module is identified by the PUBLIC and SYSTEM identifiers:
PUBLIC "-//W3C//ELEMENTS XHTML Inline Phrasal 1.0//EN"
SYSTEM "http://www.w3.org/MarkUp/DTD/xhtml-inlphras-1.mod"
Revisions:
(none)
....................................................................... -->
<!-- Inline Phrasal
abbr, acronym, cite, code, dfn, em, kbd, q, samp, strong, var
This module declares the elements and their attributes used to
support inline-level phrasal markup.
-->
<!ENTITY % abbr.element "INCLUDE" >
<![%abbr.element;[
<!ENTITY % abbr.content
"( #PCDATA | %Inline.mix; )*"
>
<!ENTITY % abbr.qname "abbr" >
<!ELEMENT %abbr.qname; %abbr.content; >
<!-- end of abbr.element -->]]>
<!ENTITY % abbr.attlist "INCLUDE" >
<![%abbr.attlist;[
<!ATTLIST %abbr.qname;
%Common.attrib;
>
<!-- end of abbr.attlist -->]]>
<!ENTITY % acronym.element "INCLUDE" >
<![%acronym.element;[
<!ENTITY % acronym.content
"( #PCDATA | %Inline.mix; )*"
>
<!ENTITY % acronym.qname "acronym" >
<!ELEMENT %acronym.qname; %acronym.content; >
<!-- end of acronym.element -->]]>
<!ENTITY % acronym.attlist "INCLUDE" >
<![%acronym.attlist;[
<!ATTLIST %acronym.qname;
%Common.attrib;
>
<!-- end of acronym.attlist -->]]>
<!ENTITY % cite.element "INCLUDE" >
<![%cite.element;[
<!ENTITY % cite.content
"( #PCDATA | %Inline.mix; )*"
>
<!ENTITY % cite.qname "cite" >
<!ELEMENT %cite.qname; %cite.content; >
<!-- end of cite.element -->]]>
<!ENTITY % cite.attlist "INCLUDE" >
<![%cite.attlist;[
<!ATTLIST %cite.qname;
%Common.attrib;
>
<!-- end of cite.attlist -->]]>
<!ENTITY % code.element "INCLUDE" >
<![%code.element;[
<!ENTITY % code.content
"( #PCDATA | %Inline.mix; )*"
>
<!ENTITY % code.qname "code" >
<!ELEMENT %code.qname; %code.content; >
<!-- end of code.element -->]]>
<!ENTITY % code.attlist "INCLUDE" >
<![%code.attlist;[
<!ATTLIST %code.qname;
%Common.attrib;
>
<!-- end of code.attlist -->]]>
<!ENTITY % dfn.element "INCLUDE" >
<![%dfn.element;[
<!ENTITY % dfn.content
"( #PCDATA | %Inline.mix; )*"
>
<!ENTITY % dfn.qname "dfn" >
<!ELEMENT %dfn.qname; %dfn.content; >
<!-- end of dfn.element -->]]>
<!ENTITY % dfn.attlist "INCLUDE" >
<![%dfn.attlist;[
<!ATTLIST %dfn.qname;
%Common.attrib;
>
<!-- end of dfn.attlist -->]]>
<!ENTITY % em.element "INCLUDE" >
<![%em.element;[
<!ENTITY % em.content
"( #PCDATA | %Inline.mix; )*"
>
<!ENTITY % em.qname "em" >
<!ELEMENT %em.qname; %em.content; >
<!-- end of em.element -->]]>
<!ENTITY % em.attlist "INCLUDE" >
<![%em.attlist;[
<!ATTLIST %em.qname;
%Common.attrib;
>
<!-- end of em.attlist -->]]>
<!ENTITY % kbd.element "INCLUDE" >
<![%kbd.element;[
<!ENTITY % kbd.content
"( #PCDATA | %Inline.mix; )*"
>
<!ENTITY % kbd.qname "kbd" >
<!ELEMENT %kbd.qname; %kbd.content; >
<!-- end of kbd.element -->]]>
<!ENTITY % kbd.attlist "INCLUDE" >
<![%kbd.attlist;[
<!ATTLIST %kbd.qname;
%Common.attrib;
>
<!-- end of kbd.attlist -->]]>
<!ENTITY % q.element "INCLUDE" >
<![%q.element;[
<!ENTITY % q.content
"( #PCDATA | %Inline.mix; )*"
>
<!ENTITY % q.qname "q" >
<!ELEMENT %q.qname; %q.content; >
<!-- end of q.element -->]]>
<!ENTITY % q.attlist "INCLUDE" >
<![%q.attlist;[
<!ATTLIST %q.qname;
%Common.attrib;
cite %URI.datatype; #IMPLIED
>
<!-- end of q.attlist -->]]>
<!ENTITY % samp.element "INCLUDE" >
<![%samp.element;[
<!ENTITY % samp.content
"( #PCDATA | %Inline.mix; )*"
>
<!ENTITY % samp.qname "samp" >
<!ELEMENT %samp.qname; %samp.content; >
<!-- end of samp.element -->]]>
<!ENTITY % samp.attlist "INCLUDE" >
<![%samp.attlist;[
<!ATTLIST %samp.qname;
%Common.attrib;
>
<!-- end of samp.attlist -->]]>
<!ENTITY % strong.element "INCLUDE" >
<![%strong.element;[
<!ENTITY % strong.content
"( #PCDATA | %Inline.mix; )*"
>
<!ENTITY % strong.qname "strong" >
<!ELEMENT %strong.qname; %strong.content; >
<!-- end of strong.element -->]]>
<!ENTITY % strong.attlist "INCLUDE" >
<![%strong.attlist;[
<!ATTLIST %strong.qname;
%Common.attrib;
>
<!-- end of strong.attlist -->]]>
<!ENTITY % var.element "INCLUDE" >
<![%var.element;[
<!ENTITY % var.content
"( #PCDATA | %Inline.mix; )*"
>
<!ENTITY % var.qname "var" >
<!ELEMENT %var.qname; %var.content; >
<!-- end of var.element -->]]>
<!ENTITY % var.attlist "INCLUDE" >
<![%var.attlist;[
<!ATTLIST %var.qname;
%Common.attrib;
>
<!-- end of var.attlist -->]]>
<!-- end of xhtml-inlphras-1.mod -->
F.4.5.
Inline
Presentational
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/xhtml-inlpres-1.mod
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/xhtml-inlpres-1.mod
.
<!-- ...................................................................... -->
<!-- XHTML Inline Presentation Module .................................... -->
<!-- file: xhtml-inlpres-1.mod
This is XHTML, a reformulation of HTML as a modular XML application.
Copyright 1998-2005 W3C (MIT, ERCIM, Keio), All Rights Reserved.
Revision: $Id: xhtml-inlpres-1.mod,v 4.0 2001/04/02 22:42:49 altheim Exp $ SMI
This DTD module is identified by the PUBLIC and SYSTEM identifiers:
PUBLIC "-//W3C//ELEMENTS XHTML Inline Presentation 1.0//EN"
SYSTEM "http://www.w3.org/MarkUp/DTD/xhtml-inlpres-1.mod"
Revisions:
(none)
....................................................................... -->
<!-- Inline Presentational Elements
b, big, i, small, sub, sup, tt
This module declares the elements and their attributes used to
support inline-level presentational markup.
-->
<!ENTITY % b.element "INCLUDE" >
<![%b.element;[
<!ENTITY % b.content
"( #PCDATA | %Inline.mix; )*"
>
<!ENTITY % b.qname "b" >
<!ELEMENT %b.qname; %b.content; >
<!-- end of b.element -->]]>
<!ENTITY % b.attlist "INCLUDE" >
<![%b.attlist;[
<!ATTLIST %b.qname;
%Common.attrib;
>
<!-- end of b.attlist -->]]>
<!ENTITY % big.element "INCLUDE" >
<![%big.element;[
<!ENTITY % big.content
"( #PCDATA | %Inline.mix; )*"
>
<!ENTITY % big.qname "big" >
<!ELEMENT %big.qname; %big.content; >
<!-- end of big.element -->]]>
<!ENTITY % big.attlist "INCLUDE" >
<![%big.attlist;[
<!ATTLIST %big.qname;
%Common.attrib;
>
<!-- end of big.attlist -->]]>
<!ENTITY % i.element "INCLUDE" >
<![%i.element;[
<!ENTITY % i.content
"( #PCDATA | %Inline.mix; )*"
>
<!ENTITY % i.qname "i" >
<!ELEMENT %i.qname; %i.content; >
<!-- end of i.element -->]]>
<!ENTITY % i.attlist "INCLUDE" >
<![%i.attlist;[
<!ATTLIST %i.qname;
%Common.attrib;
>
<!-- end of i.attlist -->]]>
<!ENTITY % small.element "INCLUDE" >
<![%small.element;[
<!ENTITY % small.content
"( #PCDATA | %Inline.mix; )*"
>
<!ENTITY % small.qname "small" >
<!ELEMENT %small.qname; %small.content; >
<!-- end of small.element -->]]>
<!ENTITY % small.attlist "INCLUDE" >
<![%small.attlist;[
<!ATTLIST %small.qname;
%Common.attrib;
>
<!-- end of small.attlist -->]]>
<!ENTITY % sub.element "INCLUDE" >
<![%sub.element;[
<!ENTITY % sub.content
"( #PCDATA | %Inline.mix; )*"
>
<!ENTITY % sub.qname "sub" >
<!ELEMENT %sub.qname; %sub.content; >
<!-- end of sub.element -->]]>
<!ENTITY % sub.attlist "INCLUDE" >
<![%sub.attlist;[
<!ATTLIST %sub.qname;
%Common.attrib;
>
<!-- end of sub.attlist -->]]>
<!ENTITY % sup.element "INCLUDE" >
<![%sup.element;[
<!ENTITY % sup.content
"( #PCDATA | %Inline.mix; )*"
>
<!ENTITY % sup.qname "sup" >
<!ELEMENT %sup.qname; %sup.content; >
<!-- end of sup.element -->]]>
<!ENTITY % sup.attlist "INCLUDE" >
<![%sup.attlist;[
<!ATTLIST %sup.qname;
%Common.attrib;
>
<!-- end of sup.attlist -->]]>
<!ENTITY % tt.element "INCLUDE" >
<![%tt.element;[
<!ENTITY % tt.content
"( #PCDATA | %Inline.mix; )*"
>
<!ENTITY % tt.qname "tt" >
<!ELEMENT %tt.qname; %tt.content; >
<!-- end of tt.element -->]]>
<!ENTITY % tt.attlist "INCLUDE" >
<![%tt.attlist;[
<!ATTLIST %tt.qname;
%Common.attrib;
>
<!-- end of tt.attlist -->]]>
<!-- end of xhtml-inlpres-1.mod -->
F.4.6.
Inline
Structural
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/xhtml-inlstruct-1.mod
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/xhtml-inlstruct-1.mod
.
<!-- ...................................................................... -->
<!-- XHTML Inline Structural Module ...................................... -->
<!-- file: xhtml-inlstruct-1.mod
This is XHTML, a reformulation of HTML as a modular XML application.
Copyright 1998-2005 W3C (MIT, ERCIM, Keio), All Rights Reserved.
Revision: $Id: xhtml-inlstruct-1.mod,v 4.0 2001/04/02 22:42:49 altheim Exp $ SMI
This DTD module is identified by the PUBLIC and SYSTEM identifiers:
PUBLIC "-//W3C//ELEMENTS XHTML Inline Structural 1.0//EN"
SYSTEM "http://www.w3.org/MarkUp/DTD/xhtml-inlstruct-1.mod"
Revisions:
(none)
....................................................................... -->
<!-- Inline Structural
br, span
This module declares the elements and their attributes
used to support inline-level structural markup.
-->
<!-- br: forced line break ............................. -->
<!ENTITY % br.element "INCLUDE" >
<![%br.element;[
<!ENTITY % br.content "EMPTY" >
<!ENTITY % br.qname "br" >
<!ELEMENT %br.qname; %br.content; >
<!-- end of br.element -->]]>
<!ENTITY % br.attlist "INCLUDE" >
<![%br.attlist;[
<!ATTLIST %br.qname;
%Core.attrib;
>
<!-- end of br.attlist -->]]>
<!-- span: generic inline container .................... -->
<!ENTITY % span.element "INCLUDE" >
<![%span.element;[
<!ENTITY % span.content
"( #PCDATA | %Inline.mix; )*"
>
<!ENTITY % span.qname "span" >
<!ELEMENT %span.qname; %span.content; >
<!-- end of span.element -->]]>
<!ENTITY % span.attlist "INCLUDE" >
<![%span.attlist;[
<!ATTLIST %span.qname;
%Common.attrib;
>
<!-- end of span.attlist -->]]>
<!-- end of xhtml-inlstruct-1.mod -->
F.4.7.
Param
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/xhtml-param-1.mod
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/xhtml-param-1.mod
.
<!-- ...................................................................... -->
<!-- XHTML Param Element Module ..................................... -->
<!-- file: xhtml-param-1.mod
This is XHTML, a reformulation of HTML as a modular XML application.
Copyright 1998-2005 W3C (MIT, ERCIM, Keio), All Rights Reserved.
Revision: $Id: xhtml-param-1.mod,v 4.0 2001/04/02 22:42:49 altheim Exp $ SMI
This DTD module is identified by the PUBLIC and SYSTEM identifiers:
PUBLIC "-//W3C//ELEMENTS XHTML Param Element 1.0//EN"
SYSTEM "http://www.w3.org/MarkUp/DTD/xhtml-param-1.mod"
Revisions:
(none)
....................................................................... -->
<!-- Parameters for Java Applets and Embedded Objects
param
This module provides declarations for the param element,
used to provide named property values for the applet
and object elements.
-->
<!-- param: Named Property Value ....................... -->
<!ENTITY % param.element "INCLUDE" >
<![%param.element;[
<!ENTITY % param.content "EMPTY" >
<!ENTITY % param.qname "param" >
<!ELEMENT %param.qname; %param.content; >
<!-- end of param.element -->]]>
<!ENTITY % param.attlist "INCLUDE" >
<![%param.attlist;[
<!ATTLIST %param.qname;
%XHTML.xmlns.attrib;
%id.attrib;
name CDATA #REQUIRED
value CDATA #IMPLIED
valuetype ( data | ref | object ) 'data'
type %ContentType.datatype; #IMPLIED
>
<!-- end of param.attlist -->]]>
<!-- end of xhtml-param-1.mod -->
F.4.8.
Legacy
Redeclarations
You
can
download
this
version
of
this
file
from
http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729/DTD/xhtml-legacy-redecl-1.mod
.
The
latest
version
is
available
at
http://www.w3.org/MarkUp/DTD/xhtml-legacy-redecl-1.mod
.
<!-- ...................................................................... -->
<!-- XHTML Legacy Redeclarations Module ................................... -->
<!-- file: xhtml-legacy-redecl-1.mod
This is an extension of XHTML, a reformulation of HTML as a modular XML application.
Copyright 1998-2005 W3C (MIT, ERCIM, Keio), All Rights Reserved.
Revision: $Id: xhtml-legacy-redecl-1.mod,v 4.4 2001/04/10 09:42:30 altheim Exp $ SMI
This DTD module is identified by the PUBLIC and SYSTEM identifiers:
PUBLIC "-//W3C//ELEMENTS XHTML Legacy Redeclarations 1.0//EN"
SYSTEM "http://www.w3.org/MarkUp/DTD/xhtml-legacy-redecl-1.mod"
Revisions:
(none)
....................................................................... -->
<!-- Legacy Redeclarations
This optional module replaces the Modular Framework module, interspersing
redeclarations of various parameter entities to allow for inclusions of
Transitional markup in the XHTML 1.1 document model. This instantiates
the modules needed to support the XHTML modularization model, including:
+ notations
+ datatypes
+ namespace-qualified names
+ common attributes
+ document model
+ character entities
By default, the Object module is included, with Frames and IFrames ignored.
The Intrinsic Events module is ignored by default but
occurs in this module because it must be instantiated
prior to Attributes but after Datatypes.
-->
<!ENTITY % xhtml-legacy.module "INCLUDE" >
<!ENTITY % xhtml-arch.module "IGNORE" >
<![%xhtml-arch.module;[
<!ENTITY % xhtml-arch.mod
PUBLIC "-//W3C//ELEMENTS XHTML Base Architecture 1.0//EN"
"xhtml-arch-1.mod" >
%xhtml-arch.mod;]]>
<!ENTITY % xhtml-notations.module "INCLUDE" >
<![%xhtml-notations.module;[
<!ENTITY % xhtml-notations.mod
PUBLIC "-//W3C//NOTATIONS XHTML Notations 1.0//EN"
"xhtml-notations-1.mod" >
%xhtml-notations.mod;]]>
<!-- Datatypes Module ............................................ -->
<!ENTITY % xhtml-datatypes.module "INCLUDE" >
<![%xhtml-datatypes.module;[
<!ENTITY % xhtml-datatypes.mod
PUBLIC "-//W3C//ENTITIES XHTML Datatypes 1.0//EN"
"xhtml-datatypes-1.mod" >
%xhtml-datatypes.mod;]]>
<!-- Qualified Names Module ...................................... -->
<!ENTITY % xhtml-qname.module "INCLUDE" >
<![%xhtml-qname.module;[
<!ENTITY % xhtml-qname.mod
PUBLIC "-//W3C//ENTITIES XHTML Qualified Names 1.0//EN"
"xhtml-qname-1.mod" >
%xhtml-qname.mod;]]>
<!-- Additional Qualified Names .................................. -->
<!-- xhtml-legacy-1.mod -->
<!ENTITY % font.qname "%XHTML.pfx;font" >
<!ENTITY % basefont.qname "%XHTML.pfx;basefont" >
<!ENTITY % center.qname "%XHTML.pfx;center" >
<!ENTITY % s.qname "%XHTML.pfx;s" >
<!ENTITY % strike.qname "%XHTML.pfx;strike" >
<!ENTITY % u.qname "%XHTML.pfx;u" >
<!ENTITY % dir.qname "%XHTML.pfx;dir" >
<!ENTITY % menu.qname "%XHTML.pfx;menu" >
<!ENTITY % isindex.qname "%XHTML.pfx;isindex" >
<!-- xhtml-frames-1.mod -->
<!ENTITY % frameset.qname "%XHTML.pfx;frameset" >
<!ENTITY % frame.qname "%XHTML.pfx;frame" >
<!ENTITY % noframes.qname "%XHTML.pfx;noframes" >
<!-- xhtml-iframe-1.mod -->
<!ENTITY % iframe.qname "%XHTML.pfx;iframe" >
<!ENTITY % xhtml-events.module "IGNORE" >
<![%xhtml-events.module;[
<!ENTITY % xhtml-events.mod
PUBLIC "-//W3C//ENTITIES XHTML Intrinsic Events 1.0//EN"
"xhtml-events-1.mod" >
%xhtml-events.mod;]]>
<!-- Additional Common Attributes ................................ -->
<!-- include historical 'lang' attribute (which should
always match the value of 'xml:lang')
-->
<!ENTITY % lang.attrib
"xml:lang %LanguageCode.datatype; #IMPLIED
lang %LanguageCode.datatype; #IMPLIED"
>
<!-- Common Attributes Module .................................... -->
<!ENTITY % xhtml-attribs.module "INCLUDE" >
<![%xhtml-attribs.module;[
<!ENTITY % xhtml-attribs.mod
PUBLIC "-//W3C//ENTITIES XHTML Common Attributes 1.0//EN"
"xhtml-attribs-1.mod" >
%xhtml-attribs.mod;]]>
<!-- placeholder for content model redeclarations -->
<!ENTITY % xhtml-model.redecl "" >
%xhtml-model.redecl;
<!-- Document Model Redeclarations ............................... -->
<!ENTITY % InlPres.class
"| %tt.qname; | %i.qname; | %b.qname; | %big.qname;
| %small.qname; | %sub.qname; | %sup.qname;
| %font.qname; | %basefont.qname; | %iframe.qname;
| %s.qname; | %strike.qname; | %u.qname;"
>
<!ENTITY % InlSpecial.class
"| %img.qname; | %map.qname;
| %applet.qname; | %object.qname;" >
<!ENTITY % BlkPres.class
"| %hr.qname; | %center.qname;"
>
<!ENTITY % BlkSpecial.class
"| %table.qname; | %form.qname; | %fieldset.qname;
| %noframes.qname; | %isindex.qname;"
>
<!ENTITY % List.class
"%ul.qname; | %ol.qname; | %dl.qname;
| %dir.qname; | %menu.qname;"
>
<!-- Document Model Module ...................................... -->
<!ENTITY % xhtml-model.module "INCLUDE" >
<![%xhtml-model.module;[
<!-- instantiate the Document Model module declared in the DTD driver
-->
%xhtml-model.mod;]]>
<!ENTITY % blockquote.content
"( #PCDATA | %Flow.mix; )*"
>
<!ENTITY % noscript.content
"( #PCDATA | %Flow.mix; )*"
>
<!ENTITY % body.content
"( #PCDATA | %Flow.mix; )*"
>
<!-- redeclare content model of <html> to allow for either
body or frameset content. The SGML markup minimization
features used in HTML 4 do not apply, so the ambiguity
that necessitated separation into the separate Frameset
and Transitional DTDs is eliminated.
-->
<!ENTITY % html.content
"( %head.qname;, ( %body.qname; | %frameset.qname; ) )"
>
<!ENTITY % xhtml-charent.module "INCLUDE" >
<![%xhtml-charent.module;[
<!ENTITY % xhtml-charent.mod
PUBLIC "-//W3C//ENTITIES XHTML Character Entities 1.0//EN"
"xhtml-charent-1.mod" >
%xhtml-charent.mod;]]>
<!-- end of xhtml-legacy-redecl-1.mod -->
G.
References
This
appendix
is
normative
.
G.1.
Normative
References
-
[CSS2]
-
"
Cascading
Style
Sheets,
level
2
(CSS2)
Specification
",
W3C
Recommendation,
B.
Bos,
H.
W.
Lie,
C.
Lilley,
I.
Jacobs,
eds.
,
12
May
1998.
Available
at:
http://www.w3.org/TR/1998/REC-CSS2-19980512
-
[DOM]
-
"
Document
Object
Model
(DOM)
Level
1
Specification
",
L.
Wood
et
al.
,
1
October
1998.
Available
at:
http://www.w3.org/TR/1998/REC-DOM-Level-1-19981001
-
[HTML4]
-
"
HTML
4.01
Specification:
W3C
Recommendation
",
W3C
Recommendation,
D.
Raggett,
A.
Le
Hors,
I.
Jacobs,
eds.
,
24
December
1999.
Available
at:
http://www.w3.org/TR/1999/REC-html401-19991224
-
[IETF
BCP
47]
-
BCP
47,
consisting
of
RFC
5646:
Tags
for
Identifying
Languages
,
IETF
(Internet
Engineering
Task
Force)
Best
Current
Practice,
A.
Phillips,
M.
Davis.
2009.
Available
at:
http://www.rfc-editor.org/rfc/bcp/bcp47.txt
-
[ISO10646]
-
"
Information
Technology
--
Universal
Multiple-Octet
Coded
Character
Set
(UCS)
",
ISO/IEC
10646:2003,
as,
from
time
to
time,
amended,
replaced
by
a
new
edition
or
expanded
by
the
addition
of
new
parts.
(See
http://www.iso.org/iso/en/ISOOnline.openerpage
for
the
latest
version.)
-
[RFC1808]
-
(obsoleted,
see
[
URI
])
-
[RFC2045]
-
"
Multipurpose
Internet
Mail
Extensions
(MIME)
Part
One:
Format
of
Internet
Message
Bodies
",
RFC
2045,
N.
Freed,
N.
Borenstein,
November
1996.
Available
at:
http://www.ietf.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.ietf.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
-
[RFC3987]
-
"
Internationalized
Resource
Identifiers
(IRI)
",
RFC
3987,
M.Duerst,
M.
Suignard
January
2005.
Available
at:
http://www.ietf.org/rfc/rfc3987.txt
-
[SRGB]
-
"
A
Standard
Default
Color
Space
for
the
Internet
",
version
1.10,
M.
Stokes,
M.
Anderson,
S.
Chandrasekar,
and
R.
Motta,
5
November
1996.
Available
at:
http://www.w3.org/Graphics/Color/sRGB
-
[UNICODE]
-
"
The
Unicode
Standard,
Version
4.1
",
as
updated
from
time
to
time
by
the
publication
of
new
versions,
The
Unicode
Consortium.
See
http://www.unicode.org/unicode/standard/versions
for
the
latest
version
and
additional
information
on
versions
of
the
standard
and
of
the
Unicode
Character
Database).
-
[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.
This
RFC
updates
RFC
1738
[
URL
]
and
obsoletes
RFC
2732,
2396
and
1808.
-
[URL]
-
"
Uniform
Resource
Locators
(URL)
",
RFC
1738,
T.
Berners-Lee,
L.
Masinter,
M.
McCahill,
December
1994.
Available
at:
http://www.ietf.org/rfc/rfc1738.txt
-
[XHTML1]
-
"
XHTML
1.0:
The
Extensible
HyperText
Markup
Language
(Second
Edition)
",
W3C
Recommendation,
S.
Pemberton
et
al.
,
26
January
2000,
revised
1
August
2002.
Available
at:
http://www.w3.org/TR/2002/REC-xhtml1-20020801
-
[XML]
-
"
Extensible
Markup
Language
(
XML
)
1.0
(Fourth
Edition)
",
W3C
Recommendation,
T.
Bray,
J.
Paoli,
C.
M.
Sperberg-McQueen,
E.
Maler,
F.
Yergeau,
eds.
,
16
August
2006.
Available
at:
http://www.w3.org/TR/2006/REC-xml-20060816
-
[XMLNAMES]
-
"
Namespaces
in
XML
(Second
Edition)
",
W3C
Recommendation,
T.
Bray,
D.
Hollander,
A.
Layman,
eds.
,
17
August
2006.
Available
at:
http://www.w3.org/TR/2006/REC-xml-names-20060816
-
[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/
See
also
"
XML
Schema
Part
2:
Datatypes
Second
Edition
",
available
at:
http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/
G.2.
Informative
References
-
[MATHML]
-
"
Mathematical
Markup
Language
(MathML)
Version
2.0
(Second
Edition)
",
W3C
Recommendation,
D.
Carlisle,
P.
Ion,
R.
Miner,
N.
Poppelie,
eds.
,
21
October
2003.
Available
at:
http://www.w3.org/TR/2003/REC-MathML2-20031021/
-
[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/
about
SGML.
-
[SMIL]
-
"
Synchronized
Multimedia
Integration
Language
",
W3C
Recommendation,
D.
Bulterman
et
al.,
eds.
Available
at:
http://www.w3.org/TR/SMIL/
-
[XHTMLBASIC]
-
"
XHTML
Basic
",
W3C
Recommendation,
S.
McCarron,
et
al.,
eds.
Available
at:
http://www.w3.org/TR/xhtml-basic/
-
[XHTML11]
-
"
XHTML
1.1
-
Module-based
XHTML
",
W3C
Recommendation,
M.
Altheim,
S.
McCarron
eds.
,
31
May
2001.
Available
at:
http://www.w3.org/TR/2001/REC-xhtml11-20010531/
The
latest
version
is
available
at:
http://www.w3.org/TR/xhtml11/
-
[XLINK]
-
"
XML
Linking
Language
(XLink)
Version
1.0
",
W3C
Recommendation,
S.
DeRose,
E.
Maler,
D.
Orchard,
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.
Available
at:
http://www.w3.org/1999/06/REC-xml-stylesheet-19990629
H.
Design
Goals
This
appendix
is
informative
.
In
this
appendix,
design
goals
are
identified
with
a
label
"Gn",
and
requirements
are
identified
with
a
label
"Rn.n".
There
are
four
major
design
goals
for
the
modularization
framework
for
XHTML:
-
[G1]
To
group
semantically
related
parts
of
XHTML
together.
-
[G2]
Using
DTD
technology,
to
support
the
creation
of
related
languages
(subsets,
supersets)
for
specific
purposes
(small
devices,
special-purpose
devices),
while
guaranteeing
commonality
of
the
overlapping
parts.
-
[G3]
To
facilitate
future
development
by
allowing
parts
of
the
language
to
be
replaced
by
improved
modules
(for
instance,
forms)
without
disturbing
the
rest
of
the
language.
-
[G4]
To
encourage
and
facilitate
the
reuse
of
modules
in
other
languages.
H.1.
Requirements
The
design
goals
listed
in
the
previous
section
lead
to
a
large
number
of
requirements
for
the
modularization
framework.
These
requirements,
summarized
in
this
section,
can
be
further
classified
according
to
the
major
features
of
the
framework
to
be
described.
H.1.1.
Granularity
Collectively
the
requirements
in
this
section
express
the
desire
that
the
modules
defined
within
the
framework
hit
the
right
level
of
granularity:
-
[R1.1]
Abstract
modules
should
promote
and
maintain
content
portability.
-
[R1.2]
Abstract
modules
should
promote
platform
profile
standardization.
-
[R1.3]
Abstract
modules
should
be
large
enough
to
promote
interoperability.
-
[R1.4]
Abstract
modules
should
be
small
enough
to
avoid
the
need
for
subsets.
-
[R1.5]
Abstract
modules
should
collect
elements
with
similar
or
related
semantics.
-
[R1.6]
Abstract
modules
should
separate
elements
with
dissimilar
or
unrelated
semantics.
-
[R1.7]
Modules
should
be
small
enough
to
allow
single
element
document
type
modules.
H.1.2.
Composibility
The
composibility
requirements
listed
here
are
intended
to
ensure
that
the
modularization
framework
be
able
to
express
the
right
set
of
target
modules
required
by
the
communities
that
will
be
served
by
the
framework:
-
[R2.1]
The
module
framework
should
allow
construction
of
abstract
modules
for
XHTML
1.0.
-
[R2.2]
The
module
framework
should
allow
construction
of
abstract
modules
that
closely
approximate
HTML
4.
-
[R2.3]
The
module
framework
should
allow
construction
of
abstract
modules
for
other
W3C
Recommendations.
-
[R2.4]
The
module
framework
should
allow
construction
of
abstract
modules
for
other
XML
document
types.
-
[R2.5]
The
module
framework
should
allow
construction
of
abstract
modules
for
a
wide
range
of
platform
profiles.
H.1.3.
Ease
of
Use
The
modularization
framework
will
only
receive
widespread
adoption
if
it
describes
mechanisms
that
make
it
easy
for
our
target
audience
to
use
the
framework:
-
[R3.1]
The
module
framework
should
make
it
easy
for
document
type
designers
to
subset
and
extend
XHTML
abstract
modules.
-
[R3.2]
The
module
framework
should
make
it
easy
for
document
type
designers
to
create
abstract
modules
for
other
XML
document
types.
-
[R3.3]
The
module
framework
should
make
it
easy
for
document
authors
to
validate
elements
from
different
abstract
modules.
H.1.4.
Compatibility
The
intent
of
this
document
is
that
the
modularization
framework
described
here
should
work
well
with
the
XML
and
other
standards
being
developed
by
the
W3C
Working
Groups:
-
[R4.1]
The
module
framework
should
strictly
conform
to
the
XML
1.0
Recommendation.
-
[R4.2]
The
module
framework
should
be
compatible
with
the
XML
Linking
Language
(XLink)
[XLINK]
specification.
-
[R4.3]
The
module
framework
should
be
compatible
with
the
Associating
Style
Sheets
with
XML
documents
[XMLSTYLE]
specification.
-
[R4.4]
The
module
framework
should
be
able
to
adopt
new
W3C
Recommendations
where
appropriate.
-
[R4.5]
The
module
framework
should
not
depend
on
W3C
work
in
progress.
-
[R4.6]
The
module
framework
should
not
depend
on
work
done
outside
W3C.
The
effectiveness
of
the
framework
will
also
be
measured
by
how
easy
it
is
to
test
the
behavior
of
modules
developed
according
to
the
framework,
and
to
test
the
documents
that
employ
those
modules
for
validation:
-
[R5.1]
It
should
be
possible
to
validate
documents
constructed
using
elements
and
attributes
from
abstract
modules.
-
[R5.2]
It
should
be
possible
to
explicitly
describe
the
behavior
of
elements
and
attributes
from
abstract
modules.
-
[R5.3]
It
should
be
possible
to
verify
the
behavior
of
elements
and
attributes
from
abstract
modules.
-
[R5.4]
It
should
be
possible
to
verify
a
hybrid
document
type
as
an
XHTML
document
type.
-
[R5.5]
Modules
defined
in
accordance
with
the
methods
in
this
document
shall
not
duplicate
the
names
of
elements
or
parameter
entities
defined
in
XHTML
modules.
J.
Acknowledgements
This
appendix
is
informative
.
This
specification
was
prepared
by
the
W3C
XHTML
2
Working
Group.
The
members
at
the
time
of
publication
of
version
1.0
were:
-
Steven
Pemberton,
CWI
(
HTML
Working
Group
Chair)
-
Murray
Altheim,
Sun
Microsystems
-
Daniel
Austin,
Mozquito
Technologies
-
Jonny
Axelsson,
Opera
Software
-
Mark
Baker,
Sun
Microsystems
-
Wayne
Carr,
Intel
-
Tantek
Çelik,
Microsoft
-
Doug
Dominiak,
Openwave
Systems
-
Andrew
W.
Donoho,
IBM
-
Herman
Elenbaas,
Philips
Electronics
-
Beth
Epperson,
Netscape/
AOL
-
Masayasu
Ishikawa,
W3C
(
HTML
Activity
Lead)
-
Shin'ichi
Matsui,
Panasonic
-
Shane
McCarron,
Applied
Testing
and
Technology
-
Ann
Navarro,
WebGeek,
Inc.
-
Peter
Stark,
Ericsson
-
Michel
Suignard,
Microsoft
-
Jeremy
Wadsworth,
Quark
Inc.
-
Malte
Wedel,
Mozquito
Technologies
-
Ted
Wugofski,
Openwave
Systems
The
contributors
to
the
original
Modularization
of
XHTML
in
XML
Schema
effort
were:
The
members
at
the
time
of
publication
of
version
1.1
were:
-
Roland
Merrick
IBM
(
XHTML
2
Working
Group
Co-Chair)
-
Steven
Pemberton,
CWI
(
XHTML
2
Working
Group
Co-Chair)
-
Mark
Birbeck,
webBackplane
-
Susan
Borgrink,
Progeny
Systems
-
Christina
Bottomley,
Society
for
Technical
Communication
(STC)
-
Alessio
Cartocci,
International
Webmasters
Association
/
HTML
Writers
Guild
(IWA-HWG)
-
Alexander
Graf,
University
of
Innsbruck
-
Tina
Holmboe,
Greytower
Technologies
-
John
Kugelman,
Progeny
Systems
-
Luca
Mascaro,
International
Webmasters
Association
/
HTML
Writers
Guild
(IWA-HWG)
-
Shane
McCarron,
Aptest
-
Michael
Rawling,
IVIS
Group
Limited
-
Gregory
Rosmaita,
Invited
Expert
-
Sebastian
Schnitzenbaumer,
Dreamlab
Technologies
AG
-
Richard
Schwerdtfeger,
IBM
-
Elias
Torres,
IBM
-
Masataka
Yakura,
Mitsue-Links
Co.,
Ltd.
-
Toshihiko
Yamakami,
ACCESS
Co.,
Ltd.
This
appendix
is
informative
.
This
specification
supercedes
XHTML
Modularization
1.0
.
This
section
describes
at
a
high
level
the
changes
from
that
version.
This
section
does
not
attempt
to
address
the
various
editorial
corrections
that
were
made.
For
a
detailed
comparison,
see
the
"diff
marked"
version
from
that
recommendation.