Oscal issue678 milestone3 enhancements #54
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Committer Notes
This PR addresses functionality gaps in Metaschema for OSCAL Milestone 3 as described in usnistgov/OSCAL#678.
The second gap identified had already been addressed by PR #13 and will also be in next-gen Metaschema.
The first requirement is support for an actual (lexical) JSON data type for a "uuid". Note: currently, we do not validate the uniqueness of UUID values or indeed (always) ID values in the generated schemas. This support is so far only for the lexical form of a string (flag or field value) expected to be a UUID.
All Submissions:
Changes to Core Features: