Brian Ruf

@aj-stein-nist given the local-definition should only be correcting content in "the OSCAL stack" (aka other content linked to either directly or indirectly via import statements), anything that can point to...

@aj-stein-nist ideally there is existing guidance; however, if there is not, see several possible options for handling this, such as one of the following: - Ignore all whitespace around the...

I agree with @GaryGapinski on the point about there being no other explicit multi-valued `prop` values; however, there is precedence in OSCAL for using multiple `prop` fields with the same...

Made good progress on the collection of issues. This one will be addressed in sprint 68.

Per today's discussion: - The description for the `resourceUUID` parameter should be "UUID of the Back Matter Resource". This applies to: - `GET /[model-name]/{file-id}/attachment/{resourceUUID}` - `PUT /model-name]/{file-id}/attachment/{resourceUUID}` - `DELETE /[model-name]/{file-id}/attachment/{resourceUUID}`...

@pjavan hopefully the status is showing for you as in-review. I have one or two items ahead of this in the priority queue. I hope to review it today.

This looks good! Closing.

Closing as it is out of date with the revised spec.

May be a leftover artifact form when we were allowing both XML and JSON returns. Now that we are only offering JSON returns, this should be flattened.

Made good progress on the collection of issues. This one will be addressed in sprint 68.