Download Altova StyleVision 2010
Transcript
Reference Authentic Menu 685 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. © 2010 Altova GmbH Altova StyleVision 2010
Related documents
Altova StyleVision 2010
Altova StyleVision 2012
Altova StyleVision 2016 Basic Edition
Altova StyleVision User Manual
Data Extraction Tool - The California State University
Altova MapForce User Manual
manual - PhatWare
FAQs - BizFinx Portal
Altova StyleVision Professional Edition User Manual
DATAdesign The main program - Dilwyn Jones Sinclair QL Pages
DPOJET Jitter and Eye Diagram Analysis Tools
Altova UModel 2013