element <alternative> (global)
Namespace:
Type:
anonymous complexType (extension of xsd:string)
Content:
simple, 3 attributes
Defined:
globally in cmlreact.xsd; see XML source
Used:
XML Representation Summary
<alternative
   
 = 
xsd:string
 = 
xsd:string
 = 
(("synonym" | "quasi-synonym" | "acronym" | "abbreviation" | "homonym" | "identifier") | xsd:string)
    >
   
Content: 
{ xsd:string }
</alternative>
Included in content model of elements (2):
entry, unitType
Known Usage Locations
Annotation
<h:div class="summary">An alternative name for an entry.</h:div> <h:div class="description"> At present a child of _entry_ which represents an alternative string that refers to the concept. There is a partial controlled vocabulary in _alternativeType_ with values such as : <h:ul> <h:li>synonym</h:li> <h:li>acronym</h:li> <h:li>abbreviation</h:li> </h:ul> </h:div> <h:div class="example" href="alternative1.xml"/>
Anonymous Type Detail
Type Derivation Tree
xsd:string (extension)
  complexType
Derivation:
extension of xsd:string
XML Source (see within schema source)
<xsd:element id="el.alternative" name="alternative">
<xsd:annotation>
<xsd:documentation>
<h:div class="summary">An alternative name for an entry.</h:div>
<h:div class="description">
At present a child of _entry_ which represents an alternative string that refers to the concept. There is a partial controlled vocabulary in _alternativeType_ with values such as :
<h:ul>
<h:li>synonym</h:li>
<h:li>acronym</h:li>
<h:li>abbreviation</h:li>
</h:ul>
</h:div>
<h:div class="example" href="alternative1.xml"/>
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:simpleContent>
<xsd:extension base="xsd:string">
<xsd:attributeGroup ref="id"/>
<xsd:attributeGroup ref="convention"/>
<xsd:attributeGroup ref="alternativeType"/>
</xsd:extension>
</xsd:simpleContent>
</xsd:complexType>
</xsd:element>
Attribute Detail (all declarations; 3/3)
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>

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>

type
Type:
anonymous simpleType (union of (restriction of xsd:string | restriction of namespaceRefType))
Use:
optional
Defined:
locally within alternativeType attributeGroup
<h:div class="summary">The type of an alternative.</h:div> <h:div class="general">This adds semantics to an _alternative_ and might be used by an RDF or related engine.</h:div>
Anonymous simpleType
Derivation:
by union
Member Types
  1. anonymous simpleType:
    Derivation:
    restriction of xsd:string
  2. anonymous simpleType:
    Derivation:
    restriction of namespaceRefType
XML Source (see within schema source)
<xsd:attribute id="att.alternativeType" name="type">
<xsd:annotation>
<xsd:documentation>
<h:div class="summary">The type of an alternative.</h:div>
<h:div class="general">
This adds semantics to an _alternative_ and might be used by an RDF or related engine.
</h:div>
</xsd:documentation>
</xsd:annotation>
<xsd:simpleType>
<xsd:union>
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="synonym"/>
<xsd:enumeration value="quasi-synonym"/>
<xsd:enumeration value="acronym"/>
<xsd:enumeration value="abbreviation"/>
<xsd:enumeration value="homonym"/>
<xsd:enumeration value="identifier"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:simpleType>
<xsd:restriction base="namespaceRefType"/>
</xsd:simpleType>
</xsd:union>
</xsd:simpleType>
</xsd:attribute>

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/