<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Data Privacy Vocabularies and Controls: Semantic Web for Transparency and Privacy</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Piero A. Bonatti</string-name>
          <email>piero.bonatti@unina.it</email>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Bert Bos</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Stefan Decker</string-name>
          <email>decker@informatik.rwth-aachen.de</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Javier D. Fernandez</string-name>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Sabrina Kirrane</string-name>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Vassilios Peristeras</string-name>
          <email>v.peristeras@ihu.edu.gr</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Axel Polleres</string-name>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Rigo Wenning</string-name>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>International Hellenic University</institution>
          ,
          <country country="GR">Greece</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>RWTH Aachen University</institution>
          ,
          <addr-line>Germany</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Universita` degli Studi di Napoli Federico II</institution>
          ,
          <country country="IT">Italy</country>
        </aff>
        <aff id="aff3">
          <label>3</label>
          <institution>Vienna University of Economics and Business</institution>
          ,
          <country country="AT">Austria</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Managing Privacy and understanding the handling of personal data has turned into a fundamental right|at least for Europeans| since May 25th with the coming into force of the General Data Protection Regulation. Yet, whereas many di erent tools by di erent vendors promise companies to guarantee their compliance to GDPR in terms of consent management and keeping track of the personal data they handle in their processes, interoperability between such tools as well uniform user facing interfaces will be needed to enable true transparency, usercon gurable and -manageable privacy policies and data portability (as also|implicitly|promised by GDPR). We argue that such interoperability can be enabled by agreed upon vocabularies and Linked Data.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Why Privacy needs Interoperability</title>
      <p>The level of privacy and trust concerns has raised to a point where regulators,
citizens and companies have started to take action. Services on the Web are
often very complex orchestrations of cooperations between multiple actors, and
the processing of personal data in Big Data environments is becoming
intransparently complex. The level of complexity will increase further if the upcoming
Internet of Things is taken into account. If trust in such services is eroded, the
growth of the Web and the digital economy itself, and therefore the prosperity
of society in general are endangered. The challenge is how to convey the
transparency to the user to allow for informed personal data self determination. This
includes especially methods to gather and manage user consent, even in an IoT
environment.
? Authors alphabetically odered. Copyright c 2018 for this paper by its authors.</p>
      <p>Copying permitted for private and academic purposes.</p>
      <p>
        While building privacy-by-design[
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] into systems is a much wider scope, we
already lack the tools and best practices for those wanting to be good citizens of
the Web to provide interoperable and understandable privacy controls, with the
exception maybe of work on Permissions[
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] and on tracking protection[
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], but
even those only cover partial aspects.
      </p>
      <p>
        We argue that existing work on Standards in this domain have not yet
enabled interoperabilty. In particular:
{ There are no standard vocabularies to describe and interchange personal
data { these are needed to support the data subjects' right to personal data
portability.
{ There are { with the exception maybe of starting points in P3P [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] no agreed
upon vocabularies or taxonomies for describing purposes of personal data
handling and kinds of processing : the GDPR requires that both consent and
data processing are tied to a concrete purpose and processing data for other
than this purpose is unlawful. Consequently personal data processing should
be logged with a standard reference to a purpose which complies with the
users consent. While e.g. the PROV ontology [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] vocabulary provides a means
to express processing and provenance of processed data, and ODRL [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] allows
to describe certain permissions and obligations, concrete taxonomies for such
processing and permissions in the context of personal data handling are not
yet standardized.
{ There are no agreed upon vocabularies or ontologies that align the
terminology of privacy legislations, such as the GDPR, with the above mentioned
vocabularies, that would allow software vendors to claim compliance with
such regulations.
2
      </p>
    </sec>
    <sec id="sec-2">
      <title>Finding agreement on areas for Standardisation</title>
      <p>As a rst step towards closing these gaps, on the 17th and 18th April 2018,
some forty people took part in a W3C workshop on data privacy controls and
vocabularies in Vienna. The initial idea was that linked data annotations can
help tackle the issue of privacy in modern data environments and will allow for
the creation of the next generation of privacy enhancing technologies. Of course,
the enactment of the GDPR was also prominent in the discussions. The agenda,
developed on the basis of position statements submitted by various stakeholders
active in the area of standard solutions for interoperable privacy6 consisted of
sessions on four themes,`relevant vocabularies and initiatives', `industry
perspective', `research topics' and `the governmental side &amp; initiatives'. The workshop
ended with a discussion on next steps and in particular on priorities for
standardisation. In order from highest to lowest priority, the goal is to develop a:
1. Taxonomy of regulatory privacy terms (including all GDPR terms).
2. Taxonomy for personal data.
3. Taxonomy of purposes.
6 All the over 30 position statements and expressions of interests by various
stakeholders and organisations are available at https://www.w3.org/2018/vocabws/people.html
Title Suppressed Due to Excessive Length
4. Taxonomy of disclosure and consent.
5. Metadata related to the details of anonymisation.
6. Log vocabularies to describe and exchange logs on personal data processing.
3</p>
    </sec>
    <sec id="sec-3">
      <title>The Data Privacy Vocabularies and Controls</title>
    </sec>
    <sec id="sec-4">
      <title>Community Group</title>
      <p>One of the primarily outputs of the workshop was the setup of a `W3C
Community Group (CG)' entitled Data Privacy Vocabularies and Controls CG (DPVCG)7
which was created on the 25th of May, the o cial starting date of the General
Data Protection Regulation.</p>
      <p>The goal of the CG is to harmonize related e orts and bring together
stakeholders that already have put forward proposals to develop vocabularies to enable
semantic interoperability and interchange of transparency logs about personal
data processing, enable data portability for data subjects, etc. The exact scope
of use cases related to making personal data processing interoperable by
respective standards in order to ease proof of compliance with the GDPR and related
privacy protection regulations will be the rst deliverable of the CG.</p>
      <p>More concretely, the following steps and deliverables are planned so far.
1. Use cases and requirements: in a rst step we will collect and align
common requirements from industry and also from other stakeholders to identify
areas where interoperability is most needed in the handling of personal data.
The outcome shall be a prioritized list of requirements for what needs to be
covered by shared vocabularies to enable interoperability in the identi ed
use cases.
2. Alignment of vocabularies and identi cation of overlaps: in a second
document, we will collect existing vocabularies and standardization e orts
to identify their overlaps and suitability as starting points to minimally and
extensibly cover the requirements prioritized in step one.
3. Glossary of GDPR terms: a third deliverable will be an understandable
glossary of common terms from the GDPR and how they shall be covered
by the agreed vocabularies.
4. Vocabularies based on the heterogeneity or homogeneity of the agreed upon
use cases and requirements, we plan de ne a set of vocabularies for
exchanging and representing interoperably: personal data, purposes/processing,
disclosure/consent, anonymisation, and transparency logs.</p>
      <p>
        Some starting points for these vocabularies e.g. for transparency logs that
companies can keep on their collected consent and personal data handling [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ],
along with lightweight reasoning techniques [
        <xref ref-type="bibr" rid="ref1 ref2 ref7">1, 7, 2</xref>
        ] to check GDPR-compliance
over these logs have already been created in draft versions by the EU H2020
project SPECIAL8, in which several of the co-authors are actively involved.
7 https://www.w3.org/community/dpvcg/
8 Scalable Policy-aware Linked Data Architecture For Privacy, Transparency and
      </p>
      <p>Compliance, cf. http://specialprivacy.eu</p>
      <p>
        Starting points in terms of a description of existing vocabularies and gaps
between them can be found in [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ].
4
      </p>
    </sec>
    <sec id="sec-5">
      <title>Input and Collaboration</title>
      <p>Interoperability and agreed upon vocabularies are in our opinion crucial for truly
implementing the goals of stricter, more user-centric privacy controls for data
subjects, but also to alleviate the burden for companies in the context of ful lling
their compliance obligations in the context of GDPR. We invite any interested
stakeholders to join the Data Privacy Vocabularies and Controls Community
Group and provide feedback to its drafts. The rst Face-2-face meeting is being
planned at the MyData2018 conference in Helsinki, Finland, in August, and the
second 2nd Face-2-face meeting being planned to be co-located with the
European Big Data Value Forum in Vienna, Austria, in 12-14 November 2018. We
hope the SW4CG workshop at ISWC also o ers a stage to discuss the emerging
needs for interoperability in terms of privacy and personal data handling, and
how Semantic Web technologies and standards can help to satisfy these needs.
Acknowledgments. This work has been supported by the European Union's
Horizon 2020 research and innovation programme under grant 731601
(SPECIAL).</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Bonatti</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kirrane</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Petrova</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sauro</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schlehahn</surname>
          </string-name>
          , E.:
          <article-title>Deliverable D2.1: Policy language v1 (Dec 2017), SPECIAL public project deliverable</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Bonatti</surname>
            ,
            <given-names>P.A.</given-names>
          </string-name>
          :
          <article-title>Fast compliance checking in an OWL2 fragment</article-title>
          .
          <source>In: Proc. IJCAI</source>
          (
          <year>2018</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Cavoukian</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Privacy by design. Take the challenge</article-title>
          .
          <source>Information and privacy commissioner of Ontario</source>
          , Canada (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Cranor</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Langheinrich</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Marchiori</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Presler-Marshall</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Reagle</surname>
            ,
            <given-names>J.:</given-names>
          </string-name>
          <article-title>The platform for privacy preferences 1.0 (p3p1.0) speci cation</article-title>
          (
          <year>Apr 2002</year>
          ), https://www.w3.org/TR/P3P/, W3C Rec.
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Fielding</surname>
          </string-name>
          , R.T.,
          <string-name>
            <surname>Singer</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>Tracking preference expression</article-title>
          (dnt) (
          <year>Oct 2017</year>
          ), https://www.w3.org/TR/2017/CR-tracking-dnt-
          <volume>20171019</volume>
          /, W3C Candidate Rec.
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Iannella</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Steidl</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Myles</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rodr</surname>
            guez-Doncel,
            <given-names>V.</given-names>
          </string-name>
          :
          <source>ODRL Vocabulary &amp; Expression 2.2 (Feb</source>
          <year>2018</year>
          ), https://www.w3.org/TR/odrl-vocab/, W3C Rec.
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Kirrane</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bonatti</surname>
            ,
            <given-names>P.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fernandez</surname>
            ,
            <given-names>J.D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Galdi</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sauro</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          :
          <article-title>Deliverable D2.4: Transparency and compliance algorithms v1 (</article-title>
          <year>2018</year>
          ),
          <article-title>SPECIAL public project deliverable</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Kirrane</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fernandez</surname>
          </string-name>
          ,
          <string-name>
            <surname>U.M.J.D.</surname>
          </string-name>
          ,
          <string-name>
            <surname>Polleres</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Deliverable D2.3: Transparency framework v1 (</article-title>
          <year>2018</year>
          ),
          <article-title>SPECIAL public project deliverable</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Lebo</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sahoo</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>McGuinness</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Belhajjame</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cheney</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Corsar</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Garijo</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Soiland-Reyes</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zednik</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zhao</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          :
          <article-title>Prov-o: The prov ontology</article-title>
          (
          <year>Apr 2013</year>
          ), https://www.w3.org/TR/prov-o/, W3C Rec.
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Polleres</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kirrane</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wenning</surname>
          </string-name>
          , R.:
          <source>Deliverable D6</source>
          .
          <article-title>3: Plan for community group and standardisation contribution (2017), SPECIAL public project deliverable</article-title>
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>