element <label> (global)

Namespace:	http://www.xml-cml.org/schema/cml2/react
Type:	anonymous complexType
Content:	complex, 4 attributes, elem. wildcard
Defined:	globally in cmlreact.xsd; see XML source
Includes:	definition of elem. wildcard
Used:	at 12 locations

XML Representation Summary

<label

dictRef	=	xsd:string
id	=	xsd:string
objectClass	=	xsd:string
value	=	xsd:string

Content:

{any}*

</label>

Included in content model of elements (12):

atom, atomType, bondType, mechanism, molecule, product, reactant, reaction, reactionScheme, reactionStep, reactionStepList, spectator

Known Usage Locations

Within anonymous complexTypes of elements (12):
atom [ref], atomType [ref], bondType [ref], mechanism [ref], molecule [ref], product [ref], reactant [ref], reaction [ref], reactionScheme [ref], reactionStep [ref], reactionStepList [ref], spectator [ref]

Annotation

<h:div class="summary">A text string qualifying an object.</h:div> <h:div class="description">A label can be used to identify or distinguish elements, add keywords or classifications and similar processes. It is usually interpretable by domain-aware humans (e.g. C3'-endo, but not a34561). It is usually either built in a semantically rich fashion (e.g. C2'-alpha-H) or belongs to a controlled vocabulary. It is possibly accessed by software in a domain-specific manner. It differs from <h:tt>description</h:tt> which is free text. The distinction between titles, names and labels is fuzzy, but we think this is worth making. Labels may be necesssary to identify objects within programs, while names are more likely to be reserved for database searches. Titles are likely to be freer text and not recommended for precise object retrieval.</h:div> <h:div class="note">Labels should not contain whitespace. Punctuation marks are often necessary, but should not be gratuitously used. Punctuation clashing with XML character entities should be avoided; if this is not possible it should be escaped.</h:div> <h:div class="example" href="label1.xml"> <h:em>From IUPAC Dictionary of Medicinal Chemistry</h:em> </h:div>

XML Source (see within schema source)

<xsd:element id="el.label" name="label">

<xsd:annotation>

<xsd:documentation>

<h:div class="summary">A text string qualifying an object.</h:div>

<h:div class="description">

A label can be used to identify or distinguish elements, add keywords or classifications and similar processes. It is usually interpretable by domain-aware humans (e.g. C3'-endo, but not a34561). It is usually either built in a semantically rich fashion (e.g. C2'-alpha-H) or belongs to a controlled vocabulary. It is possibly accessed by software in a domain-specific manner. It differs from

<h:tt>description</h:tt>

which is free text. The distinction between titles, names and labels is fuzzy, but we think this is worth making. Labels may be necesssary to identify objects within programs, while names are more likely to be reserved for database searches. Titles are likely to be freer text and not recommended for precise object retrieval.

</h:div>

<h:div class="note">

Labels should not contain whitespace. Punctuation marks are often necessary, but should not be gratuitously used. Punctuation clashing with XML character entities should be avoided; if this is not possible it should be escaped.

</h:div>

<h:div class="example" href="label1.xml">

<h:em>From IUPAC Dictionary of Medicinal Chemistry</h:em>

</h:div>

</xsd:documentation>

</xsd:annotation>

<xsd:complexType>

<xsd:sequence maxOccurs="unbounded" minOccurs="0">

<xsd:any processContents="lax"/>

</xsd:sequence>

<xsd:attributeGroup ref="id"/>

<xsd:attributeGroup ref="dictRef"/>

<xsd:attributeGroup ref="value"/>

<xsd:attributeGroup ref="objectClass"/>

</xsd:complexType>

</xsd:element>

Attribute Detail (all declarations; 4/4)

dictRef

Type:	namespaceRefType
Use:	optional
Defined:	locally within dictRef attributeGroup

<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 document containing _entry_ elements and validated against STMML Schema. <h:p>Where there is concern about the dictionary becoming separated from the document 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"/>

XML Source (see within schema source)

<xsd:attribute id="att.dictRef" name="dictRef" type="namespaceRefType">

<xsd:annotation>

<xsd:documentation>

<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 document containing _entry_ elements and validated against STMML Schema.

<h:p>

Where there is concern about the dictionary becoming separated from the document 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"/>

</xsd:documentation>

</xsd:annotation>

</xsd:attribute>

Type:	idType
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>

objectClass

Type:	xsd:string, predefined
Use:	optional
Defined:	locally within objectClass attributeGroup

<h:div class="summary">The class of an object.</h:div> <h:div class="description">The type of this information. This is not controlled, but examples might include: <h:ul> <h:li>label</h:li> <h:li>summary</h:li> <h:li>note</h:li> <h:li>usage</h:li> <h:li>qualifier</h:li> </h:ul> It might be used to control display or XSL filtering.</h:div> <h:div class="note">The attribute is named 'objectClass' to avoid clashes with other class attributes and inappropriate conversion to foo.getClass().</h:div>

XML Source (see within schema source)

<xsd:attribute id="att.objectClass" name="objectClass" type="xsd:string">

<xsd:annotation>

<xsd:documentation>

<h:div class="summary">The class of an object.</h:div>

<h:div class="description">

The type of this information. This is not controlled, but examples might include:

<h:ul>

<h:li>label</h:li>

<h:li>summary</h:li>

<h:li>note</h:li>

<h:li>usage</h:li>

<h:li>qualifier</h:li>

</h:ul>

It might be used to control display or XSL filtering.

</h:div>

<h:div class="note">

The attribute is named 'objectClass' to avoid clashes with other class attributes and inappropriate conversion to foo.getClass().

</h:div>

</xsd:documentation>

</xsd:annotation>

</xsd:attribute>

value

Type:	xsd:string, predefined
Use:	optional
Defined:	locally within value attributeGroup

<h:div class="summary">Value of a scalar object.</h:div> <h:div class="description">The value must be consistent with the dataType of the object.</h:div>

XML Source (see within schema source)

<xsd:attribute id="att.value" name="value" type="xsd:string">

<xsd:annotation>

<xsd:documentation>

<h:div class="summary">Value of a scalar object.</h:div>

<h:div class="description">

The value must be consistent with the dataType of the object.

</h:div>

</xsd:documentation>

</xsd:annotation>

</xsd:attribute>

Content Element Detail (all declarations; 1/1)

{any element with any namespace}

Defined:

within (this) label element

XML Source (see within schema source)

<xsd:any processContents="lax"/>

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/