complexType "DataType"
Namespace:
Content:
complex, 2 attributes, 7 elements
Defined:
globally in vo-dml-v1.0.xsd; see XML source
Includes:
definitions of 2 elements
Used:
XML Representation Summary
<...
    abstract
 = 
xs:boolean : "false"
    id
 = 
xs:string
    >
   
Content: 
vodml-id, name, description?, extends?, constraint*, attribute*, reference*
</...>
Content Model Elements (7):
All Direct / Indirect Based Elements (1):
Known Usage Locations
Type Definition Detail
Type Derivation Tree
ReferableElement (extension)
  Type (extension)
      ValueType (extension)
          DataType
XML Source (see within schema source)
<xsd:complexType name="DataType">
<xsd:complexContent>
<xsd:extension base="ValueType">
<xsd:sequence>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="attribute" type="Attribute">
<xsd:annotation>
<xsd:documentation>
TODO
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element maxOccurs="unbounded" minOccurs="0" name="reference" type="Reference">
<xsd:annotation>
<xsd:documentation>
TODO
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
Attribute Detail (all declarations; 2)
abstract
Type:
Use:
optional
Default:
"false"
Defined:
locally within Type complexType
XML Source (see within schema source)
<xsd:attribute default="false" name="abstract" type="xsd:boolean" use="optional"/>

id
Type:
Use:
optional
Defined:
locally within ReferableElement complexType
A referencable element may be given an @id attribute to reflect an identifier defined in some source document form which a VO-DML model may have been derived.
XML Source (see within schema source)
<xsd:attribute name="id" type="xsd:string" use="optional">
<xsd:annotation>
<xsd:documentation>
A referencable element may be given an @id attribute to reflect an identifier
defined in some source document form which a VO-DML model may have been derived.
</xsd:documentation>
</xsd:annotation>
</xsd:attribute>
Content Element Detail (all declarations; 7)
attribute
Type:
Attribute, complex content
Defined:
locally within (this) DataType complexType
TODO
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="attribute" type="Attribute">
<xsd:annotation>
<xsd:documentation>
TODO
</xsd:documentation>
</xsd:annotation>
</xsd:element>

constraint
Type:
Constraint, complex content
Defined:
locally within Type complexType
Constraints defining valid instances of the type. May be an AttributeConstraint or an expression in some language.
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="constraint" type="Constraint">
<xsd:annotation>
<xsd:documentation>
Constraints defining valid instances of the type.
May be an AttributeConstraint or an expression in some language.
</xsd:documentation>
</xsd:annotation>
</xsd:element>

description
Type:
xsd:string, simple content
Defined:
locally within ReferableElement complexType
Human readable description of the model element.
XML Source (see within schema source)
<xsd:element minOccurs="0" name="description" type="xsd:string">
<xsd:annotation>
<xsd:documentation>
Human readable description of the model element.
</xsd:documentation>
</xsd:annotation>
</xsd:element>

extends
Type:
ElementRef, complex content
Defined:
locally within Type complexType
Reference to a type (called the base-type) that is extended by the current type (called the subtype). This implements the typical is-a inheritance relationship, similar to the extends relations in XSD and Java, the generaliation in UML, or the subclassOf relation in RDF. Note, VO-DML does not support multiple inheritance. Instances of a subtype are automatic instances of a base type. Polymorphism is assumed: When a role (see below) defines a base type as its datatype, instances of any subtype can be uased as value of the role. Roles defined on a base type are inherited by the subtypes. Relations inherited from a basetype can be 'subsetted', which is similar to overriding their definition. See the definiton of this property on the Relation type.
XML Source (see within schema source)
<xsd:element minOccurs="0" name="extends" type="ElementRef">
<xsd:annotation>
<xsd:documentation>
Reference to a type (called the base-type) that is extended by the current type (called the subtype).
This implements the typical is-a inheritance relationship, similar to the extends relations in XSD and Java,
the
generaliation in UML, or the subclassOf relation in RDF. Note, VO-DML does not support multiple inheritance.
Instances of a subtype are automatic instances of a base type.
Polymorphism is assumed: When a role (see below) defines a base type
as its datatype, instances of any subtype
can be uased as value of the role.
Roles defined on a base type are inherited by the subtypes.
Relations inherited from a basetype can be 'subsetted', which is similar to overriding their definition.
See the definiton of this property on the Relation type.
</xsd:documentation>
</xsd:annotation>
</xsd:element>

name
Type:
VODMLName, simple content
Defined:
locally within ReferableElement complexType
The name of the model element. MUST NOT be an empty string.
XML Source (see within schema source)
<xsd:element minOccurs="1" name="name" type="VODMLName">
<xsd:annotation>
<xsd:documentation>
The name of the model element.
MUST NOT be an empty string.
</xsd:documentation>
</xsd:annotation>
</xsd:element>

reference
Type:
Reference, complex content
Defined:
locally within (this) DataType complexType
TODO
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" minOccurs="0" name="reference" type="Reference">
<xsd:annotation>
<xsd:documentation>
TODO
</xsd:documentation>
</xsd:annotation>
</xsd:element>

vodml-id
Type:
VODMLID, simple content
Defined:
locally within ReferableElement complexType
Identifier for its containing element. Extracted as a separate type so that we can easily adapt to a different identifier design.
XML Source (see within schema source)
<xsd:element minOccurs="1" name="vodml-id" type="VODMLID">
<xsd:annotation>
<xsd:documentation>
Identifier for its containing element.
Extracted as a separate type so that we can easily adapt to a different identifier design.
</xsd:documentation>
</xsd:annotation>
</xsd:element>

This XML schema documentation has been generated with DocFlex/XML RE 1.8.0 using DocFlex/XML XSDDoc 2.2.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-end 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 more than 300 template parameters (working the same as "options" of an ordinary doc-gen), which will give you an unprecedented control over the generated content!
  • To use certain features disabled in the free mode (such as the full documenting of substitution groups).
  • To enable/disable documenting of the initial, imported, included and redefined XML schemas selectively.
  • To document local element components both globally and locally (similar to attributes).
  • To enable/disable reproducing of namespace prefixes.
  • 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 use PlainDoc.tpl main template to generate all the XML schema documentation in the form of a single HTML file.
  • To use the same template to generate the incredible quality RTF documentation.
  • To document only selected XML schema components specified by name.
  • 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 SDK 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: 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 result of which you could enjoy later by yourself. Every single your purchase matters and makes a difference for us!
To buy a license, please follow this link: http://www.filigris.com/shop/