Tim, I'll admit to being a bit confused. Here is at least what comes to mind for this area. Have you studied Hollenbach's work? He developed a widget library for privacy aware policy using ACL, WebID, and FOAF. http://dig.csail.mit.edu/2010/rdf-widgets/thesis.pdf In terms of granularity of access, I believe that they did not allow permissions on particular triples, but on documents containing them. Also see more about ACL and RDF by Hollenbach here: http://dig.csail.mit.edu/2009/Papers/ISWC/rdf-access-control/paper.pdf In addition, see SPARQL/Update, which is an update language for RDF graphs. http://www.w3.org/TR/sparql11-update/ A broad overview is here: http://www.w3.org/DesignIssues/CloudStorage.html The last link you linked to. -Brent Shambaugh Website: bshambaugh.org On Wed, Jul 2, 2014 at 1:17 AM, Tim Holborn <timothy.holborn@gmail.com> wrote: > Nice. > > Thankyou for the heads-up… > > MANU: your views / please review? > > On 2 Jul 2014, at 3:50 pm, Renato Iannella <ri@semanticidentity.com> > wrote: > > > On 1 Jul 2014, at 18:13, Timothy Holborn <timothy.holborn@gmail.com> > wrote: > > So, in a roundabout way - i wanted to ‘pitch’ a broad brushed concept of > how privacy/loyalty data permissions might be described using both a > creative commons *like* format; and, FOAF. > > > The W3C ODRL Community [1] has developed such a "permission" language > (actually a Policy Ontology [2] ) which could address the use cases your > outlined as its model [3] has been developed specifically for this purpose. > > > Cheers... > Renato Iannella > Semantic Identity > http://semanticidentity.com > Mobile: +61 4 1313 2206 > > [1] http://www.w3.org/community/odrl/ > [2] http://www.w3.org/ns/odrl/2/ > [3] > http://www.w3.org/community/odrl/work/2-0-core-model-constraint-draft-changes/ > > > >
Received on Wednesday, 2 July 2014 13:33:11 UTC