On 2/7/11 11:27 AM, Leyla Jael García Castro wrote:
Thanks Ivan, I will check to link you sent me, that would work for the
medical information case. As for the papers scenario, we would have to
build a query build on top of Virtuoso.
Think about Named Graphs as View mechanisms. You can make all sorts of
Named Graphs in Virtuoso and then associate them with WebIDs. Private
stuff goes in a Private graph which is then ACL protected. Note, how you
can use WebID to protect Virtuoso SPARQL endpoints [1].
Links:
1.
http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/VirtAuthPolicyFOAFSSL
-- How to protects your SPARQL endpoint via WebID protocol
Kingsley
Cheers,
Leyla
On Mon, Feb 7, 2011 at 4:16 PM, Ivan Mikhailov
<imikhai...@openlinksw.com <mailto:imikhai...@openlinksw.com>> wrote:
Hello Leyla,
Virtuoso supports graph-level security, as described in
http://docs.openlinksw.com/virtuoso/rdfgraphsecurity.html
but not subject-level or predicate-level, so if the application should
keep some properties private it should keep their triples in an
isolated
private graph.
If a user has read access to some data it has full read access.
Virtuoso
does not have a "filter-only" access permission. What can be used in
search criteria can also be returned. The possible workaround for
paper
could be exposing only abstracts, but it would be better to make a
query
builder that would not be able to return "hidden" data.
Best Regards,
Ivan Mikhailov
OpenLink Software
http://virtuoso.openlinksw.com
On Sun, 2011-02-06 at 18:14 +0000, Leyla Jael García Castro wrote:
> Hello All,
>
> We have some RDF files modeling medical information including
desease,
> treatment, patient name, gender, age, etc. Information related to
> deseases and treatments are public while names and so other are
> private and should be visible only to authorized users.
> Both public and private information could be used in SPARQL queries,
> but actually retrieving the private fields should be restricted. How
> can this security issue taken into account in Virtuoso?
>
> Another example is related to publications. Only subscribers
should be
> able to actually retrieve the text of a publication; however
everyone
> should be able to use those fields for querying and filter. For
> instance, retrieving authors for all those papers with "term X"
in the
> "introduction" section should be possible for everyone whilst
> retrieving the corresponding text for the "introduction" section
> should be only available to subscribers. How can I achieve that with
> Virtuoso? or SPARQL?
>
> I appreciate any help in this regard,
>
> LJ
------------------------------------------------------------------------------
The modern datacenter depends on network connectivity to access resources
and provide services. The best practices for maximizing a physical server's
connectivity to a physical network are well understood - see how these
rules translate into the virtual world?
http://p.sf.net/sfu/oracle-sfdevnlfb
_______________________________________________
Virtuoso-users mailing list
Virtuoso-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/virtuoso-users
--
Regards,
Kingsley Idehen
President& CEO
OpenLink Software
Web: http://www.openlinksw.com
Weblog: http://www.openlinksw.com/blog/~kidehen
Twitter/Identi.ca: kidehen
