<!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>Building the Legal Knowledge Graph for Smart Compliance Services in Multilingual Europe</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Elena Montiel-Ponsoda</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Víctor Rodríguez-Doncel</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Jorge Gracia</string-name>
        </contrib>
      </contrib-group>
      <fpage>15</fpage>
      <lpage>17</lpage>
      <abstract>
        <p>This position paper describes the vision, objectives and methodology of the LYNX project. The aim of Lynx is to create services to better manage compliance, based on a legal knowledge graph which integrates and links heterogeneous compliance data sources including legislation, case law and standards.</p>
      </abstract>
      <kwd-group>
        <kwd />
        <kwd>Compliance</kwd>
        <kwd>Legal Knowledge Graph</kwd>
        <kwd>regtech</kwd>
        <kwd>regulatory compliance</kwd>
        <kwd>semantic web</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>1 OEG, Universidad Politécnica de Madrid
2 Universidad de Zaragoza</p>
    </sec>
    <sec id="sec-2">
      <title>Introduction</title>
      <p>
        The term compliance is widely used to refer “to the conformance to a set of laws,
regulations, policies, or best practices” [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. Every company performing almost any
activity has some concern with compliance-related problems.
      </p>
      <p>These problems are a bigger concern for small and medium-sized enterprises
(SMEs), which cannot afford expensive consultancy services and they are a bigger
hurdle for companies trying to sell abroad, as they usually lack the knowledge on the
applicable conditions in the target country. According to the European Commission1,
only 7% of European SMEs sell across borders, but those who do, exhibit 7% job
growth and 26% innovate in their offering, greater numbers than the 1% and 8% of
SMEs that do not go outside their local markets.</p>
      <p>The European Commission is aware of these legal and language barriers and is
trying to build a single market with less entry barriers. The LYNX project is a
European research project funded as an H2020 Innovation Action covering the topic
ICT-14: Big Data PPP: cross-sectorial and cross-lingual data integration and
experimentation. The project is expected to last three years, starting in December 2017.
This position paper briefly presents this research project.</p>
      <p>1 http://europa.eu/rapid/press-release_IP-10-895_en.htm</p>
    </sec>
    <sec id="sec-3">
      <title>1. The LYNX project</title>
      <p>Having identified these compliance problem, and having assumed that technology can
help lowering these legal and language barriers, the main objective of Lynx can be
stated as “to create an ecosystem of cloud services to better manage compliance, based
on a legal knowledge graph which integrates and links heterogeneous compliance data
sources including legislation, case law, standards and other aspects”. Other specific
objectives follow:
 to provide a platform that helps companies solving questions and cases related
to compliance in different sectors and jurisdictions.
 to help European SMEs to reduce costs and effort in organising and
monitoring legislation, regulations, and sectorial good practices.
 to provide citizens a better access to legal and regulatory information from
multiple jurisdictions and to facilitate their in the legislative processes and in
the writing process of standards.
 to draw a legal knowledge graph across different jurisdictions, comprising
legislation, case law, doctrine, standards, norms, and other documents.
 to deliver the necessary domain-neutral common services (such as document
annotation, interlinking, etc.) as building blocks to orchestrate aggregated
business-oriented services.
 to cover some particular business case necessities, validating the project’s
developed ecosystem.</p>
      <p>
        The referred legal knowledge graph is a collection of structured data and
unstructured documents which are densely interlinked. These documents shall be
variate in their language, and terminologies and language resources will also be
included in order to provide multilingual services. Semantic Web technologies favour
the distributed publication of documents and data, and provide the technology to
announce and traverse the links. Whereas the relationship between Semantic Web and
Law has been a rich one [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ], there had been no “Legal Linked Open Data Cloud” (cf.
Linguistic Linked Open Data Cloud) nor the term “Legal Linked Data” has gained
spread.
      </p>
      <p>The Lynx Project will identify the major legal resources necessary to provide
exploitable compliance services, storing their metadata in a uniform manner and
running the processing routines to extract, structure, transform, annotate and link the
resources whenever needed. The cloud of Lynx services will be built, including
middleware microservices as well as end-user services, offered under different access
modalities. These services will be configured in three pilots according to the industry
needs in three different domains: labour law, data protection and oil &amp; gas and energy.
The services will consider compliance in a broad sense, including not only compliance
with the law but also compliance with standards and even with good practices and
internal policies.</p>
      <p>In summary, this project may benefit European business by means of a cloud of
services providing mass-customised regulatory information including legislation,
regulations, and policies, which will open the path for a new breed of solutions. Faster
answer will be facilitated to recurrent questions like: “What is the equivalent to
regulation X in country Y?” or “How is the technical question X handled in country Y?
How has it been understood by the local courts?”. As a side benefit, citizens will also
see legislation published in different manners promoting legal knowledge and
development of new applications. Finally, Lynx will also support the creation of a
common legal ICT infrastructure that will contribute to unlock the potential of a
multilingual, truly single digital market.</p>
    </sec>
    <sec id="sec-4">
      <title>Acknowledgements</title>
      <p>Lynx has received funding from the Horizon 2020 European Union (EU) Research and
Innovation programme under Grant Agreement: 780602. We thank every partner in
Lynx for their contribution to the project’s inception and the Datos 4.0 project with ref.
TIN2016-78011-C4-1-R.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <surname>Silveira</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rodríguez</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Casati</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Daniel</surname>
          </string-name>
          , F.,
          <string-name>
            <surname>D'Andrea</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Worledge</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Taheri</surname>
            ,
            <given-names>Z.</given-names>
          </string-name>
          <article-title>On the design of compliance governance dashboards for effective compliance and audit management</article-title>
          .
          <source>In Service-Oriented Computing. ICSOC</source>
          <year>2009</year>
          , pp.
          <fpage>208</fpage>
          -
          <lpage>217</lpage>
          . Springer Berlin Heidelberg,
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <surname>Benjamins</surname>
            ,
            <given-names>V. R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Casanovas</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Breuker</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Gangemi</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          (
          <year>2005</year>
          ).
          <article-title>Law and the semantic web, an introduction</article-title>
          .
          <source>In Law and the Semantic Web</source>
          (pp.
          <fpage>1</fpage>
          -
          <lpage>17</lpage>
          ). Springer, Berlin, Heidelberg.
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <surname>Chiarcos</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hellmann</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Nordhoff</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          (
          <year>2011</year>
          ).
          <article-title>Towards a Linguistic Linked Open Data cloud: The Open Linguistics Working Group</article-title>
          . TAL,
          <volume>52</volume>
          (
          <issue>3</issue>
          ),
          <fpage>245</fpage>
          -
          <lpage>275</lpage>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>