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

[/assessment-plan/terms-and-conditions[1]/part[3]/part[1]] The cardinality '0' is below the required minimum '1' for items matching '.[@name='objective']/prop[has-oscal-namespace('http://csrc.nist.gov/ns/oscal') and @name='method']' #278

Open
Telos-sa opened this issue Aug 23, 2024 · 1 comment
Labels
question The issue contains a question that needs to be answered.

Comments

@Telos-sa
Copy link

Identified issue terms-and-conditions part assembly is different than that of assessment-objectives, but the cardinality rules for assessment-objectives seem to still apply.

Attached generated OSCAL SAP content to review, and validation leveraging the Forked validation tool on gsa site.

AssessmentPlan.json

sap_val.txt
sap_val2.txt

@Telos-sa Telos-sa added the question The issue contains a question that needs to be answered. label Aug 23, 2024
@iMichaela
Copy link
Contributor

@Telos-sa - Thank you for pointing to this bug. I noticed it too and I raised it in the Data bites (FedRAMP) meeting so we fix it in a way that aligns with the community's expectations, FedRAMP in particular.

The place for this issue is OSCAL repository, since all constraints are defined in OSCAL metaschema.

Do you mind moving the issue to the correct repo? Alternatively, I can move it, and close it here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question The issue contains a question that needs to be answered.
Projects
Status: Needs Triage
Development

No branches or pull requests

2 participants