RegTAP 1.1 Proposed Recommendation: Request for Comments
Summary
Registries provide a mechanism with which VO applications can discover and select resources - first and foremost data and services - that are relevant for a particular scientific problem. The
RegTAP specification defines an interface for searching this resource metadata based on the IVOA's TAP protocol. It specifies a set of tables that comprise a useful subset of the information contained in the registry records, as well as the table's data content in terms of the XML VOResource data model. The general design of the system is geared towards allowing easy authoring of queries.
RegTAP 1.1, as a minor version increment over
RegTAP 1.0, is backward compatible. The main differences between 1.1 and 1.0 are as follows:
- new allowed res_detail values for testQueryStrings
- more generic type information in schema tables
- mapped terms in fields for dates and resource relationships to a vocabulary for DataCite compatibility
- case-insensitive query support from ADQL 2.1
- new columns for service mirrors, rights, and authentication and authorization of protected data and services
- new table for alternate identifiers, supporting DOIs, ORCIDs, bibcodes, and future identification schemes
Latest version of
RegTAP 1.1 can be found at:
Reference Interoperable Implementations
Two separate reference implementations of server-side architecture exist at GAVO (and other archives using GAVO's codebase) and
STScI
The TOPCAT client is aware of RegTAP 1.1 features and is interoperable with both reference implementations
Implementations Validators
The RegTAP validator (currently at
http://docs.g-vo.org/regtap-val; should this move into the VCS for the standard?) has been updated to cover the main new features.
For reviewers, here's a set of
RegTAP queries exercising the main user-visible new features (TAP access URLs above):
alt_identifiers – find VO resources and their titles that have DOIs:
select ivoid, res_title, alt_identifier
from rr.resource
natural join rr.alt_identifier
where alt_identifier like 'doi:%'
rights_uri – find VO resources that have a CC license declared:
select ivoid, res_title, rights_uri
from rr.resource
where rights_uri like 'http://creativecommons.org/%'
or find what license URIs are already in use:
select distinct rights_uri from rr.resource
mirror_url – find mirrors available for a known access url (in this case, indicating that the service is available through https, too):
select ivoid, mirrors.mirror_url
from rr.interface as intfs
join rr.interface as mirrors
using (ivoid,intf_index, cap_index)
where intfs.access_url='http://dc.zah.uni-heidelberg.de/antares/q/cone/form'
authenticated_only – find resources unavailable without authentication (note that we do not claim that's enough to actually operate them; the use case at this point is filtering them out with a view to a VO that has more of them):
select distinct ivoid from rr.interface where authenticated_only=1
vocabulary mapping – use just a single term to find out services of data collections:
select res_title
from rr.resource as res
natural join rr.relationship as rel
where relationship_type='isservedby'
and rel.related_id='ivo://nasa.heasarc/services/xamin'
Comments from the IVOA Community during RFC/TCG review period: RFC_start_date - RFC_end_date
The comments from the TCG members during the RFC/TCG review should be included in the next section.
In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (include your Wiki Name so that authors can contact you for further information). When the author(s) of the document have considered the comment, they will provide a response after the comment.
Additional discussion about any of the comments or responses can be conducted on the WG mailing list. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document
Comments from TCG member during the RFC/TCG Review Period: TCG_start_date - TCG_end_date
WG chairs or vice chairs must read the Document, provide comments if any (including on topics not directly linked to the Group matters) or indicate that they have no comment.
IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.
TCG Chair & Vice Chair
TCG Vote : Vote_start_date - Vote_end_date
If you have minor comments (typos) on the last version of the document please indicate it in the Comments column of the table and post them in the TCG comments section above with the date.
Group |
Yes |
No |
Abstain |
Comments |
TCG |
|
|
|
|
Apps |
|
|
|
|
DAL |
|
|
|
|
DM |
|
|
|
|
GWS |
|
|
|
|
Registry |
|
|
|
|
Semantics |
|
|
|
|
DCP |
|
|
|
|
KDIG |
|
|
|
|
SSIG |
|
|
|
|
Theory |
|
|
|
|
TD |
|
|
|
|
Ops |
|
|
|
|
<nop>StdProc |
|
|
|
|