W3C home > Mailing lists > Public > public-rww@w3.org > April 2014

Fwd: Access Control Charter

From: cr <_@whats-your.name>
Date: Sun, 27 Apr 2014 15:50:35 +0000
To: public-rww@w3.org
Message-ID: <20140427155035.GA20282@p.clearwire-wmx.net>
some people like to write text on mailinglists, others code..

https://github.com/linkeddata/ldphp/blob/master/www/inc/class/WAC.php

am curious what constitutes the "essence" of WAC and what is implementation-specific.

"going recursive" up parent paths.. we well know URIs in RDF are opaque yet URIs have a hierarchical-part and those might be mapped to POSIX paths - where ldphp may have exited on an explicit allow, POSIX might have denied a similar situation due to a mode 700 several parents up. 

there's the nod to "root" with the "domain owner"..

LDP Containers and container-level permissions could be an optimization to avoid running 50*3 SPARQL queries, providing all 50 resources are within a container.. chances are any container-hierarchical-permission-inheritance stuff is defined in WAC at a LDP level and not POSIX dir level anyways..

any other implementations to look at? Stample's Scala is going to take a bit for me to get me head around its wizard-levels of abstraction
Received on Sunday, 27 April 2014 15:51:05 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:40:09 UTC