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
(facilitator)
(notetaker)
Agenda
- What are the issues that need resolution prior to June 20th?
- External content
- Please be prepared to discuss the appropriateness of closing the following issues:
- Introduction: https://github.com/fcrepo/fcrepo-specification/pull/132
- Ready for merge?
- Fixity section: https://github.com/fcrepo/fcrepo-specification/issues/100
- Clarify HEAD behavior https://github.com/fcrepo/fcrepo-specification/issues/103
- This comment seems like a constructive way of closing this issue
- Delete PR#126 waiting on Benjamin Armintor and Simeon Warner reviews
- Publication of Fedora ontology: https://github.com/fcrepo/fcrepo-specification/issues/108
- Branding as Core Specification https://github.com/fcrepo/fcrepo-specification/issues/122
- Clarify InboundReferences https://github.com/fcrepo/fcrepo-specification/issues/119
Minutes
Notes are enumerated in the same order as their corresponding agenda items:
- We'll make a milestone for all issues that need to be resolved before an initial public working draft. #129 and #130 have been identified as needing to be resolved. Also, references to the yet unimplemented TCK can remain as it much be produced before the spec goes final.
- We can close out all the external content tickets, many of which are no longer relevant. We will be reaching out to the people who originally opened the issues and asking them to close them.
- #132 is merged
- #128 is merged. #133 is pending on resolving the concerns over 'persistance' from @birkland. We can close issue 100 with #128 merged and note that #133 is still pending.
- We'll move forward on #103 by removing the restriction on payload headers as defined in https://tools.ietf.org/html/rfc7231#section-4.3.2
- Moving forward on #126 as is with remaining objections to be discussed in spin-off issues.
- We need to choose a namespace for publishing the ontology for the specification that isn't "Fedora", since that's taken by the community implementation. Suggested namespaces were http://fedora.info/definitions/spec# and http://fedora.info/definitions/fcrepo#. After much deliberation, the final choice was http://fedora.info/definitions/fcrepo#.
Previous Action Items
- Ben: Write up external content and redirect use cases
- Daniel Lamb / Benjamin Armintor: to review https://github.com/fcrepo/fcrepo-specification/pull/121
- Andrew Woods: to post to list inquiry of usage of
Content-Locationingest feature - Daniel Lamb: to write intro for https://github.com/fcrepo/fcrepo-specification/issues/95 (also bring in elements of https://github.com/fcrepo/fcrepo-specification/issues/93)
- Andrew Woods: to respond to https://github.com/fcrepo/fcrepo-specification/issues/108 with suggested resolution
- Daniel Lamb: to create PR for https://github.com/fcrepo/fcrepo-specification/issues/111
- ALL: to review following three issues prepared to come to next meeting with a plan for each
- Fixity section: https://github.com/fcrepo/fcrepo-specification/issues/100
- Clarify HEAD behavior https://github.com/fcrepo/fcrepo-specification/issues/103
- Clarify InboundReferences https://github.com/fcrepo/fcrepo-specification/issues/119
- Simeon Warner: to create a github issue re: branding and spec naming → https://github.com/fcrepo/fcrepo-specification/issues/122
New Action Items
- Andrew: Move Fixity section to the end and remove reference from Section 1
- Esmé: Update Fixity section to include persistence fixity language
- Danny: will move 111 forward, and create a separate ticket for async failures
