Wendell Piez
Wendell Piez
# User Story: Sometimes I need my data to point not just to a document, but to a location inside that document, as in `` to point to an element...
# User Story: So far in the OSCAL specifications we have relied on web standards for defining links (URIs and URI fragments). As long as a link is simply a...
### User Story Make a PR addressing feedback to models here: https://hackmd.io/D4W1e9bnSpq797myjrJVyQ See #1331. PR should be to the branch behind #1263. ### Goals Integrate revisions to models documentation. ###...
# Committer Notes Rough draft towards a web page addressing #1185. (PR targets `develop` pls tweak if wrong.) This may have to cycle a couple of times to get the...
# User Story: The current draft profile resolver in `develop` does not handle `oscal-version` correctly in metadata, emitting a "TODO" string. However, the specification for the desired behavior is soft:...
"Pruning" is what the profile resolution spec describes as the removal of items from catalogs to produce baselines (resolved catalogs), where those items are not wanted or needed. A typical...
This issue was surfaced by #1305. # Describe the bug The current profile resolution specification in the Modify phase needs some clarification regarding handling of ID bindings on `add` and...
# User Story: One feature is still not implemented in the new Metaschema toolkit, namely the capability to generate a Schematron that will function to enforce constraints declared in the...
# User Story: In specifying and implementing profile resolution (#508, #509) we have exposed a requirement to support tracking 'control identity' more robustly through profile resolution. This is so that...
# User Story: The XSLT profile resolver (pipeline) provided in `src/utils/util` provides only a subset of the functionality described by the [spec](https://pages.nist.gov/OSCAL/concepts/processing/profile-resolution/), enough to work for simpler baselines but not...