As discussed in #630, and in relation to #232, any time where OCDS support an array of objects, the objects in the array should each have an id property, and this property should be required.
At present, this is not true of
OrganizationOrganizationReferenceRelatedProcessAmendment
Making these fields required is backwards incompatible (data valid under X.x could be made invalid under X.x+1 as the result of stronger requirements).
These fields should be made required in OCDS 2.0, and in the meantime a warning added to validation processes.
As discussed in #630, and in relation to #232, any time where OCDS support an array of objects, the objects in the array should each have an
idproperty, and this property should be required.At present, this is not true of
OrganizationOrganizationReferenceRelatedProcessAmendmentMaking these fields required is backwards incompatible (data valid under X.x could be made invalid under X.x+1 as the result of stronger requirements).
These fields should be made required in OCDS 2.0, and in the meantime a warning added to validation processes.