- From: Tomasz Pluskiewicz <tomasz@t-code.pl>
- Date: Thu, 18 Mar 2021 11:10:09 +0100
- To: Martynas Jusevičius <martynas@atomgraph.com>
- Cc: public-rww <public-rww@w3.org>
Martynas, In practical terms you could have a generic rule that persons can read resources in general: <John> a schema:Person . <persons-can-read> acl:mode acl:Read ; acl:accessToClass rdfs:Resource ; acl:agentClass schema:Person ; . (Or make this more specific if you want, but the use of *Class terms is important. I would like a way to fine tune the access, so that I can exclude more specific classes or individuals… Hope this makes sense Tom On 18 March 2021 at 11:05:10, Martynas Jusevičius (martynas@atomgraph.com) wrote: > Hi Tomasz, > > why would it make more sense than not having such an authorization in > the first place? :) > > Martynas > > On Thu, Mar 18, 2021 at 11:02 AM Tomasz Pluskiewicz wrote: > > > > Hello > > > > All examples I see are authorisations to grant access to given resource/class. > > > > Would it make sense to also include a predicate to explicitly forbid access? Something > like “forbidden” or “inverse" > > > > To prevent from reading : > > > > <> a acl:Authorization ; > > acl:agent ; > > acl:accessTo ; > > acl:forbidden true ; > > acl:mode acl:Read ; > > . > > > > Best, > > Tom > > > > > > >
Received on Thursday, 18 March 2021 10:10:30 UTC