## Goal Let's finish groundwork for documentation, do code and infra work to support easier generation of supporting examples with that documentation. ## Sprint Details Sprint 78 is from 17-31 October 2023. Current board is [here](https://github.com/orgs/usnistgov/projects/25/views/2). - The board is sorted in priority order. - Although not directly related to the goal, the [#1771 spike](https://github.com/usnistgov/OSCAL/issues/1771), specifically its PR with test code and an ADR with a proposed update on how to perform profile resolution and OSCAL processing testing in an implementation-agnostic way, is important for all the team devs to understand. At least two more team members should review and approve. - The top half of the board will be to finalize planning on documentation and examples sprint (modulo how we set up the board in #1688 for #1910). - The second half of the board is moving forward imporant support work or issues that will block this upcoming doc work, so it is important, but less so than the top half the team should focus on. ### Leave or other priorities - A.J.: I will be at a conference on 17-18 Oct and have some other trainings, focusing more and more on transition plan. This sprint is my last as tech lead and team member. - Arminta: Full OSCAL - Chris: DEFINE meeting Thursday, prepping content today/tomorrow - Dmitry: 16h + Meetings - Michaela: At a conference Oct 17-19. 80% of the rest of the time will be on OSCAL (OSCAL Define, 101 included) - Nikita: According to calendar, Nikita is out all this week, and back next week. - Wendell: Available 20h or so - esp respecting XSLT pipelines - busy on Metaschema ### [B]lockers, [C]oncerns, [R]isks - [C] from Wendell: unit testing opportunities: profile resolution; OSCAL validation (different tools) - [C] data governance plan(s) - timing - [R] from A.J.: transition key responsibilites and knowledge from A.J. ### Action Items - Embrace WAIT and TOL (Take It Offline: take an important topic out of meeting into [the nist-team channel for chat](https://matrix.to/#/#usnistgov-OSCAL_nist-team:gitter.im)) - A.J. to document more on wiki and identify key resources (credentials, utilities) need for transition and interim period.
Last changed by  
 
Alexander Stein
118

Read more

oscal-cli 1.0.3 Release Brief

oscal-cli 1.0.2 is a patch release with improvements and changes that are backwards compatible, specifically updating liboscal-java and metaschema-framework dependencies to make use of the OSCAL v1.1.1 models and the underlying use of the Metaschema Framework.

2/2/2024
liboscal-java 3.0.3 Release Brief

oscal-cli 1.0.3 is a patch release with improvements and changes that are backwards compatible, specifically updating liboscal-java and metaschema-framework dependencies to make use of the OSCAL v1.1.2 models and the underlying use of the Metaschema Framework. This release also fixes a bug to properly reference embeeded resource files in the release.

2/1/2024
Demo Video script for metaschema-cli

Download from Maven

1/22/2024
Value stream issue management for usnistgov/OSCAL#1688

We propose in this draft document with a non-exhaustive list of value streams. A value stream is a thematic collection of work items, varying in scope of work by quantity or quality (large epics to small issues), but still relate to the same theme in that work. There are different kinds of work items, with some nested like epics with user stories within them. It is counter-intuitive to talk an epic nested with epics, so we will label each one as a value stream. For organizational purposes, we organize the value streams grouped by high-level use cases in OSCAL. This grouping may be beneifical to link the resulting value of work completed in a value stream to a downstream developer making OSCAL-enabled tooling.

1/5/2024
Read more from Alexander Stein
Published on HackMD