Michaela Iorga

@rsherwood-nist - This PR is marked as WIP, but reviewers are assigned. Please clarify - is the PR ready fro review ? Thank you for your contribution.

@rsherwood-nist & @selenaxiao-nist - Can we please discuss the intent of this PR. The PR removes the branch-check that limited the "build, test and deploy SNAPSHOT code" job to the...

> @iMichaela any update on these changes, particularly [#2111 (comment)](https://github.com/usnistgov/OSCAL/pull/2111#discussion_r1979732071)? At this juncture, we may have to consider the publication of alternate models in a fork to finalize an upcoming...

> @iMichaela I proposed a new ID because I have not heard back with a proposal, so I just made one in [#2111 (comment)](https://github.com/usnistgov/OSCAL/pull/2111#discussion_r2017054886). Can you let us know because...

> > @aj-stein-gsa - I have something to finish now and will work on PRs later today and continue tomorrow afternoon. What is your schedule? Let's try to work toward...

@Telos-sa - can you please provide the version of the `oscal-cli` you are using. I am assuming it is a FedRAMP constraint. While a better implementation is desired, we would...

How will extensions be noted when the regex pattern "^[0-9]{3}[0-9]{1,12}$" is used? Also numbers with prefixes marked with () ?

NIST `oscal-cli` latest release is v1.0.3. The version you point out to was generated not by NIST so we have no control over the OSCAL metaschema definitions (models) used to...

Since many numbers can be noted with extensions that need to be documented with the phone number, or other, a with a + sign in front for international numbers ,...

> Noting in passing that the current `metaschema-xslt` also has a prototype implementation of constraints checking under XSLT. It is 95% feature-complete and testable, regex-matching being one of the things...