The logical model currently defines a Hash type with algorithm and hashValue properties. That type is atomic, it doesn't make any sense to have an algorithm without a value, or vice versa, or to mismatch algorithm and value (e.g. an md5 algorithm with a 256 bit value).
The intent of a Created type is identical to the Hash type. An instance always has both creator and timestamp, you can't have one without the other, and you can't change either property without resulting in a different instance. Whatever argument is made against modeling Created as a single type can be made against modeling Hash as a single type. And whatever "countermeasures" are used to prevent breaking Hash atomicity apply equally to breaking Created atomicity. Dave -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#4366): https://lists.spdx.org/g/Spdx-tech/message/4366 Mute This Topic: https://lists.spdx.org/mt/89003827/21656 Group Owner: [email protected] Unsubscribe: https://lists.spdx.org/g/Spdx-tech/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
