Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

In back-matter, for a resource, the rlink/hash/@value is required, not optional #42

Open
aj-stein-gsa opened this issue Oct 22, 2024 · 0 comments

Comments

@aj-stein-gsa
Copy link

aj-stein-gsa commented Oct 22, 2024

Hello per discussion and review of a user report around FedRAMP constraints and the oscal-cli in GSA/fedramp-automation#787, we determined that the documentation generation pipeline for the OSCAL-Reference model outlines and index of fields incorrectly indicates that the back-matter/resource/hash/@value is not [0 to 1] but rather 1. The processing of fhe json-value-key in the documentation is being incorrectly processed to be an optional field or flag in some way, but it is not.

https://github.com/usnistgov/OSCAL/blob/v1.1.2/src/metaschema/oscal_metadata_metaschema.xml#L930

https://pages.nist.gov/OSCAL-Reference/models/v1.1.2/complete/json-outline/

https://pages.nist.gov/OSCAL-Reference/models/v1.1.2/system-security-plan/json-reference/#/system-security-plan/back-matter/resources/rlinks/hashes/value

image

I am not sure what proper fix is needed in the metaschema-xslt pipeline per the sub-module version defined in the code infrastrcture here and called by generate_modeldoc.sh by the Makefile, to resolve this issue and how systemic it is, but I can help further troubleshoot and debug fixes accordingly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Needs Triage
Development

No branches or pull requests

1 participant