- From: Ashok Malhotra <ashok.malhotra@oracle.com>
- Date: Wed, 06 Aug 2014 16:34:46 -0400
- To: public-ldp-wg@w3.org
Some quad stores provide access to individual triples. I know that Oracle allows that and our product folks would like to provide access control at the triple level. Thus, I am reluctant to remove this requirement. All the best, Ashok On 8/6/2014 2:11 PM, Sandro Hawke wrote: > On August 5, 2014 5:52:45 AM EDT, Kingsley Idehen <kidehen@openlinksw.com> wrote: >> On 8/5/14 10:02 AM, henry.story@bblfish.net wrote: >>> On 4 Aug 2014, at 23:32, Ashok Malhotra<ashok.malhotra@oracle.com> >> wrote: >>>>> Henry: >>>>> We decided to remove access control for attributes (parts of >> triples) >>>>> We did not discuss removing access control for triples. >>>>> We can discuss this if you wish. >>> I don't see how you can do access control on parts of triples at all. >>> >>> The argument as I understand it is that one can only give access or >> not >>> at the HTTP layer to a resource. What state of the resource you show >>> is another topic: call it filtering. That could be an orthogonal >> spec. >>> It is best to keep things simple and distinct to arrive at a >> consensus. >>> Henry >>> >> +1 > +1 > > >
Received on Wednesday, 6 August 2014 20:35:19 UTC