<!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>Semantic Workflows in Law Enforcement Investigations and Legal Requirements</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Wolfgang Mayer</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Pompeu Casanovas</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Markus Stumptner</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Louis de Koker</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Danuta Mendelson</string-name>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Data to Decisions Cooperative Research Centre</institution>
          ,
          <country country="AU">Australia</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Deakin Law School, Deakin University</institution>
          ,
          <addr-line>Melbourne</addr-line>
          ,
          <country country="AU">Australia</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>IDT-UAB, Autonomous University of Barcelona</institution>
          ,
          <country country="ES">Spain</country>
        </aff>
        <aff id="aff3">
          <label>3</label>
          <institution>La Trobe Law School, La Trobe University</institution>
          ,
          <addr-line>Melbourne</addr-line>
          ,
          <country country="AU">Australia</country>
        </aff>
        <aff id="aff4">
          <label>4</label>
          <institution>University of South Australia</institution>
          ,
          <addr-line>Adelaide</addr-line>
          ,
          <country country="AU">Australia</country>
        </aff>
      </contrib-group>
      <fpage>51</fpage>
      <lpage>63</lpage>
      <abstract>
        <p>Investigations conducted by law enforcement agencies depend on information that is obtained from a variety of sources, internal and external to the organization. Considering that investigations frequently span multiple jurisdictions and government agencies with varying objectives and powers, assessing and ensuring compliance with their policies and the legal framework is challenging. We present technical features and a semantic information modelling approach that can support compliant workflow execution in the context of law enforcement investigations and discuss how such an information system might be embedded in a complex legislative and social environment. Legal principles, and the concepts of Legal Compliance by Design (LCbD), and Legal Compliance through Design (LCtD) are also introduced.</p>
      </abstract>
      <kwd-group>
        <kwd>Workflow automation</kwd>
        <kwd>Semantic Meta-data</kwd>
        <kwd>Legal Compliance by Design</kwd>
        <kwd>Legal Compliance through Design</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        Investigations conducted by law enforcement agencies (LEAs) are dependent on
information that is obtained from a variety of sources, internal and external to the
organization [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. Sole investigators with paper notebooks have been superseded by sophisticated
information systems that aim to ingest, process, and enrich the collected information to
help law enforcement officers conduct their investigations.
      </p>
      <p>
        Investigations generally follow an iterative process of information collection,
assessment, investigation planning, execution, and brief of evidence preparation where each
step either produces new information or relies on information collected earlier in the
process. Although steps in this process could be supported by automated systems,
information systems in the law enforcement domain are often legacy “silos” that offer
little support for collaborative investigations. Timely information sharing is crucial for
the success of many investigations; however, investigations are often stalled by
impediments related to sharing information [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. Moreover, information management,
investigation planning and execution are largely left to the individual case officer, which might
result in poor information use. Individual investigators often have key responsibilities
for ensuring compliance with complex laws and policies, slowing down collaborative
investigations.
      </p>
      <p>Considering that investigations frequently span multiple jurisdictions and
government agencies with varying objectives and powers, determining the applicable rules
and ensuring compliance with the relevant laws and policies is difficult. The
implications of non-compliance are furthermore serious: evidence collected during the
investigation in contravention of the legal rules might be inadmissible in court.</p>
      <p>
        Therefore, an information system that can effectively support law enforcement
investigations should include mechanisms for enforcing compliant processes in addition
to efficient information management and analytic capabilities. Such a system responds
to the legal issues that are relevant to information use and sharing. For example,
information obtained under a warrant for a specific investigation may not generally be used
in the context of other investigations, and restrictions might apply to agencies as to what
information they can share [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. In addition, many of the aspects of the relevant laws
and rules require careful interpretation. An overly-conservative interpretation of laws
and policies might unnecessarily restrict what can be shared while a liberal approach
may not result in outcomes that are compliant. In addition to legal issues, other matters
that may require consideration include workflows and policies as well as information
security:
      </p>
      <p>Workflows and policies may impact upon investigations. Many investigators and key
offices in LEAs still adhere to antiquated processes and rely on paper forms and manual
approvals for expenditure and information access. The resulting delays have potential
to disrupt investigations. Moreover, the appropriate processes to follow may depend on
the nature of the investigation and the involved agencies. Here, automation and
electronic means of selecting, executing, and monitoring the relevant processes would
streamline the investigation and provide assurance that tasks are undertaken in
compliance with relevant policies and legal frameworks.</p>
      <p>Information security and access control across system and organization boundaries
can be difficult to achieve. In absence of a sophisticated access control mechanism, it
is challenging to guarantee secure access to a large number of users accessing a
multitude of information systems, especially where some of the information is highly
sensitive and should not be accessed by anyone outside of the immediate investigative team.
Often, information is obtained by means of personal communications outside the realms
of the investigation management system. This is especially the case in relation to
sensitive information. While such methods may provide the investigators with a sense of
comfort regarding the security of the data, this approach complicates the tracking and
integration of the information at later stages of the investigation and in the prosecutorial
stage when proof of the integrity of the information may be crucial.</p>
      <p>This paper describes the approach to comprehensive and compliant information
access pursued by the Integrated Law Enforcement project conducted by the Data to
Decisions Cooperative Research Centre (D2D CRC) in Australia. We discuss the
architecture of the Investigation Management System that is currently under development
and highlight its technical features that underpin workflow automation and
investigation planning. We focus on the semantic linked information model underpinning the
system’s workflow automation functions and discuss how they can facilitate compliant
investigations in a complex legislative and social environment.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Investigation Management System</title>
      <p>
        The project Integrated Law Enforcement (ILE) aims to develop a platform where
investigators can manage the information collection, analysis, and processes pertaining
to a case through a consistent single user-facing portal. The portal offers functions for
information ingestion, management and classification, searching, linking of entities, as
well as investigation planning and evidence export that are tailored to the needs of
investigators. Supporting the portal is an extensible software architecture for searching
for information within the collective information base, extraction of entities and
relationships from text documents, linking of entities to form a “knowledge graph”
pertaining to one or more investigations, and integration of external data sources. As such, the
platform aims to serve as a single point of access for investigators to manage their
investigations, request, obtain, and explore information from several sources. The
conceptual architecture of the platform is depicted in Fig. 1. Conceptual system
architecture. The individual components are described in [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. In this paper, we focus on the
process aspect of the architecture.
Automatic data collection and integration offer tremendous opportunities to increase
efficiency and effectiveness of investigations, the sensitivity of information that is
collected and analyzed in this context raise serious legal compliance and governance
challenges. Indeed, compliance with existing laws and principles is a pre-condition of the
whole process [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. Transparency and privacy should be preserved to foster trust
between citizens and national security and law enforcement agencies. Even more so as
prevalent data collection and sophisticated data analysis methods have the potential to
undercut the due process (procedural fairness) safeguards built into the traditional
criminal justice model of operation [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. Therefore, we advocate the view that technical
developments that enable such activities should be informed by and reflect the principles
of the rule of law.
      </p>
      <p>The approach taken in this work rests on a comprehensive semantic model of the
domain that includes entities and relationships relevant to investigations, a meta-data
framework that captures provenance and restrictions on information use, and an
investigation planning and execution model. As information is acquired through the
platform, it can be enriched with meta-data about its lineage, time of acquisition, and the
line of inquiry task that led to this information within the overall investigation plan.</p>
      <p>Semantic models extend to the process aspect of investigations, whereby
investigators can rely on investigation planning functions to open and close lines of
investigations. A taxonomy of offences linked to proof elements that must be established and
templates of potential lines of enquiries can support the investigation planning
activities. The integration of workflow planning and information acquisition functions helps
to maintain detailed lineage of each piece of evidence collected. Moreover, it enables
the system to automate parts of the process.</p>
      <p>
        For example, if a search of premises related to a suspect is to be conducted, and the
semantic model of the activity indicated that this search requires a warrant, the request
for the warrant could be generated and workflows for obtaining approval of that
warrant, planning of the search, and approval of related expenditure, could be initiated
automatically. Once all approvals have been obtained, the investigator would be notified
that the search activity can proceed. Any evidence obtained from the search would be
entered into the system and it would be automatically linked to the line of inquiry, the
task in the process, and its associated warrant. Given that the information is linked to
the investigation process and its legal documents (e.g., warrants), the lineage of the
information can then be used to determine how, when, and by whom that information
may be used, provided that an appropriate semantic model of the conditions and
restrictions is maintained. This approach is comparable to semantic policy annotations
advocated for linked data [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ].
      </p>
      <p>The technology underlying this platform rests on process templates that are
instantiated in the context of a specific investigation. Our current implementation rests on a
Business Process and Notation (BPMN) workflow engine for execution. Configurable
process templates specify the dependencies between activities, whereby process
parameters determine the fillers for placeholder roles, data elements, and concrete
sub-processes that implement hierarchical process steps. For example, business rules
embedded in process templates select appropriate sub-processes tailored for communicating
with different external organizations (to address variety in required information and
technical submission procedures), determine who shall approve a request, etc. The
information required for this configuration can be obtained from the knowledge graph
capturing the current investigation, organization structure, and external parties’
systems. Information that cannot be acquired automatically is entered by the investigator.
Where processes cannot be completed successfully, for example due to the external
organization requiring further information or an organization refusing to cooperate, the
process reverts to manual intervention (for example, initiating another request for
information with additional information attached). This simplifies the approach; as
exceptional cases do not need to be modelled in detail for each process. In the context of
law enforcement investigations, a semi-automated approach is sufficient, provided that
all actions and responses are duly captured on a timeline in a log.</p>
      <p>
        The approach described in the previous paragraphs rests on the assumption that the
relevant procedures and policies are known, well understood, and that they have been
expressed in the form of semantic models that the machine can interpret in the context
of an investigation. Although semantic models may be devised using natural language
processing techniques [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] challenges remain in the disparity between rigid formal
representations (e.g., formal modal logics) and the often context-dependent interpretation
of legal texts. In the context of law enforcement investigations considered in the project,
the relatively small number of defined (internal) workflows can be modelled and
validated manually. A library of workflows, tasks, and information objects complemented
with rules that govern process execution and information use can be created and used
to support the execution of the system.
      </p>
      <p>Further work is required to address issues related to the reconciliation of partly
incompatible norms that can arise when information is exchanged between agencies
embedded in different legal systems. Even if appropriately detailed and complete semantic
models were available, questions would still arise in relation to the reconciliation of
differences in permissions, obligations, and processes. Moreover, suitable mechanisms
for enforcing norms across organizational and legislative boundaries must be developed
to instill trust in the overall information sharing arrangements.
4</p>
    </sec>
    <sec id="sec-3">
      <title>Legal Principles</title>
      <p>
        In previous presentations [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ], we already have highlighted the main sets of legal
problems that we are addressing in this project: (i) the coexistence of both artificial and
human decision-making and information processes; (ii) the identification,
representation and modelling of specific legal requirements arising from different legal and
government sources; (iii) the definition of a blended Regtech perspective to be applied to
law enforcement and security; and (iv) the formulation of general principles for big data
regulation in the Australian environment. Risks that should be mitigated include
overcollection of data; production and use of inaccurate data; biased analysis; inappropriate
data collection, storage, management and handling; inconsistent or uncontrolled
inferences; and breaches of privacy and data protection.
      </p>
      <p>
        Security platforms can collect, store, manage and reuse personal data under Open
Source Intelligence (OSINT) provisions. Where warranted, subject to strict conditions
and appropriate controls, they have to do so [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]. This is of course controversial, as such
collection and use of data affects human, civil, and personal rights. It is therefore crucial
to observe the basic principles of the rule of law. This view has also found support
among technologists: there is a general agreement on fundamental rights and ethical
values that the sciences of design have embraced [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ].
      </p>
      <p>
        However, the specific instruments set to protect and ensure the relevant rights are
embedded in laws that differ globally and are even absent in some countries. Different
legal cultures have therefore taken different approaches. For example, the European
Regulation on Privacy contemplates the possibility to apply by design and by default
the rights initially protected by the Directive 95/46/EC, now replaced by Regulation
(EU) 2016/679, the EU General Data Protection Regulation (GDPR). Some authors
advocate for regulatory, legal and technological enforcement of privacy to prevent
major breaches and abuses [
        <xref ref-type="bibr" rid="ref13">13</xref>
        ].
      </p>
      <p>
        In countries under the Common Law rule, courts play a major role, for example to
determine whether government action that infringes a fundamental right such as
privacy, was reasonable and proportional. In relation to fundamental rights, for example,
the High Court of Australia employs a proportionality analysis to “ascertain the
rationality and reasonableness” of the restriction on the fundamental right: the greater the
restriction on the fundamental right, the more important must be the public interest
purpose of the legislation for the proposed restrictive measure to be proportionate.1 Our
work includes discussion of legal principles to set the general framework to provide
such a balance for national security law enforcement [NSLE] purposes. At present,
these principles could be summarized as follows for purposes of Australia [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]:
1.
2.
3.
4.
5.
6.
7.
8.
      </p>
      <p>Big Data analytics involving personal information should be employed when justified,
and only in so far as is reasonably necessary to achieve defined and legitimate national
security and law enforcement (NSLE) objectives.</p>
      <p>The design, operation and management of all elements of the information lifecycle,
including the application of Big Data analytics, must be proportionate.</p>
      <p>The regulatory framework should be clear, consistent, and well-articulated.</p>
      <p>Integrity of data and analysis should be supported
Data and systems must be protected.</p>
      <p>NSLE agencies and all officers using data at all stages of the information lifecycle must
be accountable.</p>
      <p>Principles, rules, processes and systems should be reviewed regularly and, outside the
review cycle when warranted.</p>
      <p>The regulatory framework should support openness and transparency while
safeguarding operational secrecy, where necessary and justified.</p>
      <p>
        While the principles are still under development, it is clear that principles and
statements about values cannot resolve the monitoring of the workflow and the regulation
1 As quoted in [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ]: “The term ‘proportionality’ in Australian law describes a class of criteria
which have been developed by the High Court of Australia over many years to determine
whether legislative or administrative acts are within the constitutional or legislative grant of
power under which they purport to be done.” McCloy v New South Wales [2015] HCA 34 at
[
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] per French CJ, Kiefel, Bell and Keane JJ.
of the platform at the technical level. They convey values that can be turned into
guidelines, but similarly to Fair Information Practices (FIPs) or privacy and data protection
principles (PP, DPP) [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ], they do not provide any mechanism to easily implement or
embed them. Principles, however, can be interpreted to inform individualized
casebased decisions once a problem or conflict has arisen. They may also be fleshed out
through use case applications, reflected into more specific contents, and
represented/translated into a formal language to minimize risks and prevent law suits and
conflictive situations. However, the scope of fundamental rights and freedoms,
including privacy, procedural fairness, and Australian tests of proportionality, is still to be
settled. Hence, the complexity of translating them into a working tool for compliance
should not be underestimated.
5
      </p>
    </sec>
    <sec id="sec-4">
      <title>Legal Compliance by Design (LCbD)</title>
      <p>
        Legal compliance by design can be defined as “the process of developing a software
system that processes personal data in such a way that its ability to meet specific legal
provisions is ascertained” (i.e. compliance of evolving security policies against formal
rules derived from legal provisions) [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ]. LCbD is however not limited to the
processing of personal data. The scope of this approach is potentially much wider,
extending to all compliance requirements. The point of departure of LCbD is that all legal
content is semi-automatically or automatically extracted from legal documents
—represented, processed, and eventually implemented. While the correctness of this
assumption can be questioned (see 6 below) LCbD is currently a “hot trend” in AI &amp; Law.
      </p>
      <p>
        Compliance by Design (CbD) emerged in the business field, to facilitate a better
understanding and modelling of the ongoing mechanisms of monitoring, evaluating,
and auditing.2 The objective to be compliant with the law was also fueled by the
enactment of Sarbanes-Oxley Act (2002), the economic crisis that followed, and by the
increasing regulatory and supervisory pressure on companies to professionalize and
document compliance management. Transparency and accountability became
important to maintain credibility and the corporate image in the market in relation to
business counterparts and consumers [
        <xref ref-type="bibr" rid="ref18">18</xref>
        ]. Thus, Compliance by Detection (CbDt) —which
entails a conformity check during and after the runtime stage to detect internal
violations— has been increasingly completed by CbD — which entails a conformity check
with regulations and laws in the runtime stage, designed in advance as a whole [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ].
2 “Over the last years, business compliance, i.e., the conformance of business procedures with
laws, regulations, standards, best practices, or similar requirements, has evolved from a
prerogative of lawyers and consulting companies to a major concern also in IT research and
software development. Given the increasing IT support in everyday business as well as the
repetitive and work-intensive nature of compliance controls and audits, this evolution can be seen
as a natural extension of current enterprise software, especially in light of the novel, technical
opportunities offered by the Service-Oriented Architecture (SOA). Yet, until only few years
ago, compliance management was not perceived as major concern in IT research.” [
        <xref ref-type="bibr" rid="ref17">17</xref>
        ]
Several business vocabularies, languages, and methodologies have been developed
so far [
        <xref ref-type="bibr" rid="ref19">19</xref>
        ]. Approaches and methodologies to identify, extract from legal documents,
model, and eventually implement and enforce the resulting rules have also been
proposed. These include Legal Goal-oriented Requirement language (LGR) based on URN
[
        <xref ref-type="bibr" rid="ref20">20</xref>
        ], REGOROUS [
        <xref ref-type="bibr" rid="ref21">21</xref>
        ], EUNOMOS [
        <xref ref-type="bibr" rid="ref22">22</xref>
        ], and NOMOS [
        <xref ref-type="bibr" rid="ref23">23</xref>
        ]. This is a common
endeavor, with several intersections, as the modelling of legal requirements; the
combination of linguistic techniques (NLP, NSP) with deontic non-standard logic; ambiguity
and vagueness of the legal language (interpretation); and the representation of legal
arguments, constitute shared problems that can be faced in common. The emergence of
semantic languages —LegalXML, LegalRuleML …— plays a major role in this
endeavor. Protections are especially (not exclusively) targeted in the financial, public
health, security, and consumer areas.
      </p>
      <p>These perspectives require some conditions: norms should be expressed at the
representation level in some (natural) language on specific written documents, valued as
“legal” (such as legal Acts or court decisions), or “regulatory” (such as standards or
best practices). What is legal (or “counts as legal”) must therefore be determined in
advance. Another condition concerns legal knowledge: it requires extensive work
carried out by experts to select, manipulate, interpret, transform legal terms and concepts,
and eventually decide the interpretation of “what counts as legal”.</p>
      <p>The essential role of inferential “intermediary concepts” in legal knowledge
representation —property, heritage, crime, privacy …—, has long been recognized in
deontic logics and in legal theory, because these concepts encapsulate the kind of semantic
properties that constitute pre-conditions to trigger normative effects, i.e. produce the
doctrine constructed by legal experts (legal doctrine). This raises several questions,
including: under which conditions do normative effects turn into “legal” binding effects;
whether legal knowledge can be completely modeled (particularly in relation to
common law, which is casuistic and inherently dynamic); and to what extent artificial
models reflect the law or rather legal knowledge (the law interpreted by experts through
legal doctrines).
6</p>
    </sec>
    <sec id="sec-5">
      <title>Legal Compliance through Design (LCtD)</title>
      <p>While we recognize the importance of these questions, they are not addressed in this
brief paper. Very likely what is called “legal knowledge” in democratic societies is the
collective result of an intertwined social process involving official and non-official
organisms (such as the Parliament and the media), political decision-making, legal
expertise, and the reception, approval, and eventual resilience of citizens. Our contention —
especially in policing and law enforcement agencies (LEA), settings, and contexts— is
that compliance with the law entails a set of dynamic conditions that cannot be
completely foreseen in advance, and thus, cannot be wholly modelled as a process, but only
as a result. In this situation, institutional design can supply the framework in which the
protections of the rule of law can be effectively implemented.</p>
      <p>
        Privacy provides a good example of this assertion [
        <xref ref-type="bibr" rid="ref24">24</xref>
        ]. The relevant legal
requirements, the passage from pre-conceptual to conceptual models, can be considered from
at least three perspectives: (i) direct PbD (where principles are embedded using
goaloriented languages or a formalism to detect privacy violations to prevent breaches, e.g.,
tracking logs, sensemaking technologies and data tethering [
        <xref ref-type="bibr" rid="ref15">15</xref>
        ] ], (ii) a combination
between tactics and strategy (where principles are nuanced to capture more constraints
to facilitate the lawyers’ work and produce “near-compliance”) [
        <xref ref-type="bibr" rid="ref25">25</xref>
        ] [
        <xref ref-type="bibr" rid="ref26">26</xref>
        ], and (iii) an
indirect strategy, a combination between PbD and institutional rules into a regulatory
comprehensive model, especially tailored for monitoring the information workflow on
the platform [
        <xref ref-type="bibr" rid="ref27">27</xref>
        ] [
        <xref ref-type="bibr" rid="ref28">28</xref>
        ] Previous regulatory projects on security platforms have shown
that auditing and monitoring OSINT processing and workflows require not only PbD
or CbD but the structured construction of hetero and self-regulatory institutions, i.e.
systems with internal and external controls able to contain functional roles within a
hybrid human-machine interface (Fig.2).
      </p>
      <p>A CbD approach that captures legal and regulatory constraints and expresses them
as requirements we call Compliance through Design [CtD]. CbD entails incorporating
(digitally as well as non-digitally) hard law, soft law (non-binding standards, protocols,
recommendations), policies (governance guidelines) and ethics (values, best practices)
into a dynamic institutional model, containing protections, rights and duties.
CbD is generally used to refer to compliance-sensitive design processes that embed
compliant processes or behaviors and facilitate compliance management. In a software
environment, it refers to a process of developing a software system that facilitates
implementation of a business process to meet specific compliance requirements. CtD on
the other hand, entails a semi-automated process embedding the interpretation of laws,
regulations, principles, policies, best practices, and ethical norms both, into the
workflow and into the institutional design. CtD is: (i) context-dependent, (ii) interactive, (iii)
interpretive, and (iv) complex, as norms and laws must be identified and interpreted in
advance to define the rules to be formulated and coded. CtD requires the description
and building of a prospective legal ecosystem defining roles, functions and
responsibilities for the key roleplayers.</p>
      <p>
        CtD is mainly focused on institutional building, as well as on interpretation. It is
worth noticing that plurality of competing legal interpretations is also respected and can
be modelled using ongoing legal CbD systems [
        <xref ref-type="bibr" rid="ref29">29</xref>
        ] or, for example, a combination of
reified deontic input/output logic and linguistic techniques (Natural Language
Processing, Natural Language Semantics) [
        <xref ref-type="bibr" rid="ref30">30</xref>
        ]. CbD has already been successfully
implemented in some public services to reduce costs of control and increase the transparency
and accountability of the Administration [
        <xref ref-type="bibr" rid="ref31">31</xref>
        ]. What is proposed here does not compete
with existing solutions. The idea is embedding LCbD into broader anchoring
institutions —i.e. regulatory bodies running socio-technical systems, platforms and
applications— to better frame, manage, and monitor the rights, duties and responsibilities of
stakeholders producing a specific and controllable legal ecosystem.
7
      </p>
    </sec>
    <sec id="sec-6">
      <title>Conclusion and future work</title>
      <p>Legal requirements discussed above do not exhaust social and legal conditions. We
will adopt a CtD strategy that will allow us to operationalize controls inside and outside
the platform. This will be done on several non-conflictive and non-intrusive uses cases
involving citizens, for example in relation to aspects of police and court history checks.
A National Police History Check is available in Australia.3 A prospective employer, a
public service or volunteer organizations, for example, can request it using the National
Police Checking Service Support System. The purposes of such enquiries can be quite
diverse: general employment, public administration, intelligence, etc. The service
provides sensitive information in many different types of cases (all kind of criminal
records). For non-NSLE purposes such information can only be requested with the consent
of the person concerned. This service, it is submitted, can be automatized, provided
that due protections are put in place. Understanding, selecting, describing and fleshing
out the legal conditions of possible scenarios for such a service is not an easy task, but
it will provide the benchmark to test the practical effectivity of our principles and the
correct functioning of the platform.4</p>
    </sec>
    <sec id="sec-7">
      <title>Acknowledgements</title>
      <p>
        This research was partially funded by the Data to Decisions Cooperative Research
Centre (D2D CRC), and Meta-Rule of Law (DER2016-78108-P, Spain). Views expressed
herein are however not necessarily representative of the views held by the funders.
4 We have used the term “linked democracy” to highlight that the implementation of rights and
democratic values on linked data ecosystems goes beyond the idea of being compliant with
rules [
        <xref ref-type="bibr" rid="ref32">32</xref>
        ]. LCbD or LCbD are only components of such a chain.
      </p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Edwards</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rashid</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rayson</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          <article-title>A systematic survey of online data mining technology intended for law enforcement</article-title>
          .
          <source>ACM Computing Surveys (CSUR)</source>
          ,
          <volume>48</volume>
          (
          <issue>1</issue>
          ),
          <volume>15</volume>
          (
          <year>2015</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Scheepers</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Whelan</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Burcher</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Nielsen</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          <article-title>Integrated Law Enforcement Project, Qualitative End User Evaluation</article-title>
          ,
          <source>Baseline Report. Technical Report, Data 2 Decisions CRC</source>
          . (
          <year>2017</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <given-names>Bennet</given-names>
            <surname>Moses</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            ;
            <surname>Chan</surname>
          </string-name>
          ,
          <string-name>
            <surname>J.</surname>
          </string-name>
          ; De Koker,
          <string-name>
            <surname>L.</surname>
          </string-name>
          et al.
          <source>Big Data Technology and National Security - Comparative International Perspectives on Strategy, Policy and Law Australia</source>
          .
          <article-title>Data to Decisions CRC (</article-title>
          <year>2016</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Marks</surname>
          </string-name>
          , Amber and Bowling, Ben and Keenan, Colman,
          <source>Automatic Justice? Technology, Crime and Social Control (October</source>
          <volume>19</volume>
          ,
          <year>2015</year>
          ). R.
          <string-name>
            <surname>Brownsword</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          <article-title>Scotford and</article-title>
          K. Yeung (eds),
          <source>The Oxford Handbook of the Law and Regulation of Technology, OUP, Queen Mary School of Law Legal Studies Research Paper No. 211/2015; TLI Think! Paper</source>
          <volume>01</volume>
          /
          <year>2015</year>
          . Available at SSRN: https://ssrn.com/abstract=2676154
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Mayer</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Stumptner</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Casanovas</surname>
          </string-name>
          , P. and
          <string-name>
            <surname>de Koker</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <year>2017</year>
          .
          <article-title>Towards a Linked Information Architecture for Integrated Law Enforcement</article-title>
          .
          <source>Linked Democracy: Artificial Intelligence for Democratic Innovation. LINKDEM@IJCAI</source>
          (
          <year>2017</year>
          ), pp.
          <fpage>28</fpage>
          -
          <lpage>37</lpage>
          , http://ceurws.org/Vol-1897.
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Casanovas</surname>
            ,
            <given-names>P</given-names>
          </string-name>
          ;
          <string-name>
            <surname>González-Conejero</surname>
            , J., de Koker,
            <given-names>L. Legal</given-names>
          </string-name>
          <article-title>Compliance by Design (LCbD) and through Design (LCtD): Preliminary Survey</article-title>
          .
          <source>TeReCom, Workshoon Technologies on Regulatory Compliance, 30th JURIX-2017</source>
          , Luxembourg,
          <volume>13</volume>
          Dec. [this volume]
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <given-names>SPECIAL</given-names>
            <surname>Scalable</surname>
          </string-name>
          <article-title>Policy-awarE Linked Data arChitecture for prIvacy, trAnsparency and compliance</article-title>
          .
          <source>Deliverable 1</source>
          .
          <article-title>3: Policy, transparency and compliance guidelines V1</article-title>
          . (
          <year>2016</year>
          ) http://www.specialprivacy.eu/.
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Stumptner</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mayer</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Grossmann</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          , Liu,
          <string-name>
            <given-names>J.</given-names>
            ,
            <surname>Li</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            ,
            <surname>Casanovas</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            ,
            <surname>De Koker</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            ,
            <surname>Mendelson</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            ,
            <surname>Watts</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            and
            <surname>Bainbridge</surname>
          </string-name>
          ,
          <string-name>
            <surname>B.</surname>
          </string-name>
          ,
          <year>2017</year>
          .
          <article-title>An Architecture for Establishing Legal Semantic Workflows in the Context of Integrated Law Enforcement</article-title>
          .
          <source>arXiv preprint arXiv:1708</source>
          .
          <fpage>06613</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Casanovas</surname>
            ,
            <given-names>P. Cyber</given-names>
          </string-name>
          <string-name>
            <surname>Warfare</surname>
            and
            <given-names>Organised</given-names>
          </string-name>
          <string-name>
            <surname>Crime</surname>
          </string-name>
          .
          <article-title>A Regulatory Model and Meta-Model for Open Source Intelligence (OSINT)</article-title>
          . In R. Taddeo and
          <string-name>
            <given-names>L.</given-names>
            <surname>Glorioso</surname>
          </string-name>
          ,
          <article-title>Ethics and Policies for Cyber Operations</article-title>
          , pp.
          <fpage>139</fpage>
          -
          <lpage>167</lpage>
          : Dordrecht: Springer International Publishing,
          <year>2017</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Pagallo</surname>
            ,
            <given-names>U.</given-names>
          </string-name>
          <article-title>Good onlife governance: On law, spontaneous orders, and design</article-title>
          . In L. Floridi (ed.)
          <source>The Onlife Manifesto. Being Human in an Hyperconnected Era</source>
          , pp.
          <fpage>161</fpage>
          -
          <lpage>177</lpage>
          . Springer Open (
          <year>2015</year>
          ). International Publishing.
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Noriega</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Verhagen</surname>
          </string-name>
          , H.,
          <string-name>
            <surname>d'Inverno</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Padget</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <year>2016</year>
          .
          <article-title>A manifesto for conscientious design of hybrid online social systems</article-title>
          . In Coordination, Organizations, Institutions, and
          <article-title>Norms in Agent Systems XII (pp</article-title>
          .
          <fpage>60</fpage>
          -
          <lpage>78</lpage>
          ). Springer, Cham.
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Dignum</surname>
            ,
            <given-names>V. Responsible</given-names>
          </string-name>
          <string-name>
            <surname>Autonomy</surname>
          </string-name>
          .
          <source>IJCAI August</source>
          <year>2017</year>
          , Melbourne. &lt;arXiv:
          <fpage>1706</fpage>
          .02513v1 [cs.
          <source>AI]&gt;.</source>
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Wright</surname>
          </string-name>
          , D., de Hert, P. (eds.).
          <source>Enforcing privacy. Regulatory, Legal and Technological Approaches</source>
          . Dordrecht: Springer (
          <year>2016</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14. Law and
          <string-name>
            <given-names>Policy</given-names>
            <surname>Program</surname>
          </string-name>
          .
          <article-title>Draft high level policy principles on the use of Big Data analytics by national security and law enforcement agencies</article-title>
          . Data to Decisions Cooperative Research Centre.
          <year>October 2017</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Cavoukian</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>Operationalizing</surname>
          </string-name>
          <article-title>Privacy by Design: A Guide to Implementing Strong Privacy Practices</article-title>
          . Information and
          <string-name>
            <given-names>Privacy</given-names>
            <surname>Commissioner</surname>
          </string-name>
          , Ontario, Canada,
          <year>December 2012</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <surname>Ranise</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Siswantoro</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          <string-name>
            <surname>Automated Legal Compliance</surname>
          </string-name>
          <article-title>Checking by Security Policy Analysis</article-title>
          . In: S. Tonetta et al. (Eds.)
          <article-title>SAFECOMP 2017 Workshops</article-title>
          , LNCS 10489, International Conference on Computer Safety, Reliability, and
          <string-name>
            <surname>Security</surname>
          </string-name>
          (pp.
          <fpage>361</fpage>
          -
          <lpage>372</lpage>
          ). Springer, Cham (
          <year>2017</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <surname>COMPAS EU</surname>
          </string-name>
          <article-title>Project 2009</article-title>
          .
          <string-name>
            <given-names>Final</given-names>
            <surname>Report</surname>
          </string-name>
          . Compliance-driven
          <string-name>
            <surname>Models</surname>
          </string-name>
          , Languages, and Architectures for Services &lt;https://cordis.europa.eu/fp7/ict/ssai/docs/finalreport-compas.pdf&gt;
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18.
          <string-name>
            <surname>Claydon</surname>
          </string-name>
          , J. Compliance/Legal Compliance. In: Idowu et al. (eds.),
          <source>Encyclopedia of Corporate Social Responsibility, DOI</source>
          <volume>10</volume>
          .1007/978-3-
          <fpage>642</fpage>
          -28036-8, #Springer-Verlag Berlin Heidelberg 2013, pp.
          <fpage>429</fpage>
          -
          <lpage>434</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19.
          <string-name>
            <surname>Ghanavati</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Amyot</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Peyton</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <year>2011</year>
          ,
          <string-name>
            <surname>August.</surname>
          </string-name>
          <article-title>A systematic review of goal-oriented requirements management frameworks for business process compliance</article-title>
          .
          <source>In Requirements Engineering and Law (RELAW)</source>
          ,
          <year>2011</year>
          Fourth International Workshop on (pp.
          <fpage>25</fpage>
          -
          <lpage>34</lpage>
          ). IEEE.
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          20.
          <string-name>
            <surname>Ghanavati</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Amyot</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Rifaut</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <year>2014</year>
          , June.
          <article-title>Legal goal-oriented requirement language (legal GRL) for modeling regulations</article-title>
          .
          <source>In Proceedings of the 6th international workshop on modeling in software engineering</source>
          (pp.
          <fpage>1</fpage>
          -
          <lpage>6</lpage>
          ). ACM.
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          21.
          <string-name>
            <surname>Sadiq</surname>
            , Shazia, and
            <given-names>Guido</given-names>
          </string-name>
          <string-name>
            <surname>Governatori</surname>
          </string-name>
          .
          <article-title>A methodological framework for aligning business processes and regulatory compliance</article-title>
          .
          <source>Handbook of business process management 2</source>
          (
          <year>2009</year>
          ):
          <fpage>159</fpage>
          -
          <lpage>176</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          22.
          <string-name>
            <surname>Boella</surname>
          </string-name>
          , Guido, Luigi Di Caro, Llio Humphreys, Livio Robaldo, Piercarlo Rossi, and Leendert van der Torre.
          <article-title>Eunomos, a legal document and knowledge management system for the Web to provide relevant, reliable and up-to-date information on the law</article-title>
          .
          <source>Artificial Intelligence and Law</source>
          <volume>24</volume>
          , no.
          <issue>3</issue>
          (
          <year>2016</year>
          ):
          <fpage>245</fpage>
          -
          <lpage>283</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          23.
          <string-name>
            <surname>Ingolfo</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jureta</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Siena</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Perini</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Susi</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <year>2014</year>
          , October. Nomos 3:
          <article-title>Legal compliance of roles and requirements</article-title>
          .
          <source>In International Conference on Conceptual Modeling</source>
          (pp.
          <fpage>275</fpage>
          -
          <lpage>288</lpage>
          ). Springer, Cham.
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          24.
          <string-name>
            <surname>Koops</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Leenes</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          (
          <year>2014</year>
          ).
          <article-title>Privacy regulation cannot be hardcoded. A critical comment on the 'privacy by design' provision in data-protection Law</article-title>
          ,
          <source>International Review of Law, Computers &amp; Technology</source>
          , (
          <year>2014</year>
          )
          <volume>28</volume>
          ,
          <issue>2</issue>
          :
          <fpage>159</fpage>
          -
          <lpage>171</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          25.
          <string-name>
            <surname>Colesky</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Ghanavati</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          <article-title>Privacy Shielding by Design-A Strategies Case for NearCompliance</article-title>
          . In Requirements Engineering Conference Workshops (REW), IEEE International (pp.
          <fpage>271</fpage>
          -
          <lpage>275</lpage>
          ). IEEE (
          <year>2016</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref26">
        <mixed-citation>
          26.
          <string-name>
            <surname>Colesky</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hoepman</surname>
            ,
            <given-names>J. H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hillen</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          <article-title>A Critical Analysis of Privacy Design Strategies</article-title>
          ,
          <source>IEEE Symposium on Security and Privacy Workshops</source>
          ,
          <fpage>33</fpage>
          -
          <lpage>40</lpage>
          . DOI 10.1109/SPW.
          <year>2016</year>
          .23
        </mixed-citation>
      </ref>
      <ref id="ref27">
        <mixed-citation>
          27.
          <string-name>
            <surname>Casanovas</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Arraiza</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>Melero</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ;
          <string-name>
            <surname>González-Conejero</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ; Molcho,
          <string-name>
            <given-names>G.; M.</given-names>
            <surname>Cuadros</surname>
          </string-name>
          ,
          <string-name>
            <surname>M.</surname>
          </string-name>
          <article-title>Fighting Organized Crime Through Open Source Intelligence: Regulatory Strategies of the CAPER Project</article-title>
          .
          <article-title>Legal Knowledge and Information Systems</article-title>
          . JURIX 2014. ed. R. Hoekstra,
          <source>Foundations on Artificial Intelligence núm. 271</source>
          , Amsterdam: IOS Press, p.
          <fpage>189</fpage>
          -
          <lpage>199</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref28">
        <mixed-citation>
          28.
          <string-name>
            <surname>González-Conejero</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Figueroa</surname>
            ,
            <given-names>R.V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Muñoz-Gomez</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Teodoro</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <year>2014</year>
          .
          <article-title>Organized crime structure modelling for European Law Enforcement Agencies interoperability through ontologies. In AI approaches to the complexity of legal systems</article-title>
          (pp.
          <fpage>217</fpage>
          -
          <lpage>231</lpage>
          ). Springer, Berlin, Heidelberg.
        </mixed-citation>
      </ref>
      <ref id="ref29">
        <mixed-citation>
          29.
          <string-name>
            <surname>Ghanavati</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Hulstijn</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          <article-title>Impact of legal interpretation on business process compliance</article-title>
          .
          <source>In Proceedings of the First International Workshop on TEchnical and LEgal aspects of data pRIvacy</source>
          (pp.
          <fpage>26</fpage>
          -
          <lpage>31</lpage>
          ). IEEE Press (
          <year>2015</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref30">
        <mixed-citation>
          30.
          <string-name>
            <surname>Bartolini</surname>
            , Cesare, Andra Giurgiu, Gabriele Lenzini, and
            <given-names>Livio</given-names>
          </string-name>
          <string-name>
            <surname>Robaldo</surname>
          </string-name>
          .
          <article-title>A Framework to Reason about the Legal Compliance of Security Standards</article-title>
          .
          <source>In Proceedings of the Tenth International Workshop on Juris-informatics (JURISIN)</source>
          .
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref31">
        <mixed-citation>
          31.
          <string-name>
            <surname>Christiaanse</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Hulstijn</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <year>2012</year>
          , June.
          <article-title>Control automation to reduce costs of control</article-title>
          .
          <source>In International Conference on Advanced Information Systems Engineering</source>
          (pp.
          <fpage>322</fpage>
          -
          <lpage>336</lpage>
          ). Springer, Berlin, Heidelberg.
        </mixed-citation>
      </ref>
      <ref id="ref32">
        <mixed-citation>
          32.
          <string-name>
            <surname>Poblet</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Casanovas</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Plaza</surname>
          </string-name>
          , E.
          <source>Proceedings of the Workshop on Linked Democracy: Artificial Intelligence for Democratic Innovation, co-located with the 26th International Joint Conference on Artificial Intelligence (IJCAI</source>
          <year>2017</year>
          ). Melbourne, Australia,
          <year>August 19</year>
          ,
          <year>2017</year>
          . http://ceur-ws.
          <source>org/</source>
          Vol-1897/.
        </mixed-citation>
      </ref>
      <ref id="ref33">
        <mixed-citation>
          33.
          <string-name>
            <surname>Sadiq</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Governatori</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <year>2015</year>
          .
          <article-title>Managing regulatory compliance in business processes</article-title>
          .
          <source>In Handbook on Business Process Management</source>
          <volume>2</volume>
          (pp.
          <fpage>265</fpage>
          -
          <lpage>288</lpage>
          ). Springer Berlin Heidelberg.
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>