Olle E. Johansson
Olle E. Johansson
This was raised during our meeting. I think it is doable.
Example added to api-flow
There are two cases here: * Software with a release candidate. The release is different from the rc so that's a new leaf, new UUID. * Software where the release...
Steve: Make it changeable - it's basically a life cycle event
During the meeting we suggested that a leaf can be promoted to production version, but add implementation guide that there should not be support for flagging a production version as...
I think the product is something the manufacturer hands over to the user. The same product can have many names and a "product" can be a bundle of many bundles...
I don't see any reason to separate BOMs from other files in phase one. Did you have any specific reason for doing so?
Stuff that happens when you're on holiday. ha ha :-) I still think we need one attachment object - could be that we have additional attributes for BOMs, like the...
Checked https://github.com/CycloneDX/transparency-exchange-api/pull/22/files and I already had an optional BOM identifier in the definition of an artefact.
@goneall thank you for your feedback. There is a use case document in the repository if you are interested. I also have a pull request adding to it.