Jumps: ObsDMCoreComponents :: VOResource :: VODataService
Meetings: InterOpMay2010
TAP VOResource Extension Schema
Contents
About creating a VOResource extension
The
VOResource spec has some specific recommendations about how to create an
extension schema; however, a
"how-to" create an extension presentation gives an introduction to the process.
In summary, the
RWG recommends the following steps for defining a new extension:
- Name and define the concepts to be captured
- Create a prototype VOResource instance
- Create the Schema Extension
- Describe the extension in an IVOA document (preferably as a section of a protocol document).
Step 1: Concepts to Include
This is just a prototype list of concepts to try to capture in the TAP extension.
- dataModel
- a URI identifying a data model supported by this TAP service
- the ObsCore model:
ivo://ivoa.net/std/ObsCore
- multiple entries should be allowed.