Alexios Zavras (zvr)

@bact you are correct; the descriptions of these RelationshipTypes will have to be updated.

@kestewart the main use case is not in SBOMs; in this case, in a specific software release you have a specific `curl` (for example, version 8.12.1-3ubuntu1 supplied by Canonical). But...

No, the glossary contains information about the model infrastructure, but not really the content. That's why it's not part of the spec itself. It's just some useful info for people...

What is the purpose of the "validation"? I assume to make sure that the input is "correct" / "valid". What does this mean? More specifically: - errors should most definitely...

Full examples would probably be placed best in the https://github.com/spdx/spdx-examples repo. Snippets should probably be placed best in the https://github.com/spdx/using repo. I don't think they should be in the specification...

@umm0 What is the included PowerPoint slides file? Was it part of a meeting? If yes, it should be associated with one. If not, it should not be in this...

No, we tell them: - in text, in the spec repo, use sentence case - in special formatted files, in the model repo, use one of the predefined headers

> spdx.github.io/spdx-spec/v3.0.1/serializations#canonical-serialization is too weak Can you explain what you mean by "too weak"? The other website was only active when the working group was active. It has produced the...

Right, that's exactly what I was trying to convey. The whole point of the "SPDX canonical serialization" is to have a unique way of representing some data. This can be...

This is about _Summaries_ , not _Descriptions_. The Summary section _should_ be a single line, since it's translated into a `rdfs:comment` in the ontology. We don't have (yet) a nice...