Closed azaroth42 closed 7 years ago
Ping @hybox/drs-team:
Unless you have further guidance, we'll run with Accounts being a required model and linked to Persons (or other Agents like Organization or SoftwareApplication). Please let us know any requirements, otherwise we'll take a best guess :)
:+1:
This image is a sketch of the Agent, Account, and ACL models. Note that the ACL/Auth relationships (the bottom right) is slightly flattened in the drawing. The full structure is as documented at WebACL.
In summary:
foaf:Account
s are used for sign-on/identification; they are sioc:account_of
foaf:Agent
.
dc:creator
) may be the same person, so we make no distinction between these Agent types.org:memberOf
foaf:Group
.acl:agent
which is an Agent, or an acl:agentClass
which is a Group.@azaroth42, @awoods we talked a bit about the IP authentication use case: do we want to consider the possibility of using acl:trustedOrigin
for these kinds of cases?
:+1: to the write-up above
Diagram of above whiteboard:
This issue can be closed when the above documentation is available in models/permissions.md.
@azaroth42, @awoods we talked a bit about the IP authentication use case: do we want to consider the possibility of using
acl:trustedOrigin
for these kinds of cases?
acl:trustedOrigin
doesn't exist in the BasicAccessControl vocabulary yet. I'm creating a new issue to track IP-based auth.
Closed by #54
Should model the following:
Use cases: