Element Groups
To shorten the lists in each element to describe the
"Elements Allowed Within..." and "Allowed In Content Of..."
various elements are defined by RFC 1866 as members of a group.
These group names are used throughout the RFC 1866.
Since group names can be defined to contain other group names,
this mechanism makes nesting and recursion more obvious.
Note that these element groups only deal with entities defined in RFC 1866
and do not include any of the entities in proposed extensions.
block
Contains the groups
,
,
and the entities
and
The tables proposal defines the element
as a member of this group
block.forms
Contains the entities
,
and
body.content
Is allowed to contain the groups
,
,
and the entities
and
It is recommended that it contain only the groups
,
and the entities
,
and
This recommended change in the members of this group means that
all text within a body should be enclosed in some kind of block.
This means that
<h1>Heading<h1>
<p>Text ...
is recommended over
<h1>Heading<h1>
Text ...
font
Contains the entities
,
and
heading
Contains the entities
,
,
,
,
and
list
Contains the entities
,
,
and
Note that it does not contain
which is identified separately.
phrase
Contains the entities
,
,
,
,
,
and
preformated
Is allowed to contain the entities
,
and
The last two entities are deprecated
and this group should contain only the entity
text
Contains the groups
and
and the entities
,
and
and parsed character data.
Parsed character data is any valid character data after the data
has been parsed and all
entities have been replaced with their character data.
The internationalization proposal also includes in group text
the entities
,
,
,
,
