2026-04-21T02:36:30Z http://rofr.ivoa.net/oai ivo://ivoa.net/std/hips 2023-05-23T14:03:00Z Standard ivo_managed ivo://ivoa.net/std/hips IVOA Apps Working Group Fernique, P. Allen, M. Boch, T. Donaldson, T. Durand, D. Ebisawa, K. Michel, L. Salgado, J. Stoehr, F. 2017-06-01T09:33:00 IVOA Apps Working Group apps@ivoa.net Virtual observatory Standards HiPS HiPS: a hierarchical scheme for the description, storage and access of sky survey data. The system is based on hierarchical tiling of sky regions at finer and finer spatial resolution which facilitates a progressive view of a survey, and supports multi-resolution zooming and panning. HiPS uses the HEALPix tessellation of the sky as the basis for the scheme and is implemented as a simple file structure with a direct indexing scheme that leads to practical implementations. http://ivoa.net/documents/HiPS 1.0 hipslist-1.0 A service returning a list of HiPS identifiers and metadata for HiPS. This term is used to form a standardID, for instance for use in vr:Capability. hips-1.0 A single HiPS. This term is used to form a standardID, for instance for use in vr:Capability. ivo://ivoa.net/std/MOC 2023-05-23T14:03:00Z Standard ivo_managed ivo://ivoa.net/std/MOC IVOA Fernique, P. Boch, T. Donaldson, T. Durand, D. O'Mullane, W. Reinecke, M. Taylor, M. 2014-06-02 1.0 Applications WG apps@ivoa.net Virtual observatory 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. http://ivoa.net/documents/MOC/ Other Research 1.0 ivo://ivoa.net/std/ucdvoc 2023-05-23T14:03:00Z Standard ivo_managed ucdvoc ivo://ivoa.net/std/ucdvoc doi:10.5479/ADS/bib/2018ivoa.spec.0527M IVOA Preite Martinez, A. Louys, M. Cecconi, B. Derriere, S. Ochsenbein, F. 2018-05-27 1.3 IVOA Semantics Working Group semantics@ivoa.net Virtual observatory Semantics This document describes the list of controlled terms used to build the Unified Content Descriptors, Version 1+ (UCD1+). The document describing the UCD1+ can be found at the URL: http://www.ivoa.net/Documents/latest/UCD.html. This document reviews the structure of the UCD1+ and presents the current vocabulary. This version contains new UCD words for the planetary data community as proposed in the Technical Note by Cecconi et al.. The suggested list of line labels under the em.line branch is not included. A general solution is currently under study to deal with lists of element instances such spectral lines, chemical elements, elementary particles, etc. using either utypes or a vocabulary. http://www.ivoa.net/documents/UCD1+/ Other Research 1.3 ivo://ivoa.net/std/SimpleDALRegExt 2023-05-23T14:03:00Z Standard ivo_managed SimpleDALRegExt ivo://ivoa.net/std/SimpleDALRegExt International Virtual Observatory Alliance Raymond Plante Jesus Delago Paul Harrison Doug Tody 2012-10-26 1.0 Registry Working Group registry@ivoa.net software standard virtual observatory registry data access layer DAL 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 any of the four fundamental 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 Standard 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. http://www.ivoa.net/Documents/SimpleDALRegExt/ Other Research related-to Simple Image Access Protocol related-to Simple Cone Search related-to Simple Spectral Access Protocol related-to Simple Line Access Protocol related-to VOResource: an XML Encoding Schema for Resource Metadata 1.0 http://www.ivoa.net/xml/ConeSearch/v1.0 the VOResource extension schema for describing Simple Cone Search services in the registry. http://206-12-97-214.cloud.computecanada.ca/examples/ http://www.ivoa.net/xml/SIA/v1.1 the VOResource extension schema for describing Simple Image Access services in the registry. http://206-12-97-214.cloud.computecanada.ca/examples/ http://www.ivoa.net/xml/SSA/v1.1 the VOResource extension schema for describing Simple Spectral Access services in the registry. http://206-12-97-214.cloud.computecanada.ca/examples/ http://www.ivoa.net/xml/SLAP/v1.0 the VOResource extension schema for describing Simple Line Access services in the registry. http://206-12-97-214.cloud.computecanada.ca/examples/ ivo://ivoa.net/std/VOResource 2025-04-16T09:07:32.628361Z Standard ivo_managed VOResource ivo://ivoa.net/std/VOResource International Virtual Observatory Alliance Raymond Plante Kevin Benson Markus Demleitner Matthew Graham Gretchen Greene Paul Harrison Gerard Lemson Tony Linde Guy Rixon 2025-04-16 2008-02-22 1.2 Registry Working Group registry@ivoa.net virtual-observatories This document describes an XML encoding standard for IVOA Resource Metadata, referred to as VOResource. This schema is primarily intended to support metadata exchange between interoperable registries and resource discovery within them. However, any application that needs to describe resources may use this schema. In this document, we define the types and elements that make up the schema in close alignment to the metadata terms defined in Resource Metadata for the Virtual Observatory (Hanisch 2007), but also taking into account other metadata standards as well as experiences from the operation of the VO Registry. We also describe the general model for the schema and explain how it is extended to add new metadata terms and describe more specific types of resources. http://www.ivoa.net/Documents/VOResource Other Research related-to Resource Metadata for the Virtual Observatory 1.2 http://www.ivoa.net/xml/VOResource/v1.0 The core VOResource schema for describing resources in the registry. https://dc.g-vo.org/purx/q/enroll/info ivo://ivoa.net/std/VODataService 2023-05-23T14:03:00Z Standard ivo_managed ivo://ivoa.net/std/VODataService IVOA Plante, R. Stébé, A. Benson, K. Dowler, P. Graham, M. Greene, G. Harrison, P. Lemson, G. Linde, T. Rixon, G. 2021-11-02 1.2 IVOA Registry WG registry@ivoa.net virtual-observatories 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 and Demleitner et al., 2018) 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 and the frequency and time axes. 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. http://ivoa.net/documents/VODataService/ Other Research 1.2 http://ivoa.net/xml/VODataService/v1.1 A schema defining resource types for data and catalog services, including table metadata. ivo://ivoa.net/std/TAPRegExt 2023-05-23T14:03:00Z Standard ivo_managed ivo://ivoa.net/std/TAPRegExt IVOA IVOA Registry WG http://www.ivoa.net/icons/ivoa_logo_small.jpg IVOA DAL WG http://www.ivoa.net/icons/ivoa_logo_small.jpg 2012-08-27 1.0 IVOA DAL WG dal@ivoa.net standard language identifiers virtual observatory This document describes an XML encoding standard for metadata about TAP services. Specifically, it defines how the services' capability element is used to communicate upload methods, data formats, data models and languages supported, the languages' properties, as well as server limits. http://www.ivoa.net/Documents/TAPRegExt 1.0 upload-inline Table upload inline with the request, as per section 2.5.2 of the TAP recommendation 1.0. upload-http Table upload by giving an http URL in the UPLOAD parameter, see section 2.5.1 of the TAP recommendation 1.0. upload-https Table upload by giving an https URL in the UPLOAD parameter, see section 2.5.1 of the TAP recommendation 1.0. upload-ftp Table upload by giving an ftp URL in the UPLOAD parameter, see section 2.5.1 of the TAP recommendation 1.0. output-votable-td VOTable with data in a TABLEDATA element. output-votable-binary VOTable with data in a BINARY stream. output-votable-binary2 VOTable with data in a BINARY2 stream. features-udf An enumeration of ADQL or SQL user defined functions with their signatures. See the TAPRegExt specification for details. features-adqlgeo An enumeration of ADQL geometry functions implemented by the server. Support for a geometry function is declared by including a feature having just the function name in its form element. Since ADQL 2.0, there are the features AREA, BOX (deprecated in 2.1), CENTROID, CIRCLE, CONTAINS, COORD1, COORD2, DISTANCE, INTERSECTS, REGION, POINT, and POLYGON here. features-adql-string An enumeration of optional string functions implemented by the service. ADQL 2.1 defines the UPPER, LOWER and ILIKE features here. features-adql-common-table Features related to the support of common table expressions in the service's ADQL. ADQL 2.1 only has one feature, WITH, here. features-adql-sets Features related to the support of set operators in the service's ADQL. ADQL 2.1 defines three features here: UNION, EXCEPT, INTERSECT. features-adql-type Features related to the type conversions in the service's ADQL. ADQL 2.1 defines one feature here: CAST. features-adql-unit Features related to the service's support of in-ADQL unit parsing and coversion. ADQL 2.1 has only one feature, IN_UNIT, here. features-adql-offset Features related to the service's support of the ADQL OFFSET construct; ADQL 2.1 has only one feature, OFFSET, here. ivo://ivoa.net/std/ConeSearch 2023-05-23T14:03:00Z Standard ivo_managed ConsSearch ivo://ivoa.net/std/ConeSearch International Virtual Observatory Alliance Roy Williams Robert Hanisch Alex Szalay Raymond Plante 2008-02-22 1.0 Data Access Layer Working Group dal@ivoa.net software standard virtual observatory data access layer DAL This specification defines a simple query protocol for retrieving records from a catalog of astronomical sources. The query describes sky position and an angular distance, defining a cone on the sky. The response returns a list of astronomical sources from the catalog whose positions lie within the cone, formatted as a VOTable. This version of the specification is essentially a transcription of the original Cone Search specification in order to move it into the IVOA standardization process. Note that the metadata used to describe a Cone Search service in the registry is defined in the SimpleDALRegExt standard (ivo://www.ivoa.net/std/SimpleDALRegExt; http://www.ivoa.net/Documents/SimpleDALRegExt/). http://www.ivoa.net/Documents/latest/ConeSearch.html Other Research related-to SimpleDALRegExt: Describing Simple Data Access Services 1.03 http://sample.org/cgi-bin/scs GET text/xml+votable RA the right-ascension in the ICRS coordinate system for the positon of the center of the cone to search, given in decimal degrees. degrees real DEC the declination in the ICRS coordinate system for the positon of the center of the cone to search, given in decimal degrees. degrees real SR the radius of the cone to search, given in decimal degrees. degrees real VERB the level of verbosity in the output. string ivo://ivoa.net/std/RegistryInterface 2023-05-23T14:03:00Z Standard ivo_managed ivo://ivoa.net/std/RegistryInterface IVOA Dower, T. Demleitner, M. Benson, K. Plante, R. Auden, E. Graham, M. Greene, G. Hill, M. Linde, T. Morris, D. O'Mullane, W. Rixon, G. Stébé, A. Andrews, K. 2015-03-10 1.1 Registry WG registry@ivoa.net Virtual observatory Registry OAI-PMH The VO Registry provides a mechanism with which VO applications can discover and select resources that are relevant for a particular scientific problem. This specification defines the operation of this system. It is based on a general, distributed model composed of searchable and publishing registries, as introduced at the beginning of this document. The main body of the specification has two components: (a) an interface for harvesting publishing registries, which builds upon the Open Archives Initiative Protocol for Metadata Harvesting. (b) A VOResource extension for registering registry services and description of a central list of said IVOA registry services. Finally, this specification briefly discusses client interfaces to the Registry as provided by searchable registries. http://www.ivoa.net/documents/RegistryInterface Other Research 1.1 http://ivoa.net/xml/RegistryInterface/RegistryInterface-v1.0.xsd A small schema defining the global ri:Resource element used as a root element for VOResource records; it is necessary because VOResoruce itself defines no global elements by design. http://ivoa.net/xml/VORegistry/VORegistry-v1.0.xsd A VOResource extension defining resource and capability types for describing registry services. ivo://ivoa.net/std/vocabularies 2023-05-23T14:03:00Z Standard ivo_managed vocabularies ivo://ivoa.net/std/vocabularies IVOA Demleitner, M. Gray, N. Taylor, M. 2023-02-06 2.1 IVOA Semantics WG semantics@ivoa.net virtual-observatories 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. https://ivoa.net/documents/Vocabularies Other Research 2.1 ivo://ivoa.net/std/StandardsRegExt 2023-05-23T14:03:00Z Standard ivo_managed StandardsRegExt ivo://ivoa.net/std/StandardsRegExt International Virtual Observatory Alliance Paul Harrison Douglas Burke Ray Plante Guy Rixon Dave Morris IVOA Registry Working Group http://www.ivoa.net/icons/ivoa_logo_small.jpg 2010-05-19 2012-02-17 1.0 Resource Registry Working Group registry@ivoa.net software standard virtual observatory This document describes an XML encoding standard for metadata about IVOA standards themselves, referred to as StandardsRegExt. It is intended to allow for the discovery of a standard via an IVOA identifier that refers to the standard. It also allows one to define concepts that are defined by the standard which can themselves be referred to via an IVOA identifier (augmented with a URL fragment identifier). Finally, it can also provide a machine interpretable description of a standard service interface. We describe the general model for the schema and explain its intended use by interoperable registries for discovering resources. http://www.ivoa.net/Documents/StandardsRegExt/ Other Research 1.0 http://www.ivoa.net/xml/StandardsRegExt/v1.0 the VOResource extension XML Schema for registering standards http://206-12-97-214.cloud.computecanada.ca/examples/StandardsRegExt.xml http://206-12-97-214.cloud.computecanada.ca/examples/SIA.xml http://206-12-97-214.cloud.computecanada.ca/examples/VOSpace.xml ivo://ivoa.net/std/SSA 2023-05-23T14:03:00Z Standard ivo_managed SSA ivo://ivoa.net/std/SSA International Virtual Observatory Alliance Doug Tody Markus Dolensky Jonathan McDowell Francois Bonnarel Tamas Budavari Ivo Busko Alberto Micol Pedro Osuna Jesus Salgado Petr Skoda Randy Thompson Frank Valdes 2012-02-10 1.1 Data Access Layer Working Group dal@ivoa.net software standard virtual observatory data access layer DAL The Simple Spectral Access (SSA) Protocol (SSAP) defines a uniform interface to remotely discover and access one dimensional spectra. SSA is a member of an integrated family of data access interfaces altogether comprising the Data Access Layer (DAL) of the IVOA. SSA is based on a more general data model capable of describing most tabular spectrophotometric data, including time series and spectral energy distributions (SEDs) as well as 1-D spectra; however the scope of the SSA interface as specified in this document is limited to simple 1-D spectra, including simple aggregations of 1-D spectra. The form of the SSA interface is simple: clients first query the global resource registry to find services of interest and then issue a data discovery query to selected services to determine what relevant data is available from each service; the candidate datasets available are described uniformly in a VOTable format document which is returned in response to the query. Finally, the client may retrieve selected datasets for analysis. Spectrum datasets returned by an SSA spectrum service may be either precomputed, archival datasets, or they may be virtual data which is computed on the fly to respond to a client request. Spectrum datasets may conform to a standard data model defined by SSA, or may be native spectra with custom project-defined content. Spectra may be returned in any of a number of standard data formats. Spectral data is generally stored externally to the VO in a format specific to each spectral data collection; currently there is no standard way to represent astronomical spectra, and virtually every project does it differently. Hence spectra may be actively mediated to the standard SSA-defined data model at access time by the service, so that client analysis programs do not have to be familiar with the idiosyncratic details of each data collection to be accessed. Note that the metadata used to describe an SSA service in the registry is defined in the SimpleDALRegExt standard (ivo://www.ivoa.net/std/SimpleDALRegExt; http://www.ivoa.net/Documents/SimpleDALRegExt/). http://www.ivoa.net/Documents/SSA/ Other Research related-to VOTable Format Definition related-to SimpleDALRegExt: Describing Simple Data Access Services 1.1 http://sample.org/cgi-bin/ssa GET text/xml+votable REQUEST The request or operation name, where only "queryData" is allowed as a value. string VERSION The version of the SSA standard this query requests support for. string POS Search Position in the form "ra,dec" where ra and dec are given in decimal degrees. The coordinate system defaults to ICRS; otherwise, the system can be specified by appending ";sys", where sys is the name of the desired standard reference frame as defined in the STC standard. degrees real SIZE The diameter of the search cone specified in decimal degrees. degrees real BAND The desired spectral bandpass given either by a name or a frequency range. string BAND The desired spectral bandpass given either by a name or a frequency range. string TIME The desired time coverage (epoch) given as a time range. string FORMAT A comma-delimited list of requested formats, each specified as a MIME-type or one of "all", "compliant", "native", "graphic", "votable", "fits", "xml", or "metadata". string APERTURE diameter of the effective aperature to use when deriving spectra. real SPECRP The minimum spectral resolution, specified as the spectral resolving power l/dl in dimensionless units. real SPATRES minimum spatial resolution (corresponding to the PSF of the observed signal) specified in decimal degrees. degrees real TIMERES The minimum time resolution, specified in seconds. seconds real SNR The minimum signal-to-noise ratio of a candidate dataset, for example specified as the ratio of the mean signal to the RMS noise of the background. real REDSHIFT The photometric (observed) redshift range to restrict search to, specified as a single element open or closed range-list string VARAMPL The acceptable range of variability amplitude, specified as a single element open or closed range-list, with values in the range 0.0 to 1.0. string TARGETNAME The target name to search for, suitable for input to a source name resolver. string TARGETCLASS A comma delimited list of strings denoting the types of astronomical objects to be searched for. string FLUXCALIB The minimum level of flux calibration for acceptable data, given as one of “absolute”, "relative", "normalized", or “any” (the default). string WAVECALIB the minimum level of spectral coordinate calibration for acceptable data, given as one of “absolute”, "relative", or "any" (the default). string PUBDID The dataset identifier, as assigned by the publisher, to restrict to. string CREATORDID The dataset identifier, as assigned by the creator, to restrict to. string COLLECTION the name of the collection to restrict the search to string TOP The maximum number of records to return, selecting the best matched records. integer MAXREC The maximum number of records to be returned. integer MTIME The time range that the dataset was last modified or deleted to restrict the results to. string COMPRESS if present, return compressed versions of the datasets if available. boolean RUNID the opaque string to identify the logical collection of related queries. string ivo://ivoa.net/std/RegTAP 2024-10-02T09:59:00Z Standard ivo_managed ivo://ivoa.net/std/RegTAP IVOA Demleitner, M. Harrison, P. Molinaro, M. Greene, G. Dower, T. Perdikeas, M. 2024-10-02 1.2 IVOA Registry WG registry@ivoa.net virtual-observatories astronomy-databases 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. http://www.ivoa.net/documents/RegTAP Other Research 1.2 1.0 The data model for the tables making up the relational registriy in version 1.0. This key is used to locate TAP services implementing RR in TAPRegExt dataModel elements. 1.1 The data model for the tables making up the relational registriy in version 1.1. This key is used to locate TAP services implementing RR in TAPRegExt dataModel or VODataService schema/@utype elements. 1.2 The data model for the tables making up the relational registriy in version 1.2. This key is used to locate TAP services implementing the RR in TAPRegExt dataModel or VODataService schema/@utype elements. ivo://ivoa.net/std/sso 2023-05-23T14:03:00Z Standard ivo_managed ivo://ivoa.net/std/sso IVOA Taffoni, G. http://www.ivoa.net/icons/ivoa_logo_small.jpg Schaaff, A. Rixon, G. Major, B. 2017-05-24 2017-05-24 2.0 IVOA GWS WG grid@ivoa.net virtual observatory Approved client-server authentication mechanisms are described for the IVOA single-sign-on profile: No Authentication; HTTP Basic Authentication; TLS with passwords; TLS with client certificates; Cookies; Open Authentication; Security Assertion Markup Language; OpenID. Normative rules are given for the implementation of these mechanisms, mainly by reference to pre-existing standards. The Authorization mechanisms are out of the scope of this document. http://www.ivoa.net/Documents/SSOAuthMech 2.0 BasicAA Service supports authentication with HTTP basic authentication (RFC2617, sect. 4 of the Recommendation). tls-with-password Service supports authentication with a password transmitted through TLS as per section 7 of the Recommendation. tls-with-password Service supports authentication with a password transmitted through TLS as per section 7 of the Recommendation. tls-with-certificate Service supports authentication with a client-side X.509 certificate as per section 6 of the Recommendation. cookie Service supports authentication with RFC 6265-type cookies as per section 8 of the Recommendation. saml2.0 Service supports authentication via SAML (most likely, "Shibboleth") as per section 9 of the Recommendation. OAuth Service supports authentication via Open Authentication 2.0 ("OAuth") as per section 10 of the Recommendation. OpenID Service supports authentication via OpenID as per section 11 of the Recommendation. ivo://ivoa.net/std/SLAP 2023-05-23T14:03:00Z Standard ivo_managed SLAP ivo://ivoa.net/std/SLAP International Virtual Observatory Alliance Jesus Salgado Pedro Osuna Matteo Guainazzi Isa Barbarisi Marie-Lise Dubernet Doug Tody 2010-12-09 1.0 Data Access Layer Working Group dal@ivoa.net software standard virtual observatory data access layer DAL The Simple Line Access Protocol (SLAP) is an IVOA Data Access protocol which defines a protocol for retrieving spectral lines coming from various Spectral Line Data Collections through a uniform interface within the VO framework. These lines can be either observed or theoretical and will be typically used to identify emission or absorption features in astronomical spectra. It makes use of the Simple Spectral Line Data Model (SSLDM) to characterize spectral lines through the use of uTypes. Physical quantities of units are described by using the standard Units DM. SLAP services can be registered in an IVOA Registry of Resources using the VOResource Extension standard, having a unique ResourceIdentifier in the Registry. The SLAP interface is meant to be reasonably simple to implement by service providers. A basic query will be done in a wavelength range for the different services. The service returns a list of spectral lines formatted as a VOTable. Thus, an implementation of the service may support additional search parameters (some which may be custom to that particular service) to more finely control the selection of spectral lines. The specification also describes how the search on extra parameters has to be done, making use of the support provided by the Simple Spectral Line Data Model. Note that the metadata used to describe an SLAP service in the registry is defined in the SimpleDALRegExt standard (ivo://www.ivoa.net/std/SimpleDALRegExt; http://www.ivoa.net/Documents/SimpleDALRegExt/). http://www.ivoa.net/Documents/SLAP/ Other Research related-to VOTable Format Definition related-to SimpleDALRegExt: Describing Simple Data Access Services 1.0 http://sample.org/cgi-bin/sia GET text/xml+votable REQUEST The request or operation name, where only "queryData" is allowed as a value. string VERSION The version of the SLAP standard this query requests support for. string WAVELENTH The range of wavelengths to restrict search to string CHEMICAL_ELEMENT a list of chemical elements to search for string INITIAL_LEVEL_ENERGY The range of energy to restrict matched lines to based on the initial energy level of the transition measured in Joules. string FINAL_LEVEL_ENERGY The range of energy to restrict matched lines to based on the final energy level of the transition measured in Joules. string TEMPERATURE The expected temperature of the emitting or absorbing medium. degrees Kelvin real EINSTEIN_A The range of the Einstein A parameter to select lines by in units of probability per second. string PROCESS_TYPE The type of physical process responsible for the generation of the transition to restrict lines by, given as one of "Matter-radiationinteraction", `Matter-matter interaction", "Energy shift", "Broadening". string PROCESS_NAME The specific process responsible for the generation of the transition to restrict lines by, such as "Photoionization", "Collisional excitation", "Gravitational redshift", "Stark broadening", "Resonance broadening", "Van der Waals broadening", etc. string ivo://ivoa.net/std/ADQL 2023-05-23T14:03:00Z Standard ivo_managed ADQL ivo://ivoa.net/std/ADQL International Virtual Observatory Alliance Ortiz, I. Lusted, J. Dowler, P. Szalay, A. Shirasaki, Y. Nieto-Santisteban, M. Ohishi, M. O'Mullane, W. Osuna, P. 2008-10-30 Data Access Layer Working Group dal@ivoa.net software standard virtual observatory This document describes the Astronomical Data Query Language (ADQL). ADQL has been developed based on SQL92. This document describes the subset of the SQL grammar supported by ADQL. Special restrictions and extensions to SQL92 have been defined in order to support generic and astronomy specific operations. http://www.ivoa.net/Documents/latest/ADQL.html Other Research 2.0 v2.0 Version 2.0 of the query language. This key is used in TAPRegExt documents to declare support for this particular version of the standard. ivo://ivoa.net/std/UCDmaint 2023-05-23T14:03:00Z Standard ivo_managed UCDmaint ivo://ivoa.net/std/UCDmaint doi:10.5479/ADS/bib/2006ivoa.spec.0528M IVOA Genova, F. Louys, M. Preite Martinez, A. Derriere, S. Molinaro, M. Delmotte, N. Gray, N. Mann, R. McDowell, J. Mc Glynn, T. Ochsenbein, F. Osuna, P. Rixon, G. Williams, R. 2018-08-23 2.0 IVOA Semantics WG semantics@ivoa.net Virtual observatory Semantics According to what is stated in the IVOA Recommendation An IVOA standard for Unified Content Descriptors, this procedural document describes the maintenance (add, change, suppress words) of the IVOA list of UCD1+ words The UCD1+ Controlled Vocabulary. All versions of the list after V1.3, IVOA Recommendation 1.3, are IVOA Endorsed Notes. http://www.ivoa.net/documents/UCDlistMaintenance/ Other Research 2.0 ivo://ivoa.net/std/Identifiers 2023-05-23T14:03:00Z Standard ivo_managed ivo://ivoa.net/std/Identifiers IVOA Demleitner, M. Plante, R. Linde, T. Williams, R. Noddle, K. 2016-05-23 2.0 IVOA Registry WG registry@ivoa.net Virtual observatory URI 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. http://www.ivoa.net/documents/Identifiers Other Research 2.0 ivo://ivoa.net/std/obscore 2023-05-23T14:03:00Z Standard ivo_managed ivo://ivoa.net/std/obscore IVOA Louys, M. Tody, D. Dowler, P. Durand, D. Michel, L. Bonnarel, F. Micol, A. 2017-05-09 1.1 IVOA Data Model Working Group dm@ivoa.net Virtual observatory Metadata modeling 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. http://ivoa.net/documents/ObsCore/ Other Research 1.1 core-1.1 The TAP/ADQL table schema for ObsCore version 1.1 . Examples for TAPv1.0 ivo://ivoa.net/std/samp 2023-05-23T14:03:00Z Standard ivo_managed ivo://ivoa.net/std/samp IVOA Taylor, M. Boch, T. Fitzpatrick, M. Allan, A. Fay, J. Paioro, L. Taylor, J. Tody, D. 2012-04-11 1.3 Applications WG apps@ivoa.net Virtual observatory 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. http://ivoa.net/documents/SAMP/ Other Research 1.3 ivo://ivoa.net/std/obsloctap 2023-05-23T14:03:00Z Standard ivo_managed  ObsLocTAP ivo://ivoa.net/std/obsloctap IVOA Ibarra, Aitor Salgado, Jesús Ehle, Matthias Gabriel, Carlos Kretschmar, Peter Kuulkers, Erik Merín, Bruno Ness, Jan-Uwe Salazar, Emilio Saxton, Richard Cecconi, Baptiste Foster, Karl Demleitner, Markus Dempsey, James Molinaro, Marco Sánchez, Celia Taylor, Mark Trigo, María Díaz Kennea, Jaime Kettenis, Mark Matt, Giorgio Osborne, Julian de Oña Wilhelmi, Emma Salbol, Edward J. Sivakoff, Gregory Tao, Lian Tohuvavohu, Aaron Workman, Bill 2021-07-27 1.0 IVOA Data Model Working Group dm@ivoa.net virtual-observatories observatories The Observation Locator Table Access Protocol (ObsLocTAP) defines a data model for scheduled observations and a method to run queries over compliant data, using several Virtual Observatory technologies. The data model builds on the ObsCore data model, removing elements associated with dataset access that are not available during the planning phase. In this way, this standard is focused on access to metadata related to the planning of a certain observatory, more than on access to the scientific data products. Also, the data model will be focused on discovery of planned observations, which is very useful information for multi-wavelength coordination observations, re-planning information propagation, follow-up of Targets of Opportunity alerts, preparation of proposals, etc. As with ObsCore, a serialisation into a relational table is defined, which allows users to run complex queries using the IVOA Table Access Protocol. The document also prescribes how to register and discover ObsLocTAP services. http://ivoa.net/documents/ObsLocTAP/ Other Research 1.0 table-1.0 The table schema as defined by version 1.0 of the recommendation. ivo://ivoa.net/std/RM 2023-05-23T14:03:00Z Standard ivo_managed ivo://ivoa.net/std/RM IVOA Hanisch, R. 2007-03-02 1.12 IVOA Registry Working Group registry@ivoa.net Virtual observatory 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. http://www.ivoa.net/documents/latest/RM.html Other Research 1.12 ivo://ivoa.net/std/STC 2023-05-23T14:03:00Z Standard ivo_managed STC ivo://ivoa.net/std/STC International Virtual Observatory Alliance Arnold Rots 2011-11-20 1.33 Data Models Working Group dm@ivoa.net software standard virtual observatory data model coordinate system This document provides a complete design description of the Space-Time Coordinate (STC) metadata for the Virtual Observatory. It explains the various components, highlights some implementation considerations, presents a complete set of UML diagrams, and discusses the relation between STC and certain other parts of the Data Model. Two serializations are discussed: XML Schema (STC-X) and String (STC-S); the former is an integral part of this Recommendation. http://www.ivoa.net/Documents/latest/STC.html Other Research 1.33 http://www.ivoa.net/xml/STC/stc-v1.30.xsd the STC-X XML schema for serializing descriptions of space-time coordinates and coordinate systems. http://206-12-97-214.cloud.computecanada.ca/examples/ ivo://ivoa.net/std/SpectrumDM 2023-05-23T14:03:00Z Standard ivo_managed SpectrumDM ivo://ivoa.net/std/SpectrumDM International Virtual Observatory Alliance Jonathan McDowell Doug Tody Tamas Budavari Markus Dolensky Inga Kamp Kelly McCusker Pavlos Protopapas Arnold Rots Randy Thompson Frank Valdes Petr Skoda Bruno Rino Sebastien Derriere Jesus Salgado Omar Laurino 2011-11-20 1.1 Data Models Working Group dm@ivoa.net software standard virtual observatory data model We present a data model describing the structure of spectrophotometric datasets with spectral and temporal coordinates and associated metadata. This data model may be used to represent spectra, time series data, segments of SED (Spectral Energy Distributions) and other spectral or temporal associations. http://www.ivoa.net/Documents/SpectrumDM/ Other Research related-to Simple Spectral Access Protocol 1.1 http://www.ivoa.net/xml/Spectrum/Spectrum-1.01.xsd the recommended XML schema for serializing a spectral data model instance. http://206-12-97-214.cloud.computecanada.ca/examples/ ivo://ivoa.net/std/VODML 2023-05-23T14:03:00Z Standard ivo_managed ivo://ivoa.net/std/VODML IVOA Lemson, G. Laurino, O. Bourges, L. Cresitello-Dittmar, M. Demleitner, M. Donaldson, T. Dowler, P. Graham, M. Gray, N. Michel, L. Salgado, J. 2018-05-19 1.0 IVOA Data Models WG dm@ivoa.net Virtual observatory 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. http://ivoa.net/documents/VODML/ Other Research 1.0 ivo://ivoa.net/std/SIA 2023-05-23T14:03:00Z Standard ivo_managed SIA ivo://ivoa.net/std/SIA International Virtual Observatory Alliance Doug Tody Ray Plante 2004-05-24 1.0 Data Access Layer Working Group dal@ivoa.net software standard virtual observatory data access layer DAL The Simple Image Access (SIA) Protocol is a protocol for retrieving image data from a variety of astronomical image repositories through a uniform interface. The interface is meant to be reasonably simple to implement by service providers. A query defining a rectangular region on the sky is used to query for candidate images. The service returns a list of candidate images formatted as a VOTable. For each candidate image an access reference URL may be used to retrieve the image. Images may be returned in a variety of formats including FITS and various graphics formats. Referenced images are often computed on the fly, e.g., as cutouts from larger images. Note that the metadata used to describe an SIA service in the registry is defined in the SimpleDALRegExt standard (ivo://www.ivoa.net/std/SimpleDALRegExt; http://www.ivoa.net/Documents/SimpleDALRegExt/). http://www.ivoa.net/Documents/SIA/ Other Research related-to VOTable Format Definition related-to SimpleDALRegExt: Describing Simple Data Access Services 1.0 http://sample.org/cgi-bin/sia GET text/xml+votable POS Search Position in the form "ra,dec" where ra and dec are given in decimal degrees in the ICRS coordinate system. degrees real SIZE Size of search region in the RA and Dec. directions in decimal degrees. degrees real FORMAT Requested format of images. string INTERSECT Choice of intersection of matched images with the region of interest. string NAXIS The number of pixels desired along each axis integer CFRAME the coordinate frame to impose on the image. string EQUINOX the epoch of the mean equator and equinox for the specified coordinate system reference frame (CFRAME). coordinate frame to impose on the image. string CRPIX the pixel position to locate the reference position in the output image. real CRVAL the world coordinates of the reference position in the output image in decimal degrees real CDELT the scale of the output image in decimal degrees per pixel real ROTANG the rotation angle to put into the output image's coordinate system real PROJ the projection to impose in the construction of the output image string VERB the level of verbosity in the output. string ivo://ivoa.net/std/VOTable 2025-01-30T00:00:00Z Standard ivo_managed ivo://ivoa.net/std/VOTable IVOA Francois Ochsenbein Roy Williams Clive Davenhall Markus Demleitner Tom Donaldson Daniel Durand Pierre Fernique David Giaretta Robert Hanisch Tom McGlynn Alex Szalay Mark Taylor Andreas Wicenec 2025-01-30 2019-10-21 2013-09-20 2009-11-30 2004-08-11 1.5 Applications WG apps@ivoa.net virtual-observatories This document describes the structures making up the VOTable standard. The main part of this document describes the adopted part of the VOTable standard; it is followed by appendices presenting extensions which have been proposed and/or discussed, but which are not part of the standard. http://www.ivoa.net/documents/VOTable Other Research 1.5 http://www.ivoa.net/xml/VOTable/v1.3 VOTable is meant to serialize tabular documents in the context of Virtual Observatory applications. This schema corresponds to the VOTable document available from http://www.ivoa.net/Documents/latest/VOT.html ivo://ivoa.net/std/VOUnits 2023-05-23T14:03:00Z Standard ivo_managed VOUnits ivo://ivoa.net/std/VOUnits doi:10.5479/ADS/bib/2014ivoa.spec.0523D IVOA Derriere, S. Gray, N. Demleitner, M. Louys, M. Ochsenbein, F. 2014-05-23 1.0 IVOA Semantics WG semantics@ivoa.net Virtual observatory 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. http://ivoa.net/documents/VOUnits/ Other Research 1.0 ivo://ivoa.net/std/UCD 2023-05-23T14:03:00Z Standard ivo_managed UCD ivo://ivoa.net/std/UCD doi:10.5479/ADS/bib/2005ivoa.spec.0819D IVOA Derriere, S. Gray, N. Mann, R. Preite Martinez, A. McDowell, J. Mc Glynn, T. Ochsenbein, F. Osuna, P. Rixon, G. Williams, R. 2005-08-19 1.10 IVOA Semantics Working Group semantics@ivoa.net Virtual observatory Semantics This document describes the current understanding of the IVOA controlled vocabulary for describing astronomical data quantities, called Unified Content Descriptors (UCDs). The present document defines a new standard (named UCD1+) improving the first generation of UCDs (hereafter UCD1). The basic idea is to adopt a new syntax and vocabulary requiring little effort for people to adapt softwares already using UCD1. This document also addresses the questions of maintenance and evolution of the UCD1+. Examples of use cases within the VO, and tools for using UCD1+ are also described. http://www.ivoa.net/documents/latest/UCD.html Other Research 1.10