...

• David Wilcox
• Andrew Woods
• Nick Ruest
• Joshua Westgard
• Stefano Cossu
• Ben WallbergPeter Eichman
• Karen Estlund
• Unknown User (acoburn)
• Jared Whiklo

...

• https://www.w3.org/wiki/WebAccessControl
• https://github.com/duraspace/pcdm/wiki#webacl
• Authorization Delegates
• http://www.w3.org/ns/auth/acl

Minutes

Facilitate Stakeholder Verification

• Enable WebAC feature in fcrepo4-vagrant
• Script the creation of resources and ACLs that correspond to stakeholder use cases
  • Stakeholders should provide additional use cases/scenarios as needed to help round out the verification

Sprint 2 Items to address

1. Allow a specific agent to CREATE a resource, but not update it
2. Currently, ACL resources are protected like other repository resources. Add special protection for ACL resources
3. Implement "agent class" support:
   1. For agent classes that are found within the repository
   2. For agent classes that are found external to the repository (stretch, do stakeholders want this?)
   3. Allow repository admins to turn of "agent class" capability
4. Implement "remote ACLs", if stakeholders view it as a priority
5. Stretch goal: acl:include

Note: Since the WebAC "specification" does not have provisions for time-based authorization, the proposal is to move logic for policies such as leases or embargoes up into the application layer. Question for stakeholders, Is that reasonable?