Open aj-stein-nist opened 2 years ago
Some ideas towards this are implicit in my profile import examiner application. It tests some of the constraints on profiles, specifically referential integrity (on the assumption of particular catalog or profile imports).
User Story
As an OSCAL tools developer, in order to clearly understand how to define
profile
elements in a coherent way that effectively and correctly is executed by a specification-conformant profile resolution tool, I want OSCAL constraints that will give me informational, warning, and error information when a profile uses bad syntax or resolution patterns that are problematic.Goals
This idea was surfaced in a model review meeting when reviewing one item in the PR around this as part of usnistgov/OSCAL#1066. It is not clear if this completely viable and desirable (pending prioritization).
The goals of this spike:
id
s of constraints back to profile resolution requirement IDDependencies
N/A at this time.
Acceptance Criteria