2015-10-09 - Fedora API Extensions Meeting

Dial In Details

Date: Friday September October 9, 2pm EDT (-4 UTC)

•  NEW  Dial-in Number: (712) 775-7035
  • Participant Code: 479307#
  • International numbers: Conference Call Information
  • You may also call in using the VoIP dialer from a web browser, or Android/iOS apps
• IRC:
  
  • Join the #fcrepo chat room via Freenode Web IRC (enter a unique nick)
  • Or point your IRC client to #fcrepo on irc.freenode.net

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

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. 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
4. Think about composition of extensions for next meting?
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)

Use Cases Parent Page

Previous meeting agenda, including minutes

Minutes