...
- Update on contract developers: API Test Suite
- PRs to review
- Authorization issues
- issue-164: acl:default instead of acl:defaultForNew resolved (solid)
- acl:default is now in the acl ontology
- Maybe nothing is required if we adopt the solid usage
- issue-165: acl:accessToClass Removing support for acl:accessToClass?
- Agreement to retain acl:accessToClass
- issue-166: resolved Requiring WebIDs?
- resolved with pr-199
- issue-167: Requiring acl:agentGroup?
- trivial, just needs a PR
- issue-168: Cross-domain Authorization?
- Needs a PR
- issue-170 thumbs and comments: Require acl:Append and acl:Control
- Needs discussion on what this would mean in practice
- issue-172 remains open: Clarify algorithm for finding authorizations
- Pending clarification from Solid
- issue-175: Should we say default ACL MUST be resolvable?
- resolved with pr-198 - needs attention
- issue-176 resolved-needs pr: ACL creation and linking -- be explicitly silent or specify?
- Needs attention
- issue-164: acl:default instead of acl:defaultForNew resolved (solid)
Minutes
Action Items
- Benjamin Armintor to ask Hydra stakeholders about recursive deletion expectations