TAPRegExt-1.0 Proposed Recommendation: Request for Comments

This document serves as the RFC center for the Proposed Recommendation entitled "TAPRegExt: a VOResource Schema Extension for Describing TAP Services, Version 1.0".

The latest version of TAPRegExt:

• http://www.ivoa.net/Documents/TAPRegExt/

Reference Interoperable Implementations

• TOPCAT (client)
• GAVO data center and the underlying software DaCHS software (server)
• CADC TAP service: the VOSI-capabilities resource includes extended metadata defined in TAPRegExt-1.0

Implementations Validators

Any schema validator will do for syntactic validation. STILTS' taplint task does a partial semantic validation.

The OpenCADC TAP library contains a TAPRegExtParser that performs full schema validation on VOSI-capabilities documents with TAPRegExt extended metadata.

RFC Review Period: 14 February 2012 - 13 March 2012

TCG Review Period:

---

---

Comments from the IVOA Community during RFC period: 09 February 2012 - 08 March 2012

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

• Sample comment by WikiName
  • Response (by WikiName)

Comment from Mark Taylor

The example document in Appendix B has similar upload specifiers in two formats, e.g.

<uploadMethod ivo-id="ivo://ivoa.org/tap/uploadmethods#http"/>
<uploadMethod ivo-id="ivo://ivoa.net/std/TAPRegExt#upload-http"/>

The second form corresponds to the upload method sanctioned by this standard, but the first form corresponds to an earlier version of this standard. Although it's legal to declare non-standard upload methods, and it might make some sense (for the near future) to have both versions in a production service to cope with clients written against the earlier version, it's confusing to have this in an example contained in the standards document. I suggest removing the out-of-date versions and just retaining the ..std/TAPRegExt#.. uploadMethod elements in this example. At the very least comment what these apparently redundant declarations are doing here. -- MarkTaylor - 09 Mar 2012

Oops -- that was an editorial oversight. The obsolete ivo-ids are gone from current SVN (r1648). -- MarkusDemleitner - 12 Mar 2012

---