- From: Kei Cheung <kei.cheung@yale.edu>
- Date: Fri, 05 Jun 2009 19:54:33 -0400
- To: Helena Deus <helenadeus@gmail.com>
- Cc: Eric Prud'hommeaux <eric@w3.org>, public-semweb-lifesci@w3.org
Does named graph play a role here? For example, data (triples) generated from a project (experiment) may only be accessed by the one(s) who did the experiment (as well as the lab PI). Also, there may be multiple projects/experiments going on within a lab. The PI of the lab should be able to access data generated from all projects/experiments within the lab. Access control may be given at the experiment/project level and the lab level ... Cheers, -Kei Helena Deus wrote: > Hi Eric, > > I like your solution of using SPARQL to create views as graphs. For my > two cents on permission control in RDF, I tend to follow the premise > that every user is a URI and permission of the URI in pieces of data > are defined using some namespace such as rdf:canSee, or rdf:canEdit > I also liked your solution on using keys to building those graphs - I > tend to do the same. > > I saw that you use the XACML for defining access control. That is > interesting, I never heard about it before. It would be really cool if > I get some help from W3C on defining a set of predicates standards for > access control especially for RDF triples - for example, it would be > usefull to have some sort of owl:TransitiveProperty to allow > permissions to propagate > > Lena > > On Fri, Jun 5, 2009 at 11:03 AM, Eric Prud'hommeaux <eric@w3.org > <mailto:eric@w3.org>> wrote: > > I've been scrounging around looking for the state of the art in access > control in RDF. I'll be flushing out > http://www.w3.org/2009/Talks/0504-swobjects-ep/acls > over the next few days. If folks have input, or related presentations, > please reply to this thread. > > -- > -eric > > office: +1.617.258.5741 32-G528, MIT, Cambridge, MA 02144 USA > mobile: +1.617.599.3509 > > (eric@w3.org <mailto:eric@w3.org>) > Feel free to forward this message to any list for any purpose > other than > email address distribution. > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.1 (GNU/Linux) > > iQEVAwUBSilB7pZX2p1ccTnpAQKdTgf/aGOZ1EJFur8dU01rRo84i8Fg7U3LTNfZ > 4sycaH2w7CpjcUG113H/Dh75Q/y53WQvH+pFk6iPcg8FtKPW/lWnf8Hp/uDA9XwP > /5ubX3Ld1m94FyIzGybZ5aBvVkDBUWib03N2TrH3vMD4kFhy3GCHQ8Jud+uvgc0P > SBGkN9uXjqk15fIUJH+VN881hRJRWwA4ftlH3orU3ideSaGBJ8u1t5tZZJtEeA0l > ksbGrmv12PtNuKx1SRJkAonG+mQhi65bmTlAIPW5I95kSL0Wg5AAlliZHqwLiIpM > ecMZjFEkMveyypIUeOjYnogJWHfF6g8kbvXqMg0l05GWNrD3K4e04Q== > =uHh4 > -----END PGP SIGNATURE----- > >
Received on Friday, 5 June 2009 23:55:14 UTC