oscal-content
oscal-content copied to clipboard
ssp model - metadata - actions - system
For the actions element, it requires a system URI. Can additional details and/or examples be provided to understand how this should be leveraged.
As an example, the FedRAMP SSP (legacy document version) contains a section for the approvals. There are no type elements, though this may be part of the revision history. Also, assuming the system is the internal system used to track the changes to the SSP, customers may be hesitant to release. So understanding this requirement and how it should be leveraged to meet the current use cases would be helpful.