An important mechanism for specification of the generic ELEMENTs (XVAR, ARRAY, XLIST) is the BUILTIN attribute. Only certain values are given in the DTD (through *.ent files) and these are used to specify the type or use of the element. BUILTIN values can also be added by included DTDs. Postprocessing software must be able to interpret the values of BUILTINs - and there are about 100 such. Failing this, they should pass the values to the application program.
An example is BUILTIN="X2" for the 2-dimensional coordinates of an atomic array in the MOL.DTD DTD or BUILTIN="MATRIX" to require an ARRAY to be treated as a matrix. The mechanics of inclusion in the DTD is quite involved (hopefully hidden!), and the possible values of the attribute are provided in files (*-arr.ent, *-list.ent, *-var.ent) in the main DTD directory.
NOTE: The files referred to should always be taken as the primary enumeration of BUILTIN values; unfortunately due to limitations of SGML and the dtd2html software in this particular instance, they can't be automatically documented yet.
The potential values of BUILTIN will usually be described under the appropriate GI; often this contains an XVAR or similar subelement which has a builtin attribute. Thus the MATRIX example above will be documented under ARRAY, whilst X2 is under ATOMS.
Number of coumns in TABLE
NUMBER
STRUCT, ARRAY, TABLE, GRAPH, NODE (see above)
In certain contexts the CONVENTION defaults to a TecML-specific value. Thus DICTNAME within TERMENTRY refers to ISO12620 by default, and within the UNITS glossary to that glossary. In general, however, authors cannot assume any default other than the reserved values "" or LOCAL.
CDATA
Processing applications are under no obligation to process DICTNAME, but in that case should pass it to other applications.
CDATA
Hints to the rendering program on how to display the data. Possibilities might be GRAPH, SPREADSHEET, etc. This does NOT affect the data. The semantics are yet to be decided.
CDATA
The HREF attribute is inherited from HTML2.0 and is used consistently throughout CML. It serves as the tail of a hyperlink, whose semantics are being developed by Murray Maloney and others of the HTML-WG as an Internet draft.
Here is some more information.
CDATA
NAMES
NAME specifies the target of a hyperlink and must be unique within a document. It is used in the same way as in HTML, but note that whereas the A element appears to refer to a point in a document, all CML elements are containers and their extent is clearly defined. Here is some more information.
CDATA
The REL attribute is inherited from HTML2.0 and is used consistently throughout CML. It describes the target of a hyperlink, whose semantics are being developed by Murray Maloney and others of the HTML-WG as an Internet draft.
The use of REL is under review (Jan 1997). At present it has not been used as the CML addressing mechanisms are more advanced.
NAMES
The REV attribute is inherited from HTML2.0 and is used consistently throughout CML. It describes the backwards relationship of a hyperlink, whose semantics are being developed by Murray Maloney and others of the HTML-WG as an Internet draft.
At present CML does not specify a use and it should evolve in parallel with what the WWW community decides.
NAMES
Number of rows in TABLE
NUMBER
Number of contained items (without XHTML)
NUMBER
Name ('typedef') of STRUCT
CDATA
The attribute value of TITLE is searchable, but may be better as contents of an XVAR in some cases.
CDATA
The type of the content (XVAR or ARRAY). Applications and postprocessors should interpret the TYPE and transform the content if necessary. All defaults and error actions are presently undefined. At present TYPE is chosen from:
The definitive list of ARRAY types is kept in the file x-type.ent. These types are available to the elements, ARRAY, XLIST and XVAR. If TYPE is not given a value, it defaults to "", which is interpreted as STRING.
It's up to the application how TYPE is treated.
CDATA
CDATA