Character Data: A string consisting of one or more numbers or
other characters representing data as specified in the entity definitions below.
These character include US-ASCII codes, Latin-1 charset,
Symbol charset, and Special
Characters charsets. Cdata is never parsed but is rendered as presented,
thus "<" and "&" are rendered as displayable
characters. Line feeds are ignored while each carriage return and tab is replaced with
a space. Browsers may ignore leading and trailing whitespace within the
attribute value. CDATA attribute values are typically case-sensitive, though this is not the
case with all attributes that take CDATA values.
Parsed Character Data: A character string that can be read and interpreted
by the user agent or server side application. The same characters allowed for cdata are
acceptable. The left angle "<" is interpreted as the start of an
element, and the ampersand "&" is interpreted as the start of an
entity. Substitute < and & to over-ride this behavior.
Named tokens: arbitrarily assigned names that represent various members of a
defined set of names in a controlled vocabulary. For example, the use of "en" to refer to
English as a member of the set of all languages. Frequently these are
described in a defined namespace.
The attribute is optional and need not be defined. The implication refers to the default or inherited value that is applied if not
otherwise specified.
This element is presently supported however it is in disfavor and may be
dropped from future specifications. There are always suitable
alternatives which should be used.
This denotes declaration of an XHTML entity. The entity name is immediately followed by its respective
attribute list. Comments in curly braces provide additional descriptive information.
This denotes declaration of an XHTML element. The element name is immediately followed by its respective
child elements in parentheses followed by its attribute list.
Comments in curly braces provide additional descriptive information.
This denotes declaration of an XHTML element. The element name is immediately followed by its respective
child elements in parentheses followed by its attribute list.
Comments in curly braces provide additional descriptive information. Block
elements may not be nested inside other block elements but may contain inline
elements.
This denotes declaration of an XHTML element. The element name is immediately followed by its respective
child elements in parentheses followed by its attribute list.
Comments in curly braces provide additional descriptive information. Inline
elements can be inside either block or inline elements, may contain other
inline elements, and may not contain block elements unless specifically noted.
Note: This element requires a head and body container. Theoretically, there could be a variety of named body elements for different purposes, however no present browsers support this capability.
Note: Exactly one title element and a meta
element to set the charset are required. The others are
optional. There can only be one head container per html container.
Author's note: the profile attribute appears to be a hook included in
XHTML to provide a catchall means to extend the function of the markup. There
are three instances when a profile seems to be needed. First, acceptable
values for the rel and rev attributes provided in the anchor
and link elements must be defined for them to be useful. W3C suggests
some possible meanings but no real standard exists--yet. I have published an
ontology in both html
and xml/rdf
as as early attempt at defining these. Second, XML namespaces must be declared
before they can be used. For example, in the Dublin
CoreDC:Author meta-element, the meaning of "Author"
is defined in the "DC" namespace, so without an explicit reference to
that namespace, "Author" has no meaning. Third, properly designed meta
description requires the use of ontologies (controlled vocabularies) or
structural specifications (complex datatyping such as URI). I have published a
possible implementation of such a profile in both html
and xml/rdf to demonstrate how
it might be implemented. While the use of this profile is open to general
use, it should not be considered a standard and is subject to change. The author
invites comments and suggestions.
Note: The title element is not considered part of the flow of text. It should
be displayed, for example, as the page header when printed or in the window
titlebar. Exactly one title
is required per document.
Note: Meta tags provide a means to pass information about the nature of the
document. Some search engines use various declarations to classify searches.
However, most meta information is not used in the indexing process. The content
of a meta tag is defined by the external application that is evaluating it.
Note: the name attribute used in the Meta Elements is different from
the name attribute used in other elements. Semantically, it is the subject of
the triple, scheme describes the nature of the predicate, and content is the
predicate of the triple.
for document specific toolbars/menus when used with the link element in document head e.g. start,
contents, previous, next, index, end, help;
to link to a separate style sheet (rel="stylesheet");
to make a link to a script (rel="script");
by stylesheets to control how collections of html nodes are rendered into printed
documents, or
to make a link to a printable version of this document e.g. a PostScript or PDF version (rel="alternate" media="print".
Note: the rev and rel attributes describe the semantic
relationship between two resources. For example rel="parent" and
rev="child". These relationships should be described in the
document specified in the head element profile attribute.
Note: This element was intended to provide a means to provide user input into a
script positioned in the head container that runs before the page loads. It is
the only input element that can be placed in the head
container. For example, it could prompt for a
document name then run a script to load the selected document:
Alternatively, the use of the input element provides greater control options
when positioned in a body container.
Note: the noframes element is a block element however its contents
render only on user agents that either do not support frames or have frame
rendering suppressed. For example, It's used to provide a replacement for
nav links that ordinarily would be rendered in another frame.
Note: inline elements are required to be contained within flow elements.
Flow elements are prohibited inside inline elements and other flow elements except where specifically permitted.
Note: the basefont element works as either a block or an inline element.
It establishes a new size, color, and/or face from this point in the
document until explicitly changed.
Note: when the hotspot specifications shape and coords are not
specified, the entire anchor content is a link; however, when specified only,
that region is a link.
Note: the rev and rel attributes describe the semantic
relationship between two resources. For example rel="parent" and
rev="child". These relationships should be described in the
document specified in the head element profile attribute.
Note:
param elements should precede other content with in the element. Parameters
can also be expressed as attribute/value pairs on the
object element itself when brevity is desired.
Note: one of code or object attributes must be present. Place param elements before other content.
The use of this element is non preferred as the object element provides
greater capability.
data - (default) This means that the value submitted by the value attribute will be evaluated and passed as a string
ref - This means that the value submitted by the value attribute will be an unresolved URI
object - This means that the value submitted by the value attribute will refer to an object declaration
Note: In XML it would seem natural to follow RDF and support an
abbreviated syntax where the param elements are replaced
by attribute value pairs on the object start tag.
Note: the contents of the script container must be valid functions and
expressions consistent with the programming language specified in the required type
attribute. The script content within the tags is identical to the content of the
external file. The script element is both block and inline.
Note: the noscript element should follow any block level script element to provide a suitable substitute for the functionality of the intended
scripting if the user agent cannot render the script. The noscript
element is both block and inline.
Note: to avoid accessibility problems for people who aren't
able to see the image, you should provide a text
description using the alt and longdesc attributes.
In addition, avoid the use of server-side image maps.
Note: although a number of elements can be held in this container, normally the only elements within are
area elements. The map element is inline only.
Note: these can be placed in the same document or grouped in a separate document although this is not widely supported yet.
A hotspot is simply an area on the image map of specified shape and
dimension that when clicked loads the document specified in the href atttribute.
Note: the button element is legal either inside a form or as an inline element.
This element differs from the input button in that image and/or text content can
be placed inside the tags.
Note: the button element must not contain the following elements: a,
form, iframe, input, select, textarea, label, or button.
Note: only one legend element should occur in the content
and if present should only be preceded by whitespace.
Note: the fieldset tag is valid within the following tags: blockquote, body, center, dd, div, fieldset, form, iframe, li, noframes,
noscript, object, td, th
Note: 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.
* align and valign override positioning set by THEAD TFOOT TBODY TR COLGROUP
elements and is overridden by TH and TD settings.
Note: The headers attribute specifies a space-separated list of header
cells that provide header information for the current cell. It references the id
attributes of the headers. This is used most often to make tables more
accessible, for example the header information might be spoken before each cell
in a non-visual user agent.
Note: The axis attribute is used to place the cell into conceptual
categories that can be considered to form axes in an n-dimensional space. This
allows the user agent to then display the categorized cells in various ways.
Note: The scope attribute specifies the table cells that the current
cell provides header information for. A value of col indicates that the
cell is a header for the the rest of the column below it. A value of colgroup
indicates that the cell is a header for its current column group. A value of row
indicates that that the cell contains header information for the rest of the row
it is in. A value of rowgroup indicates that the cell is a header for its
row group. This attribute might be used in place of the header attribute and is
useful for rendering assistance by nonvisual browsers. This attribute was added
very late to the HTML 4 specification so support for this attribute is minimal.
* align and valign override positioning set by TR THEAD TFOOT TBODY COL
COLGROUP elements.
Note: The headers attribute specifies a space-separated list of header
cells that provide header information for the current cell. It references the id
attributes of the headers. This is used most often to make tables more
accessible, for example the header information might be spoken before each cell
in a non-visual user agent.
Note: The axis attribute is used to place the cell into conceptual
categories that can be considered to form axes in an n-dimensional space. This
allows the user agent to then display the categorized cells in various ways.
Note: The scope attribute specifies the table cells that the current
cell provides header information for. A value of col indicates that the
cell is a header for the the rest of the column below it. A value of colgroup
indicates that the cell is a header for its current column group. A value of row
indicates that that the cell contains header information for the rest of the row
it is in. A value of rowgroup indicates that the cell is a header for its
row group. This attribute might be used in place of the header attribute and is
useful for rendering assistance by nonvisual browsers. This attribute was added
very late to the HTML 4 specification so support for this attribute is minimal.
* align and valign override positioning set by TR THEAD TFOOT TBODY COL
COLGROUP elements.
ENTITY DECLARATIONS
Internal Names
[ENTITY] Bookmark—pcdata
{ A unique document wide identifier.}
Creates an item in a list of nmtokens used as the targets
for anchors. Attribute values of type ID and NAME must begin with a letter in
the range A-Z or a-z and may be followed by letters (A-Za-z), digits (0-9),
hyphens ("-"), underscores ("_"), colons (":"),
and periods ("."). These values are case-sensitive.
opens the child frame into a
full browser window (essentially breaking the frame out of the frameset).
_parent
render in the frameset document containing the frame
_blank
opens a new window and renders in that window.
framename
render in the named frame
Note: framename is the name of any child frame defined in a frameset.
FrameNames can also be created by the name attribute of iframe. Reserved framenames
begin with "_", named ones begin with a letter.
Note: the values _parent, _self, and _top are only meaningful in the context
of a framed (frameset) document and do not open a new window.
[ENTITY] Id—pcdata
{ A unique document wide identifier }
Id is used to connect to the
entity by either style or scripting. Attribute values of type ID must begin with a letter in the range A-Z or
a-z and may be followed by letters (A-Za-z), digits (0-9), hyphens
("-"), underscores ("_"), colons (":"), and
periods ("."). These values are case-sensitive.
Note: while the specification lists top, bottom, left, and right as legal
values, the browsers only respond to left, center, and right.
[ENTITY] Length—pcdata {
pixels or nn% for percentage length } Length attribute values may be either an integer--interpreted as a number of
pixels--or a percentage of the horizontal or vertical space. The value 50%
means half the available space while 50 means 50 pixels.
[ENTITY] MultiLength—pcdata { Length
or relative } MultiLength attribute values may be an integer in pixels, a percentage of the horizontal or vertical space, or a relative length expressed as i*
where i is an integer. In allotting space, a browser first allots pixel and percentage lengths, then divides the
remaining space among all elements with a relative length. An element with a length of 3* will be allotted three times the
space of an element with length 1*. The value * is equivalent to 1* and is often used to mean
"fill the remaining space."
A MultiLengths value is a comma-separated list of MultiLength values.
[ENTITY] Sname—pcdata
{ A unique document wide identifier.}
Creates an item in a list of nmtokens used to connect to
elements for client and server scripting. Attribute values of type NAME must
begin with a letter in the range A-Z or a-z and may be followed by letters (A-Za-z),
digits (0-9), hyphens ("-"), underscores ("_"), colons
(":"), and periods ("."). These values are case-sensitive.
[ENTITY] StyleSheet—pcdata { style sheet data
from either internal or external styling }
[ENTITY] TAlign—nmtoken
{ horizontal placement of element relative to document }
left
align at left side of document or context
center
align in the center of document or context
right
align at right side of document or context
[ENTITY] Text—cdata
{ text is a sequence of characters representing renderable content. }
Legal characters include either the tab, carriage return, line feed, or any of the characters of Unicode
[ENTITY] LinkTypes—nmtoken { space-separated list of link
types }
Options include alternate | stylesheet | start | next | prev | contents | index
| glossary | copyright | chapter | section | subsection | appendix | help | bookmark
[ENTITY] KeyChar—nmtoken { a single textual character
corresponding to the keys on the keyboard }
On MS Windows machines the user
presses the [ALT] key and then this key, on Apple/McIntosh machines, the [CMD]
key and this key.
KeyChar—implied { accessibility key character.
Best Practices suggests that when this property is defined, a suitable explanation
should be included in the title property.}