Skip to content
Brian Thomas edited this page Jan 13, 2015 · 13 revisions

Representation of Information

Related Use case(s)

Use Case 1

Use Case 9

Description

The format shall be capable of representing various desired astronomical and related information. Several sub-requirements below define a minimum (but not limiting) set of information which the format must be capable of representing.

Sub-requirements

Requirement 1.1 - Representation of multi-dimensional images

The format shall be capable of representing multi-dimensional images. {further definition of what is meant by "multi-dimensional image" needed here; possibly data cubes; furthermore, do we need to call out in sub-requirements of this one particular image types, for example "sky image"?}

Requirement 1.2 - Representation of tabular data

The format shall be capable of representing tabular data. {describe what is meant by "tabular data"; is this simply a sub-set of a data cube?}

Requirement 1.3 - Representation of spectral data

The format shall be capable of representing spectral data. {definition of what "spectral data" means should go here}

Requirement 1.4 - Representation of datasets (collections)

The format shall be capable of representing a collection (ordered set) of data within a single instance.

Requirement 1.4.1 - Representation of datasets of data products

Format collections shall be capable of holding any admixture of individual data product types (e.g. images, data cubes, spectra, tables, etc)

Requirement 1.4.2 - Representation of datasets with sub-collections

Format collections shall also be capable of holding (sub)-collections so that a hierarchy of data products may be constructed (any admixture of data product types and sub-collections shall be allowed). There shall be no limit to the number of nested levels within the collection hierarchy.