elements contain a set of alternative children, i.e. exactly one of them must be used in place of the alternative element. They are translated to alternatives (or-groups) in the DTD. Therefore, the name of an abstract element is not shown in the DTD and therefore not by the XML–editor. Still in this document, they are retained since they greatly contribute to clarity. Also, they are often used to use the same group of alternatives in different elements. Aliases are used in cases where elements with different names share the same syntactic structure. They appear as distinct elements in the DTD but are specified together in the HSL–file to ease maintenance. Note that the aliasing refers to the syntax only. The semantics of such twins are often contradictory (e.g., is-at-end and is-at-start). The following table gives an example of how elements are described in this document. 1E.g. in numerical-constant, the value is shown after the unit instead before it, which would be more intuitive.
[1]
Yuval Shahar,et al.
The Asgaard project: a task-specific framework for the application and critiquing of time-oriented clinical guidelines
,
1998,
Artif. Intell. Medicine.
[2]
Silvia Miksch,et al.
Abstracting Steady Qualitative Descriptions over Time from Noisy, High-Frequency Data
,
1999,
AIMDM.
[3]
James F. Allen.
Towards a General Theory of Action and Time
,
1984,
Artif. Intell..
[4]
Yuval Shahar,et al.
ASBRU: A TASK-SPECIFIC, INTENTION-BASED, AND TIME-ORIENTED LANGUAGE FOR REPRESENTING SKELETAL PLANS
,
1999
.
[5]
Silvia Miksch,et al.
Continual Planning with Time-Oriented, Skeletal Plans
,
2000,
ECAI.