Clients making HTTP requests on behalf of agents (social entities) may need to be given different set of access privileges than the agents.
Considerations:
- Client is authenticated - protocol agnostic.
- Specific predicate for the client (eg.
acl:client as possibly a subPropertyOf acl:agent) vs. reuse acl:agent since the object ie. the WebID that's changing.
- Access privileges given to a client is same as agent's or can be different.
- Related but may not be relevant: whether an access subject (eg. agent, agentGroup, agentClass) delegates (
acl:delegates) a client to act on behalf of the agent.
Clients making HTTP requests on behalf of agents (social entities) may need to be given different set of access privileges than the agents.
Considerations:
acl:clientas possibly a subPropertyOfacl:agent) vs. reuseacl:agentsince the object ie. the WebID that's changing.acl:delegates) a client to act on behalf of the agent.