Identifies an entry in a row.
[Extracted from http://www.oasis-open.org/specs/a502.htm.]
Default values for colsep, rowsep, valign, align, char, and charoff may come from like-named attributes from the nearest element identified as influencing this entry. The values may come from table, tgroup, colspec (defining namest or colname), tbody, or row. Note that colspec is not strictly in the element lineage.
The char and charoff attributes are allowed on colspec as well as on entry. While an implementation should accept these attributes on either of these elements upon input, it may produce logically equivalent output that nevertheless differs with respect to these attributes and still be considered in compliance with the semantics of this Memorandum. A table with one or more entrys with values of either char or charoff that differ from the value for the same attribute on any other entry in that logical column or from a colspec that logically contains the entry(s) does not conform to the model defined in this Memorandum. It is left up to the implementation receiving such a table to determine how it should be handled. It is recommended that an authoring or editing implementation or any implementation that verifies the compliance of the table markup to this Memorandum offer the option of producing a warning message when it encounters such markup.
An entry gets its defaults from its starting column. A row has no explicit entry in any column into which a vertical straddle occurs because of a morerows attribute on an entry from a prior row. A spanning entry has no explicit repeated entrys in the columns to the right of the column identified by namest. An entry without specific starting column (a namest attribute) cannot span, and falls in the next non-straddled
non-spanned column.
The precedence for determining the column(s) for any entry is:
span before individual column:
namest through nameend
individual column:
namest
colname if no namest
implicit if neither namest or colname
The implicit Memorandum places the entry in the next available column.
There are various markup combinations which this Memorandum defines as "erroneous" and referred to as "errors" in some of the following attribute descriptions. It is left up to the implementation how to handle each of these situations:
any column referenced by name (either colname, namest or nameend) is not a colname of a colspec in that tgroup;
any of those names are multiply defined in different colspecs of that tgroup;
any portions of different entrys overlap each other;
morerows vertical straddling extends beyond the rows appropriate to that thead or tbody;
too many entrys occur in any row, exceeding the cols on the tgroup;
any colnames used in namest and nameend to define a span in an entry refers to the namest column that is not to the left of the nameend column;
an entry specifies a start column via entry's namest or colname that is to the left of the column where the entry would be placed by default.
It is recommended that an authoring or editing implementation or any implementation that verifies the compliance of the table markup to this Memorandum offer the option of producing a warning message when it encounters such markup. It is an error for an authoring or editing implementation to produce a table with such markup.
If the content of an entry is too deep for the available depth of a page, what information is presented and how it is presented is left to be determined by the implementation.
Note on terminology:
A spanning table cell is one that occupies more than one column. In this DTD, the only way a table cell (entry) can span is by specifying both namest and nameend attributes.
A straddling table cell is one that occupies more than one row. In this DTD, the only way a table cell (entry) can straddle multiple rows is by specifying a morerows attribute.
Spanning and straddling are independent; a spanning cell can also straddle.
View entry's attributes
View entry's content model
Created: Tue Dec 23 14:02:01 2003