<!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>Privacy Level Agreements for Public Administration Information Systems</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Vasiliki Diamantopoulou</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Michalis Pavlidis</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Haralambos Mouratidis</string-name>
          <email>h.mouratidisg@brighton.ac.uk</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>School of Computing, Engineering and Mathematics University of Brighton</institution>
        </aff>
      </contrib-group>
      <fpage>97</fpage>
      <lpage>104</lpage>
      <abstract>
        <p>Improving Public Administration (PA) operations and services is a major focus globally; they should be transparent, accountable and provide services that improve citizens' con dence and trust. In this context, it is important that PAs have the ability to de ne agreements between citizens and PAs and that such agreements can be used in the context of PAs Information Systems to specify citizens' privacy needs, provide feedback on data sharing and enable PA departments to analyse privacy threats and vulnerabilities, compliance with laws and regulations and analyse trust relationships. We propose the use of the concept of Privacy Level Agreement (PLA) to address the aforementioned issues. The PLA is formally speci ed, based on an XML schema, which enables its automated use.</p>
      </abstract>
      <kwd-group>
        <kwd>Privacy Level Agreement</kwd>
        <kwd>Privacy Management</kwd>
        <kwd>Citizen</kwd>
        <kwd>Public Administration</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        Advancements in ICT have enabled Public Administration (PA) to o er an
increasing number of e-services to citizens [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. The bene ts provided to citizens,
such as increase in e ciency, productivity, and growth [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ], can be signi cantly
improved when information is shared across multiple information systems
belonging to di erent PAs (one-stop concept [
        <xref ref-type="bibr" rid="ref13 ref15">15,13</xref>
        ]) and when citizens do not
need to input the same information across di erent PA information systems.
      </p>
      <p>
        On the other hand, a recent EC initiative for capturing European citizens'
opinion concerning their attitude to data protection [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] revealed that 69% are
concerned that the personal data they provide may be used for a purpose other
than that for which it was collected. Moreover, the General Data Protection
Regulation (GDPR) [
        <xref ref-type="bibr" rid="ref12">12</xref>
        ] on data privacy forces organisations to manage data in
a speci c way with regards to privacy. In such context, it is crucial that PA
information systems are developed and operate in a way that improve transparency of
citizen data sharing. In doing so, it is important that PAs are able to clearly
specify citizen privacy needs, provide them with feedback on how their data is shared
and on whether sharing of their data con icts with their needs. In addition, PAs
should enable citizens to understand potential threats and vulnerabilities to their
privacy needs, as well as trust relationships that might endanger their privacy.
We address this challenge by proposing the use of the concept of Privacy Level
Agreement (PLA), which formalises a mutual agreement between a citizen and
a PA regarding the citizens privacy needs and supports the transparency of
citizens' data sharing. The PLA is delivered in a form of a structured agreement
that consists of elds, each of them capturing important and obligatory
information with regards to privacy of citizens' data. We also propose an XML schema
to enable the creation and management of machine-readable PLAs, allowing its
utilisation by distributed information systems, thus addressing interoperability
issues.
      </p>
      <p>The paper is structured as follows: Section 2 discusses related work while
Section 3 presents the context and the de nition of the PLA and also provides
the speci cation of it. In Section 4 we provide the outcome of this work and
nally, Section 5 summarises the paper.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Related Work</title>
      <p>
        The concept of PLA has been launched as an initiative to capture privacy
aspects of cloud providers. The Privacy Level Agreement Working Group of the
Cloud Security Alliance has de ned a PLA in the context of cloud services [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ].
Similarly, the concept of PLA has been presented by [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] as a standardised way
for cloud providers to describe their data protection practices. In this
environment the PLA is considered as a means for the cloud providers to ensure that
their privacy policy is communicated to the service consumers. However, these
works are limited only to privacy aspects of cloud provision and do not provide
support for speci cation of user preferences and needs or ways to de ne privacy
threats and vulnerabilities related to these needs.
      </p>
      <p>
        On the other hand, the literature provides many examples of works that
focus on the speci cation of Service Level Agreements (SLAs) which refer to
the mutual agreement that ensures the obligations and the requirements both
of a service provider and a customer (e.g., [
        <xref ref-type="bibr" rid="ref1 ref9">1,9</xref>
        ]). In contrast to PLA, an SLA
does not take into account privacy aspects of the agreement between a service
provider and a service consumer.
      </p>
      <p>
        Concerning the privacy policies enforcement, the idea of a standardised way
for web sites to communicate with users about their privacy policies in a
standard machine-readable format has been introduced by the Platform of Privacy
Preferences (P3P) project [
        <xref ref-type="bibr" rid="ref16">16</xref>
        ]. This standard enables web browsers and other
user agents to interpret privacy policies on behalf of their users, assisting them
to decide when to exchange data with web sites. However, P3P was designed for
static environments where users privacy preferences are not expected to change
and it also provides limited support for speci cation of privacy threats and
vulnerabilities that might endanger the privacy needs. Finally, in [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] the authors
propose an architecture that promotes the employment of privacy policies and
preferences. They introduce the Privacy Controller Agent for storing and
comparing service providers' privacy policies and user privacy preferences. However,
this work does not provide an agreement between the interested entities but
rather an architecture to de ne privacy policies.
3
      </p>
    </sec>
    <sec id="sec-3">
      <title>Speci cation of a Privacy Level Agreement</title>
      <p>In the context of our work we de ne a PLA as the mutual agreement of the
privacy settings between a service provider (i.e. Public Administration (PA)) and
a user (i.e. citizen), where the former will commit to provide and maintain these
settings throughout the provision of the service. Thus, the PAs can (i) handle
the personal data they keep taking into account citizens' privacy needs, (ii)
provide information concerning the processes they follow and the management of
personal data and (iii) demonstrate that they have proceeded to all the necessary
actions to make their systems robust, mitigating all possible threats.</p>
      <p>The structure of the proposed PLA is depicted in Fig. 1 as a UML class
diagram which shows the concepts of the PLA, their hierarchy, and their
relationships with each other. The PLA is represented as a class that contains two
subclasses, the rst with information related to the PA and the second with
information related to the citizen. In turn, each section contains a number of
elds that includes information related to the privacy of the citizens' data.
3.1</p>
      <sec id="sec-3-1">
        <title>Public Administration PLA Section</title>
        <p>The PA section has the following elds. For each eld we provide a short
description and we specify them using an xml schema1. The schema enables us
to represent the PLA with the potential to be machine readable and to allow
information systems to further process the information included in the PLA, for
example, for enforcing privacy polices.</p>
        <p>
          Identity : This eld describes the publication of administration's name, place
of establishment, and the contact details of the PA's data controller
administrator. Assigning such a responsibility to an employee of the organisation is
important so that the citizen has a point of contact in case they want to make
a query, contributing to the accountability of the service [
          <xref ref-type="bibr" rid="ref10">10</xref>
          ].
        </p>
        <p>Data: Speci es which personal data the citizen needs to provide to the PA.</p>
        <p>Data processing rights : Provides information about processing and storing of
citizens' data. Acquiring complete information about processing and storing of
their personal data to the PAs' information systems, citizens are fully informed,
e.g., on the location of their stored data, on the processing rights, etc.</p>
        <p>
          Data Sharing Preferences : Provides information about third parties that can
have access to citizens' data, since as the PA has the ability to collect huge
amount of citizen data, this may attract external parties that want to acquire
the data [
          <xref ref-type="bibr" rid="ref10">10</xref>
          ].
1 http://www.sense-brighton.eu/xml_pla/
        </p>
        <p>Data Privacy Measures : Speci es the technical, physical and organisational
measures in place to protect citizens' personal data against accidental or
unlawful destruction or loss, alteration, unauthorised use, modi cation, disclosure of
access, and against all other unlawful forms of processing. These measures can
ensure the satisfaction of the relevant privacy requirements.</p>
        <p>Privacy Threat Analysis : Provides the threat analysis of the PA's privacy
needs and requirements. Citizens need assurances that the PA introduces
appropriate mechanisms and processes to support the privacy needs, and inform
them when these needs are not followed due to either PA policies or legislation.
Having such information improves the transparency of PA's operations in terms
of data management, and it therefore helps to improve citizens' trust.</p>
        <p>
          Privacy Trust Analysis : Provides the trust analysis of the PA's privacy needs
and requirements. Since trust is considered a very important factor for the
adoption of e-government services [
          <xref ref-type="bibr" rid="ref14">14</xref>
          ], PA's have to demonstrate that the
infrastructure and the sta responsible for the operation of the infrastructure can be
trusted [
          <xref ref-type="bibr" rid="ref11 ref8">8,11</xref>
          ].
        </p>
        <p>Law compliance: Provides information on whether privacy requirements are
complaint with privacy laws at a national and EU level. In particular, it speci es
the constraints imposed by regulations and laws and also how the PA
uses/manages citizen data. Also, it veri es if the data management speci ed by the PAs
respects the constraints speci ed in laws and regulations.
3.2</p>
      </sec>
      <sec id="sec-3-2">
        <title>Citizen PLA Section</title>
        <p>The citizen section has the following elds:</p>
        <p>National Public Authority : Contains the details of the National Public
Authority responsible for protecting citizens' personal data rights. Adding such
information to the PLA will raise the awareness of the citizens about the
protection of their data rights by the speci c national public authority.</p>
        <p>
          Citizen Privacy Preferences : Contains the privacy preferences of the citizen
that have been collected by the PA. The study of [
          <xref ref-type="bibr" rid="ref17">17</xref>
          ] reveals that the government
applications that engage citizens and allow interactivity with them, have positive
payo s for trust in government.
        </p>
        <p>History based assessment : Consists of an analysis of the citizens' privacy
preferences and the generation of a prediction of the possible outcomes of subsequent
requests. It contains an estimation of the accepted or denied requests for citizens
data, based on their requirements available and the aggregated statistics about
other citizens, collected up to that moment.</p>
        <p>Data Value: Contains the citizens' perspective concerning their data and the
valuation of citizens' data by the PA and the average valuation of all the citizens.
This information can increase transparency since it communicates to the citizen
the relative value of data and consequently, it will increase the trust of the citizen
in the PA.
4</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>Illustrative example of a Privacy Level Agreement</title>
      <p>To better demonstrate the applicability of the PLA in the context of a PA
information system, we apply the de ned PLA to a real-case study. In this scenario,
a local Public Administration, the Municipality of Athens (MoA), makes use of
their information system MACS (Municipality Athens Citizen System) to
provide e-services to Athenian citizens and to store all their data. Although multiple
services are provided through MACS, in this paper, due to space limitations, we
focus on the e-service related to the issue of a birth certi cate. As part of that
service, the PA supports the creation and enforcement of a PLA. In doing so, the
PA requests that all citizens requiring the birth certi cate e-service are provided
with the option to provide their privacy preferences and create a PLA. The
interaction among the citizen and the PA is depicted in Fig. 2 and described as
follows. A citizen requests the issue of a birth certi cate, using the MACS
system. The MACS receives the request and presents a questionnaire that enables
the citizen to declare their privacy preferences. Based on the citizen's answers,
the PA information system proceeds to the creation of the PLA which is
presented to the citizen. After the citizen has received their personalised PLA, they
are requested by the MACS to give all the necessary data for requesting the
issue of a birth certi cate. The citizen proceeds and provides the MACS with all
the necessary information. The MACS receives the data and, after its storage,
it sends a noti cation to an MoA employee to process the request. When the
request has been processed, then citizen receives their birth certi cate.</p>
      <p>The creation of the PLA requires that all elds described in the previous
section are lled in with relevant information. Some of the elds (such as the
identity and National Public Authority ) can be pre-de ned by the PA. Others,
such as Citizen Privacy Preferences, are lled in based on the answers the citizen
provides to the questionnaire. The rest of the elds are lled in following privacy
related analysis that PA performs using appropriate tools and systems.</p>
      <p>The PLA, depicted in Fig. 3, gives the citizen the ability to be aware of
exactly the data the PA has about them, how this data is processed, with whom
this data will be shared, the privacy mechanisms implemented by the PA along
with the threats that can endanger citizen's privacy and the corresponding
mitigation actions. In addition, the citizen knows the PA employee assigned as the
data controller of their data, has an estimation of the value of their data and
information about past events that enables them to make more informed decisions
about the sharing of their data.
5</p>
    </sec>
    <sec id="sec-5">
      <title>Conclusions</title>
      <p>PAs should realise the importance of the adoption of a privacy culture that
enhances their trustworthiness, by making their systems and procedures
transparent. Towards this goal, the establishment of a PLA can contribute to the
achievement of the desired degree of PAs transparency, increasing the awareness
of citizens concerning the preservation of their personal data and allowing them
to set their preferences concerning the handling of their data.</p>
      <p>The idea of PLA can also be applied in other contexts where online services
are provided, especially in situations where the provision of individuals' personal
data is necessary for the service to be carried out. These contexts can include
relationships between healthcare institutions and patients, business to business,
and customers to business.</p>
      <p>Acknowledgement This research was supported by the Visual Privacy
Management in User Centric Open Environments (VisiOn) project, supported by the
EU Horizon 2020 programme, Grant Agreement No. 653642.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Bouman</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Trienekens</surname>
          </string-name>
          , J.,
          <string-name>
            <surname>Van der Zwan</surname>
          </string-name>
          , M.:
          <article-title>Speci cation of service level agreements, clarifying concepts on the basis of practical research</article-title>
          .
          <source>In: Software Technology and Engineering Practice</source>
          ,
          <year>1999</year>
          . STEP'
          <fpage>99</fpage>
          .
          <string-name>
            <surname>Proceedings</surname>
          </string-name>
          . pp.
          <volume>169</volume>
          {
          <fpage>178</fpage>
          .
          <string-name>
            <surname>IEEE</surname>
          </string-name>
          (
          <year>1999</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Carter</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Belanger</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          :
          <article-title>The utilization of e-government services: citizen trust, innovation and acceptance factors</article-title>
          .
          <source>Information systems journal 15(1)</source>
          ,
          <volume>5</volume>
          {
          <fpage>25</fpage>
          (
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Commission</surname>
          </string-name>
          , E.:
          <article-title>Eurobarometer 431 - data protection report</article-title>
          .
          <source>Tech. rep. (</source>
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4. CSA:
          <article-title>Privacy level agreement outline for the sale of cloud services in the european union</article-title>
          .
          <source>Tech. rep., Cloud Security Alliance</source>
          , Privacy Level Agreement Working Group (
          <year>February 2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>DErrico</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pearson</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Towards a formalised representation for the technical enforcement of privacy level agreements</article-title>
          .
          <source>In: Cloud Engineering (IC2E)</source>
          , 2015 IEEE International Conference on. pp.
          <volume>422</volume>
          {
          <fpage>427</fpage>
          .
          <string-name>
            <surname>IEEE</surname>
          </string-name>
          (
          <year>2015</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Drogkaris</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gritzalis</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lambrinoudakis</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          :
          <article-title>Employing privacy policies and preferences in modern e{government environments</article-title>
          .
          <source>International Journal of Electronic Governance</source>
          <volume>6</volume>
          (
          <issue>2</issue>
          ),
          <volume>101</volume>
          {
          <fpage>116</fpage>
          (
          <year>2013</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Ebrahim</surname>
            ,
            <given-names>Z.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Irani</surname>
            ,
            <given-names>Z.</given-names>
          </string-name>
          :
          <article-title>E-government adoption: architecture and barriers</article-title>
          .
          <source>Business process management journal 11(5)</source>
          ,
          <volume>589</volume>
          {
          <fpage>611</fpage>
          (
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <surname>Horst</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kuttschreuter</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gutteling</surname>
            ,
            <given-names>J.M.:</given-names>
          </string-name>
          <article-title>Perceived usefulness, personal experiences, risk perception and trust as determinants of adoption of e-government services in the netherlands</article-title>
          .
          <source>Computers in Human Behavior</source>
          <volume>23</volume>
          (
          <issue>4</issue>
          ),
          <year>1838</year>
          {
          <year>1852</year>
          (
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9. Keller, A.,
          <string-name>
            <surname>Ludwig</surname>
          </string-name>
          , H.:
          <article-title>The wsla framework: Specifying and monitoring service level agreements for web services</article-title>
          .
          <source>Journal of Network and Systems Management</source>
          <volume>11</volume>
          (
          <issue>1</issue>
          ),
          <volume>57</volume>
          {
          <fpage>81</fpage>
          (
          <year>2003</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Marche</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>McNiven</surname>
            ,
            <given-names>J.D.</given-names>
          </string-name>
          :
          <article-title>E-government and e-governance: the future isn't what it used to be</article-title>
          .
          <source>Canadian Journal of Administrative Sciences/Revue Canadienne des Sciences de l'Administration</source>
          <volume>20</volume>
          (
          <issue>1</issue>
          ),
          <volume>74</volume>
          {
          <fpage>86</fpage>
          (
          <year>2003</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <surname>Milloy</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Fink</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Morris</surname>
          </string-name>
          , R.:
          <article-title>Modeling online security and privacy to increase consumer purchasing intent</article-title>
          .
          <source>In: Informing Science &amp; IT Education Joint Conference (InSITE)</source>
          (
          <year>2002</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <surname>Parliament</surname>
          </string-name>
          , E.:
          <article-title>Regulation (eu) 2016/679 of the european parliament and of the coucil of 27 april 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data</article-title>
          ,
          <source>and repealing directive</source>
          <volume>95</volume>
          /46/ec (general
          <source>data protection regulation)</source>
          (
          <year>2016</year>
          ), http://eur-lex. europa.eu/legal-content/EN/TXT/
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <surname>Sedek</surname>
            ,
            <given-names>K.A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sulaiman</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Omar</surname>
            ,
            <given-names>M.A.</given-names>
          </string-name>
          :
          <article-title>A systematic literature review of interoperable architecture for e-government portals</article-title>
          .
          <source>In: Software Engineering (MySEC)</source>
          ,
          <year>2011</year>
          5th Malaysian Conference in. pp.
          <volume>82</volume>
          {
          <fpage>87</fpage>
          .
          <string-name>
            <surname>IEEE</surname>
          </string-name>
          (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <surname>Srivastava</surname>
            ,
            <given-names>S.C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Teo</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          :
          <article-title>Citizen trust development for e-government adoption: Case of singapore</article-title>
          .
          <source>PACIS 2005</source>
          Proceedings p.
          <volume>59</volume>
          (
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <surname>Tambouris</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Archetypon</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wimmer</surname>
            ,
            <given-names>G.M.:</given-names>
          </string-name>
          <article-title>Online one-stop government: A single point of access to</article-title>
          .
          <source>Electronic government strategies and implementation</source>
          p.
          <volume>115</volume>
          (
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16. (
          <issue>W3C</issue>
          ), W.W.W.C.:
          <article-title>Platform for privacy preferences (p3p) project (</article-title>
          <year>2016</year>
          ), https: //www.w3.org/P3P/
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <surname>Welch</surname>
            ,
            <given-names>E.W.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hinnant</surname>
            ,
            <given-names>C.C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Moon</surname>
          </string-name>
          , M.J.:
          <article-title>Linking citizen satisfaction with egovernment and trust in government</article-title>
          .
          <source>Journal of public administration research and theory 15</source>
          (
          <issue>3</issue>
          ),
          <volume>371</volume>
          {
          <fpage>391</fpage>
          (
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>