We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
From @JJediny
Long term, we should harmonize is the difference between a static spec (JSON schema) from that of a responsive API (where swagger/raml excel), idk if you've had thoughts on that (e.g.): https://github.com/opencontrol/OpenControl-Editor https://github.com/GSA/codeinventory-metadata-generator
The text was updated successfully, but these errors were encountered:
I suggest this could be added now to the "future topics" section of the standards.
@JJediny Take a look at the future topics and suggest the wording to be added. (Either in this issue or in the pull request is OK with me.)
Sorry, something went wrong.
No branches or pull requests
From @JJediny
Long term, we should harmonize is the difference between a static spec (JSON schema) from that of a responsive API (where swagger/raml excel), idk if you've had thoughts on that (e.g.):
https://github.com/opencontrol/OpenControl-Editor
https://github.com/GSA/codeinventory-metadata-generator
The text was updated successfully, but these errors were encountered: