Search

Start Over Publisher IVOA Content Level Research Validation Level 2
1. Adopting the UAT as an IVOA vocabulary
ID:
ivo://ivoa.net/std/uat-as-upstream
Title:
Adopting the UAT as an IVOA vocabulary
Short Name:
uat-as-upstream
Date:
25 Jul 2022 13:00:00
Publisher:
IVOA
Description:
The Unified Astronomy Thesaurus (UAT) provides a comprehensive, interlinked set of concepts relevant for astronomy and astrophysics using SKOS. It is taken up in the Virtual Observatory at least for registry subject keywords. For various reasons, it is desirable to have the UAT available subject to the constraints laid down in the IVOA Vocabularies in the VO 2 specification. This Note describes the rationale and the details of the UAT adoption by the IVOA.
2. IVOA Identifiers
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.
3. IVOA Registry Relational Schema
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.
4. MOC - HEALPix Multi-Order Coverage map
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.
5. Observation Data Model Core Components and its Implementation in the Table Access Protocol
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.
6. Resource Metadata for the Virtual Observatory
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.
7. Simple Application Messaging Protocol
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.
8. The ivoa data model
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
9. Units in the VO
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.
10. Vocabularies in the VO
ID:
ivo://ivoa.net/std/vocabularies
Title:
Vocabularies in the VO
Short Name:
vocabularies
Date:
02 Jun 2023 00:30:00
Publisher:
IVOA
Description:
In this document, we discuss practices related to the use of RDF-based consensus vocabularies in the Virtual Observatory, that is the creation, publication, maintenance, and consumption of hierarchical word lists agreed upon within the IVOA. To cover the wide range of use cases envisoned, we define different vocabulary types for informal knowledge organisation on the one hand, and strict hierarchies of classes and properties on the other. While the framework rests on the solid foundations of W3C RDF, provisions are made to facilitate using IVOA vocabularies without specific RDF tooling. Non-normative appendices detail the current vocabulary-related tooling.

Limit your search