element <entry> (global)
Namespace:
Type:
anonymous complexType
Content:
complex, 20 attributes, 7 elements
Defined:
globally in cmlreact.xsd; see XML source
Includes:
definitions of 7 elements
Used:
XML Representation Summary
<entry
   
 = 
xsd:nonNegativeInteger
 = 
xsd:string
 = 
(("xsd:string" | "xsd:boolean" | "xsd:float" | "xsd:double" | "xsd:decimal" | "xsd:duration" | "xsd:dateTime" | "xsd:time" | "xsd:date" | "xsd:gYearMonth" | "xsd:gYear" | "xsd:gMonthDay" | "xsd:gDay" | "xsd:gMonth" | "xsd:hexBinary" | "xsd:base64Binary" | "xsd:anyURI" | "xsd:QName" | "xsd:NOTATION" | "xsd:normalizedString" | "xsd:token" | "xsd:language" | "xsd:IDREFS" | "xsd:ENTITIES" | "xsd:NMTOKEN" | "xsd:NMTOKENS" | "xsd:Name" | "xsd:NCName" | "xsd:ID" | "xsd:IDREF" | "xsd:ENTITY" | "xsd:integer" | "xsd:nonPositiveInteger" | "xsd:negativeInteger" | "xsd:long" | "xsd:int" | "xsd:short" | "xsd:byte" | "xsd:nonNegativeInteger" | "xsd:unsignedLong" | "xsd:unsignedInt" | "xsd:unsignedShort" | "xsd:unsignedByte" | "xsd:positiveInteger") | xsd:string)
 = 
xsd:nonNegativeInteger
 = 
xsd:string
 = 
xsd:nonNegativeInteger
 = 
xsd:float
 = 
xsd:float
 = 
xsd:positiveInteger
 = 
xsd:float
 = 
xsd:float
 = 
xsd:nonNegativeInteger
 = 
xsd:string
 = 
xsd:nonNegativeInteger
 = 
xsd:string
 = 
xsd:string
 = 
xsd:positiveInteger
 = 
xsd:string
 = 
xsd:string
 = 
xsd:string
    >
   
Content: 
(metadataList | alternative | annotation | definition | description | enumeration | relatedEntry)*
</entry>
Content model elements (7):
alternative, annotation, definition, description, enumeration, metadataList, relatedEntry
Included in content model of elements (1):
dictionary
Known Usage Locations
Annotation
<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"/>
XML Source (see within schema source)
<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:element ref="metadataList"/>
<xsd:element ref="alternative"/>
<xsd:element ref="annotation"/>
<xsd:element ref="definition"/>
<xsd:element ref="description"/>
<xsd:element ref="enumeration"/>
<xsd:element ref="relatedEntry"/>
</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="whiteSpace"/>
<xsd:attributeGroup ref="pattern"/>
<xsd:attributeGroup ref="term"/>
</xsd:complexType>
</xsd:element>
Attribute Detail (all declarations; 20/20)
columns
Type:
Use:
optional
Defined:
locally within columns attributeGroup
<h:div class="summary">Number of columns.</h:div>
XML Source (see within schema source)
<xsd:attribute id="att.columns" name="columns" type="sizeType">
<xsd:annotation>
<xsd:documentation>
<h:div class="summary">Number of columns.</h:div>
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>

convention
Type:
Use:
optional
Defined:
locally within convention attributeGroup
<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"/>
XML Source (see within schema source)
<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>

dataType
Type:
Use:
optional
Defined:
locally within dataType attributeGroup
<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>
XML Source (see within schema source)
<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>

fractionDigits
Type:
xsd:nonNegativeInteger, predefined
Use:
optional
Defined:
locally within fractionDigits attributeGroup
<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>
XML Source (see within schema source)
<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>

id
Type:
Use:
optional
Defined:
locally within id attributeGroup
<h:div class="summary">An attribute providing a unique ID for an element.</h:div> <h:div class="description"/>
XML Source (see within schema source)
<xsd:attribute id="att.id" name="id" type="idType">
<xsd:annotation>
<xsd:documentation>
<h:div class="summary">
An attribute providing a unique ID for an element.
</h:div>
<h:div class="description"/>
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>

length
Type:
xsd:nonNegativeInteger, predefined
Use:
optional
Defined:
locally within length attributeGroup
<h:div class="summary">Length of a scalar.</h:div> <h:div class="description">Probably will be replaced with xsd:schema tool.</h:div>
XML Source (see within schema source)
<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>

maxExclusive
Type:
xsd:float, predefined
Use:
optional
Defined:
locally within maxExclusive attributeGroup
<h:div class="summary">maximum exclusive value.</h:div> <h:div class="description">by analogy with xsd:schema.</h:div>
XML Source (see within schema source)
<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>

maxInclusive
Type:
xsd:float, predefined
Use:
optional
Defined:
locally within maxInclusive attributeGroup
<h:div class="summary">minimum inclusive value.</h:div> <h:div class="description">by analogy with xsd:schem.</h:div>
XML Source (see within schema source)
<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>

maxLength
Type:
xsd:positiveInteger, predefined
Use:
optional
Defined:
locally within maxLength attributeGroup
<h:div class="summary">maximum length of a scalar.</h:div> <h:div class="description">by analogy with xsd:schem.</h:div>
XML Source (see within schema source)
<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>

minExclusive
Type:
xsd:float, predefined
Use:
optional
Defined:
locally within minExclusive attributeGroup
<h:div class="summary">minimum exclusive value.</h:div> <h:div class="description">by analogy with xsd:schema.</h:div>
XML Source (see within schema source)
<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>

minInclusive
Type:
xsd:float, predefined
Use:
optional
Defined:
locally within minInclusive attributeGroup
<h:div class="summary">minimum inclusive value.</h:div> <h:div class="description">by analogy with xsd:schema.</h:div>
XML Source (see within schema source)
<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>

minLength
Type:
xsd:nonNegativeInteger, predefined
Use:
optional
Defined:
locally within minLength attributeGroup
<h:div class="summary">minimum length of a scalar.</h:div> <h:div class="description">by analogy with xsd:schema.</h:div>
XML Source (see within schema source)
<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>

pattern
Type:
xsd:string, predefined
Use:
optional
Defined:
locally within pattern attributeGroup
<h:div class="summary">Pattern constraint.</h:div> <h:div class="description">Based on xsd:schema.</h:div>
XML Source (see within schema source)
<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>

rows
Type:
Use:
optional
Defined:
locally within rows attributeGroup
<h:div class="summary">Number of rows.</h:div>
XML Source (see within schema source)
<xsd:attribute id="att.rows" name="rows" type="sizeType">
<xsd:annotation>
<xsd:documentation>
<h:div class="summary">Number of rows.</h:div>
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>

term
Type:
xsd:string, predefined
Use:
required
Defined:
locally within term attributeGroup
<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>
XML Source (see within schema source)
<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>

title
Type:
xsd:string, predefined
Use:
optional
Defined:
locally within title attributeGroup
<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"/>
XML Source (see within schema source)
<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>

totalDigits
Type:
xsd:positiveInteger, predefined
Use:
optional
Defined:
locally within totalDigits attributeGroup
<h:div class="summary">total digits in a scalar.</h:div> <h:div class="description">based on xsd:schema.</h:div>
XML Source (see within schema source)
<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>

units
Type:
Use:
optional
Defined:
locally within units attributeGroup
<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>
XML Source (see within schema source)
<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>

unitType
Type:
xsd:string, predefined
Use:
optional
Defined:
locally within unitType attributeGroup
<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>
XML Source (see within schema source)
<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>

whiteSpace
Type:
xsd:string, predefined
Use:
optional
Defined:
locally within whiteSpace attributeGroup
<h:div class="summary">Whitespace.</h:div> <h:div class="description">Attached to entry. This may be obsolete.</h:div>
XML Source (see within schema source)
<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>
Content Element Detail (all declarations; 7/7)
alternative
Type:
anonymous complexType (extension of xsd:string), simple content
Defined:
by reference within (this) entry element
XML Source (see within schema source)
<xsd:element ref="alternative"/>

annotation
Type:
anonymous complexType, mixed content
Defined:
by reference within (this) entry element
XML Source (see within schema source)
<xsd:element ref="annotation"/>

definition
Type:
anonymous complexType, mixed content
Defined:
by reference within (this) entry element
XML Source (see within schema source)
<xsd:element ref="definition"/>

description
Type:
anonymous complexType, mixed content
Defined:
by reference within (this) entry element
XML Source (see within schema source)
<xsd:element ref="description"/>

enumeration
Type:
anonymous complexType, complex content
Defined:
by reference within (this) entry element
XML Source (see within schema source)
<xsd:element ref="enumeration"/>

metadataList
Type:
anonymous complexType, complex content
Defined:
by reference within (this) entry element
XML Source (see within schema source)
<xsd:element ref="metadataList"/>

relatedEntry
Type:
anonymous complexType, mixed content
Defined:
by reference within (this) entry element
XML Source (see within schema source)
<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:
  • To configure the generated documentation so much as you want. Thanks to our template technology, it was possible to support > 400 template parameters, which work the same as "options" of ordinary doc-generators. The parameters are organized in nested groups, which form a parameter tree. Most of them have their default values calculated dynamically from a few primary parameters. So, you'll never need to specify all of them. That will give you swift and effective control over the generated content!
  • To use certain features disabled in the free mode (such as the full documenting of substitution groups).
  • To select only the initial, imported, included, redefined XML schemas to be documented or only those directly specified by name.
  • To include only XML schema components specified by name.
  • To document local element components both globally and locally (similar to attributes).
  • To allow/suppress unification of local elements by type.
  • To enable/disable reproducing of namespace prefixes.
  • To use PlainDoc.tpl main template to generate all the XML schema documentation in a signle-file form as both HTML and incredible quality RTF output.
  • To format your annotations with XHTML tags and reproduce that formatting both in HTML and RTF output.
  • To insert images in your annotations using XHTML <img> tags (supported both in HTML and RTF output).
  • To remove this very advertisement text!
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/