I'm currently thinking about some QOL ideas for the golang library, hopefully to add some helpers to interface with some of the consumers of the library i've been talking to. Pardon the ignorance on some of these topics. It is unfortunate I have a conflict with the tooling WG, but I guess that would have been the best place to bring up this question.
Is there a description of what's considered a minor version / major version change for SPDX? I am asking this from a tooling perspective where I'm considering adding in function receivers (for tools-golang repo). Assuming there is some level of backward compatibility, would there be a change in behavior of how certain fields are handled? (i.e. can we take an SPDX 2.1 document and convert it to 2.2 and have all operations done on it be valid?). Would it be fair to also say that a 2.2 element would encapsulate all fields of a 2.1 element? And that one could embed the struct within it? -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#4561): https://lists.spdx.org/g/Spdx-tech/message/4561 Mute This Topic: https://lists.spdx.org/mt/91609001/21656 Group Owner: [email protected] Unsubscribe: https://lists.spdx.org/g/Spdx-tech/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
