Namespace:	{global namespace}
Type:	vs:TableSchema
Content:	complex, attr. wildcard, 5 elements
Defined:	locally at 2 locations in VODataService-v1.1.xsd

XML Representation Summary

<schema

{any attribute with non-schema namespace}

Content:

name, title?, description?, utype?, table*

</schema>

Content model elements (5):

description (type xs:token),

name (type xs:token),

table (type vs:Table),

title (type xs:token),

utype (type xs:token)

Included in content model of elements (2):

Definition Locations

Within global complexTypes (2):
vs:TableSet [def], vs:TableSet [def]

Annotations (1) (by all definition locations)

within vs:TableSet complexType [def], within vs:TableSet complexType [def]

A named description of a set of logically related tables.

The name given by the "name" child element must be unique within this TableSet instance. If there is only one schema in this set and/or there's no locally appropriate name to provide, the name can be set to "default".

This aggregation does not need to map to an actual database, catalog, or schema, though the publisher may choose to aggregate along such designations, or particular service protocol may recommend it.

Attribute Detail (all declarations; 1)

{any attribute with non-schema namespace}

Defined:

within vs:TableSchema complexType

XML Source (see within schema source)

<xs:anyAttribute namespace="##other"/>

Content Element Detail (all declarations; 5)

Type:	xs:token, simple content
Defined:	locally within vs:TableSchema complexType

A free text description of the tableset that should explain in general how all of the tables are related.

XML Source (see within schema source)

<xs:element maxOccurs="1" minOccurs="0" name="description" type="xs:token">

<xs:annotation>

<xs:documentation>

A free text description of the tableset that should
explain in general how all of the tables are related.

</xs:documentation>

</xs:annotation>

</xs:element>

Type:	xs:token, simple content
Defined:	locally within vs:TableSchema complexType

A name for the set of tables.

This is used to uniquely identify the table set among several table sets. If a title is not present, this name can be used for display purposes.

If there is no appropriate logical name associated with this set, the name should be explicitly set to "default".

XML Source (see within schema source)

<xs:element maxOccurs="1" minOccurs="1" name="name" type="xs:token">

<xs:annotation>

<xs:documentation>

A name for the set of tables.

</xs:documentation>

<xs:documentation>

This is used to uniquely identify the table set among
several table sets. If a title is not present, this
name can be used for display purposes.

</xs:documentation>

<xs:documentation>

If there is no appropriate logical name associated with
this set, the name should be explicitly set to
"default".

</xs:documentation>

</xs:annotation>

</xs:element>

Type:	vs:Table, complex content
Defined:	locally within vs:TableSchema complexType

A description of one of the tables that makes up the set.

The table names for the table should be unique.

XML Source (see within schema source)

<xs:element maxOccurs="unbounded" minOccurs="0" name="table" type="vs:Table">

<xs:annotation>

<xs:documentation>

A description of one of the tables that makes up the set.

</xs:documentation>

<xs:documentation>

The table names for the table should be unique.

</xs:documentation>

</xs:annotation>

</xs:element>

Type:	xs:token, simple content
Defined:	locally within vs:TableSchema complexType

a descriptive, human-interpretable name for the table set.

This is used for display purposes. There is no requirement regarding uniqueness. It is useful when there are multiple schemas in the context (e.g. within a tableset; otherwise, the resource title could be used instead).

XML Source (see within schema source)

<xs:element minOccurs="0" name="title" type="xs:token">

<xs:annotation>

<xs:documentation>

a descriptive, human-interpretable name for the table set.

</xs:documentation>

<xs:documentation>

This is used for display purposes. There is no requirement
regarding uniqueness. It is useful when there are
multiple schemas in the context (e.g. within a
tableset; otherwise, the resource title could be
used instead).

</xs:documentation>

</xs:annotation>

</xs:element>

Type:	xs:token, simple content
Defined:	locally within vs:TableSchema complexType

an identifier for a concept in a data model that the data in this schema as a whole represent.

The format defined in the VOTable standard is strongly recommended.

XML Source (see within schema source)

<xs:element minOccurs="0" name="utype" type="xs:token">

<xs:annotation>

<xs:documentation>

an identifier for a concept in a data model that
the data in this schema as a whole represent.

</xs:documentation>

<xs:documentation>

The format defined in the VOTable standard is strongly
recommended.

</xs:documentation>

</xs:annotation>

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