I wonder why the latest XJDF specification references the product to which a RunList resource belongs to via the product’s optional ExternalID attribute and not via the ID attribute which is exactly for such a purpose. Can somebody enlighten me?
IDs such as ID-IDRef pairs are designed to be throw away items.
Partition keys are designed to remain constant over multiple submissions / changes of the same job.
@ProductPart was a reference to an ID and thus a bit different from the other partition keys.
@Product was therefore introduced to have a lasting reference.
Note also that there are ideas to completely get rid of the remaining ID IDREF pairs - at least in case we continue with a design for json mapping. See JSON mapping for XJDF datatypes.
Powered by a free Atlassian Confluence Open Source Project License granted to CIP4. Evaluate Confluence today.