XML Template for the SPASE Data Model.

This is the location of templates for resource description for the SPASE data model. Click on a resource type to get a blank template with all possible (required and optional) elements.

Details on the SPASE data model are available as a tree, dictionary search, and document, .

Resource Type	Description	Action
Person	An individual human being.	View Download
Observatory	A device which is used to sense and parameterize a physical phenomenon.	View Download
Instrument	A device which is used to sense and parameterize a physical phenomenon.	View Download
DisplayData	A graphical representation of data wherein the underlying numeric values are not (readily) accessible for analysis. Examples are line plots and spectrograms.	View Download
NumericalData	Data stored as numerical values in a specified format.	View Download
Catalog	A tabular listing of events or observational notes, especially those that have utility in aiding a user in locating data. Catalogues include lists of events, files in a product, and data availability.	View Download
Granule	An accessible portion of another resource. A Granule may be composed of one or more physical pieces (files) which are considered inseperable. For example, a data storage format that maintains metadata and binary data in seperate, but tightly coupled files. Granules should not be used to group files that have simple relationships or which are associated through a parent resource. For example, each file containing a time interval data for a Numerical Data resource would each be considered a Granule. The ParentID of a Granule resource must be a NumericalData resource. The attributes of a Granule supersede the corresponding attributes in the NumericalData resource.	View Download
Registry	A location or facility where resources are cataloged.	View Download
Repository	A location or facility where resources are stored.	View Download
Service	A location or facility that can perform a well defined task.	View Download
Extension	A container of other metadata which is not part of the SPASE data model. The contents of this element are defined by individual usage. The organization and content are constrained by the implementation. For example, in an XML representation of the SPASE metadata the content must conform to the XML specications.	View Download