-
Notifications
You must be signed in to change notification settings - Fork 183
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
Data type for duration #1003
Comments
Here is a list of 238 800-53r5 ODPs related to time:
|
5 tasks
This requires adjustments to the Metaschema syntax to support the necessary data types. |
david-waltermire
added a commit
to david-waltermire/metaschema-java-old
that referenced
this issue
Mar 7, 2022
…solves usnistgov/OSCAL#1132. Resolves usnistgov/OSCAL#1131. Resolves usnistgov/OSCAL#1003.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
User Story:
As an OSCAL user, I value temporal data types which conform to a standard and are suitable for automated evaluation.
Goals:
While OSCAL defines data types for dates and times, it currently neglects to define one for durations, intervals, and cadences. This allows parameters frequently used in catalogs such as "organization-defined time period" and "organization-defined frequency" to be specified quite arbitrarily, such as "every other full moon", "upon closest approach of the planet Venus", "every so often", and "a long time".
A suggestion is to adopt ISO 8601 format for duration (which is in accord with xs:duration) as a data type for duration as well as a delta relative to a date or dateTime.
Acceptance Criteria
The text was updated successfully, but these errors were encountered: