- From: Serena Villata <serena.villata@inria.fr>
- Date: Thu, 18 Apr 2013 15:12:45 +0200 (CEST)
- To: Henry Story <henry.story@bblfish.net>
- Cc: ashok malhotra <ashok.malhotra@oracle.com>, public-ldp-wg@w3.org, Luca Costabello <luca.costabello@inria.fr>
Hi, > >> 4. Ability to discover the access control policy > > > > The access control module should manage that, I don't think it's up > > to the LDP server to do that. > > Why? Clients may want to know who SHOULD be able to access a > resource. If they do then they can tell > if there is a bug on the server, which is very helpful to the > resource owner, as he can be pinged about > the error. OK, I see your point. However, maybe it's better first to define what we mean by "discover the access control policy". In my mind, each policy is associated to a (set of) resources it protects. > > ACLs are just another LDP resource. There is no reason why they > should not be something one can create, edit or delete using LDP. Agreed. All the best, Serena
Received on Thursday, 18 April 2013 13:13:16 UTC