Constraint Task

Consistent with issue #813, these constraints check that applicable inventory items (and/or components) provide the "diagram-label" FedRAMP extension

Intended Outcome

• Every inventory-item MUST have a "diagram-label" FedRAMP Extension either within the inventory-item itself, or within the component linked by the inventory-item.
• Every hardware, software, service, and interconnection component - not linked to an inventory item - MUST have a "diagram-label" FedRAMP Extension.

Syntax Type

This is a mix of required, optional, and/or extended syntax.

Allowed Values

There are no relevant allowed values.

Metapath(s) to Content

<!-- First constraint -->
context="//inventory-item"

target=". | //component[@uuid=./implemented-component/@component-uuid]"

count(./prop[@name='diagram-label' @ns='http://fedramp.gov/ns/oscal']) >= 1

-----

<!-- Second constraint -->

context="//component[not(@uuid=//inventory-item/implemented-component/@component-uuid) and @type=('hardware', 'software', 'service', 'interconnection')]"

target="."

count(./prop[@name='diagram-label' @ns='http://fedramp.gov/ns/oscal']) = 1

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

No response