SPASE (meta)Data Model

The SPASE Data Model consists of an exclusive set of resource types which can be used to describe data along with its scientific context, source, provenance, content and location. It is designed to support a federated data system where data may reside at different locations and may be seperated from the metadata which describes it.

While the data model is neutral on how to it may be expressed, the preferred expression form is XML. There are XML Schema documents which can be used to generate and validate SPASE compliant XML documents.

There are tutorials and other information available at the SPASE School.

Top Level View

The Resource Types currently in the data model are:

Annotation
Explanatory or descriptive information that is associated with another resource.
Catalog
Listing of events or observational notes.
Document
Plain or formatted text that may include graphics, sound, other multimedia data, or hypermedia references.
Display Data
A graphical representation of data.
Numerical Data
Data product stored as numerical values in a specified format.
Granule
An accessible portion of another resource.
Instrument
A device that is used to sense and parameterize a physical phenomenon.
Observatory
The host (spacecraft, network, facility) for instruments making observations.
Person
An individual human being.
Registry
A location or facility where resources are catalogued.
Repository
A location or facility where resources are stored.
Service
A location or facility that can perform a well-defined task.

Each of these elements is broken down into sub-elements that provide sufficient detail for adequate description of data sets. The Resource Types Numerical Data, Display Data and Catalogue are the resources used to describe Heliophysics data products. These data product descriptions reference the other resources which contain descriptions of the observatories, instruments, people, etc. that created the data products. The resources are described using the terms from the SPASE Data Dictionary presented in the Data Model document.