February 28, 2019 Project deliverable Open Access

Filippo Maganza; Kennedy Junior Anagbo

DataCite XML Export

<?xml version='1.0' encoding='utf-8'?>
<resource xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://datacite.org/schema/kernel-4" xsi:schemaLocation="http://datacite.org/schema/kernel-4 http://schema.datacite.org/meta/kernel-4.1/metadata.xsd">
  <identifier identifierType="DOI">10.5281/zenodo.2580245</identifier>
  <creators>
    <creator>
      <creatorName>Filippo Maganza</creatorName>
      <affiliation>Alpenite</affiliation>
    </creator>
    <creator>
      <creatorName>Kennedy Junior Anagbo</creatorName>
      <affiliation>Alpenite</affiliation>
    </creator>
  </creators>
  <titles>
    <title>Lynx D1.3 Technical architecture design</title>
  </titles>
  <publisher>Zenodo</publisher>
  <publicationYear>2019</publicationYear>
  <subjects>
    <subject>technical architecture</subject>
  </subjects>
  <contributors>
    <contributor contributorType="Other">
      <contributorName>Socorro Bernardos Galindo</contributorName>
      <affiliation>Ontology Engineering Group, Universidad Politécnica de Madrid</affiliation>
    </contributor>
    <contributor contributorType="Other">
      <contributorName>Ilan Kenerman</contributorName>
      <affiliation>KDictionaries</affiliation>
    </contributor>
    <contributor contributorType="Other">
      <contributorName>Julián Moreno-Schneider</contributorName>
      <affiliation>DFKI</affiliation>
    </contributor>
    <contributor contributorType="Other">
      <contributorName>Stefanie Hegele</contributorName>
      <affiliation>DFKI</affiliation>
    </contributor>
  </contributors>
  <dates>
    <date dateType="Issued">2019-02-28</date>
  </dates>
  <language>en</language>
  <resourceType resourceTypeGeneral="Text">Project deliverable</resourceType>
  <alternateIdentifiers>
    <alternateIdentifier alternateIdentifierType="url">https://zenodo.org/record/2580245</alternateIdentifier>
  </alternateIdentifiers>
  <relatedIdentifiers>
    <relatedIdentifier relatedIdentifierType="DOI" relationType="IsVersionOf">10.5281/zenodo.2580244</relatedIdentifier>
    <relatedIdentifier relatedIdentifierType="URL" relationType="IsPartOf">https://zenodo.org/communities/lynx</relatedIdentifier>
  </relatedIdentifiers>
  <version>1.0</version>
  <rightsList>
    <rights rightsURI="https://creativecommons.org/licenses/by/4.0/legalcode">Creative Commons Attribution 4.0 International</rights>
    <rights rightsURI="info:eu-repo/semantics/openAccess">Open Access</rights>
  </rightsList>
  <descriptions>
    <description descriptionType="Abstract">&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;</description>
  </descriptions>
  <fundingReferences>
    <fundingReference>
      <funderName>European Commission</funderName>
      <funderIdentifier funderIdentifierType="Crossref Funder ID">10.13039/100010661</funderIdentifier>
      <awardNumber awardURI="info:eu-repo/grantAgreement/EC/H2020/780602/">780602</awardNumber>
      <awardTitle>Building the Legal Knowledge Graph for Smart Compliance Services in Multilingual Europe</awardTitle>
    </fundingReference>
  </fundingReferences>
</resource>