A xml element (or node) can be mapped into an object, simple or composite, or a builder/factory object. The attributes of xml nodes in ohmms and other applications are used to tell the applications something about the content of the node and to guide the applications what to do. The table below lists the attribute names commonly used by ohmms. The names follow docbook definitions[1] The meaning of each attribute depends on the element itself and the implementations within an application.
The id and name elements are common for all the nodes, even though they may not be explicitly stated in the reference pages.
The specialized meanings and the expected behaviors of the attributes for each node are discussed in the sections of the reference pages.
Table 2.1. Common attribute names and general meanings
| Name | General meanings |
|---|---|
| id | ID type, unique within a file as ID. Can be referenced within a file. |
| name | name of the object represented by the element. |
| condition | constraint on the element, such as, the unit of the object. |
| datatype | object type within an application. |
| src | an external file. |
| role | functions of the element. |
| class | class or category of the element. |
[1] It is very likely that many of the xml elements will be substituted by those of docbook or other standard DTD/schema and that namespace will be used for specializations.