VODataService: a VOResource Schema Extension for Describing Collections, Services Version 1.1

Plante, Raymond; Stebe, A.; Benson, K.; Dowler, Patrick; Graham, Matthew; Greene, Gretchen; Harrison, Paul; Lemson, Gerard; Linde, Tony; Rixon, G.

doi:10.5479/ads/bib/2010ivoa.spec.1202p

Cited by 8 publications

(16 citation statements)

References 2 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…For instance, classes for Dataset, Curation, and Identification had been designed early in the Resource Metadata standard and organized in a tree-like structure as an XML schema 3 in VOResource and VODataService (Plante et al, 2010). These concepts, first stated in the Registry WG, are valid throughout the VO and are reused as key building blocks in other data models.…”

Section: Metadata All Aroundmentioning

confidence: 98%

Data modeling for the virtual observatory

Louys

2015

Astronomy and Computing

View full text Add to dashboard Cite

Section: Metadata All Aroundmentioning

confidence: 98%

Data modeling for the virtual observatory

Louys

2015

Astronomy and Computing

View full text Add to dashboard Cite

“…VOSI requests supply metadata concerning the availability ('VOSI-availability') of a TAP service, its main interfaces ('VOSI-capabilities'), and its data model ('VOSI-tables'). VOSI-capabilities and VOSItables outputs use the same XML schema [7] as the IVOA registry [16] and can be incorporated in service registrations.…”

Section: Vosimentioning

confidence: 99%

“…The /tables resource must be accessible via the http GET method. The content is described by [7] and is equivalent to the metadata from the TAP_SCHEMA described in 2.6 .…”

Section: /Tablesmentioning

confidence: 99%

“…First, the VOSI tables resource provides metadata on all tables and columns; this resource is described in 2.2.5 . The VOSI tables resource provides the same metadata as the TAP_SCHEMA but in a rigorously controlled format; the information in the TAP_SCHEMA is equivalent to that defined by the VODataService [7]. Second, the client may specify a query of one or more tables setting the MAXREC parameter to 0 so that only the metadata regarding the requested fields is returned.…”

Section: Metadata and Tap_schemamentioning

confidence: 99%

See 1 more Smart Citation

Table Access Protocol Version 1.0

Dowler¹,

Rixon²,

Tody³

Self Cite

View full text Add to dashboard Cite

The table access protocol (TAP) defines a service protocol for accessing general table data, including astronomical catalogs as well as general database tables. Access is provided for both database and table metadata as well as for actual table data. This version of the protocol includes support for multiple query languages, including queries specified using the Astronomical Data Query Language (ADQL [1]) and the Parameterised Query Language (PQL, under development) within an integrated interface. It also includes support for both synchronous and asynchronous queries. Special support is provided for spatially indexed queries using the spatial extensions in ADQL. A multi-position query capability permits queries against an arbitrarily large list of astronomical targets, providing a simple spatial cross-matching capability.More sophisticated distributed cross-matching capabilities are possible by orchestrating a distributed query across multiple TAP services.

show abstract

“…This class is a place holder that gathers all metadata relative to an observed and distributed dataset. It points to existing classes of Spectrum DM and types from VODataService (Plante & al., 2010) .…”

Section: B1 Observation Informationmentioning

confidence: 99%

Observation Data Model Core Components, its Implementation in the Table Access Protocol Version 1.0

Louys¹,

Bonnarel²,

Schade³

et al.

Self Cite

View full text Add to dashboard Cite

This document defines the core components of the Observation data model that are necessary to perform data discovery when querying data centers for observations of interest. It exposes usecases to be carried out, explains the model and provides guidelines for its implementation as a data access service based on the Table Access Protocol (TAP). It aims at providing a simple model easy to understand and to implement by data providers that wish to publish their data into the Virtual ObsTAP -2 -Observatory. This interface integrates data modeling and data access aspects in a single service and is named ObsTAP. It will be referenced as such in the IVOA registries. There will be a separate document to cover the full Observation data model. In this document, the Observation Data Model Core Components (ObsCoreDM) defines the core components of queryable metadata required for global discovery of observational data. It is meant to allow a single query to be posed to TAP services at multiple sites to perform global data discovery without having to understand the details of the services present at each site. It defines a minimal set of basic metadata and thus allows for a reasonable cost of implementation by data providers. The combination of the ObsCoreDM with TAP is referred to as an ObsTAP service. As with most of the VO Data Models, ObsCoreDM makes use of STC, Utypes, Units and UCDs. The ObsCoreDM can be serialized as a VOTable. ObsCoreDM can make reference to more complete data models such as ObsProvDM (the Observation Provenance Data Model, to come), Characterisation DM, Spectrum DM or Simple Spectral Line Data Model (SSLDM). Status of this documentThis document has been produced by the IVOA Data Model (DM) working group, in coordination with partners involved in the definition of data access protocols (DAL) and of the ADQL language. It describes the core components of the Observation data model and the metadata to be attached to an astronomical observation, and contains a guide for implementing this model within the Table Access Protocol (TAP) framework. Due to the DM and DAL aspects of this document, this will circulate and be reviewed by both Working Groups. The document content has been worked out as working draft in a previous stage (2009)(2010) and is now proposed for IVOA recommendation.A list of current IVOA Recommendations and other technical documents can be found at http://www.ivoa.net/Documents/ Acknowledgements This work has been partly funded by Euro-VO AIDA project that we acknowledge here. SSC XMM Catalog service supported the implementation of the SAADA version of ObsTAP at Strasbourg Observatory. The US-VAO project contributed to developing this specification and prototyping the use of ObsTAP in the VAO portal. The CANFAR project also contributed for the reference implementation of ObsTAP at CADC, Victoria.ObsTAP -3 -

show abstract

VODataService: a VOResource Schema Extension for Describing Collections, Services Version 1.1

Cited by 8 publications

References 2 publications

Data modeling for the virtual observatory

Data modeling for the virtual observatory

Table Access Protocol Version 1.0

Observation Data Model Core Components, its Implementation in the Table Access Protocol Version 1.0

Contact Info

Product

Resources

About