<!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>Modelling Ontology Use for Information Systems</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Roland Kaschek</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Department of Information Systems, Massey University</institution>
          ,
          <country country="NZ">New Zealand</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>This paper characterizes ontologies as models. It looks then at ways of using ontologies for information systems. These ways are discussed in terms of ontology role, role justification, and relevance. Space limitations prevent from discussing IS ontology papers and elaborating on conclusions.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>Among the ontologies used in information systems (IS) are the ones of Bunge
(see, e.g. [Web03]) and Chisholm (see, e.g. [MK01]). Regarding information
systems the differences between these ontologies are significant. The most
widespread use of an ontology in information systems appears to be the one that
comes with the use of semantic models. Examples for semantic models are the
Entity-Relationship model (ERM), see [Che76], State Charts, Dataflow
Diagrams and Petri Nets. They have a built-in ontology that aids modelers in:
identifying, classifying and relating to each other phenomena in a universe of
discourse and by doing so obtain a specification of a consistent
conceptualization.</p>
      <p>For example, in ER modelling one is guided to (1) define the scope of the
universe of discourse D; (2) recognize phenomena within D that appear to be
relevant for a task at hand; (3) classify these phenomena as entity, attribute,
or relationship; and (4) relate classified phenomena to each other following the
ERM’s syntactic conventions. Defining the scope of U is more formalized in
Function Point Analysis, see [GH96], than in ER modelling. The
conceptualizations obtained with a semantic model intentionally often are shared by a number
of involved individuals.</p>
    </sec>
    <sec id="sec-2">
      <title>Models</title>
      <p>This paper draws from Stachowiak’s general model theory (GMT) (see [Sta92],
[Sta83], [Sta73]). A similar theory was recently used in [M*03]. A recent
discussion of the GMT for software engineering is in [Lud03]. Let a cultural unit
be something to which one, in a given culture, can intelligibly refer to. This
concept according to Eco, see [Eco94, p. 75], was introduced by Schneider. Let
A be a group of agents and M; O specifications of cultural units UM ; UO. Let
A refer to O by means of M . Codify this with the predicate ¹(O; M; A) and
call it model relationship. Call the roles of O and M in it original and model
respectively. Stachowiak has characterized models by: (1) a mapping property, i.e.,
each model is a model of something, i.e., its original; (2) a truncation property,
i.e., the model in general lacks some of the specification parts of the original; and
(3) a pragmatic property, i.e., the model is subdue to a purpose and its use for
this purpose is only justified with respect to particular users, their objectives,
applied techniques and tools, and period of time etc. This paper deviates from
his views on models: originals do not have to predate the model, the cognitive
dimension of models is explicitly recognized, as is a plenty property. The latter
states that specification M can be richer than O. Consider a map M as a model
of an intuitive specification W for a world CW . M can easily be transported
and folded, as the map is made of paper. This significantly impacts the map’s
usability.</p>
      <p>The Reference mode, i.e., the kind of reference A makes with the model to the
original is a dimension of the model relationship ¹(O; M; A). It helps addressing
questions like: Do all agent instances share the view of model and original or do
they have different views? In which way does the agent relate the model to the
original? is it a descriptive, prescriptive, prognostic, idealizing or constitutive
way? In the descriptive, prescriptive, prognostic and idealizing reference mode
the agent A uses M for specifying what O is like, should be like, expects it to
be like under particular stated conditions, and what O will be like under ideal
conditions respectively. In the constitutive reference mode A replaces O by M
and in this sense constitutes UO by means of M .</p>
      <p>For an example of a model that occurs frequently in information systems
consider a table in a relational database and its primary key. For each primary
key there is a table (mapping property). Usually there is a number of table
columns that do not belong to the key (truncation property). The primary key
only is valid for distinguishing between any two tuples of the table if the table
is maintained properly and only for those who are entitled for using it etc.
(pragmatic property). In contrast to the table the primary key can be the target
of a foreign key reference (plenty property).</p>
    </sec>
    <sec id="sec-3">
      <title>Ontologies and their use</title>
      <p>Following the frequently used definition of Gruber, see [Gru93, p. 199], an ”: : :
ontology is an explicit specification of a conceptualization”. And a ”: : :
conceptualization is an abstract simplified view of the world that we wish to represent
for some purpose.” In [UG96, p. 96] and [SMJ02] ontologies more specifically are
considered as shared conceptualization.</p>
      <p>An ontology model A shared conceptualization is a cultural unit. Let an
ontology X be used by an agent A to specify a cultural unit UW . Let a
specification W exist that allows for justification of the use of X to specify UW . Let
furthermore UX be the cultural unit associated with X prior to agreeing that
X actually should be used as a specification of UW . Note that UX may be void.
Conceptualizing the consideration of an ontology X for UW by an agent A thus
leads to the model relation ¹(W; X; A) in which a constitutive mode of reference
occurs, i.e., a replacement of W by X.</p>
      <p>Modelling ontology use Let the predicate u(A; M; D; L; T ) denote an
ontology use, i.e., let it mean that a group A of agents uses ontology M with respect
to a domain D, for a task T in which a language L is involved. Dimensions of an
ontology use can be identified as (1) role, (i.e., the way the ontology is used); (2)
justification (addressing whether A is entitled for using M in role R because M
is an ontology); and (3) relevance (addressing whether it is relevant for using M
in role R that M is an ontology). To each of these dimensions will be associated
a scale. For both of the latter dimensions the scale values ”+”, and ”-” will be
used in the obvious meaning. The scale for ’role’ comprises providers of:
correctness criterium (ccp), communication medium (cmp), knowledge (kp), meaning
(mp), quality concept (qcp), and world view (wvp). Let T ve a task. The
ontology m in the role ccp, cmp, kp, mp, qcp, and wvp is used for distinguishing
the correct from the wrong sentences of L; for providing agents in A the media
L for taking about D; for providing knowledge regarding D to members of A;
for associating items in D as a meaning to the sentences of L; for establishing
the concept of quality regarding items in D; and specifying a conceptualization
of D respectively. For an ontology use u the triplet ®u = (½; ¶; !), with ½; ¶; !
scale values of role, justification and relevance respectively is called use
assessment. An ontology use u should be considered as problematic if its assessment
®u scores ”-” for ’justification’ or ’relevance’.</p>
      <p>Some pragmatic concerns regarding ontology roles are: (1) truth of
propositions is not always sufficient for a task T . Assume a postman knows a letter’s
recipient name and street of residence but not the house number. If the street
has many houses he is likely not to deliver the letter. What he knows is
correct but not precise. (2) proving a proposition can let it appear as unrefutable.
Quantum Theory is used as an ontology enabling such proofs. At 2 April 2004
the Web edition of the ”Neue Zu¨rcher Zeitung” (Science Column) reported in
the article (in German:) ”The Quantum Lab in the Matchbox” on an encryption
device cipherings of which provably cannot be deciphered without having access
to the respective key. (3) wrong models are used in favor of correct ones if their
differences are insignificant with respect to a task T . In primary and secondary
education for example the wrong ball-model of molecules (Chemistry) and orbs
(Physics) are used rather than (more) correct ones. Note, finally, that it is a
well established approach in software engineering to relate quality to use and
usability, see, e.g. [ISO91].</p>
      <p>Let the predicate ¹(O; M; A) be true and A use M in the constitutive
reference mode. Consider an ontology use u = u(A; M; D; L; T ). Using M as wvp
is justified if the overlap of D and CO is counted as significant. What counts as
significant depends on T . It is relevant for using M as wvp that M actually is
an ontology because that makes M capable of specifying CO. Using M as ccp
regarding L turns discriminating true from false propositions in L into drawing
implications from M . It is justified to use M in this role. However, it is not
relevant for this use that M is an ontology. For a theory to be used in this role
it would be relevant that the important propositions can be implied efficiently.
What counts as ’important’ or ’efficient’ depends on T . Using M as kp is
justified if CO = D. It is relevant for this use that M is an ontology. Using M as
cmp can be justified if D = CO. Using M in this role would not be justified if
enough members of A are not fluent in L. What counts as enough depends on
T . It is not relevant for this use of M that M is an ontology. It is justified to
use M as mp, if L enables A to talk about CO. It is not relevant for using M in
this role that M is an ontology. Note that justification of using M as mp may
involve a fluency issue like the one discussed with respect to the role cmp. The
characteristics of a theory suitable for being used as mp depend on T . Using
M as a qcp can be justified if for T an understanding of quality as ontology
compliance is adequate. An ontology does not qualify per-se for the qcp. It is
less important that a quality concept means ontology compliance than it is that
this concept helps doing T .</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          <string-name>
            <surname>[Che76] Peter P. Chen. The Entity-Relationship</surname>
            <given-names>Model</given-names>
          </string-name>
          :
          <article-title>Toward a Unified View of Data</article-title>
          .
          <source>ACM Transactions on Database Systems</source>
          ,
          <volume>1</volume>
          (
          <issue>1</issue>
          ):
          <fpage>9</fpage>
          -
          <lpage>37</lpage>
          ,
          <year>1976</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [Eco94]
          <string-name>
            <given-names>Umberto</given-names>
            <surname>Eco</surname>
          </string-name>
          .
          <article-title>Einuf¨hrung in die Semiotik</article-title>
          .
          <source>Wilhelm Fink Verlag GmbH &amp; Co. KG</source>
          , Mu¨nchen,
          <year>1994</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [GH96]
          <string-name>
            <given-names>David</given-names>
            <surname>Garmus</surname>
          </string-name>
          and
          <string-name>
            <given-names>David</given-names>
            <surname>Herron</surname>
          </string-name>
          .
          <article-title>Managing the software process: a practical guide to functional measurements</article-title>
          . Yourdon Press Computing Series. Prentice
          <string-name>
            <surname>Hall</surname>
            <given-names>PTR</given-names>
          </string-name>
          , Upper Saddle River, New Jersey,
          <year>1996</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [Gru93]
          <string-name>
            <given-names>Thomas</given-names>
            <surname>Gruber</surname>
          </string-name>
          .
          <article-title>A translation approach to portable ontologies</article-title>
          .
          <source>Knowledge Acquisition</source>
          ,
          <volume>5</volume>
          (
          <issue>2</issue>
          ):
          <fpage>199</fpage>
          -
          <lpage>220</lpage>
          ,
          <year>1993</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [ISO91]
          <article-title>Information technology-Software product evaluation-Quality characteristics and guidelines for their use</article-title>
          ,
          <year>1991</year>
          .
          <source>International Standard</source>
          <volume>9126</volume>
          :
          <string-name>
            <surname>1991(E).</surname>
          </string-name>
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [Lud03]
          <string-name>
            <given-names>Jochen</given-names>
            <surname>Ludewig</surname>
          </string-name>
          .
          <article-title>Models in software engineering - an introduction</article-title>
          .
          <source>Software and Systems Modeling</source>
          ,
          <volume>2</volume>
          (
          <issue>1</issue>
          ):
          <fpage>5</fpage>
          -
          <lpage>14</lpage>
          ,
          <year>March 2003</year>
          .
          <article-title>Reworked version of Ludewig's presentation at</article-title>
          ”
          <source>Modellierung</source>
          <year>2002</year>
          ”.
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [MK01]
          <string-name>
            <given-names>Simon</given-names>
            <surname>Milton</surname>
          </string-name>
          and Ed. Kazmierczak.
          <article-title>An ontological study of data modelling languages using Chisholm's ontology</article-title>
          .
          <source>In European-Japanese conference on information modelling and knowledge bases</source>
          , Amsterdam et al.,
          <year>2001</year>
          . IOS Press.
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [SMJ02]
          <string-name>
            <given-names>Peter</given-names>
            <surname>Spyns</surname>
          </string-name>
          , Robert Meersman, and
          <string-name>
            <given-names>Mustafa</given-names>
            <surname>Jarrar</surname>
          </string-name>
          .
          <article-title>Data modelling versus Ontology engineering</article-title>
          .
          <source>ACM SIGMOD Record</source>
          ,
          <volume>31</volume>
          (
          <issue>4</issue>
          ):
          <fpage>12</fpage>
          -
          <lpage>17</lpage>
          ,
          <year>December 2002</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [Sta73]
          <string-name>
            <given-names>Herbert</given-names>
            <surname>Stachowiak</surname>
          </string-name>
          .
          <source>Allgemeine Modelltheorie</source>
          . Springer Verlag, Wien, New York,
          <year>1973</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [Sta83]
          <string-name>
            <given-names>Herbert</given-names>
            <surname>Stachowiak</surname>
          </string-name>
          .
          <article-title>Erkenntnisstufen zum Systematischen Neopragmatismus und zur Allgemeinen Modelltheorie</article-title>
          . In Herbert Stachowiak, editor,
          <source>Modelle-Konstruktionen der Wirklichkeit</source>
          , pages
          <fpage>87</fpage>
          -
          <lpage>146</lpage>
          . Wilhelm Fink Verlag, Mu¨nchen,
          <year>1983</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [Sta92]
          <string-name>
            <given-names>Herbert</given-names>
            <surname>Stachowiak</surname>
          </string-name>
          . Modell. In Helmut Seiffert and Gerard Radnitzky, editors,
          <source>Handlexikon Zur Wissenschaftstheorie</source>
          , pages
          <fpage>219</fpage>
          -
          <lpage>222</lpage>
          . Deutscher Taschebuch Verlag GmbH &amp; Co. KG, Mu¨nchen,
          <year>1992</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [UG96]
          <string-name>
            <given-names>Mike</given-names>
            <surname>Uschold</surname>
          </string-name>
          and
          <string-name>
            <given-names>Michael</given-names>
            <surname>Gruninger</surname>
          </string-name>
          .
          <article-title>Ontologies: principles, methods and applications</article-title>
          .
          <source>The Knowledge Engineering Review</source>
          ,
          <volume>11</volume>
          (
          <issue>2</issue>
          ):
          <fpage>93</fpage>
          -
          <lpage>136</lpage>
          ,
          <year>1996</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [Web03]
          <string-name>
            <given-names>Ron</given-names>
            <surname>Weber</surname>
          </string-name>
          .
          <article-title>Conceptual modelling and ontology: possibilities and pitfalls</article-title>
          .
          <source>Journal of Database Management</source>
          ,
          <volume>14</volume>
          (
          <issue>3</issue>
          ):
          <fpage>1</fpage>
          -
          <lpage>20</lpage>
          , July - September
          <year>2003</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>