complexType "vs:TableParam"
Namespace:
http://www.ivoa.net/xml/VODataService/v1.1
Content:
complex, 1 attribute, attr. wildcard, 20 elements
Defined:
globally in VODataService.xsd; see XML source
Includes:
definitions of 1 attribute, 2 elements
Used:
never
XML Representation Summary
<...
    std
 = 
 xs:boolean
    {any attribute with non-schema namespace}
    >
   
Content: 
 name?, description?, unit?, ucd?, utype?, stats?, dataType?, flag*
</...>
Content Model Elements (8):
dataType (type vs:TableDataType),
description (type xs:token),
flag (type xs:token),
name (type xs:token),
stats (type vs:Stats),
ucd (type xs:token),
unit (type xs:token),
utype (type xs:token)
Annotation
A description of a table parameter having a fixed data type.
Type Definition Detail
Type Derivation Tree
vs:BaseParam (extension)
  vs:TableParam
XML Source (see within schema source)
<xs:complexType name="TableParam">
<xs:annotation>
<xs:documentation>
A description of a table parameter having a fixed data type.
</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="vs:BaseParam">
<xs:sequence>
<xs:element minOccurs="0" name="dataType" type="vs:TableDataType">
<xs:annotation>
<xs:documentation>
A type of data contained in the column
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element maxOccurs="unbounded" minOccurs="0" name="flag" type="xs:token">
<xs:annotation>
<xs:documentation>
A keyword representing traits of the column.
Recognized values include &#8220;indexed&#8221;, &#8220;primary&#8221;, and
&#8220;nullable&#8221;.
</xs:documentation>
<xs:documentation>
While other values are allowed, the following semantics
is defined by this specification: indexed &#8211; The column
has an index on it for faster search against its values;
primary &#8211; The values column in the column represent in
total or in part a primary key for its table; nullable &#8211;
the column may contain null or empty values.
</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
<xs:attribute name="std" type="xs:boolean">
<xs:annotation>
<xs:documentation>
If true, the meaning and use of this parameter is
reserved and defined by a standard model. If false,
it represents a parameter specific to the data described
If not provided, then the value is unknown.
</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:extension>
</xs:complexContent>
</xs:complexType>
Attribute Detail (all declarations; 2)
std
Type:
xs:boolean
Use:
optional
Defined:
locally within (this) vs:TableParam complexType
If true, the meaning and use of this parameter is reserved and defined by a standard model. If false, it represents a parameter specific to the data described If not provided, then the value is unknown.
XML Source (see within schema source)
<xs:attribute name="std" type="xs:boolean">
<xs:annotation>
<xs:documentation>
If true, the meaning and use of this parameter is
reserved and defined by a standard model. If false,
it represents a parameter specific to the data described
If not provided, then the value is unknown.
</xs:documentation>
</xs:annotation>
</xs:attribute>
{any attribute with non-schema namespace}
Defined:
within vs:BaseParam complexType
XML Source (see within schema source)
<xs:anyAttribute namespace="##other"/>
Content Element Detail (all declarations; 20)
dataType
Type:
vs:TableDataType, simple content
Defined:
locally within (this) vs:TableParam complexType
A type of data contained in the column
XML Source (see within schema source)
<xs:element minOccurs="0" name="dataType" type="vs:TableDataType">
<xs:annotation>
<xs:documentation>
A type of data contained in the column
</xs:documentation>
</xs:annotation>
</xs:element>
description
Type:
xs:token, simple content
Defined:
locally within vs:BaseParam complexType
A free-text description of a parameter's or column'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 a parameter's or column's
contents.
</xs:documentation>
</xs:annotation>
</xs:element>
description
Type:
xs:token, simple content
Defined:
locally within vs:BaseParam complexType
A free-text description of a parameter's or column'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 a parameter's or column's
contents.
</xs:documentation>
</xs:annotation>
</xs:element>
description
Type:
xs:token, simple content
Defined:
locally within vs:BaseParam complexType
A free-text description of a parameter's or column'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 a parameter's or column's
contents.
</xs:documentation>
</xs:annotation>
</xs:element>
flag
Type:
xs:token, simple content
Defined:
locally within (this) vs:TableParam complexType
Annotation 1 [src]:
A keyword representing traits of the column. Recognized values include “indexed”, “primary”, and “nullable”.
Annotation 2 [src]:
While other values are allowed, the following semantics is defined by this specification: indexed – The column has an index on it for faster search against its values; primary – The values column in the column represent in total or in part a primary key for its table; nullable – the column may contain null or empty values.
XML Source (see within schema source)
<xs:element maxOccurs="unbounded" minOccurs="0" name="flag" type="xs:token">
<xs:annotation>
<xs:documentation>
A keyword representing traits of the column.
Recognized values include &#8220;indexed&#8221;, &#8220;primary&#8221;, and
&#8220;nullable&#8221;.
</xs:documentation>
<xs:documentation>
While other values are allowed, the following semantics
is defined by this specification: indexed &#8211; The column
has an index on it for faster search against its values;
primary &#8211; The values column in the column represent in
total or in part a primary key for its table; nullable &#8211;
the column may contain null or empty values.
</xs:documentation>
</xs:annotation>
</xs:element>
name
Type:
xs:token, simple content
Defined:
locally within vs:BaseParam complexType
The name of the parameter or column.
XML Source (see within schema source)
<xs:element minOccurs="0" name="name" type="xs:token">
<xs:annotation>
<xs:documentation>
The name of the parameter or column.
</xs:documentation>
</xs:annotation>
</xs:element>
name
Type:
xs:token, simple content
Defined:
locally within vs:BaseParam complexType
The name of the parameter or column.
XML Source (see within schema source)
<xs:element minOccurs="0" name="name" type="xs:token">
<xs:annotation>
<xs:documentation>
The name of the parameter or column.
</xs:documentation>
</xs:annotation>
</xs:element>
name
Type:
xs:token, simple content
Defined:
locally within vs:BaseParam complexType
The name of the parameter or column.
XML Source (see within schema source)
<xs:element minOccurs="0" name="name" type="xs:token">
<xs:annotation>
<xs:documentation>
The name of the parameter or column.
</xs:documentation>
</xs:annotation>
</xs:element>
stats
Type:
vs:Stats, complex content
Defined:
locally within vs:BaseParam complexType
Annotation 1 [src]:
Statistics of the distribution underlying this parameter.
Annotation 2 [src]:
What “underlying distribution” means depends on the semantics of the derived type. For vs:TableParam-s, for instance, it would be the distribution of the values in the corresponding table columns. With vs:InputParam-s that are directly translated into relational constraints, it would similarly be the distribution of the corresponding column. For more complex input parameters, the distribution of an associated physical quantity might also be appropriate.
XML Source (see within schema source)
<xs:element minOccurs="0" name="stats" type="vs:Stats">
<xs:annotation>
<xs:documentation>
Statistics of the distribution underlying this parameter.
</xs:documentation>
<xs:documentation>
What &#8220;underlying distribution&#8221; means depends on the
semantics of the derived type. For vs:TableParam-s, for
instance, it would be the distribution of the values in
the corresponding table columns. With vs:InputParam-s
that are directly translated into relational constraints,
it would similarly be the distribution of the corresponding
column. For more complex input parameters, the
distribution of an associated physical quantity might also
be appropriate.
</xs:documentation>
</xs:annotation>
</xs:element>
stats
Type:
vs:Stats, complex content
Defined:
locally within vs:BaseParam complexType
Annotation 1 [src]:
Statistics of the distribution underlying this parameter.
Annotation 2 [src]:
What “underlying distribution” means depends on the semantics of the derived type. For vs:TableParam-s, for instance, it would be the distribution of the values in the corresponding table columns. With vs:InputParam-s that are directly translated into relational constraints, it would similarly be the distribution of the corresponding column. For more complex input parameters, the distribution of an associated physical quantity might also be appropriate.
XML Source (see within schema source)
<xs:element minOccurs="0" name="stats" type="vs:Stats">
<xs:annotation>
<xs:documentation>
Statistics of the distribution underlying this parameter.
</xs:documentation>
<xs:documentation>
What &#8220;underlying distribution&#8221; means depends on the
semantics of the derived type. For vs:TableParam-s, for
instance, it would be the distribution of the values in
the corresponding table columns. With vs:InputParam-s
that are directly translated into relational constraints,
it would similarly be the distribution of the corresponding
column. For more complex input parameters, the
distribution of an associated physical quantity might also
be appropriate.
</xs:documentation>
</xs:annotation>
</xs:element>
stats
Type:
vs:Stats, complex content
Defined:
locally within vs:BaseParam complexType
Annotation 1 [src]:
Statistics of the distribution underlying this parameter.
Annotation 2 [src]:
What “underlying distribution” means depends on the semantics of the derived type. For vs:TableParam-s, for instance, it would be the distribution of the values in the corresponding table columns. With vs:InputParam-s that are directly translated into relational constraints, it would similarly be the distribution of the corresponding column. For more complex input parameters, the distribution of an associated physical quantity might also be appropriate.
XML Source (see within schema source)
<xs:element minOccurs="0" name="stats" type="vs:Stats">
<xs:annotation>
<xs:documentation>
Statistics of the distribution underlying this parameter.
</xs:documentation>
<xs:documentation>
What &#8220;underlying distribution&#8221; means depends on the
semantics of the derived type. For vs:TableParam-s, for
instance, it would be the distribution of the values in
the corresponding table columns. With vs:InputParam-s
that are directly translated into relational constraints,
it would similarly be the distribution of the corresponding
column. For more complex input parameters, the
distribution of an associated physical quantity might also
be appropriate.
</xs:documentation>
</xs:annotation>
</xs:element>
ucd
Type:
xs:token, simple content
Defined:
locally within vs:BaseParam complexType
Annotation 1 [src]:
The name of a unified content descriptor that describes the scientific content of the parameter.
Annotation 2 [src]:
There are no requirements for compliance with any particular UCD standard.
XML Source (see within schema source)
<xs:element minOccurs="0" name="ucd" type="xs:token">
<xs:annotation>
<xs:documentation>
The name of a unified content descriptor that
describes the scientific content of the parameter.
</xs:documentation>
<xs:documentation>
There are no requirements for compliance with any
particular UCD standard.
</xs:documentation>
</xs:annotation>
</xs:element>
ucd
Type:
xs:token, simple content
Defined:
locally within vs:BaseParam complexType
Annotation 1 [src]:
The name of a unified content descriptor that describes the scientific content of the parameter.
Annotation 2 [src]:
There are no requirements for compliance with any particular UCD standard.
XML Source (see within schema source)
<xs:element minOccurs="0" name="ucd" type="xs:token">
<xs:annotation>
<xs:documentation>
The name of a unified content descriptor that
describes the scientific content of the parameter.
</xs:documentation>
<xs:documentation>
There are no requirements for compliance with any
particular UCD standard.
</xs:documentation>
</xs:annotation>
</xs:element>
ucd
Type:
xs:token, simple content
Defined:
locally within vs:BaseParam complexType
Annotation 1 [src]:
The name of a unified content descriptor that describes the scientific content of the parameter.
Annotation 2 [src]:
There are no requirements for compliance with any particular UCD standard.
XML Source (see within schema source)
<xs:element minOccurs="0" name="ucd" type="xs:token">
<xs:annotation>
<xs:documentation>
The name of a unified content descriptor that
describes the scientific content of the parameter.
</xs:documentation>
<xs:documentation>
There are no requirements for compliance with any
particular UCD standard.
</xs:documentation>
</xs:annotation>
</xs:element>
unit
Type:
xs:token, simple content
Defined:
locally within vs:BaseParam complexType
The unit associated with the values in the parameter or column.
XML Source (see within schema source)
<xs:element minOccurs="0" name="unit" type="xs:token">
<xs:annotation>
<xs:documentation>
The unit associated with the values in the parameter
or column.
</xs:documentation>
</xs:annotation>
</xs:element>
unit
Type:
xs:token, simple content
Defined:
locally within vs:BaseParam complexType
The unit associated with the values in the parameter or column.
XML Source (see within schema source)
<xs:element minOccurs="0" name="unit" type="xs:token">
<xs:annotation>
<xs:documentation>
The unit associated with the values in the parameter
or column.
</xs:documentation>
</xs:annotation>
</xs:element>
unit
Type:
xs:token, simple content
Defined:
locally within vs:BaseParam complexType
The unit associated with the values in the parameter or column.
XML Source (see within schema source)
<xs:element minOccurs="0" name="unit" type="xs:token">
<xs:annotation>
<xs:documentation>
The unit associated with the values in the parameter
or column.
</xs:documentation>
</xs:annotation>
</xs:element>
utype
Type:
xs:token, simple content
Defined:
locally within vs:BaseParam complexType
Annotation 1 [src]:
An identifier for a concept in a data model that the data in this schema represent.
Annotation 2 [src]:
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 schema 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>
utype
Type:
xs:token, simple content
Defined:
locally within vs:BaseParam complexType
Annotation 1 [src]:
An identifier for a concept in a data model that the data in this schema represent.
Annotation 2 [src]:
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 schema 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>
utype
Type:
xs:token, simple content
Defined:
locally within vs:BaseParam complexType
Annotation 1 [src]:
An identifier for a concept in a data model that the data in this schema represent.
Annotation 2 [src]:
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 schema 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/