-
Notifications
You must be signed in to change notification settings - Fork 124
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/local-definitions[1]/objectives-and-methods[1]/part[2]/prop[1]/@name] Value 'method' doesn't match one of 'alt-identifier, label, marking, or sort-id' at path '/assessment-plan/local-definitions[1]/objectives-and-methods[1]/part[2]/prop[1]/@name' #277
Comments
When testing without the prop, get a cardinality issue. Cannot identify the structure discrepancy |
@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. Do you mind moving the issue to the correct repo? Alternatively, I can move it, and close it here. |
@iMichaela If you could move it, that would be helpful, and drop us a line as to where we should place these. We are starting to ramp up on the FedRAMP validation pilot, so there will be elements coming through from all of the models. Let me know what the best practice should be for this, so we can sort these issues appropriately. |
Hi Lacy - those are all OSCAL schema issues and the OSCAL repo is the place for this kind of bugs. In this repo we only keep the artifacts in OSCAL. Wishing you and Telos team the best of luck with the pilot. |
@Telos-sa - On a more careful review of the With that said, I am guessing you are alluding to a known constraints bug that requires a fix in the OSCAL metaschema definitions. Here is the SAP file demonstrating it:
I moved this to the usnistgov/OSCAL#2059 bug in OSCAL repo and close it here. |
Validation error seems to conflict with cardinality rules for assessment-method. Located in Local Definitions.
What was validated
Cardinality rules from Model seems to indicate the structure is correct.
Can you please provide guidance in determining our error:
The text was updated successfully, but these errors were encountered: