Michaela Iorga

The Discussion #1968 is also analyzing `prop/@name` constraints error in the assessment layer (discovered in the AP and reported int he [OSCAL/Lobby](https://matrix.to/#/!KiqEhMrfjXqEyIwUMw:gitter.im/$4nGDIsK9xkIiIZoNTY2oyuiaQcWjr4KpnLMEEDTviUM?via=gitter.im&via=matrix.org&via=matrix.freyachat.eu))

I think the documentation lists prop@name="marking" as a constraint, that does not allow other values (there is no allow-others="yes" -- see oscal_metadata_metaschema.xml (line 720) ``` A label or descriptor that...

Thank you for providing the decision record. I was proposing allow-other="yes", not "no". On a brief review, the documentation link does not explain how allow-other should be processed when: -...

The allow-other="no" with and without @extension is well summarized. Thanks.

I concur with @wendellpiez's proposal of defining the constraints in separate pages. The way they are currently defined and get pulled into the Reference is confusing for many. Regarding the...

@brian-ruf has a vision and researched an extension model. My understanding (from Chris) is that in FHIR anyone can establish an extension server. Maybe the `ns` is used as a...

> Very much 💯 on the idea of helping orgs define and govern their own extensions. @wendell - I feel I need to clarify that I totally agree organizations need...

> Updated test calendars. Michaela has tested this for one of our next community meetings. @aj-stein-nist - I tested it with our team, I did not invite the entire community...

## Analysis and Summary ### Control implementation status `system-security-plan/control-implementation/implemented-requirement/by-component/implementation-status` = indicates the degree to which the a given control is implemented. The `implementation-status` is used to qualify the `status` value...

@JustKuzya - can you please provide an update on this issue. I know you were working on it before holidays.