Jumps: ObsDMCoreComponents :: VOResource :: VODataService
Meetings: InterOpMay2010

TAP VOResource Extension Schema

Contents

2011-11-27 Working draft

This is post-Pune; no important new features have been added, intrusive changes are limited to changed ids.

Points that may be discussed:

• Add a feature type for supported refsystems
  • In Pune, nobody uttered strong feelings on this; I'd rather leave it out in order to discourage the use of the first argument in geometries -- MarkusDemleitner - 28 Oct 2011
• Add an element saying whether sync and async are suppored
  • Unfortunately, there are services out there that don't support async. My take is that such services are not services conforming to ivo://ivoa.net/std/TAP and thus shouldn't even be putting out such capability records in the first place. However, sometimes practicality beats purity, so I'd be easily swayed. -- MarkusDemleitner - 28 Oct 2011

TAP examples

Somewhat related (in that it's about TAP service metadata and capabilities, too) is a proposal for what boils down to a TAP example microformat. See http://dc.g-vo.org/tapexample.

Older discussion

Use the Wiki's history function to read up on what issues we've already reached some consensus on.