Difference: ResourceMetadata (21 vs. 22)

Revision 222010-05-19 - RayPlante

 
META TOPICPARENT name="IvoaResReg"
Jumps: IvoaResReg :: registry mail archive :: VOResource :: VOResource
Changed:
<
<

Meetings: InterOpMay2008ResReg :: InterOpSep2007ResReg :: InterOpMay2007ResReg
>
>

Meetings: InterOpMay2010Reg :: InterOpNov2009Reg :: InterOpMay2008ResReg :: InterOpSep2007ResReg
 

Resource Metadata

Last updated: 19 June 2007 - RayPlante

Standard Specifications

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.

Metadata Definition Documents

Resource Metadata (RM)

IVOA Recommendation
"Resource Metadata for the Virtual Observatory" v1.01
Robert Hanisch, Ed.

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.

IVOA Working Draft
"Astronomy Visualization Metadata (AVM)" v1.1
Adrienne Gauthier, Editor.

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.

XML Schemas

VOResource

IVOA Recommendation
VOResource: an XML Encoding Schema for Resource Metadata (v1.03)
RayPlante, Editor. RFC completed Aug 2007.
Changed:
<
<
VOResource in general refers to a set of XML Schemas that includes a core schema (VOResource-v__X.X__.xsd) based on the RM Recommendation and a set of standard extension schemas that define particular types of resources.
>
>
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.

VODataService

Proposed Recommendation
VODataService: a VOResource extension for Data Collections and Services, v1.0 (Aurelien Stebe and Ray Plante, editors)
Changed:
<
<

VOStandard

>
>

StandardsRegExt (VOStandard)

 
Changed:
<
<
A working draft of a document defining the extension schemas for describing standards (including the ability to define IVORN-identifiable properties) is under development at VOStandard.
>
>
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. See StandardsRegExt for the latest information about this document and schema.
 

Simple Services (SCS, SIA, SSA)

Changed:
<
<
A working draft of a document defining the extension schemas for describing SIA (schema), SSA (schema), and ConeSearch (schema) is under development at RegSimpleDAL.
>
>
Formerly known as RegSimpleDAL, SimpleDALRegExt defines extension schemas for describing SIA (schema), SSA (schema), and ConeSearch (schema). This document is under development at SimpleDALRegExt.
 

VOApplication

Changed:
<
<
A working draft of a document defining the extension schemas for describing applications is under development at RegDMApplications.
>
>
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.
 
Added:
>
>
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.
 

Other Extensions in Development

Added:
>
>
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.

 

Creating Registry Extensions

Changed:
<
<
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, consult the VOResource page.
>
>
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.
 

Useful Links and Tools for Developers

  • Tools for converting VOResource v0.10 to v1.0 can be found at RegUpgradeToV10

Deprecated versions

<--  
-->
 
This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback