ieee-2791-schema issueshttp://opensource.ieee.org/2791-object/ieee-2791-schema/-/issues2021-02-24T16:17:33Zhttp://opensource.ieee.org/2791-object/ieee-2791-schema/-/issues/2Derived from should be multi field2021-02-24T16:17:33ZCharles KingDerived from should be multi fieldThe derived_from field should be updated to allow for multiple references. This would be important in situations where the derivative BCO is a combination of multiple parents.
https://opensource.ieee.org/2791-object/ieee-2791-schema/...The derived_from field should be updated to allow for multiple references. This would be important in situations where the derivative BCO is a combination of multiple parents.
https://opensource.ieee.org/2791-object/ieee-2791-schema/-/blob/master/provenance_domain.json#L75
```json
"derived_from": {
"description": "value of `ieee2791_id` field of another IEEE-2791 that this object is partially or fully derived from",
"$ref": "2791object.json#/definitions/object_id"
}
```
suggested edit:
```json
"derived_from": {
"description": "value of `ieee2791_id` field of other IEEE-2791 that this object is partially or fully derived from",
"type": "array",
"items" :{
"$ref": "2791object.json#/definitions/object_id"
}
}
```
I do not believe that this would cause any changes to the written spec, only the schema here.
Page 13 in the IEEE-2791-2020 Standard says:
>In the event that a IEEE 2791 Object retrospectively references an existing Object (such as an example Object), the derived_from field within the Provenance Domain shall reference the specific Object by object_id field. In the event that the Object is an example Object or is created de novo without reference to existing work, this field is not included. In the event that the Object is an example or template IEEE 2791 Object, best practice is to state this in the Usability Domain, along with relevant details (such as completeness of data, whether data is real or artificial, etc.).