Time/Place

This meeting is a hybrid teleconference and IRC chat. Anyone is welcome to join...here's the info:

• Time: 11:00am Eastern Daylight Time US (UTC-4)
• 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
• IRC:
  
  • Join the #duraspace-ff chat room via Freenode Web IRC (enter a unique nick)
  • Or point your IRC client to #duraspace-ff on irc.freenode.net

Attendees

• Andrew Woods 
• Ed Fugikawa
• Stefano Cossu 
• Unknown User (escowles@ucsd.edu)
• Jared Whiklo
• Eric James
• Yinlin Chen
• Michael Durbin
• Chris Beer

Agenda

1. Major refactoring underway
2. Workspaces use-cases?
3. AWS Clustering
4. Authorization Header Provider

Minutes

Recent refactoring

• Aligning with LDP
• Cleaning dependencies and unused methods

• REST-API will be updated, on the order of:

  Under the new LDP model, you have a resource /a, and a bytestream at /a/b
  .. when you GET /a/b, you get the bytestream
  .. and /a/b is described by some other resource (the triples  that used to be at /a/b), say, /a/b/fcr:metadata
  .. and you can PUT bytestreams to /a/c, and get them stored there. (right now, you'd get some 400 Bad Request exception)

• Esme will be updating java-client based on recent impacts

Workspaces

• AIC uses non-default workspace name
  • Potentially, has interest in having multiple workspaces
• UCSD, also has potential interest in using multiple workspaces
  • But could likely live without workspaces
• Could be useful for multi-tenancy

Clustering

• AWS does not support UDP broadcasting of cluster node membership
• An alternate approach is to configure cluster nodes to read-from/write-to an S3 bucket for node addresses
• Yinlin to continue investigations

Authorization Header Provider

• AIC interested in defining multiple auth headers
  • Will experiment with defining multiple Spring beans of the type: HttpHeaderPrincipalProvider
  • Will report to the list on outcomes

OAI Provider

• As mentioned last week, two issues need to be addressed before the oai-provider project is ready for community review:

  1. Determine/Define appropriate predicates to describe OAI relationships
  2. Determine how to extend dc-generator or other mechanism for generating basic OAI-DC content
• As for the first item, predicates, Esme has offered to create a separate namespace that could be published alongside the Fedora ontology