Difference: TAPRegExt (1 vs. 2)

  META TOPICPARENT 
  name="TableAccess"  

Jumps:  ObsDMCoreComponents :: VOResource :: VODataService 

 Meetings:  InterOpMay2010  

  TAP VOResource Extension Schema 

  Contents 
 
  2011-11-27 Working draft
   TAP examples
   Older discussion
 


 About creating a VOResource extension
- META TOPICPARENT
+  name="TableAccess"
-<
<
+ Concepts to Include
->
>
+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).
 

 Steps 1:  Concepts to Include
 This is just a prototype list of concepts to try to capture in the TAP extension.
-<
<
+ obsCore  
 boolean value that indicates whether the database supports a compliant ObsCore table.
->
>
+ 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.
 <-- 
 
 
 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

META TOPICPARENT	name="TableAccess"

TAP VOResource Extension Schema

This is just a prototype list of concepts to try to capture in the TAP extension.

obsCore: boolean value that indicates whether the database supports a compliant ObsCore table.

<-- 
 
 
 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->