Manifest: surrogate-key for Master and Reference Data
Version 1.0.0 of Manifest Schema has containers for Work Product, Work Product Component, and Files. These containers are captured using the AbstractAnyRecordWorkProduct*, AbstractAnyRecordWorkProductComponent*, and AbtractAnyRecordFile* $ref inclusions. Within these three AbstractAnySchema* items, the properties.id
pattern supports the surrogate-key
construct. However, the AbstractAnyRecordMasterData* and AbstractAnyRecordReferenceData* schemas have properties.id
definitions that do not have a place for surrogate-key
identification.
Two questions for consideration:
- Would it be possible for the AbstractAnyRecordMasterData and AbstractAnyRecordReferenceData schemas to have a
properties.id
definition that supports thesurrogate-key
pattern? - If the
surrogate-key
was intentionally left out of AbstractAnyRecordMasterData and AbstractAnyRecordReferenceData, what was the reason?