<!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>Towards a Linked Information Architecture for Integrated Law Enforcement</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Wolfgang Mayer</string-name>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Markus Stumptner</string-name>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Pompeu Casanovas</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Louis de Koker</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>La Trobe Law School, La Trobe University</institution>
          ,
          <addr-line>Melbourne</addr-line>
          ,
          <country country="AU">Australia</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>UAB Institute of Law and Technology, Universitat Autònoma de Barcelona</institution>
          ,
          <country country="ES">Spain</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>University of South Australia</institution>
          ,
          <addr-line>Adelaide</addr-line>
          ,
          <country country="AU">Australia</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Law enforcement agencies are facing an ever-increasing flood of data to be acquired, stored, assessed and used. Automation and advanced data analysis capabilities are required to supersede traditional manual work processes and legacy information silos by automatically acquiring information from a range of sources, analyzing it in the context of on-going investigations, and linking it to other pieces of knowledge pertaining to the investigation. This paper outlines a modular architecture for management of linked data in the law enforcement domain and discusses legal and policy issues related to workflows and information sharing in this context.</p>
      </abstract>
      <kwd-group>
        <kwd>law enforcement</kwd>
        <kwd>investigation management</kwd>
        <kwd>linked data</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        Investigations conducted by law enforcement agencies (LEAs) are increasingly reliant
on effective collection and analysis of information that may be obtained from a
variety of sources, internal and external to the organization [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. 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.
      </p>
      <p>Information collected within the organization include information about
individuals, organizations, objects and entities of interest, witness statements, evidence
obtained from crime scenes, communications intercepts and the results of forensic
analysis. This information may be complemented and integrated with data such as
financial transactions, travel and immigration records, and criminal history that are
obtained from external sources. In addition, documentation about the investigation
process and data provenance must be maintained in order to establish that evidence
submitted to court had been obtained within the law and policies relevant to the
investigation.</p>
      <p>
        Accessing data as well as linking and integrating them in a correct and consistent
way is a pressing challenge in particular when underlying data structures and access
methods change over time. Lack of interoperability between information systems
within and across organizations remains one of the prevalent concerns of investigators
[
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. Investigations are delayed by poor information management practices that result
in information being unavailable or not being available in a timely manner, poor
information quality, and cumbersome manual approval and information retrieval
procedures.
      </p>
      <p>The project Integrated Law Enforcement (ILE), conducted by the Data to
Decisions Cooperative Research Centre (D2D CRC)1, 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 platform. The project has been
developing technological solutions for information management, linking, and analysis
that are tailored to the needs of investigators. An extensible software architecture for
searching, linking, and integration of data sources forms one of the corner stones of
the project. The platform will eventually include analytic services that can be invoked
by investigators. The data management architecture is complemented with a state of
the art user-facing portal and an analysis of legal aspects pertaining to workflows and
information sharing.</p>
      <p>
        Effective linking, integration, and analysis of data requires breaking down data
“silos” and opening up legacy systems within organizations to make information
accessible, establishing procedures and technical infrastructure to effectively and timely
share information across organizational boundaries, creating data standards to
facilitate interpretation and analysis of the body of collected data, and automating, where
possible, analysis and semantic enrichment of data [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ].
      </p>
      <p>
        Data integration in this context raises serious legal compliance and good
governance challenges. Compliance with existing laws and principles is a pre-condition of
the whole process [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. Transparency and privacy should be preserved to foster trust
between citizens and national security and law enforcement agencies. A 2015
literature review on online data mining technology intended for law enforcement broadly
singled out eight main problems (crimes, investigative requirements) in 2015 [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ].
Separately, some criminologists warned against the profound effect of automated data
collection on the traditional criminal justice system, as it could undercut the due
process safeguards built into the traditional criminal justice model [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. It is our
contention that this technological modelling should be performed under the protections of
the rule of law.
      </p>
      <p>
        In this paper, we present the overall system architecture for information sharing
and outline the related legal issues pertaining to workflows and information exchange
in the context of policing investigations. Our work has resulted in a data access
framework for law enforcement which provides a comprehensive data and meta-data
model including provenance, security, confidence, links and timeline information
related to entities and links. This meta-data layer spans a Knowledge Graph-like view
[
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] of information pertaining to entities relevant to investigations. The resulting data
and meta-data model serves as the foundation for information use, governance, data
quality protocols, analytic pipelines and exploration of search results.
      </p>
    </sec>
    <sec id="sec-2">
      <title>1 http://www.d2dcrc.com.au/</title>
      <sec id="sec-2-1">
        <title>Information Sharing in Law Enforcement</title>
        <p>
          Timely information sharing domain is crucial for the success of many investigations
in the law enforcement domain. Unfortunately, many investigations are stalled by one
or more of a number of impediments related to effectively sharing information among
investigators and organizations [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ]. In the following we highlight a selection of issues
relevant in context of linked information access.
        </p>
        <p>Among the technical impediments, internal information silos and cumbersome
information access procedures are common. Investigators routinely enter the same
queries across a multitude of legacy information systems and manually collate and
integrate the results. Lack of information access mechanisms for investigators in the field
hamper the timely acquisition of information in electronic form and information may
not be updated in timely manner. In absence of automated alerts, investigators may be
unaware that new information relevant to a case has become available unless they
manually issue queries periodically or rely on informal personal connections to
receive notifications. As a result, relevant information may be missed even though it
had been available in an information system. Data quality varies greatly as data
quality standards are often not enforced and instead left to the individual user.</p>
        <p>Workflows and policies may impact upon investigations. Where approvals for
actions are required, for example expenditure approval for call records requests,
antiquated policies and work processes may still rely on paper forms and manual approval
which result in excessive delays, in particular if approvals are sought outside of
normal office hours. Here, automation and electronic means of requesting and obtaining
warrants and approvals would streamline the investigation process.</p>
        <p>
          Legal issues relate to restrictions on 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. Similarly, agencies are generally subject to
restrictions on what information they can share with other agencies [
          <xref ref-type="bibr" rid="ref2">2</xref>
          ]. Even where
information sharing may be legally permitted, many organizations, concerned about
the implications of breaching the law, are prone to adopt prudential attitudes and
policies that perhaps may unnecessarily restrict what can be shared. Information security
and access control are challenging issues when multiple systems and organizations are
involved. It is challenging to guarantee comprehensive and secure access to a large
number of users accessing a multitude of information systems across organizational
boundaries. Moreover, there is interaction between analytics and security attributes as
new information derived from automated analytic processes must be classified using
appropriate security policies to avoid inadvertently disclosing otherwise inaccessible
information. Determining appropriate classification and access restrictions can be
challenging in organizations.
3
        </p>
      </sec>
      <sec id="sec-2-2">
        <title>System Architecture</title>
        <p>
          An open architecture for data/meta-data management and analytic processes has been
defined. It translates the best practices from Enterprise Application Integration to the
“Big Data” analytic pipelines [
          <xref ref-type="bibr" rid="ref6">6</xref>
          ]. Our work addresses aspects related to data and
meta-data modelling and storage, modelling and execution of analytic processes, and
efficient execution of analytic processes across multiple analytic tools and data
sources. Central to this architecture is a method for effective semi-interactive entity
linking and querying of linked data (akin to automatically generated linked ontologies
such as YAGO [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ]). The project intends to realize a comprehensive data
management framework that relies on a well-defined share data and meta-data model
supported by vendor-agnostic interfaces for data access and execution of processes
comprising analytic services offered by different tools.
        </p>
        <p>The overall architecture of the ILE platform is shown in Figure 1. A federated
architectural model has been adopted, where one or more instances of the ILE platform
can be deployed and access a number of external data sources. Each instance may
provide query and analytic services to the front-end applications and can obtain data
from other instances and external sources on demand. This approach is necessary as
data in external sources is usually controlled by external organizations and may
change at any time. Moreover, organizational policies in this context rarely support
traditional Extract-Transform-Load ingestion processes across organizational
boundaries.</p>
        <p>The ILE platform provides programmatic interfaces (APIs) to front-end
applications to access data and invoke analytic services. The interfaces expose the platform’s
services using a uniform data format and communication protocol. The APIs can be
accessed from a desktop front-end where investigators can search and enter
information as well as invoke services. Mobile applications for investigators may be
developed in future versions of the platform.</p>
        <p>Each instance maintains a Curated Linked Data Store, that is, a set of databases
that collectively implement a knowledge-graph like structure comprising entities and
their links and meta-data. This curated data store holds facts and meta-data about
entities and their links whose veracity has been confirmed. This data store is used to
infer the results for queries and to synthesize requests to external sources and other
instances if further information is required. As such, the linked data store implements
a directory of entities and links enriched with appropriate meta-data and source
information such that detailed information can be obtained from authoritative sources
that may be external to the system. This approach is needed as data in the law
enforcement domain is dispersed among a number of systems owned and operated by
different agencies. As such no centrally controlled database can feasibly be put in
place in the foreseeable future.</p>
        <p>The information contained in the linked data store is governed by an Ontology that
defines the entity types, link types, and associated meta-data that is available among
the collective platform. The ontology acts as a reference for knowledge
management/organization and aids in the integration of information stemming from external
sources, where it acts as a reference for linking and translating information into a
form suitable for the knowledge hub. The ontology has been designed specifically for
the law enforcement domain and includes detailed provenance information and
metadata related to information access restrictions. It is explicitly represented and can be
queried. All information within the ILE platform is represented in the ontology in
order to facilitate entity linking and analysis.</p>
        <p>
          The ILE ontology is too large to reproduce it in full in this paper; it comprises 19
high-level domain concepts which are further refined into a total of ~140 concepts
and a taxonomy of ~400 specialized relationship types. It has been documented in [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ].
The ontology conceptualizes the domain on three levels: meta-level where concept
types are captured, the type level, where domain concepts are represented in terms of
types, and the instance level, where instance-level data is represented and linked. For
example, the meta-level defines EntityType, RelationshipType, and
MetaAttributeType. Their instances on the level below represent persons, organizations, (and more
broadly a hierarchy of object types), concrete domain relationships that may be
established between objects (for example that a Person works for an Organization), and
meta-data attributes related to access control, provenance, and temporal validity.
        </p>
        <p>
          These domain concepts are closely aligned with the draft National Police
Information Model (NPIM), complemented with relevant aspects drawn from the NIEM
standard2 and concepts related to case management. The provenance model is an
extension of PROV-O [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ]. The instances of the domain concepts form the objects
comprising the Knowledge Graph on the lowest layer in the ontology. The aforementioned
concepts are complemented with classes and objects representing data sources linked
to the domain information stored therein as well as schema mapping information
required to translate between the external source and the ontology model adopted within
the federated architecture.
        </p>
        <p>This multi-level modelling method has been adopted to provide a modular and
extensible knowledge representation architecture. The semantic technologies that
underpin our platform facilitate incremental addition of elements to the ontology, and
phasing out of obsolete concepts can be implemented via meta-data annotations
interpreted by the underlying information systems. Changes in information representation
received from external parties can be addressed by ontology matching techniques and
machine learning methods for information extraction and linking. Profound changes
in the information acquisition pipelines however would require changes to the
underlying information system. Our modular architecture has been designed to
accommodate such changes.</p>
        <p>
          Information from external sources is sought based on a catalog of data sources that
are available to the system, each with a corresponding adapter that communicates
with the external systems and rewrites the information and meta-data into the
ontology used within the ILE platform [
          <xref ref-type="bibr" rid="ref11">11</xref>
          ]. Our platform spans several sources, including
an entity database (Person, Objects, Location, Event, and Relations), a case
management system, and a repository of unstructured documents.
        </p>
        <p>
          Information received from external systems is passed through an ingestion and
enrichment pipeline where entities are extracted [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ], enriched with meta-data
(provenance and access restrictions) and linked to the knowledge graph in the linked data
store.
        </p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>2 https://www.niem.gov/</title>
      <p>
        Analytic services include entity extraction from unstructured text [
        <xref ref-type="bibr" rid="ref14">14</xref>
        ], entity
linking, similarity calculation and ranking. Services provided by commercial tools, such
as network analysis and entity liking/resolution solutions, can be integrated in the
modular architecture.
      </p>
      <p>Automation services will provide workflow orchestration and alert notices if new
information relevant to a case becomes available. Workflow services will facilitate
the enactment of work processes such as acquiring authorization and warrants. The
automation services component is pending implementation.</p>
      <p>
        Cross-cutting technical concerns, including access control and user management,
logging, monitoring and other deployment facilities, have been omitted in this
architecture view. Our implementation builds on open source big data technologies
(Hadoop/Spark, polyglot persistence, message queues, and RESTful interfaces). The
technical building blocks are outlined in [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ].
      </p>
      <p>Fig. 1 draws the overall architecture and plot the direction of legal workflow
processing.</p>
      <sec id="sec-3-1">
        <title>Legal and governance issues</title>
        <p>
          A key concern is the incorporation of legal risk management and compliance
constraints into the workflow execution to ensure observance of and compliance with the
applicable legal rules, for example agency and privacy rules as well as internal agency
policies and procedures. Natural Language parsing can be used to elicit event
specifications that could then be translated to business rules in an executable formal
language and issued to an event processor in the knowledge hub [
          <xref ref-type="bibr" rid="ref16">16</xref>
          ]. These rules would
be used to check and guarantee conformance of analytic processes/workflows and
data usage. [
          <xref ref-type="bibr" rid="ref16">16</xref>
          ] provides support for extracting data from a variety of sources
(relational databases, CSV files, JSON, and XML), for modeling it according to a
vocabulary of the user’s choice and for integrating multiple data sources. This process
deserves a closer attention, because (i) it implies LEAs cooperation, and (ii) must be
compliant with Australian law.3
        </p>
        <p>
          The D2D CRC’s law and policy team outlined for discussion a set of high level
principles that may guide the development of an appropriate framework: (i) engender
public confidence in government use of data and analytic tools, (ii) develop principles
for data governance in National Security Law Enforcement (NSLE) agencies; (iii)
employ clear and consistent principles in developing legal frameworks, (iv) improve
processes to enhance effective use of data within NSLE agencies, (v) ensure the
continued effectiveness of the oversight regime as technologies and NSLE agency
practices evolve, (v) disentangle elements of technological change associated with ‘Big
Data’, (vi) maintain data integrity and security in a high volume environment, (vii)
ensure fair and appropriate use of data analytics, (viii) use appropriate systems for
data matching, data integration or federated access that takes account of benefits and
risks; (ix) ensure efficient, appropriate, and regulated sharing of specific data for
NSLE purposes [
          <xref ref-type="bibr" rid="ref17">17</xref>
          ].
        </p>
        <p>
          In a recent survey we carried out on the state of the art of Compliance by Design
(CbD) [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ], we found that the passage from Business to Legal CbD mainly follows a
semantic path, in which Natural Language Processing (NLP), non-monotonic
defeasible logic and inferential reasoning are combined with enriched annotated legal
sources (e.g. described according linked data standards). This is aligned with recent
developments in e-business4 [
          <xref ref-type="bibr" rid="ref26">26</xref>
          ] and e-government [
          <xref ref-type="bibr" rid="ref27">27</xref>
          ]. Architectures are deemed
3 We consider primarily investigations conducted by Australian law enforcement agencies,
where compliance with Australian laws governing these investigations and subsequent legal
proceedings is paramount.
4 ISO/IEC 42010:2007 defines "architecture" as: "The fundamental organization of a system,
embodied in its components, their relationships to each other and the environment, and the
principles governing its design and evolution". It has been fleshed out by [
          <xref ref-type="bibr" rid="ref26">26</xref>
          ], and [
          <xref ref-type="bibr" rid="ref27">27</xref>
          ] [
          <xref ref-type="bibr" rid="ref28">28</xref>
          ]
for the e-government architecture. See esp. ADM Architecture Requirements Management,
and the Architecture Compliance steps defined at TOGAF 9.1, Part VII: Architecture
Capability Framework Architecture Compliance.
http://pubs.opengroup.org/architecture/togaf9doc/arch/
to be understandable, robust, complete, consistent and stable. [
          <xref ref-type="bibr" rid="ref28">28</xref>
          ] has proposed a
comprehensive approach to develop interoperable European e-government services
adapting and extending the existing enterprise architecture requirements. The
investigation shows that at least half —i.e. not all— of the 30 requirements identified are
adequately addressed by enterprise architectures (EA).5 It concludes with ten
interoperability challenges that should be taken into account and addressed when providing
pan-European e-government services (PEGS) across Member State borders. Quoting
at length: (i) critical success factors should be identified, (ii) an EA framework for
PEGS should be built upon widely accepted principles and strategies, (iii) it should
comprise architecture design principles and guidelines to reason about alternative
design strategies, (iv) in order to facilitate stakeholder management, it should refer to
abstract stakeholder classes and roles in interoperability projects and determine
drivers for their engagement, (v) the creation of contents can be improved through a
methodology that supports the capturing of requirements from business-driven needs,
policy implementation processes and other strategic aspects in order to establish
common path and to increase the acceptance of architecture outputs among
stakeholders (vi) another methodology should describe how to define interoperability
specifications on semantic and organizational level, which can be used as a basis for
collaboration agreements, (vii) a detailed design of each architecture should identify relevant
model fragments and should be based on a commonly agreed architecture description
language, (viii) there are missing guidelines and methods that describe how to
transition and to govern architectures in multi-stakeholder environments, (ix) several
independent implementations of PEGS have to be coordinated, extended and sustained
over time (e.g. it should integrate appropriate assessment methodologies to measure
specifications and the compliance of solutions with the underlying collaboration
agreements, (x) other assessment methodologies can help to determine the level of
business standardizations in a domain and to appraise the maturity of market solutions
in order to detect appropriate ways forward.
        </p>
        <p>
          This is a valuable programme. Likewise, we have also devised one close to it with
the Australian framework in mind. However, as [
          <xref ref-type="bibr" rid="ref28">28</xref>
          ] underline as well, business
languages do not completely match all governance and security requirements.
Interoperability frameworks do not enable an anticipatory management [29].
        </p>
        <p>
          Legal compliance is complex, even in relation to national laws where the
jurisdiction concerned is a unified, non-federal national state. There are several
methodologies and languages to represent norms using formal rules —e.g. Regorous and
LegalRuleML [31]—, but there are not fully automated ways to carry out such a task. Legal
norms must be interpreted in particular fields according to the specific domains to
which they apply, anticipating the possible risks and unintended side effects. In
addition, ethical principles can nuance or mould this interpretation according to different
jurisdictions — e.g. Fair Information Practices in USA, or Data Protection Principles
5 The 30 requirements obtained in the survey of the literature have been structured into six
categories [
          <xref ref-type="bibr" rid="ref28">28</xref>
          ]: project management (PM), stakeholder management (ST), service
development (SD), interoperability layers and architecture viewpoints (LV), building blocks (BB),
and collaboration agreements (CA).
similar to the brand new General Data Protection Regulation in Europe. Similarly,
information governance rules and policies differ between private corporations and
state agencies.
        </p>
        <p>
          At a more general level, legal scholars have noticed that the protection of relative
civil rights such as privacy does not necessarily entail tradeoffs [
          <xref ref-type="bibr" rid="ref21">21</xref>
          ]6. Nevertheless, as
we have already suggested, there are many ways to comply with rule of law
requirements, depending on the plurality of legal constraints and constitutional
specifications. Apparently, protections for civil rights are not as clear —and arguably as
strong— in Australia as in the EU, where the police and their criminal intelligence
functions operate subject to well-developed data protection and privacy norms. In
contrast to a more comprehensive, integrated EU approach, it could be argued that
public transparency and operational secrecy are, for example, not as finely balanced
under current Australian law [
          <xref ref-type="bibr" rid="ref19">19</xref>
          ]. Contrary to European provisions, the 2017
Australian Productivity Commission Inquiry Report on Data Availability and Use, excludes
national security data [
          <xref ref-type="bibr" rid="ref20">20</xref>
          ]. As asserted by the Report, governments use data to
monitor and investigate compliance and implement enforcement actions. They retrieve,
extract and analyse information from publicly available sources (Open Source
Intelligence, OSINT) in a way that can also be regulated [
          <xref ref-type="bibr" rid="ref22">22</xref>
          ].
        </p>
        <p>Having a closer look, problems about fragmentation and interoperability are
analogous in both Australia and Europe. Different as they might be, the post-facto
investigations about the Abdelsam brothers in the Bataclan crisis in Paris [30] and the
inquest into the deaths arising from the Lindt Café siege in Sydney7 have come to
similar conclusions. Cooperation among state departments and agencies; and between
Law Enforcement Agencies (LEA), can and should be improved.</p>
        <p>These conclusions are not limited solely to security issues but can be also extended
to the coordination of public administration and the legal system in policy domains.
For instance, in many situations, problems might arise “because of gaps of
information flow between the family law system, the family violence system, and the child
protection system: in many circumstances, important information is not being shared
among courts and agencies and this is having a negative impact on victims, impeding
the ‘seamlessness’ of the legal and service responses to the family violence”.8</p>
        <p>
          Disparity is produced as well across all Australian jurisdictions. At a federal level
the Privacy Act 1988, for example, regulates the handling of personal information by
the federal government and the private sector. The Act does not extend to state
governments. Some states have their own comprehensive frameworks. In Victoria, for
example, the Privacy and Data Protection Act 2014 (Vic) contains the following
Information Privacy Principles (IPPs) which apply to all information held by the
Victorian public sector (including the police and a contracted service provider): (i) Open
and transparent management of personal information, (ii) Sensitive information, (iii)
6 International human rights law distinguishes between absolute and relative rights. Absolute
rights —such as freedom from slavery, torture and servitude— cannot be suspended, restricted,
or limited for any reason. Non-absolute or relative rights are those which stand in the various
private and legal relations, and can be discussed, re-defined or qualified.
7 http://www.lindtinquest.justice.nsw.gov.au/
8 Australian Law Reform Commission (2010), as quoted in [
          <xref ref-type="bibr" rid="ref20">20</xref>
          ].
        </p>
        <p>Right to anonymity/pseudonymity, (iv) Notification of collection, (v) Purpose test for
use / disclosure, (vi) Direct marketing restrictions, (vii) Cross border disclosure, (viii)
Government-related or unique identifiers, (ix) Data quality, (x) Data security, (xi)
Access and correction. South Australia, on the other hand, only has an administrative
instruction requiring government agencies to comply with a set of Information
Privacy Principles while Western Australia does not currently have a comprehensive
legislative privacy regime.</p>
        <p>
          Australia has a comprehensive oversight regime in relation to national security and
law enforcement agencies. Different bodies have however oversight over different
agencies or have oversight over closely-defined aspects of a range of agencies. The
fragmented nature of the oversight framework in Australia “will be challenged by an
environment where NSLE agencies collaborate more closely in a Big Data
framework” [
          <xref ref-type="bibr" rid="ref19">19</xref>
          ]. But to reach this milestone, it is our contention that the information
integration process that takes place on the platform through reusable ontologies and
vocabularies requires a broader regulatory framework. To overcome the patchwork of
disparate and sometimes contradictory legal constraints, we will work within an
intermediate implementation level, setting what can be called an “anchoring institution”
between the semantic tools of the platform and LEAs (end-users).
        </p>
        <p>
          This set of intermediate conceptual rules constitute a semantic web regulatory
model (SWRM), i.e. a specific cluster of guidelines to regulate the information flow,
establishing a system of check and balances between LEA’s investigative powers and
their use of semantic technology [
          <xref ref-type="bibr" rid="ref22">22</xref>
          ]. This is an indirect strategy for Compliance by
Design (CbD) purposes, in which police officers might set forth internal and external
controls, and adopt a conceptual scheme to implement privacy and security principles
including ethics as a main component, i.e. at the intermediate level of linked
democracy [
          <xref ref-type="bibr" rid="ref23">23</xref>
          ]. To encompass both behavioural and informational trends, we use the
expression ‘Compliance through Design’ [CtD] [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ] . This means that the increasing of
pressure on human compliance management resources in the security area can be
taken into account [
          <xref ref-type="bibr" rid="ref25">25</xref>
          ]. The crucial point is the coexistence of both artificial and
human decision-making and information processes.
        </p>
        <p>
          Likewise, ‘linked democracy’ can be defined as “a meso-level approach to both
online and offline innovations that elucidates the interactions between people,
technology, and data in particular settings, providing a framework of analysis to
understand the emerging properties (and tensions) of these interactions” [
          <xref ref-type="bibr" rid="ref24">24</xref>
          ]. Therefore,
public principles such as transparency, accountability and security could be graduated
and connected within particular investigations according to their weight at their
specific implementation level. This entails the emergence of different notions, degrees
and values of legal compliance, enhancing their semantic side, and outstripping the
traditional obstacles of operating from separate information silos.
        </p>
        <p>
          It is worth noticing that from this pragmatic approach, interoperability does not
only mean ‘semantic interoperability’ —the creation of a common meaning for
information ex- change across computational systems— but systemic interoperability. That
is, the ability of complex systems to interact, share, and exchange information. It
focuses onto the coordination of practices, including human behavior, organizational
structures, tools, languages, and techniques [
          <xref ref-type="bibr" rid="ref23">23</xref>
          ]. Establishing such a model,
translating legal and systemic conditions to institutional and computational constraints and
requirements, is the next step.
        </p>
        <p>Acknowledgements
This research was partially funded by the Data to Decisions Cooperative Research
Centre (D2D CRC), with participation of the Spanish Project DER2016-78108-P.
Views expressed herein are however not necessarily representative of the views held
by the funders.
29. Mondorf, A. and Wimmer, M., Contextual Components of an Enterprise Architecture
Framework for Pan-European eGovernment Services. In Proceedings of the 50th Hawaii
International Conference on System Sciences, HICSS, 2017, pp. 2933-2942.
30. Bureš, O., 2016. Intelligence sharing and the fight against terrorism in the EU: lessons
learned from Europol. European View, 15(1): 57-66.
31. Sadiq, S., Governatori. G. A methodological framework for aligning business processes
and regulatory compliance. In: Jan van Brocke and Michael Rosemann, editors, Handbook
of Business Process Management, pp. 159-176, Springer, 2010.</p>
      </sec>
    </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>
          ) (
          <year>2015</year>
          ):
          <fpage>1</fpage>
          -
          <lpage>56</lpage>
          .
        </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>Nielsen</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Burcher</surname>
            ,
            <given-names>M.</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>
            <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>Grossmann</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <article-title>Jordan A. Semantic Interoperability in the Oil and Gas Industry: A Challenging Testbed for Semantic Technologies</article-title>
          .
          <source>In AAAI Fall Symposium on Semantics for Big Data</source>
          , Arlington, Virginia,
          <year>November 2013</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4. Law and
          <string-name>
            <given-names>Policy</given-names>
            <surname>Program</surname>
          </string-name>
          .
          <article-title>Big Data Technology and National Security - Comparative International Perspectives on Strategy, Policy and Law: Australia (Data to Decisions CRC</article-title>
          ),
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Marks</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bowling</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Keenan</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          <article-title>Automatic Justice? Technology, Crime and Social Control</article-title>
          . In: 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</source>
          , Oxford University Press, pp.
          <fpage>705</fpage>
          -
          <lpage>730</lpage>
          ,
          <year>2017</year>
          . Available at SSRN: https://ssrn.com/abstract=2676154 [2015]
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          <article-title>6. Data to Decisions CRC Big Data Reference Architecture</article-title>
          , vol.
          <volume>1</volume>
          -
          <issue>4</issue>
          ,
          <string-name>
            <given-names>Technical</given-names>
            <surname>Report</surname>
          </string-name>
          , Data to Decisions CRC,
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Heath</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bizer</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          <article-title>Linked Data: Evolving the Web into a Global Data Space</article-title>
          .
          <source>Synthesis Lectures on the Semantic Web: Theory and Technology</source>
          , Morgan &amp; Claypool Publishers,
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Grossmann</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kashefi</surname>
            ,
            <given-names>A.K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Feng</surname>
            ,
            <given-names>Z.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Li</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kwashie</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Liu</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <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>Integrated Law Enforcement Platform Federated Data Model</surname>
          </string-name>
          ,
          <source>Technical Report, Data 2 Decision CRC</source>
          ,
          <year>2017</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Lebo</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sahoo</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>McGuinness</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Belhajjame</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cheney</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Corsar</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Garijo</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Soiland-Reyes</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zednik</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Zhao</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          <article-title>Prov-o: The PROV ontology</article-title>
          .
          <source>W3C recommendation</source>
          ,
          <year>2013</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <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>
          ,
          <string-name>
            <surname>Jiu</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Li</surname>
            ,
            <given-names>W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>De Koker</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mendelson</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bainbridge</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Watts</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Casanovas</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          <article-title>An Architecture for Establishing Legal Semantic Workflows in the Context of Integrated Law Enforcement, Workshop on Legal Knowledge and the Semantic Web (LK&amp;SW-</article-title>
          <year>2016</year>
          ),
          <source>International Conference on Knowledge Engineering and Knowledge Management</source>
          , Bologna, Italy, Nov. LNAI,
          <year>2017</year>
          (forthcoming).
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Bellahsene</surname>
            ,
            <given-names>Z.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bonifati</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rahm</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          <article-title>Schema Matching and Mapping</article-title>
          .
          <source>Data-Centric Systems and Applications</source>
          , Berlin, Heidelberg: Springer,
          <year>2011</year>
          . DOI:
          <volume>10</volume>
          .1007/978-3-
          <fpage>642</fpage>
          - 16518-4.
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Casanovas</surname>
            ,
            <given-names>P</given-names>
          </string-name>
          ;
          <string-name>
            <surname>González-Conejero</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          <article-title>Technical Bases for Compliance by Design (CbD)</article-title>
          .
          <source>CRC D2D Deliverable</source>
          , May
          <year>2017</year>
          (updated
          <year>July 2017</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Suchanek</surname>
            ,
            <given-names>F.M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kasneci</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Weikum</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          <article-title>YAGO: a core of semantic knowledge unifying Wordnet and Wikipedia</article-title>
          .
          <source>In Proceedings of the 16th international conference on World Wide Web</source>
          , pp.
          <fpage>697</fpage>
          -
          <lpage>706</lpage>
          , ACM, May
          <year>2007</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Del Corro</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gemulla</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          <string-name>
            <surname>Clausie</surname>
          </string-name>
          <article-title>: clause-based open information extraction</article-title>
          .
          <source>In Proceedings of the 22nd international conference on World Wide Web</source>
          , pp.
          <fpage>355</fpage>
          -
          <lpage>366</lpage>
          , ACM, May
          <year>2013</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Cardellino</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          , et al.
          <article-title>Licentia: A Tool for Supporting Users in Data Licensing on the Web of Data</article-title>
          .
          <source>Proceedings of the 2014 International Conference on Posters &amp; Demonstrations Track-Volume 1272. CEUR-WS. org</source>
          ,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <surname>Gupta</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Szekely</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Knoblock</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Aman</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Taheriyan</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Muslea</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <article-title>Karma: A system for mapping structured sources into the Semantic Web</article-title>
          . In E. Simperl,
          <string-name>
            <given-names>P.</given-names>
            <surname>Cimiano</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Polleres</surname>
          </string-name>
          , Ó. Corcho, and V. Presutti, editors,
          <source>The Semantic Web: Research and Applications - 9th Extended Semantic Web Conference, ESWC</source>
          <year>2012</year>
          , Heraklion, Crete, Greece, May
          <volume>27</volume>
          -31,
          <year>2012</year>
          . Proceedings, LNCS 7295, pp.
          <fpage>430</fpage>
          -
          <lpage>434</lpage>
          , Springer,
          <year>2012</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17. Law and
          <string-name>
            <given-names>Policy</given-names>
            <surname>Program</surname>
          </string-name>
          .
          <source>Big Data Technology and National Security - Comparative International Perspectives on Strategy</source>
          , Policy and Law:
          <string-name>
            <surname>Australia (Data to Decisions</surname>
            <given-names>CRC</given-names>
          </string-name>
          ,
          <year>2016</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18.
          <string-name>
            <surname>Casanovas</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>De Koker</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mendelson</surname>
            , and
            <given-names>David</given-names>
          </string-name>
          <string-name>
            <surname>Watts</surname>
          </string-name>
          .
          <article-title>"Regulation of Big Data: Perspectives on strategy, policy, law and privacy." Health and Technology (</article-title>
          <year>2017</year>
          ):
          <fpage>1</fpage>
          -
          <lpage>15</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19.
          <string-name>
            <surname>Bennet-Moses</surname>
          </string-name>
          , L.,
          <string-name>
            <surname>de Koker</surname>
          </string-name>
          , L. Open Secrets:
          <article-title>Balancing Operational Secrecy and Transparency in the Collection</article-title>
          and
          <article-title>Use of Data for National Security and Law Enforcement Agencies</article-title>
          ,
          <source>CRC Report</source>
          ,
          <year>2017</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          20.
          <string-name>
            <given-names>Australian</given-names>
            <surname>Government</surname>
          </string-name>
          .
          <article-title>Data availability and use</article-title>
          .
          <source>Productivity Commission Inquiry Report</source>
          , No.
          <volume>82</volume>
          ,
          <issue>31</issue>
          <year>March 2017</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          21.
          <string-name>
            <surname>Pagallo</surname>
            ,
            <given-names>U.</given-names>
          </string-name>
          <article-title>Online Security and the Protection of Civil Rights: A Legal Overview</article-title>
          .
          <source>Philosophy &amp; Technology</source>
          <volume>26</volume>
          (
          <year>2013</year>
          ):
          <fpage>381</fpage>
          -
          <lpage>395</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          22.
          <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>Gkorioso</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="ref23">
        <mixed-citation>
          23.
          <string-name>
            <surname>Casanovas</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Mendelson</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          &amp;
          <string-name>
            <surname>Poblet</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <article-title>A Linked Democracy approach to regulate health data</article-title>
          .
          <source>Health and Technology</source>
          (
          <year>2017</year>
          ),
          <source>DOI: 10.1007/s12553-017-0191-5</source>
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          24.
          <string-name>
            <surname>Poblet</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Plaza</surname>
            ,
            <given-names>E. Democracy</given-names>
          </string-name>
          <string-name>
            <surname>Models</surname>
          </string-name>
          and Civic Technologies: Tensions, Trilemmas, and Trade-offs,
          <year>2017</year>
          , arXiv preprint arXiv:
          <volume>1705</volume>
          .
          <fpage>09015</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          25.
          <string-name>
            <surname>Watts</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <given-names>Bridget</given-names>
            <surname>Bainbridge</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            ,
            <surname>de Koker</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            ,
            <surname>Casanovas</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            ,
            <surname>Smythe</surname>
          </string-name>
          , S. Project B.
          <article-title>3 A Governance Framework for the National Criminal Intelligence System (NCIS), Data to Decisions Cooperative Research Centre</article-title>
          , La Trobe University, 30 June 2017.
        </mixed-citation>
      </ref>
      <ref id="ref26">
        <mixed-citation>
          26. Open Group Standard TOGAF Version 9.1 Document Number:
          <fpage>G116</fpage>
          . ISBN:
          <volume>9789087536794</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref27">
        <mixed-citation>
          27.
          <string-name>
            <surname>Brous</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Janssen</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vilminko-Heikkinen</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          <article-title>Coordinating Decision-Making in Data Management Activities: A Systematic Review of Data Governance Principles</article-title>
          . In H. J.
          <string-name>
            <surname>Scholl</surname>
          </string-name>
          et al.
          <source>International Conference on Electronic Government and the Information Systems Perspective EGOVIS</source>
          <year>2016</year>
          , LNCS 9820, pp.
          <fpage>115</fpage>
          -
          <lpage>125</lpage>
          , Springer International Publishing,
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref28">
        <mixed-citation>
          28.
          <string-name>
            <surname>Mondorf</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wimmer</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <article-title>A. Requirements for an Architecture Framework for PanEuropean E-Government Services</article-title>
          . In H. J.
          <string-name>
            <surname>Scholl</surname>
          </string-name>
          et al.
          <source>International Conference on Electronic Government and the Information Systems Perspective EGOVIS</source>
          <year>2016</year>
          , LNCS 9820, pp.
          <fpage>135</fpage>
          -
          <lpage>150</lpage>
          , Springer International Publishing,
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>