Namespace: |
|
Content: |
|
Defined: |
globally in VODataService.xsd; see XML source |
Includes: |
|
Used: |
at 1 location |
| XML Representation Summary | |||||
| <... | |||||
| std | = |
xs:boolean | |||
| {any attribute with non-schema namespace} | |||||
| > | |||||
|
|||||
| </...> | |||||
| Type Derivation Tree vs:BaseParam (extension) |
| <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:sequence> <xs:annotation> <xs:documentation> A type of data contained in the column </xs:documentation> </xs:annotation> </xs:element> <xs:annotation> <xs:documentation> A keyword representing traits of the column. Recognized values include “indexed”, “primary”, and “nullable”. </xs:documentation> <xs:documentation> 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. </xs:documentation> </xs:annotation> </xs:element> </xs:sequence> <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> |
Type: |
|
Use: |
optional |
Defined: |
| <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> |
Defined: |
| <xs:anyAttribute namespace="##other"/> |
Type: |
vs:TableDataType, simple content |
Defined: |
| <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> |
Type: |
xs:token, simple content |
Defined: |
| <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> |
Type: |
xs:token, simple content |
Defined: |
| <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> |
Type: |
xs:token, simple content |
Defined: |
| <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> |
Type: |
xs:token, simple content |
Defined: |
| <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 “indexed”, “primary”, and “nullable”. </xs:documentation> <xs:documentation> 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. </xs:documentation> </xs:annotation> </xs:element> |
Type: |
xs:token, simple content |
Defined: |
Type: |
xs:token, simple content |
Defined: |
Type: |
xs:token, simple content |
Defined: |
Type: |
vs:Stats, complex content |
Defined: |
| <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 “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. </xs:documentation> </xs:annotation> </xs:element> |
Type: |
vs:Stats, complex content |
Defined: |
| <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 “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. </xs:documentation> </xs:annotation> </xs:element> |
Type: |
vs:Stats, complex content |
Defined: |
| <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 “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. </xs:documentation> </xs:annotation> </xs:element> |
Type: |
xs:token, simple content |
Defined: |
| <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> |
Type: |
xs:token, simple content |
Defined: |
| <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> |
Type: |
xs:token, simple content |
Defined: |
| <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> |
Type: |
xs:token, simple content |
Defined: |
Type: |
xs:token, simple content |
Defined: |
Type: |
xs:token, simple content |
Defined: |
Type: |
xs:token, simple content |
Defined: |
| <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> |
Type: |
xs:token, simple content |
Defined: |
| <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> |
Type: |
xs:token, simple content |
Defined: |
| <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:
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/ |