Difference: VOStandard (1 vs. 8)
Revision 82012-06-26 - root
Meetings: InterOpNov2009Reg :: InterOpMay2009ResReg :: InterOpMay2008ResReg :: InterOpSep2007ResReg :: InterOpMay2007ResReg VOStandard
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:
Latest materialsSummary of Changessince v0.3
DiscussionHistorical materialsThis 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 | |||||||||
| Changed: | |||||||||
| < < | |||||||||
| > > | |||||||||
|
-- PaulHarrison - 25 Apr 2007
| |||||||||
Revision 72010-05-19 - RayPlante
Meetings: InterOpNov2009Reg :: InterOpMay2009ResReg :: InterOpMay2008ResReg :: InterOpSep2007ResReg :: InterOpMay2007ResReg VOStandard | |||||||||
| Added: | |||||||||
| > > |
| ||||||||
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:
Latest materialsSummary of Changessince v0.3
DiscussionHistorical materialsThis 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 <--
| |||||||||
Revision 62010-05-15 - RayPlante
Meetings: InterOpNov2009Reg :: InterOpMay2009ResReg :: InterOpMay2008ResReg :: InterOpSep2007ResReg :: InterOpMay2007ResReg VOStandardThe version 1.0 registry data model uses Resource Identifiers in several places to identify which standard a particular resource follows (e.g. thecapability 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:
Latest materialsSummary of Changessince v0.3
DiscussionHistorical materialsThis 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 <--
|
Revision 52010-05-14 - RayPlante
Meetings: InterOpNov2009Reg :: InterOpMay2009ResReg :: InterOpMay2008ResReg :: InterOpSep2007ResReg :: InterOpMay2007ResReg VOStandardThe version 1.0 registry data model uses Resource Identifiers in several places to identify which standard a particular resource follows (e.g. thecapability 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:
Latest materials | |||||||||
| Changed: | |||||||||
| < < | |||||||||
| > > | |||||||||
Summary of Changessince v0.3
DiscussionHistorical materialsThis 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 <--
| |||||||||
Revision 42010-05-14 - RayPlante
Meetings: InterOpNov2009Reg :: InterOpMay2009ResReg :: InterOpMay2008ResReg :: InterOpSep2007ResReg :: InterOpMay2007ResReg VOStandardThe version 1.0 registry data model uses Resource Identifiers in several places to identify which standard a particular resource follows (e.g. thecapability 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:
Latest materialsSummary of Changessince v0.3
DiscussionHistorical materialsThis 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 <--
| |||||||||
| Added: | |||||||||
| > > |
| ||||||||
Revision 32009-11-10 - RayPlante
Meetings: InterOpNov2009Reg :: InterOpMay2009ResReg :: InterOpMay2008ResReg :: InterOpSep2007ResReg :: InterOpMay2007ResReg VOStandard | ||||||||
| Changed: | ||||||||
| < < | The version 1.0 registry data model uses Resource Identifiers in several places to identify which standard a particular resource follows. By using IVOA resource identifiers in this way there is an implicit assumption that the standard is itself registered - though no formal requirement to do so. The VOStandard data model and schema provides a framework in which IVOA standards can be described in the registry. | |||||||
| > > | 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. | |||||||
| Added: | ||||||||
| > > | The goals of this extension are: | |||||||
| Added: | ||||||||
| > > |
| |||||||
| Added: | ||||||||
| > > | ||||||||
Latest materials | ||||||||
| Changed: | ||||||||
| < < | ||||||||
| > > | ||||||||
| Added: | ||||||||
| > > | Summary of Changes | |||||||
| Added: | ||||||||
| > > | since v0.3
| |||||||
DiscussionHistorical materialsThis 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 <--
| ||||||||
Revision 22009-11-10 - RayPlante
Meetings: InterOpNov2009Reg :: InterOpMay2009ResReg :: InterOpMay2008ResReg :: InterOpSep2007ResReg :: InterOpMay2007ResReg VOStandardThe version 1.0 registry data model uses Resource Identifiers in several places to identify which standard a particular resource follows. By using IVOA resource identifiers in this way there is an implicit assumption that the standard is itself registered - though no formal requirement to do so. The VOStandard data model and schema provides a framework in which IVOA standards can be described in the registry.Latest materialsDiscussionHistorical materialsThis 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 <--
| ||||||||
| Added: | ||||||||
| > > |
| |||||||
Revision 12009-11-10 - RayPlante
Meetings: InterOpNov2009Reg :: InterOpMay2009ResReg :: InterOpMay2008ResReg :: InterOpSep2007ResReg :: InterOpMay2007ResReg VOStandardThe version 1.0 registry data model uses Resource Identifiers in several places to identify which standard a particular resource follows. By using IVOA resource identifiers in this way there is an implicit assumption that the standard is itself registered - though no formal requirement to do so. The VOStandard data model and schema provides a framework in which IVOA standards can be described in the registry.Latest materialsDiscussionHistorical materialsThis 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 <--
|
View topic | History: r8 < r7 < r6 < r5 | More topic actions...
Copyright © 2008-2025 by the contributing authors. All material on this collaboration platform is the property of the contributing authors. Ideas, requests, problems regarding TWiki? Send feedback