<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">Open data for accountability in the fight against corruption</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Joris</forename><surname>Hulstijn</surname></persName>
							<email>j.hulstijn@uvt.nl</email>
							<affiliation key="aff0">
								<orgName type="department">Tilburg School of Economics and Management</orgName>
								<orgName type="institution">Tilburg University</orgName>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Darusalam</forename><surname>Darusalam</surname></persName>
							<email>d.darusalam@tudelft.nl</email>
							<affiliation key="aff1">
								<orgName type="department">Department of Technology, Policy and Management</orgName>
								<orgName type="institution">Delft University of Technology</orgName>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Marijn</forename><surname>Janssen</surname></persName>
							<affiliation key="aff1">
								<orgName type="department">Department of Technology, Policy and Management</orgName>
								<orgName type="institution">Delft University of Technology</orgName>
							</affiliation>
						</author>
						<title level="a" type="main">Open data for accountability in the fight against corruption</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">44D9FDC679E8000CE2BFF808E7B183C5</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-25T08:49+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>There has been a lot of research on the use of open data in the fight against corruption. Although there are some promising examples, it appears that a systematic approach is lacking. What are the design principles for an architecture to open up data and thereby reduce corruption? In this paper we use theory about fraud, and about public accountability to derive design principles for an open data architecture. Crucial is the sustained presence of a specific forum: a group of people who are critical, have expertise, are free to challenge the authorities. Unlike the general public, a specific forum has an interest in reviewing the data. The architecture is motivated and illustrated by an extensive example of an E-procurement system in the context of an anticorruption program in Palembang, Indonesia.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1">Introduction</head><p>There has been a lot of attention for 'opening up' government data in the field of e-government <ref type="bibr" target="#b27">[28]</ref>. One particular application area of open data is the fight against corruption. Corruption is a complex and difficult problem, also in government <ref type="bibr" target="#b11">[12]</ref>. Corruption can harm society and result in increased poverty, reduce available money for essential public services, destroy citizens' trust in government and undermine economic growth <ref type="bibr" target="#b25">[26]</ref>. There are many factors that can lead to corruption in government <ref type="bibr" target="#b20">[21]</ref>. In principle, addressing these different factors will lead to different approaches in the fight against corruption. In this paper, we will focus on the factors of transparency and accountability. Therefore we investigate a particular strategy to fight corruption: to open up government data to the public <ref type="bibr" target="#b24">[25]</ref>. One of the claimed benefits of open data is that the government becomes more transparent and accountable <ref type="bibr" target="#b14">[15]</ref>. This appears intuitive. Open data allows scrutiny by the public, which will reduce opportunities for corruption and increase changes of detection. Indeed, there are successful examples of e-government systems to reduce corruption, see <ref type="bibr" target="#b15">[16]</ref> and <ref type="bibr" target="#b1">[2]</ref> (p 265-266). There have also been examples of system to open up government data to reduce corruption, for example in Brazil. A recent study by Transparency International <ref type="bibr" target="#b13">[14]</ref> shows that a lot has been achieved in Brazil.</p><p>"Nonetheless, open data is still underutilized, and anti-corruption enforcement is weak" <ref type="bibr" target="#b13">[14]</ref>(p 4). In particular, there are problems with data quality. Moreover, the initiatives lack involvement: when there is a 'lead' there is not always a follow up. Apparently, the relationship between open data, transparency and accountability and eventually reducing corruption is not immediate, but rests on specific assumptions. For instance, in the context of corporate governance, Elia argues that opening up too much data, in too much detail, is pointless or even counterproductive <ref type="bibr" target="#b10">[11]</ref>. Details of illicit behavior may be drowned out.</p><p>In this discussion paper we therefore propose design principles for an open data architecture that should foster accountability, and in turn, reduce opportunities for corruption. We will take a theoretical approach, based on an analogy with fraud <ref type="bibr" target="#b0">[1,</ref><ref type="bibr" target="#b8">9]</ref>, and theory of public accountability by Bovens <ref type="bibr" target="#b2">[3]</ref>. Following Day and Klein <ref type="bibr" target="#b9">[10]</ref>, Bovens characterizes accountability as a dialogue between an actor and a 'significant other', called the forum. The actor feels obliged to provide accounts of its conduct to the forum. In order to hold the actor accountable, the forum should be critical and powerful enough to ask for explanations, and eventually pass judgement about the conduct of the actor.</p><p>To motivate the approach and validate the design principles, we discuss a case study of an e-procurement system at the local government of Palembang in Indonesia.</p><p>The remainder of the paper is structured as follows. Section 2 provides a background on corruption and how it can be reduced. Section explain the idea of accountability as a dialogue, and derives some general principles about the actor and the forum. Section 3 applies these principles to an architecture for opening up data. Section 4, finally, discusses application of these ideas in the Palembang case study.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2">Corruption and Fraud</head><p>In this section we provide a background of the notion of corruption in government and how it can be reduced. Corruption is an important topic that deserves a proper literature review. In this discussion paper, we cannot provide a full review. Instead, we will focus on two elements. First, we will draw an analogy with fraud, and derive three ways to address corruption. Second, we will discuss anti-corruption strategies.</p><p>The word 'corruption' is based on Latin: corrumpere means to spoil or destroy. Corruption is defined as "behavior which deviates from the normal duties of a public role because of private-regarding (family, close private clique) pecuniary or status gains" <ref type="bibr" target="#b20">[21]</ref> (p. 4). An additional aspect of corruption in the case of government, is the misuse of power <ref type="bibr" target="#b11">[12]</ref>. So similar to the notion of fraud, which is defined as a violation of trust <ref type="bibr" target="#b8">[9]</ref>, corruption involves the misuse of responsibilities related to a public role or duty. For instance, corruption involves "bribery (use of reward to pervert the judgments of a person in a position of trust), nepotism (bestowal of patronage because of ascriptive relationship rather than merit), and misappropriation (illegal appropriation of public resources for private-regarding uses" <ref type="bibr" target="#b20">[21]</ref> (p. 4).</p><p>Figure <ref type="figure" target="#fig_0">1</ref>. Fraud triangle <ref type="bibr" target="#b0">[1,</ref><ref type="bibr" target="#b8">9]</ref> There is an interesting analogy between corruption and the notion of fraud as studied in accounting <ref type="bibr" target="#b0">[1]</ref> and criminology <ref type="bibr" target="#b8">[9]</ref>. In Figure <ref type="figure" target="#fig_0">1</ref>, fraud is depicted as a triangle, involving three necessary elements.</p><p>(1) Opportunity: the actor has been trusted with responsibilities that involve certain powers (budget; decision rights), (2) Pressure: the actor has a 'non-shareable problem' (e.g. financial problems, status), and misuse of trust can offer a 'private solution' (3) Rationalization: the actor provides a kind of explanation for crossing the line: "I am only borrowing the money" or "others do it too".</p><p>The triangle suggests three ways of reducing fraud or corruption. These are effectively means to improve management control <ref type="bibr" target="#b18">[19]</ref> and the system of internal controls <ref type="bibr" target="#b7">[8]</ref>, in particular the control environment. First, one could try to reduce opportunities for corruption. That means limiting the powers of an actor in a certain role, by putting administrative restrictions in the procedures or by recording details of execution (audit trail). This is the easiest element to adjust. In modern organizations, many institutional powers are controlled by ICT, such as the ERP system or business process management system. In accounting, there is a lot of expertise on ways to strengthen internal controls, partly by means of ICT. In particular, there are so called application controls, which are built into software applications. For instance, there are authorization tables, restrictions on the budget a person can control, on tariffs and pricing policies, etc. In addition, there are also many manual controls, that are supported by technological means. For instance, if all invoices are numbered consecutively, it is harder to make one disappear. Finally, there are the IT general controls, that help to maintain a reliable control environment. In particular, consider such measures as segregation of duties, audit trail, access controls, logging and monitoring <ref type="bibr" target="#b22">[23]</ref> Second, one could try to reduce pressure. In the financial sector there has been a lot of debate about remuneration. If you pay people enough, is the argument, there should be less incentives to misuse trust for personal gains. However, the evidence as to the effectiveness of this measure is inconclusive, at best <ref type="bibr" target="#b23">[24]</ref>. Another option to reduce pressure is suggested by Cressey's original paper <ref type="bibr" target="#b8">[9]</ref>: foster an environment in which people feel safe to discuss problems. In this way, when people do have a problem (gambling debts, dissatisfaction), they are less likely to see misuse of trust as a way out. For example, one could implement a regular meeting structure, in which officials have an opportunity to discuss -in secret -difficult decisions with peers.</p><p>Third, one could try to raise moral standards and make it harder for people to 'rationalize' misuse of trust. This is perhaps the most effective but also the hardest option. It involves elements of organizational culture, such as public values, social practices and role models <ref type="bibr" target="#b12">[13,</ref><ref type="bibr" target="#b21">22]</ref>. Organizational culture can't be managed directly. Instead, one can only try and improve side conditions. The 'tone at the top' makes an enormous difference. For example, in the Enron case, efforts to improve compliance were useless, as executives themselves were seen to violate the rules <ref type="bibr" target="#b23">[24]</ref>. Public values such as quality awareness, safety or integrity, can be stimulated. For example, to stimulate quality awareness, one could routinely publish examples of products that are rejected. This will demonstrate the borderline. Practices and procedures may help to reach consensus. If it is mandatory to rate and discuss quality of a product with colleagues, this will help establish a common threshold.</p><p>We will now discuss an example from the literature, to see how these approaches to fraud are applied.</p><p>Example. Kim <ref type="bibr" target="#b15">[16]</ref> reports about the OPEN system, as part of a longterm effort in Korea to fight corruption (1998-2007). The OPEN system "is an online system used to disclose administrative procedures (likely to be related to corruption) to citizens in various public service areas (such as housing and construction, sanitation, and urban planning, among others)." <ref type="bibr" target="#b15">[16]</ref> (p 45). The purpose was to improve efficiency, by preventing unnecessary delays or unfair handling by civil servants, and also to improve transparency in some areas of civil administration.</p><p>First, such a system is likely to reduce opportunities for corruption. By allowing citizens to view the procedures and status of their requests, an audit trail is created. Decisions can be compared. Moreover, the system was supported by projects to clarify the procedures and design systems that simplify, standardize, and de-personalize delivery of services <ref type="bibr" target="#b15">[16]</ref>.</p><p>Second, we do not know if the system helped to reduce pressure. We do know, that the system reduced personal contact between applicants and officials <ref type="bibr" target="#b15">[16]</ref>, thus reducing opportunities to be put under pressure.</p><p>Third, the 'tone at the top' proved decisive. The system was supported by Kun Koh, mayor of the city of Seoul. "Mayor Koh took resolute steps to fight corruption. He launched a variety of reform programs which culminated in the declaration of a 'War against Corruption'" <ref type="bibr" target="#b15">[16]</ref> (p 46). By doing this, Koy set values such 'clean' and 'transparent' as norms that no one could deny.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Strategies to Combat Corruption</head><p>Activities to reduce corruption are often presented as phases in an anticorruption cycle: prevention, detection, investigation and sanction <ref type="bibr" target="#b19">[20]</ref>.</p><p>Alternatively, the literature mentions four strategies to combat corruption: prevention, enforcement, access to information and empowerment, and capacity building <ref type="bibr" target="#b15">[16]</ref>. Unlike the stages, which focus on officials, these strategies also assign an important role to citizens. They indicate how ICT or open data can help: by providing access to information and empowering citizens, and by helping to organize and improve expertise, i.e. capacity building. In the next section, we will try to make these ideas about empowerment more systematic, by relating them to a theory of public accountability.</p><p>Accountability has positive connotations, and is used as a kind of synonym to good governance. However, the meaning of the term depends on the context, on a relationship with others: "Accountability can be defined as a social relationship in which an actor feels an obligation to explain and to justify his or her conduct to some significant other" <ref type="bibr" target="#b9">[10]</ref>. According to Bovens <ref type="bibr" target="#b2">[3,</ref><ref type="bibr" target="#b3">4]</ref> an accountability relationship involves an actor and a forum (Figure <ref type="figure">2</ref>). The actor can be a person or agency. Then there is some significant other, who can be a person or agency, but can also be a more abstract entity, such as God or 'the public'. Bovens calls this the forum.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Figure 2. Accountability as a dialogue</head><p>The accountability relationship develops in three stages. First, the actor must feel obliged to inform the forum about its conduct, including justifications in case of failure. The obligation may be both formal, i.e., required by law or by contract, or informal and self-imposed, for instance because the actor is dependent on the forum. Second, the information may be reason for the forum to challenge the actor, ask for explanations and debate the adequacy of the conduct. The actor responds, providing additional facts or motivations. Third, the forum passes judgement on the actor's conduct. A negative judgment often leads to some kind of sanction; again this can be both formal and informal. This means that an accountability relation should provide room for discussion: it is not a one-way stream of reports, but rather a dialogue. The process can be formalized as a dialogue game <ref type="bibr" target="#b4">[5]</ref>.</p><p>Bovens <ref type="bibr" target="#b2">[3]</ref> identifies five necessary conditions of public accountability, which characterize the dialogue game just described: (1) "public accessibility of the account giving-and not purely internal, discrete informing;</p><p>(2) explanation and justification of conduct-and not propaganda, or the provision of information or instructions to the general public;</p><p>(3) the explanation should be directed at a specific forum-and not be given at random; (4) the actor must feel obliged to come forward-instead of being at liberty to provide any account whatsoever; and (5) there must be a possibility for debate and judgment, including an optional imposition of (informal) sanctions, by the forum-and not a monologue without engagement" <ref type="bibr" target="#b2">[3]</ref> (p 185); italics added. The prototypical example of an accountability relation exists between government and parliament, where parliament derives its power from the population, and can send the government home (confidence vote). Journalists play an important role, demanding transparency and challenging the government. By informing the public, they can mobilize the underlying power of parliament.</p><p>Another example of an accountability relation is auditing <ref type="bibr" target="#b5">[6,</ref><ref type="bibr" target="#b4">5]</ref>. In that case, management is the actor, reporting the annual financial accounts. The shareholders act as a forum. The forum is assisted by an auditor, who has the expertise and authority to evaluate the financial accounts, compare them to standards and norms and provide assurance about their reliability <ref type="bibr" target="#b16">[17]</ref>. However, the auditor as such has little power. The power derives from the shareholders, or other powerful stakeholders, such as the board of directors or regulators.</p><p>Based on these examples, we derive four additional necessary conditions for a fruitful accountability relationship, compare also <ref type="bibr" target="#b5">[6]</ref> . <ref type="bibr" target="#b5">(6)</ref> The organization of the actor must provide reliable reports about its conduct. Reports must be accurate (correspond to reality) and complete (contain all relevant aspects of reality). In practice this can be ascertained by internal controls. <ref type="bibr" target="#b6">(7)</ref> The forum must be independent of the actor, allowing it to challenge the actor, as stated in (5) above. In particular, the forum should not depend on the actor for employment. Individual members should not have family ties, or personal relationships. (8) The forum must have, or have access to, expertise, to evaluate the reports, compare them to standards and norms, and eventually pass judgement. If necessary, the forum can be supported by experts or auditors, who possess specific expertise. That means that those experts must also be independent.</p><p>(9) The forum must wield enough power or influence over the actor to "make the actor feel obliged to come forward" as in (4), and to have a credible claim to sanctions, as in <ref type="bibr" target="#b4">(5)</ref>. In particular, when the actor is dependent on the forum in some way, the forum has the power to withhold whatever the actor depends upon.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4">An open data architecture for accountability</head><p>So how can we apply these ideas to an open data architecture? An architecture is a set of fundamental concepts or properties of a system in its environment, embodied in its elements, relationships, and in the principles of its design and evolution <ref type="bibr" target="#b17">[18]</ref> (p 2).</p><p>What are the components, what are their relationships, and what are the design principles? If we want to conform to conditions (1) -( <ref type="formula">9</ref>) above, we have to include some form of governance. So we will treat architecture here in a broad sense, including also the organizational structure. An open data architecture is a socio-technical system <ref type="bibr" target="#b6">[7]</ref>. At first sight, an open data architecture seems to be just a website to publish data in a particular format. The website makes the data available to the forum (D0. Availability). Crucial elements are the legislation, policies and business rules that determine which data eventually gets Because accountability involves a relationship, the architecture should not only focus on what governments have to do in order to reliably 'open up' data sets, but also on the forum. That means in particular that the architecture should have components for the forum to gather, and mobilize support (F0. Mobilize). Consider for example outlets on social media. Clearly, mobilizing a forum is not the responsibility of the government! The government should collaborate with those institutions that happen to represent the forum, such as pressure groups, branch organizations, watchdogs, regulators, parliaments, etc. Given such collaboration, the platform should allow all members of the forum easy access (F1. Access). The platform should have components for the forum, or experts and auditors, to analyze the data (F2. Analysis). The architecture should have components to pose challenges and questions, about specific data elements and get a relevant proper response (F3. Challenge and response), see also D5. Responses should be archived, and should in principle also be made public (F4. Archive). In some cases, absence of a response would also be telling. Finally, the architecture should make it possible to escalate and file complaints, in case of a suspected deviation from the policies (F5. Complaints procedure). In addition, the architecture should have specific support for journalists, experts or auditors (F1 and F2).</p><p>The list of requirements is summarized in Table <ref type="table" target="#tab_1">1</ref>. </p><formula xml:id="formula_0">Data</formula></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.">Case: E-procurement in Palembang</head><p>Data Collection Data for this case study was collected by investigating various sources, including the official website, official documents, prior research and the participating observations of one of the authors. Case Description. The local government in Palembang South Sumatera Indonesia uses the Systems Electronic Procurement Service (LPSE) for the procurement of government goods and services. The LPSE system has been introduced to improve the efficiency, effectiveness, quality, and transparency in the procurement of goods and services. The system matches vendors and governments. LPSE is hosted by a unit formed across ministries and other institutions. This system facilitates procurement officers and also provides services for the provider of goods and services, in the territory of the LPSE concerned.</p><p>The procurement process starts by defining the needs, which is followed by publishing the Request for Quotation (RFQ). Next, suppliers receive the RFQ and develop their quotes. The supplier sends the quotes to government, government who receives the proposals. Once the proposals are received and the deadline has passed, the proposals are evaluated and supplier(s) will be selected and a final tender will be requested and the contract is signed. Thereafter follows the execution of the contract in which the products and services are delivered and paid. Finally, the delivered products and services can be evaluated.</p><p>According to local government regulation, all working units of local government must use the LPSE system. This should prevent bypassing and the risks of fraud. All the working units are obliged to announce their planning, implementation and results of their procurement processes via the LPSE system. As such, there is a huge potential for opening data. The types of data available in the LPSE system are as follows:  Auction announcement: The LPSE system provides an announcement about what types of procurement are available from working units in Palembang;  Information about system failure: The system provides information in case a package cannot be generated, or if a file failed to upload, so the system can provide solutions;  Electronic Catalogue (EC): This catalogue provides a detailed listing of vendor offerings. For example, description of products, prices, delivery times.  Monitoring and online evaluation: The system provides information about planning packages of procurements, financial progress, physical progress, procurement of goods and services progress;  Whistleblowing: The LPSE system has a link to https://wbs.lkpp.go.id/container.php. This website provides an opportunity for a person who has information about illegal, unethical or corruption related behavior related to procurement. The person can report these activities to the corruption watch or audit board.</p><p>In the current system, all this data is not yet open to the public. In the next section we present patterns for opening data.</p><p>Case Problem. How could opening up such data, help to reduce corruption?</p><p>Case Solution. In earlier research on the case, we found six types of patterns for corruption detection, which are presented in Table <ref type="table">2</ref>. These patterns are all based on internal control measures <ref type="bibr" target="#b22">[23]</ref>.</p><p>Evaluation. The patterns show that not only the resulting data should be opened, but also information about the operation of the administrative processes and the implemented internal control measures to prevent corruption should be opened. However, these internal control principles are not commonly known. Accounting expertise is needed to evaluate which segregations of duties, ought to be met. This puts additional requirements on the kind of audience that the Palembang authorities are trying to reach. Without proper guidance, providing such meta-data may distract users from viewing the actual procurements.</p><p>Opening up government data to the public, seems a good strategy to try and fight corruption. The claim is that opening up government data will somehow improve transparency and accountability. Current examples of systems that attempt to open up data in the fight against corruption, therefore make an ad hoc impression. In this paper, we have tried to provide some theoretical underpinning to these attempts, in two ways. First, we have used an analogy with fraud, to identify three ways of reducing fraud or corruption: (1) by reducing opportunities for misuse of trust, essentially by strengthening the internal controls, (2) by fostering an environment in which people talk about their problems, before they become insurmountable, and (3) by stimulating an organizational culture, in which normative decisions are being discussed and recorded, establishing consensus on norms and values.</p><p>Second, we have used the theory of public accountability of Bovens, with five necessary conditions for a fruitful accountability relationship. Based on an analogy with accounting, we derived another four necessary conditions: reliable reporting (for the actor), and independence, expertise and power (for the forum). These conditions can be translated into a set of five requirements for an architecture and governance procedure for opening up data (Availability, Data selection policies, Representation standard, Content, Reliability, Relevance) and five requirements focusing on establishing a critical forum (Mobilize, Access, Analysis, Challenge and response, Archive and Complaints procedure).</p><p>Some of these requirements were discussed in the context of a case study of an e-procurements system in Palembang, that makes it possible to open up crucial data about the procurement process. The case shows that indeed it is crucial to identify a specific forum. This is contrary to current practice in the open data community, where data is being opened up for a general public, in the hope they will find some purpose for it (e.g. hackatons). Lack of a specific audience and purpose for the data being shared, means in particular, that reliability and relevance are hard to establish. This may partly explain the current problems with data quality that are reported for many open data initiatives, e.g. <ref type="bibr" target="#b27">[28]</ref>.</p><p>In the Palembang e-Procurement case, it is likely that the forum will include vendors, in particular the competitors of those vendors who received the contract, because they have an incentive to protect their interests. The case also shows, that it makes sense to open up meta-data, to reveal if the internal controls that ensure reliable reporting, are effective. However, this will require the forum to involve experts, such as accountants, who can interpret and evaluate such data.</p><p>Future research will have to show whether also the dialogue-related aspects of the theory are valid in this case.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Figure 1 .</head><label>1</label><figDesc>Figure 1. Conceptualizing open data [27] (p 157)</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_0"><head></head><label></label><figDesc>Data selection). Published data should be relevant to the issues addressed by the application, and later to the challenges or inquiries made. Data should be fit to be published. In particular, state secrets, data that are recognized to be confidential (e.g. medical; military) or data about individual persons should not be published. This means that data selection should involve a careful trade-off between transparency and confidentiality. Ideally, the forum should have an advisory role on setting the roles and policies for data selection. Moreover, data sets should adhere to representation standards, that improve interoperability between various systems, and allow for comparison (D2. Representation standards). Data sets are filled with real data by interfaces with day-to-day operational systems, such as databases and ERP systems (D3. Content). A coherent system of internal controls should help guarantee reliability of the data (accuracy and completeness) (D4. Reliability). Note that completeness is hard to ensure, as it involves comparison to what is considered to be 'all'. Once selected for publication, officials should not be able to delete data or obstruct publication. Finally, the architecture should have features to respond to challenges and inquiries with data that are relevant (D5. Relevance).</figDesc><table><row><cell>published (D1.</cell><cell></cell></row><row><cell></cell><cell>1. Creating Data (e.g.</cell></row><row><cell></cell><cell>producing, collecting,</cell></row><row><cell></cell><cell>storing and paying for</cell></row><row><cell></cell><cell>data)</cell></row><row><cell>(Governmental)</cell><cell>2. Opening data</cell></row><row><cell>organizations</cell><cell>5. Discussing and</cell></row><row><cell></cell><cell>providing feedback on</cell></row><row><cell>Users</cell><cell>(linked) open data</cell></row><row><cell></cell><cell>3. Finding open data</cell></row><row><cell></cell><cell>4. Using open data (e.g.</cell></row><row><cell></cell><cell>curating, annotating,</cell></row><row><cell></cell><cell>enhancing, processing,</cell></row><row><cell></cell><cell>visualising, linking)</cell></row></table></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_1"><head>Table 1 .</head><label>1</label><figDesc>Requirements for an open data architecture, focusing both on publishing open data (D) and on the role of the forum (F)</figDesc><table><row><cell>publishing requirements</cell><cell>Forum requirements</cell></row><row><cell>D0. Availability</cell><cell>F0. Mobilize</cell></row><row><cell>D1. Data selection policies</cell><cell>F1. Access</cell></row><row><cell>D2. Representation standard</cell><cell>F2. Analysis</cell></row><row><cell>D3. Content</cell><cell>F3. Challenge and response</cell></row><row><cell>D4. Reliability</cell><cell>F4. Archive</cell></row><row><cell>D5. Relevant</cell><cell>F5. Complaints procedure</cell></row></table></figure>
		</body>
		<back>
			<div type="annex">
<div xmlns="http://www.tei-c.org/ns/1.0"><p>A possible 'forum' for this case is the pool of potential vendors. It is likely that competitors of the vendor who received the procurement contract, have enough interest to actually analyze the data, and challenge the local government in case of irregularities. Collectively, the pool of vendors is large enough to wield some power or influence over the local government, as they form a substantial portion of the voting population.</p><p>The most promising pattern seems to be number 2: cross data comparison. This may help to identify whether awarded contracts actually conform to the stated contract requirements, and whether there are any oddities in awarding behavior.</p></div>			</div>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">Red Flagging Management Fraud: A Validation</title>
		<author>
			<persName><forename type="first">S</forename><surname>Albrecht</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Romney</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Advances in Accounting</title>
		<imprint>
			<biblScope unit="volume">3</biblScope>
			<biblScope unit="page" from="323" to="333" />
			<date type="published" when="1986">1986</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">Using ICTs to create a culture of transparency: E-government and social media as openness and anti-corruption tools for societies</title>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">C</forename><surname>Bertot</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><forename type="middle">T</forename><surname>Jaeger</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">M</forename><surname>Grimes</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Government information quarterly</title>
		<imprint>
			<biblScope unit="volume">27</biblScope>
			<biblScope unit="issue">3</biblScope>
			<biblScope unit="page" from="264" to="271" />
			<date type="published" when="2010">2010</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">Public Accountability</title>
		<author>
			<persName><forename type="first">M</forename><surname>Bovens</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">The Oxford Handbook of Public Management, ferlie</title>
				<meeting><address><addrLine>Oxford, United Kingdom</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2005">2005</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<analytic>
		<title level="a" type="main">Analysing and Assessing Accountability: A Conceptual Framework</title>
		<author>
			<persName><forename type="first">M</forename><surname>Bovens</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">European Law Journal</title>
		<imprint>
			<biblScope unit="volume">13</biblScope>
			<biblScope unit="issue">4</biblScope>
			<biblScope unit="page" from="447" to="468" />
			<date type="published" when="2007">2007</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">Value-based Argumentation for Justifying Compliance</title>
		<author>
			<persName><forename type="first">B</forename><surname>Burgemeestre</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Hulstijn</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y.-H</forename><surname>Tan</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Artificial Intelligence and Law</title>
		<imprint>
			<biblScope unit="volume">19</biblScope>
			<biblScope unit="issue">2-3</biblScope>
			<biblScope unit="page" from="149" to="186" />
			<date type="published" when="2011">2011</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">Design for the Values of Accountability and Transparency</title>
		<author>
			<persName><forename type="first">B</forename><surname>Burgemeestre</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Hulstijn</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Handbook of Ethics, Values, and Technological Design</title>
				<editor>
			<persName><forename type="first">J</forename><surname>Van Den Hoven</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">P</forename><surname>Vermaas</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">I</forename><surname>Van De Poel</surname></persName>
		</editor>
		<meeting><address><addrLine>Berlin</addrLine></address></meeting>
		<imprint>
			<publisher>Springer Verlag</publisher>
			<date type="published" when="2015">2015</date>
			<biblScope unit="page" from="303" to="333" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">Sociotechnical principles for system design</title>
		<author>
			<persName><forename type="first">C</forename><forename type="middle">W</forename><surname>Clegg</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Applied Ergonomics</title>
		<imprint>
			<biblScope unit="volume">31</biblScope>
			<biblScope unit="page" from="463" to="477" />
			<date type="published" when="2000">2000</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">Internal Control -Integrated Framework</title>
	</analytic>
	<monogr>
		<title level="m">Committee of Sponsoring Organizations of the Treadway Commission</title>
				<imprint>
			<date type="published" when="1992">1992</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">The Criminal Violation of Financial Trust</title>
		<author>
			<persName><forename type="first">D</forename><forename type="middle">R</forename><surname>Cressey</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">American Sociological Review</title>
		<imprint>
			<biblScope unit="volume">15</biblScope>
			<biblScope unit="issue">6</biblScope>
			<biblScope unit="page" from="738" to="743" />
			<date type="published" when="1950">1950</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<monogr>
		<author>
			<persName><forename type="first">P</forename><surname>Day</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Klein</surname></persName>
		</author>
		<title level="m">Accountabilities: Five Public Services</title>
				<meeting><address><addrLine>London</addrLine></address></meeting>
		<imprint>
			<publisher>Tavistock</publisher>
			<date type="published" when="1987">1987</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<analytic>
		<title level="a" type="main">Transparency rights, technology, and trust</title>
		<author>
			<persName><forename type="first">J</forename><surname>Elia</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Ethics and Information Technology</title>
		<imprint>
			<biblScope unit="volume">11</biblScope>
			<biblScope unit="issue">2</biblScope>
			<biblScope unit="page" from="145" to="153" />
			<date type="published" when="2009">2009</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b11">
	<monogr>
		<title level="m" type="main">Political corruption</title>
		<author>
			<persName><forename type="first">A</forename><forename type="middle">J</forename><surname>Heidenheimer</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Johnston</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><forename type="middle">T</forename><surname>Levine</surname></persName>
		</author>
		<imprint>
			<date type="published" when="1970">1970</date>
			<publisher>Holt, Rinehart &amp; Winston</publisher>
			<biblScope unit="volume">24</biblScope>
			<biblScope unit="page" from="26" to="27" />
			<pubPlace>New York</pubPlace>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b12">
	<analytic>
		<title level="a" type="main">Measuring Organizational Cultures: A Qualitative and Quantitative Study</title>
		<author>
			<persName><forename type="first">G</forename><surname>Hofstede</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Administrative Science Quarterly</title>
		<imprint>
			<biblScope unit="volume">35</biblScope>
			<biblScope unit="issue">2</biblScope>
			<biblScope unit="page" from="286" to="316" />
			<date type="published" when="1990">1990</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b13">
	<monogr>
		<author>
			<persName><forename type="first">D</forename><surname>Iglesias</surname></persName>
		</author>
		<title level="m">Open Data and the Fight Against Corruption in Brazil</title>
				<meeting><address><addrLine>Berlin</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2017">2017</date>
		</imprint>
	</monogr>
	<note>Transparency International</note>
</biblStruct>

<biblStruct xml:id="b14">
	<monogr>
		<author>
			<persName><forename type="first">M</forename><surname>Janssen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Zuiderwijk</surname></persName>
		</author>
		<title level="m">Open data and transformational government</title>
				<meeting><address><addrLine>United Kingdom</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2012">2012</date>
		</imprint>
		<respStmt>
			<orgName>Brunel University</orgName>
		</respStmt>
	</monogr>
	<note>Transforming Government Workshop</note>
</biblStruct>

<biblStruct xml:id="b15">
	<analytic>
		<title level="a" type="main">An institutional analysis of an e-government system for anticorruption: The case of OPEN</title>
		<author>
			<persName><forename type="first">S</forename><surname>Kim</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><forename type="middle">J</forename><surname>Kim</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Lee</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Government Information Quarterly</title>
		<imprint>
			<biblScope unit="volume">26</biblScope>
			<biblScope unit="page" from="42" to="50" />
			<date type="published" when="2009">2009</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b16">
	<monogr>
		<author>
			<persName><forename type="first">W</forename><surname>Knechel</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Salterio</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Ballou</surname></persName>
		</author>
		<title level="m">Auditing: Assurance and Risk</title>
				<meeting><address><addrLine>Cincinatti</addrLine></address></meeting>
		<imprint>
			<publisher>Thomson Learning</publisher>
			<date type="published" when="2007">2007</date>
			<biblScope unit="volume">3</biblScope>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b17">
	<monogr>
		<title level="m" type="main">Enterprise Architecture at Work: Modelling, Communication and Analysis</title>
		<author>
			<persName><forename type="first">M</forename><surname>Lankhorst</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2009">2009</date>
			<publisher>Springer Verlag</publisher>
			<pubPlace>Berlin</pubPlace>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b18">
	<monogr>
		<author>
			<persName><forename type="first">K</forename><forename type="middle">A</forename><surname>Merchant</surname></persName>
		</author>
		<title level="m">Modern Management Control Systems, text &amp; cases</title>
				<meeting><address><addrLine>New Jersey</addrLine></address></meeting>
		<imprint>
			<publisher>Prentice Hall</publisher>
			<date type="published" when="1998">1998</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b19">
	<monogr>
		<title level="m" type="main">Understanding and preventing police corruption: lessons from the literature</title>
		<author>
			<persName><forename type="first">T</forename><surname>Newburn</surname></persName>
		</author>
		<author>
			<persName><forename type="first">B</forename><surname>Webb</surname></persName>
		</author>
		<imprint>
			<date type="published" when="1999">1999</date>
			<publisher>Home Office London</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b20">
	<analytic>
		<title level="a" type="main">Corruption and political development: A cost-benefit analysis</title>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">S</forename><surname>Nye</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">American political science review</title>
		<imprint>
			<biblScope unit="volume">61</biblScope>
			<biblScope unit="issue">02</biblScope>
			<biblScope unit="page" from="417" to="427" />
			<date type="published" when="1967">1967</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b21">
	<analytic>
		<title level="a" type="main">On studying organizational cultures</title>
		<author>
			<persName><forename type="first">A</forename><forename type="middle">M</forename><surname>Pettigrew</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Administrative Science Quarterly</title>
		<imprint>
			<biblScope unit="volume">2</biblScope>
			<biblScope unit="issue">4</biblScope>
			<biblScope unit="page" from="570" to="581" />
			<date type="published" when="1979">1979</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b22">
	<monogr>
		<title level="m" type="main">Accounting Information Systems</title>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">B</forename><surname>Romney</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><forename type="middle">J</forename><surname>Steinbart</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2015">2015</date>
			<publisher>Pearson Education</publisher>
		</imprint>
	</monogr>
	<note>13th ed</note>
</biblStruct>

<biblStruct xml:id="b23">
	<analytic>
		<title level="a" type="main">The Anatomy of Corporate Fraud: A Comparative Analysis of High Profile American and European Corporate Scandals</title>
		<author>
			<persName><forename type="first">B</forename><surname>Soltani</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Journal of Business Ethics</title>
		<imprint>
			<biblScope unit="volume">120</biblScope>
			<biblScope unit="issue">2</biblScope>
			<biblScope unit="page" from="251" to="274" />
			<date type="published" when="2014">2014</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b24">
	<analytic>
		<title level="a" type="main">Open government and the use of ICT to reduce corruption risks</title>
		<author>
			<persName><forename type="first">L</forename><forename type="middle">D</forename><surname>Sousa</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">PPT</title>
		<imprint>
			<date type="published" when="2016">2016</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b25">
	<monogr>
		<title level="m" type="main">Transforming Lives: Accelerating Human Development in the Asia and the Pacific</title>
		<author>
			<persName><forename type="first">T</forename><forename type="middle">C</forename><surname>Undp</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2008">2008</date>
			<publisher>Macmillan</publisher>
			<pubPlace>New Delhi</pubPlace>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b26">
	<analytic>
		<title level="a" type="main">Socio-technical Impediments of Open Data</title>
		<author>
			<persName><forename type="first">A</forename><surname>Zuiderwijk</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Electronic Journal of e-Government</title>
		<imprint>
			<biblScope unit="volume">10</biblScope>
			<biblScope unit="issue">2</biblScope>
			<biblScope unit="page" from="156" to="172" />
			<date type="published" when="2012">2012</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b27">
	<analytic>
		<title level="a" type="main">Open data policies, their implementation and impact: A comparison framework</title>
		<author>
			<persName><forename type="first">A</forename><surname>Zuiderwijk</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Janssen</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Government Information Quarterly</title>
		<imprint>
			<biblScope unit="volume">31</biblScope>
			<biblScope unit="issue">1</biblScope>
			<biblScope unit="page" from="17" to="29" />
			<date type="published" when="2014">2014</date>
		</imprint>
	</monogr>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
