<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//TaxonX//DTD Taxonomic Treatment Publishing DTD v0 20100105//EN" "../../nlm/tax-treatment-NS0.dtd">
<article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:tp="http://www.plazi.org/taxpub" article-type="research-article" dtd-version="3.0" xml:lang="en">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">109</journal-id>
      <journal-id journal-id-type="index">urn:lsid:arphahub.com:pub:3dc5f44e-8666-58db-bc76-a455210e8891</journal-id>
      <journal-title-group>
        <journal-title xml:lang="en">JUCS - Journal of Universal Computer Science</journal-title>
        <abbrev-journal-title xml:lang="en">jucs</abbrev-journal-title>
      </journal-title-group>
      <issn pub-type="ppub">0948-695X</issn>
      <issn pub-type="epub">0948-6968</issn>
      <publisher>
        <publisher-name>Journal of Universal Computer Science</publisher-name>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="doi">10.3217/jucs-020-08-1109</article-id>
      <article-id pub-id-type="publisher-id">23413</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Research Article</subject>
        </subj-group>
        <subj-group subj-group-type="scientific_subject">
          <subject>C.3 - SPECIAL-PURPOSE AND APPLICATION-BASED SYSTEMS</subject>
          <subject>H.4.1 - Office Automation</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>Internet of Things Aware WS-BPEL Business Processes Context Variables and Expected Exceptions</article-title>
      </title-group>
      <contrib-group content-type="authors">
        <contrib contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Domingos</surname>
            <given-names>Dulce</given-names>
          </name>
          <email xlink:type="simple">dulce@di.fc.ul.pt</email>
          <xref ref-type="aff" rid="A1">1</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Martins</surname>
            <given-names>Francisco</given-names>
          </name>
          <xref ref-type="aff" rid="A1">1</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Cândido</surname>
            <given-names>Carlos</given-names>
          </name>
          <xref ref-type="aff" rid="A1">1</xref>
        </contrib>
        <contrib contrib-type="author" corresp="no">
          <name name-style="western">
            <surname>Martinho</surname>
            <given-names>Ricardo</given-names>
          </name>
          <xref ref-type="aff" rid="A2">2</xref>
        </contrib>
      </contrib-group>
      <aff id="A1">
        <label>1</label>
        <addr-line content-type="verbatim">University of Lisbon, Lisbon, Portugal</addr-line>
        <institution>University of Lisbon</institution>
        <addr-line content-type="city">Lisbon</addr-line>
        <country>Portugal</country>
      </aff>
      <aff id="A2">
        <label>2</label>
        <addr-line content-type="verbatim">Polytechnic Institute of Leiria, Leiria, Portugal</addr-line>
        <institution>Polytechnic Institute of Leiria</institution>
        <addr-line content-type="city">Leiria</addr-line>
        <country>Portugal</country>
      </aff>
      <author-notes>
        <fn fn-type="corresp">
          <p>Corresponding author: Dulce Domingos (<email xlink:type="simple">dulce@di.fc.ul.pt</email>).</p>
        </fn>
        <fn fn-type="edited-by">
          <p>Academic editor: </p>
        </fn>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2014</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>01</day>
        <month>08</month>
        <year>2014</year>
      </pub-date>
      <volume>20</volume>
      <issue>8</issue>
      <fpage>1109</fpage>
      <lpage>1129</lpage>
      <uri content-type="arpha" xlink:href="http://openbiodiv.net/7C53CC6F-B638-5D67-8D28-1E077CCA15F4">7C53CC6F-B638-5D67-8D28-1E077CCA15F4</uri>
      <uri content-type="zenodo_dep_id" xlink:href="https://zenodo.org/record/5505421">5505421</uri>
      <history>
        <date date-type="received">
          <day>04</day>
          <month>04</month>
          <year>2014</year>
        </date>
        <date date-type="accepted">
          <day>23</day>
          <month>07</month>
          <year>2014</year>
        </date>
      </history>
      <permissions>
        <copyright-statement>Dulce Domingos, Francisco Martins, Carlos Cândido, Ricardo Martinho</copyright-statement>
        <license license-type="creative-commons-attribution" xlink:href="" xlink:type="simple">
          <license-p>This article is freely available under the J.UCS Open Content License.</license-p>
        </license>
      </permissions>
      <abstract>
        <label>Abstract</label>
        <p>Business processes can use Internet of Things (IoT) information to monitor context data in real-time and to respond to changes in their values in a timely fashion. For this matter, business process definition and execution languages should foresee an easy way for process modelers to define which values to monitor, and which automatic behaviors to adopt when these values change. In this paper, we propose the use of context variables to monitor sensor values, as well as a when-then language construct to detect and handle changes in these values within business processes. We define a Web Services Business Process Execution Language (WS-BPEL) extension to convey these constructs, and implement then using a "BPEL language transformation" approach. With these contributions, process modelers can define IoT-aware business processes avoiding the increase of process complexity and keeping their focus on modeling the processes' main logic. In addition, the language transformation approach assures the portability of processes using our constructs amongst WS-BPEL execution engines.</p>
      </abstract>
    </article-meta>
  </front>
</article>
