Date: Friday September October 9, 2pm EDT (-4 UTC)
Ratify the list of things we want to distill from use cases
Close the loop on Stefano Cossu's content and structural validation use case
Discuss the potential role of API-X for supporting transactions
Review the use case for composite (referred to as "chaining" in the previous meeting) services
Taking the API-X effort coupled with F4's direction towards a continued shrinking of the core codebase and limited scope to the core services, many conversations around "repository capabilities" naturally migrate towards API-X solutions.
That is very general, but if we establish a robust yet simple API-X framework, I anticipate it getting a lot of use.
The specific, Hydra-related use cases that came up at HydraConnect are:
Design Page (with use cases outline)
Previous meeting agenda, including minutes