Arthit Suriyawongkul

As an informative document, it is moved out of the spec distribution and placed here https://github.com/spdx/using/blob/main/docs%2Fusing-SPDX-short-identifiers-in-source-files.md

But it is an interesting question if we can use the license short identifier as an spdxId of a license object and expect the SPDX 3 consumer to interpret it...

CI failed because the new heading value does not matched what spec-parser expected ("Property values" vs "Property Values"): https://github.com/spdx/spec-parser/blob/3550116f10972d2398561b0d178ee7aca0e76e1f/spec_parser/loaders.py#L97-L98

> There is no need to change anything in the model files ("Profile Conformance", "Property Values", etc.). The generated section names come from templates, not the input. I am not...

It is more difficult to tell people that, "when write for spdx-spec uses sentence casing, but when write for spdx-3-model uses title casing - unless spec-parser will failed" than "just...

@stevenc-stb may be of your interest.

During development period, the redirection setup could look like: - https://spdx.org/schema/3.1/spdx-json-schema.json -> https://spdx.github.io/spdx-spec/v3.1-dev/rdf/spdx-model.jsonld - https://spdx.org/rdf/3.1/spdx-model.ttl -> https://spdx.github.io/spdx-spec/v3.1-dev/rdf/spdx-model.ttl - https://spdx.org/rdf/3.1/spdx-context.jsonld -> https://spdx.github.io/spdx-spec/v3.1/rdf/spdx-context.jsonld

I have got similar issue: I run: `git checkout --track upstream/gh-pages` Then: `git status` And got this: ```text Refresh index: 100% (7335/7335), done. On branch gh-pages Your branch is up...

#1269 may solve this, after merge + running the publication workflow once.

Thanks Gary. I will look again at this. I think there's some patterns on this. Will investigate.