DatasetMetadata model version 1.0GoalAll IVOA datsets must contain a common set of metadata elements to facilitate the registration, discovery, and interoperability of these datasets. To date, individual IVOA data models have independently defined this metadata within separate documents. This has resulted in some level of inconsistency between models, as well as document bloat. This document describes a high-level model of generic dataset metadata for the IVOA. The descriptions of many elements of this model are a result of reviewing and combining those contained in the ObsCore (1.0), Spectral (2.0), and Characterisation (1.33) models. As such, it represents a uniform, consistent description set capable of supporting the use cases covered by those models.ParticipantsMarkCresitelloDittmar (editor); FrancoisBonnarel, OmarLaurino, GerardLemson, MireilleLouys, ArnoldRots, DougTodyUse CasesAs a high level model, this model will support, either directly or indirectly a wide range of use cases. It is being developed in conjunction with the NDCube data model with primary goals to support the following: 1) Provide the framework model behind ObsCore, thereby indirectly supporting the use cases of that document and the ObsTap access protocol. To clarify, ObsCore describes a flattened view of a more full and complete Observation/ObsDataset model, including only those portions necessary for interoperability and useful in support of the ObsTap access protocol. This document provides the model for datasets derived from observations. By being compatible with ObsCore, we create a consistent path from the dataset to the access protocol(s) used to discover them. 2) Provide the high level dataset metadata model in support of the NDCube model, which describes generic N-Dimensional datasets, including pixelated images to sparse hypercubes. The model must be generic and extensible to serve the same purpose for a wide variety of datasets. 3) Support SIAv2.1Requirements
DocumentsLatest document: The latest released document can be found on the IVOA Documents and Standards page. Volute: | ||||||||
Changed: | ||||||||
< < | The volute repository holds all revisions of the document, as well as the source open office document, diagrams, etc. here | |||||||
> > | The volute repository holds all revisions of the document, as well as the source open office document, diagrams, etc. here | |||||||
UML Model | ||||||||
Changed: | ||||||||
< < | The model is being developed in UML, using Modelio-3.0. The model project can be obtained as a zip file in the volute repository, here. | |||||||
> > | The model is being developed in UML, using Modelio-3.0. The model project can be obtained as a zip file in the volute repository, here. | |||||||
We also provide an export of the UML specification in XMI format (version 2.4.1), which is compatible with the vo-dml xslt scripts for generating the vo-dml XML representation.
Discussion TopicsThis model has spawned from earlier work of the Spectral-2.0 model and Image-1.0 models. The bulk of the earlier discussions defining the separation and metadata components into Dataset, Observation, ObsDataset took place then and are described on the ImageDM page. Since that time, focus has concentrated on the areas of vo-dml compliance and the generation of the STC2 model. More recent WG topics include:
ImplementationsValidators | ||||||||
Changed: | ||||||||
< < | The requirements for validating a data model are still unclear. At this stage, we will provide the following: | |||||||
> > | The requirements for validating a data model are still unclear. At this stage, we will provide the following: | |||||||
| ||||||||
Changed: | ||||||||
< < | Dataset is a component model, as such it cannot be directly implemented in a science use case. It will be used in conjunction with other models to satisfy the requirements of the use case. The following are examples of threads/cases which the model is targeted to support. | |||||||
> > | Dataset is a component model, as such it cannot be directly implemented in a science use case. It will be used in conjunction with other models to satisfy the requirements of the use case. The following are examples of threads/cases which the model is targeted to support. | |||||||
| ||||||||
Deleted: | ||||||||
< < | ||||||||
<--
|
DatasetMetadata model version 1.0GoalAll IVOA datsets must contain a common set of metadata elements to facilitate the registration, discovery, and interoperability of these datasets. To date, individual IVOA data models have independently defined this metadata within separate documents. This has resulted in some level of inconsistency between models, as well as document bloat. This document describes a high-level model of generic dataset metadata for the IVOA. The descriptions of many elements of this model are a result of reviewing and combining those contained in the ObsCore (1.0), Spectral (2.0), and Characterisation (1.33) models. As such, it represents a uniform, consistent description set capable of supporting the use cases covered by those models.ParticipantsMarkCresitelloDittmar (editor); FrancoisBonnarel, OmarLaurino, GerardLemson, MireilleLouys, ArnoldRots, DougTodyUse CasesAs a high level model, this model will support, either directly or indirectly a wide range of use cases. It is being developed in conjunction with the NDCube data model with primary goals to support the following: 1) Provide the framework model behind ObsCore, thereby indirectly supporting the use cases of that document and the ObsTap access protocol. To clarify, ObsCore describes a flattened view of a more full and complete Observation/ObsDataset model, including only those portions necessary for interoperability and useful in support of the ObsTap access protocol. This document provides the model for datasets derived from observations. By being compatible with ObsCore, we create a consistent path from the dataset to the access protocol(s) used to discover them. 2) Provide the high level dataset metadata model in support of the NDCube model, which describes generic N-Dimensional datasets, including pixelated images to sparse hypercubes. The model must be generic and extensible to serve the same purpose for a wide variety of datasets. 3) Support SIAv2.1Requirements | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
DocumentsLatest document: The latest released document can be found on the IVOA Documents and Standards page. Volute: The volute repository holds all revisions of the document, as well as the source open office document, diagrams, etc. here UML Model The model is being developed in UML, using Modelio-3.0. The model project can be obtained as a zip file in the volute repository, here. We also provide an export of the UML specification in XMI format (version 2.4.1), which is compatible with the vo-dml xslt scripts for generating the vo-dml XML representation.Discussion TopicsThis model has spawned from earlier work of the Spectral-2.0 model and Image-1.0 models. | ||||||||
Changed: | ||||||||
< < | The bulk of the earlier discussions defining the separation and metadata components into Dataset, Observation, ObsDataset took place then and are described on the ImageDM page. | |||||||
> > | The bulk of the earlier discussions defining the separation and metadata components into Dataset, Observation, ObsDataset took place then and are described on the ImageDM page. | |||||||
Since that time, focus has concentrated on the areas of vo-dml compliance and the generation of the STC2 model.
More recent WG topics include:
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Implementations | ||||||||
Changed: | ||||||||
< < |
DatasetMetadata model version 1.0Goal | ||||||||
Changed: | ||||||||
< < | Uses cases | |||||||
> > | ||||||||
Added: | ||||||||
> > | All IVOA datsets must contain a common set of metadata elements to facilitate the registration, discovery, and interoperability of these datasets. To date, individual IVOA data models have independently defined this metadata within separate documents. This has resulted in some level of inconsistency between models, as well as document bloat. This document describes a high-level model of generic dataset metadata for the IVOA. The descriptions of many elements of this model are a result of reviewing and combining those contained in the ObsCore (1.0), Spectral (2.0), and Characterisation (1.33) models. As such, it represents a uniform, consistent description set capable of supporting the use cases covered by those models. | |||||||
ParticipantsMarkCresitelloDittmar (editor); FrancoisBonnarel, OmarLaurino, GerardLemson, MireilleLouys, ArnoldRots, DougTody | ||||||||
Added: | ||||||||
> > | Use CasesAs a high level model, this model will support, either directly or indirectly a wide range of use cases. It is being developed in conjunction with the NDCube data model with primary goals to support the following: 1) Provide the framework model behind ObsCore, thereby indirectly supporting the use cases of that document and the ObsTap access protocol. To clarify, ObsCore describes a flattened view of a more full and complete Observation/ObsDataset model, including only those portions necessary for interoperability and useful in support of the ObsTap access protocol. This document provides the model for datasets derived from observations. By being compatible with ObsCore, we create a consistent path from the dataset to the access protocol(s) used to discover them. 2) Provide the high level dataset metadata model in support of the NDCube model, which describes generic N-Dimensional datasets, including pixelated images to sparse hypercubes. The model must be generic and extensible to serve the same purpose for a wide variety of datasets. 3) Support SIAv2.1Requirements
| |||||||
Documents | ||||||||
Added: | ||||||||
> > | Latest document: The latest released document can be found on the IVOA Documents and Standards page. | |||||||
Volute: | ||||||||
Changed: | ||||||||
< < | Model package and diagrams can be found here | |||||||
> > | The volute repository holds all revisions of the document, as well as the source open office document, diagrams, etc. here | |||||||
Added: | ||||||||
> > | UML Model The model is being developed in UML, using Modelio-3.0. The model project can be obtained as a zip file in the volute repository, here. We also provide an export of the UML specification in XMI format (version 2.4.1), which is compatible with the vo-dml xslt scripts for generating the vo-dml XML representation. | |||||||
Discussion Topics | ||||||||
Added: | ||||||||
> > |
This model has spawned from earlier work of the Spectral-2.0 model and Image-1.0 models.
The bulk of the earlier discussions defining the separation and metadata components into Dataset, Observation, ObsDataset took place then and are described on the ImageDM page.
Since that time, focus has concentrated on the areas of vo-dml compliance and the generation of the STC2 model.
More recent WG topics include:
Implementations | |||||||
<--
|
DatasetMetadata model version 1.0GoalUses casesParticipantsMarkCresitelloDittmar (editor); FrancoisBonnarel, OmarLaurino, GerardLemson, MireilleLouys, ArnoldRots, DougTodyDocumentsVolute: Model package and diagrams can be found hereDiscussion Topics<--
|