Time/Place
- Time: 2:30pm Eastern Time US
- Dial-in Number: (712) 775-7035
- Participant Code: 479307#
- International numbers: Conference Call Information
- Web Access: https://www.freeconferencecallhd.com/wp-content/themes/responsive/flashphone/flash-phone.php
Attendees
- Andrew Woods - regrets
- Esmé Cowles - (facilitator)
- Daniel Lamb
- Simeon Warner (notetaker)
- Benjamin Armintor
Agenda
- External content
- Prioritize outstanding issues
- ...
Minutes
- External content wiki proposal seems solid and generally accepted
- Simeon: How do we decide which (undocumented) use cases are in scope, and which (undocumented) use cases are out of scope? Would be nice to have these written down as a way to decide Ben: Would use cases go in spec or supporting documentation or elsewhere?
Simeon: Not sure they go anywhere formal but just use for decisions on spec
Esme: Think they might be supporting documentation
Danny: Have tried in Islandora
Ben: Had tried to do this with #41
Danny: Have use case template and label, could do this.
Ben: Could have a procedure where part of closing a use case is a PR with a markdown file
Esme: .. but this sounds like a PR based process again
Agreed: It would be good to document the use cases behind some of the spec changes. Will have use cases directory and Danny will put in a template. Will add use cases as a PR - Wiki proposal: https://github.com/fcrepo/fcrepo-specification/wiki/External-Content
Esme: How are folks with this proposal
Danny: OK with me
Ben: Can make that work. Is it OK if you support an external body then you advertize with Accept POST on containers, else do 415 -- agreement . Will try to do the PR before next call.
- Simeon: How do we decide which (undocumented) use cases are in scope, and which (undocumented) use cases are out of scope? Would be nice to have these written down as a way to decide Ben: Would use cases go in spec or supporting documentation or elsewhere?
- Outstanding issue review
- Many of the outstanding issues seem resolved, but we need follow-up
- Messaging/notifications has a PR that needs review
- Editor list needs to be updated to reflect recent formation of this editors group
- Long discussion on https://github.com/fcrepo/fcrepo-specification/issues/43 needs to be summarized
A few tickets have asked for various kinds of clarification but lack of consensus has prevented those from moving forward
- At least adding an intro to summarize the different kinds of implementations anticipated and how they might differ could address some of those concerns
- Many of the outstanding issues seem resolved, but we need follow-up
- Next meeting
- Danny and Simeon will be out next week, so our next meeting will be 5/24/17.
Action Items
- Ben: Write up external content proposal as a PR
- Danny: Create use case template https://github.com/fcrepo/fcrepo-specification/pull/114
- Ben: Write up external content and redirect use cases
- Esmé, Danny, and Andrew will review https://github.com/fcrepo/fcrepo-specification/pull/106
- Simeon: Review and summarize https://github.com/fcrepo/fcrepo-specification/issues/43
- Danny: Draft intro text to address https://github.com/fcrepo/fcrepo-specification/issues/93 and https://github.com/fcrepo/fcrepo-specification/issues/95
- Esmé: PR to update editors section https://github.com/fcrepo/fcrepo-specification/pull/115