[3.1-RC1] Editorial cleanup: documentation and annexes (7.1)

[henrylyons]

Affected Sections: docs/, front/, annexes/

Feedback
Low-risk editorial corrections (typos, grammar, casing, outdated references).

Suggested Change:

Section	Issue	Suggested fix
docs/ (OMG submission text)	Wrong version 'Specification Version 3.0.1'	Replace 3.0.1 with 3.1
front/introduction.md	Final paragraph still references 3.0.1	Update to mention 3.1
docs/references.md	Broken White House executive-order URL (404)	Replace with a stable, valid URL
docs/references.md	'Software Bill of Material' missing final 's'	'Software Bill of Materials'
docs/annexes/rdf-model.md	Extra word 'in'	Remove 'in'
docs/terms-and-definitions.md	No hyperlink for CNSSI 4009-2015	Add a hyperlink
examples/jsonld/converted_from_spdx_2.json	Comment says converted to SPDX 3.0	Update to '...converted to SPDX 3.1'
docs/serializations.md (Canonical)	Says 'two characters' but enumerates three	Correct to 'the following characters'
annexes/spdx-lite.md (CreationInfo)	specVersion rule '3.1.n' is ambiguous	Clarify with a regex/example, e.g. ^3.1.[0-9]+$
annexes/spdx-lite.md	Inconsistent specVersion: '3.1.n' vs '3.1'	'3.1 or a supported 3.1.n patch version'
annexes/spdx-lite.md (NameSpaceMap)	Invalid casing NameSpaceMap	Correct to NamespaceMap
annexes/spdx-lite.md (homepage)	Invalid casing homepage	Correct to homePage
annexes/spdx-lite.md	'should be objects' - shall vs should unclear	Clarify the normative intent
annexes/spdx-lite.md	'BlankNode' meaning unclear	Clarify
annexes/spdx-lite.md	'and is composed of 4 fields' - only 2 required	'composed of either 2 or 4 fields'
annexes/license-matching-...md	Example (?i:copyright.{0,200}). is not POSIX ERE	Change the example or broaden 'match' to include PCRE
docs/serializations.md	'ordered by name' lacks collation/algorithm	Define or reference a sorting algorithm

Notes:
This feedback was provided by Microsoft at the SPDX working group meeting on June 30, 2026.

[bact]

All of these are in spdx-spec repo. Should move there.

[bact]

docs/ (OMG submission text):

• Wrong version 'Specification Version 3.0.1' -- false positive. It has to be 3.0.1. We never submit 3.1 to OMG.

front/introduction.md:

• Final paragraph still references 3.0.1 -- false positive. That paragraph is specifically about 3.0.1:

  Since the release of 3.0.0, we have gathered feedback on the level of documentation and minor errors in the model which have been addressed in the 3.0.1 release.

  We can revise the paragraph for 3.1 or remove the entire paragraph. But do not just replace "3.0.1" with "3.1"

docs/references.md:

• whitehouse.gov dead link - to fix by References: Fix EO 14028 dead link #1444
• 'Software Bill of Material' missing final 's' <-- the spelling is verbatim to the ref title "Types of Software Bill of Material (SBOM) Documents" https://www.cisa.gov/sites/default/files/2023-04/sbom-types-document-508c.pdf

docs/annexes/rdf-model.md:

• Extra word 'in' - to fix by Model annex: typo - remove extra "in" #1446

docs/terms-and-definitions.md:

• No hyperlink for CNSSI 4009-2015 - to fix by Add link for CNSSI 4009 #1447
  • Web browsers will report that the page is insecure

docs/serializations.md (Canonical):

• Says 'two characters' but enumerates three / Correct to 'the following characters' - to fix by Revise Strings in Canonical serialization #1448

docs/annexes/spdx-lite.md:

• Invalid casing NameSpaceMap, Invalid casing homepage, 'should be objects' - shall vs should unclear - to fix by Lite: fix typos/casing #1445

docs/annexes/license-matching-guidelines-and-templates.md:

• "'and is composed of 4 fields' - only 2 required" and "Example (?i:copyright.{0,200}). is not POSIX ERE" - to fix by Fix POSIX ERE in SPDX License List matching guidelines #1449