Process of the Anvil

[edwinvandenbelt]

After the Forge, we'll have a draft technical specification (goal). We can go over each of the endpoints until somewhere July 2027, but that's only the technical part. What should we do with the "use cases"???

Option 1: create an additional stream, just addressing the use cases (how can we align the use cases and the technical part?) Final delivery: a 'use case library', containing a consistent set of use cases. Also bridges the gap use cases - technical specification.
Option 2: bundle what we've produced until the forge, use the existing use cases of the standards (OSDM, TOMP-API, BoB, etc), remove the doubles.
Option 3: any other thoughts?

[bobvinke]

I would be a fan of option 2.

As Einar states in #39 (comment) there seem to be about 34 macro use cases. However I think we are talking about System use cases here. Where Sonia is creating business use cases.