February 28, 2019 Project deliverable Open Access

Filippo Maganza; Kennedy Junior Anagbo

MARC21 XML Export

<?xml version='1.0' encoding='UTF-8'?>
<record xmlns="http://www.loc.gov/MARC21/slim">
  <leader>00000nam##2200000uu#4500</leader>
  <datafield tag="041" ind1=" " ind2=" ">
    <subfield code="a">eng</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">technical architecture</subfield>
  </datafield>
  <controlfield tag="005">20200120171048.0</controlfield>
  <controlfield tag="001">2580245</controlfield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">Alpenite</subfield>
    <subfield code="a">Kennedy Junior Anagbo</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">Ontology Engineering Group, Universidad Politécnica de Madrid</subfield>
    <subfield code="4">oth</subfield>
    <subfield code="a">Socorro Bernardos Galindo</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">KDictionaries</subfield>
    <subfield code="4">oth</subfield>
    <subfield code="a">Ilan Kenerman</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">DFKI</subfield>
    <subfield code="4">oth</subfield>
    <subfield code="a">Julián Moreno-Schneider</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">DFKI</subfield>
    <subfield code="4">oth</subfield>
    <subfield code="a">Stefanie Hegele</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">892863</subfield>
    <subfield code="z">md5:ecfa3814fab727ec4ed4682be8c60f93</subfield>
    <subfield code="u">https://zenodo.org/record/2580245/files/Final_D1.3_Technical_architecture_design.pdf</subfield>
  </datafield>
  <datafield tag="542" ind1=" " ind2=" ">
    <subfield code="l">open</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="c">2019-02-28</subfield>
  </datafield>
  <datafield tag="909" ind1="C" ind2="O">
    <subfield code="p">openaire</subfield>
    <subfield code="p">user-lynx</subfield>
    <subfield code="o">oai:zenodo.org:2580245</subfield>
  </datafield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="u">Alpenite</subfield>
    <subfield code="a">Filippo Maganza</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">Lynx D1.3 Technical architecture design</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">user-lynx</subfield>
  </datafield>
  <datafield tag="536" ind1=" " ind2=" ">
    <subfield code="c">780602</subfield>
    <subfield code="a">Building the Legal Knowledge Graph for Smart Compliance Services in Multilingual Europe</subfield>
  </datafield>
  <datafield tag="540" ind1=" " ind2=" ">
    <subfield code="u">https://creativecommons.org/licenses/by/4.0/legalcode</subfield>
    <subfield code="a">Creative Commons Attribution 4.0 International</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="7">
    <subfield code="a">cc-by</subfield>
    <subfield code="2">opendefinition.org</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">&lt;p&gt;The Lynx project as a compliance service-oriented platform that seeks to address compliance and regulatory related needs of its clients and users, comprises many services ranging from the fields of Information Extraction and Linking, Knowledge Management and Sematic Web; for which there is the need for a high level technical architecture design that integrates these services in order to address the objectives of the project.&lt;/p&gt;

&lt;p&gt;This document, therefore, provides a detailed description of the technical architectural design solution for the Lynx platform. Architecture design in any software development project as in the case of Lynx serves as a blueprint that drives the smooth design and implementation of the software system. Once implemented, fundamental structural choices are costly to change.&lt;/p&gt;

&lt;p&gt;In this deliverable, standard architectural patterns such as the Monolithic architecture pattern, SOA and MSA are described narrowing down on the choice of the architectural patterns that suites the architectural design needs of the Lynx platform with reference to the functional and technical requirements of the Lynx platform.&lt;/p&gt;

&lt;p&gt;For the Lynx platform, we adopted the &lt;strong&gt;MSA pattern&lt;/strong&gt; which supports loose coupling between services; a feature that allows for easy separation of work and which makes this pattern most adaptable to the Lynx platform requirements.&lt;/p&gt;

&lt;p&gt;The document also provides detailed description of the logical and physical architectures.&lt;/p&gt;

&lt;p&gt;The logical architecture describes the following:&lt;/p&gt;

&lt;ul&gt;
	&lt;li&gt;Access control system&lt;/li&gt;
	&lt;li&gt;Microservices coordination system&lt;/li&gt;
	&lt;li&gt;Communication system&lt;/li&gt;
	&lt;li&gt;Foundational microservices&lt;/li&gt;
	&lt;li&gt;How the software microservices are wired together to form a larger software system&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The physical architecture describes the type of infrastructures, the platform and the deployment architecture of the software application and how to deliver the deployable system.&lt;/p&gt;</subfield>
  </datafield>
  <datafield tag="773" ind1=" " ind2=" ">
    <subfield code="n">doi</subfield>
    <subfield code="i">isVersionOf</subfield>
    <subfield code="a">10.5281/zenodo.2580244</subfield>
  </datafield>
  <datafield tag="024" ind1=" " ind2=" ">
    <subfield code="a">10.5281/zenodo.2580245</subfield>
    <subfield code="2">doi</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">publication</subfield>
    <subfield code="b">deliverable</subfield>
  </datafield>
</record>