<!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>DALICC: A Framework for Publishing and Consuming Data Assets Legally</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Giray Havur</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff4">4</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Simon Steyskal</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
          <xref ref-type="aff" rid="aff4">4</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Oleksandra Panasiuk</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Anna Fensel</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Victor Mireles</string-name>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Tassilo Pellegrini</string-name>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Thomas Thurner</string-name>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Axel Polleres</string-name>
          <xref ref-type="aff" rid="aff4">4</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Sabrina Kirrane</string-name>
          <xref ref-type="aff" rid="aff4">4</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>STI Innsbruck, University of Innsbruck</institution>
          ,
          <country country="AT">Austria</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Siemens AG Österreich</institution>
          ,
          <country country="AT">Austria</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>St. Pölten University of Applied Sciences</institution>
          ,
          <country country="AT">Austria</country>
        </aff>
        <aff id="aff3">
          <label>3</label>
          <institution>The Semantic Web Company</institution>
          ,
          <country country="AT">Austria</country>
        </aff>
        <aff id="aff4">
          <label>4</label>
          <institution>Vienna University of Economics and Business</institution>
          ,
          <country country="AT">Austria</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>In this paper we introduce the Data Licenses Clearance Center, which provides a library of machine readable standard licenses and allows users to compose arbitrary licenses. In addition, the system supports the clearance of rights issues by providing users with information about the equivalence, similarity and compatibility of licenses. A beta version of the system is available at https://www.dalicc.net/.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        DALICC stands for Data Licenses Clearance Center. It is a software framework
that supports legal experts, innovation managers and application developers in
the legally secure reutilization of third party digital assets such as data sets,
software or content. The DALICC framework enables the automated clearance
of rights, thus helping to detect licensing conflicts and significantly reducing the
costs of rights clearance in the creation of derivative works. This is necessary
insofar as modern IT applications increasingly retrieve, store and process data
assets from a variety of sources. This can raise questions about the compatibility
of licenses and the application‘s compliance with existing law. In order to
provide commercial products and services on top of third party data assets, license
clearance is necessary to assure legal compatibility[
        <xref ref-type="bibr" rid="ref2">2</xref>
        ].
      </p>
      <p>The DALICC framework consists of three main functional components,
namely: license library, license search, and license composer, as shown in Figure 1.
These are backed by storage for licenses and an automatic reasoning engine.</p>
      <p>The license library is a repository that contains machine-readable and
humanreadable representations of the licenses, the former as ODRL policies , and the
latter as plain text. These are laid out in a UI as shown in Figure 3.</p>
      <p>In the case of license search, the user defines a set of permissions or
prohibitions (cf. Figure 2) which are then matched against existing licenses via a
JavaScript triggered SPARQL query and processed by a reasoning mechanism
which returns the licenses that are consistent with the given input.</p>
    </sec>
    <sec id="sec-2">
      <title>License</title>
    </sec>
    <sec id="sec-3">
      <title>Search</title>
    </sec>
    <sec id="sec-4">
      <title>License</title>
    </sec>
    <sec id="sec-5">
      <title>Composer</title>
    </sec>
    <sec id="sec-6">
      <title>License</title>
    </sec>
    <sec id="sec-7">
      <title>Library</title>
      <p>Data Sources
R
e
a
s
o
n
e
r</p>
    </sec>
    <sec id="sec-8">
      <title>License Library,</title>
    </sec>
    <sec id="sec-9">
      <title>Dependency Graph &amp;</title>
    </sec>
    <sec id="sec-10">
      <title>Questionnaire</title>
    </sec>
    <sec id="sec-11">
      <title>Customized</title>
    </sec>
    <sec id="sec-12">
      <title>License</title>
      <p>The license composer (cf. Figure 4) allows to create customized licenses from
a set of questions which are mapped to ODRL, ccREL and DALICC
vocabularies. The composer allows for the declaration of necessary provenance information
about an asset (e.g., purl:title for the work’s title and cc:deprecatedOn for the
expiration date of the license) and gives the possibility to download an RDF
representation and a human-readable version of the created license.</p>
      <p>Technology-wise, the DALICC system combines the following components: a
Virtuoso6 triplestore, a Drupal7 based web application, the PoolParty
Semantic Suite8, and a Clingo Answer Set Programming (ASP) reasoner that checks
license consistency and allows to detect conflicts between licenses.</p>
      <sec id="sec-12-1">
        <title>6 https://virtuoso.openlinksw.com/ 7 https://www.drupal.org 8 https://www.poolparty.biz/</title>
        <sec id="sec-12-1-1">
          <title>Data Modelling</title>
          <p>In order to represent license concepts in a structured machine-readable format
we chose the ODRL policy expression language, which includes a flexible and
interoperable information model9 and an extendable vocabulary10.</p>
          <p>The ODRL information model is particularly suitable for modeling licenses
in the form of policies that express permissions, prohibitions and duties related
to the usage of assets.</p>
          <p>ODRL also defines a vocabulary of general terms (e.g., odrl:modify ,
odrl:reproduce, odrl:distribute) and can be further extended with terms from other
vocabularies such as CC REL (e.g., cc:CommercialUse, cc:DerivativeWorks)11 or,
like in our case, with a custom one.</p>
          <p>To finally model legally valid licenses we extended the expressivity of ODRL
with a DALICC vocabulary providing additional legal terms such as dalicc:
worldwide as a jurisdictional property, dalicc:perpetual as a validity type,
dalicc:chargeLicenseFee as permission and prohibition actions, and dalicc:
modificationNotice as a duty action.</p>
          <p>
            Additionally, DALICC utilises a dependency graph encoding the expert
knowledge about the implicit and explicit semantic dependencies between
actions. Following the work of Steyskal and Polleres [
            <xref ref-type="bibr" rid="ref3">3</xref>
            ], the dependency graph
represents hierarchical relations between actions (e.g., odrl:sell odrl:includedIn
odrl:commercialize), implications derived from a specific action (e.g.,
cc:Attribution odrl:implies cc:Notice), equalities (e.g., odrl:copy owl:sameAs
odrl:reproduce), and contradictions between specific actions (e.g., cc:ShareAlike
dalicc:contradicts dalicc:addStatement).
          </p>
          <p>Figure 5 depicts the central role of odrl:Action in integrating the licenses,
dependency graph and the composer and search functionalities.
3</p>
        </sec>
        <sec id="sec-12-1-2">
          <title>Reasoning over Licenses</title>
          <p>
            To reason over licenses we use Answer Set Programming (ASP)[
            <xref ref-type="bibr" rid="ref1">1</xref>
            ], a declarative
(logic-programming-style) paradigm for solving combinatorial search problems
by defining and evaluating rule sets. Licenses are represented in ASP as a set of
rules of the form rule(L,C,I,α,T) where L, C, I, α, and T correspond to license
name, category of rule, assignee, action, and asset, respectively.
          </p>
          <p>Policies are derived from the RDF graphs of the licenses. Herein, a rule that
permits or prohibits the execution of an action on certain assets does not only
affect other rules that govern the execution of the same action on the same
asset(s) but also those permitting or prohibiting related actions on the same
asset(s). In this sense, clingo is an alternative to extensive materialization, which
in this case is essential for search, and also enables listing sets of compatible</p>
        </sec>
      </sec>
      <sec id="sec-12-2">
        <title>9 https://www.w3.org/TR/odrl-model/ 10 https://www.w3.org/TR/odrl-vocab 11 https://creativecommons.org/ns#</title>
        <p>odrl:Action 
dalicc:excludesPermission
dalicc:excludesDuty
dalicc:excludesProhibition
dalicc:needsPermission
dalicc:needsDuty
dalicc:needsProhibition
dalicc:question
dalicc:Questionnaire  Questionnaire
statements. This is necessary for effective computation of conflicts between
licences, in particular for identifying the conflicting and non-conflicting parts of
a license.
4</p>
        <sec id="sec-12-2-1">
          <title>Conclusion and Future Work</title>
          <p>Licensing and rights clearance are complex topics that require a high level of
problem awareness and legal expertise. The potential for future work directions
are as follows: (i) enabling organizations to create their own applications and
workflows using DALICC APIs; (ii) the visualization of data workflows taking
into account the license provenance information; (iii) utilizing already existing
capabilities of the reasoning component for conflict resolution; (iv) the provision
of license management schemes that tackle consistence and trustability issues at
the document and workflow level by leveraging transparent infrastructures such
as blockchains.</p>
          <p>Acknowledgments. Funded by the Austrian Federal Ministry of Transport,
Innovation and Technology (BMVIT) DALICC project https://www.dalicc.net.</p>
        </sec>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <given-names>Gerhard</given-names>
            <surname>Brewka</surname>
          </string-name>
          , Thomas Eiter, and
          <string-name>
            <given-names>Mirosław</given-names>
            <surname>Truszczyński</surname>
          </string-name>
          .
          <article-title>Answer set programming at a glance</article-title>
          .
          <source>Communications of the ACM</source>
          ,
          <volume>54</volume>
          (
          <issue>12</issue>
          ),
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <given-names>Axel</given-names>
            <surname>Hoffmann</surname>
          </string-name>
          , Thomas Schulz, Julia Zirfas, Holger Hoffmann, Alexander Roßnagel, and Jan Marco Leimeister.
          <article-title>Legal Compatibility as a Characteristic of Sociotechnical Systems: Goals and Standardized Requirements</article-title>
          .
          <source>Business &amp; Information Systems Engineering</source>
          ,
          <volume>57</volume>
          (
          <issue>2</issue>
          ):
          <fpage>103</fpage>
          -
          <lpage>113</lpage>
          ,
          <year>April 2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <given-names>Simon</given-names>
            <surname>Steyskal</surname>
          </string-name>
          and
          <string-name>
            <given-names>Axel</given-names>
            <surname>Polleres</surname>
          </string-name>
          .
          <article-title>Towards formal semantics for ODRL policies</article-title>
          .
          <source>In 9th International Symposium RuleML</source>
          , pages
          <fpage>360</fpage>
          -
          <lpage>375</lpage>
          ,
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>