This is a ...

improvement - something could be better

This relates to ...

• the FedRAMP OSCAL Registry
• the FedRAMP OSCAL baselines
• the Guide to OSCAL-based FedRAMP Content
• the Guide to OSCAL-based FedRAMP System Security Plans (SSP)
• the Guide to OSCAL-based FedRAMP Security Assessment Plans (SAP)
• the Guide to OSCAL-based FedRAMP Security Assessment Results (SAR)
• the Guide to OSCAL-based FedRAMP Plan of Action and Milestones (POA&M)
• the FedRAMP SSP OSCAL Template (JSON or XML Format)
• the FedRAMP SAP OSCAL Template (JSON or XML Format)
• the FedRAMP SAR OSCAL Template (JSON or XML Format)
• the FedRAMP POA&M OSCAL Template (JSON or XML Format)
• the FedRAMP OSCAL Validations

User Story

As a developer of OSCAL-based tools for FedRAMP documentation, I would like alignment on the properties @ns, @system and other identifier URIs that FedRAMP uses in different variations in their customization of the upstream custom models.

Goals

• Document a uniform approach in a decision record (in Update system identifier-type and FedRAMP extension namespaces - Issue 773 #774)
• Review and update constraints accordingly (in Fix constraints and constraint test files per issue #773 #828)
• Update website documentation accordingly (in Fix namespace, identifier-type and system per issue #773 automate.fedramp.gov#102)
• Update baselines and examples accordingly (in Fix constraints and constraint test files per issue #773 #828)

Dependencies

N/A

Acceptance Criteria

• All FedRAMP Documents Related to OSCAL Adoption (https://github.com/GSA/fedramp-automation) affected by the changes in this issue have been updated.
• A Pull Request (PR) is submitted that fully addresses the goals of this User Story. This issue is referenced in the PR.

Other information

1. Add reference to 774 PR for item 1 in goals