Inventory - End of Life date datatype

[Rene2mt]

Constraint Task

Consistent with issue #813, this constraint checks that where EOL information is provided, it must be provide in date data type.

Intended Outcome

• Where the "end-of-life-date" optional FedRAMP extension property is present, the 'date' datatype must be enforced.

NOTE - Where applicable the end-of-life date must be provided; however, there is currently no way to write a constraint that detects whether this information is available for inclusion.

Syntax Type

This is optional core OSCAL syntax.

Allowed Values

FedRAMP allowed values must be defined or verified.

Metapath(s) to Content

context="//(component | inventory-item)"

<matches target="./prop[@ns='http://fedramp.gov/ns/oscal' and @name='end-of-life-date']/@value" datatype="date"/>

Purpose of the OSCAL Content

No response

Dependencies

No response

Acceptance Criteria

• All OSCAL adoption content affected by the change in this issue have been updated in accordance with the Documentation Standards.
  • Explanation is present and accurate
  • sample content is present and accurate
  • Metapath is present, accurate, and does not throw a syntax exception using oscal-cli metaschema metapath eval -e "expression".
• All constraints associated with the review task have been created
• The appropriate example OSCAL file is updated with content that demonstrates the FedRAMP-compliant OSCAL presentation.
• The constraint conforms to the FedRAMP Constraint Style Guide.
  • All automated and manual review items that identify non-conformance are addressed; or technical leads (David Waltermire; AJ Stein) have approved the PR and “override” the style guide requirement.
• Known good test content is created for unit testing.
• Known bad test content is created for unit testing.
• Unit testing is configured to run both known good and known bad test content examples.
• Passing and failing unit tests, and corresponding test vectors in the form of known valid and invalid OSCAL test files, are created or updated for each constraint.
• A Pull Request (PR) is submitted that fully addresses the goals section of the User Story in the issue.
• This issue is referenced in the PR.

Other information

Updated Metapath pseudocode to ensure FedRAMP namespace required, to match acceptance criteria description.