Alexios Zavras (zvr)

We can merge this, and improve it later. Still missing, for example: the file where translations will provide the headings in their own language. But I haven't fully worked it...

Looking at the 4 bullets in @goneall [last comment](https://github.com/spdx/spdx-spec/issues/1155#issuecomment-2494632545), I'm not sure everything is clear -- nor that I agree with everything: 1. I think it presumes that all of...

You're thinking it from a wrong point of view: the meaning of a tag a.b.c-XX is that this contains the released content of a.b.c in language XX. It might contain...

I don't believe this should be visible there. It's part of the JSON-LD context, and it is relevant only for the JSON-LD serialization. We could have a short sentence explaining...

The statement in first bullet is not accurate, as we may as well declare that `https://spdx.org/a/3.0.x/b` is the same as `https://spdx.org/a/3.0.y/b` in the ontology.

I think the "changes" should start with much more general view, talking about how we went from SpdxDocument to general data, leaving behind the Package/File/Snippet types but introducing dozens of...

No, there is no need for custom IRIs for these individuals. Every class, property, individual gets an automatic IRI. These are perfectly fine for almost all cases. In this case...

I still maintain that this is not needed and should be closed.

Yes, we should, but we don't even publish the ontology yet, @bact. The simple `.ttl` that we generate will be further processed and generate a whole website, like https://spdx.org/rdf/terms/ After...

The incompatibility between SPDXv2 and SPDXv3 is by design: we had to make breaking changes, that's why we moved to a new major release number. So `http://spdx.org/rdf/terms#checksumAlgorithm_sha1` and `https://spdx.org/rdf/3.0.1/terms/Core/HashAlgorithm/sha1` are...