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
- Open PRs ...ready to go?
- Authorization issues to be decided upon
- Deadline for "completing" webac section:
- all 5 sections covered by end of Aug
- "Sprint" on AuthZ until Jul 26th
- Deletion-related issues to be decided upon
- Recursive delete is not required
- Require use of headers to indicate capability
- 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
- 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
Minutes
- Open PRs
- Esmé will create a new PR incorporating agreed-upon language from https://github.com/fcrepo/fcrepo-specification/pull/137
- Andrew created issues for the differences between the SOLID guidelines and the current implementation.
- Will create a delta doc
- Re: #163: Simeon will create a PR to add language about always having a Link rel="acl" and using the default
- Re: #166: Do we need WebIDs, or are any URIs enough?
- Any URI should be enough, dereferencing etc. are not required for WebAC to work
- Re: #168: Referencing ACLs/groups outside of the repository — we should add a non-normative note about this
- Maybe add an item to the security considerations section too?
- Re: #164: There is a note about webac:defaultForNew being renamed to webac:default, but not when
- Simeon will ask if/when this will be changed so we can know which we should use
- Andrew will start moving them forward — provide feedback on the issues before Friday
- Deletion
- We have agreed that recursive deletion isn't required, and headers should be used to indicate capability
- Sticking point is what does containment, and atomicity (should be handled in atomic operations spec)
- Ben will check with Hydra stakeholders about expectations for recursive deletion
- Danny will open a PR to add non-normative note about atomicity not being guaranteed, and that the Depth header should be respected
- Multiple implementations
- We should work towards cultivating other implementations, including aligning the Modeshape impl. with the spec, Cavendish, etc.
- Test suite
- Need to be able to run with different implementations in different languages, environments, etc.
- Don't want to conflict with Java projects' dependencies
- Don't want to require non-Java projects to setup Maven just to run the test suite
- Andrew will contact the contractors about scoping and specifying work
- Need to be able to run with different implementations in different languages, environments, etc.
Action Items
- Simeon Warner to close out https://github.com/fcrepo/fcrepo-specification/issues/122
- Simeon Warner to write issue about test suite language → https://github.com/fcrepo/fcrepo-specification/issues/159
- All to read up on https://fcrepo.github.io/fcrepo-specification/#resource-authorization and SOLIDWEBAC
- Andrew Woods to suggest way forward for fleshing out https://fcrepo.github.io/fcrepo-specification/#resource-authorization section
- Esme: create a new PR incorporating agreed-upon language
- Andrew: create delta doc for WebAC changes
- Simeon: create PR addressing #163, adding language about always including Link rel="acl" header and using default
- Simeon: ask about timeline for updating webac:defaultForNew to webac:default
- Ben: ask Hydra stakeholders about recursive deletion expectations
- Danny: open PR to add non-normative note about atomicity not being guaranteed, and that the Depth header should be respected (not ignored)
- Andrew: work with contractors to scope and specify TCK work