Namespace: |
|
Type: |
anonymous complexType |
Content: |
complex, 20 attributes, 7 elements |
Defined: |
globally in cmlreact.xsd; see XML source |
Includes: |
definitions of 7 elements |
Used: |
at 1 location |
XML Representation Summary |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
<entry | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
</entry> |
<xsd:element id="el.entry" name="entry"> <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 maxOccurs="unbounded" minOccurs="0"> </xsd:choice> </xsd:sequence> </xsd:complexType> </xsd:element> |
Type: |
|
Use: |
optional |
Defined: |
Type: |
|
Use: |
optional |
Defined: |
<xsd:attribute id="att.convention" name="convention" type="namespaceRefType"> <xsd:annotation> <xsd:documentation> <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" href="convGroup1.xml" id="ex"/> </xsd:documentation> </xsd:annotation> </xsd:attribute> |
Type: |
|
Use: |
optional |
Defined: |
<xsd:attribute id="att.dataType" name="dataType" type="dataTypeType"> <xsd:annotation> <xsd:documentation> <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> </xsd:documentation> </xsd:annotation> </xsd:attribute> |
Type: |
xsd:nonNegativeInteger, predefined |
Use: |
optional |
Defined: |
<xsd:attribute id="att.fractionDigits" name="fractionDigits" type="xsd:nonNegativeInteger"> <xsd:annotation> <xsd:documentation> <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> </xsd:documentation> </xsd:annotation> </xsd:attribute> |
Type: |
|
Use: |
optional |
Defined: |
Type: |
xsd:nonNegativeInteger, predefined |
Use: |
optional |
Defined: |
<xsd:attribute id="att.length" name="length" type="xsd:nonNegativeInteger"> <xsd:annotation> <xsd:documentation> <h:div class="summary">Length of a scalar.</h:div> <h:div class="description">Probably will be replaced with xsd:schema tool.</h:div> </xsd:documentation> </xsd:annotation> </xsd:attribute> |
Type: |
xsd:float, predefined |
Use: |
optional |
Defined: |
<xsd:attribute id="att.maxExclusive" name="maxExclusive" type="xsd:float"> <xsd:annotation> <xsd:documentation> <h:div class="summary">maximum exclusive value.</h:div> <h:div class="description">by analogy with xsd:schema.</h:div> </xsd:documentation> </xsd:annotation> </xsd:attribute> |
Type: |
xsd:float, predefined |
Use: |
optional |
Defined: |
<xsd:attribute id="att.maxInclusive" name="maxInclusive" type="xsd:float"> <xsd:annotation> <xsd:documentation> <h:div class="summary">minimum inclusive value.</h:div> <h:div class="description">by analogy with xsd:schem.</h:div> </xsd:documentation> </xsd:annotation> </xsd:attribute> |
Type: |
xsd:positiveInteger, predefined |
Use: |
optional |
Defined: |
<xsd:attribute id="att.maxLength" name="maxLength" type="xsd:positiveInteger"> <xsd:annotation> <xsd:documentation> <h:div class="summary">maximum length of a scalar.</h:div> <h:div class="description">by analogy with xsd:schem.</h:div> </xsd:documentation> </xsd:annotation> </xsd:attribute> |
Type: |
xsd:float, predefined |
Use: |
optional |
Defined: |
<xsd:attribute id="att.minExclusive" name="minExclusive" type="xsd:float"> <xsd:annotation> <xsd:documentation> <h:div class="summary">minimum exclusive value.</h:div> <h:div class="description">by analogy with xsd:schema.</h:div> </xsd:documentation> </xsd:annotation> </xsd:attribute> |
Type: |
xsd:float, predefined |
Use: |
optional |
Defined: |
<xsd:attribute id="att.minInclusive" name="minInclusive" type="xsd:float"> <xsd:annotation> <xsd:documentation> <h:div class="summary">minimum inclusive value.</h:div> <h:div class="description">by analogy with xsd:schema.</h:div> </xsd:documentation> </xsd:annotation> </xsd:attribute> |
Type: |
xsd:nonNegativeInteger, predefined |
Use: |
optional |
Defined: |
<xsd:attribute id="att.minLength" name="minLength" type="xsd:nonNegativeInteger"> <xsd:annotation> <xsd:documentation> <h:div class="summary">minimum length of a scalar.</h:div> <h:div class="description">by analogy with xsd:schema.</h:div> </xsd:documentation> </xsd:annotation> </xsd:attribute> |
Type: |
xsd:string, predefined |
Use: |
optional |
Defined: |
<xsd:attribute id="att.pattern" name="pattern" type="xsd:string"> <xsd:annotation> <xsd:documentation> <h:div class="summary">Pattern constraint.</h:div> <h:div class="description">Based on xsd:schema.</h:div> </xsd:documentation> </xsd:annotation> </xsd:attribute> |
Type: |
|
Use: |
optional |
Defined: |
Type: |
xsd:string, predefined |
Use: |
required |
Defined: |
<xsd:attribute id="att.term" name="term" type="xsd:string" use="required"> <xsd:annotation> <xsd:documentation> <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> </xsd:documentation> </xsd:annotation> </xsd:attribute> |
Type: |
xsd:string, predefined |
Use: |
optional |
Defined: |
<xsd:attribute id="att.title" name="title" type="xsd:string"> <xsd:annotation> <xsd:documentation> <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"/> </xsd:documentation> </xsd:annotation> </xsd:attribute> |
Type: |
xsd:positiveInteger, predefined |
Use: |
optional |
Defined: |
<xsd:attribute id="att.totalDigits" name="totalDigits" type="xsd:positiveInteger"> <xsd:annotation> <xsd:documentation> <h:div class="summary">total digits in a scalar.</h:div> <h:div class="description">based on xsd:schema.</h:div> </xsd:documentation> </xsd:annotation> </xsd:attribute> |
Type: |
|
Use: |
optional |
Defined: |
<xsd:attribute id="att.units" name="units" type="unitsType"> <xsd:annotation> <xsd:documentation> <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> </xsd:documentation> </xsd:annotation> </xsd:attribute> |
Type: |
xsd:string, predefined |
Use: |
optional |
Defined: |
<xsd:attribute id="att.unitType" name="unitType" type="xsd:string"> <xsd:annotation> <xsd:documentation> <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> </xsd:documentation> </xsd:annotation> </xsd:attribute> |
Type: |
xsd:string, predefined |
Use: |
optional |
Defined: |
<xsd:attribute id="att.whiteSpace" name="whiteSpace" type="xsd:string"> <xsd:annotation> <xsd:documentation> <h:div class="summary">Whitespace.</h:div> <h:div class="description">Attached to entry. This may be obsolete.</h:div> </xsd:documentation> </xsd:annotation> </xsd:attribute> |
Type: |
|
Defined: |
<xsd:element ref="alternative"/> |
Type: |
anonymous complexType, mixed content |
Defined: |
<xsd:element ref="annotation"/> |
Type: |
anonymous complexType, mixed content |
Defined: |
<xsd:element ref="definition"/> |
Type: |
anonymous complexType, mixed content |
Defined: |
<xsd:element ref="description"/> |
Type: |
anonymous complexType, complex content |
Defined: |
<xsd:element ref="enumeration"/> |
Type: |
anonymous complexType, complex content |
Defined: |
<xsd:element ref="metadataList"/> |
Type: |
anonymous complexType, mixed content |
Defined: |
<xsd:element ref="relatedEntry"/> |
This XML schema documentation has been generated with DocFlex/XML RE 1.8.5 using DocFlex/XML XSDDoc 2.5.0 template set. DocFlex/XML RE is a reduced edition of DocFlex/XML, which is a tool for programming and running highly sophisticated documentation and reports generators by the data obtained from
any kind of XML files. The actual doc-generators are implemented in the form of special templates that are designed visually
using a high-quality Template Designer GUI basing on the XML schema (or DTD) files describing the data source XML. DocFlex/XML XSDDoc is a commercial template application of DocFlex/XML that implements a high-quality XML Schema documentation generator with simultaneous support of framed multi-file HTML,
single-file HTML and RTF output formats. (More formats are planned in the future). A commercial license for "DocFlex/XML XSDDoc" will allow you:
Once having only such a license, you will be able to run the fully-featured XML schema documentation generator both with DocFlex/XML (Full Edition) and with DocFlex/XML RE, which is a reduced free edition containing only the template interpretor / output generator. No other licenses will be required! But this is not all. In addition to it, a commercial license for "DocFlex/XML SDK" will allow you to modify the XSDDoc templates themselves as much as you want. You will be able to achieve whatever was impossible to do with the template parameters only.
And, of course, you could develop any template applications by your own! Please note that by purchasing a license for this software, you not only acquire a useful tool,
you will also make an important investment in its future development, the results of which you could enjoy later by yourself.
Every single your purchase matters and makes a difference for us! To purchase a license, please follow this link: http://www.filigris.com/shop/ |