Alexios Zavras (zvr)

I don't understand the question. All SPDX data are under CC0-1.0. Why would you think that the license would be wrong ("more often than not", even!).

> What causes all SPDX data to be under CC0? The SPDX specification, which, since the beginning, 10+ years ago, said that the data license is CC-1.0. Even without the...

But @swinslow, Clause 10 https://spdx.github.io/spdx-spec/v2-draft/other-licensing-information-detected/ says that `LicenseRef` is to be used for **licenses**, not **licensing information** in general. So I'm not sure how to create something that says "I...

I think the `;` was proposed by @MarkGisi as a way to combine different licenses in a package... I seem to remember a discussion in a conference about the differences...

For those of us who have no idea about the underlying principles, can you provide more information explaining this? What is "Code Rule"? What does it mean to be "applied"?...

An enthusiastic +1 on this proposal. A few thoughts: 1. I would strongly suggest to only have existent valid SPDX tags and not introduce any other information. Therefore, in the...

So, where shall the discussion on the actual specification of this file take place? There is need to: - define exact syntax (including clear pattern matching rules); and - specify...

@goneall if we're going this deep, I'd really like to actually exactly specify what is allowed there: Full ISO-8601? Full RFC-3339? Something else? My vote: leave the format definition as...

Aren't these relationship directed to opposite ends? I mean, expressing the same thing would be `curl DEPENDS_ON zlib` and `zlib DEPENDENCY_OF curl`. If you remove one of them, how can...

I also agree that the sample file is wrong. Since Tag-Value format does not have hierarchical nesting (Package/File/Snippet), we've always maintained that this was expressed by the order that entries...