<small>Jumps: ObsDMCoreComponents :: [[VOResource]] :: VODataService <br> Meetings: InterOpMay2010 </small> ---+!! TAP VOResource Extension Schema ---+++!! Contents %TOC% ---++ About creating a VOResource extension The [[http://www.ivoa.net/Documents/REC/ReR/VOResource-20080222.html][VOResource spec]] has some specific recommendations about how to create an [[http://www.ivoa.net/Documents/REC/ReR/VOResource-20080222.html#extend][extension schema]]; however, a [[http://www.ivoa.net/internal/IVOA/InterOpMay2007VOEvent/IVOAHowto4VOEvent]["how-to" create an extension]] presentation gives an introduction to the process. In summary, the [[IvoaResReg][RWG]] recommends the following steps for defining a new extension: 1. Name and define the concepts to be captured 2. Create a prototype VOResource instance 3. Create the Schema Extension 4. Describe the extension in an IVOA document (preferably as a section of a protocol document). ---++ Steps 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. <br/> <!-- * Set ALLOWTOPICRENAME = %MAINWEB%.TWikiAdminGroup -->
This topic: IVOA
>
WebHome
>
IvoaDAL
>
TableAccess
>
TAPRegExt
Topic revision: r2 - 2010-05-19 - RayPlante
Copyright © 2008-2025 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki?
Send feedback