nikitawootten-nist

> I just sent an email, but I attended the OSCAL Mini Workshop and was told to ask for access to TypeScript repository here. I would be interested to see...

@wendellpiez @aj-stein-nist I sent you both a calendar invite for Wednesday to discuss.

Next steps: @wendellpiez and I are going to: - Adjust the doc generation pipeline to exclude the "Switch to ..." button and collapse headings by default (@wendellpiez) - Set up...

@wendellpiez until I have a more permanent home for this script in the OSCAL repo, refer to the script we'll be using to test here: https://gist.github.com/nikitawootten-nist/76dfdb45ad68f7d49c396780c90dbf63

As an update, I realize that the work on this issue may have reached far afield of the original intention of the issue, so I'd like to provide a simple...

Another note, the removal of the "Switch to XML/JSON" buttons did not yield any meaningful performance gains, signalling that #1369 may not be a meaningful next step

Hi all, I'm excited to see renewed interest in this issue. @aj-stein-nist is out this week, but I'm sure he'll be able to provide a update when he's back.

I'll take this one over. As someone who has no idea how the XSLT profile resolution workflow works, I can probably understand the audience.

I'll be working out of the develop branch, thanks. @galtm Unless https://github.com/usnistgov/OSCAL/pull/1639 merges before I am done, I'll also add a note specifying that Saxon 11 and 12 are not...

Also contingent on #1639, I added a nice helper script that should assist users living in https://github.com/nikitawootten-nist/OSCAL/blob/nikitawootten-nist/issue1178_wrapper-script/src/utils/util/resolver-pipeline/oscal-profile-resolve.sh