Migrate improved UUID support from OSCAL repo

[wendellpiez]

With PR https://github.com/usnistgov/OSCAL/pull/1158 in the OSCAL repository, we have much improved support for UUID generation using native XSLT pseudo-random-number generation.

This code is useful for use outside profile resolution.

To make this code sharable between applications, the code should be migrated as a function library into its own repository that is available more broadly.

Tasks to create the uuid library:

• [ ] ~Refit for use (consider xsl:package)~
• [ ] ~Consider / refit / design demo application~
• [ ] ~Check for dependencies and test for regression~
  • [ ] ~xslt/generate XSLTs in this repo~
• [x] Migrate XSLT for UUID generation from OSCAL repo as appropriate (i.e., https://github.com/usnistgov/xslt3-functions)
• [x] Build out / update documentation as appropriate (readmes and/or docs for site)

[david-waltermire]

This relates to usnistgov/OSCAL#1416.

[wendellpiez]

Now we have two repositories underway, with PRs in development (or soon to be):

• https://github.com/usnistgov/oscal-xslt
• https://github.com/usnistgov/xslt3-functions

The random UUID-generating functionality will go in the latter.

Any processing specific to OSCAL (not excluding profile resolution) will go into the first repository, starting with the XSLT presently in yet another repository, namely this one (https://github.com/usnistgov/oscal-tools).

[wendellpiez]

After some cleanup, copied the useful contents of the oscal-tools/xslt directory just mentioned into the oscal-xslt repo.

PRs (still in progress):

• https://github.com/usnistgov/oscal-xslt/pull/1
• https://github.com/usnistgov/xslt3-functions/pull/1

[aj-stein-nist]

Like https://github.com/usnistgov/OSCAL/issues/1416#issuecomment-1410958556, we are going to need to update around this, plot an effective set of next steps, and set expectations about what we want to do sooner or backlog for later.

[aj-stein-nist]

@wendellpiez can you schedule 60 minutes of time this week between us to work through 1) reviewing the issues and 2) potentially pairing on code changes or PR reviews to move this ball forward?

[aj-stein-nist]

@wendellpiez can you schedule 60 minutes of time this week between us to work through 1) reviewing the issues and 2) potentially pairing on code changes or PR reviews to move this ball forward?

@wendellpiez, thank you for reminding me I already scheduled this and it skipped my mind we are to meet on this topic Wednesday. 🤦

[aj-stein-nist]

Pairing to follow on this with Wendell next week alongside usnistgov/OSCAL#1416.