Wendell Piez

Proposed language for spec is in #1272.

@galtm [the spec under `develop`](https://github.com/usnistgov/OSCAL/blob/036e2396655c2d80d0d96a4bb1f75fbd792583be/src/specifications/profile-resolution/profile-resolution-specml.xml#L1393) should be okay see PR https://github.com/usnistgov/OSCAL/pull/1386 thanks! I also have to make functional tests for this....

Next up: - [ ] Add functional unit tests for this behavior in working branch - [ ] Make a PR for that branch - [ ] Continue prep for...

(Discussed with @david-waltermire-nist and @aj-stein-nist March 22.) A one-time fix will unfortunately not defend against slippage. There is a variety of different content formats in the OSCAL repo, including JSON,...

Rambling, but trying to be concise: - We should update ourselves the *actual* constraints being validated around strings, markup-line and markup-multiline. (Which datatypes forbid whitespace-only, like [`string`](https://pages.nist.gov/OSCAL/reference/datatypes/#string), and which ones...

@shaila309 this is work under development. We have a Schematron fork at https://github.com/usnistgov/schematron where we intend to address this. @david-waltermire-nist can update you as to its current status. In any...

@david-waltermire-nist as I noted in chat, there are (generated) files in this PR that could (should?) be removed: is there an easy way to do that? The only files in...

The latest commit is about ready, so I am marking this for review. Small/final items to come back to: - Filling in the 'reflective' link e.g. the file source (which...

@aj-stein-nist has a couple of questions/issues to float up, but not AFAIK blockers at this time. Our long-term strategy is still evolving....

This has been ready and not touched. Is there a way for me to put it back into the Triage bucket? @david-waltermire-nist @aj-stein-nist