Brian Ruf

@david-waltermire-nist I agree option #2 sounds like the best balance, and agree with @wendellpiez on the need to include any expanded HTML-in-MD tagging in unit testing. While I can confirm...

Forgetting the general functionality of OSCAL fragments, there is a compelling need to manage inventory content separate from the rest of SSP content. As inventory content and component content goes...

@iMichaela while I haven't been able to regularly make the OSCAL-DEFINE meetings recently, if this topic is on the agenda for a given session, I'm happy to lead the discussion,...

[This StackOverflow Article](https://stackoverflow.com/questions/43104791/how-to-prevent-xml-wrapper-element-in-swagger-ui) seems to describe the situation and offer possible resolution. It's almost six years old, so there may be better solutions available now. In summary, it clarifies that...

2024-02-07 deferring until controls internal MVP is achieved. Moving to next sprint just to track.

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

~80% complete. Handled linting issues. Expect to complete remaining 20% plus testing in sprint 68.

I would argue that there is similarity between `@ns` and `@class` - at least in the way each is used for properties in current NIST content, and that `@class` should...

Thank you @iMichaela and @wendellpiez for your responses. It sounds like both of you are suggesting that the use of `@class` would normally be at the catalog author's discretion, which...

Assumption: Error handling will function the same way it has. No change in error handling mechanisms.