<!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>THE TECHNOLOGY AND TOOLS FOR THE BUILDING OF INFORMATION EXCHANGE PACKAGE BASED ON SEMANTIC DOMAIN MODEL</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Yu.M. Akatkin</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>M.G. Bich</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>E.D. Yasinovskaya</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>A.V. Shilin</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Plekhanov Russian University of Economics</institution>
          ,
          <addr-line>36 Stremyanny per., Moscow, 117997</addr-line>
          ,
          <country country="RU">Russia</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Yuri Akatkin, Michael Bich, Elena Yasinovskaya</institution>
          ,
          <addr-line>Andrey Shilin</addr-line>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2021</year>
      </pub-date>
      <fpage>5</fpage>
      <lpage>9</lpage>
      <abstract>
        <p>This paper presents the technology developed by the authors with the aim to improve the semantic interoperability in heterogeneous environment, where the systems use web-services orchestrated by an object-oriented exchange bus for cross-agency interaction and information sharing. The suggested solution, including the set of tools, allows to map the models of interacting information systems with a unified data model (domain otology) on the semantic level during the development of an information exchange package.</p>
      </abstract>
      <kwd-group>
        <kwd>Semantic models</kwd>
        <kwd>Semantic interoperability</kwd>
        <kwd>Semantic integration</kwd>
        <kwd>Cross-agency interaction</kwd>
        <kwd>Information sharing</kwd>
        <kwd>Domain data model</kwd>
        <kwd>Information exchange</kwd>
        <kwd>NIEM</kwd>
        <kwd>SDMX</kwd>
        <kwd>SOAP</kwd>
        <kwd>Eclipse Papyrus</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>Heterogeneous environment inherent for information sharing requires the application of
integration methods, which will guarantee the achievement of unambiguous and meaningful
interpretation of data at all levels. Following to the opinion of expert community the authors consider
US National Information Exchange Model (NIEM) [1,2] as one of the most developed and widely
used technologies for information sharing during cross-agency interaction. NIEM is a US national
standard. This model as well as the methods and technologies for its implementation provide full stack
support for developers by using both proprietary software tools (e.g., IBM [1], Oracle1 и Microsoft2)
and a set of open-source software tools3.</p>
      <p>The development of Information Exchange Package Documentation (IEPD) sets the basis for
the application of object-oriented approach in NIEM. The developers build IEPDs by implementing all
the matching elements from NIEM Core or NIEM domains and where applicable, they can extend this
content with new items to meet those information requirements which NIEM does not cover.
Thoroughly elaborated over the past 10 years IEPD building process includes 6 steps [1,1]. There is an
appropriate toolkit for each step of the IEDP development life cycle.</p>
      <p>In object-oriented approach the data models providing semantic interoperability for interacting
heterogeneous information systems via are created in compliance with the methods, which include the
analysis of exchange business processes in the domain context. However, the built exchange object
model obtains only those entities that are essential for this specific information exchange as well as
their properties and relationships.</p>
      <p>Within the development of the Semantic Web the use of semantic models, actively studied and
tested in practice in ontology engineering [3,4,5], has become the dominant method for solving the
problem of heterogeneous data semantics.</p>
      <p>The authors consider significant to release the potential for the convergence of NIEM-type
models, providing data integration on federation principle, with Semantic Web models, supporting
semantic annotation. For example, OMG offers such approach in the initiative called the Semantic
Information Modeling for Federation [6,7]. The research in this direction had been going on for the
last 10 years4, although it has not yet received a wide practical implementation. Nevertheless, the
enrichment of object-oriented data exchange models with semantics promises the fastest achievement
of a new level of semantic interoperability.</p>
    </sec>
    <sec id="sec-2">
      <title>2. Methods</title>
      <p>The authors represent the technology and tools developed following the methods of software
design and development adopted in Russia, as well as in accordance with the internationally used
Design Science Research Methodology for Information Systems Research (DSRM) [8].</p>
      <p>The research of semantic integration methods from the prospective of 8 years’ experience,
presented in several works5, served as the Problem identification and motivation stage, which
highlighted the Objectives for the solution, demonstrated in this paper (Section 3.1). The technological
stack including the development tools represented in Section 3.2 together with the description of
suggested information exchange package (Section 3.3) show the results of Design and development
stage. Section 3.3. demonstrates the use case and application of our solution for cross-agency
information sharing in chemical and biological security domain. It represents the Implementation stage
1 https://blogs.oracle.com/xmlorb/entry/oracle_niem_resources_site_launches,
http://www.oracle.com/us/products/applications/public-sector/niem/index.html
2 http://blogs.msdn.com/b/jrspinella/archive/2011/06/20/biztalk-2010-real-world-example-part-1.aspx
3 https://www.niem.gov/tools-catalog
4 https://github.com/ModelDriven/SIMF/tree/master/Presentations
5 https://www.researchgate.net/lab/Yuri-Akatkin-Lab
and covers Demonstration и Evaluation activities as well. The authors aim to present the technology
and tools to start the discussion during the GRID Conference at Communication stage and use more
opportunities for further implementation. Section 4 summarizes current experience and provides demo
links for detailed instructions and screen shots for everyone who is interested in testing the suggested
solution in real time.</p>
    </sec>
    <sec id="sec-3">
      <title>3. Solution</title>
      <p>3.1</p>
      <sec id="sec-3-1">
        <title>Problem and Objectives</title>
        <p>Based on the current experience in the arrangement of cross-agency interaction and conducted
research (e.g., [9]) the authors consider that at the present time the topical problem in information
sharing is the lack of methods and software tools combining the informative richness of semantic
models, describing the interacting information systems domain, with the power of industrial solutions
for object-oriented data exchange.</p>
        <p>To overcome this challenge, the authors suggest the solution aimed to achieve the following
objectives:
●
●
●</p>
        <p>To support mapping of an information system model with the unified data model (domain
model) used for the cross-agency interaction;
To enrich an object information exchange model (exchange model) with semantic descriptions
by linking its elements with the domain model, supporting integrity and verifiability;
To generate object domain models from semantic models automatically.
3.2</p>
      </sec>
      <sec id="sec-3-2">
        <title>Components</title>
        <sec id="sec-3-2-1">
          <title>The developed solution includes four interrelated components [fig. 1].</title>
          <p>Data Model Catalog provides registration, storage and retrieval of object and semantic
models. The authors have implemented Asset Description Metadata Schema (ADMS)6 extended with
the classes and entities to support and track cross relationships of the assets as well as to use domain
management services for experts’ collaboration [9].</p>
          <p>REST7 service provides access to the catalog and its modification. It serves to search an asset
search, gets its description (in JSON8 format) and contents (as files of various formats). Through
transactions the service software ensures the integrity of the catalog when creating a new asset or
saving a modified version of the existing one.</p>
          <p>Domain Management component is responsible for joint work of experts on the validation
of exchange models as well as on the domain improvement. The component supports the collaboration
functions. It provides the set of tools for setting up and executing business processes using various
teamwork functions (task management, commenting, voting, notification, etc.).</p>
          <p>
            External Design Tool serves for the development of exchange models. The authors suggest
using Eclipse Papyrus9 extended with additional plugins: (
            <xref ref-type="bibr" rid="ref1">1</xref>
            ) functions for REST service application
and domain import; (
            <xref ref-type="bibr" rid="ref2">2</xref>
            ) specially developed Papyrus Architectural Context. This architectural context
includes: (a) UML profile for exchange model development; (b) icon palette and (c) additional
Papyrus plugins. These plugins realize (
            <xref ref-type="bibr" rid="ref1">1</xref>
            ) filling special properties of UML classes with IRIs of
domain elements, (
            <xref ref-type="bibr" rid="ref2">2</xref>
            ) OCL and programmed model validators, (
            <xref ref-type="bibr" rid="ref3">3</xref>
            ) automatic conformity control for
object and semantic models, (
            <xref ref-type="bibr" rid="ref4">4</xref>
            ) the domain ontology file containing OWL and the automatically
generated UML domain model. The same IRI in different object models correspond to equal
semantics, and automatic control provides equivalent syntax.
3.3
          </p>
        </sec>
      </sec>
      <sec id="sec-3-3">
        <title>Information Exchange Package</title>
        <p>The authors have primary implemented such approach in the Center of Semantic Integration
(CSI) project [9]. It is important to highlight the difference between the CSI Information Exchange
Package created for cross-agency interaction in our solution and NIEM IEPD.</p>
        <p>There are two main features distinguishing the suggested solution:
●
●
●
●
●
●</p>
        <p>The use of semantic technologies during the development and publication of the information
exchange package;
The additional data fixing the collaboration between developers and domain experts
(comments, recommendations, discussion).</p>
        <p>Considering the general logic of NIEM IEPD, CSI Information Exchange Package includes:</p>
        <sec id="sec-3-3-1">
          <title>Ontological representation of data model and proposals for its extension; Object representation of data model in the format of the tools used for its design; Platform-dependent elements simplifying the implementation of the package into applied information systems;</title>
          <p>Extended package documentation, including semantic annotation for the object models.
3.4</p>
        </sec>
      </sec>
      <sec id="sec-3-4">
        <title>Use case</title>
        <p>This use case represents the developed solution in the process of cross-agency interaction in
the chemical and biological security domain regulated by the Ministry of Healthcare of the Russian
Federation. The fulfillment of the following tasks demonstrates the capability of suggested technology
and tools:
● To design information exchange models;
● To build data exchange schemes using SDMX10;
● To use the developed schemes for tuning exchange web-services.</p>
        <p>Figure 2 represents the contents of CSI Information Exchange Package and the screen shots
from CSI web interfaces [Fig.2].</p>
        <sec id="sec-3-4-1">
          <title>9 https://www.eclipse.org/papyrus/</title>
          <p>10 Statistical Data and Metadata Exchange (SDMX), https://sdmx.org/</p>
          <p>To support the lifecycle of CSI Information Exchange Package the authors consider efficient
to implement NIEM methodology for IEPD building. The main actors are the developers of agency
information system responsible for the information exchange (developers), domain experts, supporting
the development of the unified data model (domain ontology), and domain stewards with the authority
to modify it.</p>
          <p>
            During steps (
            <xref ref-type="bibr" rid="ref1">1</xref>
            ) Scenario Planning and (
            <xref ref-type="bibr" rid="ref2">2</xref>
            ) Requirements Analysis, the developers use their
own tools, resources and follow the agency regulations. To work with the suggested solution at the
next steps, they get access to web interfaces and download External Design Tool.
          </p>
          <p>
            At step (
            <xref ref-type="bibr" rid="ref3">3</xref>
            ) Mapping and Modeling, a developer: (
            <xref ref-type="bibr" rid="ref1">1</xref>
            ) imports the current version of domain
ontology; (
            <xref ref-type="bibr" rid="ref2">2</xref>
            ) creates a new UML exchange model; (
            <xref ref-type="bibr" rid="ref3">3</xref>
            ) maps this model with the developed
Architecture Context and fills it with typical content, if necessary, or (
            <xref ref-type="bibr" rid="ref4">4</xref>
            ) adds his own elements in
UML notation. Thus, the elements of the exchange model will have the link to the domain ontology
entities associated via indicated IRIs.
          </p>
          <p>
            At step (
            <xref ref-type="bibr" rid="ref4">4</xref>
            ), Building and Validating, the developed exchange model gets formal (OCL) and
program (embedded program code) validation. If there is no matching element in the domain ontology,
the tool automatically creates an extension proposal. It indicates both the suggested element and its
place in domain ontology.
          </p>
          <p>
            At step (
            <xref ref-type="bibr" rid="ref5">5</xref>
            ) Assembling and Documenting, the tool assembles the CSI Information Exchange
Package that archives the results of modeling. As described in section 3.3 it includes information
exchange model, extension proposal (if necessary) and supplementary files (UML diagrams, test data,
XSD and WSDL schemas, etc.). The REST service transfers the package to the Data Model Catalog.
          </p>
          <p>
            At step (
            <xref ref-type="bibr" rid="ref6">6</xref>
            ) Publishing and Implementing, domain experts analyze the received package using
Domain Management tools. They check the package and the suggested extension proposals. They can
accept or decline them, as well as suggest matching domain elements or making more precise
mappings. If the extension proposal contains concepts and data still not reflected in the unified data
model, the domain experts can refine or extend it in compliance with the developed information
exchange model. After the approval the domain steward, publishes the package in the catalog for
further reuse. Notification informs the developers about all decisions, package status and domain
ontology updates.
          </p>
        </sec>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>4. Conclusion</title>
      <p>Semantic interoperability is the point of great importance for the integration of information
systems in heterogeneous environment of cross-agency interaction. The authors suggest combining the
informative richness of semantic models describing the domain with the power of industrial solutions
for object-oriented data exchange. It is necessary to create the technology and software tools to
implement this approach and to support the developers of interacting information systems.</p>
      <p>This paper demonstrates the solution allowing semantically map the models of interacting
information systems with a unified data model (domain otology) during the development of
information exchange package. Indication of IRIs in the object model allows enriching the formal
representation of the object structure, for example, in the form of an XSD schema, with additional
information. Using the developed models, the special tools can generate exchange interfaces and
automatically adjust semantic web services. Represented solution provides an unambiguous
correspondence between the object and semantic models throughout the development cycle and
ensures the transformation of models, which, in its turn, will serve to implement the semantic service
bus for the arrangement of cross-agency information sharing.</p>
      <p>All demo links and detailed instructions for the demonstration of presented solution are
available on http://csi.semanticpro.org/material2021.htm.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>Government</given-names>
            <surname>Information</surname>
          </string-name>
          <string-name>
            <surname>Sharing</surname>
          </string-name>
          &amp;
          <article-title>Advanced Insight and Analytics. The National Information Exchange Model (NIEM)</article-title>
          .
          <source>IBM Software Information Management</source>
          ,
          <year>2010</year>
          . Available at: http://www.acceleratedim.com/whitepapers/IBM-NIEM-Whitepaper-Final.
          <source>pdf (accessed 03.09</source>
          .
          <year>2021</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>NIEM</given-names>
            <surname>User Guide Vol</surname>
          </string-name>
          .
          <volume>1</volume>
          ,
          <year>2008</year>
          . Available at: https://reference.niem.gov/niem/guidance/userguide/vol1/user-guide-vol1.
          <source>pdf (accessed 03.09</source>
          .
          <year>2021</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>Peristeras</given-names>
            <surname>Vassilios</surname>
          </string-name>
          . Semantic Standards:
          <article-title>Preventing Waste in the Information Industry</article-title>
          .
          <source>IEEE Intelligent Systems</source>
          . Vol.
          <volume>28</volume>
          . P.
          <volume>72</volume>
          -
          <fpage>75</fpage>
          . doi:
          <volume>10</volume>
          .1109.
          <string-name>
            <surname>MIS</surname>
          </string-name>
          .
          <year>2013</year>
          .
          <volume>115</volume>
          ,
          <year>2013</year>
          . Available at: https://ieeexplore.ieee.org/document/6682939/ (accessed 03.09.
          <year>2021</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <surname>Walaa</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          <string-name>
            <surname>Ismail</surname>
            , Mona,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Nasr</surname>
            , Torky,
            <given-names>I. Sultan Ayman E.</given-names>
          </string-name>
          <string-name>
            <surname>Khedr</surname>
          </string-name>
          .
          <article-title>Semantic Conflicts Reconciliation as a Viable Solution for Semantic Heterogeneity Problems</article-title>
          . (IJACSA) International
          <source>Journal of Advanced Computer Science and Applications</source>
          . Vol.
          <volume>4</volume>
          . No.
          <issue>4</issue>
          ,
          <year>2013</year>
          . Available at: https://pdfs.semanticscholar.
          <source>org/22bb/9c1c27049fce16d1546c54d51e0ede2854d8.pdf (accessed 03.09</source>
          .
          <year>2021</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <surname>Madnick</surname>
            <given-names>S.E.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Zhu H</surname>
          </string-name>
          .
          <article-title>Improving data quality through effective use of data semantics</article-title>
          ,
          <source>Data and Knowledge Engineering</source>
          ,
          <volume>59</volume>
          (
          <issue>2</issue>
          ). pp.
          <fpage>460</fpage>
          -
          <lpage>475</lpage>
          ,
          <year>2006</year>
          . Available at: http://citeseerx.ist.psu.edu/viewdoc/download?doi
          <source>=10.1.1.89.3747&amp;rep=rep1&amp;type=pdf (accessed 03.09</source>
          .
          <year>2021</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>Semantic</given-names>
            <surname>Information</surname>
          </string-name>
          <article-title>Modeling for Federation (SIMF) Request for</article-title>
          Proposal,
          <year>2012</year>
          . Available at: https://www.omg.org/cgi-bin/doc?ad/11-12-10
          <source>(accessed 03.09</source>
          .
          <year>2021</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>Semantic</given-names>
            <surname>Information Modeling for Federation</surname>
          </string-name>
          ,
          <source>EMTECH Semantic Technology &amp; Business Conference</source>
          ,
          <year>2011</year>
          . Available at: http://ontolog.cim3.net/file/work/OntologySummit2012/2012-03- 01_
          <article-title>Ontology-for-Systems-Federation-n-Integration/OntologSummit2012_Semantic-InformationModeling-for-</article-title>
          <string-name>
            <surname>Federation</surname>
          </string-name>
          --
          <source>CoryCasanave_20120301.pdf (accessed 03.09</source>
          .
          <year>2021</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <surname>Peffers</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tuunanen</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rothenberger</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <year>a</year>
          .,
          <string-name>
            <given-names>A.</given-names>
            <surname>Chatterjee</surname>
          </string-name>
          ,
          <source>S. Design Science Research Methodology for Information Systems Research</source>
          ,
          <year>January 2008</year>
          ,
          <source>Journal of Management Information Systems</source>
          <volume>24</volume>
          (
          <issue>3</issue>
          ):
          <fpage>45</fpage>
          -
          <lpage>77</lpage>
          ,
          <year>2013</year>
          . DOI:
          <volume>10</volume>
          .2753/MIS0742-1222240302
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <surname>Akatkin</surname>
            ,
            <given-names>Yu.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Yasinovskaya</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Bich</surname>
          </string-name>
          .
          <article-title>Semantic Information Management: The Approach to Semantic Assets Development Lifecycle</article-title>
          .
          <source>Proceedings of GRID</source>
          <year>2018</year>
          , Available at: http://ceurws.org/Vol-
          <volume>2267</volume>
          /
          <fpage>447</fpage>
          -452-paper-85.
          <source>pdf (accessed 03.09</source>
          .
          <year>2021</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>