Namespace:	http://www.ivoa.net/xml/VOSITables/v1.0
Type:	vs:Table
Content:	complex, 1 attribute, attr. wildcard, 7 elements
Defined:	globally in VOSITables-v1.0.xsd; see XML source
Used:	never

XML Representation Summary

<table

xs:string

{any attribute with non-schema namespace}

Content:

name, title?, description?, utype?, nrows?, column*, foreignKey*

</table>

Content model elements (7):

A description of a single table supported by the service associated with a VOSI-enabled resource.

XML Source (see within schema source)

<xsd:element name="table" type="vs:Table">

<xsd:annotation>

<xsd:documentation>

A description of a single table supported by the
service associated with a VOSI-enabled resource.

</xsd:documentation>

</xsd:annotation>

</xsd:element>

Attribute Detail (all declarations; 2)

Type:	xsd:string
Use:	optional
Defined:	locally within vs:Table complexType

A name for the role this table plays. Recognized values include “output”, indicating this table is output from a query; “base_table”, indicating a table whose records represent the main subjects of its schema; and “view”, indicating that the table represents a useful combination or subset of other tables. Other values are allowed.

XML Source (see within schema source)

<xs:attribute name="type" type="xs:string">

<xs:annotation>

<xs:documentation>

A name for the role this table plays. Recognized
values include “output”, indicating this table is output
from a query; “base_table”, indicating a table
whose records represent the main subjects of its
schema; and “view”, indicating that the table represents
a useful combination or subset of other tables. Other
values are allowed.

</xs:documentation>

</xs:annotation>

</xs:attribute>

{any attribute with non-schema namespace}

Defined:

within vs:Table complexType

XML Source (see within schema source)

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

Content Element Detail (all declarations; 7)

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

A description of a table column.

XML Source (see within schema source)

<xs:element maxOccurs="unbounded" minOccurs="0" name="column" type="vs:TableParam">

<xs:annotation>

<xs:documentation>

A description of a table column.

</xs:documentation>

</xs:annotation>

</xs:element>

Type:	xsd:token, simple content
Defined:	locally within vs:Table complexType

A free-text description of the table's contents

XML Source (see within schema source)

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

<xs:annotation>

<xs:documentation>

A free-text description of the table's contents

</xs:documentation>

</xs:annotation>

</xs:element>

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

A description of a foreign keys, one or more columns from the current table that can be used to join with another table.

XML Source (see within schema source)

<xs:element maxOccurs="unbounded" minOccurs="0" name="foreignKey" type="vs:ForeignKey">

<xs:annotation>

<xs:documentation>

A description of a foreign keys, one or more columns
from the current table that can be used to join with
another table.

</xs:documentation>

</xs:annotation>

</xs:element>

Type:	xsd:token, simple content
Defined:	locally within vs:Table complexType

The fully qualified name of the table. This name should include all catalogue or schema prefixes needed to sufficiently uniquely distinguish it in a query.

In general, the format of the qualified name may depend on the context; however, when the table is intended to be queryable via ADQL, then the catalogue and schema qualifiers are delimited from the table name with dots (.).

XML Source (see within schema source)

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

<xs:annotation>

<xs:documentation>

The fully qualified name of the table. This name
should include all catalogue or schema prefixes
needed to sufficiently uniquely distinguish it in a
query.

</xs:documentation>

<xs:documentation>

In general, the format of the qualified name may
depend on the context; however, when the
table is intended to be queryable via ADQL, then the
catalogue and schema qualifiers are delimited from the
table name with dots (.).

</xs:documentation>

</xs:annotation>

</xs:element>

Type:	xsd:nonNegativeInteger, simple content
Defined:	locally within vs:Table complexType

The size of the table in rows.

This is not expected to be exact. For instance, the estimates on table sizes databases keep for query planning purposes are suitable for this field.

XML Source (see within schema source)

<xs:element maxOccurs="1" minOccurs="0" name="nrows" type="xs:nonNegativeInteger">

<xs:annotation>

<xs:documentation>

The size of the table in rows.

</xs:documentation>

<xs:documentation>

This is not expected to be exact. For instance, the
estimates on table sizes databases keep for query
planning purposes are suitable for this field.

</xs:documentation>

</xs:annotation>

</xs:element>

Type:	xsd:token, simple content
Defined:	locally within vs:Table complexType

A descriptive, human-interpretable name for the table.

This is used for display purposes. There is no requirement regarding uniqueness.

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.

</xs:documentation>

<xs:documentation>

This is used for display purposes. There is no requirement
regarding uniqueness.

</xs:documentation>

</xs:annotation>

</xs:element>

Type:	xsd:token, simple content
Defined:	locally within vs:Table complexType

An identifier for a concept in a data model that the data in this table represent.

The form of the utype string depends on the data model; common forms are sequences of dotted identifiers (e.g., in SSA) or URIs (e.g., in RegTAP).

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 table represent.

</xs:documentation>

<xs:documentation>

The form of the utype string depends on the data
model; common forms are sequences of dotted identifiers
(e.g., in SSA) or URIs (e.g., in RegTAP).

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