Dial In Details
Date: Friday September October 9, 2pm EDT (-4 UTC)
- U.S.A/Canada toll free: 866-740-1260, participant code: 2257295
- International toll free: http://www.readytalk.com/intl
- Use the above link and input 2257295 and the country you are calling from to get your country's toll-free dial-in number
- Once on the call, enter participant code 2257295
Meeting Goals
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
Attendees
Agenda
- Ratify initial list of "what to distill from use cases". (Aaron Birkland)
- Refined validation use cases from Stefano Cossu
- Introduction and discussion of composite extensions use case (Unknown User (acoburn))
- Role of API-X for supporting transactions (??)
- Actor models - having the API-X (or an extension) be an actor
- Transactions as a core feature of the Fedora 4 platform
- Any Other Business
- 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)
Previous meeting agenda, including minutes
Minutes
