think about a deserialization profile

[maxhbr]

this was created when thinking about #403 (comment)

[goneall]

I though about suggesting a subclass of File, but after thinking about it we would want to cover the case where something is serialized as a network stream.

[goneall]

I'm a bit confused about the element property description - would this reference that actual elements in the graph deserialized from the file?

[maxhbr]

I thought that this would reference all element objects, that were created in the de-serialization process

[goneall]

Makes sense - I may suggest some word smithing if we go down this route.

[goneall]

Would I be able to handle the following scenario?:

• A single "Payload" is created by aggregating several existing previous Payloads (the commonly request merge function for the SPDX Tools) Note that the namespace map used for this merged Payload is irrelevant to this scenario.
• You then want to "break apart" the single Payload back to the individual previous Payload and retain their original namespace maps - in this scenario, you don't care about the namespace map for the merged Payload

[maxhbr]

Discussions moved along and are no happening in a different place. Closing this issue. In discussions it is now called the X-Collection