...

• 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

• Stefano Cossu
• Nick Ruest
• Jared Whiklo
• Daniel Davis
• Elliot Metsger
• Unknown User (acoburn)
• Ruth DuerrDiego Pino Navarro
• Joshua Westgard
• Bethany Seeger
• Katherine Lynch
• Andrew Woods

Agenda

1. Progress updates
   1. Design proposal docs - some ready for people to start looking at, see where there's consensus and what needs more work.
      1. Overview - includes glossary, suggests/clarifies implementation components
      2. Extension Definition & Binding - Mostly new material, investigates OWL reasoning for binding services to objects. 
      3. Execution - Addresses service invocation, 
      4. Service Discovery & Binding - Just a stub at the moment, suggests a few tweaks to the existing SD&B doc
2. Can somebody volunteer to review/critique the design docs discussed above in the upcoming weeks?  We can start implementing the good parts where there is consensus.
3. Choose concrete extension(s) to develop?, see github issue

...

• (Andrew) Documents appears to be of high quality. He feels that not much disagreement will arise against what’s being proposed in the documents. The documents captures the essence of what’s been going on for a quite a while. Suggested that instead of asking for volunteer to review, we should put out a public call for document review with a published ratified-by date, to give people a chance and a deadline to review and contribute to the ratification of design docs.  

• @ the July 7th meeting the design documents will be ratified. Call for design review and contribution could be sent out now, while noting that design docs are in draft stage.

• Some implementation could take place concurrently.

• Elliot, Ruth, a lady whose name i couldn’t hear, intent Katherine intent to review the docs

• TODO: Aaron to comment on the GitHub issues to link them to particular sections of the design documents.

• Google docs are good home for the design docs initially until a firmer vision for the design is achieved, at which time the design will be put in to markdown pages in the repository.  

• Comments on a design doc that are of a debate/opinion nature should be added as comments on the doc

...