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
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Added: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
<--
Samples
Status
<--
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 The suggestion was incorporated into the latest draft. -- RayPlanteHistorical materialsThis work used to be traced via the RegSimpleDAL page. That page is now deprecated. Attachments to that page include:<--
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Added: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||
<--
Samples
Status
<--
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 The suggestion was incorporated into the latest draft. -- RayPlanteHistorical materialsThis work used to be traced via the RegSimpleDAL page. That page is now deprecated. Attachments to that page include:<--
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
Added: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | Jumps: IvoaResReg :: registry mail archive :: VOResource :: VODataService :: StandardsRegExt | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | Jumps: IvoaResReg :: registry mail archive :: VOResource :: VODataService :: StandardsRegExt Meetings: InterOpOct2011Registry :: InterOpMay2011Registry :: InterOpMay2010Reg :: InterOpNov2009Reg :: InterOpMay2009ResReg :: InterOpMay2008ResReg :: InterOpSep2007ResReg :: InterOpMay2007ResReg | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
Deleted: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | Meetings: InterOpOct2011Registry :: InterOpMay2011Registry :: InterOpMay2010Reg :: InterOpNov2009Reg :: InterOpMay2009ResReg :: InterOpMay2008ResReg :: InterOpSep2007ResReg :: InterOpMay2007ResReg | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
Deleted: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
VOResource Extensions for Describing SSA, SIA, SLA, and ConeSearch Services | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | The page tracks the development of the IVOA specification document defining VOResource Extensions for SSA, SIA, SLA, and ConeSearch Services. The draft abstract is as follows: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | The page tracks the development of the IVOA specification document defining VOResource Extensions for SSA, SIA, SLA, and ConeSearch Services. The draft abstract is as follows: | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | 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. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
Deleted: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | 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. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
Contents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
Added: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
Documents | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||
<--
Samples
Status | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||
Deleted: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | The details can be reviewed in this follow-up report
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||
<--
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
Deleted: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
Schema-to-Spec Stylesheet | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | To 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 coming | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | To 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 coming | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
Deleted: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
Comments to current draft | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | The suggested ssa: prefix for the SSAP extension schema is unfortunate. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | The 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? | ||||||||||||||||||||||||||||||||||||||||||||||||||||||
Deleted: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | 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 The suggestion was incorporated into the latest draft. -- RayPlante | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
Deleted: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
Historical materialsThis work used to be traced via the RegSimpleDAL page. That page is now deprecated. Attachments to that page include: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
Deleted: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||
<--
|
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: | |||||||||||||||||||||||||||||
< < |
| ||||||||||||||||||||||||||||
> > |
| ||||||||||||||||||||||||||||
Deleted: | |||||||||||||||||||||||||||||
< < |
| ||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||
< < |
| ||||||||||||||||||||||||||||
> > |
| ||||||||||||||||||||||||||||
Added: | |||||||||||||||||||||||||||||
> > |
| ||||||||||||||||||||||||||||
<--
Samples
Status
<--
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 The suggestion was incorporated into the latest draft. -- RayPlanteHistorical materialsThis work used to be traced via the RegSimpleDAL page. That page is now deprecated. Attachments to that page include:<--
| |||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||
< < |
| ||||||||||||||||||||||||||||
> > |
| ||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||
< < |
| ||||||||||||||||||||||||||||
> > |
| ||||||||||||||||||||||||||||
Added: | |||||||||||||||||||||||||||||
> > |
| ||||||||||||||||||||||||||||
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
<--
Samples
Status
<--
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 The suggestion was incorporated into the latest draft. -- RayPlanteHistorical materialsThis work used to be traced via the RegSimpleDAL page. That page is now deprecated. Attachments to that page include:<--
| |||||||||||||||||||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||||||||||||||||||
< < |
| ||||||||||||||||||||||||||||||||||||||||||||
> > |
| ||||||||||||||||||||||||||||||||||||||||||||
|
Meetings: InterOpOct2011Registry :: InterOpMay2011Registry :: InterOpMay2010Reg :: InterOpNov2009Reg :: InterOpMay2009ResReg :: InterOpMay2008ResReg :: InterOpSep2007ResReg :: InterOpMay2007ResReg | |||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||||||||||||||||||||||||
< < | VOResource Extensions for Describing SSA, SIA, SLA, and ConeSearch Services | ||||||||||||||||||||||||||||||||||||||||||||||||||
> > | 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: | |||||||||||||||||||||||||||||||||||||||||||||||||||
< < |
| ||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
| ||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||||||||||||||||||||||||
< < |
| ||||||||||||||||||||||||||||||||||||||||||||||||||
> > |
| ||||||||||||||||||||||||||||||||||||||||||||||||||
Added: | |||||||||||||||||||||||||||||||||||||||||||||||||||
> > | |||||||||||||||||||||||||||||||||||||||||||||||||||
Samples
Status
<--
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 The suggestion was incorporated into the latest draft. -- RayPlanteHistorical materialsThis work used to be traced via the RegSimpleDAL page. That page is now deprecated. Attachments to that page include:<--
|
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
Samples
Status
<--
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 The suggestion was incorporated into the latest draft. -- RayPlanteHistorical materialsThis work used to be traced via the RegSimpleDAL page. That page is now deprecated. Attachments to that page include:<--
| |||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||
< < |
| ||||||||||||||||||||||||
> > |
| ||||||||||||||||||||||||
| |||||||||||||||||||||||||
Added: | |||||||||||||||||||||||||
> > |
| ||||||||||||||||||||||||
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: | |||||||||||||||
> > |
| ||||||||||||||
Changed: | |||||||||||||||
< < |
| ||||||||||||||
> > |
| ||||||||||||||
Deleted: | |||||||||||||||
< < |
| ||||||||||||||
Samples
Status
<--
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 The suggestion was incorporated into the latest draft. -- RayPlanteHistorical materialsThis work used to be traced via the RegSimpleDAL page. That page is now deprecated. Attachments to that page include:<--
| |||||||||||||||
Changed: | |||||||||||||||
< < |
| ||||||||||||||
> > |
| ||||||||||||||
| |||||||||||||||
Added: | |||||||||||||||
> > |
| ||||||||||||||
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 | |||||||||||||||||||||
Added: | |||||||||||||||||||||
> > |
| ||||||||||||||||||||
| |||||||||||||||||||||
Changed: | |||||||||||||||||||||
< < |
| ||||||||||||||||||||
> > |
| ||||||||||||||||||||
Samples
Status
<--
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 The suggestion was incorporated into the latest draft. -- RayPlanteHistorical materialsThis work used to be traced via the RegSimpleDAL page. That page is now deprecated. Attachments to that page include:<--
| |||||||||||||||||||||
Added: | |||||||||||||||||||||
> > |
| ||||||||||||||||||||
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
Samples
Status | |||||||||||||||||||||
Changed: | |||||||||||||||||||||
< < | |||||||||||||||||||||
> > |
| ||||||||||||||||||||
Deleted: | |||||||||||||||||||||
< < |
| ||||||||||||||||||||
| |||||||||||||||||||||
Changed: | |||||||||||||||||||||
< < |
| ||||||||||||||||||||
> > | |||||||||||||||||||||
Deleted: | |||||||||||||||||||||
< < | |||||||||||||||||||||
<--
| |||||||||||||||||||||
Changed: | |||||||||||||||||||||
< < | -- RayPlante - 18 May 2012 | ||||||||||||||||||||
> > | -- GretchenGreene - August 3, 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 The suggestion was incorporated into the latest draft. -- RayPlanteHistorical materialsThis work used to be traced via the RegSimpleDAL page. That page is now deprecated. Attachments to that page include:<--
|
Meetings: InterOpOct2011Registry :: InterOpMay2011Registry :: InterOpMay2010Reg :: InterOpNov2009Reg :: InterOpMay2009ResReg :: InterOpMay2008ResReg :: InterOpSep2007ResReg :: InterOpMay2007ResReg VOResource Extensions for Describing SSA, SIA, SLA, and ConeSearch Services | |||||||||||||||||||||
Changed: | |||||||||||||||||||||
< < |
| ||||||||||||||||||||
> > |
| ||||||||||||||||||||
The page tracks the development of the IVOA specification document defining VOResource Extensions for SSA, SIA, SLA, and ConeSearch Services. The draft abstract is as follows:
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: | |||||||||||||||||||||
< < |
| ||||||||||||||||||||
> > |
| ||||||||||||||||||||
Changed: | |||||||||||||||||||||
< < |
| ||||||||||||||||||||
> > |
| ||||||||||||||||||||
Changed: | |||||||||||||||||||||
< < |
| ||||||||||||||||||||
> > |
| ||||||||||||||||||||
Changed: | |||||||||||||||||||||
< < |
| ||||||||||||||||||||
> > |
| ||||||||||||||||||||
Samples | |||||||||||||||||||||
Changed: | |||||||||||||||||||||
< < |
| ||||||||||||||||||||
> > |
| ||||||||||||||||||||
Status | |||||||||||||||||||||
Changed: | |||||||||||||||||||||
< < | In brief,
| ||||||||||||||||||||
> > |
| ||||||||||||||||||||
-- 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 The suggestion was incorporated into the latest draft. -- RayPlanteHistorical materialsThis work used to be traced via the RegSimpleDAL page. That page is now deprecated. Attachments to that page include: | |||||||||||||||||||||
Changed: | |||||||||||||||||||||
< < | |||||||||||||||||||||
> > | |||||||||||||||||||||
|
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
Samples
StatusIn brief,
<--
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 The suggestion was incorporated into the latest draft. -- RayPlanteHistorical materialsThis work used to be traced via the RegSimpleDAL page. That page is now deprecated. Attachments to that page include:
|
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: | |||||||||||||
< < |
| ||||||||||||
> > |
| ||||||||||||
Changed: | |||||||||||||
< < |
| ||||||||||||
> > |
| ||||||||||||
| |||||||||||||
Added: | |||||||||||||
> > | Samples
| ||||||||||||
StatusIn brief,
<--
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 The suggestion was incorporated into the latest draft. -- RayPlanteHistorical materialsThis work used to be traced via the RegSimpleDAL page. That page is now deprecated. Attachments to that page include:<--
| |||||||||||||
Added: | |||||||||||||
> > |
| ||||||||||||
| ||||||||
Changed: | ||||||||
< < | Jumps: IvoaResReg :: registry mail archive :: VOResource :: VODataService :: RegDMStandards | |||||||
> > | Jumps: IvoaResReg :: registry mail archive :: VOResource :: VODataService :: StandardsRegExt | |||||||
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: | ||||||||
< < |
| |||||||
> > |
| |||||||
StatusIn brief,
<--
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 The suggestion was incorporated into the latest draft. -- RayPlanteHistorical materialsThis work used to be traced via the RegSimpleDAL page. That page is now deprecated. Attachments to that page include:<--
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
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:<--
|
Meetings: 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: | ||||||||
< < |
| |||||||
> > |
| |||||||
StatusIn brief,
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 2011Historical materialsThis work used to be traced via the RegSimpleDAL page. That page is now deprecated. Attachments to that page include:<--
|
Meetings: 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
StatusIn brief,
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 2011Historical materialsThis work used to be traced via the RegSimpleDAL page. That page is now deprecated. Attachments to that page include:<--
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
|
Meetings: 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
StatusIn brief,
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 2011Historical materialsThis work used to be traced via the RegSimpleDAL page. That page is now deprecated. Attachments to that page include:<--
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
|
Meetings: 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
StatusIn brief,
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 2011Historical materialsThis work used to be traced via the RegSimpleDAL page. That page is now deprecated. Attachments to that page include:<--
| ||||||||
Added: | ||||||||
> > |
| |||||||
Meetings: 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
StatusIn brief,
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 coming | ||||||||
Added: | ||||||||
> > |
Comments 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 | |||||||
Historical materialsThis work used to be traced via the RegSimpleDAL page. That page is now deprecated. Attachments to that page include:<--
|
Meetings: 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: | ||||||||
< < |
| |||||||
> > |
| |||||||
StatusIn brief,
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 comingHistorical materialsThis work used to be traced via the RegSimpleDAL page. That page is now deprecated. Attachments to that page include:<--
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Meetings: InterOpMay2010Reg :: InterOpNov2009Reg :: InterOpMay2009ResReg :: InterOpMay2008ResReg :: InterOpSep2007ResReg :: InterOpMay2007ResReg | ||||||||
Changed: | ||||||||
< < | VOResource Extensions for Describing SSA, SIA, and ConeSearch Services | |||||||
> > | VOResource Extensions for Describing SSA, SIA, SLA, and ConeSearch Services | |||||||
| ||||||||
Changed: | ||||||||
< < | The page tracks the development of the IVOA specification document defining VOResource Extensions for SSA, SIA, and ConeSearch Services. The draft abstract is as follows: | |||||||
> > | The page tracks the development of the IVOA specification document defining VOResource Extensions for SSA, SIA, SLA, and ConeSearch Services. The draft abstract is as follows: | |||||||
Changed: | ||||||||
< < | 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 service that supports three fundemental data access protocols--Simple Cone Search (SCS), Simple Image Access (SIA), and Simple Spectral Access (SSA)--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. | |||||||
> > | An application that queries or consumes descriptions of VO resources | |||||||
Added: | ||||||||
> > | 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: | ||||||||
< < |
| |||||||
> > |
| |||||||
StatusIn brief,
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 comingHistorical materialsThis work used to be traced via the RegSimpleDAL page. That page is now deprecated. Attachments to that page include:<--
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Meetings: InterOpMay2010Reg :: InterOpNov2009Reg :: InterOpMay2009ResReg :: InterOpMay2008ResReg :: InterOpSep2007ResReg :: InterOpMay2007ResReg VOResource Extensions for Describing SSA, SIA, 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 service that supports three fundemental data access protocols--Simple Cone Search (SCS), Simple Image Access (SIA), and Simple Spectral Access (SSA)--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: | ||||||||
< < |
| |||||||
> > |
| |||||||
StatusIn brief,
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 comingHistorical materialsThis work used to be traced via the RegSimpleDAL page. That page is now deprecated. Attachments to that page include:<--
| ||||||||
Added: | ||||||||
> > |
| |||||||
Meetings: InterOpMay2010Reg :: InterOpNov2009Reg :: InterOpMay2009ResReg :: InterOpMay2008ResReg :: InterOpSep2007ResReg :: InterOpMay2007ResReg VOResource Extensions for Describing SSA, SIA, 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 service that supports three fundemental data access protocols--Simple Cone Search (SCS), Simple Image Access (SIA), and Simple Spectral Access (SSA)--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
StatusIn brief,
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 comingHistorical materialsThis work used to be traced via the RegSimpleDAL page. That page is now deprecated. Attachments to that page include:<--
|