StandardsRegExt: Describing Standards for Registries

Note:

This standard is formerly known as VOStandard; discussion of the standard has moved here.

The version 1.0 registry data model uses Resource Identifiers in several places to identify which standard a particular resource follows (e.g. the capability element's standardID attribute). The Identifiers spec requires that any IVOA ID must have an entry in an IVOA registry; this implies that the standard itself is registered. Furthermore, there is an increasing interest to use IVOA identifiers to identify concepts and properties (e.g. VOSpace); the underlying identifier thus must be registered as well. The VOStandard data model and schema provides a framework in which IVOA standards can be described in the registry.

The goals of this extension are:

• allow support for an IVOA standard be recognized via an IVOA identifier (e.g. as in standardID)
• allow users to discover documentat about a standard protocol via the registry (in particular, via records of instances of the standard).
• allow one to define and use IVOA identifiers to identify a concept or property.

This document is approved for Recommendation.

Latest materials

• Recommendation on May 8, 2012
  • see results of RFC
  • The TCG review produced a proposal to add a <schema> element, resulting in the 17 Feb 2012 version; this change was subsequently approved by the TCG after posting to the registry list.
• schema document: StandardsRegExt-v1.0.xsd as of May 8, 2012

Samples

siastd.xml

This defines the SIA standard, defining its URI as ivo://ivoa.net/std/SIA. It enumerates the parameters that defines the standard SIA interface.

complang.xml

This defines a set of keys representing different computer languages. For example, the Python language can be identified via the URI, ivo://ivoa.net/std/application/languages#Python.

vospacestd.xml

This defines the VOSpace standard, defining terms mandated in the VOSpace specification like ivo://ivoa.net/vospace/core#httpget.

StandardsRegExt.xml

This defines the StandardsRegExt standard and includes the proposed <schema> element.

<-- 

 

 

 This requires the 17 Feb 2012 version of the schema   -->

Status

• Development of the spec document is managed via the volute google code repository. You can find it under trunk/projects/registry/StandardsRegExt
• This document is currently under Exec Review
• See also the RFC and TCG review

Summary of Changes

since v1.0

see Changes section of releases of documentation.

since v0.4

• The name was changed from VOStandard to StandardsRegExt

since v0.3

• The spec document text was completed
• Added deprecated attribute to endorsedVersion element
• Added deprecated element

Discussion

Historical materials

This work used to be traced via the VOStandards page. That page is now deprecated. Attatchments to that page include:

• VOStandard-v0.3wd.html
• VOStandard-v0.4wd.xsd
• VOStandard-v0.4wd.html
• WD-VOStandard-1.0-20100514.html

(RayPlante - 19 May 2010)

This work used to be tracked via the RegDMStandards page. That page is now deprecated. (RayPlante - 10 Nov 2009)

The previous version of the schema was distributed as part of the RegUpgradeToV10 page

-- PaulHarrison - 25 Apr 2007

StandardsRegExt: Describing Standards for Registries

Note:

This standard is formerly known as VOStandard; discussion of the standard has moved here.

The version 1.0 registry data model uses Resource Identifiers in several places to identify which standard a particular resource follows (e.g. the capability element's standardID attribute). The Identifiers spec requires that any IVOA ID must have an entry in an IVOA registry; this implies that the standard itself is registered. Furthermore, there is an increasing interest to use IVOA identifiers to identify concepts and properties (e.g. VOSpace); the underlying identifier thus must be registered as well. The VOStandard data model and schema provides a framework in which IVOA standards can be described in the registry.

The goals of this extension are:

• allow support for an IVOA standard be recognized via an IVOA identifier (e.g. as in standardID)
• allow users to discover documentat about a standard protocol via the registry (in particular, via records of instances of the standard).
• allow one to define and use IVOA identifiers to identify a concept or property.

Latest materials

• • see results of RFC
  • The TCG review produced a proposal to add a <schema> element, resulting in the 17 Feb 2012 version; this change was subsequently approved by the TCG after posting to the registry list.

Samples

siastd.xml

This defines the SIA standard, defining its URI as ivo://ivoa.net/std/SIA. It enumerates the parameters that defines the standard SIA interface.

complang.xml

This defines a set of keys representing different computer languages. For example, the Python language can be identified via the URI, ivo://ivoa.net/std/application/languages#Python.

vospacestd.xml

This defines the VOSpace standard, defining terms mandated in the VOSpace specification like ivo://ivoa.net/vospace/core#httpget.

StandardsRegExt.xml

This defines the StandardsRegExt standard and includes the proposed <schema> element.

<-- 

 

 

 This requires the 17 Feb 2012 version of the schema   -->

Status

• Development of the spec document is managed via the volute google code repository. You can find it under trunk/projects/registry/StandardsRegExt
• This document is currently under Exec Review
• See also the RFC and TCG review

Summary of Changes

since v1.0

see Changes section of releases of documentation.

since v0.4

• The name was changed from VOStandard to StandardsRegExt

since v0.3

• The spec document text was completed
• Added deprecated attribute to endorsedVersion element
• Added deprecated element

Discussion

Historical materials

This work used to be traced via the VOStandards page. That page is now deprecated. Attatchments to that page include:

• VOStandard-v0.3wd.html
• VOStandard-v0.4wd.xsd
• VOStandard-v0.4wd.html
• WD-VOStandard-1.0-20100514.html

(RayPlante - 19 May 2010)

This work used to be tracked via the RegDMStandards page. That page is now deprecated. (RayPlante - 10 Nov 2009)

The previous version of the schema was distributed as part of the RegUpgradeToV10 page

• VOStandard-v0.1.xsd

-- PaulHarrison - 25 Apr 2007

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

StandardsRegExt: Describing Standards for Registries

Note:

This standard is formerly known as VOStandard; discussion of the standard has moved here.

The version 1.0 registry data model uses Resource Identifiers in several places to identify which standard a particular resource follows (e.g. the capability element's standardID attribute). The Identifiers spec requires that any IVOA ID must have an entry in an IVOA registry; this implies that the standard itself is registered. Furthermore, there is an increasing interest to use IVOA identifiers to identify concepts and properties (e.g. VOSpace); the underlying identifier thus must be registered as well. The VOStandard data model and schema provides a framework in which IVOA standards can be described in the registry.

The goals of this extension are:

• allow support for an IVOA standard be recognized via an IVOA identifier (e.g. as in standardID)
• allow users to discover documentat about a standard protocol via the registry (in particular, via records of instances of the standard).
• allow one to define and use IVOA identifiers to identify a concept or property.

This document is currently under TCG review.

Latest materials

<-- 

 Working Draft StandardsRegExt document
 
 StandardsRegExt-v1.0wd0.xsd
 
-->

Samples

siastd.xml

This defines the SIA standard, defining its URI as ivo://ivoa.net/std/SIA. It enumerates the parameters that defines the standard SIA interface.

complang.xml

This defines a set of keys representing different computer languages. For example, the Python language can be identified via the URI, ivo://ivoa.net/std/application/languages#Python.

vospacestd.xml

This defines the VOSpace standard, defining terms mandated in the VOSpace specification like ivo://ivoa.net/vospace/core#httpget.

StandardsRegExt.xml

This defines the StandardsRegExt standard and includes the proposed <schema> element.

Status

• Development of the spec document is managed via the volute google code repository. You can find it under trunk/projects/registry/StandardsRegExt

Summary of Changes

since v1.0

see Changes section of releases of documentation.

since v0.4

• The name was changed from VOStandard to StandardsRegExt

since v0.3

• The spec document text was completed
• Added deprecated attribute to endorsedVersion element
• Added deprecated element

Discussion

Historical materials

This work used to be traced via the VOStandards page. That page is now deprecated. Attatchments to that page include:

• VOStandard-v0.3wd.html
• VOStandard-v0.4wd.xsd
• VOStandard-v0.4wd.html
• WD-VOStandard-1.0-20100514.html

(RayPlante - 19 May 2010)

This work used to be tracked via the RegDMStandards page. That page is now deprecated. (RayPlante - 10 Nov 2009)

The previous version of the schema was distributed as part of the RegUpgradeToV10 page

• VOStandard-v0.1.xsd

-- PaulHarrison - 25 Apr 2007

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

StandardsRegExt: Describing Standards for Registries

Note:

This standard is formerly known as VOStandard; discussion of the standard has moved here.

The version 1.0 registry data model uses Resource Identifiers in several places to identify which standard a particular resource follows (e.g. the capability element's standardID attribute). The Identifiers spec requires that any IVOA ID must have an entry in an IVOA registry; this implies that the standard itself is registered. Furthermore, there is an increasing interest to use IVOA identifiers to identify concepts and properties (e.g. VOSpace); the underlying identifier thus must be registered as well. The VOStandard data model and schema provides a framework in which IVOA standards can be described in the registry.

The goals of this extension are:

• allow support for an IVOA standard be recognized via an IVOA identifier (e.g. as in standardID)
• allow users to discover documentat about a standard protocol via the registry (in particular, via records of instances of the standard).
• allow one to define and use IVOA identifiers to identify a concept or property.

This document is currently under TCG review.

Latest materials

<-- 

 Working Draft StandardsRegExt document
 
 StandardsRegExt-v1.0wd0.xsd
 
-->

• Proposed Recommendation now under RFC
• internal, Post-RFC versions (containing updates; candidates for next PR version)
  • 13 Feb 2012: updated based on TCG review
  • 17 Feb 2012: adds <schema> element.
• schema document
  • StandardsRegExt-v1.0pr2.xsd
  • StandardsRegExt-v1.0pr3.xsd (includes <schema> element)

<-- 

 StandardsRegExt-v1.0pr0.xsd  -->

Samples

siastd.xml

This defines the SIA standard, defining its URI as ivo://ivoa.net/std/SIA. It enumerates the parameters that defines the standard SIA interface.

complang.xml

This defines a set of keys representing different computer languages. For example, the Python language can be identified via the URI, ivo://ivoa.net/std/application/languages#Python.

vospacestd.xml

This defines the VOSpace standard, defining terms mandated in the VOSpace specification like ivo://ivoa.net/vospace/core#httpget.

StandardsRegExt.xml

This defines the StandardsRegExt standard and includes the proposed <schema> element.

• This requires the 17 Feb 2012 version of the schema

Status

• Development of the spec document is managed via the volute google code repository. You can find it under trunk/projects/registry/StandardsRegExt
• This document is currently under TCG review

Summary of Changes

since v1.0

see Changes section of releases of documentation.

since v0.4

• The name was changed from VOStandard to StandardsRegExt

since v0.3

• The spec document text was completed
• Added deprecated attribute to endorsedVersion element
• Added deprecated element

Discussion

Historical materials

This work used to be traced via the VOStandards page. That page is now deprecated. Attatchments to that page include:

• VOStandard-v0.3wd.html
• VOStandard-v0.4wd.xsd
• VOStandard-v0.4wd.html
• WD-VOStandard-1.0-20100514.html

(RayPlante - 19 May 2010)

This work used to be tracked via the RegDMStandards page. That page is now deprecated. (RayPlante - 10 Nov 2009)

The previous version of the schema was distributed as part of the RegUpgradeToV10 page

• VOStandard-v0.1.xsd

-- PaulHarrison - 25 Apr 2007

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

StandardsRegExt: Describing Standards for Registries

Note:

This standard is formerly known as VOStandard; discussion of the standard has moved here.

The version 1.0 registry data model uses Resource Identifiers in several places to identify which standard a particular resource follows (e.g. the capability element's standardID attribute). The Identifiers spec requires that any IVOA ID must have an entry in an IVOA registry; this implies that the standard itself is registered. Furthermore, there is an increasing interest to use IVOA identifiers to identify concepts and properties (e.g. VOSpace); the underlying identifier thus must be registered as well. The VOStandard data model and schema provides a framework in which IVOA standards can be described in the registry.

The goals of this extension are:

• allow support for an IVOA standard be recognized via an IVOA identifier (e.g. as in standardID)
• allow users to discover documentat about a standard protocol via the registry (in particular, via records of instances of the standard).
• allow one to define and use IVOA identifiers to identify a concept or property.

This document is currently under TCG review.

Latest materials

<-- 

 Working Draft StandardsRegExt document
 
 StandardsRegExt-v1.0wd0.xsd
 
-->

• Proposed Recommendation now under RFC

<-- 

 StandardsRegExt-v1.0pr0.xsd  -->

Samples

siastd.xml

This defines the SIA standard, defining its URI as ivo://ivoa.net/std/SIA. It enumerates the parameters that defines the standard SIA interface.

complang.xml

This defines a set of keys representing different computer languages. For example, the Python language can be identified via the URI, ivo://ivoa.net/std/application/languages#Python.

vospacestd.xml

This defines the VOSpace standard, defining terms mandated in the VOSpace specification like ivo://ivoa.net/vospace/core#httpget.

Status

• Development of the spec document is managed via the volute google code repository. You can find it under trunk/projects/registry/StandardsRegExt
• This document is currently under TCG review

Summary of Changes

since v0.4

• The name was changed from VOStandard to StandardsRegExt

since v0.3

• The spec document text was completed
• Added deprecated attribute to endorsedVersion element
• Added deprecated element

Discussion

Historical materials

This work used to be traced via the VOStandards page. That page is now deprecated. Attatchments to that page include:

• VOStandard-v0.3wd.html
• VOStandard-v0.4wd.xsd
• VOStandard-v0.4wd.html
• WD-VOStandard-1.0-20100514.html

(RayPlante - 19 May 2010)

This work used to be tracked via the RegDMStandards page. That page is now deprecated. (RayPlante - 10 Nov 2009)

The previous version of the schema was distributed as part of the RegUpgradeToV10 page

• VOStandard-v0.1.xsd

-- PaulHarrison - 25 Apr 2007

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

StandardsRegExt: Describing Standards for Registries

Note:

This standard is formerly known as VOStandard; discussion of the standard has moved here.

The version 1.0 registry data model uses Resource Identifiers in several places to identify which standard a particular resource follows (e.g. the capability element's standardID attribute). The Identifiers spec requires that any IVOA ID must have an entry in an IVOA registry; this implies that the standard itself is registered. Furthermore, there is an increasing interest to use IVOA identifiers to identify concepts and properties (e.g. VOSpace); the underlying identifier thus must be registered as well. The VOStandard data model and schema provides a framework in which IVOA standards can be described in the registry.

The goals of this extension are:

• allow support for an IVOA standard be recognized via an IVOA identifier (e.g. as in standardID)
• allow users to discover documentat about a standard protocol via the registry (in particular, via records of instances of the standard).
• allow one to define and use IVOA identifiers to identify a concept or property.

This document is currently under TCG review.

Latest materials

<-- 

 Working Draft StandardsRegExt document
 
 StandardsRegExt-v1.0wd0.xsd
 
-->

• Proposed Recommendation now under RFC
• internal, Post-RFC version (containing updates; candidate for next PR version)
  • 13 Feb 2012: updated based on TCG review
• StandardsRegExt-v1.0pr1.xsd

<-- 

 StandardsRegExt-v1.0pr0.xsd  -->

Samples

siastd.xml

This defines the SIA standard, defining its URI as ivo://ivoa.net/std/SIA. It enumerates the parameters that defines the standard SIA interface.

complang.xml

This defines a set of keys representing different computer languages. For example, the Python language can be identified via the URI, ivo://ivoa.net/std/application/languages#Python.

vospacestd.xml

This defines the VOSpace standard, defining terms mandated in the VOSpace specification like ivo://ivoa.net/vospace/core#httpget.

Status

• Development of the spec document is managed via the volute google code repository. You can find it under trunk/projects/registry/StandardsRegExt
• This document is currently under TCG review

Summary of Changes

since v0.4

• The name was changed from VOStandard to StandardsRegExt

since v0.3

• The spec document text was completed
• Added deprecated attribute to endorsedVersion element
• Added deprecated element

Discussion

Historical materials

This work used to be traced via the VOStandards page. That page is now deprecated. Attatchments to that page include:

• VOStandard-v0.3wd.html
• VOStandard-v0.4wd.xsd
• VOStandard-v0.4wd.html
• WD-VOStandard-1.0-20100514.html

(RayPlante - 19 May 2010)

This work used to be tracked via the RegDMStandards page. That page is now deprecated. (RayPlante - 10 Nov 2009)

The previous version of the schema was distributed as part of the RegUpgradeToV10 page

• VOStandard-v0.1.xsd

-- PaulHarrison - 25 Apr 2007

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

StandardsRegExt: Describing Standards for Registries

Note:

This standard is formerly known as VOStandard; discussion of the standard has moved here.

The version 1.0 registry data model uses Resource Identifiers in several places to identify which standard a particular resource follows (e.g. the capability element's standardID attribute). The Identifiers spec requires that any IVOA ID must have an entry in an IVOA registry; this implies that the standard itself is registered. Furthermore, there is an increasing interest to use IVOA identifiers to identify concepts and properties (e.g. VOSpace); the underlying identifier thus must be registered as well. The VOStandard data model and schema provides a framework in which IVOA standards can be described in the registry.

The goals of this extension are:

• allow support for an IVOA standard be recognized via an IVOA identifier (e.g. as in standardID)
• allow users to discover documentat about a standard protocol via the registry (in particular, via records of instances of the standard).
• allow one to define and use IVOA identifiers to identify a concept or property.

This document is currently under TCG review.

Latest materials

<-- 

 Working Draft StandardsRegExt document
 
 StandardsRegExt-v1.0wd0.xsd
 
-->

• Proposed Recommendation now under RFC
• internal, Post-RFC version (containing updates; candidate for next PR version)

• StandardsRegExt-v1.0pr1.xsd

<-- 

 StandardsRegExt-v1.0pr0.xsd  -->

Samples

siastd.xml

This defines the SIA standard, defining its URI as ivo://ivoa.net/std/SIA. It enumerates the parameters that defines the standard SIA interface.

complang.xml

This defines a set of keys representing different computer languages. For example, the Python language can be identified via the URI, ivo://ivoa.net/std/application/languages#Python.

vospacestd.xml

This defines the VOSpace standard, defining terms mandated in the VOSpace specification like ivo://ivoa.net/vospace/core#httpget.

Status

• Development of the spec document is managed via the volute google code repository. You can find it under trunk/projects/registry/StandardsRegExt
• This document is currently under TCG review

Summary of Changes

since v0.4

• The name was changed from VOStandard to StandardsRegExt

since v0.3

• The spec document text was completed
• Added deprecated attribute to endorsedVersion element
• Added deprecated element

Discussion

Historical materials

This work used to be traced via the VOStandards page. That page is now deprecated. Attatchments to that page include:

• VOStandard-v0.3wd.html
• VOStandard-v0.4wd.xsd
• VOStandard-v0.4wd.html
• WD-VOStandard-1.0-20100514.html

(RayPlante - 19 May 2010)

This work used to be tracked via the RegDMStandards page. That page is now deprecated. (RayPlante - 10 Nov 2009)

The previous version of the schema was distributed as part of the RegUpgradeToV10 page

• VOStandard-v0.1.xsd

-- PaulHarrison - 25 Apr 2007

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

StandardsRegExt: Describing Standards for Registries

Note:

This standard is formerly known as VOStandard; discussion of the standard has moved here.

The version 1.0 registry data model uses Resource Identifiers in several places to identify which standard a particular resource follows (e.g. the capability element's standardID attribute). The Identifiers spec requires that any IVOA ID must have an entry in an IVOA registry; this implies that the standard itself is registered. Furthermore, there is an increasing interest to use IVOA identifiers to identify concepts and properties (e.g. VOSpace); the underlying identifier thus must be registered as well. The VOStandard data model and schema provides a framework in which IVOA standards can be described in the registry.

The goals of this extension are:

• allow support for an IVOA standard be recognized via an IVOA identifier (e.g. as in standardID)
• allow users to discover documentat about a standard protocol via the registry (in particular, via records of instances of the standard).
• allow one to define and use IVOA identifiers to identify a concept or property.

This document is currently under TCG review.

Latest materials

<-- 

 Working Draft StandardsRegExt document
 
 StandardsRegExt-v1.0wd0.xsd
 
-->

• Proposed Recommendation now under RFC

• • 17 Oct 2011: updated based on TCG review

Samples

siastd.xml

This defines the SIA standard, defining its URI as ivo://ivoa.net/std/SIA. It enumerates the parameters that defines the standard SIA interface.

complang.xml

This defines a set of keys representing different computer languages. For example, the Python language can be identified via the URI, ivo://ivoa.net/std/application/languages#Python.

vospacestd.xml

This defines the VOSpace standard, defining terms mandated in the VOSpace specification like ivo://ivoa.net/vospace/core#httpget.

Status

• Development of the spec document is managed via the volute google code repository. You can find it under trunk/projects/registry/StandardsRegExt
• This document is currently under TCG review

Summary of Changes

since v0.4

• The name was changed from VOStandard to StandardsRegExt

since v0.3

• The spec document text was completed
• Added deprecated attribute to endorsedVersion element
• Added deprecated element

Discussion

Historical materials

This work used to be traced via the VOStandards page. That page is now deprecated. Attatchments to that page include:

• VOStandard-v0.3wd.html
• VOStandard-v0.4wd.xsd
• VOStandard-v0.4wd.html
• WD-VOStandard-1.0-20100514.html

(RayPlante - 19 May 2010)

This work used to be tracked via the RegDMStandards page. That page is now deprecated. (RayPlante - 10 Nov 2009)

The previous version of the schema was distributed as part of the RegUpgradeToV10 page

• VOStandard-v0.1.xsd

-- PaulHarrison - 25 Apr 2007

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

StandardsRegExt: Describing Standards for Registries

Note:

This standard is formerly known as VOStandard; discussion of the standard has moved here.

The version 1.0 registry data model uses Resource Identifiers in several places to identify which standard a particular resource follows (e.g. the capability element's standardID attribute). The Identifiers spec requires that any IVOA ID must have an entry in an IVOA registry; this implies that the standard itself is registered. Furthermore, there is an increasing interest to use IVOA identifiers to identify concepts and properties (e.g. VOSpace); the underlying identifier thus must be registered as well. The VOStandard data model and schema provides a framework in which IVOA standards can be described in the registry.

The goals of this extension are:

• allow support for an IVOA standard be recognized via an IVOA identifier (e.g. as in standardID)
• allow users to discover documentat about a standard protocol via the registry (in particular, via records of instances of the standard).
• allow one to define and use IVOA identifiers to identify a concept or property.

This document is currently under TCG review.

Latest materials

<-- 

 Working Draft StandardsRegExt document
 
 StandardsRegExt-v1.0wd0.xsd
 
-->

• Proposed Recommendation now under RFC
• internal, Post-RFC version (containing updates; candidate for next PR version)
  • 17 Oct 2011: updated based on TCG review
• StandardsRegExt-v1.0pr0.xsd

Samples

siastd.xml

This defines the SIA standard, defining its URI as ivo://ivoa.net/std/SIA. It enumerates the parameters that defines the standard SIA interface.

complang.xml

This defines a set of keys representing different computer languages. For example, the Python language can be identified via the URI, ivo://ivoa.net/std/application/languages#Python.

vospacestd.xml

This defines the VOSpace standard, defining terms mandated in the VOSpace specification like ivo://ivoa.net/vospace/core#httpget.

Status

• Development of the spec document is managed via the volute google code repository. You can find it under trunk/projects/registry/StandardsRegExt
• This document is currently under TCG review

Summary of Changes

since v0.4

• The name was changed from VOStandard to StandardsRegExt

since v0.3

• The spec document text was completed
• Added deprecated attribute to endorsedVersion element
• Added deprecated element

Discussion

Historical materials

This work used to be traced via the VOStandards page. That page is now deprecated. Attatchments to that page include:

• VOStandard-v0.3wd.html
• VOStandard-v0.4wd.xsd
• VOStandard-v0.4wd.html
• WD-VOStandard-1.0-20100514.html

(RayPlante - 19 May 2010)

This work used to be tracked via the RegDMStandards page. That page is now deprecated. (RayPlante - 10 Nov 2009)

The previous version of the schema was distributed as part of the RegUpgradeToV10 page

• VOStandard-v0.1.xsd

-- PaulHarrison - 25 Apr 2007

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

StandardsRegExt: Describing Standards for Registries

Note:

This standard is formerly known as VOStandard; discussion of the standard has moved here.

The version 1.0 registry data model uses Resource Identifiers in several places to identify which standard a particular resource follows (e.g. the capability element's standardID attribute). The Identifiers spec requires that any IVOA ID must have an entry in an IVOA registry; this implies that the standard itself is registered. Furthermore, there is an increasing interest to use IVOA identifiers to identify concepts and properties (e.g. VOSpace); the underlying identifier thus must be registered as well. The VOStandard data model and schema provides a framework in which IVOA standards can be described in the registry.

The goals of this extension are:

• allow support for an IVOA standard be recognized via an IVOA identifier (e.g. as in standardID)
• allow users to discover documentat about a standard protocol via the registry (in particular, via records of instances of the standard).
• allow one to define and use IVOA identifiers to identify a concept or property.

This document is currently under TCG review.

Latest materials

<-- 

 Working Draft StandardsRegExt document
 
 StandardsRegExt-v1.0wd0.xsd
 
-->

• Proposed Recommendation now under RFC
• internal, Post-RFC version (containing updates; candidate for next PR version)
  • 17 Oct 2011: updated based on TCG review
• StandardsRegExt-v1.0pr0.xsd

Samples

siastd.xml

This defines the SIA standard, defining its URI as ivo://ivoa.net/std/SIA. It enumerates the parameters that defines the standard SIA interface.

complang.xml

This defines a set of keys representing different computer languages. For example, the Python language can be identified via the URI, ivo://ivoa.net/std/application/languages#Python.

vospacestd.xml

This defines the VOSpace standard, defining terms mandated in the VOSpace specification like ivo://ivoa.net/vospace/core#httpget.

Status

• Development of the spec document is managed via the volute google code repository. You can find it under trunk/projects/registry/StandardsRegExt
• This document is currently under TCG review

Summary of Changes

since v0.4

• The name was changed from VOStandard to StandardsRegExt

since v0.3

• The spec document text was completed
• Added deprecated attribute to endorsedVersion element
• Added deprecated element

Discussion

Historical materials

This work used to be traced via the VOStandards page. That page is now deprecated. Attatchments to that page include:

• VOStandard-v0.3wd.html
• VOStandard-v0.4wd.xsd
• VOStandard-v0.4wd.html
• WD-VOStandard-1.0-20100514.html

(RayPlante - 19 May 2010)

This work used to be tracked via the RegDMStandards page. That page is now deprecated. (RayPlante - 10 Nov 2009)

The previous version of the schema was distributed as part of the RegUpgradeToV10 page

• VOStandard-v0.1.xsd

-- PaulHarrison - 25 Apr 2007

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

StandardsRegExt: Describing Standards for Registries

Note:

This standard is formerly known as VOStandard; discussion of the standard has moved here.

The version 1.0 registry data model uses Resource Identifiers in several places to identify which standard a particular resource follows (e.g. the capability element's standardID attribute). The Identifiers spec requires that any IVOA ID must have an entry in an IVOA registry; this implies that the standard itself is registered. Furthermore, there is an increasing interest to use IVOA identifiers to identify concepts and properties (e.g. VOSpace); the underlying identifier thus must be registered as well. The VOStandard data model and schema provides a framework in which IVOA standards can be described in the registry.

The goals of this extension are:

• allow support for an IVOA standard be recognized via an IVOA identifier (e.g. as in standardID)
• allow users to discover documentat about a standard protocol via the registry (in particular, via records of instances of the standard).
• allow one to define and use IVOA identifiers to identify a concept or property.

Latest materials

<-- 

 Working Draft StandardsRegExt document
 
 StandardsRegExt-v1.0wd0.xsd
 
-->

• Proposed Recommendation now under RFC
• internal, Post-RFC version (containing updates; candidate for next PR version)

• StandardsRegExt-v1.0pr0.xsd

Samples

siastd.xml

This defines the SIA standard, defining its URI as ivo://ivoa.net/std/SIA. It enumerates the parameters that defines the standard SIA interface.

complang.xml

This defines a set of keys representing different computer languages. For example, the Python language can be identified via the URI, ivo://ivoa.net/std/application/languages#Python.

vospacestd.xml

This defines the VOSpace standard, defining terms mandated in the VOSpace specification like ivo://ivoa.net/vospace/core#httpget.

Status

• Development of the spec document is managed via the volute google code repository. You can find it under trunk/projects/registry/StandardsRegExt

Summary of Changes

since v0.4

• The name was changed from VOStandard to StandardsRegExt

since v0.3

• The spec document text was completed
• Added deprecated attribute to endorsedVersion element
• Added deprecated element

Discussion

Historical materials

This work used to be traced via the VOStandards page. That page is now deprecated. Attatchments to that page include:

• VOStandard-v0.3wd.html
• VOStandard-v0.4wd.xsd
• VOStandard-v0.4wd.html
• WD-VOStandard-1.0-20100514.html

(RayPlante - 19 May 2010)

This work used to be tracked via the RegDMStandards page. That page is now deprecated. (RayPlante - 10 Nov 2009)

The previous version of the schema was distributed as part of the RegUpgradeToV10 page

• VOStandard-v0.1.xsd

-- PaulHarrison - 25 Apr 2007

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

StandardsRegExt: Describing Standards for Registries

Note:

This standard is formerly known as VOStandard; discussion of the standard has moved here.

The version 1.0 registry data model uses Resource Identifiers in several places to identify which standard a particular resource follows (e.g. the capability element's standardID attribute). The Identifiers spec requires that any IVOA ID must have an entry in an IVOA registry; this implies that the standard itself is registered. Furthermore, there is an increasing interest to use IVOA identifiers to identify concepts and properties (e.g. VOSpace); the underlying identifier thus must be registered as well. The VOStandard data model and schema provides a framework in which IVOA standards can be described in the registry.

The goals of this extension are:

• allow support for an IVOA standard be recognized via an IVOA identifier (e.g. as in standardID)
• allow users to discover documentat about a standard protocol via the registry (in particular, via records of instances of the standard).
• allow one to define and use IVOA identifiers to identify a concept or property.

Latest materials

<-- 

 Working Draft StandardsRegExt document
 
 StandardsRegExt-v1.0wd0.xsd
 
-->

• Proposed Recommendation now under RFC
• internal, Post-RFC version (containing updates; candidate for next PR version)
• StandardsRegExt-v1.0pr0.xsd

Samples

siastd.xml

This defines the SIA standard, defining its URI as ivo://ivoa.net/std/SIA. It enumerates the parameters that defines the standard SIA interface.

complang.xml

This defines a set of keys representing different computer languages. For example, the Python language can be identified via the URI, ivo://ivoa.net/std/application/languages#Python.

vospacestd.xml

This defines the VOSpace standard, defining terms mandated in the VOSpace specification like ivo://ivoa.net/vospace/core#httpget.

Status

• Development of the spec document is managed via the volute google code repository. You can find it under trunk/projects/registry/StandardsRegExt

Summary of Changes

since v0.4

• The name was changed from VOStandard to StandardsRegExt

since v0.3

• The spec document text was completed
• Added deprecated attribute to endorsedVersion element
• Added deprecated element

Discussion

Historical materials

This work used to be traced via the VOStandards page. That page is now deprecated. Attatchments to that page include:

• VOStandard-v0.3wd.html
• VOStandard-v0.4wd.xsd
• VOStandard-v0.4wd.html
• WD-VOStandard-1.0-20100514.html

(RayPlante - 19 May 2010)

This work used to be tracked via the RegDMStandards page. That page is now deprecated. (RayPlante - 10 Nov 2009)

The previous version of the schema was distributed as part of the RegUpgradeToV10 page

• VOStandard-v0.1.xsd

-- PaulHarrison - 25 Apr 2007

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

StandardsRegExt: Describing Standards for Registries

Note:

This standard is formerly known as VOStandard; discussion of the standard has moved here.

The version 1.0 registry data model uses Resource Identifiers in several places to identify which standard a particular resource follows (e.g. the capability element's standardID attribute). The Identifiers spec requires that any IVOA ID must have an entry in an IVOA registry; this implies that the standard itself is registered. Furthermore, there is an increasing interest to use IVOA identifiers to identify concepts and properties (e.g. VOSpace); the underlying identifier thus must be registered as well. The VOStandard data model and schema provides a framework in which IVOA standards can be described in the registry.

The goals of this extension are:

• allow support for an IVOA standard be recognized via an IVOA identifier (e.g. as in standardID)
• allow users to discover documentat about a standard protocol via the registry (in particular, via records of instances of the standard).
• allow one to define and use IVOA identifiers to identify a concept or property.

Latest materials

<-- 

 Working Draft StandardsRegExt document
 
 StandardsRegExt-v1.0wd0.xsd
 
-->

• internal, Post-RFC version (containing updates; candidate for next PR version)
• StandardsRegExt-v1.0pr0.xsd

Samples

siastd.xml

This defines the SIA standard, defining its URI as ivo://ivoa.net/std/SIA. It enumerates the parameters that defines the standard SIA interface.

complang.xml

This defines a set of keys representing different computer languages. For example, the Python language can be identified via the URI, ivo://ivoa.net/std/application/languages#Python.

vospacestd.xml

This defines the VOSpace standard, defining terms mandated in the VOSpace specification like ivo://ivoa.net/vospace/core#httpget.

Status

• Development of the spec document is managed via the volute google code repository. You can find it under trunk/projects/registry/StandardsRegExt

Summary of Changes

since v0.4

• The name was changed from VOStandard to StandardsRegExt

since v0.3

• The spec document text was completed
• Added deprecated attribute to endorsedVersion element
• Added deprecated element

Discussion

Historical materials

This work used to be traced via the VOStandards page. That page is now deprecated. Attatchments to that page include:

• VOStandard-v0.3wd.html
• VOStandard-v0.4wd.xsd
• VOStandard-v0.4wd.html
• WD-VOStandard-1.0-20100514.html

(RayPlante - 19 May 2010)

This work used to be tracked via the RegDMStandards page. That page is now deprecated. (RayPlante - 10 Nov 2009)

The previous version of the schema was distributed as part of the RegUpgradeToV10 page

• VOStandard-v0.1.xsd

-- PaulHarrison - 25 Apr 2007

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

StandardsRegExt: Describing Standards for Registries

Note:

This standard is formerly known as VOStandard; discussion of the standard has moved here.

The version 1.0 registry data model uses Resource Identifiers in several places to identify which standard a particular resource follows (e.g. the capability element's standardID attribute). The Identifiers spec requires that any IVOA ID must have an entry in an IVOA registry; this implies that the standard itself is registered. Furthermore, there is an increasing interest to use IVOA identifiers to identify concepts and properties (e.g. VOSpace); the underlying identifier thus must be registered as well. The VOStandard data model and schema provides a framework in which IVOA standards can be described in the registry.

The goals of this extension are:

• allow support for an IVOA standard be recognized via an IVOA identifier (e.g. as in standardID)
• allow users to discover documentat about a standard protocol via the registry (in particular, via records of instances of the standard).
• allow one to define and use IVOA identifiers to identify a concept or property.

Latest materials

<-- 

 Working Draft StandardsRegExt document
 
 StandardsRegExt-v1.0wd0.xsd
 
-->

Samples

siastd.xml

This defines the SIA standard, defining its URI as ivo://ivoa.net/std/SIA. It enumerates the parameters that defines the standard SIA interface.

complang.xml

This defines a set of keys representing different computer languages. For example, the Python language can be identified via the URI, ivo://ivoa.net/std/application/languages#Python.

vospacestd.xml

This defines the VOSpace standard, defining terms mandated in the VOSpace specification like ivo://ivoa.net/vospace/core#httpget.

Status

• Development of the spec document is managed via the volute google code repository. You can find it under trunk/projects/registry/StandardsRegExt

Summary of Changes

since v0.4

• The name was changed from VOStandard to StandardsRegExt

since v0.3

• The spec document text was completed
• Added deprecated attribute to endorsedVersion element
• Added deprecated element

Discussion

Historical materials

This work used to be traced via the VOStandards page. That page is now deprecated. Attatchments to that page include:

• VOStandard-v0.3wd.html
• VOStandard-v0.4wd.xsd
• VOStandard-v0.4wd.html
• WD-VOStandard-1.0-20100514.html

(RayPlante - 19 May 2010)

This work used to be tracked via the RegDMStandards page. That page is now deprecated. (RayPlante - 10 Nov 2009)

The previous version of the schema was distributed as part of the RegUpgradeToV10 page

• VOStandard-v0.1.xsd

-- PaulHarrison - 25 Apr 2007

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

StandardsRegExt: Describing Standards for Registries

Note:

This standard is formerly known as VOStandard; discussion of the standard has moved here.

The version 1.0 registry data model uses Resource Identifiers in several places to identify which standard a particular resource follows (e.g. the capability element's standardID attribute). The Identifiers spec requires that any IVOA ID must have an entry in an IVOA registry; this implies that the standard itself is registered. Furthermore, there is an increasing interest to use IVOA identifiers to identify concepts and properties (e.g. VOSpace); the underlying identifier thus must be registered as well. The VOStandard data model and schema provides a framework in which IVOA standards can be described in the registry.

The goals of this extension are:

• allow support for an IVOA standard be recognized via an IVOA identifier (e.g. as in standardID)
• allow users to discover documentat about a standard protocol via the registry (in particular, via records of instances of the standard).
• allow one to define and use IVOA identifiers to identify a concept or property.

Latest materials

<-- 

 Working Draft StandardsRegExt document
 
 StandardsRegExt-v1.0wd0.xsd
 
-->

• PR-StandardsRegExt-1.0-20110316.html: Soon to be released PR version
• StandardsRegExt-v1.0pr0.xsd: Soon to be released PR schema
• Working Draft StandardsRegExt document (20100519)
• StandardsRegExt-v1.0wd0.xsd

Samples

siastd.xml

This defines the SIA standard, defining its URI as ivo://ivoa.net/std/SIA. It enumerates the parameters that defines the standard SIA interface.

complang.xml

This defines a set of keys representing different computer languages. For example, the Python language can be identified via the URI, ivo://ivoa.net/std/application/languages#Python.

vospacestd.xml

This defines the VOSpace standard, defining terms mandated in the VOSpace specification like ivo://ivoa.net/vospace/core#httpget.

Status

• Development of the spec document is managed via the volute google code repository. You can find it under trunk/projects/registry/StandardsRegExt

Summary of Changes

since v0.4

• The name was changed from VOStandard to StandardsRegExt

since v0.3

• The spec document text was completed
• Added deprecated attribute to endorsedVersion element
• Added deprecated element

Discussion

Historical materials

This work used to be traced via the VOStandards page. That page is now deprecated. Attatchments to that page include:

• VOStandard-v0.3wd.html
• VOStandard-v0.4wd.xsd
• VOStandard-v0.4wd.html
• WD-VOStandard-1.0-20100514.html

(RayPlante - 19 May 2010)

This work used to be tracked via the RegDMStandards page. That page is now deprecated. (RayPlante - 10 Nov 2009)

The previous version of the schema was distributed as part of the RegUpgradeToV10 page

• VOStandard-v0.1.xsd

-- PaulHarrison - 25 Apr 2007

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

StandardsRegExt: Describing Standards for Registries

Note:

This standard is formerly known as VOStandard; discussion of the standard has moved here.

The version 1.0 registry data model uses Resource Identifiers in several places to identify which standard a particular resource follows (e.g. the capability element's standardID attribute). The Identifiers spec requires that any IVOA ID must have an entry in an IVOA registry; this implies that the standard itself is registered. Furthermore, there is an increasing interest to use IVOA identifiers to identify concepts and properties (e.g. VOSpace); the underlying identifier thus must be registered as well. The VOStandard data model and schema provides a framework in which IVOA standards can be described in the registry.

The goals of this extension are:

• allow support for an IVOA standard be recognized via an IVOA identifier (e.g. as in standardID)
• allow users to discover documentat about a standard protocol via the registry (in particular, via records of instances of the standard).
• allow one to define and use IVOA identifiers to identify a concept or property.

Latest materials

<-- 

 Working Draft StandardsRegExt document
 
 StandardsRegExt-v1.0wd0.xsd
 
-->

• PR-StandardsRegExt-1.0-20110316.html: Soon to be released PR version
• StandardsRegExt-v1.0pr0.xsd: Soon to be released PR schema
• Working Draft StandardsRegExt document (20100519)
• StandardsRegExt-v1.0wd0.xsd

Samples

siastd.xml

This defines the SIA standard, defining its URI as ivo://ivoa.net/std/SIA. It enumerates the parameters that defines the standard SIA interface.

complang.xml

This defines a set of keys representing different computer languages. For example, the Python language can be identified via the URI, ivo://ivoa.net/std/application/languages#Python.

vospacestd.xml

This defines the VOSpace standard, defining terms mandated in the VOSpace specification like ivo://ivoa.net/vospace/core#httpget.

Status

• Development of the spec document is managed via the volute google code repository. You can find it under trunk/projects/registry/StandardsRegExt

Summary of Changes

since v0.4

• The name was changed from VOStandard to StandardsRegExt

since v0.3

• The spec document text was completed
• Added deprecated attribute to endorsedVersion element
• Added deprecated element

Discussion

Historical materials

This work used to be traced via the VOStandards page. That page is now deprecated. Attatchments to that page include:

• VOStandard-v0.3wd.html
• VOStandard-v0.4wd.xsd
• VOStandard-v0.4wd.html
• WD-VOStandard-1.0-20100514.html

(RayPlante - 19 May 2010)

This work used to be tracked via the RegDMStandards page. That page is now deprecated. (RayPlante - 10 Nov 2009)

The previous version of the schema was distributed as part of the RegUpgradeToV10 page

• VOStandard-v0.1.xsd

-- PaulHarrison - 25 Apr 2007

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

StandardsRegExt: Describing Standards for Registries

Note:

This standard is formerly known as VOStandard; discussion of the standard has moved here.

The version 1.0 registry data model uses Resource Identifiers in several places to identify which standard a particular resource follows (e.g. the capability element's standardID attribute). The Identifiers spec requires that any IVOA ID must have an entry in an IVOA registry; this implies that the standard itself is registered. Furthermore, there is an increasing interest to use IVOA identifiers to identify concepts and properties (e.g. VOSpace); the underlying identifier thus must be registered as well. The VOStandard data model and schema provides a framework in which IVOA standards can be described in the registry.

The goals of this extension are:

• allow support for an IVOA standard be recognized via an IVOA identifier (e.g. as in standardID)
• allow users to discover documentat about a standard protocol via the registry (in particular, via records of instances of the standard).
• allow one to define and use IVOA identifiers to identify a concept or property.

Latest materials

<-- 

 Working Draft StandardsRegExt document
 
 StandardsRegExt-v1.0wd0.xsd
 
-->

• Working Draft StandardsRegExt document (20100519)
• StandardsRegExt-v1.0wd0.xsd

Samples

siastd.xml

This defines the SIA standard, defining its URI as ivo://ivoa.net/std/SIA. It enumerates the parameters that defines the standard SIA interface.

complang.xml

This defines a set of keys representing different computer languages. For example, the Python language can be identified via the URI, ivo://ivoa.net/std/application/languages#Python.

vospacestd.xml

This defines the VOSpace standard, defining terms mandated in the VOSpace specification like ivo://ivoa.net/vospace/core#httpget.

Status

• Development of the spec document is managed via the volute google code repository. You can find it under trunk/projects/registry/StandardsRegExt

Summary of Changes

since v0.4

• The name was changed from VOStandard to StandardsRegExt

since v0.3

• The spec document text was completed
• Added deprecated attribute to endorsedVersion element
• Added deprecated element

Discussion

Historical materials

This work used to be traced via the VOStandards page. That page is now deprecated. Attatchments to that page include:

• VOStandard-v0.3wd.html
• VOStandard-v0.4wd.xsd
• VOStandard-v0.4wd.html
• WD-VOStandard-1.0-20100514.html

(RayPlante - 19 May 2010)

This work used to be tracked via the RegDMStandards page. That page is now deprecated. (RayPlante - 10 Nov 2009)

The previous version of the schema was distributed as part of the RegUpgradeToV10 page

• VOStandard-v0.1.xsd

-- PaulHarrison - 25 Apr 2007

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

StandardsRegExt: Describing Standards for Registries

Note:

This standard is formerly known as VOStandard; discussion of the standard has moved here.

The version 1.0 registry data model uses Resource Identifiers in several places to identify which standard a particular resource follows (e.g. the capability element's standardID attribute). The Identifiers spec requires that any IVOA ID must have an entry in an IVOA registry; this implies that the standard itself is registered. Furthermore, there is an increasing interest to use IVOA identifiers to identify concepts and properties (e.g. VOSpace); the underlying identifier thus must be registered as well. The VOStandard data model and schema provides a framework in which IVOA standards can be described in the registry.

The goals of this extension are:

• allow support for an IVOA standard be recognized via an IVOA identifier (e.g. as in standardID)
• allow users to discover documentat about a standard protocol via the registry (in particular, via records of instances of the standard).
• allow one to define and use IVOA identifiers to identify a concept or property.

Latest materials

<-- 

 Working Draft StandardsRegExt document
 
 StandardsRegExt-v1.0wd0.xsd
 
-->

• Working Draft StandardsRegExt document (20100519)
• StandardsRegExt-v1.0wd0.xsd

Samples

siastd.xml

This defines the SIA standard, defining its URI as ivo://ivoa.net/std/SIA. It enumerates the parameters that defines the standard SIA interface.

complang.xml

This defines a set of keys representing different computer languages. For example, the Python language can be identified via the URI, ivo://ivoa.net/std/application/languages#Python.

vospacestd.xml

This defines the VOSpace standard, defining terms mandated in the VOSpace specification like ivo://ivoa.net/vospace/core#httpget.

Status

• Development of the spec document is managed via the volute google code repository. You can find it under trunk/projects/registry/StandardsRegExt

Summary of Changes

since v0.4

• The name was changed from VOStandard to StandardsRegExt

since v0.3

• The spec document text was completed
• Added deprecated attribute to endorsedVersion element
• Added deprecated element

Discussion

Historical materials

This work used to be traced via the VOStandards page. That page is now deprecated. Attatchments to that page include:

• VOStandard-v0.3wd.html
• VOStandard-v0.4wd.xsd
• VOStandard-v0.4wd.html
• WD-VOStandard-1.0-20100514.html

(RayPlante - 19 May 2010)

This work used to be tracked via the RegDMStandards page. That page is now deprecated. (RayPlante - 10 Nov 2009)

The previous version of the schema was distributed as part of the RegUpgradeToV10 page

• VOStandard-v0.1.xsd

-- PaulHarrison - 25 Apr 2007

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

StandardsRegExt: Describing Standards for Registries

Note:

This standard is formerly known as VOStandard; discussion of the standard has moved here.

The version 1.0 registry data model uses Resource Identifiers in several places to identify which standard a particular resource follows (e.g. the capability element's standardID attribute). The Identifiers spec requires that any IVOA ID must have an entry in an IVOA registry; this implies that the standard itself is registered. Furthermore, there is an increasing interest to use IVOA identifiers to identify concepts and properties (e.g. VOSpace); the underlying identifier thus must be registered as well. The VOStandard data model and schema provides a framework in which IVOA standards can be described in the registry.

The goals of this extension are:

• allow support for an IVOA standard be recognized via an IVOA identifier (e.g. as in standardID)
• allow users to discover documentat about a standard protocol via the registry (in particular, via records of instances of the standard).
• allow one to define and use IVOA identifiers to identify a concept or property.

Latest materials

<-- 

 Working Draft StandardsRegExt document
 
 StandardsRegExt-v1.0wd0.xsd
 
-->

• Working Draft StandardsRegExt document (20100519)
• StandardsRegExt-v1.0wd0.xsd

Status

• Development of the spec document is managed via the volute google code repository. You can find it under trunk/projects/registry/StandardsRegExt

Summary of Changes

since v0.4

• The name was changed from VOStandard to StandardsRegExt

since v0.3

• The spec document text was completed
• Added deprecated attribute to endorsedVersion element
• Added deprecated element

Discussion

Historical materials

This work used to be traced via the VOStandards page. That page is now deprecated. Attatchments to that page include:

• VOStandard-v0.3wd.html
• VOStandard-v0.4wd.xsd
• VOStandard-v0.4wd.html
• WD-VOStandard-1.0-20100514.html

(RayPlante - 19 May 2010)

This work used to be tracked via the RegDMStandards page. That page is now deprecated. (RayPlante - 10 Nov 2009)

The previous version of the schema was distributed as part of the RegUpgradeToV10 page

• VOStandard-v0.1.xsd

-- PaulHarrison - 25 Apr 2007

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

StandardsRegExt: Describing Standards for Registries

Note:

This standard is formerly known as VOStandard; discussion of the standard has moved here.

The version 1.0 registry data model uses Resource Identifiers in several places to identify which standard a particular resource follows (e.g. the capability element's standardID attribute). The Identifiers spec requires that any IVOA ID must have an entry in an IVOA registry; this implies that the standard itself is registered. Furthermore, there is an increasing interest to use IVOA identifiers to identify concepts and properties (e.g. VOSpace); the underlying identifier thus must be registered as well. The VOStandard data model and schema provides a framework in which IVOA standards can be described in the registry.

The goals of this extension are:

• allow support for an IVOA standard be recognized via an IVOA identifier (e.g. as in standardID)
• allow users to discover documentat about a standard protocol via the registry (in particular, via records of instances of the standard).
• allow one to define and use IVOA identifiers to identify a concept or property.

Latest materials

Status

• Development of the spec document is managed via the volute google code repository. You can find it under trunk/projects/registry/StandardsRegExt

Summary of Changes

since v0.4

• The name was changed from VOStandard to StandardsRegExt

since v0.3

• The spec document text was completed
• Added deprecated attribute to endorsedVersion element
• Added deprecated element

Discussion

Historical materials

This work used to be traced via the VOStandards page. That page is now deprecated. Attatchments to that page include:

• VOStandard-v0.3wd.html
• VOStandard-v0.4wd.xsd
• VOStandard-v0.4wd.html
• WD-VOStandard-1.0-20100514.html

(RayPlante - 19 May 2010)

This work used to be tracked via the RegDMStandards page. That page is now deprecated. (RayPlante - 10 Nov 2009)

The previous version of the schema was distributed as part of the RegUpgradeToV10 page

• VOStandard-v0.1.xsd

-- PaulHarrison - 25 Apr 2007

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

StandardsRegExt: Describing Standards for Registries

Note:

This standard is formerly known as VOStandard; discussion of the standard has moved here.

The version 1.0 registry data model uses Resource Identifiers in several places to identify which standard a particular resource follows (e.g. the capability element's standardID attribute). The Identifiers spec requires that any IVOA ID must have an entry in an IVOA registry; this implies that the standard itself is registered. Furthermore, there is an increasing interest to use IVOA identifiers to identify concepts and properties (e.g. VOSpace); the underlying identifier thus must be registered as well. The VOStandard data model and schema provides a framework in which IVOA standards can be described in the registry.

The goals of this extension are:

• allow support for an IVOA standard be recognized via an IVOA identifier (e.g. as in standardID)
• allow users to discover documentat about a standard protocol via the registry (in particular, via records of instances of the standard).
• allow one to define and use IVOA identifiers to identify a concept or property.

Latest materials

Status

• Development of the spec document is managed via the volute google code repository. You can find it under trunk/projects/registry/StandardsRegExt

Summary of Changes

since v0.4

• The name was changed from VOStandard to StandardsRegExt

since v0.3

• The spec document text was completed
• Added deprecated attribute to endorsedVersion element
• Added deprecated element

Discussion

Historical materials

This work used to be traced via the VOStandards page. That page is now deprecated. Attatchments to that page include:

• VOStandard-v0.3wd.html
• VOStandard-v0.4wd.xsd
• VOStandard-v0.4wd.html
• WD-VOStandard-1.0-20100514.html

(RayPlante - 19 May 2010)

This work used to be tracked via the RegDMStandards page. That page is now deprecated. (RayPlante - 10 Nov 2009)

The previous version of the schema was distributed as part of the RegUpgradeToV10 page

• VOStandard-v0.1.xsd

-- PaulHarrison - 25 Apr 2007

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

StandardsRegExt: Describing Standards for Registries

Note:

This standard is formerly known as VOStandard; discussion of the standard has moved here.

The version 1.0 registry data model uses Resource Identifiers in several places to identify which standard a particular resource follows (e.g. the capability element's standardID attribute). The Identifiers spec requires that any IVOA ID must have an entry in an IVOA registry; this implies that the standard itself is registered. Furthermore, there is an increasing interest to use IVOA identifiers to identify concepts and properties (e.g. VOSpace); the underlying identifier thus must be registered as well. The VOStandard data model and schema provides a framework in which IVOA standards can be described in the registry.

The goals of this extension are:

• allow support for an IVOA standard be recognized via an IVOA identifier (e.g. as in standardID)
• allow users to discover documentat about a standard protocol via the registry (in particular, via records of instances of the standard).
• allow one to define and use IVOA identifiers to identify a concept or property.

Latest materials

• Working Draft VOStandard document
• VOStandard-v0.4.xsd

Summary of Changes

since v0.3

• The spec document text was completed
• Added deprecated attribute to endorsedVersion element
• Added deprecated element

Discussion

Historical materials

This work used to be traced via the VOStandards page. That page is now deprecated. Attatchments to that page include:

• VOStandard-v0.3wd.html
• VOStandard-v0.4wd.xsd
• VOStandard-v0.4wd.html
• WD-VOStandard-1.0-20100514.html

(RayPlante - 19 May 2010)

This work used to be tracked via the RegDMStandards page. That page is now deprecated. (RayPlante - 10 Nov 2009)

The previous version of the schema was distributed as part of the RegUpgradeToV10 page

• VOStandard-v0.1.xsd

-- PaulHarrison - 25 Apr 2007

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

Note:

This standard is formerly known as VOStandard; discussion of the standard has moved here.

The version 1.0 registry data model uses Resource Identifiers in several places to identify which standard a particular resource follows (e.g. the capability element's standardID attribute). The Identifiers spec requires that any IVOA ID must have an entry in an IVOA registry; this implies that the standard itself is registered. Furthermore, there is an increasing interest to use IVOA identifiers to identify concepts and properties (e.g. VOSpace); the underlying identifier thus must be registered as well. The VOStandard data model and schema provides a framework in which IVOA standards can be described in the registry.

The goals of this extension are:

• allow support for an IVOA standard be recognized via an IVOA identifier (e.g. as in standardID)
• allow users to discover documentat about a standard protocol via the registry (in particular, via records of instances of the standard).
• allow one to define and use IVOA identifiers to identify a concept or property.

Latest materials

• Working Draft VOStandard document
• VOStandard-v0.4.xsd

Summary of Changes

since v0.3

• The spec document text was completed
• Added deprecated attribute to endorsedVersion element
• Added deprecated element

Discussion

Historical materials

This work used to be traced via the VOStandards page. That page is now deprecated. Attatchments to that page include:

• VOStandard-v0.3wd.html
• VOStandard-v0.4wd.xsd
• VOStandard-v0.4wd.html
• WD-VOStandard-1.0-20100514.html

(RayPlante - 19 May 2010)

This work used to be tracked via the RegDMStandards page. That page is now deprecated. (RayPlante - 10 Nov 2009)

The previous version of the schema was distributed as part of the RegUpgradeToV10 page

• VOStandard-v0.1.xsd

-- PaulHarrison - 25 Apr 2007

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

StandardsRegExt

Note:

This standard is formerly known as VOStandard; discussion of the standard has moved here.

The version 1.0 registry data model uses Resource Identifiers in several places to identify which standard a particular resource follows (e.g. the capability element's standardID attribute). The Identifiers spec requires that any IVOA ID must have an entry in an IVOA registry; this implies that the standard itself is registered. Furthermore, there is an increasing interest to use IVOA identifiers to identify concepts and properties (e.g. VOSpace); the underlying identifier thus must be registered as well. The VOStandard data model and schema provides a framework in which IVOA standards can be described in the registry.

The goals of this extension are:

• allow support for an IVOA standard be recognized via an IVOA identifier (e.g. as in standardID)
• allow users to discover documentat about a standard protocol via the registry (in particular, via records of instances of the standard).
• allow one to define and use IVOA identifiers to identify a concept or property.

Latest materials

• Working Draft VOStandard document
• VOStandard-v0.4.xsd

Summary of Changes

since v0.3

• The spec document text was completed
• Added deprecated attribute to endorsedVersion element
• Added deprecated element

Discussion

Historical materials

This work used to be traced via the VOStandards page. That page is now deprecated. Attatchments to that page include:

• VOStandard-v0.3wd.html
• VOStandard-v0.4wd.xsd
• VOStandard-v0.4wd.html
• WD-VOStandard-1.0-20100514.html

(RayPlante - 19 May 2010)

This work used to be tracked via the RegDMStandards page. That page is now deprecated. (RayPlante - 10 Nov 2009)

The previous version of the schema was distributed as part of the RegUpgradeToV10 page

• VOStandard-v0.1.xsd

-- PaulHarrison - 25 Apr 2007

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->