simpleType "delimiterType"

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

Simple Content Model

xsd:string

All Direct / Indirect Based Attributes (1):

delimiter/@delimiter

Known Usage Locations

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

Annotation

<h:div class="summary">A single non-whitespace character to separate components in arrays.</h:div> <h:div class="description"> <h:p>Some STMML elements (such as <h:a href="el.array">array</h:a>) have content representing concatenated values. The default separator is whitespace (which can be normalised) and this should be used whenever possible. However in some cases the values are empty, or contain whitespace or other problematic punctuation, and a delimiter is required.</h:p> <h:p>Note that the content string MUST start and end with the delimiter so there is no ambiguity as to what the components are. Only printable characters from the ASCII character set should be used, and character entities should be avoided.</h:p> <h:p>When delimiters are used to separate precise whitespace this should always consist of spaces and not the other allowed whitespace characters (newline, tabs, etc.). If the latter are important it is probably best to redesign the application.</h:p> <h:p>At present there is a controlled pattern of characters selected so as not to collide with common usage in XML document</h:p> </h:div> <h:div class="example" href="delimiterType1.xml"> <h:em>The values in the array are</h:em> "A", "B12", "" (empty string) and "D and E" <h:em>note the spaces</h:em> </h:div>

Type Definition Detail

Type Derivation Tree

xsd:string (restriction)

delimiterType

Derivation:

restriction of xsd:string

XML Source (see within schema source)

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

<xsd:annotation>

<xsd:documentation>

<h:div class="summary">

A single non-whitespace character to separate components in arrays.

</h:div>

<h:div class="description">

<h:p>

Some STMML elements (such as

<h:a href="el.array">array</h:a>

) have
content representing concatenated values. The default separator is
whitespace (which can be normalised) and this should be used whenever
possible. However in some cases the values are empty, or contain whitespace or other
problematic punctuation, and a delimiter is required.

</h:p>

<h:p>

Note that the content string MUST start and end with the delimiter so
there is no ambiguity as to what the components are. Only printable
characters from the ASCII character set should be used, and character
entities should be avoided.

</h:p>

<h:p>

When delimiters are used to separate precise whitespace this should always
consist of spaces and not the other allowed whitespace characters
(newline, tabs, etc.). If the latter are important it is probably best to redesign
the application.

</h:p>

<h:p>

At present there is a controlled pattern of characters selected so as not to collide with common usage in XML document

</h:p>

</h:div>

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

<h:em>The values in the array are</h:em>

"A", "B12", "" (empty string) and "D and E"

<h:em>note the spaces</h:em>

</h:div>

</xsd:documentation>

</xsd:annotation>

<xsd:restriction base="xsd:string">

<xsd:pattern value="[!$%^*@~;#,/|]"/>

</xsd:restriction>

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