| <?xml version="1.0" encoding="UTF-8"?> <xs:schema attributeFormDefault="unqualified" elementFormDefault="unqualified" targetNamespace="http://www.ivoa.net/xml/VODataService/v1.1" version="1.1pr2" xmlns:stc="http://www.ivoa.net/xml/STC/stc-v1.30.xsd" xmlns:vm="http://www.ivoa.net/xml/VOMetadata/v0.1" xmlns:vr="http://www.ivoa.net/xml/VOResource/v1.0" xmlns:vs="http://www.ivoa.net/xml/VODataService/v1.1" xmlns:xs="http://www.w3.org/2001/XMLSchema"> <xs:annotation> <xs:appinfo> <vm:schemaName>VODataService</vm:schemaName> <vm:schemaPrefix>xs</vm:schemaPrefix> <vm:targetPrefix>vs</vm:targetPrefix> </xs:appinfo> <xs:documentation> An extension to the core resource metadata (VOResource) for describing data collections and services. </xs:documentation> </xs:annotation> <xs:import namespace="http://www.ivoa.net/xml/VOResource/v1.0" schemaLocation="http://vo.ari.uni-heidelberg.de/docs/schemata/VOResource.xsd"/> <xs:import namespace="http://www.ivoa.net/xml/STC/stc-v1.30.xsd" schemaLocation="http://vo.ari.uni-heidelberg.de/docs/schemata/stc.xsd"/> <xs:annotation> <xs:documentation> A logical grouping of data which, in general, is composed of one or more accessible datasets. A collection can contain any combination of images, spectra, catalogues, or other data. </xs:documentation> <xs:documentation> (A dataset is a collection of digitally-encoded data that is normally accessible as a single unit, e.g., a file.) </xs:documentation> <xs:documentation> This type is deprecated. Resource record authors should use vs:CatalogResource instead. This type will be removed from the schema when no resource record using it remains in the registry. </xs:documentation> </xs:annotation> <xs:complexContent> <xs:sequence> <xs:annotation> <xs:appinfo> <vm:dcterm>Subject</vm:dcterm> </xs:appinfo> <xs:documentation> the observatory or facility used to collect the data contained or managed by this resource. </xs:documentation> </xs:annotation> </xs:element> <xs:annotation> <xs:appinfo> <vm:dcterm>Subject</vm:dcterm> <vm:dcterm>Subject.Instrument</vm:dcterm> </xs:appinfo> <xs:documentation> the Instrument used to collect the data contain or managed by a resource. </xs:documentation> </xs:annotation> </xs:element> <xs:annotation> <xs:appinfo> <vm:dcterm>Rights</vm:dcterm> </xs:appinfo> <xs:documentation> Information about rights held in and over the resource. </xs:documentation> <xs:documentation> This should be repeated for all Rights values that apply. </xs:documentation> </xs:annotation> </xs:element> <xs:annotation> <xs:documentation> The physical or digital manifestation of the information supported by a resource. </xs:documentation> <xs:documentation> This should use RFC 2046 media (“MIME”) types for network-retrievable, digital data. Non-RFC 2046 values could be used for media that cannot be retrieved over the network. </xs:documentation> </xs:annotation> </xs:element> <xs:annotation> <xs:documentation> Extent of the content of the resource over space, time, and frequency. </xs:documentation> </xs:annotation> </xs:element> <xs:annotation> <xs:documentation> A description of the tables that are part of this collection. </xs:documentation> <xs:documentation> Each schema name must be unique within this tableset. </xs:documentation> </xs:annotation> <xs:unique name="DataCollection-schemaName"> <xs:selector xpath="schema"/> <xs:field xpath="name"/> </xs:unique> </xs:element> <xs:annotation> <xs:documentation> The URL that can be used to download the data contained in this data collection. </xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:annotation> <xs:documentation> A coverage on a sphere. By default, this refers to the celestial sphere in the ICRS frame. Non-celestial frames are indicated by non-NULL values of the frame attribute. </xs:documentation> </xs:annotation> <xs:simpleContent> <xs:annotation> <xs:documentation> When present, the MOC is written in a non-celestial (e.g., planetary) frame. Note that for celestial coverages, ICRS must be used. </xs:documentation> <xs:documentation> VODataService 1.2 does not prescribe a vocabulary for what values are allowed here; an external standard. As long as no such vocabulary is agreed upon, the frame attribute should not be set. </xs:documentation> </xs:annotation> </xs:attribute> </xs:extension> </xs:simpleContent> </xs:complexType> <xs:annotation> <xs:documentation> A description of how a resource's contents or behavior maps to the sky, to time, and to frequency space, including coverage and resolution. </xs:documentation> </xs:annotation> <xs:sequence> <xs:annotation> <xs:documentation> An STC 1.0 description of the location of the resource's data on the sky, in time, and in frequency space, including resolution. This is deprecated in favour of the separate spatial, temporal, and spectral elements. </xs:documentation> </xs:annotation> </xs:element> <xs:annotation> <xs:documentation> An ASCII-serialized MOC defining the spatial coverage of the resource. </xs:documentation> <xs:documentation> The MOC is to be understood in the ICRS reference frame unless a frame attribute is given. Resources should give the coverage at least to order 6 (a resolution of about one degree). The order should be chosen so as to keep the resulting MOC smaller than a few dozens of kB. If desired, a more precise MOC can be provided on a dedicated endpoint declared in the footprint element. </xs:documentation> </xs:annotation> </xs:element> <xs:annotation> <xs:documentation> A pair of lower, upper limits of a time interval for which the resource offers data. </xs:documentation> <xs:documentation> This is written as for VOTable tabledata (i.e., whitespace-separated C-style floating point literals), as in “47847.2 51370.2”. The limits must be given as MJD. While they are not intended to be precise, they are to be understood in TDB for the solar system barycenter. The total coverage of the resource is the union of all such intervals. </xs:documentation> </xs:annotation> </xs:element> <xs:annotation> <xs:documentation> A pair of lower, upper limits of a spectral interval for which the resource offers data. </xs:documentation> <xs:documentation> This is written as for VOTable tabledata (i.e., whitespace-separated C-style floating point literals). The limits must be given in Joules of particle energies. While the limits are not intended to be precise, they are to be understood for the solar system barycenter. </xs:documentation> <xs:documentation> For instance, the Johnson V waveband (480 .. 730 nm) would be specified as “2.72e-19 4.14e-19” </xs:documentation> </xs:annotation> </xs:element> <xs:annotation> <xs:documentation> A reference to a footprint service for retrieving precise and up-to-date description of coverage. </xs:documentation> <xs:documentation> The ivo-id attribute here refers to the standard in which the footprint is given. The only value defined by VODataService at this point is ivo://ivoa.net/std/moc, which indicates that retrieving the footprint URL will return a MOC (any IVOA-approved serialisation is legal). Note that the ivo-id attribute was intended to have a different function in VODataService 1.1. The current meaning is what implementors actually adopted. </xs:documentation> </xs:annotation> </xs:element> <xs:annotation> <xs:appinfo> <vm:dcterm>Coverage.Spectral</vm:dcterm> </xs:appinfo> <xs:documentation> A name of a messenger that the resource is relevant for (e.g., was used in the measurements). Terms must be taken from the vocabulary at http://www.ivoa.net/rdf/messenger. </xs:documentation> <xs:documentation> It is a bit unfortunate that the element is still called waveband when it is now also coverage non-electromagnetic messengers. It was deemed that this slight notional sloppiness is preferable to introducing new and deprecating old elements. </xs:documentation> </xs:annotation> </xs:element> <xs:annotation> <xs:appinfo> <vm:dcterm>Coverage.RegionOfRegard</vm:dcterm> </xs:appinfo> <xs:documentation> A single numeric value representing the angle, given in decimal degrees, by which a positional query against this resource should be “blurred” in order to get an appropriate match. </xs:documentation> <xs:documentation> In the case of image repositories, it might refer to a typical field-of-view size, or the primary beam size for radio aperture synthesis data. In the case of object catalogues RoR should normally be the largest of the typical size of the objects, the astrometric errors in the positions, or the resolution of the data. </xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType> <xs:annotation> <xs:documentation> The service URL for a potentially registerd service. That is, if an IVOA identifier is also provided, then the service is described in a registry. </xs:documentation> </xs:annotation> <xs:simpleContent> <xs:annotation> <xs:documentation> The URI form of the IVOA identifier for the service describing the capability refered to by this element. </xs:documentation> </xs:annotation> </xs:attribute> </xs:extension> </xs:simpleContent> </xs:complexType> <xs:annotation> <xs:documentation> The set of tables hosted by a resource. </xs:documentation> </xs:annotation> <xs:sequence> <xs:annotation> <xs:documentation> A named description of a group of logically related tables. </xs:documentation> <xs:documentation> 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 is no locally appropriate name to provide, the name can be set to “default”. </xs:documentation> <xs:documentation> This aggregation does not need to map to an actual database, catalogue, or schema, though the publisher may choose to aggregate along such designations. Particular service protocols may require stricter patterns. </xs:documentation> </xs:annotation> <xs:unique name="DataCollection-tableName"> <xs:selector xpath="table"/> <xs:field xpath="name"/> </xs:unique> </xs:element> </xs:sequence> <xs:anyAttribute namespace="##other"/> </xs:complexType> <xs:annotation> <xs:documentation> A detailed description of a logically related group of tables. </xs:documentation> </xs:annotation> <xs:sequence> <xs:annotation> <xs:documentation> A name for the group of tables. </xs:documentation> <xs:documentation> This is used to uniquely identify the group of tables among several groups. If no title is given, this name can be used for display purposes. </xs:documentation> <xs:documentation> If there is no appropriate logical name associated with this group, the name should be explicitly set to “default”. </xs:documentation> </xs:annotation> </xs:element> <xs:annotation> <xs:documentation> A descriptive, human-interpretable name for the group of tables. </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> <xs:annotation> <xs:documentation> A free text description of the group of tables that should explain in general how all of the tables in the group are related. </xs:documentation> </xs:annotation> </xs:element> <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 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> <xs:annotation> <xs:documentation> A description of one table. </xs:documentation> </xs:annotation> </xs:element> </xs:sequence> <xs:anyAttribute namespace="##other"/> </xs:complexType> <xs:simpleContent> <xs:annotation> <xs:documentation> If true, the content of the element is an RFC 2046-compliant media time. </xs:documentation> </xs:annotation> </xs:attribute> </xs:extension> </xs:simpleContent> </xs:complexType> <xs:annotation> <xs:documentation> A resource publishing astronomical data. </xs:documentation> <xs:documentation> This resource type should only be used if the resource has no common underlying tabular schema (e.g., an inhomogeneous archive). Use CatalogResource otherwise. </xs:documentation> </xs:annotation> <xs:complexContent> <xs:sequence> <xs:annotation> <xs:appinfo> <vm:dcterm>Subject</vm:dcterm> </xs:appinfo> <xs:documentation> The observatory or facility used to collect the data contained or managed by this resource. </xs:documentation> </xs:annotation> </xs:element> <xs:annotation> <xs:appinfo> <vm:dcterm>Subject</vm:dcterm> <vm:dcterm>Subject.Instrument</vm:dcterm> </xs:appinfo> <xs:documentation> The instrument used to collect the data contain or managed by a resource. </xs:documentation> </xs:annotation> </xs:element> <xs:annotation> <xs:documentation> Extent of the content of the resource over space, time, and frequency. </xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:annotation> <xs:documentation> A service for accessing astronomical data. </xs:documentation> <xs:documentation> This resource type should only be used if the service has no common underlying tabular schema (e.g., a storage service) or if it is not explicitly accessible (e.g., an ftp server with images). Use CatalogService otherwise. </xs:documentation> </xs:annotation> <xs:complexContent> </xs:complexContent> </xs:complexType> <xs:annotation> <xs:documentation> A service invoked via an HTTP Query (either Get or Post) with a set of arguments consisting of keyword name-value pairs. </xs:documentation> <xs:documentation> Note that the URL for help with this service can be put into the service/referenceURL element. </xs:documentation> </xs:annotation> <xs:complexContent> <xs:sequence> <xs:annotation> <xs:documentation> The type of HTTP request, either GET or POST. </xs:documentation> <xs:documentation> The service may indicate support for both GET and POST by providing 2 queryType elements, one with GET and one with POST. Since the IVOA standard DALI requires standard services to support both GET and POST, this piece of metadata is not useful in the description of standard DAL services and does not need to be given for those. </xs:documentation> </xs:annotation> </xs:element> <xs:annotation> <xs:documentation> The MIME media type of a document returned in the HTTP response. </xs:documentation> </xs:annotation> </xs:element> <xs:annotation> <xs:documentation> A description of a input parameter that can be provided as a name=value argument to the service. </xs:documentation> </xs:annotation> </xs:element> <xs:annotation> <xs:documentation> An ampersand-delimited list of arguments that can be used to test this service interface; when provided as the input to this interface, it will produce a legal, non-null response. </xs:documentation> <xs:documentation> When the interface supports GET, then the full query URL is formed by the concatenation of the base URL (given by the accessURL) and the value given by this testQuery element. </xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:annotation> <xs:documentation> The type of HTTP request, either GET or POST. </xs:documentation> </xs:annotation> <xs:enumeration value="GET"/> <xs:enumeration value="POST"/> </xs:restriction> </xs:simpleType> <xs:annotation> <xs:documentation> A resource giving astronomical data in tabular form. </xs:documentation> <xs:documentation> While this includes classical astronomical catalogues, this resource is also appropriate for collections of observations or simulation results provided their metadata are available in a sufficiently structured form (e.g., Obscore, SSAP, etc). </xs:documentation> </xs:annotation> <xs:complexContent> <xs:sequence> <xs:annotation> <xs:documentation> A description of the tables that are accessible through this service. </xs:documentation> <xs:documentation> Each schema name and each table name must be unique within this tableset. </xs:documentation> </xs:annotation> <xs:unique name="CatalogService-schemaName"> <xs:selector xpath="schema"/> <xs:field xpath="name"/> </xs:unique> <xs:unique name="CatalogService-tableName"> <xs:selector xpath="schema/table"/> <xs:field xpath="name"/> </xs:unique> </xs:element> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:annotation> <xs:documentation> A service that interacts with astronomical data through one or more specified tables. </xs:documentation> <xs:documentation> This is the appropriate resource type for normal VO services, e.g., TAP, SSAP, SIAP, ConeSearch. </xs:documentation> </xs:annotation> <xs:complexContent> </xs:complexContent> </xs:complexType> <xs:sequence> <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> <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> <xs:annotation> <xs:documentation> A free-text description of the table's contents </xs:documentation> </xs:annotation> </xs:element> <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> <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> <xs:annotation> <xs:documentation> A description of a table column. </xs:documentation> </xs:annotation> </xs:element> <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> </xs:sequence> <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> <xs:anyAttribute namespace="##other"/> </xs:complexType> <xs:annotation> <xs:documentation> A description of a parameter that places no restriction on the parameter's data type. </xs:documentation> <xs:documentation> As the parameter's data type is usually important, schemas normally employ a sub-class of this type rather than this type directly. </xs:documentation> </xs:annotation> <xs:sequence> <xs:annotation> <xs:documentation> The name of the parameter or column. </xs:documentation> </xs:annotation> </xs:element> <xs:annotation> <xs:documentation> A free-text description of a parameter's or column's contents. </xs:documentation> </xs:annotation> </xs:element> <xs:annotation> <xs:documentation> The unit associated with the values in the parameter or column. </xs:documentation> </xs:annotation> </xs:element> <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. The format of the UCD can be used to distinguish between UCD1, UCD1+, and SIA-UCD. </xs:documentation> </xs:annotation> </xs:element> <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> </xs:sequence> <xs:anyAttribute namespace="##other"/> </xs:complexType> <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> See the specification document for definitions of recognized keywords. </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> <xs:annotation> <xs:documentation> A description of a service or function parameter having a fixed data type. </xs:documentation> <xs:documentation> DALI-compliant services should use vs:VOTableType here, others should use vs:SimpleDataType. </xs:documentation> </xs:annotation> <xs:complexContent> <xs:sequence> <xs:annotation> <xs:documentation> A type of data contained in the parameter. </xs:documentation> </xs:annotation> </xs:element> </xs:sequence> <xs:annotation> <xs:documentation> An indication of whether this parameter is required to be provided for the application or service to work properly. </xs:documentation> </xs:annotation> </xs:attribute> <xs:annotation> <xs:documentation> If true, the meaning and behavior of this parameter is reserved and defined by a standard interface. If false, it represents an implementation-specific parameter that effectively extends the behavior of the service or application. </xs:documentation> </xs:annotation> </xs:attribute> </xs:extension> </xs:complexContent> </xs:complexType> <xs:enumeration value="required"> <xs:annotation> <xs:documentation> The parameter is required for the application or service to work properly. </xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="optional"> <xs:annotation> <xs:documentation> The parameter is optional but supported by the application or service. </xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="ignored"> <xs:annotation> <xs:documentation> The parameter is not supported and thus is ignored by the application or service. </xs:documentation> </xs:annotation> </xs:enumeration> </xs:restriction> </xs:simpleType> <xs:annotation> <xs:documentation> A type (in the computer language sense) associated with a parameter with an arbitrary name </xs:documentation> <xs:documentation> This XML type is used as a parent for defining data types with a restricted set of names. </xs:documentation> </xs:annotation> <xs:simpleContent> <xs:annotation> <xs:documentation> The shape of the array that constitutes the value. </xs:documentation> <xs:documentation> Leave arraysize empty for scalar values. In version 1.1, this defaulted to 1, which was intended to indicate a scalar. This is now deprecated; an arraysize of 1 should be avoided now, the future interpretation, in accord with VOTable, will be “array of size 1”. </xs:documentation> </xs:annotation> </xs:attribute> <xs:annotation> <xs:documentation> A string that is used to delimit elements of an array value in InputParams. </xs:documentation> <xs:documentation> Unless specifically disallowed by the context, applications should allow optional spaces to appear in an actual data value before and after the delimiter (e.g., “1, 5” when delim=“,”). </xs:documentation> <xs:documentation> This should not be used for VOTable types; there, VOTable (typcially TABLEDATA) conventions for writing arrays are binding. </xs:documentation> </xs:annotation> </xs:attribute> <xs:annotation> <xs:documentation> The data value represented by this type can be interpreted as of a custom type identified by the value of this attribute. </xs:documentation> <xs:documentation> If an application does not recognize this extendedType, it should attempt to handle value assuming the type given by the element's value. string is a recommended default type. </xs:documentation> <xs:documentation> This element may make use of the extendedSchema attribute to refine the identification of the type. extendedTypes without an extendedSchema mean VOTable xtypes as defined by DALI. </xs:documentation> </xs:annotation> </xs:attribute> <xs:annotation> <xs:documentation> An identifier for the schema that the value given by the extended attribute is drawn from. </xs:documentation> <xs:documentation> This attribute is normally ignored if the extendedType attribute is not present. A missing extendedSchema indicates that extendedType is a VOTable xtype. </xs:documentation> </xs:annotation> </xs:attribute> <xs:anyAttribute namespace="##other"/> </xs:extension> </xs:simpleContent> </xs:complexType> <!-- - this definition is taken from the VOTable arrayDEF type --> <xs:annotation> <xs:documentation> An expression of a the shape of a multi-dimensional array of the form LxNxM... where each value between gives the integer length of the array along a dimension. An asterisk (*) as the last dimension of the shape indicates that the length of the last axis is variable or undetermined. </xs:documentation> </xs:annotation> <xs:pattern value="([0-9]+x)*[0-9]*[0-9*]"/> </xs:restriction> </xs:simpleType> <xs:annotation> <xs:documentation> A data type restricted to a small set of names which is imprecise as to the format of the individual values. </xs:documentation> <xs:documentation> This set is intended for describing simple input parameters to a service or function. </xs:documentation> </xs:annotation> <xs:simpleContent> <xs:enumeration value="integer"/> <xs:enumeration value="real"/> <xs:enumeration value="complex"/> <xs:enumeration value="boolean"/> <xs:enumeration value="char"/> <xs:enumeration value="string"/> <xs:annotation> <xs:documentation>See vs:DataType.</xs:documentation> </xs:annotation> </xs:attribute> <xs:annotation> <xs:documentation>See vs:DataType.</xs:documentation> </xs:annotation> </xs:attribute> <xs:annotation> <xs:documentation>See vs:DataType.</xs:documentation> </xs:annotation> </xs:attribute> <xs:annotation> <xs:documentation>See vs:DataType.</xs:documentation> </xs:annotation> </xs:attribute> <xs:anyAttribute namespace="##other"/> </xs:restriction> </xs:simpleContent> </xs:complexType> <xs:annotation> <xs:documentation> An abstract parent for a class of data types that can be used to specify the data type of a table column. </xs:documentation> </xs:annotation> <xs:simpleContent> </xs:simpleContent> </xs:complexType> <xs:annotation> <xs:documentation> A data type supported explicitly by the VOTable format </xs:documentation> </xs:annotation> <xs:simpleContent> <xs:enumeration value="boolean"/> <xs:enumeration value="bit"/> <xs:enumeration value="unsignedByte"/> <xs:enumeration value="short"/> <xs:enumeration value="int"/> <xs:enumeration value="long"/> <xs:enumeration value="char"/> <xs:enumeration value="unicodeChar"/> <xs:enumeration value="float"/> <xs:enumeration value="double"/> <xs:enumeration value="floatComplex"/> <xs:enumeration value="doubleComplex"/> <xs:annotation> <xs:documentation>See vs:DataType.</xs:documentation> </xs:annotation> </xs:attribute> <xs:annotation> <xs:documentation>See vs:DataType.</xs:documentation> </xs:annotation> </xs:attribute> <xs:annotation> <xs:documentation>See vs:DataType.</xs:documentation> </xs:annotation> </xs:attribute> <xs:annotation> <xs:documentation>See vs:DataType.</xs:documentation> </xs:annotation> </xs:attribute> <xs:anyAttribute namespace="##other"/> </xs:restriction> </xs:simpleContent> </xs:complexType> <xs:annotation> <xs:documentation> An abstract parent for the specific data types supported by the Table Access Protocol. </xs:documentation> </xs:annotation> <xs:simpleContent> <xs:annotation> <xs:documentation> The length of the fixed-length value </xs:documentation> <xs:documentation> This corresponds to the size Column attribute in the TAP_SCHEMA and can be used with data types that are defined with a length (CHAR, BINARY). </xs:documentation> </xs:annotation> </xs:attribute> </xs:extension> </xs:simpleContent> </xs:complexType> <xs:annotation> <xs:documentation> A data type supported explicitly by the Table Access Protocol (v1.0). This is deprecated in VODataService 1.2, and even TAP 1.0 services are encouraged to declare their columns using VOTableType. </xs:documentation> </xs:annotation> <xs:simpleContent> <xs:enumeration value="BOOLEAN"/> <xs:enumeration value="SMALLINT"/> <xs:enumeration value="INTEGER"/> <xs:enumeration value="BIGINT"/> <xs:enumeration value="REAL"/> <xs:enumeration value="DOUBLE"/> <xs:enumeration value="TIMESTAMP"/> <xs:enumeration value="CHAR"/> <xs:enumeration value="VARCHAR"/> <xs:enumeration value="BINARY"/> <xs:enumeration value="VARBINARY"/> <xs:enumeration value="POINT"/> <xs:enumeration value="REGION"/> <xs:enumeration value="CLOB"/> <xs:enumeration value="BLOB"/> <xs:anyAttribute namespace="##other"/> </xs:restriction> </xs:simpleContent> </xs:complexType> <xs:annotation> <xs:documentation> A description of standard space-time coordinate systems, positions, and regions. </xs:documentation> <xs:documentation> This resource type is deprecated, and no resource records of this type exist in the Registry. It will be removed in version 1.3 of VODataService. </xs:documentation> </xs:annotation> <xs:complexContent> <xs:sequence> <xs:element maxOccurs="unbounded" minOccurs="1" name="stcDefinitions" type="stc:stcDescriptionType"> <xs:annotation> <xs:documentation> An STC description of coordinate systems, positions, and/or regions </xs:documentation> <xs:documentation> Each system, position, and region description should have a an XML ID assigned to it. </xs:documentation> <xs:documentation> Because the STC schema sets elementFormDefault="qualified", it is recommended that this element specify the STC default namespace via an xmlns namespace. </xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:annotation> <xs:documentation> A description of the mapping a foreign key -- a set of columns from one table -- to columns in another table. </xs:documentation> <xs:documentation> When foreign keys are declared in this way, clients can expect that joins constrained with the foreign keys are preformed efficiently (e.g., using an index). </xs:documentation> </xs:annotation> <xs:sequence> <xs:annotation> <xs:documentation> The fully qualified name (including catalogue and schema, as applicable) of the table that can be joined with the table containing this foreign key. </xs:documentation> </xs:annotation> </xs:element> <xs:annotation> <xs:documentation> A pair of column names, one from this table and one from the target table that should be used to join the tables in a query. </xs:documentation> </xs:annotation> </xs:element> <xs:annotation> <xs:documentation> A free-text description of what this key points to and what the relationship means. </xs:documentation> </xs:annotation> </xs:element> <xs:annotation> <xs:documentation> An identifier for a concept in a data model that the association enabled by this key represents. </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> </xs:sequence> </xs:complexType> <xs:annotation> <xs:documentation> A pair of columns that are used to join two tables. </xs:documentation> <xs:documentation> To do an inner join of data from the two tables, a query should include a constraint that sets the value from the first column equal to the value in the second column. </xs:documentation> <xs:documentation> This type assumes that it is used in the context of implied source (i.e., current) and target tables, as in the ForeignKey type's fkColumn. </xs:documentation> </xs:annotation> <xs:sequence> <xs:annotation> <xs:documentation> The unqualified name of the column from the current table. </xs:documentation> </xs:annotation> </xs:element> <xs:annotation> <xs:documentation> The unqualified name of the column from the target table. </xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType> <xs:annotation> <xs:documentation> An interval of floating point numbers. </xs:documentation> <xs:documentation> This uses VOTable TABLEDATA serialisation, i.e., simply a pair of XSD floating point numbers separated by whitespace; note that software utilising non-XSD aware parsers has to perform whitespace normalisation itself here (in particular, for the internal whitespace). </xs:documentation> </xs:annotation> <xs:pattern value="[+-]?([0-9]+\.?[0-9]*|\.[0-9]+)([eE][+-]?[0-9]+)? [+-]?([0-9]+\.?[0-9]*|\.[0-9]+)([eE][+-]?[0-9]+)?"/> </xs:restriction> </xs:simpleType> </xs:schema> |
| 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/ |