CALS/HTML Tables

•	whether the Authentic View user may insert XML tables (following either the CALS or the HTML table model) in the XML document or not, and

To enable XML tables in Authentic View, check the box marked Enable XML tables in Document Editor.

Enabling XML tables allows the Authentic View user to insert tables that can be structured and formatted as required by the user. This is as opposed to static and dynamic SPS tables, which are structured and formatted by you, the designer of the StyleVision Power Stylesheet. When an XML table is inserted in Authentic View, a set of XML elements conforming to either the CALS or HTML table model is inserted in the XML document. Cell content in Authentic View is entered as content of the corresponding element in the XML document. When the table is formatted in Authentic View, the appropriate attributes and their values are added to the relevant elements in the XML document.

In the combo box, select the table model (CALS or HTML) with which you want your schema table structure to correspond. This combo box is enabled only if the Enable XML tables check box has been checked. Note the following points:

•	The table elements in the schema must correspond exactly with the structure of the selected table model (either CALS or HTML) to ensure the correct functioning of this feature; however, they do not need to have the same names as those of the table model elements.

•	If a table element in the schema is named differently from the corresponding element in the selected table model, then the schema element must be mapped to the corresponding table model element by entering its name in the User Defined column of the CALS / HTML Table Properties dialog.

•

The names of all attributes of schema table elements must correspond exactly with the relevant attribute names in the table model. These attributes must therefore be defined in the schema. Attribute names must correspond exactly because when the Authentic View user modifies the table structure or enters (for HTML tables) table properties, Authentic View enters attributes and enters/modifies attribute values for the appropriate element in the XML file. If these attributes are not present in the schema or are named (or spelled) differently in the schema, then the XML file will be invalid.

After selecting the appropriate model, all elements in the selected model which do not exist in the table structure of the schema, or which do not have a corresponding schema element specified for it, are displayed in red. If a schema element exists that corresponds to a CALS/HTML element, then you must map this element to the corresponding CALS/HTML element.

Note: When all the elements in the CALS / HTML Table Properties dialog are displayed in black, this means that the schema contains elements that correspond to the elements of the selected table model. If an element name in the Default column is displayed in red, this indicates that either no corresponding schema element exists or that a corresponding schema element exists but has not been mapped to the table model element; in the latter case you must enter the name of the corresponding schema element into the User Defined column.

Caution: If all the element names are displayed in black, be aware that this does not necessarily mean that the table structure of the schema corresponds exactly with the selected table model. There may still be additional elements in the table structure of the schema that could cause errors. You should carefully check your schema for this. Also check the attributes of the schema elements for exact correspondence and naming. Absent or wrongly named attributes will cause validation errors if the Authentic View user uses table formatting properties that use these attributes.

Working with Tables, for a broader discussion of how tables can be used in an SPS.