Arthit Suriyawongkul

Hi @naruoga, I'm Art. Thank you for the review. As the PR is already approved for its structure. With the approval from the native speaker, we will merge this. Looking...

Compare to https://github.com/spdx/spdx-spec/pull/1114#issuecomment-2336501830, it is safe to merge this PR, as the publication CI will not get triggered. (The current [development/v2.3.1/.github/workflows/publish.yml](https://github.com/spdx/spdx-spec/blob/development/v2.3.1/.github/workflows/publish.yml) will only triggered when the merge is from development/v2.3,...

Need to update the publish CI to new branch names first (see PR https://github.com/spdx/spdx-spec/pull/1172), before this PR can go further. Update: the PR #1172 is merged already.

I have checked the CI of 2.3, it uses mkdocs without mike. Which means it will not recognize other versions of spec and there's a possibility that it can overwrite...

Need to update the publish CI to new branch names first (see PR #1172), before this PR can go further.

https://spdx.github.io/spdx-spec/v2.3/how-to-use/ the bullet list got fixed now

Thanks. Then, do we need to update the diagram? 

Reviewed during 2025-04-08 Tech Team meeting .

Update tools-java version to 2.0.1

We might abandon this PR if we can generate the Python code from the model ontology file (I have learned from Gary that there's a work under going for that)....