<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>The Hazardous Situation Ontology Design Pattern</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Agnieszka Lawrynowicz</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Ilona Lawniczak</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Institute of Computing Science, Poznan University of Technology</institution>
          ,
          <addr-line>Poznan</addr-line>
          ,
          <country country="PL">Poland</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>This extended abstract describes an ontology design pattern for modeling hazardous situations. We build upon state-of-art models for hazards and hazardous events, and on existing standards in the domain of occupational safety. We also present an example of the application of the pattern in the occupational safety and health domain. Hazard is a potential source of harm on someone or something. It is a threat that may be caused by source, situation, or act with a potential for harm. The need for ontological modeling of hazards and related concepts such as risks, causes and consequences has been identified in several domains. The Risk base ontology from the EU project RISCOSS [1] uses the concepts of Event and Situation from the foundational ontology Dolce Lite Plus [2] to define the concepts of Risk, Risk Event, Goal, Activity, Cause, Consequence, Impact, and Measure for software component selection. It re-uses concepts from another risk ontology, defined in the EU project Musing and definitions from standards such as ISO 31000. It does not include, however, a concept of hazard. Threat is modeled in Cyber Security ontology [3]. Also a hackathon at Ontology Summit 20141 has recently been devoted to modeling hazard and risk related concepts in travel domain. The report uses the term hazard as of an event. Furthermore, RiskEvent is a superclass of accidents in this view. In this case, Factor (such as EnvionmentalFactor, e.g. Limited Sight) is closest to our interpretation of the meaning of the term hazard. In this work, we describe the Hazardous Situation Ontology Design Pattern2. We take a step towards a clarification and consolidation of some of these terms. This pattern was inspired by a dependency scheme of terminology concerning hazards in EU norm OHSAS 18001:2007 (hazard → hazardous situation → occupational risk), but is generic.</p>
      </abstract>
      <kwd-group>
        <kwd>ontology design pattern</kwd>
        <kwd>ODP</kwd>
        <kwd>hazards</kwd>
        <kwd>occupational safety and health</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1 Introduction</title>
      <p>
        2 The Hazardous Situation Ontology Design Pattern
The Hazardous Situation Ontology Design Pattern is depicted in Figure 1.
HazardousSituation is a situation that participates in one or more HazardousEvents.
HazardousSituation represents a kind of snapshot, a context, a setting or a state.
The meaning of ’situation’ is similar to that of the class situation in the
Descriptions &amp; Situations (DnS) extension [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] of the DOLCE ontology [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], also similar
to that of the DuringState in the Event and Situation Ontology (ESO) ontology
[
        <xref ref-type="bibr" rid="ref6 ref7">6, 7</xref>
        ], or a discrete state (a fluent) in the PSL ontology [
        <xref ref-type="bibr" rid="ref8 ref9">8, 9</xref>
        ].
      </p>
      <p>HazardousEvent is defined as an event where at least one participating Object
is exposed to a Hazard. Already the exposure of an object (e.g. a person) to a
hazard suffices for the event to be called HazardousEvent, an emergence of any
consequence is not a condition. Any HazardousEvent also has some duration (of
the type of TimeInterval3).</p>
      <p>HazardousEvent may casually follow some Cause and may cause one or more
Consequences. A Cause may be an unsafe act, such as spilling oil and not clearing
it up. This results in an unsafe condition of a pool of oil on the floor. A
HazardousEvent is triggered when somebody enters this part of the floor and as a
consequence may lead to an accident such as someone slipping on the oil, falling
and breaking his/her leg.</p>
      <p>Exposure is a measure of the extent (a dose) to which an Object is exposed
to – or may be influenced by – the Hazard.</p>
      <sec id="sec-1-1">
        <title>2.1 Intent</title>
        <p>The intent of a pattern is to provide a building block for modeling hazardous
situations. Those situations are the situations where one or more objects is
ex3 http://ontologydesignpatterns.org/wiki/Submissions:TimeInterval
The Hazardous Situation Ontology Design Pattern
posed to one or more hazards to some extent (exposure value). Such situations
have some cause that triggered the enactment of a hazard. They also result in
some consequences.</p>
      </sec>
      <sec id="sec-1-2">
        <title>2.2 Competency Questions</title>
        <p>The list of competency questions for the pattern is as follows:
– What object (person, organization, equipment etc.) is exposed to a hazard?
– To which hazard is exposed an object (person, organization, equipment etc.)?
– Which hazardous events are associated with a hazardous situation?
– What is the cause of a hazardous event?
– What is the consequence of a hazardous event?
– What is the value of exposure of an object being exposed to a hazard?</p>
      </sec>
      <sec id="sec-1-3">
        <title>2.3 Pattern Formalization</title>
        <p>
          Below we provide the formalization of the pattern in the Web Ontology
Language (OWL) [
          <xref ref-type="bibr" rid="ref10">10</xref>
          ], expressed in description logic (DL) [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ]:
HazardousSituation v ∃participantIn.HazardousEvent
HazardousEvent ≡ ∃hasParticipant.(Object u ∃exposedTo.Hazard)
HazardousEvent v ∃hasQuality.Exposure
HazardousEvent v ∃hasDuration.TimeInterval
HazardousEvent v ∃casuallyFollows.Cause
Consequence v ∃casuallyFollows.HazardousEvent
Cause v Event
HazardousEvent v Event
Consequence v Event
        </p>
      </sec>
      <sec id="sec-1-4">
        <title>2.4 Example Usage: Occupational Safety and Health</title>
        <p>
          Occupational safety and health is defined as the scientific domain dealing with
the anticipation, identification, evaluation and control of hazards that emerge in
or from the workplace and that may negatively impact the health and well-being
of workers [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ].
        </p>
        <p>Consider the following scenario: ”The farmer is spraying pesticides on the
fields. He asked a student working on a farm for help in carrying pesticide
sprayers and storage containers. In this situation, neither the farmer nor the
student is wearing any personal protective equipment such as gloves or using any
respirators. After 4 hours of spraying, they student developed skin irritation.”.</p>
        <p>In this scenario, the Objects are Farmer and Student that are both Workers.
The Workplace is the field. HazardousSituation is associated with at least two
HazardousEvents both defined as a Worker (Farmer and Student) being exposed
to an OccupationalHazard (pesticides). The Cause of this exposure is lack of
personal protective equipment, and the immediate Consequence is
HealthDeterioration (skin irritation).</p>
      </sec>
    </sec>
    <sec id="sec-2">
      <title>3 Summary</title>
      <p>In this paper, we have presented an ontology design pattern for modeling
hazardous situations.</p>
      <p>In future work, we will further investigate the use of a suitable event model,
including a spatio-temporal dimension. We will also investigate in more detail
the modeling of causality. Next steps of the future work agenda include re-using
the pattern for modeling the occupational safety and health domain.
Acknowledgements. This work was partially supported from the
PARENTBRIDGE program of Foundation for Polish Science, cofinanced from European
Union, Regional Development Fund (Grant No POMOST/2013-7/8).</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Siena</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Morandini</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Susi</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Modelling risks in open source software component selection</article-title>
          . In
          <string-name>
            <surname>Yu</surname>
          </string-name>
          , E.,
          <string-name>
            <surname>Dobbie</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jarke</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Purao</surname>
          </string-name>
          , S., eds.:
          <source>Conceptual Modeling. Volume 8824 of Lecture Notes in Computer Science</source>
          . Springer International Publishing (
          <year>2014</year>
          )
          <fpage>335</fpage>
          -
          <lpage>348</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Gangemi</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Guarino</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Masolo</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Oltramari</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Sweetening wordnet with dolce</article-title>
          .
          <source>AI Mag</source>
          .
          <volume>24</volume>
          (
          <issue>3</issue>
          ) (
          <year>September 2003</year>
          )
          <fpage>13</fpage>
          -
          <lpage>24</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Oltramari</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cranor</surname>
            ,
            <given-names>L.F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Walls</surname>
            ,
            <given-names>R.J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>McDaniel</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>Building an ontology of cyber security</article-title>
          .
          <source>In: Proceedings of STIDS</source>
          <year>2014</year>
          .
          <article-title>(</article-title>
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Gangemi</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mika</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>Understanding the semantic web through descriptions and situations</article-title>
          . In Meersman, R.,
          <string-name>
            <surname>Tari</surname>
            ,
            <given-names>Z.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schmidt</surname>
          </string-name>
          , D., eds.: On The Move to Meaningful
          <source>Internet Systems</source>
          <year>2003</year>
          :
          <article-title>CoopIS, DOA, and ODBASE</article-title>
          . Volume
          <volume>2888</volume>
          of Lecture Notes in Computer Science. Springer Berlin Heidelberg (
          <year>2003</year>
          )
          <fpage>689</fpage>
          -
          <lpage>706</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Masolo</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Borgo</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gangemi</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Guarino</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Oltramari</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>Ontology library</article-title>
          .
          <source>WonderWeb Deliverable D18 (ver. 1.0</source>
          ,
          <fpage>31</fpage>
          -
          <lpage>12</lpage>
          -
          <year>2003</year>
          ).
          <article-title>(</article-title>
          <year>2003</year>
          ) http://wonderweb.semanticweb.org.
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Segers</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vossen</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rospocher</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Serafini</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Laparra</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rigau</surname>
          </string-name>
          , G.:
          <article-title>Eso: A frame based ontology for events and implied situations</article-title>
          .
          <source>In: Proceedings of MAPLEX</source>
          <year>2015</year>
          , Yamagata, Japan (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Bozzato</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Borgo</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Aprosio</surname>
            ,
            <given-names>A.P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rospocher</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Serafini</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          :
          <article-title>A Contextual Framework for Reasoning on Events</article-title>
          .
          <source>In: DeRiVE2015 Workshop Proceedings</source>
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8. Gru¨ninger,
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Menzel</surname>
          </string-name>
          ,
          <string-name>
            <surname>C.</surname>
          </string-name>
          :
          <article-title>The process specification language (psl) theory and applications</article-title>
          .
          <source>AI Mag</source>
          .
          <volume>24</volume>
          (
          <issue>3</issue>
          ) (
          <year>September 2003</year>
          )
          <fpage>63</fpage>
          -
          <lpage>74</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9. Gru¨ninger, M.:
          <article-title>Using the PSL ontology</article-title>
          . In: Handbook on Ontologies. (
          <year>2009</year>
          )
          <fpage>423</fpage>
          -
          <lpage>443</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>van Harmelen</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>McGuinness</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          :
          <article-title>OWL web ontology language overview</article-title>
          .
          <source>W3C recommendation</source>
          ,
          <source>W3C (February</source>
          <year>2004</year>
          ) http://www.w3.org/TR/2004/REC-owlfeatures-
          <volume>20040210</volume>
          /.
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Baader</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Calvanese</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>McGuinness</surname>
            ,
            <given-names>D.L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nardi</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Patel-Schneider</surname>
          </string-name>
          , P.F., eds.: The Description Logic Handbook: Theory, Implementation, and
          <string-name>
            <surname>Applications</surname>
          </string-name>
          . Cambridge University Press, New York, NY, USA (
          <year>2003</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Alli</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          :
          <article-title>Fundamental Principles of Occupational Health and Safety</article-title>
          .
          <source>International Labour Office</source>
          (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>