• 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

Attendees

• Nick Ruest
• Jared Whiklo
• Daniel Davis
• Elliot Metsger
• Unknown User (acoburn)
• Ruth Duerr
• Joshua Westgard (cannot attend due to conference travel)
• Bethany Seeger
• Katherine Lynch –> going to be late if able to attend – left my comments/suggested edits in the docs for review.
• Andrew Woods
• Stefano Cossu
• Diego Pino Navarro
• Hanh Vu

Agenda

1. Design docs - consensus that these are OK?  good to commit to GitHub?
   1. Follow up on #30 - Does API-X necessarily have to guarantee ontology resolution
   2. Follow up on #5 persisting data in repository.  Some open questions
      1. Can/should/must/ API-X be able to persist objects to the repository for its own purposes?
      2. Can/should/must API-X be configurable to specify a particular container (or containers) to inspect for API-X-related objects (service and extension definitions, ontologies, etc)
2. High level overview doc (#29)
3. Other updates
1. Unknown User (acoburn) and Bethany Seeger have started creating extension impls aligned with the current design draft
   1. These extension impls expose extension definition documents in OPTIONS body on service URI.  Should this be a pattern generally supported by API-X?  Required? 
2. Aaron Birkland has started implementing #10 and #12