Robert Sherwood

Having to account for identical names for instances of different types will make the specification more complex to create as code and use as a library. I'll add an Issue...

Good discussion of the theoretical issues over on https://github.com/usnistgov/metaschema/issues/781, but for OSCAL specifically, I have noticed that location-uuid is defined as a field and a flag, but only the field...

This proposal would solve another issue -- currently, the ComfyUI container loses all knowledge of its installed models and nodes on reboot. I attempted to solve this by having the...

Thanks for your reply. I'll open a separate issue on the ComfyUI thing - I don't want to pollute this discussion.

I will say that it's fast and fabulous and very aggressive about enforcing venvs, and does some smart things with links to reduce the disk space used for multiple copies...

I agree that there could be a significant impact for externalizing existing constraints. AJ is right that it "shouldn't" matter, but it depends on how the tools process the underlying...

> 👍 I am strongly in favor of both layering the constraint sets to make them more usable and useful, and of reducing the number of constraints in core modules...

It's also important to identify how we can use namespaces effectively for management of constraints on elements that don't include a namespace flag. Constraints on Props are easy because they...

There are (possibly) two problems here: 1. How to unambiguously identify the externally defined constraint that should apply to a given element in a Metaschema model (such as OSCAL) when...

I will do this. Thanks!