This discussion thread is for Question 1 of the list of questions William started: * Adding an abstract Collection class as the superclass of Document and ContextualCollection simplified the model, are we comfortable keeping that?
As I understand it, a "collection" is a set of unrelated elements and a "ContextualCollection" is a set of related elements. But it looks like David had a different understanding: * Contextual is a set of related elements - the collection is created as a unit and elements contained in the collection are always part of the collection even when referenced by individual IRI. The collection Element and its contained Elements are created at the same instant by the same creator, regardless of whether any creation properties are serialized in the Elements. * Non-contextual is a collection that does not define any Elements. The Elements were created before the collection, are copied into the collection, and are unchanged whether the collection exists or not. >From the above definition it seems to me that the difference between >"contextual" and "not contextual" has to do with the timestamp of the >collection. Did I understand this correctly? If yes, the concept sounds a lot like an instance of an object vs a collection of (still related) objects a la OOP. I'm personally for including both concepts of "instant collection" and "assembled collection" as long as the concepts are clearly defined, as David mentioned here: https://lists.spdx.org/g/Spdx-tech/message/4201 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#4202): https://lists.spdx.org/g/Spdx-tech/message/4202 Mute This Topic: https://lists.spdx.org/mt/85799075/21656 Group Owner: spdx-tech+ow...@lists.spdx.org Unsubscribe: https://lists.spdx.org/g/Spdx-tech/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
