opencadc / caom2

Common Archive Observation Model
GNU Affero General Public License v3.0
5 stars 11 forks source link

RFE: add more values to DataProductType #17

Closed pdowler closed 7 years ago

pdowler commented 7 years ago

Proposal from HST Archive Coordination Meeting to support additional values/details.

Currently allows ObsCore values plus catalog. We should consider moving to a more loosely coupled vocabulary to allow for extensions.

pdowler commented 7 years ago

Intend to convert the current Plane.dataProductType field to a normal string and retain the DataProductType enum simply to specify standard values -- but implementers could introduce new values as needed.

How to differentiate between ObsCore values, CAOM values, and custom values?

Add ObsCoreDataProductType with standard values from ObsCore data model. Change current DataProductType to be an extension with the CAOM vocabulary terms declared as constants. Allow for other vocabularies (base url) with terms (fragment). CAOM ocabulary terms will be, eg:

http://www.opencadc.org/caom2#term

as that will minimally make them resolvable to documentation. Serialised values for ObsCore terms will be just the fragment; all others will be full URLs.

To be included in CAOM-2.3

pdowler commented 7 years ago

Added in CAOM-2.3