IvoaValidatorsSummary < IVOA

IVOA Web>IvoaOps>IvoaValidatorsSummary (2023-10-03, TamaraCivera) (raw view)
---+ IVOA Validation Capabilities

This page provides a comprehensive summary of the validation capabilities associated with published IVOA standards. Validators include any software which takes an entity purported to be compliant with one or more IVOA standards and tests this compliance. The entity may a string, a file, a library, or an on-line service. Generally validators may produce false positives, entities which seem to pass the validator but which may still be non-compliant. Only limited tests are done and some semantic aspects of a protocol may not be amenable to automated testing. However false negatives, where failure is indicated even though the entity is compliant, should be rare and should be reported to the party responsible for the validator.

The page is given as a table with entries corresponding to each of the entries in the IVOA standards page. IVOA members who develop validators or who know of validation capabilities should update this table as appropriate. In cases where multiple validators exist for a protocol, separate entries are given for each.

%TABLE{tablewidth="800"}%

<table border="0" frame="box" rules="all" style="width: 795px; height: 2045px;"><col span="1" style="width: 5%;"></col> <col span="1" style="width: 10%;"></col> <col span="1" style="width: 10%;"></col> <col span="1" style="width: 8%;"></col> <col span="1" style="width: 40%;"></col> <col span="1" style="width: 10%;"></col> <col span="1" style="width: 15%;"></col> <tbody> <tr> <td>

---+++++ *Group*
</td> <td>
---+++++ *Standard*
</td> <td>
---+++++ *Versions*
</td> <td>
---+++++ *Status*
</td> <td>
---+++++ *Discussion*
</td> <td>
---+++++ Type
</td> </tr> <tr> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> </tr> <tr> <td> *App* </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> </tr> <tr> <td> </td> <td>SAMP</td> <td>1.3</td> <td>Yes</td> <td>

The JSAMP library/toolkit includes a fairly comprehensive set of validation tests (hubtester) for a SAMP Hub. In principle this can test both Standard and Web Profiles, though the web client is faked (it's not done from a browser). No SAMP client validator is included - such a thing wouldn't be able to do much, but could be a useful addition.
</td> <td>

[[http://www.star.bristol.ac.uk/~mbt/jsamp/commands.html#HubTester][Standalone]]
</td> </tr> <tr> <td> </td> <td>VOTable</td> <td>1.4,1.3,1.2,1.10,1.0</td> <td>Yes</td> <td>

*STILTS*

STILTS votlint provides comprehensive validation for VOTable 1.0, 1.1, 1.2, 1.3, 1.4, includes schema/DTD validation as well as much more stringent tests. Can be used standalone, but API has hooks for programmatic incorporation into other validators that need to validate VOTables (taplint does this).

You can also validate against the VOTable schema (or for v1.0 the DTD) provided in the standard.
</td> <td>

[[http://www.starlink.ac.uk/stilts/sun256/votlint.html][Standalone and library]],

[[http://www.w3schools.com/xml/xml_validator.asp][External XML validation]]
</td> </tr> <tr> <td> </td> <td> </td> <td>1.4,1.3,1.2,1.10</td> <td> </td> <td> *Astropy*

In any environment with Astropy installed, there is a *volint* command. The same output report can be generated programmatically by directly accessing the [[https://docs.astropy.org/en/stable/api/astropy.io.votable.validate.html#astropy.io.votable.validate][validate() method]], which also optionally allows schema validation.

Notes:
   * *volint* warns about version 1.0 UCDs even though they are technically legal in VOTables, so the conesearch-required UCDs ID_MAIN, POS_EQ_RA_MAIN and POS_EQ_DEC_MAIN will cause warnings.
   * UCDs are validated with *volint*, but units are not. See UCD and VOUnits sections below for notes on independent astropy validation of those.
</td> <td> [[https://docs.astropy.org/en/stable/install.html][Installing astropy for standalone or library use]]</td> </tr> <tr> <td> </td> <td>MOC</td> <td>1.0,1.1, 2.0</td> <td>Yes</td> <td>Moc.jar provides a validator method for MOC 1.0 REC. This validator is remotely usable via the !MocServer servlet provided by CDS.</td> <td> [[MocInfo#MOC_validators][Standalone Jar]] + [[http://alasky.unistra.fr/MocServer/lint][Web page]]</td> </tr> <tr> <td> </td> <td> </td> <td> </td> <td> </td> <td>ASCII MOC validator for MOC 1.1</td> <td> [[https://volute.g-vo.org/svn/trunk/projects/apps/MOC/][Standalone]]</td> </tr> <tr> <td> </td> <td>HiPS</td> <td>1.0</td> <td>Yes</td> <td>Checks a supplied !HiPS list and all services it references</td> <td> [[http://aladin.u-strasbg.fr/hips/][Standalone]]</td> </tr> <tr> <td> </td> <td> </td> <td> </td> <td> </td> <td>PADC (VOParis) provides a Hipslint-based web validator and runs Hipslint daily on registred services to provides validation reports.</td> <td>

<span style="text-decoration: underline;"> [[https://voparis-validation-reports.obspm.fr/validators/hips][Web]]</span>

<span style="color: #0000ff;"><span style="text-decoration: underline;"> [[https://voparis-validation-reports.obspm.fr/][Testing Framework]]</span></span>

<span style="color: #0000ff;"><span style="text-decoration: underline;"> [[https://voparis-validation-reports.obspm.fr/api/][Web API]]</span></span>

</td> </tr> <tr> <td> *DAL* </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> </tr> <tr> <td> </td> <td>DALI</td> <td>1.0,1.1</td> <td>None</td> <td>DALI provides a set of basic capabilities that all DAL services are to implement. DALI capabilities are sometimes tested inother validators but a specific separate test for DALI would be desirable.</td> <td> </td> </tr> <tr> <td> </td> <td>DataLink</td> <td>1.0, 1.1</td> <td>Partial</td> <td>STILTS datalinklint validates the content of a {links}-response table, including any service descriptors. It does not attempt to check link targets or {links} services themselves.</td> <td> [[http://www.starlink.ac.uk/stilts/sun256/datalinklint.html][Standalone]]</td> </tr> <tr> <td> </td> <td> </td> <td>N/A</td> <td>Partial</td> <td>shomydl ("show my datalinks") displays datalink documents hierarchically; it should help figuring out syntax problems and ways to improve annotation.</td> <td> [[https://dc.g-vo.org/shomydl/q/f/form][Web Service]]</td> </tr> <tr> <td> </td> <td>Cone Search</td> <td>1.03</td> <td>Multiple</td> <td>Cone search validators test that a service accepts standard inputs and that required fields are found in the VOTable outputs. Validators also test a limited number of error conditions</td> <td> </td> </tr> <tr> <td> </td> <td> </td> <td> </td> <td> </td> <td>The HEASARC uses an NCSA-developed package and tests registered services monthly providing a Web site to view results and run tests interactively.</td> <td> [[http://heasarc.gsfc.nasa.gov/vo/validation][Web page, testing framework]]</td> </tr> <tr> <td> </td> <td> </td> <td> </td> <td> </td> <td>PADC (VOParis) provides a web site which allows a user to validate a specific service and to view the results of their daily validation of registered services.</td> <td>

[[http://voparis-validator.obspm.fr/][Web]]

<span style="text-decoration: underline;"> [[https://voparis-validation-reports.obspm.fr/][Testing Framework]]</span>

<span style="color: #0000ff; text-decoration: underline;"> [[https://voparis-validation-reports.obspm.fr/api/][Web API]]</span>
</td> </tr> <tr> <td> </td> <td> </td> <td> </td> <td> </td> <td>

ESA enables a user to validate a particular services and to see the results of their daily testing of registered services
</td> <td>

[[https://registry.euro-vo.org/evor/#newstandalonevalidation][Web and testing framework]]
</td> </tr> <tr> <td> </td> <td> </td> <td> </td> <td> </td> <td>Astroquery (Astropy affiliated package) contains some kind of cone search validation client.</td> <td>

[[http://astroquery.readthedocs.io/en/latest/vo_conesearch/vo_conesearch.html#module-astroquery.vo_conesearch.validator.validate][Standalone]]
</td> </tr> <tr> <td> </td> <td>SIA</td> <td> </td> <td>Multiple</td> <td>SIA service validators check that a service accepts standard inputs and provides appropriate error responses in at least some situations. Most validators check only the initial VOTable response by the service.</td> <td> </td> </tr> <tr> <td> </td> <td> </td> <td>1.0 (2.0)</td> <td> </td> <td>

For 1.0 uses NCSA developed library for checking results. In addition to checking initial VOTable responses, checks that first data link is valid and of appropriate type. SIA 2.0 uses VO-Paris validator but stores results at the HEASARC.

Users can check individual services or see results of monthly validation.
</td> <td> [[http://heasarc.gsfc.nasa.gov/vo/validation][Web, Testomg framework]]</td> </tr> <tr> <td> </td> <td> </td> <td>1.0, 2.0</td> <td> </td> <td>PADC (VOParis) provides a web site which allows a user to validate a specific service and to view the results of their daily validation of registered services</td> <td>

[[http://voparis-validator.obspm.fr/][Web]]

<span style="text-decoration: underline;"> [[https://voparis-validation-reports.obspm.fr/][Testing Framework]]</span>

<span style="color: #0000ff; text-decoration: underline;"> [[https://voparis-validation-reports.obspm.fr/api/][Web API]]</span>
</td> </tr> <tr> <td> </td> <td> </td> <td>1.0</td> <td> </td> <td>ESA enables a user to validate a particular services and to see the results of their daily testing of registered services</td> <td> [[https://registry.euro-vo.org/evor/#newstandalonevalidation][Web, testing framework]]</td> </tr> <tr> <td> </td> <td>SLA</td> <td>1.0</td> <td>Yes</td> <td>PADC (VOParis) provides an SLA validator</td> <td> [[http://voparis-validator.obspm.fr/][Web]]</td> </tr> <tr> <td> </td> <td>SSA</td> <td>1.1,1.04,1.03</td> <td>Multiple</td> <td> </td> <td> </td> </tr> <tr> <td> </td> <td> </td> <td> </td> <td> </td> <td>PADC (VOParis) provides validaton of SSA services in the same fashion as other DAL services</td> <td>

<span style="color: blue; text-decoration-line: underline; background-color: transparent;"> [[http://voparis-validator.obspm.fr/][Web]]</span>

<span style="text-decoration: underline;"> [[https://voparis-validation-reports.obspm.fr/][Testing Framework]]</span>

<span style="color: #0000ff; text-decoration: underline;"> [[https://voparis-validation-reports.obspm.fr/api/][Web API]]</span>
</td> </tr> <tr> <td> </td> <td> </td> <td> </td> <td> </td> <td>ESA provides validation of SSA services in the same fashion as other DAL services</td> <td> [[https://registry.euro-vo.org/evor/#newstandalonevalidation][Web, testing framework]]</td> </tr> <tr> <td> </td> <td>STC-S</td> <td>1.0</td> <td>None</td> <td> </td> <td> </td> </tr> <tr> <td> </td> <td>TAP</td> <td>1.0,1.1</td> <td>Yes</td> <td>TAPLint provides an extensive set of tests of a TAP implementation including !DALI, synchoronous and asynchronous queries and tests of a variety of error conditions. The various methods in which metadata for the TAP service is provided are compared for consistency. Errors, warnings and informative messages are provided. Users may configure the tests to be run. Tests of included !ObsCore capabilities may be run. Versions: 1.0, 1.1.</td> <td> [[http://www.starlink.ac.uk/stilts/sun256/taplint.html][Standalone]]</td> </tr> <tr> <td> </td> <td> </td> <td> </td> <td> </td> <td>The HEASARC's VO valdiation tool runs TAPLint on registered services are saves the results with a monthly cadence.</td> <td>

[[http://heasarc.gsfc.nasa.gov/vo/validation][Testing framework]]

</td> </tr> <tr> <td> </td> <td> </td> <td> </td> <td> </td> <td>PADC (VOParis) provides a taplint-based web validator and runs taplint daily on registred services to provides validation reports.</td> <td>

<span style="text-decoration: underline;"> [[https://voparis-validation-reports.obspm.fr/validators/tap][Web]]</span>

<span style="color: #0000ff;"><span style="text-decoration: underline;"> [[https://voparis-validation-reports.obspm.fr/][Testing Framework]]</span></span>

<span style="color: #0000ff;"><span style="text-decoration: underline;"> [[https://voparis-validation-reports.obspm.fr/api/][Web API]]</span></span>
</td> </tr> <tr> <td> </td> <td>TAPRegExt</td> <td>1.0, 1.1</td> <td>Yes</td> <td>STILTS taplint (CAP stage) checks !TAPRegExt 1.0.</td> <td> [[http://www.starlink.ac.uk/stilts/sun256/taplint.html][Standalone]]</td> </tr> <tr> <td> </td> <td>ADQL</td> <td>1.0, 2.0, 2.1</td> <td> </td> <td>

Gregory Mantelet's !ADQL parser library identifies valid !ADQL 2.0 and 2.1 queries.

STILTS taplint issues a few !ADQL 2.0 queries to TAP services and notes errors, but does not attempt comprehensive feature testing.

(!ADQL 1.0 is moribund)
</td> <td>

[[http://www.starlink.ac.uk/stilts/sun256/taplint.html][CDS Library]] (?)
</td> </tr> <tr> <td> </td> <td>SkyNode</td> <td>1.01</td> <td>N/A</td> <td>Obsolete document</td> <td> </td> </tr> <tr> <td> </td> <td>SimDAL</td> <td>1.0</td> <td>N/A</td> <td> </td> <td> </td> </tr> <tr> <td> </td> <td>VOEvent Transport</td> <td>1.0, 2.0</td> <td>Missing</td> <td> </td> <td> </td> </tr> <tr> <td> </td> <td>SODA</td> <td>1.0</td> <td>Yes</td> <td>CASDA's sodalint tests the DALI and SODA endpoints plus the service descriptor</td> <td> [[https://github.com/csiro-rds/sodalint/releases][Standalone]]</td> </tr> <tr> <td> </td> <td>EPN-TAP</td> <td>2.0</td> <td>Yes</td> <td>taplint stage EPN does quite comprehensive validation of EPN-TAP services.</td> <td> [[http://www.starlink.ac.uk/stilts/sun256/taplint.html][Standalone]]</td> </tr> <tr> <td> </td> <td> </td> <td> </td> <td> </td> <td>PADC (VOParis) provides a taplint-based web validator and runs taplint daily on all tables of EPN-TAP registred services to provides validation reports.</td> <td>

<span style="text-decoration: underline;"> [[https://voparis-validation-reports.obspm.fr/validators/epntap][Web]]</span>

<span style="color: #0000ff;"><span style="text-decoration: underline;"> [[https://voparis-validation-reports.obspm.fr/][Testing Framework]]</span></span>

<span style="color: #0000ff;"><span style="text-decoration: underline;"> [[https://voparis-validation-reports.obspm.fr/api/][Web API]]</span></span>
</td> </tr> <tr> <td> *DaM* </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> </tr> <tr> <td> </td> <td>Photometry</td> <td>1.0</td> <td>N/A</td> <td> </td> <td> </td> </tr> <tr> <td> </td> <td>SimDM</td> <td>1.0</td> <td> </td> <td> </td> <td> </td> </tr> <tr> <td> </td> <td>Astronomical Dataset Characterization</td> <td>1.13,1.12</td> <td>N/A</td> <td> </td> <td> </td> </tr> <tr> <td> </td> <td>Simple Spectral Lines</td> <td>1.0</td> <td>N/A</td> <td> </td> <td> </td> </tr> <tr> <td> </td> <td>Spectral</td> <td>1.0, 2.0</td> <td>N/A</td> <td> </td> <td> </td> </tr> <tr> <td> </td> <td>ObsCore</td> <td>1.0, 1.1</td> <td>Yes</td> <td>STILTS taplint (OBS stage) does comprehensive testing that mandatory !ObsCore elements are present, and mandatory/optional elements are as prescribed by the standard, in running TAP services. Versions: 1.0, 1.1.</td> <td>

[[http://www.starlink.ac.uk/stilts/sun256/taplint.html][Standalone]]
</td> </tr> <tr> <td> </td> <td>Characterization: Complements and new features.</td> <td>1.0</td> <td>Unknown</td> <td> </td> <td> </td> </tr> <tr> <td> </td> <td>VO-DML</td> <td>1.0</td> <td> </td> <td>

Standard tooling will validate models with the
<verbatim>gradle vodmlValidate</verbatim>

command
</td> <td><a href="https://github.com/ivoa/vo-dml" target="_blank">https://github.com/ivoa/vo-dml</a></td> </tr> <tr> <td> </td> <td>VO-DML</td> <td>1.0</td> <td>Yes</td> <td>CADC Tool</td> <td>Standalone</td> </tr> <tr> <td> </td> <td>Dataset Metadata</td> <td>1.0</td> <td>N/A</td> <td>

</td> <td> </td> </tr> <tr> <td> </td> <td>Cube (Image)</td> <td>1.0</td> <td>N/A</td> <td> </td> <td>Standalone - link TBD</td> </tr> <tr> <td> </td> <td>STC</td> <td>2.0</td> <td>Yes</td> <td>

vo-dml schema validation examples pass votable and xml validation
</td> <td>Standalone - link TBD</td> </tr> <tr> <td> </td> <td>ObsLocTAP</td> <td>1.0</td> <td>Yes</td> <td>STILTS taplint LOC stage.</td> <td> [[http://www.starlink.ac.uk/stilts/][Standalone]]</td> </tr> <tr> <td> </td> <td>MIVOT</td> <td>1.0</td> <td> </td> <td> </td> <td> </td> </tr> <tr> <td> *GWS* </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> </tr> <tr> <td> </td> <td>Parameter Descripton Language</td> <td>1.0</td> <td>Missing</td> <td> </td> <td> </td> </tr> <tr> <td> </td> <td>SSO</td> <td>1.01, 2.0</td> <td>N/A</td> <td>Standard references other non-VO standards</td> <td> </td> </tr> <tr> <td> </td> <td>VOSpace</td> <td>2.0,2.1</td> <td>Yes</td> <td>A set of integration tests on VOSpace conformance.</td> <td> [[https://github.com/opencadc/vos/tree/master/cadc-test-vos][Library]]</td> </tr> <tr> <td> </td> <td>Credential Delegation</td> <td>1.0</td> <td>Missing</td> <td> </td> <td> </td> </tr> <tr> <td> </td> <td>UWS</td> <td>1.0, 1.1</td> <td>Multiple</td> <td>

STILTS taplint (UWS stage) tests most but not all aspects of UWS 1.0 operation required from TAP services.
</td> <td> [[http://www.starlink.ac.uk/stilts/sun256/taplint.html][Standalone]]</td> </tr> <tr> <td> </td> <td> </td> <td> </td> <td> </td> <td>uws-validator: suite of tests created for testing UWS 1.1 features, but can do basic tests for UWS 1.0 as well (use =--tags=-uws1_1= to exclude 1.1 specific tests). May still report false negatives, since it is quite strict.</td> <td> [[https://github.com/kristinriebe/uws-validator][Standalone]]</td> </tr> <tr> <td> </td> <td><span style="color: orangered;">%BLACK%VOSI%ENDCOLOR%</span></td> <td>1.0,1.1</td> <td>Yes</td> <td>A set of integration tests on VOSI conformance.</td> <td> [[https://github.com/opencadc/reg/tree/master/cadc-test-vosi][Library]]</td> </tr> <tr> <td> </td> <td>GMS</td> <td>1.0</td> <td> </td> <td> </td> <td> </td> </tr> <tr> <td> </td> <td>%RED%%BLACK%Web Service Basic Profile%ENDCOLOR%%ENDCOLOR%</td> <td>1.0</td> <td>N/A</td> <td>Obsolete document</td> <td> </td> </tr> <tr> <td> *ReR* </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> </tr> <tr> <td> </td> <td>IVOA Identifiers</td> <td>2.0</td> <td>Yes</td> <td>This service implements the Identifiers 2.0 suggestion for how to resolve an IVOA publisher dataset identifier; that is, it tries to resolve the registry part to Datalink, SSAP, or Obscore capabilities and tries those to find access URLs. If that fails, it repeats this procedure for services that the base resource declares as served-by.</td> <td>

[[http://dc.g-vo.org/ivoidval/q/didresolve/form][Web]],

[[http://svn.ari.uni-heidelberg.de/svn/gavo/hdinputs/ivoidval][Standalone]]

</td> </tr> <tr> <td> </td> <td>

OAI-PMH with IVOA extensions

(non-IVOA standard)
</td> <td>2.0</td> <td>Yes</td> <td>This Registry of Registries page validates entire registries. It implements an OAI 2.0 validator (using the OAI Explorer by Hussein Suleman) with additional IVOA-specific validation including the referential integrity of managed authorities, as well as validation of individual VOResources in the registry.</td> <td> [[http://rofr.ivoa.net/regvalidate/][Web]]</td> </tr> <tr> <td> </td> <td>Registry Interfaces</td> <td>1.0</td> <td>Yes</td> <td>The OAI-PMH part is validated by the rofr validator; capability instances can be validated using common XSD tools.</td> <td> [[http://rofr.ivoa.net/regvalidate/][Web]], [[https://ivoa.net/xml/VORegistry/VORegistry-1.1.xsd][XML Schema]]</td> </tr> <tr> <td> </td> <td>Resource Metadata</td> <td>1.12,1.01</td> <td>N/A</td> <td>No validatable content in this standard.</td> <td> </td> </tr> <tr> <td> </td> <td>StandardsRegExt</td> <td>1.0</td> <td>Yes</td> <td>Instance documents can be validated using common XML Schema tools</td> <td> [[http://ivoa.net/xml/StandardsRegExt/StandardsRegExt-1.0.xsd][Schema]]</td> </tr> <tr> <td> </td> <td>SimpleDALRegExt</td> <td>1.0, 1.1, 1.2</td> <td>Yes</td> <td>Instance documents can be validated using common XML Schema tools</td> <td> [[http://ivoa.net/xml/index.html][SIA, SLAP, SSA, and Cone search schema files]]</td> </tr> <tr> <td> </td> <td>VOResource</td> <td>1.03,1.1</td> <td>Yes</td> <td>Instance documents can be validated using common XML Schema tools</td> <td> [[http://ivoa.net/xml/VOResource/VOResource-v1.1.xsd][schema]]</td> </tr> <tr> <td> </td> <td>VODataService</td> <td>1.1, 1.2</td> <td>Yes</td> <td>Instance documents can be validated using common XML Schema tools</td> <td> [[http://ivoa.net/xml/VODataService/VODataService-v1.1.xsd][schema]]</td> </tr> <tr> <td> </td> <td>

!RegTAP:

Registry Relational Schema
</td> <td>1.0, 1.1, 1.2</td> <td>Yes</td> <td>GAVO has a suite of tests for a relational registry. This can be run on a specially prepared instance of !RegTAP software, not on an operational !RegTAP service. Supports 1.0, 1.1 and 1.2.</td> <td> [[http://docs.g-vo.org/regtap-val][Standalone]]</td> </tr> <tr> <td> *Sem* </td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> </tr> <tr> <td> </td> <td>VOUnits</td> <td>1.0</td> <td>Yes</td> <td>Unity is a C/Java library that parses/validates VOUnit expressions. It comes with a long list of test cases. STILTS harness also available.</td> <td> [[http://www.astro.gla.ac.uk/users/norman/ivoa/unity/][Library]], [[http://www.starlink.ac.uk/stilts/sun256/uk.ac.starlink.ttools.func.VO.html][standalone]]</td> </tr> <tr> <td> </td> <td> </td> <td> </td> <td> </td> <td>Astropy can parse and validate VOUnits, and that capability can be accessed programmatically via the [[https://docs.astropy.org/en/stable/api/astropy.units.format.VOUnit.html][VOUnit class]]. The parse() method emits warnings for unknown units.</td> <td> [[https://docs.astropy.org/en/stable/install.html][Library]]</td> </tr> <tr> <td> </td> <td>UCDs</td> <td>1.10</td> <td>N/A</td> <td>See UCD1+ vocabulary</td> <td> </td> </tr> <tr> <td> </td> <td>UCD1+ Vocubulary</td> <td>1.23,1.3,1.11</td> <td>Yes</td> <td>This web page provide some basic HTTP tools to validate, assign, translate, explain UCD1+. The validation is believed to be comprehensive following some changes in 06/2018.</td> <td> [[http://cds.unistra.fr/UCD/tools.htx][Web]]</td> </tr> <tr> <td> </td> <td> </td> <td>1.4, 1.5</td> <td> </td> <td>

Ucidy is a lightweight Java library aiming to parse and validate UCD. There is also the possibility to research UCD words in different ways among a validated and/or customised list.STILTS harness also available.</td> <td><span style="color: #0000ff;"><span style="text-decoration: underline;"> [[https://github.com/gmantele/ucidy][Library]], [[http://www.starlink.ac.uk/stilts/sun256/uk.ac.starlink.ttools.func.VO.html][standalone]]<br /></span></span></td> </tr> <tr> <td> </td> <td> </td> <td>1.4</td> <td> </td> <td>Astropy provides UCD validation programmatically via the [[https://docs.astropy.org/en/stable/api/astropy.io.votable.ucd.parse_ucd.html][parse_ucd()]] function which throws an appropriate !ValueError() for invalid UCDs.</td> <td> [[https://docs.astropy.org/en/stable/install.html][Library]]</td> </tr> <tr> <td> </td> <td>UCD Maintenance</td> <td>1.20,2.0</td> <td>N/A?</td> <td> </td> <td> </td> </tr> <tr> <td> </td> <td>Vocabularies</td> <td>1.19, 2.0</td> <td>Yes</td> <td>2.0 validator is now part of the standard.</td> <td> [[https://github.com/ivoa-std/vocinvo/tree/main/validator][Standalone]]</td> </tr> <tr> <td>SDP</td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> </tr> <tr> <td> </td> <td>IVOA Document Standards</td> <td>1.2</td> <td>N/A</td> <td> </td> <td> </td> </tr> <tr> <td>VOE</td> <td> </td> <td> </td> <td> </td> <td> </td> <td> </td> </tr> <tr> <td> </td> <td>VOEvent</td> <td>2.0,1.0</td> <td>Missing</td> <td> </td> <td> </td> </tr> <tr> <td> </td> <td>VOEventRegExt</td> <td>1.0</td> <td>Missing</td> <td> </td> <td> </td> </tr> </tbody> </table>
---++++ Notes:

   * *Group:* The IVOA Working Group under which the standard is being developed/maintained.
   * *Standard:* A short version of the name of the standard.
   * *Versions:* The versions of the standard for which a validator is available. Normally only recommendations and the version of the standard currently in development are included.
   * *Status:* Do validators exist? _Yes/Multiple_: Validators exist. _N/A_ (not applicable): Either the standard is not validatable or is obsolete/abandoned. _Missing_: A validator should be available for this standard but none is known.
   * *Discussion:* A discussion of what validators do (or might) test. When multiple validators an overall entry for the standard may be given followed with details for each validator on separate rows..
   * *Type:* What kind of validator exists. Types include
      * *Library:* Code library that can be incorporated in other applications (including validators). Download link provided.
      * *Standalone:* A standalone tool that runs on the tester's machine. A download link is provided.
      * *Web:* A tool that can be run interactively by a user at a web site. Web link provided.
      * *Testing framework:* A web site that provides links to results of tests of a class of services that is performed autonomously at some cadence. Web link provided.
      * *Web API*: An Application Programming Interface which provides test results in a programmatic way over the web. API specification link provided.
<!--
      * Set ALLOWTOPICRENAME = IVOA.TWikiAdminGroup
-->
<div id="_mcePaste" style="position: absolute; left: -10000px; top: 1297px; width: 1px; height: 1px; overflow: hidden;">http://www.star.bris.ac.uk/~mbt/stilts/sun256/sun256.html</div>
Topic revision: r60 - 2023-10-03 - TamaraCivera
IVOA
Log in or Register
IVOA.net
Wiki Home
WebChanges
WebTopicList
WebStatistics
Twiki Meta & Help
IVOA
Know
Main
Sandbox
TWiki
TWiki intro
TWiki tutorial
User registration
Notify me
Working Groups
Interest Groups
Time Domain
Committees
Stds&Procs
www.ivoa.net
Documents
Events
Members
XML Schema