complexType "SubsettedRole"

Namespace:	http://www.ivoa.net/xml/VODML/v1
Content:	complex, 4 elements
Defined:	globally in vo-dml.xsd; see XML source
Includes:	definitions of 3 elements
Used:	never

XML Representation Summary

<...>

Content:

description?, role, datatype?, semanticconcept?

</...>

Content Model Elements (4):

A special type of constraint that represents the common pattern where a subtype. would like to restrict certain aspects of a definition of a roles defined on a super type. The constraint explicitly defines the datatype of the identified role. This new datatype MUST be a subtype of the declared datatype of the role that is being constrained. Similarly a new, more restrictive semantic concept may be defined.

Type Definition Detail

Type Derivation Tree

Constraint (extension)

SubsettedRole

XML Source (see within schema source)

<xsd:complexType name="SubsettedRole">

<xsd:annotation>

<xsd:documentation>

A special type of constraint that represents the common pattern where a subtype.
would like to restrict certain aspects of a definition of a roles defined on a super type.
The constraint explicitly defines the datatype of the identified role. This new datatype MUST
be a subtype of the declared datatype of the role that is being constrained. Similarly
a new, more restrictive semantic concept may be defined.

</xsd:documentation>

</xsd:annotation>

<xsd:complexContent>

<xsd:extension base="Constraint">

<xsd:sequence>

<xsd:element name="role" type="ElementRef">

<xsd:annotation>

<xsd:documentation>

VODMLREF identifying the constrained Role.
This role MUST be available to the type containing this constraint.

</xsd:documentation>

</xsd:annotation>

</xsd:element>

<xsd:element minOccurs="0" name="datatype" type="ElementRef">

<xsd:annotation>

<xsd:documentation>

Pointer to datatype that the constrained Role must take.
This datatype MUST be a sub-type of the declared datatype of the constrained Role.

</xsd:documentation>

</xsd:annotation>

</xsd:element>

<xsd:element minOccurs="0" name="semanticconcept" type="SemanticConcept">

<xsd:annotation>

<xsd:documentation>

Maybe the super type has not defined a semantic concept for the Role, but
the subtype needs that. This attribute allows this assignment. But alse when
the Role on the super-type already has a semanticconcept with a topConcept
defined on it, the subtype may restrict the values to a narrower concept than
that assigned to it on the super-type.

</xsd:documentation>

</xsd:annotation>

</xsd:element>

</xsd:sequence>

</xsd:extension>

</xsd:complexContent>

</xsd:complexType>

Content Element Detail (all declarations; 4)

Type:	ElementRef, complex content
Defined:	locally within (this) SubsettedRole complexType

Pointer to datatype that the constrained Role must take. This datatype MUST be a sub-type of the declared datatype of the constrained Role.

XML Source (see within schema source)

<xsd:element minOccurs="0" name="datatype" type="ElementRef">

<xsd:annotation>

<xsd:documentation>

Pointer to datatype that the constrained Role must take.
This datatype MUST be a sub-type of the declared datatype of the constrained Role.

</xsd:documentation>

</xsd:annotation>

</xsd:element>

Type:	xsd:string, simple content
Defined:	locally within Constraint complexType

A natural language description of the constraint.

XML Source (see within schema source)

<xsd:element minOccurs="0" name="description" type="xsd:string">

<xsd:annotation>

<xsd:documentation>

A natural language description of the constraint.

</xsd:documentation>

</xsd:annotation>

</xsd:element>

Type:	ElementRef, complex content
Defined:	locally within (this) SubsettedRole complexType

VODMLREF identifying the constrained Role. This role MUST be available to the type containing this constraint.

XML Source (see within schema source)

<xsd:element name="role" type="ElementRef">

<xsd:annotation>

<xsd:documentation>

VODMLREF identifying the constrained Role.
This role MUST be available to the type containing this constraint.

</xsd:documentation>

</xsd:annotation>

</xsd:element>

Type:	SemanticConcept, complex content
Defined:	locally within (this) SubsettedRole complexType

Maybe the super type has not defined a semantic concept for the Role, but the subtype needs that. This attribute allows this assignment. But alse when the Role on the super-type already has a semanticconcept with a topConcept defined on it, the subtype may restrict the values to a narrower concept than that assigned to it on the super-type.

XML Source (see within schema source)

<xsd:element minOccurs="0" name="semanticconcept" type="SemanticConcept">

<xsd:annotation>

<xsd:documentation>

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