simpleType "metadataType"

Namespace:	http://www.xml-cml.org/schema/cml2/react
Defined:	globally in cmlreact.xsd; see XML source
Used:	at 1 location

Simple Content Model

All Direct / Indirect Based Attributes (1):

metadataType/@name

Known Usage Locations

As direct type of attributes within attributeGroups (1):
metadataType/@name

Annotation

<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>

Type Definition Detail

Type Derivation Tree

union of (restriction of xsd:string | restriction of namespaceRefType)

metadataType

Derivation:

by union

Member Types

anonymous simpleType:

Derivation:

restriction of xsd:string
anonymous simpleType:

Derivation:

restriction of namespaceRefType

XML Source (see within schema source)

<xsd:simpleType id="st.metadataType" name="metadataType">

<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 best practice is to select a value from a
controlled vocabulary (for example, the list of
Internet Media Types [MIME] defining computer media
formats).

</h:div>

</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="dc:relation">

<xsd:annotation>

<xsd:documentation>

<h:div class="definition">

A reference to a related
resource.

</h:div>

<h:div class="description">

Recommended best practice is to
reference the resource by means of a string or number
conforming to a formal identification system.

</h:div>

</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="dc:rights">

<xsd:annotation>

<xsd:documentation>

<h:div class="definition">

Information about rights held in
and over the resource.

</h:div>

<h:div class="description">

Typically, a Rights element will
contain a rights management statement for the resource,
or reference a service providing such information.
Rights information often encompasses Intellectual
Property Rights (IPR), Copyright, and various Property
Rights. If the Rights element is absent, no assumptions
can be made about the status of these and other rights
with respect to the resource.

</h:div>

</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="dc:subject">

<xsd:annotation>

<xsd:documentation>

<h:div class="definition">

The topic of the content of the
resource.

</h:div>

<h:div class="description">

Typically, a Subject will be
expressed as keywords, key phrases or classification
codes that describe a topic of the resource.
Recommended best practice is to select a value from a
controlled vocabulary or formal classification
scheme.

</h:div>

</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="dc:title">

<xsd:annotation>

<xsd:documentation>

<h:div class="definition">A name given to the resource.</h:div>

<h:div class="description">

Typically, a Title will be a name by
which the resource is formally known.

</h:div>

</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="dc:type">

<xsd:annotation>

<xsd:documentation>

<h:div class="definition">

The nature or genre of the
content of the resource.

</h:div>

<h:div class="description">

Type includes terms describing
general categories, functions, genres, or aggregation
levels for content. Recommended best practice is to
select a value from a controlled vocabulary (for
example, the working draft list of Dublin Core Types
[DCT1]). To describe the physical or digital
manifestation of the resource, use the FORMAT
element.

</h:div>

</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="dc:contributor">

<xsd:annotation>

<xsd:documentation>

<h:div class="definition">

An entity responsible for making
contributions to the content of the resource.

</h:div>

<h:div class="description">

Examples of a Contributor include a
person, an organisation, or a service. Typically, the
name of a Contributor should be used to indicate the
entity.

</h:div>

</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="dc:creator">

<xsd:annotation>

<xsd:documentation>

<h:div class="definition">

An entity primarily responsible
for making the content of the resource.

</h:div>

<h:div class="description">

Examples of a Creator include a
person, an organisation, or a service. Typically, the
name of a Creator should be used to indicate the
entity.

</h:div>

</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="dc:publisher">

<xsd:annotation>

<xsd:documentation>

<h:div class="definition">

An entity responsible for making
the resource available.

</h:div>

<h:div class="description">

Examples of a Publisher include a
person, an organisation, or a service. Typically, the
name of a Publisher should be used to indicate the
entity.

</h:div>

</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="dc:source">

<xsd:annotation>

<xsd:documentation>

<h:div class="definition">

A Reference to a resource from
which the present resource is derived.

</h:div>

<h:div class="description">

The present resource may be derived
from the Source resource in whole or in part.
Recommended best practice is to reference the resource
by means of a string or number conforming to a formal
identification system.

</h:div>

</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="dc:language">

<xsd:annotation>

<xsd:documentation>

<h:div class="definition">

A language of the intellectual
content of the resource.

</h:div>

<h:div class="description">

Recommended best practice for the
values of the Language element is defined by RFC 1766
[RFC1766] which includes a two-letter Language Code
(taken from the ISO 639 standard [ISO639]), followed
optionally, by a two-letter Country Code (taken from
the ISO 3166 standard [ISO3166]). For example, 'en' for
English, 'fr' for French, or 'en-uk' for English used
in the United Kingdom.

</h:div>

</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="dc:date">

<xsd:annotation>

<xsd:documentation>

<h:div class="definition">

A date associated with an event
in the life cycle of the resource.

</h:div>

<h:div class="description">

Typically, Date will be associated
with the creation or availability of the resource.
Recommended best practice for encoding the date value
is defined in a profile of ISO 8601 [W3CDTF] and
follows the YYYY-MM-DD format.

</h:div>

</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="cmlm:safety">

<xsd:annotation>

<xsd:documentation>

<h:div class="definition">

Entry contains information
relating to chemical safety.

</h:div>

<h:div class="description">

Typically the content will be a
reference to a handbook, MSDS, threshhold or other
human-readable strin.

</h:div>

</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="cmlm:insilico">

<xsd:annotation>

<xsd:documentation>

<h:div class="definition">

Part or whole of the information
was computer-generated.

</h:div>

<h:div class="description">

Typically the content will be the
name of a method or a progra.

</h:div>

</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="cmlm:structure">

<xsd:annotation>

<xsd:documentation>

<h:div class="definition">3D structure included.</h:div>

<h:div class="description">details include.</h:div>

</xsd:documentation>

</xsd:annotation>

</xsd:enumeration>

<xsd:enumeration value="cmlm:reaction"/>

<xsd:enumeration value="cmlm:identifier"/>

<xsd:enumeration value="other"/>

</xsd:restriction>

</xsd:simpleType>

<xsd:simpleType>

<xsd:restriction base="namespaceRefType"/>

</xsd:simpleType>

</xsd:union>

</xsd:simpleType>

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/