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
Namespace upgrade #312
Namespace upgrade #312
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm. This will likely break my approach to #309 😞 (as schemas can't be retrieved on the fly anymore). But you are totally right! And it makes more sense to test the local ones (as the might introduce breaking changes...)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sthagen @tschmidtb51 Looks good, but quick question: since I own the CSAF.io domain, would you like to simplify the namespace URI?
@sthagen We also need that change for https://github.com/sthagen/csaf/blob/b6834b0e9414a6638631b7750cafbb3f0cc54a7f/csaf_2.0/examples/ROLIE/example-01-feed-tlp-white.json#L36 Edit: Now done through 930246d. |
No. We should stick to the official OASIS namespace. But I would like to use |
Sounds good. Thank you! |
- addresses part of oasis-tcs#312 and oasis-tcs#313 - update namespace in ROLIE feed example
Added some plausible target namespace URLs for all three schema files - final URLs will be set collaborating with TC administration.
Closes #68.