<!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>SemFrameX - Towards a Framework for the Semantic Justification of BPMN Adaptations</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Technische Universita¨t Dresden</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Chair of Wirtschaftsinformatik</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>esp. Systems Development</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Dresden</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Germany richard.braun@tu-dresden.de</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Extension and Adaptation of BPMN</institution>
        </aff>
      </contrib-group>
      <fpage>13</fpage>
      <lpage>20</lpage>
      <abstract>
        <p>In recent years numerous extensions and adaptations of the BPMN evolved, since model users aim to both exploit the benefits of the modeling standard and adapt BPMN to particular domain peculiarities or project requirements. Methodical support for conducting such adaptations is generally rare and very focused on the abstract syntax, which is actually insufficient, since particular semantics are more relevant. Consequently, it seems to be reasonable to explicitly conduct semantical analysis and comparison checks before extending or adapting BPMN. However, appropriate semantic specifications of BPMN are missing. After introducing and motivating the entire issue, we therefore outline the SemFrameX framework that aims to specify the BPMN meta model semantics with a special consideration of ontic, epistemological, conceptual, linguistic and pragmatics aspects.</p>
      </abstract>
      <kwd-group>
        <kwd>Semantics</kwd>
        <kwd>Meta Modeling</kwd>
        <kwd>Extensibility</kwd>
        <kwd>Process Modeling</kwd>
        <kwd>Enterprise Modeling Languages</kwd>
        <kwd>Semantics Framework</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        is (widely [
        <xref ref-type="bibr" rid="ref30 ref7">30,7</xref>
        ]) well-defined, the issue of language adaptation is only supported
to a very limited extent implicating both a lack of procedural assistance and
semantics [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. Research on BPMN adaptations merely focuses the syntax and
semantic issues are only discussed occasionally [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ].
      </p>
      <p>
        We assume that this is strongly amplified by the general syntax focus of
the BPMN specification, which provides only very short and limited semantic
references in natural language statements [
        <xref ref-type="bibr" rid="ref31">31</xref>
        ]. This might be caused by the rather
technical origin of BPMN. Further, parts of BPMN are intended to be executable
[31, p. 435] implicating formal behavioral semantics [6, p. 3402], while a range
of concepts have material semantics (e.g., Manual Tasks or Pools). Both types
of semantics actually require different kinds of semantic specification (cf. [
        <xref ref-type="bibr" rid="ref33">33</xref>
        ]).
Due to the stated issues it is difficult to conduct well-justified adaptations of
BPMN, since the BPMN specification itself does not provide a solid and detailed
semantic base. To the best of our knowledge there is no complete semantic
analysis or description of BPMN, which provides respective semantic domain
concepts and mappings. Existing research works are either not very mature [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ],
focus syntactical aspects [
        <xref ref-type="bibr" rid="ref30 ref36">30,36</xref>
        ] or address only the model layer but not the
meta model layer [
        <xref ref-type="bibr" rid="ref29">29</xref>
        ]. However, imprecise or even missing semantic specification
of EMLs is a general issue that is under-investigated [21, p. 485], [1, p. 108],
although semantics seem to be an extremely promising language driver (cf. [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]).
      </p>
      <p>This paper therefore aims to bring light into the dark of semantic
specifications in BPMN. Therefore, the semantic issue of BPMN is stated in Section 2.
Section 3 then motivates the semantics first approach and outlines the
SemFrameX framework by introducing its dimensions. The paper ends with a short
outlook in Section 4.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Issues with Semantics</title>
      <p>
        Several authors criticize the lack of semantic specifications in EMLs and emphasize
their importance [20, pp. 67-69], [37, pp. 690, 706]. But despite several approaches
(e.g., [
        <xref ref-type="bibr" rid="ref22 ref26 ref32">22,32,26</xref>
        ]) no accepted and prevalent standard evolved so far and also the
explication of required modeling concepts is still rudimental [
        <xref ref-type="bibr" rid="ref16 ref19">19,16</xref>
        ]. Instead, both
the design of EMLs and EML extensions strongly focus the syntax perspective,
while semantics and pragmatics are more or less ignored [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. In the context of
BPMN, we assume that the following reasons may cause the unsatisfying struggles
with semantics.
      </p>
      <p>Awareness of relevant parts: There is a lack of consensus about those parts,
which determine semantics. The specification of semantics is rather diffuse and
remains mostly informal. It is therefore advised to take an integrated view on
semantics in regard of the meta model constructs itself as well as the used textual
elements.</p>
      <p>
        Formal and material semantics: In contrast to formal domains in the field
of Computer Science (CS) [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ], the domain of enterprises and business process
cannot be completely formalized (material semantics [
        <xref ref-type="bibr" rid="ref33">33</xref>
        ]). However, some tasks
or purposes require the definition of formal specifications (formal semantics
[
        <xref ref-type="bibr" rid="ref17 ref6">17,6</xref>
        ]). Respective differences and also integration points should be investigated
(hybrid semantics [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ]).
      </p>
      <p>
        Ambiguity: Enterprises are complex socio-technical information systems
affecting several aspects – both real-world things and artificial things [
        <xref ref-type="bibr" rid="ref26">26</xref>
        ]. This
underlines the importance of subjective interpretation depending on personal
experiences, cognition and mental conceptualization [
        <xref ref-type="bibr" rid="ref27">27</xref>
        ], which is especially
relevant within collaborative process modeling in order to avoid misunderstandings,
for instance. It is hence necessary to take ontic and epistemological issues into
account in order to become aware of its impact and respective consequences for
language design and language application.
      </p>
      <p>
        Multiple research fields: The investigation of semantics is an essential topic in
philosophy and cognition research that addresses fundamental epistemological
questions. In the CS community, semantics is relevant in the field of Information
Retrieval or Semantic Web, for instance. Both areas seem to be relevant in the
Information Systems (IS) discipline. However, integration is not trivial due to
differing semantic understandings (cf. [
        <xref ref-type="bibr" rid="ref20 ref38">38,20</xref>
        ]).
3
3.1
      </p>
    </sec>
    <sec id="sec-3">
      <title>SemFrameX - Integrated Framework Approach</title>
      <sec id="sec-3-1">
        <title>Semantically Driven Justification of BPMN Adaptations</title>
        <p>It becomes obvious that semantics are crucial in the context of BPMN and also
indispensable for BPMN adaptation. We therefore argue that all adaptations
should follow a semantics first approach in the sense of the following two parts:</p>
        <p>
          Explication of the expected semantics: First, the expected semantics in the
sense of required domain concepts should be explicated in order to express
objectives and requirements [
          <xref ref-type="bibr" rid="ref13 ref16 ref35">35,13,16</xref>
          ]. The expected semantics are closely coupled
with the underlying pragmatic intention [
          <xref ref-type="bibr" rid="ref4">4</xref>
          ]. For instance, if the user just aims to
document particular real-world aspects then material semantics are applicable
(e.g., [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ]). If the user intends to enhance BPMN for some automation tasks
then formal semantics might become relevant (e.g., [
          <xref ref-type="bibr" rid="ref6">6</xref>
          ]). Also hybrid semantics
as combination of both aspects is imaginable (e.g., in case of clinical decision
systems, where supporting processes need to be automated [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ]).
        </p>
        <p>
          Justification of EML adaptation: Afterwards it is necessary to compare the
expressiveness of BPMN with the required expressiveness of a particular situation
in order to justify and elaborate the need for adaptation based on semantic
correspondence checks [1, p. 100]. The comparison finally leads to respective
syntactical constructs [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ] and might determine the type of extension (e.g., a
profile-based BPMN dialect [
          <xref ref-type="bibr" rid="ref10">10</xref>
          ]).
3.2
        </p>
      </sec>
      <sec id="sec-3-2">
        <title>Framework Architecture</title>
        <p>As stated in Section 1, semantics in the Enterprise Modeling (EM) context are
multi-faceted, not trivial and little considered in literature so far. We therefore
aim to tackle the issue by analyzing several dimensions in regard of semantics,
which constitutes as the SemFrameX 1 framework that is presented in Figure 1.
With respect to the limited space of this paper, the architecture is introduced by
a brief presentation of the single dimensions.</p>
        <p>
          Representation Dimension
Fundamentally, any semantic consideration finally leads to an analysis of those
things that are somehow referred by symbols of a language [
          <xref ref-type="bibr" rid="ref39">39</xref>
          ]. It is therefore
necessary to analyze and categorize different types of things, e.g. material things
or artificial things [
          <xref ref-type="bibr" rid="ref26">26</xref>
          ]. As we consider the meta model layer, a thing itself is
understood as an already abstracted class of things with common features within
a particular area of discourse. Hence we consider an implicit abstraction step of
modelers, which have to be inferred from single, detectable entities to a class
of those entities. More precisely, the fundamental type of respective classes of
things in regard of their actual existence in reality (realism vs. idealism) as
well as their perception (objectively perceptible vs. subjectively perceptible)
have to be considered (adapted from [
          <xref ref-type="bibr" rid="ref14 ref3">14,3</xref>
          ]). This categorization is important for
contingent epistemological positions like Positivism, Critical Rationalism, Radical
Constructivism or Methodic Constructivism. Those positions largely determine
respective theories of truth, which are especially relevant for the differentiation
between formal and material semantics [
          <xref ref-type="bibr" rid="ref33">33</xref>
          ] as well as for the identification of
differences between conceptualizations of things [
          <xref ref-type="bibr" rid="ref25">25</xref>
          ].
1 SemFrame stands for semantic framework, while the suffix X emphasizes its relevance
for extensions and adaptations.
        </p>
      </sec>
      <sec id="sec-3-3">
        <title>Conceptualization Dimension</title>
        <p>
          Conceptualization is understood as the individual understanding of the stated
class of things. This conceptualization is a central point of analysis, as it depends
on the personal understanding of a particular meta model and finally refers to
some things s/he has in mind. The only exception is represented by a class of
things that is perceived as real and objectively perceptible (Positivism). In each
other constellation, the conceptualization is strongly subject-dependent and can
cause variant interpretations of meta model constructs by interpreting them
differently, for instance [
          <xref ref-type="bibr" rid="ref27">27</xref>
          ].
3.5
        </p>
      </sec>
      <sec id="sec-3-4">
        <title>Pragmatic Dimension</title>
        <p>
          Generally, the application context determines the expected capabilities of a
modeling language [38, p. 5] and the concrete modeling purpose plays an immanent
role within conceptualization [4, p. 436]. Some authors state that the real meaning
of a language finally results from its factual usage [4, p. 438], serving a particular
utility [
          <xref ref-type="bibr" rid="ref35">35</xref>
          ]. Hence, the underlying or intended pragmatics also influence the aimed
semantics. If BPMN is intended to be used for pure documentation then material
semantics are relevant, causing a descriptive mode of the semantics (cf. [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ]).
In contrast, BPMN can be also used to describe (at least partly) automatable
processes or message exchange services, which rather cause formal semantics and
represent a normative or prescriptive character.
3.6
        </p>
      </sec>
      <sec id="sec-3-5">
        <title>Representation Dimension</title>
        <p>
          Conceptualizations and things (in case of Positivism) need to be explicated in
any form. Ontologies are often proclaimed as means for semantic annotations
[
          <xref ref-type="bibr" rid="ref22 ref23">22,23</xref>
          ]. Basically, even those rather minimalistic languages have a certain syntax
and semantics, which have to be taken into account. Further, also the semantics
of the meta modeling language used to design the BPMN meta model has to
be considered, as it refers indirectly to some artificial things of constructs (e.g.,
Generalizations). These aspects are covered by the framework element modeling
language. In addition, natural language emphasizes the importance of single words
(sememe) as basic source of ambiguity. While structural issues are covered by the
above mentioned dimensions, natural language based ambiguity is actually the
most important issue, since all the stated problems finally lead to lexical topics
like synonym and homonym conflicts [
          <xref ref-type="bibr" rid="ref34">34</xref>
          ]. For instance, further research on other
lexical types like hypernyms, hyponyms, meronyms, holonyms, antonyms and
troponyms is needed [22, p. 1628], [38, p. 8], [28, p. 89].
3.7
        </p>
      </sec>
      <sec id="sec-3-6">
        <title>Consensus Dimension</title>
        <p>Despite divergence and ambiguity, it is important to find a particular consensus on
semantics in the sense of an agreement of different personal conceptualizations in
order to provide an applicable language within a language community. Although
Consensus Theory of Truth is usually applied in Constructivism and Critical
Rationalism, we suggest its consequent application, since process modeling usually
covers at least some things that are not invariant interpretable. After finding a
particular consensus on the semantic specification of either the entire BPMN or
prospective BPMN extensions, semantic comparison techniques can be applied in
order to justify extension or adaptation need (right side in Figure 1). Currently,
we intend to conduct specific ontological comparisons based on generic enterprise
ontologies and domain-specific ontologies for this task.
4</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>Conclusion</title>
      <p>This paper presents an overview of a research-in-progress project aiming to
elaborate an integrated and multi-faceted semantic description technique for
BPMN based on an analysis of ontic and epistemological aspects. The integrated
semantic description of BPMN elements should facilitate the justification of
potential BPMN extensions or adaptations. Further, the aimed semantic
description technique should support the specification of respective requirements
profiles, which are the base for comparison with semantics of BPMN. The initial
architecture of the SemFrameX framework is outlined and its dimensions are
briefly introduced.</p>
      <p>Further research is manifold, as each dimension has to be investigated in
detail. We therefore aim to start with the core of the framework by characterizing
and classifying different types of things and respective consequences for their
interpretation (formal or material semantics). This is closely related to current
investigations in the field of hybrid semantics aiming to specify and integrate both
types in BPMN and support the derivation of BPMN extensions and dialects.
Furthermore, an inductive application of the proposed architecture to other EMLs
seems to be promising.</p>
      <p>Acknowledgement: This paper presents results from the research project
SFB Transregio 96, which is funded by the German Research Foundation (DFG).
The author further appreciates the helpful reviewer comments on this paper.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Anaya</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Berio</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Harzallah</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Heymans</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          , Matuleviˇcius, R.,
          <string-name>
            <surname>Opdahl</surname>
            ,
            <given-names>A.L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Panetto</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Verdecho</surname>
            ,
            <given-names>M.J.:</given-names>
          </string-name>
          <article-title>The unified enterprise modelling language - overview and further work</article-title>
          .
          <source>Computers in Industry</source>
          <volume>61</volume>
          (
          <issue>2</issue>
          ),
          <fpage>99</fpage>
          -
          <lpage>111</lpage>
          (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Atkinson</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gerbig</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fritzsche</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Modeling language extension in the enterprise systems domain</article-title>
          .
          <source>In: Proceedings of the 17th IEEE EDOC</source>
          . pp.
          <fpage>49</fpage>
          -
          <lpage>58</lpage>
          (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Becker</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Holten</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Knackstedt</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Niehaves</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          :
          <article-title>Wissenschaftstheoretische grundlagen und ihre rolle fu¨r eine konsensorientierte informationsmodellierung pp</article-title>
          .
          <fpage>307</fpage>
          -
          <lpage>334</lpage>
          (
          <year>2003</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Bjekovic</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Proper</surname>
            ,
            <given-names>H.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sottet</surname>
            ,
            <given-names>J.S.:</given-names>
          </string-name>
          <article-title>Embracing pragmatics</article-title>
          .
          <source>In: Conceptual Modeling. LNCS</source>
          , vol.
          <volume>8824</volume>
          , pp.
          <fpage>431</fpage>
          -
          <lpage>444</lpage>
          (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Bjekovic</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Proper</surname>
            ,
            <given-names>H.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sottet</surname>
            ,
            <given-names>J.S.:</given-names>
          </string-name>
          <article-title>Enterprise modelling languages - just enough standardisation? In: Business Modeling and Software Design</article-title>
          .
          <source>LNBIP</source>
          , vol.
          <volume>173</volume>
          , pp.
          <fpage>1</fpage>
          -
          <lpage>23</lpage>
          (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Bork</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fill</surname>
            ,
            <given-names>H.G.</given-names>
          </string-name>
          :
          <article-title>Formal aspects of enterprise modeling methods: A comparison framework</article-title>
          .
          <source>In: Proceedings of the 47th HICSS</source>
          . pp.
          <fpage>3400</fpage>
          -
          <lpage>3409</lpage>
          (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Braun</surname>
          </string-name>
          , R.:
          <article-title>Behind the scenes of the bpmn extension mechanism - principles, problems and options for improvement</article-title>
          .
          <source>In: Proc. of the 3rd MODELSWARD</source>
          . pp.
          <fpage>403</fpage>
          -
          <lpage>410</lpage>
          (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Braun</surname>
          </string-name>
          , R.:
          <article-title>Towards the state of the art of extending enterprise modeling languages</article-title>
          .
          <source>In: Proc. of the 3rd MODELSWARD</source>
          . pp.
          <fpage>394</fpage>
          -
          <lpage>402</lpage>
          (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Braun</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Esswein</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          :
          <article-title>Classification of domain-specific bpmn extensions</article-title>
          .
          <source>In: The Practice of Enterprise Modeling. LNBIP</source>
          , vol.
          <volume>147</volume>
          , pp.
          <fpage>42</fpage>
          -
          <lpage>57</lpage>
          (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Braun</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Esswein</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          :
          <article-title>Designing dialects of enterprise modeling languages with the profiling technique</article-title>
          .
          <source>In: Proceedings of the 19th IEEE EDOC</source>
          . pp.
          <fpage>60</fpage>
          -
          <lpage>67</lpage>
          (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Braun</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Esswein</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          :
          <article-title>Extending the mof for the adaptation of hooks, aspects, plug-ins and add-ons</article-title>
          .
          <source>In: Model and Data Engineering</source>
          . pp.
          <fpage>28</fpage>
          -
          <lpage>38</lpage>
          . LNCS (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Braun</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Esswein</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          :
          <article-title>Towards hybrid semantics of enterprise modeling languages</article-title>
          .
          <source>In: Proc. of the 4th MODELSWARD</source>
          (
          <year>2016</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Braun</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schlieter</surname>
          </string-name>
          , H.:
          <article-title>Requirements-based development of bpmn extensions: The case of clinical pathways</article-title>
          .
          <source>In: IEEE 1st RE-BPMN</source>
          . pp.
          <fpage>39</fpage>
          -
          <lpage>44</lpage>
          (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Braun</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Esswein</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          :
          <article-title>Eine methode zur konzeption von forschungsdesigns in der konzeptuellen modellierungsforschung</article-title>
          .
          <source>In: Data Warehousing</source>
          . pp.
          <fpage>143</fpage>
          -
          <lpage>172</lpage>
          (
          <year>2006</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Chinosi</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Trombetta</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Bpmn: An introduction to the standard</article-title>
          .
          <source>Computer Standards &amp; Interfaces</source>
          <volume>34</volume>
          (
          <issue>1</issue>
          ),
          <fpage>124</fpage>
          -
          <lpage>134</lpage>
          (
          <year>2012</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <surname>De Kinderen</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ma</surname>
            ,
            <given-names>Q.</given-names>
          </string-name>
          :
          <article-title>Requirements engineering for the design of conceptual modeling languages - a goal-and value-oriented approach</article-title>
          .
          <source>Applied Ontology</source>
          (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <surname>Engels</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hausmann</surname>
            ,
            <given-names>J.H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Heckel</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sauer</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Dynamic meta modeling: A graphical approach to the operational semantics of behavioral diagrams in uml</article-title>
          .
          <source>In: UML 2000 - The Unified Modeling Language</source>
          , pp.
          <fpage>323</fpage>
          -
          <lpage>337</lpage>
          . Springer (
          <year>2000</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18. Fern´andez,
          <string-name>
            <surname>H.F.</surname>
          </string-name>
          , Palacios-Gonz´alez, E., Garc´ıa-D´ıaz, V.,
          <string-name>
            <surname>G</surname>
          </string-name>
          -Bustelo,
          <string-name>
            <surname>B.C.P.</surname>
          </string-name>
          , Mart´ınez,
          <string-name>
            <given-names>O.S.</given-names>
            ,
            <surname>Lovelle</surname>
          </string-name>
          ,
          <string-name>
            <surname>J.M.C.</surname>
          </string-name>
          :
          <article-title>Sbpmn - an easier business process modeling notation for business users</article-title>
          .
          <source>Computer Standards &amp; Interfaces</source>
          <volume>32</volume>
          (
          <issue>1</issue>
          ),
          <fpage>18</fpage>
          -
          <lpage>28</lpage>
          (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19.
          <string-name>
            <surname>Frank</surname>
            ,
            <given-names>U.</given-names>
          </string-name>
          :
          <article-title>Domain-specific modeling languages: requirements analysis and design guidelines</article-title>
          .
          <source>In: Domain Engineering</source>
          , pp.
          <fpage>133</fpage>
          -
          <lpage>157</lpage>
          . Springer (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          20.
          <string-name>
            <surname>Harel</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rumpe</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          :
          <article-title>Meaningful modeling: what's the semantics of semantics</article-title>
          ?
          <source>Computer</source>
          <volume>37</volume>
          (
          <issue>10</issue>
          ),
          <fpage>64</fpage>
          -
          <lpage>72</lpage>
          (
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          21.
          <string-name>
            <surname>Harzallah</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Berio</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Opdahl</surname>
            ,
            <given-names>A.L.</given-names>
          </string-name>
          :
          <article-title>New perspectives in ontological analysis: Guidelines and rules for incorporating modelling languages into ueml</article-title>
          .
          <source>Information Systems</source>
          <volume>37</volume>
          (
          <issue>5</issue>
          ),
          <fpage>484</fpage>
          -
          <lpage>507</lpage>
          (
          <year>2012</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          22. H¨offerer, P.:
          <article-title>Achieving business process model interoperability using metamodels and ontologies</article-title>
          .
          <source>In: Proceedings of the 15th ECIS</source>
          . pp.
          <fpage>1620</fpage>
          -
          <lpage>1631</lpage>
          (
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          23.
          <string-name>
            <surname>Kaczmarek</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Categories of ontologies' applications in the realm of enterprise modeling</article-title>
          .
          <source>In: Proceedings of IEEE 17th CBI</source>
          . vol.
          <volume>1</volume>
          , pp.
          <fpage>98</fpage>
          -
          <lpage>107</lpage>
          (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          24. de Kinderen,
          <string-name>
            <given-names>S.</given-names>
            ,
            <surname>Ma</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Q.</given-names>
            ,
            <surname>Proper</surname>
          </string-name>
          ,
          <string-name>
            <surname>H.A.</surname>
          </string-name>
          :
          <article-title>Model bundling: Towards a value-based componential approach for language engineering</article-title>
          .
          <source>In: Proceedings of the 8th VMBO</source>
          (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          25.
          <string-name>
            <surname>van der Linden</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hoppenbrouwers</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Challenges of identifying communities with shared semantics in enterprise modeling</article-title>
          .
          <source>In: The Practice of Enterprise Modeling. LNBIP</source>
          , vol.
          <volume>134</volume>
          , pp.
          <fpage>160</fpage>
          -
          <lpage>171</lpage>
          (
          <year>2012</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref26">
        <mixed-citation>
          26.
          <string-name>
            <surname>van der Linden</surname>
            , D., van Zee,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>On the semantic feature structure of modeling concepts: an empirical study</article-title>
          .
          <source>In: Proc. IEEE 16th CBI</source>
          . pp.
          <fpage>158</fpage>
          -
          <lpage>165</lpage>
          . IEEE (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref27">
        <mixed-citation>
          27.
          <string-name>
            <surname>van der Linden</surname>
          </string-name>
          , D.:
          <article-title>Personal semantics of meta-concepts in conceptual modeling languages</article-title>
          .
          <source>Ph.D. thesis</source>
          , Radboud University Nijmegen (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref28">
        <mixed-citation>
          28.
          <string-name>
            <surname>Mendling</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Leopold</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pittke</surname>
          </string-name>
          , F.:
          <article-title>25 challenges of semantic process modeling</article-title>
          .
          <source>IJISEBC</source>
          <volume>1</volume>
          (
          <issue>1</issue>
          ),
          <fpage>78</fpage>
          -
          <lpage>94</lpage>
          (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref29">
        <mixed-citation>
          29. Mickeviˇciu¯te˙, E.,
          <string-name>
            <surname>Butleris</surname>
          </string-name>
          , R.:
          <article-title>Towards the combination of bpmn process models with sbvr business vocabularies and rules</article-title>
          .
          <source>In: Information and Software Technologies</source>
          , pp.
          <fpage>114</fpage>
          -
          <lpage>121</lpage>
          . Springer (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref30">
        <mixed-citation>
          30. Natschl¨ager, C.:
          <article-title>Towards a bpmn 2.0 ontology</article-title>
          .
          <source>In: Business Process Model and Notation</source>
          , pp.
          <fpage>1</fpage>
          -
          <lpage>15</lpage>
          . Springer (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref31">
        <mixed-citation>
          31. OMG:
          <article-title>Business Process Model and Notation (BPMN) - Version 2.0</article-title>
          . Object Management Group (OMG) (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref32">
        <mixed-citation>
          32.
          <string-name>
            <surname>Opdahl</surname>
            ,
            <given-names>A.L.</given-names>
          </string-name>
          :
          <article-title>Anatomy of the unified enterprise modelling ontology</article-title>
          .
          <source>In: Enterprise Interoperability</source>
          , pp.
          <fpage>163</fpage>
          -
          <lpage>176</lpage>
          . Springer (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref33">
        <mixed-citation>
          33.
          <string-name>
            <surname>Pfeiffer</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gehlert</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>A framework for comparing conceptual models</article-title>
          .
          <source>In: Proceedings EMISA</source>
          . pp.
          <fpage>108</fpage>
          -
          <lpage>122</lpage>
          (
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref34">
        <mixed-citation>
          34.
          <string-name>
            <surname>Pittke</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Leopold</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mendling</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          :
          <article-title>Automatic detection and resolution of lexical ambiguity in process models</article-title>
          .
          <source>IEEE Trans. on Soft. Eng</source>
          .
          <volume>41</volume>
          (
          <issue>6</issue>
          ),
          <fpage>526</fpage>
          -
          <lpage>544</lpage>
          (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref35">
        <mixed-citation>
          35.
          <string-name>
            <surname>Proper</surname>
            ,
            <given-names>H.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Verrijn-Stuart</surname>
            ,
            <given-names>A.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hoppenbrouwers</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>On utility-based selection of architecture-modelling concepts</article-title>
          .
          <source>In: Proc. of the 2nd APCCM</source>
          . pp.
          <fpage>25</fpage>
          -
          <lpage>34</lpage>
          (
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref36">
        <mixed-citation>
          36.
          <string-name>
            <surname>Rospocher</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ghidini</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Serafini</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          :
          <article-title>An ontology for the business process modelling notation</article-title>
          .
          <source>In: Formal Ontology in Information Systems - Proceedings of the 8th FOIS</source>
          . vol.
          <volume>267</volume>
          , pp.
          <fpage>133</fpage>
          -
          <lpage>146</lpage>
          . IOS Press (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref37">
        <mixed-citation>
          37.
          <string-name>
            <surname>Santos</surname>
            ,
            <given-names>P.S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Almeida</surname>
            ,
            <given-names>J.P.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Guizzardi</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          :
          <article-title>An ontology-based analysis and semantics for organizational structure modeling in the aris method</article-title>
          .
          <source>Information Systems</source>
          <volume>38</volume>
          (
          <issue>5</issue>
          ),
          <fpage>690</fpage>
          -
          <lpage>708</lpage>
          (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref38">
        <mixed-citation>
          38.
          <string-name>
            <surname>Thalheim</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          :
          <article-title>Syntax, semantics and pragmatics of conceptual modelling</article-title>
          .
          <source>In: Natural Language Processing and Information Systems</source>
          , pp.
          <fpage>1</fpage>
          -
          <lpage>10</lpage>
          . Springer (
          <year>2012</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref39">
        <mixed-citation>
          39.
          <string-name>
            <surname>Ullmann</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          : Semantics:
          <article-title>An introduction to the science of meaning (</article-title>
          <year>1979</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>