HyTime attribute: Identifies the element or it's content as being significant to HyTime processing, and defines the corresponding HyTime architectural form
The HyTime values differs between elements, but it is always a fixed value that must not be changed.
For further explanations, see the HyTime standard (ISO 10744), clause 6.4.
NAME
Reference identity of the element.
Used to identify the element to enable referring by use of HyTime.
Due to the large number of required ID attributes, software for creating information modules should have the possibility to automatically generate ID values.
ID
Defines the target group for which the information in the module is written.
The possible values of this attribute must be defined by each project, based on the information analysis. See further Parameter Entity "malgrupp.varden" in chapter 8.
If attribute is not used, all target groups are implied. It is however good practice to always supply a value, even if the information is written for "all".
CDATA
Defines the status of the information module, in terms of production status, or version.
The values of this attribute must be defined by each project.
See further Parameter Entity "modulstatus.varden" in chapter 8.
CDATA
Defines the special conditions (external conditions or internal modes) to which the information in the module has been written.
The values of this attribute must be defined by each project, based on the information analysis. See further Parameter Entity "specforutsattn.varden" in chapter 8.
If attribute is unused, no special conditions are implied. It is however good practice to always supply a value, even if the information is written for "normal use".
CDATA
Defines the language used in the information module
The values of this attribute must be defined by each project, based on the information analysis.
See further Parameter Entity "sprak.varden" in chapter 8.
CDATA
Defines the maintenance level for which the information in the module is written.
The values of this attribute must be defined by each project.
See further Parameter Entity "uhniva.varden" in chapter 8.
If attribute is unused, "all maintenance levels" are implied. It is however good practice to always supply a value, even if the information is written for "all".
CDATA