| ||||||||
Changed: | ||||||||
< < | Meetings: InterOpMay2010Reg :: InterOpNov2009Reg :: InterOpMay2009ResReg :: InterOpMay2008ResReg :: InterOpSep2007ResReg :: InterOpMay2007ResReg | |||||||
> > | Meetings: InterOpOct2011Registry :: InterOpMay2011Registry :: InterOpMay2010Reg :: InterOpNov2009Reg :: InterOpMay2009ResReg :: InterOpMay2008ResReg :: InterOpSep2007ResReg :: InterOpMay2007ResReg | |||||||
VOResource Extensions for Describing SSA, SIA, SLA, and ConeSearch Services
An application that queries or consumes descriptions of VO resources must be able to recognize a resource's support for standard IVOA protocols. This specification describes how to describe a services that supports four fundemental data access protocols--Simple Cone Search (SCS), Simple Image Access (SIA), Simple Spectral Access (SSA), Simple Line Access (SLA)--using the VOResource XML encoding standard. A key part of this specification is the set of VOResource XML extension schemas that define new metadata that are specific to those protocols. This document describes in particular rules for describing such services within the context of IVOA Registries and data discovery as well as the VO Stadard Interface (VOSI) and service self-description. In particular, this document spells out the essential mark-up needed to identify support for a standard protocol and the base URL required to access the interface that supports that protocol. ContentsDocuments | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Added: | ||||||||
> > |
| |||||||
StatusIn brief, | ||||||||
Added: | ||||||||
> > |
| |||||||
Changed: | ||||||||
< < | -- RayPlante - 05 Nov 2009 | |||||||
> > | -- RayPlante - 18 May 2012 | |||||||
Schema-to-Spec StylesheetTo support this effort, a few people (Harrison, Plante) have author XSL stylesheets to convert XML Schemas into HTML. Ray Plante's efforts have been uploaded to the volute google code repository under trunk/projects/registry/tools. more info comingComments to current draftThe suggested ssa: prefix for the SSAP extension schema is unfortunate. This is due to the abuse of xmlns in "binding" the model name (the thing before the colon in a utype) to a data model URL in the SSA spec. Withit, in any document that contains SSA utypes (e.g., table definitions of SSA services), the ssa XML prefix is taken. So -- can we use ssap? Or ssareg? -- MarkusDemleitner - 18 May 2011 | ||||||||
Added: | ||||||||
> > | The suggestion was incorporated into the latest draft. -- RayPlante | |||||||
Historical materialsThis work used to be traced via the RegSimpleDAL page. That page is now deprecated. Attachments to that page include:<--
|