Last updated: 19 May 2010 - RayPlante
The standards for metadata used to describe resources in the VO come in two forms: prose documents that define the metadata concepts and XML Schemas used to encode them.
This document (euphemistically referred to as "RM") defines standard metadata concepts that describe resources, independent of any particular encoding format. It also describe the general resource model upon which the concepts are based.
This document is intended primarily for developers of new standards for encoding resource metadata.
This document defines a set of metadata that can be used to describe graphical images (e.g. JPEG, GIF, etc.) used for astronomy public outreach. It was developed via the IAU Virtual Astronomy Multimedia Project (VAMP) with input from the broader astronomical outreach community. The AstroVisualiztionMetadata page covers discussion of this document as a candidate IVOA standard.
VOResource in general refers to a set of XML Schemas that includes a core schema (VOResource-vX.X.xsd) based on the RM Recommendation and a set of standard extension schemas that define particular types of resources.
These schemas are intended for use by VO XML-based applications. In particular, these schemas are used for supporting interoperable communication with resource registries.
Formerly known as VOStandard, StandardsRegExt defines the extension schema for describing standards (along with concepts in those standards) so that they can be referred to via an IVOA identifier.
Formerly known as RegSimpleDAL, SimpleDALRegExt defines extension schemas for describing SIA (schema), SSA (schema), SLA (schema), and ConeSearch (schema). This document is under TCG review (see SimpleDALRegExt10RFC).
ApplicationsRegExt (formerly VOApplication) is a registry extension schema that allows one to register applications, tools, and libraries. A working draft of a document defining the extension schemas for describing applications is under development at RegDMApplications.
At the Fall 2009 Interop, the Registry Working Group agreed to table the development of this schema until a stronger driver emerges. Contributions and comments are still welcome; we are particularly interested in use cases that need the ability to dynamically discover applications. Discussion was revived again the spring and fall of 2011, and a similar conclusion was reached
Additional extensions are expected to be driven by other Working Groups as part of the development of new protocols. At the moment, extensions are in development for the following protocols:
For information about how to create a new registry extension, see the next section.
The VOResource has been designed to allow new metadata to be defined as an extension on the core. The VOResource specification recommends how to create extension schemas. Additional information about extending the VOResource schema can be found on the VOResource page.