action 

<h:div class="summary">An action which might occur in scientific data or narrative.</h:div>
<h:div class="description">An action which might occur in scientific data or narrative. The definition is deliberately vague, intending to collect examples of possible usage. Thus an action could be addition of materials, measurement, application of heat or radiation. The content model is unrestricted. _action_ iself is normally a child of _actionList_.
  <h:p>The start, end and duration attributes should be interpreted as</h:p>
  <h:ul>
    <h:li>XSD dateTimes and XSD durations. This allows precise recording of time of day, etc, or duration after start of actionList. A
      <h:tt>convention="xsd"</h:tt>attribute should be used to enforce XSD.</h:li>
    <h:li>a numerical value, with a units attribute linked to a dictionary.</h:li>
    <h:li>a human-readable string (unlikely to be machine processable)</h:li>
  </h:ul>
  <h:p>
    <h:tt>startCondition</h:tt>and
    <h:tt>endCondition</h:tt>values are not constrained, which allows XSL-like
    <h:tt>test</h:tt>attribute values. The semantics of the conditions are yet to be defined and at present are simply human readable.</h:p>
  <h:p>The order of the
    <h:tt>action</h:tt>elements in the doc may, but will not always, define the order that they actually occur in.</h:p>
  <h:p>A delay can be shown by an
    <h:tt>action</h:tt>with no content. Repeated actions or actionLists are indicated through the count attribute.</h:p>
</h:div>
<h:div class="example" href="action1.xml"/>

Element Information

Model

anyCml | ANY element from ANY namespace OTHER than 'http://www.xml-cml.org/schema' | ANY element from LOCAL namespace 'No Namespace'
Children: anyCml

Attributes

QName Type Fixed Default Use Inheritable Annotation
convention namespaceRefType optional 
<h:div class="summary">A reference to a convention.</h:div>
<h:div class="description">There is no controlled vocabulary for conventions, but the author must ensure that the semantics are openly available and that there are mechanisms for implementation. The convention is inherited by all the subelements, so that a convention for
  <h:tt>molecule</h:tt>would by default extend to its
  <h:tt>bond</h:tt>and
  <h:tt>atom</h:tt>children. This can be overwritten if necessary by an explicit
  <h:tt>convention</h:tt>.
  <h:p>It may be useful to create conventions with namespaces (e.g.
    <h:tt>iupac:name</h:tt>). Use of
    <h:tt>convention</h:tt>will normally require non-STMML semantics, and should be used with caution. We would expect that conventions prefixed with "ISO" would be useful, such as ISO8601 for dateTimes.</h:p>
  <h:p>There is no default, but the conventions of STMML or the related language (e.g. CML) will be assumed.</h:p>
</h:div>
<h:div class="example" id="ex" href="convGroup1.xml"/>
count positiveNumberType optional 
<h:div class="summary">The count of the object.</h:div>
<h:div class="description">No fixed semantics or default, normally integers. It is presumed that the element can be multiplied by the count value.</h:div>
dictRef namespaceRefType optional 
<h:div class="summary">A reference to a dictionary entry.</h:div>
<h:div class="description">Elements in data instances such as _scalar_ may have a
  <h:tt>dictRef</h:tt>attribute to point to an entry in a dictionary. To avoid excessive use of (mutable) filenames and URIs we recommend a namespace prefix, mapped to a namespace URI in the normal manner. In this case, of course, the namespace URI must point to a real XML doc containing _entry_ elements and validated against STMML Schema.
  <h:p>Where there is concern about the dictionary becoming separated from the doc the dictionary entries can be physically included as part of the data instance and the normal XPointer addressing mechanism can be used.</h:p>
  <h:p>This attribute can also be used on _dictionary_ elements to define the namespace prefix</h:p>
</h:div>
<h:div class="example" href="dictRefGroup1.xml"/>
duration xsd:string optional 
<h:div class="summary">The duration of the action.</h:div>
<h:div class="description">Semantics undefined.</h:div>
end xsd:string optional 
<h:div class="summary">The end value.</h:div>
<h:div class="description">The end value in any allowable XSD representation of data.</h:div>
endCondition xsd:string optional 
<h:div class="summary">The end condition.</h:div>
<h:div class="description">
  <h:p>At present a human-readable string describing some condition when the ac tion should end. As XML develops it may be possible to add machine-processable semantics in this field.</h:p>
</h:div>
id idType optional 
<h:div class="summary">A unique ID for an element.</h:div>
<h:div class="description">Id is used for machine identification of elements and in general should not have application semantics. It is similar to the XML ID type as containing only alphanumerics, '_', ',' and '-' and and must start with an alphabetic character. Ids are case sensitive. Ids should be unique within local scope, thus all atoms within a molecule should have unique ids, but separated molecules within a doc (such as a published article) might have identical ids. Software should be able to search local scope (e.g. all atoms within a molecule). However this is under constant review.</h:div>
order actionOrderType optional 
<h:div class="summary">Describes whether child elements are sequential or parallel.</h:div>
<h:div class="description">There is no default.</h:div>
ref refType optional 
<h:div class="summary">A reference to an element of given type.</h:div>
<h:div class="description">
  <h:tt>ref</h:tt>modifies an element into a reference to an existing element of that type within the doc. This is similar to a pointer and it can be thought of a strongly typed hyperlink. It may also be used for "subclassing" or "overriding" elements.
  <br xmlns=""/>When referring to an element most of the "data" such as attribute values and element content will be on the full instantiated element. Therefore ref (and possibly id) will normally be the only attributes on the pointing element. However there may be some attributes (title, count, etc.) which have useful semantics, but these are element-specific</h:div>
<h:div class="example" href="refGroup1.xml"/>
start xsd:string optional 
<h:div class="summary">The start value.</h:div>
<h:div class="description">The start value in any allowable XSD representation</h:div>
startCondition xsd:string optional 
<h:div class="summary">The start condition.</h:div>
<h:div class="description">This can describe the condition(s) that has to be met before an action can begin, such as in a recipe. Semantics are unexplored but could be used to control robotic operations.</h:div>
title xsd:string optional 
<h:div class="summary">A title on an element.</h:div>
<h:div class="description">No controlled value.</h:div>
<h:div class="example" href="title1.xml"/>
type xsd:string optional 
<h:div class="summary">Type of the object.</h:div>
<h:div class="description">A qualifier which may affect the semantics of the object.</h:div>
units unitsType optional 
<h:div class="summary">Scientific units on an element.</h:div>
<h:div class="description">These must be taken from a dictionary of units. There should be some mechanism for validating the type of the units against the possible values of the element.</h:div>
Wildcard: ANY attribute from ANY namespace OTHER than 'http://www.xml-cml.org/schema'

Source 

<xsd:element name="action" id="el.action" substitutionGroup="anyCml">
  <xsd:annotation>
    <xsd:documentation>
      <h:div class="summary">An action which might occur in scientific data or narrative.</h:div>
      <h:div class="description">An action which might occur in scientific data or narrative. The definition is deliberately vague, intending to collect examples of possible usage. Thus an action could be addition of materials, measurement, application of heat or radiation. The content model is unrestricted. _action_ iself is normally a child of _actionList_.
        <h:p>The start, end and duration attributes should be interpreted as</h:p>
        <h:ul>
          <h:li>XSD dateTimes and XSD durations. This allows precise recording of time of day, etc, or duration after start of actionList. A
            <h:tt>convention="xsd"</h:tt>attribute should be used to enforce XSD.</h:li>
          <h:li>a numerical value, with a units attribute linked to a dictionary.</h:li>
          <h:li>a human-readable string (unlikely to be machine processable)</h:li>
        </h:ul>
        <h:p>
          <h:tt>startCondition</h:tt>and
          <h:tt>endCondition</h:tt>values are not constrained, which allows XSL-like
          <h:tt>test</h:tt>attribute values. The semantics of the conditions are yet to be defined and at present are simply human readable.</h:p>
        <h:p>The order of the
          <h:tt>action</h:tt>elements in the doc may, but will not always, define the order that they actually occur in.</h:p>
        <h:p>A delay can be shown by an
          <h:tt>action</h:tt>with no content. Repeated actions or actionLists are indicated through the count attribute.</h:p>
      </h:div>
      <h:div class="example" href="action1.xml"/>
    </xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:choice minOccurs="0" maxOccurs="unbounded">
      <xsd:element ref="anyCml"/>
      <xsd:any namespace="##other" processContents="lax"/>
      <xsd:any namespace="##local" processContents="lax"/>
    </xsd:choice>
    <xsd:attributeGroup ref="title"/>
    <xsd:attributeGroup ref="id"/>
    <xsd:attributeGroup ref="convention"/>
    <xsd:attributeGroup ref="dictRef"/>
    <xsd:attributeGroup ref="units"/>
    <xsd:attributeGroup ref="start"/>
    <xsd:attributeGroup ref="startCondition"/>
    <xsd:attributeGroup ref="duration"/>
    <xsd:attributeGroup ref="end"/>
    <xsd:attributeGroup ref="endCondition"/>
    <xsd:attributeGroup ref="type"/>
    <xsd:attributeGroup ref="actionOrder"/>
    <xsd:attributeGroup ref="count">
      <xsd:annotation>
        <xsd:documentation>
          <h:div class="specific">Number of times the action should be repeated.</h:div>
        </xsd:documentation>
      </xsd:annotation>
    </xsd:attributeGroup>
    <xsd:attributeGroup ref="ref"/>
    <xsd:anyAttribute namespace="##other" processContents="lax"/>
  </xsd:complexType>
</xsd:element>

Sample