- From: Henry Story <henry.story@bblfish.net>
- Date: Wed, 12 May 2021 10:51:01 +0200
- To: public-n3-dev@w3.org
- Message-Id: <A03F0E39-C06B-4CF6-8DA4-EB7B62094E8A@bblfish.net>
Hi, I have a use case for an :imports relation that is somewhat close to owl:imports for access control, as described here: https://github.com/solid/authorization-panel/issues/210 See also the illustration here: https://github.com/solid/authorization-panel/issues/210#issuecomment-838747077 The idea is that the rules that apply to a resource are those that can be found in a resource linked by an HTTP `Link: <xxx.acl>; rel=acl` header. But one does not want to repeat all that information in each resource’ ACL as that could lead to a lot of duplicated RDF all around which would create a maintenance nightmare, so one wants to link to the definitions and import them. Just wondering what people thought of this here. Henry Story PS. Does anyone here have knowledge of RelBAC? I wrote up a list of links to that access control description logic https://github.com/solid/authorization-panel/issues/150 It actually seems to me that the ACL ontology is a reified version of relbac. https://co-operating.systems WhatsApp, Signal, Tel: +33 6 38 32 69 84 Twitter: @bblfish
Received on Wednesday, 12 May 2021 08:51:21 UTC