- ID:
- ivo://ivoa.net/std/Identifiers
- Title:
- IVOA Identifiers
- Date:
- 21 Oct 2016 06:52:00
- Publisher:
- IVOA
- Description:
- An IVOA Identifier is a globally unique name for a resource within the Virtual Observatory. This name can be used to retrieve a unique description of the resource from an IVOA-compliant registry or to identify an entity like a dataset or a protocol without dereferencing the identifier. This document describes the syntax for IVOA Identifiers as well as how they are created. The syntax has been defined to encourage global-uniqueness naturally and to maximize the freedom of resource providers to control the character content of an identifier.
1 - 10 of 10
Number of results to display per page
Search Results
- ID:
- ivo://ivoa.net/std/RegTAP
- Title:
- IVOA Registry Relational Schema
- Date:
- 21 Oct 2016 08:34:00
- Publisher:
- IVOA
- Description:
- Registries provide a mechanism with which VO applications can discover and select resources - first and foremost data and services - that are relevant for a particular scientific problem. This specification defines an interface for searching this resource metadata based on the IVOA's TAP protocol. It specifies a set of tables that comprise a useful subset of the information contained in the registry records, as well as the table's data content in terms of the XML VOResource data model. The general design of the system is geared towards allowing easy authoring of queries.
- ID:
- ivo://ivoa.net/std/MOC
- Title:
- MOC - HEALPix Multi-Order Coverage map
- Date:
- 20 Sep 2016 09:45:00
- Publisher:
- IVOA
- Description:
- The Multi-Order Coverage map method (MOC) is dedicated to specify arbitrary sky regions. The goal is to be able to provide a very fast comparison mechanism between coverage maps. The mechanism is based on the HEALPix sky tessellation algorithm. It is essentially a simple way to map regions of the sky into hierarchically grouped predefined cells.
- ID:
- ivo://ivoa.net/std/obscore
- Title:
- Observation Data Model Core Components and its Implementation in the Table Access Protocol
- Date:
- 10 May 2017 08:00:00
- Publisher:
- IVOA
- Description:
- This document defines the core components of the Observation data model that are necessary to perform data discovery when querying data centers for astronomical observations of interest. It exposes use-cases 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 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. 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. 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 Characterisation DM, Spectrum DM or Simple Spectral Line Data Model (SSLDM). ObsCore shares a large set of common concepts with DataSet Metadata Data Model (Cresitello-Dittmar et al. 2016) which binds together most of the data model concepts from the above models in a comprehensive and more general frame work. This current specification on the contrary provides guidelines for implementing these concepts using the TAP protocol and answering ADQL queries. It is dedicated to global discovery.
- ID:
- ivo://ivoa.net/std/RM
- Title:
- Resource Metadata for the Virtual Observatory
- Date:
- 21 Oct 2016 09:40:00
- Publisher:
- IVOA
- Description:
- An essential capability of the Virtual Observatory is a means for describing what data and computational facilities are available where, and once identified, how to use them. The data themselves have associated metadata (e.g., FITS keywords), and similarly we require metadata about data collections and data services so that VO users can easily find information of interest. Furthermore, such metadata are needed in order to manage distributed queries efficiently; if a user is interested in finding x-ray images there is no point in querying the HST archive, for example. In this document we suggest an architecture for resource and service metadata and describe the relationship of this architecture to emerging Web Services standards. We also define an initial set of metadata concepts.
- ID:
- ivo://ivoa.net/std/samp
- Title:
- Simple Application Messaging Protocol
- Date:
- 19 Sep 2016 22:00:00
- Publisher:
- IVOA
- Description:
- SAMP is a messaging protocol that enables astronomy software tools to interoperate and communicate. IVOA members have recognised that building a monolithic tool that attempts to fulfil all the requirements of all users is impractical, and it is a better use of our limited resources to enable individual tools to work together better. One element of this is defining common file formats for the exchange of data between different applications. Another important component is a messaging system that enables the applications to share data and take advantage of each other's functionality. SAMP supports communication between applications on the desktop and in web browsers, and is also intended to form a framework for more general messaging requirements.
- ID:
- ivo://ivoa.net/std/ivoadm
- Title:
- The ivoa data model
- Date:
- 19 May 2018 09:00:00
- Publisher:
- IVOA
- Description:
- Ultimately all types in a VO-DML model are defined as hierarchies of primitive types. This Model defines a special, predefined model that contains a set of the most common of such types: integer, real, string etc. This
- ID:
- ivo://ivoa.net/std/VOUnits
- Title:
- Units in the VO
- Short Name:
- VOUnits
- Date:
- 04 Dec 2019 16:44:00
- Publisher:
- IVOA
- Description:
- This document describes a recommended syntax for writing the string representation of unit labels ("VOUnits"). In addition, it describes a set of recognised and deprecated units, which is as far as possible consistent with other relevant standards (BIPM, ISO/IEC and the IAU). The intention is that units written to conform to this specification will likely also be parsable by other well-known parsers. To this end, we include machine-readable grammars for other units syntaxes.
- ID:
- ivo://ivoa.net/std/VODataService
- Title:
- VODataService: a VOResource Schema Extension for Describing Collections and Services
- Date:
- 21 Oct 2016 08:20:00
- Publisher:
- IVOA
- Description:
- VODataService refers to an XML encoding standard for a specialized extension of the IVOA Resource Metadata that is useful for describing data collections and the services that access them. It is defined as an extension of the core resource metadata encoding standard known as VOResource [Plante et al. 2008] using XML Schema. The specialized resource types defined by the VODataService schema allow one to describe how the data underlying the resource cover the sky as well as cover frequency and time. This coverage description leverages heavily the Space-Time Coordinates (STC) standard schema [Rots 2007]. VODataService also enables detailed descriptions of tables that includes information useful to the discovery of tabular data. It is intended that the VODataService data types will be particularly useful in describing services that support standard IVOA service protocols.
- ID:
- ivo://ivoa.net/std/VODML
- Title:
- VO-DML: a consistent modeling language for IVOA data models
- Date:
- 31 May 2018 09:00:00
- Publisher:
- IVOA
- Description:
- This document defines a standard modelling language, or meta-model, for expressing data models in the IVOA. Adopting such a uniform language for all models allows these to be used in a homogeneous manner and allows a consistent definition of reuse of one model by another. The particular language defined here includes a consistent identification mechanism for model which allows these to be referenced in an explicit and uniform manner also from other contexts, in particular from othe IVOA standard formats such as VOTable. The language defined in this specification is named VO-DML (VO Data Modeling Language). VO-DML is a conceptual modeling language that is agnostic of serializations, or physical representations. This allows it to be designed to fit as many purposes as possible. VO-DML is directly based on UML, and can be seen as a particular representation of a UML2 Profile. VO-DML is restricted to describing static data structures and from UML it only uses a subset of the elements defined in its language for describing "Class Diagrams". Its concepts can be easily mapped to equivalent data modelling concepts in other representations such as relational databases, XML schemas and object-oriented computer languages. VO-DML has a representation as a simple XML dialect named VO-DML/XML that must be used to provide the formal representation of a VO-MDL data model. VO-DML/XML aims to be concise, explicit and easy to parse and use in code that needs to interpret annotated data sets. VO-DML as described in this document is an example of a domain specific modeling language, where the domain here is defined as the set of data and meta-data structures handled in the IVOA and Astronomy at large. VO-DML provides a custom representation of such a language and as a side effect allows the creation and use of standards compliant data models outside of the IVOA standards context.
