<!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>OntoMetaWorkflow: An Ontology for Representing Data and Users in Workflows - Extended Abstract1</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Alvaro E. Prieto</string-name>
          <email>aeprieto@unex.es</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Adolfo Lozano-Tello</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>José Luis Redondo-García</string-name>
          <email>jluisred@unex.es</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Quercus Software Engineering Group, University of Extremadura</institution>
          ,
          <addr-line>av. Universidad s/n 10071</addr-line>
          ,
          <country country="ES">Spain</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Administrative processes are a type of business process commonly used in public institutions and large companies. These processes are frequently reused because there are often similar processes within the organizations. The use of ontologies for modeling the workflows of administrative processes can provide significant improvements in this reuse process. In this paper, we describe OntoMetaWorkflow, a generic ontology to represent canonical workflow terms in the domain of administrative processes.</p>
      </abstract>
      <kwd-group>
        <kwd>business process</kwd>
        <kwd>administrative process</kwd>
        <kwd>workflows</kwd>
        <kwd>ontologies</kwd>
        <kwd>WEAPON</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>Administrative processes are generally used in administrative or legal ambits. They
are characterized by being initiated by a user and which must be attended to or
evaluated by other different users following a perfectly defined protocol for data,
times and agents involved. These processes are often defined generically in the level
of management of the organizations but must be reused in the lower levels in order to
be applied in them. Examples could be the management of public contest bids, loan
application procedures or a simple holiday application.</p>
      <p>They can be managed by simple Workflow Management Systems (hereinafter
referred to as WfMS) with features that facilitate to share and reuse this type of
process. The use of ontologies as a basis for this type of WfMS could be very useful
due to their characteristics of complete and precise representation of terms.</p>
      <p>
        An appropriate case of application to reuse processes is the WfMS model based on
ontologies was proposed in [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. This model provided a generic ontology described in
[
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] as the basis of workflow representation. We have restructured the ontology and
the WfMS model to improve the reuse process.
      </p>
      <p>
        This paper is structured as follows: section 2 enumerates works that use ontologies
in WfMS, section 3 presents a brief description of the redefinition of the WfMS [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ],
now called WEAPON (Workflow Engine for Administrative Processes based on
ontologies), and, section 4 describes the new ontology, called OntoMetaWorkflow.
2
      </p>
    </sec>
    <sec id="sec-2">
      <title>Use of Ontologies in WfMS</title>
      <p>
        The application of ontologies to WfMS have been used previously in several
approaches as [
        <xref ref-type="bibr" rid="ref2 ref3 ref4 ref5">2,3,4,5</xref>
        ] and a recent survey is available in [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ].
      </p>
      <p>
        Unlike the previous approaches, this paper presents an ontology for representing
administrative processes together with their activities, domain data and users
involved. Although several models and languages of workflow representation exist
[
        <xref ref-type="bibr" rid="ref7 ref8">7,8</xref>
        ], the application of ontologies can provide the following advantages:
─ The users, following methodologies for building ontologies, can obtain
complete, precise and shared definitions of administrative process workflows.
─ The data and the users of a process can be changed without modifying the
definition of the data managed by activities or the definition of the workflow.
─ Workflows represented in ontologies, are more easily reusable although the
reuse process may involve some effort in the search, selection and, in some
cases, adaptation to the new system.
3
      </p>
    </sec>
    <sec id="sec-3">
      <title>WEAPON: Workflow Engine for Administrative Processes based on Ontologies</title>
      <p>
        WEAPON is a WfMS that proposes how a workflow designer must define, on one
hand, the taxonomy of relevant data of the domain and the taxonomy of users which
can participate in the workflow and, on the other hand, the activities that the process
contains together with the identification of which type of user defined can perform
them and the data managed by every activity. WEAPON uses ideas of ontology field
together with ideas of traditional WfMS and the Case Handling approach [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ].
      </p>
      <p>The architecture of WEAPON presents a series of interrelated components (a
graphical representation is available in 2). These components are:
1. OntoMetaWorkflow3, contains the terms that form the workflows of administrative
processes and their relationships. This ontology, represented in OWL Language, is
built adapting the definitions of workflow elements provided by the WfMC [10] to
the specific characteristics of administrative processes. It has been developed
following the METHONTOLOGY methodology [11].
2. OntoDD, an ontology of the domain data and workflow participants built following
the specifications of OntoMetaWorkflow. It imports the concepts defined in
2 http://quercusseg.unex.es/weapon/
3 http://quercusseg.unex.es/weapon/?download=OntoMetaWorkflow.owl</p>
      <p>OntoMetaWorkflow and must contain, firstly, the taxonomy of data which will be
used in the corresponding domain and, secondly, the taxonomy of the possible
workflow participants. As example, the OntoDD ontology for a loan application
domain is available in 4.
3. OntoWF represents the workflow of the administrative process that will be
managed by the WfMS. It contains the concrete workflow of the administrative
process, including its properties, the activities that it contains the order of
execution of said activities, the relevant data of OntoDD that will be shown or
modified in an activity and the participants which can perform every activity. As
example, the OntoWF ontology for a loan application process is available in 5.
4. WEAPON Designer, is the tool that allows users to combine WF-Net [12]
representation with OntoMetaWorkflow and the OntoDD of a domain in order to
design the OntoWF Ontology for a specific administrative process.
5. WEAPON Manager, is the web application that reads OntoDD and OntoWF
ontologies and generates the web forms and the database that manage the workflow
of the administrative process.
4</p>
    </sec>
    <sec id="sec-4">
      <title>OntoMetaWorkflow</title>
      <p>The different definition elements of OntoMetaWorkflow are classified into two types
(a graphical representation of OntoMetaWorkflow is available in 6):
1. Definition elements of OntoDD: are used to define the classes and properties that
represent the common data and the potential users of all similar processes within a
domain. These elements are the Domain Data, Workflow Participant and Root
classes. Domain Data stores common data of all instances of an administrative
process and has the External Document and Location attributes. The Workflow
Participant class stores the users involved in the process and has Id, Password,
Name, Surname and Email attributes. The Root subclass is a special class that can
administer the WEAPON Manager WfMS.
2. Definition elements of OntoWF: are used to define the classes and properties that
represent a particular process, that is, the sequential flow of activities and their
relationships with the elements of the domain defined in OntoDD. These elements
are the Administrative Process and Activity classes. Administrative Process class is
used for representing the process managed by the WfMS and has defined the
Generated By relationship. The Activity class represents a logical unit of work and
has defined the Is Performed By and Before relationships and the Before Control
Flow Pattern, Select Class Of Domain Data, Show Class of Domain Data,Select
Instance Of Domain Data, Show Instance of Domain Data, Fill In Instance
Attributes of Process, Show Instances Attribute, Days Time Frame, Day Notice and
Activity Description attributes.
4 http://quercusseg.unex.es/weapon/?download=OntoDD_LoanApplication.owl
5 http://quercusseg.unex.es/weapon/?download=OntoWF_LoanApplication.owl
6 http://quercusseg.unex.es/weapon/?OntoMetaWorfklow</p>
    </sec>
    <sec id="sec-5">
      <title>Conclusions</title>
      <p>We have presented OntoMetaWorkflow ontology and WEAPON.
OntoMetaWorkflow is an ontology which specifies the elements and rules that define
workflows according to the standards and recommendations of the WfMC.
OntoMetaWorkflow and the methods of WEAPON have been tested in several
domains, mainly in administrative processes of University of Extremadura. They
work properly with administrative processes that are fully oriented to humans and,
specially, in those processes that involve submitting some type of application to be
considered at different stages, where different participants need to handle current
information of a dossier in order to provide new data in the corresponding activity.
Acknowledgments. This work has been developed under support of Ministerio de
Ciencia e Innovacion Project (TIN2008-02985), FEDER, Junta de Extremadura and
Plan de Iniciacion a la Investigacion, Desarrollo Tecnologico e Innovacion 2010 de la
Universidad de Extremadura (ACCVII-04).</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Prieto</surname>
            ,
            <given-names>A.E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lozano-Tello</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Use of Ontologies as Representation Support of Workflows Oriented to Administrative Management</article-title>
          .
          <source>J. Netw. Syst. Manag</source>
          .
          <volume>17</volume>
          ,
          <issue>3</issue>
          ,
          <fpage>309</fpage>
          --
          <lpage>325</lpage>
          (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Vieira</surname>
            ,
            <given-names>T.A.S.C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Casanova</surname>
            ,
            <given-names>M.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ferrão</surname>
            ,
            <given-names>L.G.</given-names>
          </string-name>
          :
          <article-title>On the design of ontology-driven workflow flexibilization mechanisms</article-title>
          .
          <source>J. Braz. Comp Soc</source>
          .
          <volume>11</volume>
          ,
          <issue>2</issue>
          ,
          <fpage>33</fpage>
          --
          <lpage>43</lpage>
          (
          <year>2006</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Gasevic</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Devedzic</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          :
          <article-title>Petri net ontology</article-title>
          .
          <source>Knowl-Based Syst. 19</source>
          ,
          <issue>4</issue>
          ,
          <fpage>220</fpage>
          --
          <lpage>234</lpage>
          (
          <year>2006</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Haller</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Oren</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kotinurmi</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          : m3po:
          <article-title>An Ontology to Relate Choreographies to Workflow Models</article-title>
          .
          <source>In: 3th IEEE International Conference on Services Computing</source>
          , pp.
          <fpage>19</fpage>
          --
          <lpage>27</lpage>
          . IEEE Computer Society, Los Alamitos, CA (
          <year>2006</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Abramowicz</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Filipowska</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kaczmarek</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kaczmarek</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          :
          <article-title>Semantically enhanced Business Process Modelling Notation</article-title>
          .
          <source>In: 2nd Workshop on Semantic Business Process and Product Lifecycle Management</source>
          , pp.
          <fpage>88</fpage>
          --
          <lpage>91</lpage>
          . CEUR-WS, Innsbruck, Austria (
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Hoang</surname>
            ,
            <given-names>H.H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tran</surname>
            ,
            <given-names>P.C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Le</surname>
            ,
            <given-names>T.M.:</given-names>
          </string-name>
          <article-title>State of the Art of Semantic Business Process Management: An Investigation on Approaches for Business-to-Business Integration</article-title>
          . In: Nguyen,
          <string-name>
            <given-names>N.T.</given-names>
            ,
            <surname>Le</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.M.</given-names>
            ,
            <surname>Świątek</surname>
          </string-name>
          ,
          <string-name>
            <surname>J</surname>
          </string-name>
          . (eds.)
          <source>Intelligent Information and Database Systems. LNCS</source>
          , vol.
          <volume>5991</volume>
          , pp.
          <fpage>154</fpage>
          --
          <lpage>165</lpage>
          . Springer Berlin Heidelberg (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Aalst</surname>
            ,
            <given-names>W.M.P.V.D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hofstede</surname>
            ,
            <given-names>A.H.M.T.</given-names>
          </string-name>
          :
          <article-title>YAWL: yet another workflow language</article-title>
          .
          <source>Inform. Syst</source>
          .
          <volume>30</volume>
          ,
          <issue>4</issue>
          ,
          <fpage>245</fpage>
          --
          <lpage>275</lpage>
          (
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8. OMG:
          <article-title>Business Process Model and Notation (BPMN) 1</article-title>
          .2 (
          <year>2009</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Aalst</surname>
            ,
            <given-names>W.M.P.V.D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Weske</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Case handling: a new paradigm for business process support</article-title>
          .
          <source>Data Knowl. Eng</source>
          .
          <volume>53</volume>
          ,
          <issue>2</issue>
          ,
          <fpage>129</fpage>
          --
          <lpage>162</lpage>
          (
          <year>2005</year>
          )
          <fpage>10</fpage>
          .
          <string-name>
            <surname>Hollingsworth</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>The Workflow Reference Model</article-title>
          .
          <source>Document Number TC00-1003 Document Status - Issue</source>
          <volume>1</volume>
          .
          <fpage>1</fpage>
          . (
          <year>1995</year>
          )
          <fpage>11</fpage>
          .
          <string-name>
            <surname>Gómez-Pérez</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fernández-López</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Corcho</surname>
            ,
            <given-names>O.: Ontological</given-names>
          </string-name>
          <string-name>
            <surname>Engineering</surname>
          </string-name>
          .
          <article-title>With Examples from the Areas of Knowledge Management, e-Commerce and the Semantic Web</article-title>
          . Springer-Verlag, London (
          <year>2004</year>
          )
          <fpage>12</fpage>
          .
          <string-name>
            <surname>Aalst</surname>
            ,
            <given-names>W.M.P.V.D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hee</surname>
            ,
            <given-names>K.V.</given-names>
          </string-name>
          :
          <article-title>Workflow Management - Models, Methods and Systems</article-title>
          . MIT Press, Cambridge (
          <year>2002</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>