Arthit Suriyawongkul

Will rework on this but publish it from the new `support/3.0` branch

Thank you. I will try to see what we can do with tools-python. May be we can propose them to use a binding from shacl2code.

https://github.com/spdx/spdx-python-model is a new alternative. It provides a way to manually create an SPDX 3 document, using Python. We can build an SPDX 3 file reader on top of that.

@goneall since the object models in spdx-python-mdoel and tools-python are different, there's a need to convert it - if we want to get benefit from SPDX 2 SPDX 3 translation...

The initial code for SPDX 3 reader -> NTIA minimum elements (utilizing spdx-python-model) is now public at https://github.com/bact/spdx3reader . You can try the command line interface to read SPDX 3...

Thank you @goneall I will be in the call.

Related issue on redirections - https://github.com/spdx/spdx-spec/issues/1060 may related with the redirects at https://spdx.org

Proposed code are now available at repo/branches as shown in https://github.com/spdx/spec-parser/issues/132 but still need to decide where this serialized name should be displayed. HTML pages generated from those two options...

I agree that it's only relevant in the JSON-LD context and not for other serialization options, so it can be a bit "intrusive" to include this information in the main...

During [2024-07-09 Tech team meeting](https://github.com/spdx/meetings/blob/main/tech/2024-07-09.md?plain=1), towards the very end in the context of an updated spec parser, there is a discussion about the availability of this serialized name. There's no...