[Feedback]: Rename resolution-resource prop to fedramp-version and have one prop in metadata

[vmangat]

This is a ...

request - need something additional provided

This relates to ...

• [X] the FedRAMP OSCAL Registry
• [ ] the FedRAMP OSCAL baselines
• [X] the Guide to OSCAL-based FedRAMP Content
• [X] 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

What is your feedback?

Replace the resolution-resource prop with a single prop fedramp-version. This will prevent having to create a backmatter resource and having to provide multiple additional props. FedRAMP will be able to determine based on the fedramp-version, how the file needs to processed and validated across the many layers of the specifications.

This simplifies the generation and import of the SSP files for tools.

Where, exactly?

https://automate.fedramp.gov/documentation/ssp/3-working-with-oscal-files/

Other information

No response

[aj-stein-gsa]

Can you explain why /system-security-plan/metadata/version is not acceptable? If you are amenable, it would be great to hear more about the answer to that question, if not here, in the Implementer's Meeting tomorrow if you will attend, @vmangat.

[vmangat]

the version field in the metadata is used for document versioning and is correlated with the version history of the document itself, we cannot use that to specify fedramp version