-
Notifications
You must be signed in to change notification settings - Fork 40
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
Example filenames should be lower case?! #508
Comments
https://github.com/oasis-tcs/csaf/tree/master/csaf_2.0/test/validator/data has many upper case filenames as well. (Somehow I feel like I am missing something here.) |
@bernhardreiter I think we were missing to simplify the names as a coordinated task before producing editor revisions in PRs for adoption by the TC. @tschmidtb51 I suggest we use this feedback (issue) as feedback from public review and can then be confident that changes we do based on this feedback are considered non-material by the TC so we can ensure the CS02 (presumably following the CSD02/PRSD02) will receive these enhancements (and the repository for the parts not delivered to docs.oasis-open.org) |
- addresses parts of oasis-tcs#508 - add script to test filenames of CSAF files - add Github Action to run test script
- addresses parts of oasis-tcs#508 - rename CSAF examples - fix filenames of test files
- addresses parts of oasis-tcs#508 - update filename of template - adopt exclude list in validator run-script
This issue has been resolved and filename test has been added to check filenames an prevent mistakes. |
The csaf 2.0 filenames for the examples (as of this moment) are:
(https://github.com/oasis-tcs/csaf/tree/f5be5c83d34c24b732f01c054f6d65285922d8a0/csaf_2.0/examples)
According to https://docs.oasis-open.org/csaf/csaf/v2.0/cs01/csaf-v2.0-cs01.html#51-filename , shouldn't they all be lower case?
The text was updated successfully, but these errors were encountered: