TAPRegExt
xs
tr
A description of the capabilities metadata for TAP services.
The capabilities of a TAP server.
The capabilities attempt to define most issues that the
TAP standard leaves to the implementors (”may”, “should”).
Identifier of IVOA-approved data model supported by the
service.
Language supported by the service.
Output format supported by the service.
Upload method supported by the service.
The absence of upload methods indicates
that the service does not support uploads
at all.
Limits on the time between job creation and
destruction time.
Limits on executionDuration.
Limits on the size of data returned.
Limits on the size of uploaded data.
An IVOA defined data model, identified by an IVOID
intended for machine consumption and a short label
intended for human comsumption.
The IVOID of the data model.
A query language supported by the service.
Each language element can describe one or more versions
of a language. Either name alone or name-version can be
used as values for the LANG parameter of the service.
The name of the language without a version suffix.
A version of the language supported by the server.
A short, human-readable description of the
query language.
Optional features of the query language, grouped by
feature type.
This includes listing user defined functions, geometry support,
or similar concepts.
One version of the language supported by the service.
If the service supports more than one version of the
language, include multiple version elements.
It is recommended that you use a version numbering
scheme like MAJOR.MINOR in such a way that sorting
by ascending character codes will leave the most
recent version at the bottom of the list.
An optional IVOID of the language.
To more formally define a language supported by a service,
a resource record for the language can be created, either
centrally on the Registry of Registries or by other registry operators.
When such a record exists, the ivo-id attribute of language
should point to it.
An enumeration of non-standard or non-mandatory features of
a specific type implemented by the language.
A feature type is a language-dependent concept like
“user defined function”, “geometry support”, or possibly
“units supported”. A featureList gives all features of
a given type applicable for the service. Multiple featureLists
are possible.
All feature in a given list are of the same type. This type
is declared using the mandatory type attribute,
the value of which will typically be an IVOID.
To see values defined in TAPRegExt,
retrieve the ivo://ivoa.net/std/TAPRegExt
resource record and look for keys starting with “features-”.
A language feature of the type given by the
type attribute.
The type of the features given here.
This is in general an IVOID. TAPRegExt itself gives
IVOIDs for defining user defined functions and geometry
support.
A non-standard or non-mandatory feature implemented
by the language..
Formal notation for the language feature.
The syntax for the content of this element is defined by the
type attribute of its parent language list.
Human-readable freeform documentation for the language feature.
An output format supported by the service.
All TAP services must support VOTable output, with media types as
requested by the FORMAT parameter if applicable (cf.~section 2.7.1
of the TAP standard).
The primary identifier for an output format is the RFC 2046 media
type. If you want to register an output format, you must
use a media type (or make one up using the x- syntax), although
the concrete media syntax is not enforced by the schema.
For more detailed specification, an IVOID may be used.
The media type of this format.
The format of this string is specified by RFC 2046.
The service has to accept this string as a
value of the FORMAT parameter.
Other values of FORMAT (“shorthands”) that make the service return
documents with the media type.
An optional IVOID of the output format.
When the media type does not uniquely define the
format (or a generic media type like application/octet-stream or
text/plain is given), the IVOID can point to a key
or StandardsRegExt document defining the format more
precisely. To see values defined in TAPRegExt,
retrieve the ivo://ivoa.net/std/TAPRegExt
resource record and look for keys starting with “output-”.
An upload method as defined by IVOA.
Upload methods are always identified by an IVOID.
Descriptions can be obtained by dereferencing this
IVOID. To see values defined in TAPRegExt,
retrieve the ivo://ivoa.net/std/TAPRegExt
resource record and look for keys starting with ”upload-”.
You can register custom upload methods, but you must use the
standard IVOIDs for the upload methods defined in the TAP
specification.
The IVOID of the upload method.
Time-valued limits, all values given in seconds.
The value of this limit for newly-created jobs, given in seconds.
The value this limit cannot be raised above, given in seconds.
Limits on data sizes, given in rows or bytes.
The value of this limit for newly-created jobs.
The value this limit cannot be raised above.
A limit on some data size, either in rows or in bytes.
The unit of the limit specified.