Page History

...

1. Ratify initial list  of "what to distill from use cases". (Aaron Birkland)
2. Refined validation use cases from Stefano Cossu
   1. Enforce validation across repository
   2. Optional validation
   3. Validation only for selected resources
3. Introduction and discussion of composite extensions use case (Unknown User (acoburn))
4. Role of API-X for supporting transactions (??)
   1. Actor models - having the API-X (or an extension) be an actor
   2. Transactions as a core feature of the Fedora 4 platform
5. Any Other Business
   1. Elliot away: 9/28 - 10/28

HydraConnect touch points

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:

• batch ingest
• locking resources

Related Resources

Design Page (with use cases outline)

...