...
- WebAC Spec
- What is the agent/agent class being authorized?
- What is that agent being authorized against?
- Specific resource or class of resources
- RDF type
- What mode is the agent in with respect to the resource
- Read, Write, Append, Control
- Web IDs
- Not going to implement this
- Probably not using URIs for agents at least at first
- W3C LDP working group is working on access control requirements
- Nothing here looks very divergent from what we’re talking about
- MVP
- Minimum set of initial requirements
- Question: How can we allow a user to have read/write access to anything they themselves create
- By default, after creating a resource, its creator has read/write access to that resource
- This might not be desirable in all cases
- Does every resource get a default ACL on creation?
- Or should the resource inherit whatever ACL is determined by the algorithm?
- General agreement that there is a default ACL can be created that defines owners permissions for objects they create
- How do we define an owner?
- Ontology includes namespace acl:owner
- The owner may or may not be the creator
- Do all resources have an owner? Do we need a default owner?
- The concept of an owner is not necessary for the MVP (based on feedback from those on the call - please let us know if you disagree)
- Do we need a separate permission for deleting a resource?
- Currently this falls under Write permission
- There is a use case for allowing a user to edit a resource without deleting it
- Islandora and Hydra have these use cases
- This would be a divergence from the spec
- Delete and Update would be subclasses of Write
- What is the class of an agent?
- Does this map to a group?
- For Islandora: Drupal role
- URI to a list of agents in a particular class
- Appealing but may not be practical initially
- Scheduling sprints (tentative)
- Aug. 24
- Sept. 28
- We will have another meeting at the same time next week