Table information for 'rr.validation'


Table Description: Validation levels for resources and capabilities.

This table is available for ADQL queries and through the TAP endpoint.

Resource Description:

Tables containing the information in the IVOA Registry. To query these tables, use our TAP service.

For more information and example queries, see the RegTAP specification.

For a list of all services and tables belonging to this table's resource, see Information on resource 'GAVO RegTAP Service (Potsdam mirror)'

Citing this table

To cite the table as such, we suggest the following BibTeX entry:

  title={{GAVO} {RegTAP} Service (Potsdam mirror)},
  author={The {GAVO} data center team},
  howpublished={{VO} resource provided by the {AIP} {DaCHS}}


Sorted alphabetically. [Sort by DB column index]

NameTable Head DescriptionUnitUCD
cap_index Cap_index If non-NULL, the validation only refers to the capability referenced here. N/A N/A
ivoid Ivoid The parent resource. N/A N/A
val_level Val_level A numeric grade describing the quality of the resource description, when applicable, to be used to indicate the confidence an end-user can put in the resource as part of a VO application or research study. [Note v] N/A N/A
validated_by Validated_by The IVOA ID of the registry or organisation that assigned the validation level. N/A N/A

Columns that are parts of indices are marked like this.


The following services may use the data contained in this table:


VO nerds may sometimes need VOResource XML for this table.


Note v

The validation level is an integer encoding the following semantics:

The resource has a description that is stored in a registry. This level does not imply a compliant description.
In addition to meeting the level 0 definition, the resource description conforms syntactically to this standard and to the encoding scheme used.
In addition to meeting the level 1 definition, the resource description refers to an existing resource that has demonstrated to be functionally compliant. When the resource is a service, it is considered to exist and functionally compliant if use of the service accessURL responds without error when used as intended by the resource. If the service is a standard one, it must also demonstrate the response is syntactically compliant with the service standard in order to be considered functionally compliant. If the resource is not a service, then the ReferenceURL must be shown to return a document without error.
In addition to meeting the level 2 definition, the resource description has been inspected by a human and judged to comply semantically to this standard as well as meeting any additional minimum quality criteria (e.g., providing values for important but non-required metadata) set by the human inspector.
In addition to meeting the level 3 definition, the resource description meets additional quality criteria set by the human inspector and is therefore considered an excellent description of the resource. Consequently, the resource is expected to be operate well as part of a VO application or research study.