-
Notifications
You must be signed in to change notification settings - Fork 140
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suggested naming convention for SPDX v3 files #987
Comments
From Outreach meeting 2024-07-22, OMG needs that a file should have only one extension (i.e. |
In 3.0.1, suggested name will be in "5.12 Standard data format requirements" subsection of Conformance chapter |
This information has been removed from Conformance chapter - so keeping this open until we handle serialization and documentation. |
Suggestion is to add to the https://github.com/spdx/spdx-spec/blob/development/v3.0.1/docs/serializations.md page. We can move this to 3.1 to allow for more time to discuss. |
I also vote to leave it unspecified for now, and at some point in the future (3.1?) come up with all the corresponding entries (filenames, media types, etc.) |
https://www.iana.org/assignments/media-types/application/spdx+json has a file extension as |
SPDX v2 has a suggested naming convention:
According to https://spdx.github.io/spdx-spec/v2.3/conformance/#44-standard-data-format-requirements it "should be easy to recognize in a file system without opening the file."
Will the naming convention be the same for SPDX v3?
Or do we like to have something like
*.spdx3.*
to differentiate the version?Currently, Example 13 in spdx-examples repo uses
example13.spdx3.json
This may appear in "Serialization" chapter of standard.
The text was updated successfully, but these errors were encountered: