29.06.2013 Views

NUI Galway – UL Alliance First Annual ENGINEERING AND - ARAN ...

NUI Galway – UL Alliance First Annual ENGINEERING AND - ARAN ...

NUI Galway – UL Alliance First Annual ENGINEERING AND - ARAN ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

A Privacy Preference Framework for the Social Semantic Web<br />

Owen Sacco and Alexandre Passant<br />

Digital Enterprise Research Institute, National University of Ireland <strong>Galway</strong><br />

firstname.lastname@deri.org<br />

Abstract<br />

In this brief article we present a Privacy Preference Ontology<br />

(PPO) that enables users to define privacy preferences for<br />

RDF data. Moreover, we also present a Privacy Preference<br />

Manager (PPM) that enables users to define privacy<br />

preferences using the PPO that grants or denies other users<br />

requesting user profile information. The PPM demonstrates<br />

how privacy preferences can be created for the Social<br />

Semantic Web.<br />

1. Introduction<br />

Many Social Web applications are being developed<br />

to allow collaboration and sharing of information with<br />

one another on the Web. The Semantic Web community<br />

suggests to structure data published on the Web using<br />

RDF [1]. Vocabularies such as the Friend-of-a-Friend<br />

(FOAF) 1 vocabulary aide to define terms in RDF data<br />

to describe what the data is about.<br />

Although the Semantic Web has added value to the<br />

Social Web, privacy still remains a concern for most<br />

Web users. Current Social Web applications provide<br />

system default privacy settings whereby users specify<br />

either to allow or deny access to their personal<br />

information to all or a group of friends in their social<br />

graph. However, users require defining more complex<br />

privacy settings to restrict specific information that may<br />

be accessed by particular friends. Therefore we created<br />

a Privacy Preference Ontology (PPO) [2] that contains a<br />

vocabulary, which allows users to define fine-grained<br />

privacy preferences to RDF data. In order to<br />

demonstrate the use of the PPO, we are currently<br />

developing a Privacy Preference Manager (PPM) that<br />

enables users to create privacy preferences, which allow<br />

or deny access to other users requesting information.<br />

2. Privacy Preference Ontology (PPO)<br />

The Privacy Preference Ontology (PPO) describes<br />

privacy preferences that can restrict access to<br />

information represented as RDF Data. The vocabulary<br />

provides the ability to restrict access to: (1) a particular<br />

statement; or (2) to a group of statements (i.e. an RDF<br />

graph); or (3) to a resource, either as a subject or an<br />

object of a particular statement.<br />

Access is restricted according to patterns which<br />

users (that want to access data) must satisfy, for<br />

instance having a particular interest or being a member<br />

of a group. We rely on the Web Access Control (WAC)<br />

vocabulary 2 to describe the access privilege to the data:<br />

1 FOAF: a vocabulary to describe user profile<br />

information - http://www.foaf-project.org<br />

2 WAC - http://www.w3.org/ns/auth/acl<br />

128<br />

either Read, Write or both. Therefore, a privacy<br />

preference contains properties defining: (1) which<br />

resource, statement or graph to restrict access; (2) the<br />

type of restriction; (3) the access control type; and (4) a<br />

SPARQL query containing a graph pattern representing<br />

what must be satisfied by the user requesting<br />

information.<br />

3. Privacy Preference Manager (PPM)<br />

One way to use the PPO ontology is to define a<br />

personal Privacy Preference Manager (PPM), providing<br />

users with means to specify preferences based on their<br />

FOAF profile. The PPM can then be used to grant<br />

privileges to requesters that want to access the user's<br />

information. Figure 1 illustrates the related concept: (1)<br />

a requester authenticates to the other user's PPM using<br />

the WebID protocol [3]; (2) the privacy preferences are<br />

queried to identify which preference applies; (3) the<br />

preferences are matched according to the requester's<br />

profile to test what the requester can access; (4) the<br />

requested information (in this case, FOAF data) is<br />

retrieved based on what can be accessed; and (5) the<br />

requester is provided with the data she/he can access.<br />

This privacy manager will not be limited to only data<br />

described in FOAF, but to any RDF data since PPO is<br />

ontology-agnostic. For instance, it can be used to<br />

restrict microblog posts described using SIOC and other<br />

ontologies used in SMOB [4].<br />

Figure 1 Privacy Preference Manager<br />

8. References<br />

[1] C. Bizer, T. Heath, and T. Berners-Lee. Linked Data - The<br />

Story So Far. International Journal on Semantic Web and<br />

Information Systems, 2009.<br />

[2] O. Sacco and A. Passant. A Privacy Preference Ontology<br />

(PPO) for Linked Data. In Proceedings of the Linked Data on the<br />

Web Workshop. LDOW’11. 2011.<br />

[3] H. Story, B. Harbulot, I. Jacobi, and M. Jones. FOAF + SSL :<br />

RESTful Authentication for the Social Web. Semantic Web<br />

Conference, 2009.<br />

[4] A. Passant, J. Breslin, and S. Decker. Rethinking<br />

Microblogging: Open, Distributed, Semantic. In Proceedings of<br />

the 10th International Conference on Web Engineering,<br />

ICWE’10, 2010.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!