Examples for Validator for IVOA Identifiers

Valid IVOID

IVOA identifers without query or fragment ("Registry reference") must resolve to Registry records. For instance, uri = ivo://org.gavo.dc/ivoidval/q/val is the (valid) ivoid of this service.

Registry references not resolving are bad

A Registry reference like uri = ivo://example.org/does/not/exist is invalid because it does not resolve to a record in the VO Registry.

No percent encoding in Registry references

uri = ivo://example.org/%64oes/not/exist is not an IVOID as percent-encoding is not allowed in either authority or the resource key.

Dataset identifier

Publisher dataset identifiers have a query part, but the Registry reference still has to resolve: uri = ivo://org.gavo.dc/~?feros/data/f89411.vot

Standard identifier

New-style standardIds use fragments to refer to standard keys within vstd:Standard records, as in uri = ivo://org.gavo.dc/std/glots#tables-1.0

Query part and frament identifier

With Identifiers 2 PubDIDs, one can reference things within suitable datasets; in the case of uri = ivo://org.gavo.dc/~?feros/data/f89411.vot#spectral , the PubDID references a VOTable (which you can inspect at http://dc.zah.uni-heidelberg.de/getproduct/feros/data/f89411.vot), and the fragment is an ID within that file.