This PR has the model I proposed at the end of today's meeting:
https://github.com/spdx/spdx-3-model/pull/25

>From the PR description:
This is the model I proposed at the end of the meeting. Notable changes:

  *   Added the missing inherits from Collection to Element.
  *   Renamed Document to SpdxDocument.
  *   Added Bundle and moved BOM to inherit from Bundle to remove the 
implication that BOM's need to be a serialization root.
  *   Moved SpdxDocument to inherit from Bundle since they are a special type 
of bundle.

There is an open question on whether the distinction between SpdxDocument and 
Bundle is necessary, but this proposal doesn't force you to use SpdxDocument 
while providing a clear migration path from SPDX 2.x.

If during the formal definition of the classes it becomes clear we don't need 
both they can be collapsed together, but for now this would unblock us.


Regards,

William Bartholomew (he/him) - Let's 
chat<https://outlook.office.com/bookwithme/user/[email protected]/meetingtype/SVRwCe7HMUGxuT6WGxi68g2?anonymous&ep=mlink>
Principal Security Strategist
Global Cybersecurity Policy - Microsoft

My working day may not be your working day. Please don't feel obliged to reply 
to this e-mail outside of your normal working hours.



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#4699): https://lists.spdx.org/g/Spdx-tech/message/4699
Mute This Topic: https://lists.spdx.org/mt/92634687/21656
Group Owner: [email protected]
Unsubscribe: https://lists.spdx.org/g/Spdx-tech/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-


Reply via email to