cmlall.xsd

化学图形处理软件

            <h:pre>
 0  7  9
-7  0 -1
-9  1  0
      </h:pre></h:div>
                        </xsd:documentation>
                    </xsd:annotation>
                </xsd:enumeration>
                <xsd:enumeration value="squareAntisymmetricUT">
                    <xsd:annotation>
                        <xsd:documentation>
                            <h:div class="description">Square symmetric with the upper triangle explicit and diagonal and lower triangle omitted. Rows are of length n-1, n-2,... 2,1.
            <h:pre>
 7  9
   -1
      </h:pre>
is equivalent to      
            <h:pre>
 0  7  9
-7  0 -1
-9  1  0
      </h:pre></h:div>
                        </xsd:documentation>
                    </xsd:annotation>
                </xsd:enumeration>
                <xsd:enumeration value="diagonal">
                    <xsd:annotation>
                        <xsd:documentation>
                            <h:div class="description">Symmetric. Elements are zero except on the diagonal. No compressed representation available (use <h:tt>array</h:tt> element).</h:div>
            <h:pre>
1 0 0
0 3 0
0 0 4
      </h:pre>
                        </xsd:documentation>
                    </xsd:annotation>
                </xsd:enumeration>
                <xsd:enumeration value="upperTriangular">
                    <xsd:annotation>
                        <xsd:documentation>
                            <h:div class="description">Square. Elements are zero below the diagonal
            <h:pre>
1 2 3 4
0 3 5 6
0 0 4 8
0 0 0 2
      </h:pre></h:div>
                        </xsd:documentation>
                    </xsd:annotation>
                </xsd:enumeration>
                <xsd:enumeration value="upperTriangularUT">
                    <xsd:annotation>
                        <xsd:documentation>
                            <h:div class="description">Square. Elements below the diagonal are zero and omitted, and rows are of length n, n-1, ... , 2, 1.
            <h:pre>
1 2 3 4
  3 5 6
    4 8
      2
      </h:pre>
      is equivalent to
            <h:pre>
1 2 3 4
0 3 5 6
0 0 4 8
0 0 0 2
      </h:pre></h:div>
                        </xsd:documentation>
                    </xsd:annotation>
                </xsd:enumeration>
                <xsd:enumeration value="lowerTriangular">
                    <xsd:annotation>
                        <xsd:documentation>
                            <h:div class="description">Square. Elements are zero above the diagonal
            <h:pre>
1 0 0
7 3 0
9 2 4
      </h:pre></h:div>
                        </xsd:documentation>
                    </xsd:annotation>
                </xsd:enumeration>
                <xsd:enumeration value="lowerTriangularLT">
                    <xsd:annotation>
                        <xsd:documentation>
                            <h:div class="description">Square. Elements above the diagonal are zero and omitted, and rows are of length 1, 2, ...n.
            <h:pre>
1
3 7
9 2 3            
      </h:pre>
      is equivalent to
            <h:pre>
1 0 0
3 7 0
9 2 3            
      </h:pre></h:div>
                        </xsd:documentation>
                    </xsd:annotation>
                </xsd:enumeration>
                <xsd:enumeration value="unit">
                    <xsd:annotation>
                        <xsd:documentation>
                            <h:div class="description">Square. Diagonal elements are 1 and off-diagonal are zero. 
            <h:pre>
1 0 0
0 1 0
0 0 1            
      </h:pre></h:div>
                        </xsd:documentation>
                    </xsd:annotation>
                </xsd:enumeration>
                <xsd:enumeration value="unitary">
                    <xsd:annotation>
                        <xsd:documentation>
                            <h:div class="description">Square. When multiplied by its transpose gives the unit matrix. 
            <h:pre>
0 -1  0
1  0  0
0  0  1           
      </h:pre></h:div>
                        </xsd:documentation>
                    </xsd:annotation>
                </xsd:enumeration>
                <xsd:enumeration value="rowEigenvectors">
                    <xsd:annotation>
                        <xsd:documentation>
                            <h:div class="description">Square. Each row corresponds to an eigenvector of a square matrix. Elements are real. The length of the eigenvectors is undefined, i.e. they are not required to be normalised to 1.
            <h:pre>
0 -1  0
1  0  0
0  0  1           
      </h:pre></h:div>
                        </xsd:documentation>
                    </xsd:annotation>
                </xsd:enumeration>
                <xsd:enumeration value="rotation22">
                    <xsd:annotation>
                        <xsd:documentation>
                            <h:div class="description">The rotation is defined by the matrix premultiplyin a column vector (x, y) .
            <h:pre>
0 -1
1  0
      </h:pre>
      produces (-y, x), i.e. a rotation of -90 degrees.</h:div>
                        </xsd:documentation>
                    </xsd:annotation>
                </xsd:enumeration>
                <xsd:enumeration value="rotationTranslation32">
                    <xsd:annotation>
                        <xsd:documentation>
                            <h:div class="description">A third column defining the translation is added to a rotation22.
            <h:pre>
0 -1 22
1  0 33
      </h:pre>
      produces (-y + 22, x + 33), i.e. a rotation of -90 degrees followed by a translation of (22, 33).</h:div>
                        </xsd:documentation>
                    </xsd:annotation>
                </xsd:enumeration>
                <xsd:enumeration value="homogeneous33"/>
                <xsd:enumeration value="rotation33"/>
                <xsd:enumeration value="rotationTranslation43"/>
                <xsd:enumeration value="homogeneous44"/>
            </xsd:restriction>
        </xsd:simpleType>
        <xsd:simpleType>
            <xsd:restriction base="namespaceRefType">
                <xsd:annotation>
                    <xsd:documentation>
                        <h:div class="summary">User-defined matrix-type.</h:div>
                        <h:div class="description">This definition must be by reference to a namespaced dictionary entry.</h:div>
                    </xsd:documentation>
                </xsd:annotation>
            </xsd:restriction>
        </xsd:simpleType>
    </xsd:union>
</xsd:simpleType><xsd:simpleType name="metadataType" id="st.metadataType" xmlns:h="http://www.w3.org/1999/xhtml">
    <xsd:annotation>
        <xsd:documentation>
            <h:div class="summary">The name of the metadata.</h:div>
            <h:div class="description">Metadata consists of name-value pairs (value is in the "content" attribute). The names are from a semi-restricted vocabulary, mainly Dublin Core. The content is unrestricted. The order of metadata has no implied semantics at present. Users can create their own metadata names using the namespaced prefix syntax (e.g. foo:institution). Ideally these names should be defined in an STMML dictionary.</h:div>
            <h:div class="curation">2003-03-05: Added UNION to manage non-controlled name.</h:div>
        </xsd:documentation>
    </xsd:annotation>
    <xsd:union>
        <xsd:simpleType>
            <xsd:restriction base="xsd:string">
                <xsd:enumeration value="dc:coverage">
                    <xsd:annotation>
                        <xsd:documentation>
                            <h:div class="definition">The extent or scope of the
            content of the resource.</h:div>

                            <h:div class="description">Coverage will typically include
            spatial location (a place name or geographic
            coordinates), temporal period (a period label, date, or
            date range) or jurisdiction (such as a named
            administrative entity). Recommended best practice is to
            select a value from a controlled vocabulary (for
            example, the Thesaurus of Geographic Names [TGN]) and
            that, where appropriate, named places or time periods
            be used in preference to numeric identifiers such as
            sets of coordinates or date ranges.</h:div>
                        </xsd:documentation>
                    </xsd:annotation>
                </xsd:enumeration>

                <xsd:enumeration value="dc:description">
                    <xsd:annotation>
                        <xsd:documentation>
                            <h:div class="definition">An account of the content of the
            resource.</h:div>

                            <h:div class="description">Description may include but is not
            limited to: an abstract, table of contents, reference
            to a graphical representation of content or a free-text
            account of the content.</h:div>
                        </xsd:documentation>
                    </xsd:annotation>
                </xsd:enumeration>

                <xsd:enumeration value="dc:identifier">
                    <xsd:annotation>
                        <xsd:documentation>
                            <h:div class="definition">An unambiguous reference to the
            resource within a given context.</h:div>

                            <h:div class="description">Recommended best practice is to
            identify the resource by means of a string or number
            conforming to a formal identification system. Example
            formal identification systems include the Uniform
            Resource Identifier (URI) (including the Uniform
            Resource Locator (URL)), the Digital Object Identifier
            (DOI) and the International Standard Book Number
            (ISBN).</h:div>
                        </xsd:documentation>
                    </xsd:annotation>
                </xsd:enumeration>

                <xsd:enumeration value="dc:format">
                    <xsd:annotation>
                        <xsd:documentation>
                            <h:div class="definition">The physical or digital
            manifestation of the resource.</h:div>

                            <h:div class="description">Typically, Format may include the
            media-type or dimensions of the resource. Format may be
            used to determine the software, hardware or other
            equipment needed to display or operate the resource.
            Examples of dimensions include size and duration.
            Recommended be