<!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>A Pattern-based Approach to Transform Natural Text from Laws into Compliance Controls in the Food Industry</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Andrea Zasada</string-name>
          <email>azasada@web.de</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Michael Fellmann</string-name>
          <email>michael.fellmann@uni-rostock.de</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Rostock University</institution>
          ,
          <addr-line>Rostock</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
      </contrib-group>
      <fpage>230</fpage>
      <lpage>238</lpage>
      <abstract>
        <p>In the food industry, regulations support companies to specify what needs to be done to minimize the risks of processing, trade and consumption of inferior food products. Complying with regulations protects companies from expensive and negative perceived product recalls, sanctions and financial penalties. A compliant manufacturing process requires a process design that conforms to legal requirements, quality and safety standards. Regulations are generally described in natural text so that relevant information has to be retrieved and formalized before it can be used for process description. In this contribution, we use a sample of laws and an initial set of generic control patterns to explore the scope of food regulations and the extent of formalization that can be reached by applying control patterns. All in all, we present a pattern-based approach to turn natural text from laws into formalized machine-readable constructs that may serve as basis for a compliant process design.</p>
      </abstract>
      <kwd-group>
        <kwd>Business Process Management</kwd>
        <kwd>Control Pattern</kwd>
        <kwd>Business Process Compliance</kwd>
        <kwd>Regulations</kwd>
        <kwd>Food Industry</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Motivation and Introduction</title>
      <p>
        The “act of being in alignment with guidelines, regulations and/or legislation” is
defined as compliance [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. This definition implies that compliance does not only
comprise the adherence to laws but also standards, codes of practice and business partner
contracts [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]. Compliance has been driven by reforms of the American banking and
insurance sector since the 1990s, when more and more scandals of money laundering
and insider trading have been revealed [
        <xref ref-type="bibr" rid="ref10 ref14">10, 14</xref>
        ]. The increasing reform pressure
finally summits in the Sarbanes-Oxley Act (SOX) of 2002 which makes listed companies
responsible for establishing and maintaining an internal control system [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ].
      </p>
      <p>
        Similar observations can be made for the food industry, where compliance is seen
as a current issue but an old problem that has been subject of many regulative
attempts [
        <xref ref-type="bibr" rid="ref10 ref14">10, 14</xref>
        ]. Most frequent compliance offences in the food industry relate to
violations of disclosure information, tax and import regulations and to the processing and
trade of spoiled food [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. Business process compliance considers how a business
operation or service should be carried out to comply with a normative system while
executing a process [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. In this regard, control patterns are important since they can be
understood as high level domain-specific templates which can be applied to specify
recurring process requirements like regulations [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ]. A regulation is a declarative
written statement defined as “a rule or order issued by an executive authority or
regulatory agency of a government and having the force of law” [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ].
      </p>
      <p>The purpose of this paper is to reduce the complexity regulations making implicit
information accessible and machine-readable through the use of control patterns. The
challenge is to identify and convert relevant process information from natural text into
formalized constructs that can implemented by process execution languages. The
investigation’s focus lies on the degree of formalization (extent) and the thematic
focus (scope) of a real-world domain (food industry), which is used as empirical basis
for specifying control patterns. In behalf of that, the resulting research questions are:</p>
      <sec id="sec-1-1">
        <title>RQ1: What is the scope of regulations in the food industry?</title>
      </sec>
      <sec id="sec-1-2">
        <title>RQ2: To what extent can regulations be formalized by control patterns?</title>
        <p>
          To answer these two research questions, we discuss related work and present a
conceptual model for automating compliance checking in Section 2. In Section 3 we
continue with the textual analysis of German food regulations. The regulations have
been retrieved by querying the database of the Federal Ministry of Justice and
Consumer Protection [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ]. The title search for the keyword “food” led to 20 national
regulations, which were analyzed to specify requirement, objective and risk for every
single regulation. Control patterns that are extracted from regulations are classified
with regard to the given process information. Concluding remarks and prospects on
future work are given in Section 5.
2
2.1
        </p>
      </sec>
    </sec>
    <sec id="sec-2">
      <title>Principles of Control Patterns</title>
      <sec id="sec-2-1">
        <title>Related Work and Problem Specification</title>
        <p>
          Considerable work on patterns has been provided by Dwyer, Avrunin and Corbett
(1999), who developed a pattern system for finite-state verification based on a large
sample of over 500 examples of property specifications [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ]. Extensive work on
compliance automation has also been conducted by Sadiq, Governatori (2015) [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ],
Namiri (2007) [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ] as well as Turetken et al. (2012) [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ] by exploiting formal
techniques (e.g. MTL/LTL and FCL) in alignment to the de facto standard COSO for
managing internal controls. COSO has been settled by the Committee of Sponsoring
Organizations of the Treadway Commission (COSO) to comply with significant
regulations like SOX [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ]. We decided to build our conceptual model upon the four
control patterns Order, Occurrence, Resource and Time suggested by Turetken et al.
(2012) [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ] because of the existence of a framework for the key elements of business
process compliance management (BPCM) and its alignment to an established control
framework like COSO. The key elements of BPCM refer to the operational activities
of compliance management (e.g. risk assessment and response) and corresponding
entities of the compliance repository (e.g. risk).
2.2
        </p>
      </sec>
      <sec id="sec-2-2">
        <title>Conceptual Model for Capturing Compliance Controls</title>
        <p>
          In order to capture compliance controls in the food industry we adopted the BPCM
framework of Turetken et al. (2012) [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ]. The focus of the framework has been
shifted from operational compliance management activities to the formalization of natural
text language through control patterns. Control Patterns form a separate layer in the
continuum of abstraction ranging from Regulations to machine-readable Process
Execution Languages (see Fig. 1). Each layer contains several process elements
represented by different operands (compare Section 3.2). Regulations are the source of
compliance requirements used to define the requirement, objective and risk of a
control. The smallest entity of a Regulation is a rule. In this layer relevant rules are
adopted, control objectives are set and possible risks are assed. The next layer is
assigned to the scope of Control Patterns. Within this layer the templates for process
controls are defined and classified. In the bottom layer we specified a number of
criteria for selecting a compatible Process Execution Language to pave the way for
automated compliance controls.
        </p>
        <p>Adoption of relevant rules</p>
        <p>Regulations
Requirement</p>
        <p>Objective</p>
        <p>Risk</p>
        <p>Control Patterns
Specification of process requirements</p>
        <p>Order</p>
        <p>
          As we conducted a facet classification on compliance checking approaches in
previous work [
          <xref ref-type="bibr" rid="ref3">3</xref>
          ], we adopted one of its dimensions to assess the scope of regulations in
the food industry. We chose the dimension Scope because we wanted to analyze the
applicability of its elements in more detail. The dimension Scope is based on the
compliance concerns identified by COMPAS, a study on Compliance-driven Models,
Languages and Architectures for Services (COMPAS), which has been conducted by
Tilburg University (2008) [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ]. The study introduces two categories of compliance
1 In alignment to Turetken et al. (2012).
concerns that have been aligned from business process modeling. The first category
comprises the basic compliance concerns control flow, locative, information, resource
and time. The second category describes more advanced compliance concerns (e.g.
monitoring, privacy and quality aspects).
3
3.1
        </p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>Applying Control Patterns to Capture Compliance Controls</title>
      <sec id="sec-3-1">
        <title>Text Analysis of Regulations in the Food Industry</title>
        <p>
          Regulations for the German food industry have been discovered by searching the
database of the Federal Ministry of Justice and Consumer Protection, which claims to
offer nearly the entire body of federal law [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ]. A title search for the German
equivalent for “food” returned 20 hits of national regulations, which were further analyzed
to gain information on the requirement, objective and risk of each regulation. The
analysis of subsequent paragraphs and sections of each regulation led us to a total of
108 single requirements with process characteristics. The requirements are used to
extract important process information for specifying control patterns. While a
requirement can be seen as an early stage of a control pattern, the objective is necessary
to express the importance of each control and the risk to access the negative
consequence of non-compliance. Table 1 shows an excerpt of the complete listing which is
addressing the scope of compliance regulations (compare RQ1). The advantage of the
chosen examples is that they cover nearly all facets of the dimension Scope, which is
used in Section 3.2 to demonstrate the transformation from compliance requirements
to control patterns. The retrieved types of regulations vary from the definition of:
• quality controls,
• hygiene and purity requirements,
• requirements regarding the processing of goods,
• preventing the spread of animal diseases,
• requirements regarding transport and storage,
• disclosure agreements to
• tax and export regulations.
        </p>
      </sec>
      <sec id="sec-3-2">
        <title>Regulation</title>
      </sec>
      <sec id="sec-3-3">
        <title>Requirement</title>
      </sec>
      <sec id="sec-3-4">
        <title>Objective</title>
        <p>Conduct quality
controls if infectious
animal diseases are
reported.</p>
        <p>Export goods within a
certain time limit or
store goods in an
approved or
registered national storage.</p>
      </sec>
      <sec id="sec-3-5">
        <title>Risk</title>
        <p>Spread of infectious
animal diseases.</p>
        <p>Violation of tax and
import regulations.
01
02</p>
        <p>LMÜV
§ 5, Sec. 1
LMEV
§ 9, Sec. 2
(1) Fulfil occasionally
imposed obligations to combat
animal diseases.
(2) Take precaution if
infectious animal diseases occur.</p>
        <p>Export goods within 30 days
to a third country or store
goods within 60 days in an
approved or registered
national storage unit.</p>
        <p>LME
Appendix 4,
Chapter I,
No. 3
TLMV
§ 2
ATP
§ 5
LMHV
§ 20</p>
        <p>Depending on the statutory
sample size, a sensory
testing and a legal assessment
have to be conducted after
opening the packaging.</p>
        <p>During deep freezing, goods
have to be separated from
specified inadmissible
substances.</p>
        <p>Containers classified as
thermal maritime by land
without transloading the
goods does not require an
export permit.</p>
        <p>Transport and store chicken
eggs 18 days after laying
date at a temperature
between 5 °C and 8 °C.</p>
        <p>Conduct quality
control to check
goods after opening
the packaging.</p>
        <p>Prevent contact to
forbidden substances.</p>
        <p>Transport goods
without permit if
containers are
classified as thermal
maritime by land.</p>
        <p>Transport special
goods within a certain
time limit at a given
temperature range.</p>
        <p>Processing, trade and
consumption of
spoiled or
contaminated goods.</p>
        <p>Processing, trade and
consumption of
spoiled or
contaminated goods.</p>
        <p>Violation of
disclosure agreements.</p>
        <p>Processing, trade and
consumption of
spoiled or
contaminated goods.
• processing, trade and consumption of spoiled or contaminated goods,
• spread of infectious animal diseases,
• violation of disclosure agreements and
• violation of tax and import regulations.</p>
        <p>Subsequent risks are negative consequences like disposal costs, sanctions and
financial penalties or even health hazards. However, these consequences depend on the
risks above so they have not been considered as single risk types. Given these explicit
information on requirement, objective and risk the next Section is dedicated to the
control pattern layer that serves as intermediary to automate compliance controls with
process execution languages (compare Section 2.2).
3.2</p>
      </sec>
      <sec id="sec-3-6">
        <title>Specification of Control Patterns in the Food Industry</title>
        <p>The formalization of legal text implies to find a reasonable abstraction level. This
raises the question to what extent regulations can be formalized by simple constructs
like control patterns (compare RQ2). Table 2 provides an overview on frequent
control patterns in the food industry. Due to space limitations, only those patterns have
been listed that have been applied to formalize compliance regulations. The frequency
(FRQ) indicates how often a pattern has been used and to which category it belongs.
The listing contains 21 unique control patterns that can be combined to express even
more complex compliance requirements using operands and Boolean delimiters (see
Table 3). Patterns can be defined using simple verb constructs and prepositions (e.g.
Oi CompliesWith Qi). Operands are either used to specify general process elements
(e.g. object Oi) or specific compliance concerns (e.g. quality control Qi), which were
introduced in Section 2.2. A complete description of operands is given in Table 2.</p>
      </sec>
      <sec id="sec-3-7">
        <title>Pattern</title>
      </sec>
      <sec id="sec-3-8">
        <title>Description</title>
        <p>c Aj Precedes Ai
i
s
a
B Ai LeadsTo Aj</p>
        <p>Oi Exclusive Oj
c
i
s
aB Oi Exists</p>
        <p>ProcessedWith pi</p>
        <p>StoredIn li
c
isa MovedFrom li MovedTo lj
B
(Oi , …; m)
MultiProcessedWith pi
(Oi , …; m)
MultiStoredIn li</p>
        <p>Oi CompliesWith Qi
ced Oi CompliesWith Di
n
a
v
d
A</p>
        <p>Ai CompliesWith Pi
Ai CompliesWith Qi</p>
        <p>Given A, O, l, p, k and t as operands representing process elements:
A = activity, O = object, l = location, p = production facility,
k = time, t = temperature and
FRQ</p>
        <p>Q, D and P as operands representing compliance concerns:
Q = quality, D = disclosure and P = security precautions,
with i, j = 1, 2, 3, …n, i ≠ j and constant m.
1
1
6
3
5
4
4
3
1
24
10
3
2</p>
        <p>Ai must be preceded by Aj.</p>
        <p>Ai must be followed by Aj.</p>
        <p>If Oi is present then Oj must be absent and vice versa.</p>
        <p>Oi must exist in the process specification.</p>
        <p>Used with order and occurrence patterns to denote a given
Oi is processed with production facility pi.</p>
        <p>Used with order and occurrence patterns to denote a given
Oi is stored in storage unit li.</p>
        <p>Used with order and occurrence to denote a given Oi is
moved from storage unit li to another storage unit lj.</p>
        <p>A set of objects (Oi , …) has to be processed with a certain
number of m different production facilities pi.</p>
        <p>A set of objects (Oi , …) has to be stored in a certain
number of m different storage units li.</p>
        <p>Object Oi complies with quality standards, hygiene and
purity requirements by passing regular quality controls as
well as extraordinary quality controls Qi. Subject of these
controls are e.g. temperature, weight, date of expiry,
ingredients, texture and consistence.</p>
        <p>Object Oi complies with disclosure requirements Di.
Subject of these requirements are the consumer protection, tax
and import regulations e.g. by correct and complete
product declaration, complying with quality and security
standards, transparent production processes and a
traceable supply chain.</p>
        <p>Activity Ai has to be performed with special security
precautions Pi in order to protect users from e.g. infectious
animal diseases.</p>
        <p>Activity Ai complies with quality standards, hygiene and
purity requirements by applying regular quality controls as
well as extraordinary quality controls Qi (e.g. to prevent
the spread of animal diseases).</p>
        <p>Used with order pattern to denote a given Ai to happen
within k time units.</p>
        <p>Used with order patterns to denote a given Ai to happen
before k time units.</p>
        <p>Ai must hold at most/minimum k time units once it
happens
Ai must happen in every k time unit.</p>
        <p>Used with time patterns to denote a given Oi is tempered
within temperature t (with i &gt; j).</p>
        <p>Used with time patterns to denote a given Oi is tempered
below temperature t.</p>
        <p>Used with time patterns to denote a given Oi is tempered
exactly at temperature t.</p>
        <p>Object Oi has to be tempered at most/minimum at
temperature t.</p>
        <p>To formalize the requirements given in Table 2, we distinguish a number of typical
keywords for each pattern. For example, a control is often aligned to the assurance of
quality standards, so that the word “control” is tied to an Information pattern.
Resource patterns (Res.) are usually described by expressions that indicate how goods
should be handled, which is indicated by word orders like “prevent contact”. Location
patterns are clearly addressed if something is about to be “processed”, “moved” or
“stored”. Depending on the context, keywords like “within” or “below” can also
indicate if a pattern depends on Time and/or Temperature pattern. The most important
indicators to classify control patterns with regard to our conceptual model for
automating checking are:
• temporal order (e.g. precedes or leads),
• occurrence (e.g. exists, absent or universal),
• human resource (e.g. to segregate or merge activities),
• location in conjunction with the process status (e.g. processed, moved or stored),
• time limitation (e.g. interval, minimum or maximum) and
• temperature setting (e.g. within, below, above or exactly at).</p>
        <p>
          Instead of the control flow proposed by COMPAS [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ] we used the three patterns
Time, Order and Occurrence recommended by Turetken et al. (2012) [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ] and
expanded the focus of the Resource pattern from the segregation of duties to the
segregation of input goods. Besides, we added an information, location and temperature
pattern. The Information pattern indicates which legal source, control objective and
risk is addressed or whether the requirements of a quality control, security precaution
or disclosure agreement is met. This ensures transparency and provides valuable
con2
        </p>
        <p>According to Turetken et al. (2012). Newly added control patterns are indicated by a grey
filled table row.
text information about the impact of different food regulations. The Location pattern
considers how goods should be stored, moved or where they are processed with
regard to time and temperature constraints. The Temperature pattern is necessary to
capture compliance regulations regarding the storage and transport of perishable food.
The final set of control patterns consists of seven categories: Order, Occurrence,
Resource, Location, Information, Time and Temperature. Table 3 concludes with the
formalization of compliance regulations that started with Table 1. It shows simple
patterns as well as more complex patterns to demonstrate the applicability of the most
frequent compliance patterns in the food industry.</p>
        <p>Control Patterns
01
02
03
04
05
06</p>
        <p>Oi CompliesWith Qi AND Ai CompliesWith
Pi AND Oi ProcessedWith pi
(Oi MovedFrom li MovedTo lj Within k)
OR (Oi StoredIn li Within k)
Ai LeadsTo Aj AND Oi CompliesWith Qi
In this contribution we applied a pattern-based approach for specifying compliance
controls in the food industry. Based on a sample of 20 legal text documents, provided
by the German Federal Ministry of Justice and Consumer Protection law database, we
derived 108 legal statements with process character. These were used to analyze the
content of every regulation concerning requirement, objective and risk. To access the
scope of food regulations we adopted a business process compliance framework and
expanded it by refining the Scope of control patterns by Resource, Location,
Information and Temperature patterns. Determining the frequency of compliance patterns
we were able to present a list of relevant control patterns in the food industry. The use
of control patterns has been illustrated by a choice of regulations which address the
previously defined facets of the Scope dimension. This led to a deeper understanding
of the involved process elements and compliance concerns, which will help to
evaluate the benefits and boundaries of current process execution languages used for
compliance checking. Future work will be guided by the research question, how control
patterns can be used to automate compliance controls. Remaining challenges,
regarding the syntax of control patterns, deal with the accuracy versus complexity of applied
control patterns and a standardized use of patterns and connectors that enable the
implementation of compliance patterns by common process execution languages. To
improve the approach further, we will evaluate the usability for the average user with
basic IT knowledge and the process modeler with high IT affinity as well.</p>
      </sec>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Dwyer</surname>
            ,
            <given-names>M. B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Avrunin</surname>
            ,
            <given-names>G. S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Corbett</surname>
            ,
            <given-names>J. C.</given-names>
          </string-name>
          :
          <article-title>Patterns in property specifications for finitestate verification</article-title>
          .
          <source>In: IEEE International Conference on Software Engineering</source>
          , pp.
          <fpage>411</fpage>
          -
          <lpage>420</lpage>
          . IEEE Press, New York (
          <year>1999</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Federal</surname>
          </string-name>
          <article-title>Ministry of Justice and Consumer Protection, Juris (Bundesministerium für Justiz und Verbraucherschutz -</article-title>
          BMJ): http://www.gesetze
          <article-title>-im-internet</article-title>
          .de
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Fellmann</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zasada</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>State-of-the-Art of Business Process Compliance Approaches: A Survey</article-title>
          ,
          <source>Proceedings of the 22nd European Conference on Information Systems (ECIS)</source>
          ,
          <source>Tel Aviv</source>
          (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>4. Foodwatch: http://www.foodwatch.org/en/what-we-do/campaigns/foodwatch-campaigns</mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Hashmi</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Governatori</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wynn</surname>
          </string-name>
          , M.T.:
          <article-title>Normative requirements for business process compliance</article-title>
          .
          <source>Service Research and Innovation</source>
          , pp.
          <fpage>100</fpage>
          -
          <lpage>116</lpage>
          . Springer, Berlin (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Merriam-Webster</surname>
          </string-name>
          , An Encyclopaedia Britannica Company: Compliance, http://www.merriam-webster.com/dictionary/compliance
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Merriam-Webster</surname>
          </string-name>
          , An Encyclopaedia Britannica Company: Regulation, http://www.merriam-webster.com/dictionary/regulation
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Namiri</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Stojanovic</surname>
          </string-name>
          , N.:
          <article-title>Pattern-based design and validation of business process compliance</article-title>
          .
          <source>In: Proceedings of 6th On The Move Conference (OTM)</source>
          , Tari,
          <string-name>
            <surname>Z</surname>
          </string-name>
          . (ed.),
          <source>LNCS 4083</source>
          , pp.
          <fpage>59</fpage>
          -
          <lpage>76</lpage>
          . Springer, Berlin, (
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Sadiq</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Governatori</surname>
          </string-name>
          , G.:
          <article-title>Managing Regulatory Compliance in Business Processes</article-title>
          .
          <source>In: Handbook on Business Process Management</source>
          <volume>2</volume>
          :
          <string-name>
            <surname>Strategic</surname>
            <given-names>Alignment</given-names>
          </string-name>
          , Governance, People and Culture,
          <source>International Handbooks on Information Systems</source>
          , vom Brocke, J.,
          <string-name>
            <surname>Rosemann</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <source>(eds.)</source>
          , vol.
          <volume>2</volume>
          , pp.
          <fpage>265</fpage>
          -
          <lpage>288</lpage>
          . Springer, Berlin (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Shears</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>Food Fraud: A Current Issue but an Old Problem</article-title>
          .
          <source>British Food Journal</source>
          , vol.
          <volume>112</volume>
          , no.
          <issue>2</issue>
          , pp.
          <fpage>198</fpage>
          -
          <lpage>213</lpage>
          (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11. SOX: Sarbanes-Oxley
          <source>Act of 30 July</source>
          <year>2002</year>
          ,
          <volume>15</volume>
          USC 7201 note,
          <source>Public Law 107-204, 107th Congress</source>
          , 116 Statistics Act,
          <year>Sec</year>
          .
          <volume>404</volume>
          , pp.
          <fpage>745</fpage>
          -
          <lpage>810</lpage>
          (
          <year>2002</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12. Tilburg University:
          <article-title>State-of-the-Art for Compliance Languages: Compliance-driven Models, Languages, and Architectures for Services</article-title>
          ,
          <source>Specific Targeted Research Project. Information Society Technologies (COMPAS Project no. 215175</source>
          ,
          <issue>D2</issue>
          .1), Netherlands (
          <year>2008</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Turetken</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Elgammal</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          , Van den Heuvel, W.J.,
          <string-name>
            <surname>Papazoglou</surname>
            ,
            <given-names>M.P.</given-names>
          </string-name>
          :
          <article-title>Capturing compliance requirements: A pattern-based approach</article-title>
          . IEEE, vol.
          <volume>29</volume>
          , no.
          <issue>3</issue>
          , pp.
          <fpage>28</fpage>
          -
          <lpage>36</lpage>
          . IEEE Press, New York (
          <year>2012</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Weber</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Diaz</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Schwegler</surname>
          </string-name>
          , R.:
          <article-title>Corporate social responsibility of the financial sector - Strengths, weaknesses and the impact on sustainable development</article-title>
          .
          <source>Sustainable Development</source>
          , vol.
          <volume>22</volume>
          , no.
          <issue>5</issue>
          , pp.
          <fpage>321</fpage>
          -
          <lpage>335</lpage>
          (
          <year>2014</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>