Conversation
Signed-off-by: Marc-Etienne Vargenau <marc-etienne.vargenau@nokia.com>
bact
left a comment
There was a problem hiding this comment.
Very minor Markdown formatting suggestions.
The content is good. Thank you for putting this together.
Co-authored-by: Arthit Suriyawongkul <arthit@gmail.com> Signed-off-by: Marc-Etienne Vargenau <marc-etienne.vargenau@nokia.com>
Co-authored-by: Arthit Suriyawongkul <arthit@gmail.com> Signed-off-by: Marc-Etienne Vargenau <marc-etienne.vargenau@nokia.com>
bact
left a comment
There was a problem hiding this comment.
LGTM. Aligned with general agreement from 31 March 2026 Tech Call, see notes #1359 (comment)
If OMG sees it other way, we can of course update this later.
|
A specification, which becomes an ISO standard is not a place to have content about wishes ("should be easy") or suggestions. This is part of a Normative chapter; what does this text mean? Is it required to use these file extensions in order to conform with the specification? If not, these do not belong here. |
What if we change the context of the statement to reference the IANA media type once it is approved? Something like "SPDX JSON-LD is registered as an IANA media type XXX which is associated with the file extension .spdx3.json." |
Hi Alexios, I am sorry, but I have to disagree. In the current SPDX ISO standard, the wording is as follows: So yes the ISO standard is "suggesting". In my proposal, I tried to be as close as possible to the SPDX 2 ISO standard. |
|
Checked with ISO/IEC 5962:2021 (SPDX v2.2.1) https://www.iso.org/standard/81870.html (free to download) page 5, line 2, same wording there ("Should be easy to ..."). The text is inside "4.4 Standard data format requirements" clause. |
This solves #987