Time/Place
- Time: 2:30pm Eastern Time US
- Dial-in Number: (712) 775-7035
Attendees
(facilitator)
(notetaker)
Agenda
- Open PRs ...ready to go?
- https://github.com/fcrepo/fcrepo-specification/pull/154
- https://github.com/fcrepo/fcrepo-specification/pull/155
- https://github.com/fcrepo/fcrepo-specification/pull/156
- https://github.com/fcrepo/fcrepo-specification/pull/158
- Establishing a plan for landing this effort by Nov 2017
- How do we want to systematically approach spec revision?
- Test compatibility suite
- Aligning Fedora4 with the specification
- At least one other implementation of the specification
- Cavendish discussion
- Option for implementation of test suite - contractors
- Contractors have been contacted and are interested... even if Python
- Define initial scope of work
- Follow-up on: https://github.com/fcrepo/fcrepo-specification/issues/111
- Deletion-related issues
- Branding as Core Specification https://github.com/fcrepo/fcrepo-specification/issues/122
- Respec license
Minutes
Plan for landing the spec
- Target AuthZ first
- Look at F4 impl choices, and decide if they go in the spec or not
- We all decide to look at that section
- Action: Andrew to create some finer-grained issues for webac
- or create a more expansive draft spec
- Action: all to read solid-webac doc
- Deadline for "completing" webac section:
- all 5 sections covered by end of Aug
- "Sprint" on AuthZ until Jul 26th
Contractors
- Better error output from tests: What was request, what was response, and what requirement was tested
- Provide LDP spec to contractors
- Provide Fedora API documentation to contractors
- Initial test: Resource Management - GET, HEAD, POST
- Initial tests should be limited to things that Fedora impl already does
- Action: Simeon to create github issue for language of compatibility tests
Delete
- #136, do we need to specify
- Recursive delete is not required
- Require use of headers to indicate capability
- Action: Danny to raise delete topics on Slack tomorrow
Branding
Action Items