Help > Authoring > Working with Tables > OASIS Exchange Tables > Effects of Table Editing on OASIS Exchange Markup
  
Effects of Table Editing on OASIS Exchange Markup
Any time you edit a table, you affect the elements and attributes of the underlying table markup.
The following table shows the elements used to create a table image, those which are updated when the table is edited, those which are deleted when the table is loaded, and those which are changed by Arbortext Editor.
Element/Attribute
Used to Create Image
Updated When Edited
Deleted When Edited
Changed
TABLE: This element is visible when table is displayed in image mode (that is, when View > Tables > Table Markup is turned off).
<frame>
yes
yes
no
n/a
<colsep>
yes
yes
no
n/a
<rowsep>
yes
yes
no
n/a
<orient>
no
no
no
no
<pgwide>
no
no
no
no
TGROUP:
<cols>
yes
yes
no
yes
<colsep>
yes
yes
no
yes
<rowsep>
yes
yes
no
yes
<align>
yes
yes
no
yes
<charoff>
yes
yes
no
yes
<char>
yes
yes
no
yes
COLSPEC:
<colnum>
no
no
no
yes
<colname>
yes
yes
no
yes
<align>
yes
yes
no
yes
<charoff>
yes
yes
no
yes
<char>
yes
yes
no
yes
<colwidth>
yes
yes
no
yes
<colsep>
yes
yes
no
yes
<rowsep>
yes
yes
no
yes
SPANSPEC: Arbortext Editor will convert <spanspec> to <entry namest= nameend=> in a document unless the table model does not support <entry namest= nameend=>.
<namest>
yes
yes
no
yes
<nameend>
yes
yes
no
yes
<spanname>
yes
yes
sometimes
yes
<align>
yes
yes
no
yes
<charoff>
yes
yes
no
yes
<char>
yes
yes
no
yes
<colsep>
yes
yes
no
yes
<rowsep>
yes
yes
no
yes
THEAD:
<valign>
yes
yes
no
yes
TFOOT: Even though tfoot is not supported in the OASIS Exchange model, it is supported for any DTD that includes it.
<valign>
yes
yes
no
yes
TBODY:
<valign>
yes
yes
no
yes
ROW:
<rowsep>
yes
yes
no
yes
ENTRY:
<colname>
yes
yes
no
yes
<namest>
yes
yes
no
yes
<nameend>
yes
yes
no
yes
<spanname>
yes
yes
sometimes
yes
<morerows>
yes
yes
no
yes
<colsep>
yes
yes
no
yes
<rowsep>
yes
yes
no
yes
<rotate>
no
no
no
no
<valign>
yes
yes
no
yes
<align>
yes
yes
no
yes
<charoff>
yes
yes
no
yes
<char>
yes
yes
no
yes
ENTRYTBL: entrytbl content is displayed as markup, not as a nested table.
<cols>
no
no
no
n/a
<tgroupstyle>
no
no
no
n/a
<colname>
no
no
no
n/a
<spanname>
no
no
no
n/a
<colsep>
no
no
no
n/a
<rowsep>
no
no
no
n/a
<align>
no
no
no
n/a
<charoff>
no
no
no
n/a
<char>
no
no
no
n/a