<!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>Meta-Modelling as a Means for Improved Communication and Interoperability - The Case of Frisco</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Petia Wohed</string-name>
          <email>petia.wohed@cran.uhp-nancy.fr</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Birger Andersson</string-name>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Centre de Recherche en Automatique de Nancy Universit ́e Henri Poincar ́e, Nancy 1/CNRS BP239</institution>
          ,
          <addr-line>54506 Vandoeuvre les Nancy</addr-line>
          ,
          <country country="FR">France</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Department of Computer and Systems Sciences Stockholm University/The Royal Institute of Technology Forum 100</institution>
          ,
          <addr-line>SE-164 40 Kista</addr-line>
          ,
          <country country="SE">Sweden</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Unclear and disparate terminology are causing problems in the area of information system development. To address these issues, modelling frameworks and ontologies based on solid philosophical and logical foundations have been developed. Hypothesizing that a diagrammatic interface will be beneficial for comprehension and communication resulting in wider dissemination, we propose a UML-based meta-model of one of those frameworks-Frisco. The analysis done during the development of the meta-model resulted in identification of a number of ambiguities in the framework. Discussion of these as well as suggestions of ways to solve them are also presented.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>
        Terminological fuzziness is characterizing the field of information systems
creating all kinds of problems. To address this, during the last decades, frameworks
like Frisco (Framework of Information Systems Concepts) [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] and BWW (Bunge,
Wand and Weber models) [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] were developed. The goals of those frameworks
coincides with the goals of ontology analysis and engineering [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], namely: to provide
a coherent system of concepts, the use of which would reduce misunderstandings
and ambiguities and would 1) support communication between stakeholder with
different needs and approaches 2) facilitate interoperability among systems and
3) be beneficial for requirement identification, reusability and reliability within
information system development process. Thus, the field of ontology engineering
has received a growing attention where ontologies like CYC [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] in the knowledge
representation area, and Toronto Virtual Enterprise (TOVE) and Enterprise
Ontology (EO) [
        <xref ref-type="bibr" rid="ref5 ref6">5, 6</xref>
        ] for enterprise modelling have been developed.
      </p>
      <p>Characteristic for all these approaches is that they rely on solid theoretical
work, are developed by mathematicians, logicians and/or computer scientists,
are well formalised and their initial representation is in some formal notation.
While this last property is an absolute requirement for achieving
interoperability and clear semantics, it is hardly beneficial when it comes to the fulfilment
of the communication goal mentioned above. Not every person involved in an
information system development process can be assumed to be skilled in reading
and understanding formal notations.</p>
      <p>
        To address the issue of comprehensibility, graphical formalisms has been
developed. For instance, in [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] a graphical meta-model was developed for
representation of BWW models. In this paper we report on using this approach when
developing such a meta-model for the Frisco framework. As in [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] we motivate
the approach by the following arguments.
      </p>
      <p>– The development of a meta-model that visualises the concepts currently
existing and the framework and the relationships between them will increase
the communication and understanding of the framework and facilitate its
use.
– The development of a meta-model will support analysis of the framework
and facilitate a further development of it.
– The existence of a meta-model will further facilitate analysis of Frisco with
respect to other existing approaches e.g., BWW, Tove, EO, etc. During such
analysis overlapping and discrepancies between the ontologies shall be
outlined which will result in a clearer positioning of Frisco according to the
other relevant works in the area.
– Meta-models of ontologies, in general, support the analysis of modelling
languages in the sense that they can be used as reference frameworks through
which the considered languages are analysed.
– The experience of the work on the development and utilisation of the
metamodel will contribute to the overall knowledge within Ontology Engineering
field.</p>
      <p>
        Unlike [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ], where the benefits of the developed meta-model were mainly
demonstrated for the purposes of the analysis of two grammars, i.e., according
to the fourth point outlined above, and only briefly exemplifying the second
point above, we are in this paper in detail demonstrating how the development
of a meta-model can benefit for the further development of a framework. We
have selected Frisco to be the subject for our work because, 1) it was specifically
developed for addressing the conceptualization within the Information Systems
domain, 2) we are interested in an cross-analysis between FRISCO and BWW
(and later on with EO and TOVE). As an initial step in such a cross-analysis,
the creation and use of graphical meta-models, e.g. the one developed for BWW
or the one for Frisco partially presented here, will be beneficial.
      </p>
      <p>
        As a graphical representation language, we are using UML class diagrams [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ].
This choice is motivated by the wide dispersion and knowledge of UML, often
also referred to as a de-facto standard for information system analysis and
development. UML class diagrams limits our expressive power to what can be stated
using those diagrams, but for the purposes of this paper they are adequate.
      </p>
      <p>The paper proceeds by presentation of Frisco and the development of
metamodel for it in the next section. In section 3, the results of the analysis of Frisco
provided during the development of the meta-model are presented and some
improvements suggested. Section 4, concludes the work and outlines directions
for further research.
2</p>
    </sec>
    <sec id="sec-2">
      <title>The Frisco framework</title>
      <p>As any other axiomatic system, Frisco starts by defining a small set of primitives
from which the rest of the concepts are gradually built up. It is divided into a
number of layers: a fundamental layer, an actor, actions and actands layer, a
system concepts layer, and an organizational and information system concepts
layer. Due to space limitation, in this paper we only present and work on the
the fundamental and actor, actions, and actands layers, which we discuss below.
2.1</p>
      <sec id="sec-2-1">
        <title>The Fundamental Layer</title>
        <p>The world is made up of Things. A thing is either an Elementary or a Composite
thing. Composite things are build up through Relationships. Relationships are sets
of binary tuples, the elements of which are things: the first element in a tuple
is called a Predicated thing and the second element a Predicator. Relationships
are themselves considered as things, which makes it possible to represent the
complex structures often existing in a domain.</p>
        <p>
          The formal definitions are reprinted from [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ] in table 1 in the Appendix. The
meta-model which we propose is drawn in figure 1. Generally, every concept is
represented by a class and in the lower right hand corner of every class the name
of the set as defined in table 1 is given.
        </p>
        <p>The relationships between concepts are captured either by generalisation/
specialisation constraints (i.e., isa relationships) or by ordinary relationships to
which we have given names either appearing in the formal definitions, or just
close to the natural language comprehension. The cardinality constraints are
derived from the formal definitions. Some rules like that “A Thing is either
Elementary or Composite” are directly captured in the graphical model (by joining
the ends of the corresponding isa relationships) while others like that “An
Elementary Thing is defined as a Thing which is not a Relationship...” can rather
indirectly be seen in the graphical model through the implications they bring
e.g., “The sets of Elementary things and Relationships are disjoint” and through
the reasoning that Relationships are kinds of (isa) Composite Things which in
turns are disjoint with the Elementary Things. Furthermore, for the sake of
explicitness we have introduced the class Pair, which does not have a formal
definition of its own. However, the concept Pair is used for defining
Relationships and distinguishing between unary relationships (consisting of one pair),
binary (i.e., relationships composed of a couple of pairs), ternary relationships
(consisting three pairs), and so on.</p>
        <p>According to the description in Frisco, Predicator and Predicated Things
do not need to be disjoint sets (so we have not joined their isa relationships
endings) but in most real life cases they are indeed disjoint. Furthermore, the
isa relationship between Relationship and Thing classes is derivable through the</p>
        <sec id="sec-2-1-1">
          <title>PredicatorP PreTdhicinagtedQ</title>
          <p>1 1
^ has * * ^ has
transitivity of the isa relationships from Relationship to Composite Thing to
Thing, but we have chosen to explicitly draw it in the model to directly depict
the definition of Relationship concept stating that a relationships is a thing.
Finally for this part of the framework, a Set Membership is a binary relationship
with the predicators has-element and is-element-of within its first and second pair
correspondingly. As instances of the class Predicator has-element and
is-elementof are not directly depicted in the graphical model. Also the relationship between
Elementary Thing, as consisting of Things that are not Relationships and that
does not appear in pairs with the predicator has-element has been difficult to
capture graphically and is for the moment missing from the model.
In the remainder of the Fundamental layer the concept of Transition with
surrounding terminology is introduced. (The formal definitions are reprinted in
table 2 in the Appendix). A Transition is a kind of binary relationship in which the
predicators in the tuples are the primitives before and after and the predicated
things are composite things, so called States. Complex transitions can be built
up through Sequence, Choice and Concurrency to State Transitions Structures. A
coherent state transition structure, i.e., a structure with a unique input (before)
state and a unique output (after) state, is called a Composite Transition.
Furthermore, Rules are used to define the set of permissible states and transitions in a
context. To capture these concepts we are gradually extending the meta-model
with the shaded classes as depicted in figure 2.</p>
          <p>In this part of the framework the concept of Transition Occurrence for
capturing the different occurrences of the transitions is introduced. We have introduced
the corresponding class into the model, but we leave the discussion of it for the
next section. The concepts Type, Population and Instance, which are all part of
the formal definition of the framework, are for the moment left out of the model
but will be discussed in the next section.
2.2</p>
        </sec>
      </sec>
      <sec id="sec-2-2">
        <title>The Layer of Actors, Actions and Actands</title>
        <p>Transitions which are performed by someone are distinguished and called
Actions. Actions are presented through a couple of tuples, the predicated thing of
the first of which shows the performing Actor and of the second one the transition</p>
        <p>1
State S 1
Composite
Transition CT</p>
        <p>Predica1toPr PreTdhi1cinagtedQ
^ has * * ^ has
he/she is performing. The predicators used for describing this are the primitives
performing and performed-by, correspondingly. The things involved in the input
and the output states of an action, and which are not actors for that action, are
called Actands. The input actands for an action (i.e. the actands from the input
state) together with the actors are the Resources for that action. Also using the
primitive is-context, some of the input actands can be predicated, in order to
define the Action context. In a similar way the Goal of an action can be defined
by intentionally stating the desired output state.</p>
        <p>The formal definitions for this layer are reprinted in table 3 in the Appendix.
The meta-model is drawn in figure 3. The transition part of the Fundamental
layer, as closely related to the concepts defined here, is reprinted in the bottom
of the figure. The isa relationships between the different layers are indicated by
dotted arrows. Furthermore, the basic concept from the fundamental layer on
which a concept is built on is indicated by giving the name of the set in the
upper right corner of the rectangle of the class.
3</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>Results from the analysis of Frisco during the construction of the meta-model</title>
      <p>During the process of building the meta-model we identified some minor
problems within the formal definitions of Frisco. A discussion of them as well as
suggestions for how to solve them are provided below.</p>
      <p>The idea of defining State Transition Structure and Composite Transition
concepts is to be able to build up complex transitions. However, the necessary
recursive element for achieving this and assumed in the natural language
description of the framework is missing from the formal definitions. This makes
it unclear how complex transitions are actually built up. In the meta-model in</p>
      <p>1
State S 1
of v</p>
      <sec id="sec-3-1">
        <title>Action NT iinnvvoollvveess&gt;&gt;</title>
        <p>Actand DZ</p>
        <p>Actor QO
Input</p>
        <p>Z
ResourceRS
figure 2, which is based on the formal definitions and not the textual description
of the framework, this defect can be seen through the absence of a recursive
relation. The relationship involves between State Transition Structure and
Transition drawn twice in order to make explicit the fact that a State Transition
Structure is built on two Transitions, does not capture the necessary recursion.</p>
        <p>One way to solve this and to introduce recursion would be to define a State
Transition Structure to be a Transition. This would not though work for Choice,
where a unique post-state is not defined. Besides, it would make the definition
of Composite Transition unnecessary. An alternative and more successful way
would then be to include recursion within the definition of State Transition
Structure. This is done by relaxing the existing assumption of tx and ty on
being just Transitions into being Transitions or State Transition Structures, i.e.
the following definition adjustment to the definition from table 2 is proposed.
Def adj 1 If tx : s1 → s2, ty : s3 → s4 are transitions or state transition structures
then the following state transition structures exists</p>
        <p>Sequence: sequ(tx, ty) if s3 ⊆ s2
Choice: choice(tx, ty) if s1 ∩ s3 = ∅</p>
        <p>Concurrency: concur(tx, ty) if s1 ∩ s3 = ∅
In the meta-model this change will be depicted by changing the range for one
of the involves relationship from the current Transition to be State Transition
Structure. The cardinality constraints of both involves relationship have to be
adjusted, as it is not longer known in advance how many of the involved in the
State Transition Structures elements are Transitions and how many are other
State Transition Structures. This is depicted in figure 4a. More complicated ways
for capturing this as well as a bit more of the semantics are available. However,
even the simple solution we are proposing here exemplifies well enough how a
meta-model can facilitate the analysis of a framework and how the model evolves
to capture its changes.</p>
        <p>Furthermore, going back to the concept of Transition Occurrence (as we’ve
promised in the previous section), we note that interestingly, but not surprisingly,
Transition
occurrence</p>
        <p>Action NT 1&lt; of * occurrence</p>
        <p>Action</p>
        <p>involves ^</p>
        <p>T &lt; of Action
ActionN 1 * occurrence
a) Recursion
b) Time
c) Action Occurrence</p>
        <p>
          d) Entity Type
after its formal definition in [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ] an elaborated discussion on the formalisation of
the time concept was given and how a relative ordering between transition
occurrences could be done. However, even if discussed, the concept of absolute time
was not formalised. Therefore, we propose the following formal definitions for
Time Point, Time Interval and Time Unit concepts (for a detailed analysis of the
time concept, please refer to [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ]).
        </p>
        <p>Def 2 Let T P = {tp|tp ∈ EZ} denote the set of time points for which the following
holds:</p>
        <p>If tp1 ∈ T P and tp2 ∈ T P and tp1 = tp2 then tp1 &lt; tp2 or tp2 &lt; tp1</p>
        <p>If tp1 &lt; tp2 and tp2 &lt; tp3 then tp1 &lt; tp3, where tp1, tp2, tp3 ∈ T P
Def 3 Let T I = { tps, tpe |tps, tpe ∈ T P ∧ tps &lt; tpe} denote the set of time intervals,
where tps is called the start time point of an interval and tpe is called the end of the
interval.</p>
        <p>Def 4 Let T U = T P ∪ T I denote the set of time units.</p>
        <p>After have defined a set of Time Units, it is now natural to extend the definition
of Transition Occurrence with the notion of time. The following definition
adjustment allows us to express not only that a transition has occurred, but also
the time unit at which it occurred. The changes in the meta-model are shown
in figure 4b. The distinction between a time point at which a transition occurs
versus a time interval spanning over the occurrence of a composite transition, in
the definition below, justifies the necessity of introducing both time points and
time intervals.</p>
        <p>Def adj 5 A transition t : s1 → s2 is enabled to occur in state s if s1 ⊆ s.
If a transition t : s1 → s2 occurs in state s, then s is changed to the new state s =
(s \ s1) ∪ s2.</p>
        <p>The occurrence of a transition t : s1 ⇒ s2 in state s leading to state s’ at time unit tu
is denoted as occ(t, tu) : s → s . When the occurrence is of a composite transition the
time unit tu is a time interval, otherwise it is a time point.</p>
        <p>We are now turning our attention into the Action concept of the Actor, Action
and Actands layer and how it builds on the Transaction concept. At the moment,
the Transition Occurrence concept from the Fundamental layer is used to capture
both the fact that a transition occurs, as well as the fact that an action is
performed. Graphically, it can be pointed out that the symmetry in figure 3
existing between the concepts Transition-Action and Composite Transition
Composite Action (from the Fundamental and Actor, Action, Actand layers
correspondingly) is lacking for the concept Transition Occurrence. In order to
make explicit the occurrences of the actions we suggest the introduction of an
Action Occurrence concept (see figure 4c). Such a concept will naturally be based
on the Transition Occurrence concept, which is indicated by the intra-layers isa
relationship in the figure. In addition to bring explicitness and clarity to the
model, this change allows for an independent consideration of the Actor, Action
and Actands layer from the Fundamental layer. It also clearly establishes the
Fundamental layer as a supporting layer which we also believe was its initial
purpose.</p>
        <p>Recall furthermore, that the difference between an Action and a Transition
is that an action is performed by an actor. According to the formal definitions
and to the meta-model in figure 3 when defining an action its actor is explicitly
specified. However, having now introduced the concept of Action Occurrence, it
would be far more natural to specify the actual performer of an action first when
it has occurred. Furthermore, instead of specifying an Actor for the performance
of an action it is rather natural to specify the potential performers for the action.
We also find the limitation that for the moment an action can only be specified
to be performed by an individual actor as quite unnecessary, especially as for
the most actions (e.g., composite actions) the opposite is valid. In order to make
the definition of an action more general, by allowing a whole group of actors
to be specified as potential performers of it, we introduce the concept of Entity
Type. This concept is actually used in some examples of the framework already.
However it is not formally separated, but occurs as a part of the Type concept
and even then it is not a part of its formal definition, but appears only in its
exemplification. Whether this name is the most suitable one can be discussed.
However, as we try to stay as close to the framework as possible we decide to
keep it for now.</p>
        <p>Def 6 Let ET = 2E denote the set of entity types.</p>
        <p>Now, the definition of action is changed to specify an Entity Type as the
performer of an action, while the fact that a specific actor has performed an action
is captured in the definition for action occurrence adjusted below. The resulting
change in the meta-model is shown in figure 4d.</p>
        <p>Def adj 7 Let N denote the set of all actions. N = {t ∈ T |∃q ∈ ET , ∃r ∈ R[r =
{ q, perf orming , t, perf ormed by } ∧ q ∈ P restateof (t)]}
As argued above, we now give a separate definition for the concept of action
occurrence.</p>
        <p>Def 8 An action n : s1 → s2 is enabled to be performed by an actor a in state s if
s1 ⊆ s and a ∈ Actorof (n). If an action n : s1 → s2 is performed in state s, then s is
The Actor, Action
and Actand layer
Goal G</p>
        <p>of &gt;
CompositeCT</p>
        <p>Action CN
Composite
TransitionCT</p>
        <p>Actand ZD</p>
      </sec>
      <sec id="sec-3-2">
        <title>ETnyptiteyEET Actor QO</title>
        <p>invionlvvoelsve^s ^ performed by ^</p>
        <p>Action NT 1 &lt; of * ocAcucrtrioennce
** * Tran0s.^.i2tiinovnolTves1 &lt; of * oTcrcaunrsreitniocne
0..S2tat&lt;eTin*rvaolnvse*sition</p>
        <p>Structure ST</p>
        <p>Input
ResourcRZeS</p>
        <p>Time</p>
        <p>Unit
changed to the new state s = (s \ s1) ∪ s2.</p>
        <p>The performance of an action n : s1 ⇒ s2 by actor a in state s leading to state s’ at
time unit tu is denoted as occ(n, a, tu) : s → s .</p>
        <p>This definition invokes the function Actorof, which takes as input an action and
returns its performer, who is generally defined as a predicated thing. In order
to unify it with the adjusted definition of an action, where the performer is an
entity type, the following modification is suggested:
Def adj 9 Let Actorof : N → 2E be a function determining the entity types specified
as performers of an action, where Actorof (n) = {q ∈ 2E |q ∈ P restateof (n) ∧ ∃r ∈
R[r = { q, perf orming , n, perf ormed by }]}
The meta-model in figure 5 is drawn to summarize the results of the analysis
and present the suggested improvements. The introduced concepts are indicated
by shading the corresponding classes.
4</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>Conclusions and Further Work</title>
      <p>In this work we focused on the construction of a meta-model for the Framework of
Information Systems Concepts (Frisco). The initial results, i.e., the development
of a meta-model for the first two layers of the framework was presented here
and as a modelling language the notation of UML class diagrams was used.
We believe this diagrammatical way of presenting a well formalised system of
concepts will serve as a communication aid facilitating the dissemination of it.</p>
      <p>Furthermore, we have demonstrated how the analysis provided through the
meta-model development can be used in the further development of Frisco. This
was done by in detail presenting the ambiguities identified and the amendments
suggested to resolve them.</p>
      <p>
        During the work Frisco was analysed in isolation. The next and even more
interesting step will be to use the proposed meta-model for analysing Frisco across
other alternative attempts existing in the area. In particular, the representatives
of two rather contrasting approaches are of interest:
– The closely related, i.e., top-down developed and well formalised, frameworks
or ontologies such as BWW, EO, TOVE are interesting to compare to Frisco
so that overlap and discrepancies are outlined. Such an analysis would not
only position the frameworks relative each other but it could also be
beneficial for the potential development of each one of them (according to the
technique of meta-model comparison as demonstrated in [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]).
– The pragmatic, bottom-up developed attempts like UEML [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] and the
framework proposed by So¨derstro¨m et al. [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ]. Such an analysis could
initially be provided for surveying the similarities and differences between the
approaches (and be beneficial for works like the one presented in [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ]).
Furthermore, mapping these non-formalised frameworks to the well-formalised
Frisco (in line with the work presented in [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ]) would also give clear semantics
to them.
      </p>
      <p>Common for all the attempts mentioned above is that they were all developed
addressing the interoperability issues and that they are all supposed to be used
for facilitating communication (between people, organisations and tools). Then
an interesting research direction is to investigate the “interoperability” of the
frameworks themselves.</p>
      <sec id="sec-4-1">
        <title>Appendix</title>
        <p>—————
3. Let Predthingin:R → 2Q be a function from relationships to sets of predicted things,
where P redthingin(r) = {q ∈ Q|∃p ∈ P[ q, p ∈ r]}.</p>
        <p>N N = {t ∈ T |∃q ∈ Q, ∃r ∈</p>
        <p>R[r = { q, perf orming ,
t, perf ormed − by } ∧ q ∈</p>
        <p>P restateof (t) 4]}
Composite CN CN = ST ∩ N
action</p>
        <p>Description
A transition involving a non-empty
set of actors
A composite transition with the
same condition as applying for the
notion of action
A thing able to cause transition
—————
4. Let Prestateof:T → S be a function from transitions to states,
where P restateof (t : sb ⇒ sa) = sb denotes the (pre-)state before the transition t.
Let Poststateof:T → S be a function from transitions to states,
where P oststateof (t : sb ⇒ sa) = sa denotes the (post-)state after the transition t.
5. Let Actorof:N → 2Q be a function determining the actors performing an action,
where Actorof (n) = {q ∈ Q|
q ∈ P restateof (n) ∧ ∃r ∈ R[r = { q, perf orming , n, perf ormed − by }]}.
6. Let Outputof:N → 2Z be a function determining the output actands of an action,
where Outputof (n) = {z ∈ P oststateof (n)|¬(z ∈ Actorof (n))}.</p>
        <p>Let Inputof:N → 2Z be a function determining the input actands of an action,
where Inputof (n) = {z ∈ P restateof (n)|¬(z ∈ Actorof (n))}.</p>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Falkenberg</surname>
            ,
            <given-names>E.D.</given-names>
          </string-name>
          , et al.
          <source>: FRISCO - A Framework of Information System Concepts</source>
          .
          <source>Technical Report ISBN 3-901882-01-4</source>
          , IFIP (
          <year>1998</year>
          ) http://www.wi.leidenuniv. nl/∼verrynst/fri-full-7.pdf.
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Wand</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Weber</surname>
            ,
            <given-names>R.:</given-names>
          </string-name>
          <article-title>An ontological model on an information system</article-title>
          .
          <source>IEEE Trans. Software Eng</source>
          .
          <volume>16</volume>
          (
          <year>1990</year>
          )
          <fpage>1281</fpage>
          -
          <lpage>1291</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Uschold</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gruninger</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Ontologies: Principles, methods and applications</article-title>
          .
          <source>Knowledge Engineering Review</source>
          <volume>11</volume>
          (
          <year>1996</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4. OpenCyc.
          <source>org: Opencyc</source>
          <volume>0</volume>
          .7b.
          <source>Technical report, Cycorp</source>
          (
          <year>2004</year>
          ) http://www. opencyc.org/doc/.
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5. Enterprise Integration Laboratory, U.o.T.:
          <string-name>
            <surname>TOVE (TOronto Virtual Enterprise) Ontology Project</surname>
          </string-name>
          .
          <source>Accessed November</source>
          <year>2004</year>
          from http://www.eil.utoronto.ca/ enterprise-modelling/tove/index.html (
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Uschold</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>King</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Moralee</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zorgios</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          :
          <article-title>The Enterprise Ontology</article-title>
          .
          <source>Technical report, AIAI</source>
          , The University of Edinburgh (
          <year>1997</year>
          ) http://www.aiai.ed.ac. uk/project/enterprise/enterprise/ontology.html.
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Rosemann</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Green</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>Developing a meta model for the Bunge-Wand-Weber ontological constructs</article-title>
          .
          <source>Information Systems</source>
          <volume>27</volume>
          (
          <year>2002</year>
          )
          <fpage>75</fpage>
          -
          <lpage>91</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8. OMG:
          <article-title>UML 2.0 Superstructure Specification</article-title>
          .
          <source>OMG Draft Adopted Specification, ptc/03-08-02</source>
          (
          <year>2003</year>
          ) http://www.omg.org/cgi-bin/doc?ptc/2003-08-02.
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Allen</surname>
          </string-name>
          , J.:
          <article-title>Towards a general theory of action and time</article-title>
          .
          <source>Artificial Intelligence</source>
          <volume>23</volume>
          (
          <year>1984</year>
          )
          <fpage>123</fpage>
          -
          <lpage>154</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Panetto</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          , et al.:
          <article-title>A Unified Enterprise Modelling Language for enhanced interoperability of Enterprise Models</article-title>
          .
          <source>In: Proc. of the 11th IFAC INCOM2004 Symposium</source>
          , Bahia, Brazil (
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11. S¨oderstro¨m, E., et al:
          <article-title>Towards a framework for comparing process modelling languages</article-title>
          .
          <source>In: Proc. of the 14th Int. Conf. on Advanced Inf. Systems Engineering (CAiSE)</source>
          . Volume 2348 of LNCS., Springer (
          <year>2002</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Rukanova</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Slooten</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Stegwee</surname>
          </string-name>
          , R.: Business Process Requirements,
          <article-title>Modeling Technique, and Standard: How to identify interoperability gaps on a process level</article-title>
          .
          <source>In: Pre-proc. of the 1th Int. Conf. on Interoperability of Enterprise Sofware and Applications (INTEROP-ESA2005)</source>
          . (
          <year>2005</year>
          )
          <fpage>13</fpage>
          -
          <lpage>25</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Wohed</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Andersson</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          :
          <article-title>(Reconciliation of two Business Modelling Frameworks) to be presented at CAiSE 2005 Forum</article-title>
          , to be held in Porto, Portugal, June,
          <year>2005</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>