If the number or range of steps is large or convoluted and their order or selection is really important, promote that order to an element.
<aircraft-approach-procedure>
<order>
<transition step="s1" condition="is-controlled()"/>
<transition step="s3"/>
<transition step="s5"/>
<order/>
<steps xml:lang="en">
<transition id="s3">Enter glide slope</transition>
<transition id="s2">Hide the whiskey</transition>
<transition id="s5">Correct for wind conditions</transition>
<transition id="s4">Wake the pilot</transition>
<transition id="s1">Contact control tower</transition>
</steps>
</aircraft-approach-order>
Contrary (to some extent) to what Frank said, every document type does embodies a theory about its use-case: the more complex the use case, the more likely that extra layers of clearly labelled indirection may be appropriate.
Cheers
Rick
Hi Folks,
Thanks again for the excellent responses.
Recall that I advocated for adding an attribute that indicates the order in which a list of elements are to be evaluated, e.g.,
<aircraft-approach-procedure>
<transition step="2">Enter glide slope</transition>
<transition step="3">Correct for wind conditions</transition>
<transition step="1">Contact control tower</transition>
</aircraft-approach-procedure>
The argument that dissuaded me most powerfully was this simple message from a colleague:
What is the benefit of adding @step (a
sequence number)? We are not using
key punch cards, so we will not drop it.
/Roger
_______________________________________________________________________
XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.
[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
subscribe: xml-dev-subscribe@lists.xml.org
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php