entry 

<h:div class="summary">A dictionary entry.</h:div>
<h:div class="desacription">The original design for validation with attribute-based constraints is ponderous and fragile. In future constraints will be added through
  <h:tt>appinfo</h:tt>in
  <h:tt>annotation</h:tt>. We shall develop this further in the near future.</h:div>
<h:div class="curation">2003-03-30: added metadataList to content mode.</h:div>
<h:div class="example" href="entry1.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
columns sizeType optional 
<h:div class="summary">Number of columns.</h:div>
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"/>
dataType dataTypeType optional 
<h:div class="summary">The data type of the object.</h:div>
<h:div class="description">Normally applied to scalar/array objects but may extend to more complex one.</h:div>
fractionDigits xsd:nonNegativeInteger optional 
<h:div class="summary">Number of digits after the point.</h:div>
<h:div class="description">This is used in dictionaries to define precision. However it might be replaced by xsd:facet.</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>
length xsd:nonNegativeInteger optional 
<h:div class="summary">Length of a scalar.</h:div>
<h:div class="description">Probably will be replaced with xsd:schema tool.</h:div>
maxExclusive xsd:double optional 
<h:div class="summary">maximum exclusive value.</h:div>
<h:div class="description">by analogy with xsd:schema.</h:div>
maxInclusive xsd:double optional 
<h:div class="summary">minimum inclusive value.</h:div>
<h:div class="description">by analogy with xsd:schem.</h:div>
maxLength xsd:positiveInteger optional 
<h:div class="summary">maximum length of a scalar.</h:div>
<h:div class="description">by analogy with xsd:schem.</h:div>
minExclusive xsd:double optional 
<h:div class="summary">minimum exclusive value.</h:div>
<h:div class="description">by analogy with xsd:schema.</h:div>
minInclusive xsd:double optional 
<h:div class="summary">minimum inclusive value.</h:div>
<h:div class="description">by analogy with xsd:schema.</h:div>
minLength xsd:nonNegativeInteger optional 
<h:div class="summary">minimum length of a scalar.</h:div>
<h:div class="description">by analogy with xsd:schema.</h:div>
pattern xsd:string optional 
<h:div class="summary">Pattern constraint.</h:div>
<h:div class="description">Based on xsd:schema.</h:div>
rows sizeType optional 
<h:div class="summary">Number of rows.</h:div>
term xsd:string optional 
<h:div class="summary">A term in a dictionary.</h:div>
<h:div class="description">The term should be a noun or nounal phrase, with a separate definition and further description.</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"/>
totalDigits xsd:positiveInteger optional 
<h:div class="summary">total digits in a scalar.</h:div>
<h:div class="description">based on xsd:schema.</h:div>
unitType xsd:string optional 
<h:div class="summary">A reference to the type of a unit.</h:div>
<h:div class="description">Used in defining the unit and doing symbolic algebra on the dimensionality.</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="entry" id="el.entry" substitutionGroup="anyCml">
  <xsd:annotation>
    <xsd:documentation>
      <h:div class="summary">A dictionary entry.</h:div>
      <h:div class="desacription">The original design for validation with attribute-based constraints is ponderous and fragile. In future constraints will be added through
        <h:tt>appinfo</h:tt>in
        <h:tt>annotation</h:tt>. We shall develop this further in the near future.</h:div>
      <h:div class="curation">2003-03-30: added metadataList to content mode.</h:div>
      <h:div class="example" href="entry1.xml"/>
    </xsd:documentation>
  </xsd:annotation>
  <xsd:complexType>
    <xsd:sequence>
      <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:sequence>
    <xsd:attributeGroup ref="title"/>
    <xsd:attributeGroup ref="id"/>
    <xsd:attributeGroup ref="convention"/>
    <xsd:attributeGroup ref="dataType"/>
    <xsd:attributeGroup ref="rows"/>
    <xsd:attributeGroup ref="columns"/>
    <xsd:attributeGroup ref="unitType"/>
    <xsd:attributeGroup ref="minExclusive"/>
    <xsd:attributeGroup ref="minInclusive"/>
    <xsd:attributeGroup ref="maxExclusive"/>
    <xsd:attributeGroup ref="maxInclusive"/>
    <xsd:attributeGroup ref="totalDigits"/>
    <xsd:attributeGroup ref="fractionDigits"/>
    <xsd:attributeGroup ref="length"/>
    <xsd:attributeGroup ref="minLength"/>
    <xsd:attributeGroup ref="maxLength"/>
    <xsd:attributeGroup ref="units"/>
    <xsd:attributeGroup ref="pattern"/>
    <xsd:attributeGroup ref="term"/>
    <xsd:anyAttribute namespace="##other" processContents="lax"/>
  </xsd:complexType>
</xsd:element>

Sample