summaryrefslogtreecommitdiff
path: root/eut.raw
blob: a5d2f08980b39379b2140ef6bef050fc43a495e3 (plain) 
    

  1. <!DOCTYPE html>
    2. 

  2. <html lang="en" dir="ltr" class="client-nojs">
    3. 

  3. <head>
    4. 

  4. <meta charset="UTF-8" />
    5. 

  5. <title>View source for EUT/2nd-edition - EU-wiki</title>
    6. 

  6. <meta http-equiv="X-UA-Compatible" content="IE=EDGE" />
    7. 

  7. <meta name="generator" content="MediaWiki 1.23.3" />
    8. 

  8. <meta name="robots" content="noindex,nofollow" />
    9. 

  9. <link rel="shortcut icon" href="/favicon.ico" />
    10. 

  10. <link rel="search" type="application/opensearchdescription+xml" href="/w/opensearch_desc.php" title="EU-wiki (en)" />
    11. 

  11. <link rel="EditURI" type="application/rsd+xml" href="http://en.euwiki.org/w/api.php?action=rsd" />
    12. 

  12. <link rel="alternate" type="application/atom+xml" title="EU-wiki Atom feed" href="/w/index.php?title=Special:RecentChanges&amp;feed=atom" />
    13. 

  13. <link rel="stylesheet" href="http://en.euwiki.org/w/load.php?debug=false&amp;lang=en&amp;modules=mediawiki.legacy.commonPrint%2Cshared%7Cmediawiki.skinning.interface%7Cmediawiki.ui.button%7Cskins.monobook.styles&amp;only=styles&amp;skin=monobook&amp;*" />
    14. 

  14. <!--[if IE 6]><link rel="stylesheet" href="/w/skins/monobook/IE60Fixes.css?303" media="screen" /><![endif]-->
    15. 

  15. <!--[if IE 7]><link rel="stylesheet" href="/w/skins/monobook/IE70Fixes.css?303" media="screen" /><![endif]--><meta name="ResourceLoaderDynamicStyles" content="" />
    16. 

  16. <style>a:lang(ar),a:lang(kk-arab),a:lang(mzn),a:lang(ps),a:lang(ur){text-decoration:none}
    17. 

  17. /* cache key: new_euwiki-en_:resourceloader:filter:minify-css:7:7c2ee0c606b1353543b5ce882fb1bb3b */</style>
    18. 

  18. <script src="http://en.euwiki.org/w/load.php?debug=false&amp;lang=en&amp;modules=startup&amp;only=scripts&amp;skin=monobook&amp;*"></script>
    19. 

  19. <script>if(window.mw){
    20. 

  20. mw.config.set({"wgCanonicalNamespace":"","wgCanonicalSpecialPageName":false,"wgNamespaceNumber":0,"wgPageName":"EUT/2nd-edition","wgTitle":"EUT/2nd-edition","wgCurRevisionId":17563,"wgRevisionId":0,"wgArticleId":5353,"wgIsArticle":false,"wgIsRedirect":false,"wgAction":"edit","wgUserName":null,"wgUserGroups":["*"],"wgCategories":[],"wgBreakFrames":true,"wgPageContentLanguage":"en","wgPageContentModel":"wikitext","wgSeparatorTransformTable":["",""],"wgDigitTransformTable":["",""],"wgDefaultDateFormat":"dmy","wgMonthNames":["","January","February","March","April","May","June","July","August","September","October","November","December"],"wgMonthNamesShort":["","Jan","Feb","Mar","Apr","May","Jun","Jul","Aug","Sep","Oct","Nov","Dec"],"wgRelevantPageName":"EUT/2nd-edition","wgIsProbablyEditable":false,"wgRestrictionEdit":[],"wgRestrictionMove":[]});
    21. 

  21. }</script><script>if(window.mw){
    22. 

  22. mw.loader.implement("user.options",function($,jQuery){mw.user.options.set({"ccmeonemails":0,"cols":80,"date":"default","diffonly":0,"disablemail":0,"editfont":"default","editondblclick":0,"editsectiononrightclick":0,"enotifminoredits":0,"enotifrevealaddr":0,"enotifusertalkpages":1,"enotifwatchlistpages":1,"extendwatchlist":0,"fancysig":0,"forceeditsummary":0,"gender":"unknown","hideminor":0,"hidepatrolled":0,"imagesize":2,"math":1,"minordefault":0,"newpageshidepatrolled":0,"nickname":"","norollbackdiff":0,"numberheadings":0,"previewonfirst":0,"previewontop":1,"rcdays":7,"rclimit":50,"rows":25,"showhiddencats":0,"shownumberswatching":1,"showtoolbar":1,"skin":"monobook","stubthreshold":0,"thumbsize":2,"underline":2,"uselivepreview":0,"usenewrc":0,"watchcreations":1,"watchdefault":1,"watchdeletion":0,"watchlistdays":3,"watchlisthideanons":0,"watchlisthidebots":0,"watchlisthideliu":0,"watchlisthideminor":0,"watchlisthideown":0,"watchlisthidepatrolled":0,"watchmoves":0,"wllimit":250,
    23. 

  23. "useeditwarning":1,"prefershttps":1,"language":"en","variant-gan":"gan","variant-iu":"iu","variant-kk":"kk","variant-ku":"ku","variant-shi":"shi","variant-sr":"sr","variant-tg":"tg","variant-uz":"uz","variant-zh":"zh","searchNs0":true,"searchNs1":false,"searchNs2":false,"searchNs3":false,"searchNs4":false,"searchNs5":false,"searchNs6":false,"searchNs7":false,"searchNs8":false,"searchNs9":false,"searchNs10":false,"searchNs11":false,"searchNs12":false,"searchNs13":false,"searchNs14":false,"searchNs15":false,"searchNs274":false,"searchNs275":false,"searchNs828":false,"searchNs829":false,"variant":"en"});},{},{});mw.loader.implement("user.tokens",function($,jQuery){mw.user.tokens.set({"editToken":"+\\","patrolToken":false,"watchToken":false});},{},{});
    24. 

  24. /* cache key: new_euwiki-en_:resourceloader:filter:minify-js:7:adba14c0d9d371c7fb6643bc48c5a21a */
    25. 

  25. }</script>
    26. 

  26. <script>if(window.mw){
    27. 

  27. mw.loader.load(["mediawiki.page.startup","mediawiki.legacy.wikibits","mediawiki.legacy.ajax"]);
    28. 

  28. }</script>
    29. 

  29. </head>
    30. 

  30. <body class="mediawiki ltr sitedir-ltr ns-0 ns-subject page-EUT_2nd-edition skin-monobook action-edit">
    31. 

  31. <div id="globalWrapper">
    32. 

  32. <div id="column-content"><div id="content" class="mw-body-primary" role="main">
    33. 

  33.     <a id="top"></a>
    34. 

  34.     
    35. 

  35.     <h1 id="firstHeading" class="firstHeading" lang="en"><span dir="auto">View source for EUT/2nd-edition</span></h1>
    36. 

  36.     <div id="bodyContent" class="mw-body">
    37. 

  37.         <div id="siteSub">From EU-wiki</div>
    38. 

  38.         <div id="contentSub">← <a href="/EUT/2nd-edition" title="EUT/2nd-edition">EUT/2nd-edition</a></div>
    39. 

  39.         <div id="jump-to-nav" class="mw-jump">Jump to: <a href="#column-one">navigation</a>, <a href="#searchInput">search</a></div>
    40. 

  40. 

  41.         <!-- start content -->
    42. 

  42. <div id="mw-content-text"><p>You do not have permission to edit this page, for the following reason:
    43. 

  43. </p>
    44. 

  44. <div class="permissions-errors">
    45. 

  45. <p>The action you have requested is limited to users in one of the groups: <a href="/w/index.php?title=EU-wiki:Bots&amp;action=edit&amp;redlink=1" class="new" title="EU-wiki:Bots (page does not exist)">Bots</a>, <a href="/w/index.php?title=EU-wiki:Administrators&amp;action=edit&amp;redlink=1" class="new" title="EU-wiki:Administrators (page does not exist)">Administrators</a>, staff.
    46. 

  46. </p>
    47. 

  47. </div>
    48. 

  48. <hr />
    49. 

  49. <p>You can view and copy the source of this page:
    50. 

  50. </p><textarea readonly="" accesskey="," id="wpTextbox1" cols="80" rows="25" style="" lang="en" dir="ltr" name="wpTextbox1">&lt;table align="center" border="1">&lt;tr>&lt;td>
    51. 

  51. &lt;table align="center" bgcolor="#f9cc77">
    52. 

  52. &lt;tr>
    53. 

  53. &lt;td>Work in progress on 2nd edition&lt;/td>
    54. 

  54. &lt;/tr>
    55. 

  55. &lt;/table>
    56. 

  56. &lt;/td>&lt;/tr>&lt;/table>
    57. 

  57. 

  58. 

  59. = About =
    60. 

  60. 

  61. The study "''Ensuring utmost transparency — Free Software and Open Standards under the Rules of Procedure of the European Parliament''" has been produced at the request of the Greens/EFA Group in the European Parliament by Carlo Piana&lt;ref name="Carlo Piana">'''Carlo Piana''' is an Italian qualified attorney based in Milano, founder of [http://array.eu Array] and specializing in Information Technology Law. He also serves in the Editorial Committee of the Free and Open Source Software Law Review [http://www.ifosslr.org Ifosslr] {{cite web|title=Carlo Piana|url=http://en.wikipedia.org/wiki/Carlo_Piana|accessdate=14 October 2014}}&lt;/ref> and Ulf Öberg&lt;ref name="Ulf Öberg">'''Ulf Öberg''' is Founder and Managing Partner of the law firm Öberg &amp; Associés. He is specialised in EU and Competition law and has extensive trial experience before the EU Courts, Swedish courts and European Court of Human Rights. {{cite web|title=Ulf Öberg|url=http://www.obergassocies.eu/en/about-us/ulf-oberg|accessdate=14 October 2014}}&lt;/ref> under the supervision&lt;ref>From {{cite web|title=Greens/EFA commissions "Rule 103" study|url=http://icg.greens-efa.eu/pipermail/hub/2014-May/000130.html|accessdate=12 October 2014|ref=Greens/EFA Internet Core Group public mailing list}}&lt;/ref> of Professor Douwe Korff&lt;ref name="Douwe Korff">'''Professor Douwe Korff''' is an Associate of the [http://www.oxfordmartin.ox.ac.uk/people/578 Oxford Martin School] of the University of Oxford and a member of the cybersecurity working group of its Global Cybersecurity Capacity Centre; a [http://isp.yale.edu/douwe-korff Visiting Fellow] at Yale University (in its Information Society Project); and a [https://cihr.eu/people/ Fellow] of the Centre for Internet &amp; Human Rights of the European University Viadrina in Berlin.&lt;/ref>. The viewpoints in this study belong to the authors and the authors alone.
    62. 

  62. 

  63. The study has been open for public review on euwiki.org from 15 October till 15 November 2014. Online support during the review period has been provided by Jonatan Walck&lt;ref name="Jonatan Walck">'''Jonatan Walck''' is a computer and computer networks specialist working with [https://web.archive.org/web/20141214070422/http://www.netnod.se/new-staff-netnod/ system administration and development of internet-connected services, hardware-software integration and electronics]. He is a founding member the Swedish non-profit [https://web.archive.org/web/20090923123947/http://juliagruppen.se/lang/en/om-juliagruppen/vi-ar-juliagruppen/ Juliagruppen] and a long term [https://web.archive.org/web/20130312211020/https://fscons.org/2012/people/jonatan-walck/ advocate for a free and open internet].&lt;/ref>.
    64. 

  64. 

  65. The cover illustration has been created by Siri Reiter&lt;ref name="Siri Reiter">'''Siri Reiter''' is a [http://sirireiter.dk/ graphic designer, illustrator and artist]. She graduated at [https://www.designskolenkolding.dk/en Kolding School of Design] and works primarily from Orø, Denmark.&lt;/ref> based on a photograph provided by the European Parliament's Audiovisual Services for Media who also holds the copyright of the original&lt;ref>European Parliament's Audiovisual Services for Media hosts the the photograph used for the illustration. Link: http://audiovisual.europarl.europa.eu/Assetdetail.aspx?id=3a50e246-d3c4-4ae8-9068-ce3249307d15&lt;/ref>.
    66. 

  66. 

  67. The work and the cover illustration are licensed under the Creative Commons Attribution-ShareAlike 4.0 International License.
    68. 

  68. 

  69. = Table of Contents =
    70. 

  70. __TOC__
    71. 

  71. 

  72. = Foreword =
    73. 

  73. '''''By Professor Douwe Korff'''''
    74. 

  74. 

  75. This report is timely, and deals with an important issue in an era of widespread disillusionment with and distrust of politics and political institutions (or at least politicians). "Utmost transparency" has the potential to strengthen accountability and increase popular participation in the democratic processes. The report links this principle with the technical standards and practical steps that can be taken to ensure its full implementation – or that can effectively limit access. As the authors of this study point out, there is a difference between the somewhat legalistic right of access to information ("freedom of information") on an ad hoc, on-request basis, and general openness and transparency. The former right allows entrance to an in-principle closed building, or to closed rooms within closed buildings, on request, subject to limitations; the latter removes entire walls and allows daylight to permeate to all corners. Parliament’s duty to ensure "utmost transparency" clearly demands the latter rather than just the former.
    76. 

  76. 

  77. In order to elucidate the relevant requirements, the authors provide excellent overviews of a large number of widely diverging and complex issues relevant to the topic: human rights law, EU law ranging from the Charter of Fundamental Rights to EC directives on public sector information and Commission decisions on data re-use, copyright, patents and protection of databases, principles of good governance, transparency standards relating to the environment (Aarhus), the G8 Open Data Charter and others on the mainly legal and governance standards side; the European Interoperability Framework (versions 1 and 2), open standards (as variously formally defined) and "semi-formal" RFCs, FOSS and email system requirements on the more practical, technical side. They have looked at relevant rules and practices in a range of countries including India, Sweden and the UK.
    78. 

  78. 

  79. Crucially, the authors have managed to draw on all these sources to indicate clearly what should be done in practical, technical terms by the officials managing the information and IT systems relating to the work of the European Parliament to truly and fully achieve the legal requirement of "utmost transparency". This report will become a major point of reference for the debates on those steps. It is to be greatly commended for having taken the issue seriously (rather than just rely on all-too-easy slogans or political rallying cries). It cannot be dismissed by those with the power to take action. Rather, it should lead to Parliament clearly instructing its civil servants to take the steps needed to achieve the "utmost transparency" required of the institution. The recommendations should be fully implemented: that will enhance democracy, accountability and public participation, and trust in the Union at a time of doubt and insecurity.
    80. 

  80. 

  81. '''''London 15 November 2014'''''
    82. 

  82. 

  83. = Scope and method of analysis=
    84. 

  84. 

  85. This study arises from a proposal by the Greens/EFA, backed by two Plenary decisions, that the European Parliament investigates its own transparency obligations under its Rules of Procedure with regard to Free Software and Open Standards. &lt;ref>"The Greens/EFA group in the European Parliament has commissioned a study into the implications of Rule 103 of the European Parliament's Rules of Procedure for the Parliament's decisions, policies, procedures, etc., with regard to Free Software and Open Standards [...] The study will assess whether, and if so how and to what extent, Rule 103 can inform the EP's ICT decisions, policies, procedures, etc. (including procurement decisions) with regard to Free Software and Open Standards." From {{cite web|title=Greens/EFA commissions "Rule 103" study|url=http://icg.greens-efa.eu/pipermail/hub/2014-May/000130.html|accessdate=12 October 2014|ref=Greens/EFA Internet Core Group public mailing list}}&lt;/ref>
    86. 

  86. 

  87. The scope is therefore to verify whether, in general or in single areas, the principle of openness and the right of access to information mandates, and if so to what extent, the use of Free Software and Open Standards, or what kind of preference towards it, if any.
    88. 

  88. 

  89. Distilling general principles and propositions into practical guidelines is largely a matter of political decisions, therefore extraneous to this study. Conversely, the aim of this study is to bridge the gap between an overly laconic provision and the strategical administration of the IT, by utilising the available information in different trajectories.
    90. 

  90. 

  91. The first trajectory is top-down, and analyses the principle of openness from a constitutional point of view. This aims to provide the cardinal points to the rest of the analysis.
    92. 

  92. 

  93. The second trajectory is lateral, and aims to retrieve useful material from neighbouring areas, both in terms of policy and legislation, that could be useful to define a sort of ''"acquis"'' in terms of openness of EU bodies and institutions, where available and relevant.
    94. 

  94. 

  95. The third trajectory is bottom-up, and analyses single areas of IT, which have been discussed in the recent past or can be exemplary, their possible failures and shortcomings in terms of openness and possible actions and directions to solve the situation.
    96. 

  96. 

  97. Finally, as the study analyses the inference between the principle of openness and Free Software and Open Standards, a short description of what they are cannot be avoided.
    98. 

  98. 

  99. Although similar in concept, this study only addresses the adjacent area of "Right to Access" or "Freedom of Information" in so far it is relevant for the understanding of the Principle of Openness in EU law, and its possible requirements for the discussion on Free Software and Open Standards. Access to document procedures are laid down the Regulation (EC) No 1049/2001&lt;ref>Regulation (EC) No 1049/2001 of the European Parliament and of the Council of 30 May 2001 regarding public access to European Parliament, Council and Commission documents http://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32001R1049&amp;from=EN&lt;/ref> and by Rule 116&lt;ref>Rules of Procedure of the European Parliament, TITLE IV : TRANSPARENCY OF BUSINESS, Rule 116 : Public access to documents http://www.europarl.europa.eu/sides/getDoc.do?pubRef=-//EP//TEXT+RULES-EP+20140701+RULE-116+DOC+XML+V0//EN&amp;language=EN&amp;navigationBar=YES&lt;/ref>, and are not as such material to this study. Undoubtedly the right of access to documents is an useful complement to openness as it ensures that the openness is achieved in full, by providing means to take an active role in disclosing facts and documents that are withheld from public view and should not. However, the access to documents mechanism proceeds by formal questions and answers, whereas the openness is evidently a more dynamic and holistic process that does not depend on legal actions and requests by individuals.
    100. 

  100. 

  101. Therefore, the right to access to documents as such is only treated insofar as it provides useful information for the application of the principle of openness in practice on the debate on Free Software and Open Standards.
    102. 

  102. 

  103. = The Constitutional Principle of Openness under European Law =
    104. 

  104. 

  105. == Parliament has Imposed upon Itself a Commitment to Conduct its Activities with the Utmost Transparency ==
    106. 

  106. 

  107. Rule 115 of the Rules of Procedure of the European Parliament provides that:
    108. 

  108. 

  109. &lt;blockquote>Parliament shall ensure that its activities are conducted with the utmost transparency, in accordance with the second paragraph of Article 1 of the Treaty on European Union, Article 15 of the Treaty on the Functioning of the European Union and Article 42 of the Charter of Fundamental Rights of the European Union.&lt;ref>Rules of Procedure of the European Parliament, TITLE IV : TRANSPARENCY OF BUSINESS, Rule 115 : Transparency of Parliament's activities http://www.europarl.europa.eu/sides/getDoc.do?pubRef=-//EP//TEXT+RULES-EP+20140701+RULE-115+DOC+XML+V0//EN&amp;language=EN&amp;navigationBar=YES&lt;/ref>&lt;/blockquote>
    110. 

  110. 

  111. The European Parliament has been a champion in promoting not only openness of the legislative process and the access to legislative documents, but also that the EU Courts should accept that openness constitutes a general principle of EU law, and that the right to information is as such a fundamental human right. In Netherlands v Council, the European Parliament argued as follows:
    112. 

  112. 

  113. &lt;blockquote>In this connection, the Parliament avers that, whilst it is competent for the institutions to adopt appropriate measures for their internal organization with a view to ensuring their sound operation and the proper conduct of their procedures, the principle of openness of the legislative process and the access to legislative documents entailed thereby constitute essential requirements of democracy and therefore cannot be treated as organizational matters purely internal to the institutions. In this context, the Parliament adverts to the democratic nature of the Community legal order. It maintains moreover that the requirement for openness constitutes a general principle common to the constitutional traditions of the Member States which is also enshrined in Community law. Lastly, it argues that the right to information, of which access to documents constitutes the corollary, is a fundamental human right recognized by various international instruments.&lt;ref>Case C-58/94 Netherlands v Council [1996] ECLI:EU:C:1996:171 at para 18.&lt;/ref>&lt;/blockquote>
    114. 

  114. 

  115. In its judgment, the Court stressed that the domestic legislation of most Member States enshrines, in a general manner, the public’s right of access to documents held by public authorities as a constitutional or legislative principle. The Court found that this trend "discloses a progressive affirmation of individuals’ right of access to documents held by public authorities" and that accordingly, the Council deemed it necessary to amend the rules governing its internal organisation, which had hitherto been based on the principle of confidentiality. The Court added that, "so long as the Community legislature has not adopted general rules on the right of public access to documents held by the Community institutions, the institutions must take measures as to the processing of such requests by virtue of their power of internal organisation, which authorises them to take appropriate measures in order to ensure their internal operation in conformity with the interests of good administration".
    116. 

  116. 

  117. While dated, this analysis is still interesting for at least three reasons. First, the legal doctrine is divided as to whether or not it is possible to interpret the Netherlands v Council judgment as authority for the existence of a fundamental right of access to documents.&lt;ref>See in that regard, for example, Chiti, E., "Further Developments of Access to Community Information: Kingdom of the Netherlands v. Council of the European Union", European Public Law, Vol. 2, No 4, 1996, p. 536 et seq.; Lafay, F., "L'accès aux documents du Conseil de l'Union: contribution à une problématique de la transparence en droit communautaire", RTD eur. 33(1), January-March 1997, p. 37 et seq.; Bradley, K. St. C., "La transparence de l'Union européenne: une évidence ou un trompe-l'oeil?", Cahier de droit européen, 3-4, 1999, p. 283 et seq.; Travers, N., "Access to Documents in Community law: on the road to a European participatory democracy", The Irish Jurist, Vol. 35, 2000, p. 164 et seq. For a different interpretation, see, for example, Ragnemalm, H., "Démocratie et transparence: sur le droit général d'accès des citoyens de l'Union européenne aux documents détenus par les institutions communautaires", Scritti in onore di G. F. Mancini, p. 809 et seq., Öberg, U., EU Citizen’s Right to Know: The Improbable Adoption of a European Freedom of Information Act, Cambridge Yearbook of European Legal Studies, Vol. 2, 1999, s. 303-328&lt;/ref> Second, when interpreting Rule 115, the relevant legal question is whether or not internal rules of the institutions may confer a substantive legal right to access to documents, to information, and/or to data on EU citizens. Third, the Court clearly links the issue of public access to documents to the nascent principle of good administration.
    118. 

  118. 

  119. According to the case law of the Court, the purpose of the Community institutions’ internal Rules of Procedure is to organise the internal functioning of its services in the interests of good administration. The essential purpose of such rules, particularly those with regard to the organisation of deliberations and the adoption of decisions, is to ensure the smooth conduct of the decision-making procedure. It follows that natural or legal persons may normally not rely on an alleged breach of such rules, as they are not intended to ensure protection for individuals.
    120. 

  120. 

  121. Therefore, internal rules cannot be regarded as measures conferring on European citizens a substantive right of access to documents, to information, or to data held by the EU institutions. They are not intended to vest in European citizens a formal ”right to know” what is going on within the European institutions, which is a prerequisite in a participatory democracy, where decisions are taken "as closely as possible to the citizen”. In the absence of general rules on the right of public access to information or to data held by the EU institutions, European citizens’ ”right to know” and to participate ”as closely as possible” in the decision-making process must therefore be found elsewhere.
    122. 

  122. 

  123. As a preliminary conclusion, Rule 115 does not in itself confer any rights on European citizens. Nevertheless, as compliance with internal Rules of Procedure may constitute an essential procedural requirement, and may in some circumstances have legal effects vis-à-vis third parties, their breach can give rise to an action for annulment before the EU Courts. Indeed, procedural rules laid down in Rule 115 constitutes an essential procedural requirement within the meaning of the second paragraph of Article 263 TFEU and its infringement leads to the nullity of the measure thereby vitiated.
    124. 

  124. 

  125. In the light of the Court's judgment in European Parliament v. Council, that rule is an expression of the democratic principles on which the European Union is founded. In particular, the Court has already stated that the Parliament’s involvement in the decision-making process is the reflection, at the EU level, of the fundamental democratic principle that the people should participate in the exercise of power through the intermediary of a representative assembly.&lt;ref>judgment European Parliament v. Council EU:C:2014:2025, paragraph 80-81&lt;/ref> Not only has Parliament imposed upon itself that it shall ensure that its activities are conducted with the utmost transparency, but its actions shall also conform with the Principle of Openness enshrined in the Treaties and in the Charter, and the Right of Access to Information in Art. 10 of the European Convention for the Protection of Human Rights and Fundamental Freedoms (ECHR).
    126. 

  126. 

  127. == The Principle of Openness and the Right of Access to Information: A Basis for Imposing Free Software and Open Standards ? ==
    128. 

  128. 

  129. The first real step towards allowing the public a right of access to documents held by the Community institutions dates back to 7 February 1992 when the Member States signed the Final Act to the Maastricht Treaty.&lt;ref>Broberg, M., Access to documents: a general principle of Community law?, European Law Review (2002), pp. 196, 197&lt;/ref>. In Declaration No. 17 to that Act, the Member States pointed to the close connection between the transparency of the decision-making process and the democratic nature of the Community institutions. Nowadays, the principle of openness in European Union law has solid roots, as the very text of the Rule 115 makes clear, in the fundamental Treaties of the European Union.
    130. 

  130. 

  131. === The Treaties ===
    132. 

  132. 

  133. Article 1(2) and Article 10(3) of the Treaty establishing the European Union (TEU) states that in the European Union decisions are to be taken as "openly as possible" and ''as closely as possible'' to the citizen.
    134. 

  134. 

  135. In this respect, Article 15(1) TFEU states that in order to promote good governance and ensure the participation of civil society, the Union’s institutions, bodies, offices and agencies are to conduct their work as openly as possible. According to the first subparagraph of Article 15(3) TFEU, any citizen of the Union, and any natural or legal person residing in or having its registered office in a Member State, is to have a right of access to documents of the Union’s institutions, bodies, offices, and agencies, whatever their medium, subject to the principles and the conditions to be defined in accordance with that paragraph. Moreover, according to the second subparagraph of Article 15(3), the general principles and limits on grounds of public or private interest governing this right of access to documents are to be determined by the European Parliament and the Council of the European Union, by means of regulations, acting in accordance with the ordinary legislative procedure. In accordance with the third subparagraph of Article 15(3) TFEU, each institution, body, office or agency is to ensure that its proceedings are transparent and is to elaborate in its own Rules of Procedure specific provisions regarding access to its documents, in accordance with the regulations referred to in the second subparagraph of Article 15(3) TFEU.
    136. 

  136. 

  137. It should be noted at the outset that the General Court has held that Article 1, para. 2 EU and Article 255 EC did not have direct effect, and could therefore not form the basis of a request for disclosure of a document of an institution. The first provision was not regarded as "clear"&lt;ref>Within the meaning of the judgment in Case 26/62 Van Gend en Loos [1963] ECR 1&lt;/ref>, and the second was not considered to lay down an unconditional obligation, since its implementation was held to be dependent on the adoption of subsequent measures. &lt;ref>Case T‑191/99 Petrie and Others v Commission [2001] ECR II‑3677, paragraph 34-38 and Joined Cases T‑3/00 and T‑337/04 Pitsiorlas v Council and ECB [2007] ECR II‑4779&lt;/ref> 
    138. 

  138. 

  139. In a different strand of its case-law, the General Court has referred to the "principle of the right to information" &lt;ref>Case T‑14/98 Hautala v Council [1999] ECR II‑2489, paragraph 87&lt;/ref>, and to the "principle of transparency" &lt;ref> Case T‑211/00 Kuijer v Council [2002] ECR II‑485, paragraph 52&lt;/ref>, in support of a finding that the previous internal rules of access to documents of the institutions must be interpreted in the light of the "principle of the right to information" and the principle of proportionality. The issue has obviously divided the General Court, which has also stated:
    140. 

  140. 

  141. &lt;blockquote>For the purpose of applying Article 4 of Regulation EC No 1049/2001 regarding public access to European Parliament, Council and Commission documents, the concept of a document must be distinguished from that of information. The public’s right of access to the documents of the institutions covers only documents and not information in the wider meaning of the word and does not imply a duty on the part of the institutions to reply to any request for information from an individual.&lt;ref>Case T 264/04 WWF European Policy Programme v Council [2007] ECR II-911 at para 76.&lt;/ref>&lt;/blockquote>
    142. 

  142. 

  143. To date, no clear guidance on this issue has been provided by the Court. In Council v Hautala, the Court did not find it necessary to rule on "the existence of a principle of the right to information" in European Union law.&lt;ref>Case C‑353/99 P Council v Hautala [2001] ECR I‑9565, paragraph 31&lt;/ref>
    144. 

  144. 

  145. Based on this lack of clarity in the case-law of the EU Courts, in Pitsiorlas v Council and ECB, the ECB contested the very existence in EU law of a fundamental legal principle which provides for a general right of access to its documents and to those of the EU institutions. It argued that although arguments based on such a principle have been raised on numerous occasions before the EU judicature, none of the EU Courts has considered it appropriate to examine them. 
    146. 

  146. 

  147. In its judgement, the General Court held that "even supposing that the right of access to the documents held by the Community public authorities, including the ECB, may be regarded as a fundamental right protected by the Community legal order as a general principle of law", the plea of illegality in respect of Article 23.3 of the ECB Rules of Procedure, based on the alleged infringement of such a principle, could not be upheld. The General Court pointed out that fundamental rights cannot be understood as "unfettered prerogatives" and that it is "legitimate that these rights should, if necessary, be subject to certain limits justified by the overall objectives pursued by the Community, on condition that the substance of these rights is left untouched" &lt;ref>Case 4/73 Nold v Commission [1974] ECR 491, paragraph 14&lt;/ref>. The General Court held that, as regards the right of access to documents, reasons related to the protection of the public interest or a private interest may legitimately restrict that right.&lt;ref>Pitsiorlas v Council and ECB, paragraph 221-223&lt;/ref> 
    148. 

  148. 

  149. Be that as it may. As Advocate General Poiares Maduro has correctly pointed out, the fact remains that henceforth the existence of the right of access to documents of the institutions is no longer based on internal measures adopted by the institutions, with which they are bound to comply, or even on Regulation 1049/2001, but on a provision of constitutional import.&lt;ref>Sweden v Commission, C‑64/05 P, EU:C:2007:802&lt;/ref> The Court has in this regard clarified that the "principle of openness" stated in a general manner in the second paragraph of Article 1 TEU is "crystallised" by Regulation 1049/2001.&lt;ref >Commission v Agrofert Holding EU:C:2012:394, paragraph 88 &lt;/ref> An alleged infringement of the second paragraph of Article 1 TEU is therefore in the Court's view not distinct from a plea alleging a wrongful application of the exceptions referred to in Regulation No 1049/2001.
    150. 

  150. 

  151. The existence of a "principle of openness" is confirmed by Art. 15 of the Treaty on the Functioning of the European Union, which states:
    152. 

  152. 

  153. &lt;blockquote>In order to promote good governance and ensure the participation of civil society, the Union institutions, bodies, offices and agencies ''shall conduct their work as openly as possible''. [emphasis added]&lt;/blockquote>
    154. 

  154. 

  155. === Charter of Fundamental Rights of the European Union ===
    156. 

  156. 

  157. Similarly, Article 42 of the Charter of Fundamental Rights of the European Union proclaimed in Nice on 7 December 2000 (‘Charter of Fundamental Rights’) also acknowledges this right:
    158. 

  158. 

  159. &lt;blockquote>Any citizen of the Union, and any natural or legal person residing or having its registered office in a Member State, has a right of access to documents of the institutions, bodies, offices and agencies of the Union, whatever their medium.&lt;/blockquote>
    160. 

  160. 

  161. Article 42 of the Charter of Fundamental Rights of the European Union (‘the Charter’), Article 15(3) TFEU and Article 2(1) of Regulation No 1049/2001 thereby establish a right of access to documents of the institutions. In the context of the European Parliament documents, it should be noted that Article 4 of the Statute for Members of the European Parliament&lt;ref>OJ 2005 L 262, p. 1&lt;/ref> provides that documents and electronic records which a Member has received, drafted or sent are not to be treated as Parliament documents unless they have been tabled in accordance with the Rules of Procedure. As Advocate general Kokkot has noted, the documents relating to a legislative procedure which are in the possession of a rapporteur must in principle be regarded as being in the possession of the Parliament. It will at some point in time be necessary to decide whether Article 15 TFEU and Article 42 of the Charter of Fundamental Rights of the European Union allow such documents to be excluded from the right of access in the future.&lt;ref>Opinion Afton Chemical EU:C:2010:258&lt;/ref>
    162. 

  162. 

  163. Moreover, Art. 10 TEU regarding the principle of democracy (especially Article 10(3), echoes the second paragraph of Article 1) and Article 15 TFEU, dealing with good governance, openness, transparency and access to documents.
    164. 

  164. 

  165. === Article 10 in the European Convention of Human Rights ===
    166. 

  166. 

  167. The development of the principle of openness in EU law has been accompanied by a parallel development of the case law of the European Court of Human Rights. In Guerra and Others v. Italy, the Strasbourg Court held that freedom to receive information under Art. 10 of the ECHR merely prohibited a State from restricting a person from receiving information that others wished or might be willing to impart to him. It states that freedom could not be construed as imposing on a State, in the circumstances of that case, positive obligations to collect and disseminate information of its own motion &lt;ref>See Guerra and Others v. Italy, 19 February 1998, § 53, Reports of Judgments and Decisions 1998‑I).&lt;/ref> Similarly, Társaság a Szabadságjogokért concerned a request for access to information by a non-governmental organisation for the purposes of contributing to public debate. Here, the Court noted that it had recently advanced towards a broader interpretation of the notion of the “freedom to receive information” and thereby towards the recognition of a right of access to information.&lt;ref>Társaság a Szabadságjogokért v. Hungary, no. 37374/05, § 44, 14 April 2009.&lt;/ref>
    168. 

  168. 

  169. In a recent judgment of 25 June 2013, for the case of Youth Initiative for Human Rights v Serbia,&lt;ref>Application no. 48135/06, http://hudoc.echr.coe.int/sites/eng/pages/search.aspx?i=001-120955&lt;/ref>, the Court unanimously recalled, in its reasoning on admissibility, that the notion of “freedom to receive information” embraces a "right of access to information". The judgment has, in our view correctly, been interpreted as having "established implicitly the right of access”, in that the notion of “freedom to receive information” embraces a right of access to information.&lt;ref>European Parliament Policy Department C on request by the Committee on Civil Liberties, Justice and Home Affairs (LIBE): Openness, transparency and access to documents and information in the European Union, available at http://www.europarl.europa.eu/RegData/etudes/note/join/2013/493035/IPOL-LIBE_NT%282013%29493035_EN.pdf ; see also Dirk Voorhoof, Article 10 of the Convention includes the right of access to data held by an intelligence agency, accessible via http://strasbourgobservers.com/2013/07/08/article-10-of-the-convention-includes-the-right-of-access-to-data-held-by-intelligence-agency/&lt;/ref>
    170. 

  170. 

  171. In a concurring opinion, judges Sajó and Vučinić highlighted the general need to interpret Article 10 in conformity with developments in international law regarding freedom of information, which entails access to information held by public bodies referring, in particular, to Human Rights Committee, General Comment No. 34 &lt;ref>Document CCPR/C/GC/34 of 12 September 2011, §§ 18, 3, 15)&lt;/ref>.
    172. 

  172. 

  173. The Human Rights Committee has in turn stressed both the proactive and the reactive dimensions of the freedom of expression and freedom of information. Article 19, paragraph 2 embraces a right of access to information held by public bodies. Such information includes records held by a public body, regardless of the form in which the information is stored, its source, and the date of production. As the Committee has observed in its General Comment No. 16, regarding Article 17 of the Covenant, every individual should have the right to ascertain in an intelligible form, whether, and if so, what personal data is stored in automatic data files, and for what purposes. Paragraph 3 of the General Comment No. 34 provides as follows:
    174. 

  174. 

  175. &lt;blockquote>Freedom of expression is a necessary condition for the realization of the principles of transparency and accountability that are, in turn, essential for the promotion and protection of human rights.&lt;/blockquote>
    176. 

  176. 

  177. Moreover, to give effect to the right of access to information, States Parties should proactively put in the public domain government information of public interest. States parties should make every effort to ensure easy, prompt, effective, and practical access to such information. In regard to freedom of expression, the Committee has linked it with the developments in information and communication technologies (paragraph 15):
    178. 

  178. 

  179. &lt;blockquote>States Parties should take account of the extent to which developments in information and communication technologies, such as internet and mobile based electronic information dissemination systems, have substantially changed communication practices around the world.  There is now a global network for exchanging ideas and opinions that does not necessarily rely on the traditional mass media intermediaries.  States parties should take all necessary steps to foster the independence of these new media and to ensure access of individuals thereto.&lt;/blockquote>
    180. 

  180. 

  181. The principle of openness and the right of access to information are directed ‒ among other things ‒ at ensuring that decisions are taken as openly as possible and closely as possible to the citizens, in other words, it is a basic democratic tenet, where citizens must see what happens within the institutions (which is one of the means through which accountability of the institutions and their agents is ensured) ''and'' the institutions have an obligation to at least listen to what citizens have to say (in other words, participation and representation of interests). &lt;ref >Interesting a reading is the work {{cite web | title = Transparency in Three Dimensions | url = http://illinoislawreview.org/wp-content/ilr-content/articles/2011/4/Schauer.pdf | year = 2011 | author = Schauer, Frederick | journal = University of Illinois Law Review | pages = 1339–1358 | volume = 2011 | issue = 4 | accessdate = 2014-08-08}} although in the US constitutional environment&lt;/ref>.
    182. 

  182. 

  183. == Legislative Openness ==
    184. 

  184. 

  185. Ever since the Treaty of Amsterdam the concept of "the legislative" has had a place in the language of the EU Treaties. Under the second subparagraph of Article 207(3) EC the Council was already required to define "the cases in which it is to be regarded as acting in its legislative capacity" to allow the right of access to documents under Article 255(1) EC to be exercised.
    186. 

  186. 

  187. In the realm of secondary legislation, Recital 6 in the Preamble to Regulation No 1049/2001 states that "[w]ider access should be granted to documents in cases where the institutions are acting in their legislative capacity." The Treaty of Amsterdam enshrined both the right of access to documents of the institutions, on the one hand, and referred to the special consideration to be given to the ‘legislative capacity’ of the Council, on the other. It has been argued that this indicated that the appropriate context for exercising the right of access was where the Council was acting in a "legislative capacity", thus acknowledging the close relationship that, in principle, exists between legislative procedures and the principles of openness and transparency &lt;ref>Opinion of Advocate General Cruz Villalón in Case C‑280/11 P Council v Access Info Europe, EU:C:2013:325&lt;/ref>.
    188. 

  188. 

  189. On a comparative note, and despite the differences that may exist between national legislation and EU "legislation", or between Member State legislatures and the EU "legislature", the "legislative procedure" by which the Council and the European Parliament are bound, is conceptually very close to the national "legislative procedure", speaking from the point of view of its underlying purpose and thus the principles on which it must be based. In the end, they have in common the need to satisfy the imperative requirements of democratic legitimacy.
    190. 

  190. 

  191. As the Advocate General correctly pointed out in Case C‑280/11 P Council v Access Info Europe:
    192. 

  192. 

  193. &lt;blockquote>’Legislating’ is, by definition, a law-making activity that in a democratic society can only occur through the use of a procedure that is public in nature and, in that sense, ‘transparent’. Otherwise, it would not be possible to ascribe to ‘law’ the virtue of being the expression of the will of those that must obey it, which is the very foundation of its legitimacy as an indisputable edict. In a representative democracy, it must be possible for citizens to find out about the legislative procedure, since if this were not so, citizens would be unable to hold their representatives politically accountable, as they must be by virtue of their electoral mandate.
    194. 

  194. 

  195. In the context of this public procedure, transparency therefore plays a key role that is somewhat different from its role in administrative procedures. While, in administrative procedures, transparency serves the very specific purpose of ensuring that the authorities are subject to the rule of law, in the legislative procedure it serves the purpose of legitimising the law itself and with it the legal order as a whole.&lt;ref>Opinion of Advocate General Cruz Villalón in Case C‑280/11 P Council v Access Info Europe, EU:C:2013:325&lt;/ref>&lt;/blockquote>
    196. 

  196. 

  197. In its judgment in Sweden and Turco v Council,&lt;ref>(EU:C:2008:374)&lt;/ref> the Court held that it is for the Council to balance the particular interest to be protected by non-disclosure of the document concerned against, inter alia, the public interest in the document being made accessible in the light of the advantages stemming from increased openness. It states that when the Council is acting in its legislative capacity, it is particularly relevant that openness be considered, given that it enables citizens to participate more closely in the decision-making process, guarantees that the administration enjoys greater legitimacy, and is more effective and more accountable to the citizen in a democratic system.
    198. 

  198. 

  199. The following Recitals in the Preamble to Regulation No 1049/2001 are relevant in this respect:
    200. 

  200. 

  201. &lt;blockquote>(1) The second subparagraph of Article 1 of the Treaty on European Union enshrines the concept of openness, stating that the Treaty marks a new stage in the process of creating an ever closer union among the peoples of Europe, in which decisions are taken as openly as possible and as closely as possible to the citizen.
    202. 

  202. 

  203. (2) Openness enables citizens to participate more closely in the decision-making process and guarantees that the administration enjoys greater legitimacy and is more effective and more accountable to the citizen in a democratic system. Openness contributes to strengthening the principles of democracy and respect for fundamental rights as laid down in Article 6 of the EU Treaty and in the Charter of Fundamental Rights of the European Union.
    204. 

  204. 

  205. (6) Wider access should be granted to documents in cases where the institutions are acting in their legislative capacity, including under delegated powers, while at the same time preserving the effectiveness of the institutions’ decision-making process. Such documents should be made directly accessible to the greatest possible extent.&lt;/blockquote>
    206. 

  206. 

  207. The Court has confirmed that the considerations of legislative openness are clearly of particular relevance where the Council is acting in its legislative capacity: "Openness in that respect contributes to strengthening democracy by enabling citizens to scrutinise all the information which has formed the basis for a legislative act. The possibility for citizens to find out the considerations underpinning legislative action is a precondition for the effective exercise of their democratic rights".&lt;ref>Sweden and Turco v Council, paragraph 46 and Council of the European Union v Access Info Europe, paragraph 00&lt;/ref>
    208. 

  208. 

  209. The theoretical underpinnings of the Principle of Openness and of legislative openness has thus acquired a solid foundation in the Treaties and in the case-law of the court. However, due to the eternal tide wave and purported conflict between Openness and Efficiency, Parliament has in practice struggled to live up to the Principle of Openness by resorting to informal decision-making procedures. As Nikoleta Yordanova has correctly noted:
    210. 

  210. 

  211. &lt;blockquote>Traditionally, the parliamentary committees have offered important venues for political involvement of extra-parliamentary actors due to the openness and transparency of their meetings. In the past fifteen years, however, the EP has been resorting ever more often to informal decision-making, whereby the parliamentary decisions are not reached internally following deliberations and debate in committee and plenary but in secluded trilogue meetings of limited number of representatives of the three EU legislative institutions – the EP, the Council of Ministers and the European Commission.
    212. 

  212. 

  213. [...]
    214. 

  214. 

  215. The implications of the switch to an informal mode of legislating for representation in the EP are twofold – decreased input and, potentially also, output legitimacy. Specifically, the decrease in committee influence has curtailed the channels of representation of interest groups to affect decision-making, depriving them of an effective tool to monitor and shape the legislative process and outcomes by raising timely demands. A possible implication of this is diminished receptiveness of legislators to constituents’ interests. Moreover, the lack of transparency of the secluded inter-institutional meetings has limited the ability of constituents to monitor their representatives’ policy bargaining, positions and the concessions, and, consequently, to evaluate how responsive legislators are to their preferences and demands.&lt;ref>Nikoleta Yordanova, Collusion in Bicameral EU Decision-making Efficiency at the expense of transparency and representation?, Paper prepared for the Conference: New Trends in Political Representation, available at http://nikoletayordanova.net/wp-content/uploads/exeter.pdf&lt;/ref>&lt;/blockquote>
    216. 

  216. 

  217. === The Need for Lawmakers to Deliberate in Private ===
    218. 

  218. 

  219. The European Union, the Member States and 19 other States are parties to the Aarhus Convention on Access to Information, Public Participation in Decision-Making and Access to Justice in Environmental Matters (‘the Convention’), which entered into force on 30 October 2001. The Convention is based on three ‘pillars’ – access to information, public participation, and access to justice. Its preamble includes the following recitals:
    220. 

  220. 

  221. &lt;blockquote>Recognising that, in the field of the environment, improved access to information and public participation in decision-making enhance the quality and the implementation of decisions, contribute to public awareness of environmental issues, give the public the opportunity to express its concerns and enable public authorities to take due account of such concerns,
    222. 

  222. 

  223. Aiming thereby to further the accountability of and transparency in decision-making and to strengthen public support for decisions on the environment,
    224. 

  224. 

  225. Recognising the desirability of transparency in all branches of government and inviting legislative bodies to implement the principles of this Convention in their proceedings,&lt;/blockquote>
    226. 

  226. 

  227. The second sentence of Article 2(2) allows Member States to exclude from the scope of the Directive bodies otherwise falling within the definition of ‘public authority’, ‘when acting in a judicial or legislative capacity’.
    228. 

  228. 

  229. The Convention was approved on behalf of the European Community by Council Decision 2005/370, (3) the annex to which contains a declaration by the European Community (‘the Declaration’) which reads, in so far as relevant, as follows:
    230. 

  230. 

  231. &lt;blockquote>In relation to Article 9 of the Aarhus Convention the European Community invites Parties to the Convention to take note of Article 2(2) and Article 6 of [the Directive]. These provisions give Member States of the European Community the possibility, in exceptional cases and under strictly specified conditions, to exclude certain institutions and bodies from the rules on review procedures in relation to decisions on requests for information.
    232. 

  232. 

  233. Therefore the ratification by the European Community of the Aarhus Convention encompasses any reservation by a Member State of the European Community to the extent that such a reservation is compatible with Article 2(2) and Article 6 of [the Directive].&lt;/blockquote>
    234. 

  234. 

  235. In ratifying the Convention on 20 May 2005, Sweden lodged a reservation which, in so far as is relevant, reads as follows:
    236. 

  236. 

  237. &lt;blockquote>Sweden lodges a reservation in relation to Article 9.1 with regard to access to a review procedure before a court of law of decisions taken by the Parliament, the Government and Ministers on issues involving the release of official documents.&lt;/blockquote>
    238. 

  238. 

  239. In accordance with Directive 2003/4,&lt;ref>Directive 2003/4/EC of the European Parliament and of the Council of 28 January 2003 on public access to environmental information and repealing Council Directive 90/313/EEC (OJ 2003 L 41, p. 26) (‘the Directive’).&lt;/ref> public authorities must in principle be required to make environmental information held by or for them available to any applicant at his request. However, the Directive permits Member States to exclude public bodies acting in a legislative capacity from the definition of a ‘public authority’. In addition, access may be refused to certain types of document, or if disclosure would adversely affect the confidentiality of proceedings of authorities where such confidentiality is provided for by law.
    240. 

  240. 

  241. In her opinion in Flachglas Torgau, AG Sharpstone summarised the dilemma as follows:
    242. 

  242. 

  243. &lt;blockquote>The performance of both judicial and legislative functions could be impaired if information of all kinds concerning each and every stage of the process – analysing the relevant issues and data, deriving conclusions from that analysis and formulating a final decision – could be demanded of right at all times by any member of the public. It seems reasonable to assume that considerations of that kind were in the minds of those who initially drafted the first of the instruments concerned and have remained, albeit implicitly, in the minds of those who have participated in the drafting of the subsequent instruments.
    244. 

  244. 

  245. Yet it is by no means desirable, nor would it appear consistent with the overall thrust of the Convention or the Directive, for legislative or judicial activity to take place in impenetrable secrecy. It is generally considered necessary, in order to ensure the rule of law and democratic government, for both courts of law and legislative assemblies to operate in the presence of the public (or at least of the media as an intermediary) other than in wholly exceptional circumstances – and it is, moreover, generally accepted that such circumstances are more common in the course of judicial than of legislative activity. Other than in wholly exceptional circumstances, therefore, in neither case should decisions be taken on the basis of facts, or for reasons, which are concealed from citizens.&lt;ref>Opinion Flachglas Torgau EU:C:2011:413&lt;/ref>&lt;/blockquote>
    246. 

  246. 

  247. == Conduct of Business as "Openly as Possible" or with the "Utmost Transparency" ==
    248. 

  248. 

  249. Rule 115 states that "Parliament shall ensure that its activities are conducted with the utmost transparency", which on a textual interpretation goes beyond the more relative principle of openness enshrined in Article 1 TEU, whereby “decisions are taken as openly as possible”. Indeed, it strikes that Rule 115 uses the word '''''utmost''''', which is a far stronger word than "as openly as possible" used for other institutions:
    250. 

  250. 

  251. &lt;blockquote>
    252. 

  252. ''ut·most'' 
    253. 

  253. 

  254. adj.
    255. 

  255. 

  256. 1. Being or situated at the most distant limit or point; farthest: the utmost tip of the peninsula.
    257. 

  257. 

  258. 2. Of the highest or greatest degree, amount, or intensity; most extreme: a matter of the utmost importance.
    259. 

  259. 

  260. n.
    261. 

  261. 

  262. The greatest possible amount, degree, or extent; the maximum: worked every day to the utmost of her abilities.&lt;ref>http://www.tfd.com/utmost American Heritage® Dictionary of the English Language, Fourth Edition copyright ©2000 by Houghton Mifflin Company. As reported by The Free Dictionary&lt;/ref>
    263. 

  263. &lt;/blockquote>
    264. 

  264. 

  265. Therefore it is clear that there is no effort to spare in order to bring the "utmost" openness or transparency, in other words, openness to the most extreme consequences. Parliament has in this respect imposed upon itself a far higher standard to meet in order to ensure openness than any other institution.
    266. 

  266. 

  267. This means that the balancing test at hand should at least equal, and may even exceed, the one laid down in the case-law of the Court under the Principle of Openness. To this effect, the Court has held that assessing whether or not information is confidential therefore requires that the legitimate interests opposing disclosure be weighed against the public interest in the activities of the Community institutions taking place as openly as possible&lt;ref>General Court Case T‑237/05 Éditions Jacob v Commission [2010] ECR II‑2245, citing, to that effect, Bank Austria Creditanstalt v Commission, paragraph 71, and Case T‑474/04 Pergan Hilfsstoffe für industrielle Prozesse v Commission [2007] ECR II‑4225, paragraphs 63 to 66.&lt;/ref>.
    268. 

  268. 

  269. A similar construction has been adopted by the Court as regards access to documents. The Court has held that since they derogate from the "principle of the widest possible public access to documents", exceptions to that principle must be interpreted and applied strictly&lt;ref>Council v In 't Veld, EU:C:2014:2039, paragraph 48, Council v Access Info Europe, EU:C:2013:671, paragraph 30 and the case-law cited.&lt;/ref>. In Council v In 't Veld, access was requested to an opinion of the Council’s Legal Service, issued in the context of the adoption of the Council’s decision authorising the opening of negotiations, on behalf of the European Union, in respect of the proposed agreement. Having established the "principle of the widest possible public access to documents", the Court held:
    270. 

  270. 

  271. &lt;blockquote>
    272. 

  272. 51  However, the mere fact that a document concerns an interest protected by an exception to the right of access laid down in Article 4 of Regulation No 1049/2001 is not sufficient to justify the application of that provision (see, to that effect, Commission v Éditions Odile Jacob, C‑404/10 P, EU:C:2012:393, paragraph 116).
    273. 

  273. 

  274. 52  Indeed, if the institution concerned decides to refuse access to a document which it has been asked to disclose, it must, in principle, first explain how disclosure of that document could specifically and actually undermine the interest protected by the exception — among those provided for in Article 4 of Regulation No 1049/2001 — upon which it is relying. In addition, the risk of the interest being undermined must be reasonably foreseeable and must not be purely hypothetical (Council v Access Info Europe, EU:C:2013:671, paragraph 31 and the case-law cited).
    275. 

  275. 

  276. 53  Moreover, if the institution applies one of the exceptions provided for in Article 4(2) and (3) of Regulation No 1049/2001, it is for that institution to weigh the particular interest to be protected through non-disclosure of the document concerned against, inter alia, the public interest in the document being made accessible, having regard to the advantages of increased openness, as described in recital 2 to Regulation No 1049/2001, in that it enables citizens to participate more closely in the decision-making process and guarantees that the administration enjoys greater legitimacy and is more effective and more accountable to the citizen in a democratic system (Council v Access Info Europe, EU:C:2013:671, paragraph 32 and the case-law cited).&lt;ref>C-350/12 P, Council v In 't Veld, ECLI:EU:C:2014:2039&lt;/ref>
    277. 

  277. &lt;/blockquote>
    278. 

  278. 

  279. In the same vein, the European Ombudsman has recognised that the wording and purpose of Articles 11 and 12 of Regulation 1049/2001 do not imply an obligation on Parliament to have, in its public register of documents, a reference to each and every document it holds. However, the Ombudsman found that Parliament should certainly interpret Articles 11 and 12 of Regulation 1049/2001 in a manner which allows the public to obtain "as complete a picture as possible" of how Parliament carries out its core tasks. Documents which relate to these core tasks should therefore, as far as possible, be recorded in Parliament's public register of documents. &lt;ref>Decision of the European Ombudsman closing the inquiry into complaint 262/2012/OV against the European Parliament, available at http://www.ombudsman.europa.eu/cases/decision.faces/en/57773/html.bookmark&lt;/ref>
    280. 

  280. 

  281. Against this background, any derogations from the Parliament's Rule 115 that "its activities are conducted with the utmost transparency" must be interpreted strictly, and in the light of the Court's case law on the Principle of Openness and the right of access to documents.
    282. 

  282. 

  283. It is also clear that Rule 115 section 1 does not just refer to the fact that the works of the Parliament must be open and public. This is a separate concept, it cannot be a replacement for openness, as it is dealt with by different provisions, e.g., section 2 of Rule 115:
    284. 

  284. 

  285. &lt;blockquote>Debates in Parliament shall be public.&lt;/blockquote>
    286. 

  286. 

  287. Therefore it is safe to conclude that simply the publicity of the works is not sufficient. On the other hand, it is evident that those parts that need to be non-public shall be subtracted from the principle of openness, but this shall be an exception to the rule.
    288. 

  288. 

  289. It should be noted that one of the open issues during the negotiations in the Council on the reform of regulation 1049/2001, is whether some reforms are needed to comply with the Treaty of Lisbon, which obliges the EU institutions to take decisions “as openly and as closely as possible to the citizen” and which requires a transparent legislative process. As has been The European Charter of Fundamental Rights also now recognises the right of access to EU documents “whatever their medium”, as a fundamental human right. At the very least the Treaties extend the scope of the right of access to all EU bodies and it is not clear whether this requires a legislative amendment to do away with current discrepancies such as different time frames for different EU bodies.
    290. 

  290. 

  291. == Neighbouring concepts ==
    292. 

  292. 

  293. === Re-use of Public Sector Information ===
    294. 

  294. The Directive 2003/98/EC on the re-use of public sector information &lt;ref>Directive 2003/98/EC of the European Parliament and of the Council of 17 November 2003 on the re-utilisation of public sector information (OJ 2003 L 345, p. 90)&lt;/ref>  as amended by Directive 2013/
    295. 

  295. 37/EU &lt;ref>Directive 2013/37/EU of the European Parliament and of the Council of 26 June 2013 amending Directive 2003/98/EC on the re-use of public sector information (OJ L 175, 27.6.2013 p. 1-8)&lt;/ref>, also known as the "PSI Directive" &lt;ref>In the remainder of this section, by using "PSI Directive" we make reference to the amended directive.&lt;/ref>, establishes a minimum set of rules governing the re-use and the practical means of facilitating re-use of existing documents held by public sector bodies of the Member States. Article 2(4) of the PSI Directive defines re-use as "the use by persons or legal entities of documents held by public sector bodies, for commercial or non-commercial purposes other than the initial purpose within the public task for which the documents were produced. Exchange of documents between public sector bodies purely in pursuit of their public tasks does not constitute re-use".
    296. 

  296. 

  297. Article 3 of the PSI Directive entitled ‘General principle’ states that Member States shall ensure that, where the re-use of documents held by public sector bodies is allowed, these documents shall be re-usable for commercial or non-commercial purposes in accordance with the conditions set out in in the Directive. 
    298. 

  298. 

  299. Recital 9 clarifies that the definition of "document" is not intended to cover computer programmes. To facilitate re-use, public sector bodies should make their own documents available in a format which, as far as possible and appropriate, is not dependent on the use of specific software. Where possible and appropriate, public sector bodies should take into account the possibilities for the re-use of documents by and for people with disabilities.
    300. 

  300. 

  301. In recital 16, the PSI Directive establishes a link between re-use of public sector information and the "right to knowledge" in the following terms:
    302. 

  302. &lt;blockquote>Making public all generally available documents held by the public sector - concerning not only the political process but also the legal and administrative process - is a fundamental instrument for extending the right to knowledge, which is a basic principle of democracy. This objective is applicable to institutions at every level, be it local, national or international.&lt;/blockquote>
    303. 

  303. 

  304. The PSI Directive does not contain an obligation to allow re-use of documents, and the decision whether or not to authorise re-use remains with the Member States or the public sector body concerned. It applies to documents that are made accessible for re-use when public sector bodies license, sell, disseminate, exchange or give out information. To avoid cross-subsidies, re-use includes further use of documents within the organisation itself for activities falling outside the scope of its public tasks. Activities falling outside the public task will typically include supply of documents that are produced and charged for exclusively on a commercial basis and in competition with others in the market.
    305. 

  305. 

  306. In Recital 9, the PSI Directive purports to build on the existing access regimes in the Member States and does not change the national rules for access to documents. It does not apply in cases in which citizens or companies can, under the relevant access regime, only obtain a document if they can prove a particular interest. At Community level, Articles 41 (right to good administration) and 42 of the Charter of Fundamental Rights of the European Union recognise the right of any citizen of the Union and any natural or legal person residing or having its registered office in a Member State to have access to European Parliament, Council and Commission documents. Public sector bodies should be encouraged to make available for re-use any documents held by them. Public sector bodies should promote and encourage re-use of documents, including official texts of a legislative and administrative nature in those cases where the public sector body has the right to authorise their re-use.
    307. 

  307. 

  308. An addition to Article 2 of the PSI Directive, introduced by Directive 2013/37/EU &lt;ref>See note above&lt;/ref>, provides a number of useful definitions for the purpose of this study, since the European legislator has made an attempt to define open format and open standards as follows:
    309. 

  309. 

  310. &lt;blockquote>
    311. 

  311. 6. ‘machine-readable format’ means a file format structured so that software applications can easily identify, recognize and extract specific data, including individual statements of fact, and their internal structure;
    312. 

  312. 

  313. 7. ‘open format’ means a file format that is platform-independent and made available to the public without any restriction that impedes the re-use of documents;
    314. 

  314. 

  315. 8. ‘formal open standard’ means a standard which has been laid down in written form, detailing specifications for the requirements on how to ensure software interoperability;
    316. 

  316. &lt;/blockquote>
    317. 

  317. 

  318. Under the new article 5.1 on available formats, public sector bodies shall make their documents available in any pre-existing format or language, and, where possible and appropriate, in open and machine-readable format together with their metadata. Both the format and the metadata should, in so far as possible, comply with formal open standards. However, this does not imply an obligation for public sector bodies to create or adapt documents or provide extracts in order to comply with that obligation where this would involve disproportionate effort, going beyond a simple operation.
    319. 

  319. 

  320. Article 11 of the PSI Directive provides a prohibition of exclusive arrangements. Under Article 11.1, the re-use of documents shall be open to all potential actors in the market, even if one or more market players already exploit added-value products based on these documents. Contracts or other arrangements between the public sector bodies holding the documents and third parties shall not grant exclusive rights. Under Article 11.2 where an exclusive right is necessary for the provision of a service in the public interest, the validity of the reason for granting such an exclusive right shall be subject to regular review, and shall, in any event, be reviewed every three years. The exclusive arrangements established shall be transparent and made public.
    321. 

  321. 

  322. === The G8 Open Data Charter ===
    323. 

  323. 

  324. In June 2013, the EU endorsed the G8 Open Data Charter and, with other G8 members, committed to implementing a number of open data activities in the G8 members’ Collective Action Plan. Commitment 1 of the Collective Action Plan required each member to publish by October 2013 details of how they would implement the Open Data Charter according to their individual national frameworks. In the EU implementation of the G8 Open Data Charter, it is stressed that compliance with the G8 Open Data Charter and para. 47 of the June 2013 G8 communique is fully consistent with existing EU policy. Particular reference is in particular made to "the many initiatives already adopted at EU level, including the revised Directive on the re-use of public sector information, the EU Open Data Portal and the new Commission rules on the re-use of its own documents".
    325. 

  325. 

  326. In its self assessment, the European Union stressed that it "has for years been stressing the goal of opening up data as a resource for innovative products and services and as a means of addressing societal challenges and fostering government transparency. Indeed, better use of data, including government data, can help to power the economy, serving as a basis for a wide range of information products and services and improving the efficiency of the public sector and of different segments of industry. The European Union aims to be at the forefront of public administrations in terms of openness in relation to its own documents." It is noteworthy that Open Data within the European Union is first and foremost seen as "a resource for innovative products and services" with economic potential, and only seem to regard Open Data to hold a secondary function in fostering Open Government.
    327. 

  327. 

  328. The challenges identified by the EU for making further progress towards the openness of information resources were considered mainly practical and technical, namely:
    329. 

  329. 

  330. &lt;blockquote>
    331. 

  331. 

  332. * making data available in an open format;
    333. 

  333. 

  334. * enabling semantic interoperability;
    335. 

  335. 

  336. * ensuring quality, documentation and where appropriate reconciliation across different data sources;
    337. 

  337. 

  338. * implementing software solutions allowing easy management, publication or visualisation of datasets;
    339. 

  339. 

  340. * simplifying clearance of intellectual property rights.&lt;ref>EU implementation of the G8 Open Data Charter, Open data context, page 2 http://ec.europa.eu/information_society/newsroom/cf/document.cfm?action=display&amp;doc_id=3489&lt;/ref>&lt;/blockquote>
    341. 

  341. 

  342. The EU has furthermore committed to promoting the application of the principles of the G8 Open Data Charter to all EU Member States within the context of a range of ongoing activities, in particular through ensuring the implementation of Directive 2013/37/EU of 26 June 2013 revising Directive 2003/98/EC on the re-use of public sector information (or the PSI Directive as defined in the previous section) which, according to the EU:
    343. 

  343. 

  344. &lt;blockquote>
    345. 

  345. * ensures that publicly accessible content can be reused in compliance with the Directive;
    346. 

  346. 

  347. * encourages free provision of public sector information (government data) for reuse and lowering the cost of reuse of government data by introducing a new maximum ceiling for reuse based on marginal costs;
    348. 

  348. 

  349. * expands the scope of application of the EU Directive to certain cultural institutions;
    350. 

  350. 

  351. * defines ‘machine-readable format’ and ‘open format’ and encouraging the use of those formats;&lt;ref>EU implementation of the G8 Open Data Charter, EU Commitment 4: Promoting the application of the principles of the G8 Open Data Charter in all 28 EU Member States, page 8 http://ec.europa.eu/information_society/newsroom/cf/document.cfm?action=display&amp;doc_id=3489&lt;/ref>&lt;/blockquote>
    352. 

  352. 

  353. === Re-use of EU Institution documents ===
    354. 

  354. 

  355. As a rule, the European Commission has allowed re-use of its documents for commercial and non- commercial purposes at no charge since 2006, adopting a first decision of 7 April 2006 on re-use of Commission documents&lt;ref> http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=OJ:L:2006:107:0038:0041:EN:PDF &lt;/ref>
    356. 

  356. 

  357. According to the seventh recital of this decision, "An open re-use policy at the Commission will support new economic activity, lead to a wider use and spread of Community information, enhance the image of openness and transparency of the Institutions, and avoid unnecessary administrative burden for users and Commission services". Again, the underlying rationale of the decision was to "support new economic activity", and the ambition in fostering Open Government was reduced "enhance the image of openness and transparency" of the Institutions.
    358. 

  358. 

  359. In 2011, the Commission engaged itself to work towards providing documents in machine-readable format, where possible and appropriate, and to set up an Open Data Portal to promote the accessibility and re-use of this information. In December 2012, the European Union Open Data Portal was launched and provides access to data held by the Commission and other EU institutions and bodies.&lt;ref>http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=OJ:L:2011:330:0039:0042:EN:PDF&lt;/ref>
    360. 

  360. 

  361. === Re-use of Public Sector Information does not necessarily ensure an Open Government ===
    362. 

  362. 

  363. Obviously, the main purpose of the Public Sector Information Directive (PSI Directive) is to pave the way for a European information market. At their core, these rules are intended to ensure fair, proportionate and non-discriminatory conditions for the re-use of such information.
    364. 

  364. 

  365. As noted above, the European legislator's push for Open Data has been more driven by commercial purposes of data mining than in a quest of opening government to external scrutiny. In some cases the re-use of documents will take place without a licence being agreed. In other cases, a licence will be issued imposing conditions on the re-use by the licensee dealing with issues such as liability, the proper use of documents, guaranteeing non-alteration and the acknowledgement of source. If public sector bodies license documents for re-use, the licence conditions should be fair and transparent.
    366. 

  366. 

  367. Nevertheless, in creating a private market for Public sector information can have unintended consequences. According to the directive, public sector bodies should respect competition rules when establishing the principles for re-use of documents avoiding as far as possible exclusive agreements between themselves and private partners. However, in order to provide a service of general economic interest, an exclusive right to re-use specific public sector documents may sometimes be necessary. This may be the case if no commercial publisher would publish the information without such an exclusive right.
    368. 

  368. 

  369. On 18 March 2010, the Swedish Government presented its Bill (2009/10:175) on Public Administration for Democracy, Participation and Growth. One proposal contained in the Bill was for a law on re-use of documents emanating from Swedish public administration. On 3 June 2010, the Act (2010:566) on the re-use of public administration documents entered into force. The Swedish Agency for Public Management has therefore been assigned to survey the extent to which Swedish central and local government agencies (public sector bodies) have granted exclusive rights or arrangements of the kind referred to in Article 11 of the PSI Directive.
    370. 

  370. 

  371. The survey shows that five central public sector bodies state that they have granted exclusive rights for one or more companies to re-use the respective bodies' documents. The questionnaire and interviews implemented by the Agency for Public Management show that several changes have taken place over the past year in terms of phasing out exclusive rights, if any. The survey shows, moreover, that there are unclear points regarding how the notion of 'exclusive rights' (or 'arrangements') should be defined. Based on the responses to the Agency's questionnaire survey, we find wide-ranging perceptions of differences between licensing agreements, on the one hand, and exclusive rights on the other. According to the Agency, there is substantial uncertainty regarding how the term 'exclusive right' should be interpreted. The Swedish Agency for Public Management therefore draws the conclusion that it is imperative to define the terms 'licensing agreement' and 'exclusive right', and also to assist both central and local public sector bodies in their work of developing non-discriminatory licensing agreements.&lt;ref> Statskontoret, A survey of exclusive rights or arrangements (2010:21), available at http://www.statskontoret.se/in-english/publications/2010/a-survey-of-exclusive-rights-or-arrangements/.&lt;/ref>
    372. 

  372. 

  373. It should be noted that in March 2012, the Swedish Competition Authority closed an investigation with regard to a possible abuse of a dominant position by the Swedish Patent and Registration Office (SPRO) regarding its Trademark register. The Swedish Patent and Registration Office (SPRO) started to offer from 2010 free access to the Trademark register to the downstream end-user market. Customers on the upstream wholesale market were offered more detailed data in different formats (so-called ''"register lifted data"'') for a one-time fee and then a yearly fee. Before 2010, SPRO had offered access to the database to end-users for a fee. The SPRO motivated the decision to eliminate the fee with that free access was within the public task assigned to it by the government. The complaining (incumbent) re-user alleged that it was likely it will be squeezed out of the market by SPRO offering a competing product for free.&lt;ref> Björn Lundqvist and Ylva Forsberg (Stockholm University), Marc de Vries (Citadel Consulting) and Mariateresa Maggiolino (Bocconi), LAPSI 2.0 – competition law issues position paper, available at http://www.lapsi-project.eu/sites/lapsi-project.eu/files/LAPSIcompetitionartikelDraftII-1.pdf; Elisabeth Eklund and Oscar Jansson, Lower fees for re-use of public sector information – the PSI Directive and cases from the Swedish Competition Authority, available at http://www.worldservicesgroup.com/publications.asp?action=article&amp;artid=4792; see also Björn Lundqvist, Marc de Vries, Emma Linklater och Liisa Rajala Malmgren, Business Activity and Exclusive Right in the Swedish PSI Act, Swedish Competition Authority, Uppdragsforskningsrapport 2011:2, available at http://www.konkurrensverket.se/upload/Filer/Trycksaker/Rapporter/uppdragsforskning/forsk_rap_2011-2.pdf.&lt;/ref>. This case shows that the underlying economic rationale for the PSI Directive can actually run counter the stated objective of fostering an Open Government.
    374. 

  374. 

  375. == Does Openness mean "accessible"? ==
    376. 

  376. 

  377. We submit that transparency should be measured having regard to not only the average person "without impairments", so to speak, but also with those who are for instance visually or hearing impaired. In other words, transparency also should take "accessibility" into account.
    378. 

  378. 

  379. For web content a standard has been developed by W3C, which is the Web Content Accessibility Guidelines (WCAG)&lt;ref>{{cite web|title=Web Content Accessibility Guidelines (WCAG)|url=http://www.w3.org/WAI/intro/wcag|accessdate=16 October 2014}}&lt;/ref>.
    380. 

  380. 

  381. European Commission (EC) Mandate M 376 required the three main European standardisation bodies CEN, CENELEC and ETSI to harmonise and facilitate the public procurement of accessible information and communication technologies (ICT) products and services within Europe. &lt;ref>{{cite web|title=European Accessibility Requirements for Public Procurement of Products and Services in the ICT Domain (European Commission Standardization Mandate M 376, Phase 2)|url=http://www.mandate376.eu/|accessdate=16 October 2014}}&lt;/ref>
    382. 

  382. 

  383. Both of the mentioned standardisation rules have been mandated by some Member States&lt;ref>Some information on the adoption of accessibility standards, a recent book is {{cite book|last1=Buie|first1=Elizabeth|last2=Murray|first2=Diane|title=Usability in Government Systems: User Experience Design for Citizens and Public Servants|date=2012|publisher=Elsevier|isbn=978-0-12-391063-9|url=http://books.google.it/books?id=U3P4tdoETiwC&amp;dq|accessdate=16 October 2014}}&lt;/ref>
    384. 

  384. 

  385. The Commission reports that since January 2010, all new EUROPA websites have been created in compliance with WCAG 2.0, level AA success criteria.&lt;ref>{{cite web|title=Web Accessibility|url=http://ec.europa.eu/digital-agenda/en/web-accessibility|publisher=European Commission|accessdate=16 October 2014}}&lt;/ref> and this includes the website of the European Parliament. &lt;ref>{{cite web|title=Accessibility of the Europarl website|url=http://www.europarl.europa.eu/portal/en/accessibility|publisher=European Parliament|accessdate=16 October 2014}}&lt;/ref>
    386. 

  386. 

  387. However, "accessibility" seems to extend to much more than just web view, as the flow of information is certainly passing through means that go beyond the web and the Internet in general. There is, therefore, a wider need to ensure accessibility by allowing that the IT systems be interoperable and technology neutral, so that accessibility is ensured not only by providing accessible content, but by allowing any technology provider to ensure that they can build accessible tools using the content in whichever form it can be presented, and ‒ as much as possible ‒ to make tools to tackle specific problems for people with different impairments for whom the simple accessibility criteria are insufficient.
    388. 

  388. 

  389. == Does "accessible" mean (also) Free and Open? ==
    390. 

  390. 

  391. If "transparency" here means "directly open, transparent and accessible to all the constituents" and not just to those directly involved in the Parliamentary works and interest-bearer, as a complement of democracy, openness shall be in principle brought to the farthest and least reachable corner of the Union where constituents have a chance of looking into how a particular matter has been dealt with by the Parliament and components thereof. An example of why openness is a requirement for transparency via accessibility has been provided in the previous chapter.
    392. 

  392. 

  393. In an interconnected world this goal can be efficiently achieved by means of technology, in particular through telecommunication technology. This seems a sufficiently self-evident and commonly accepted concept that does not deserve further discussion and evidence.
    394. 

  394. 

  395. Telecommunication technology cannot exist without standards. This is also quite easily understood and common ground. &lt;ref name="ITU in brief">"Standards are critical to the interoperability of ICTs and whether we exchange voice, video or data messages, standards enable global communications by ensuring that countries’ ICT networks and devices are speaking the same language." From {{cite web|title=ITU in Brief|url=http://www.itu.int/en/ITU-T/about/Pages/default.aspx|accessdate=25 July 2014|ref=ITU}}&lt;/ref>
    396. 

  396. 

  397. Therefore "openness" shall mean that the external communication channels, of all sort, must use standards, which (or the many possible) standard(s) remaining yet to be assessed.
    398. 

  398. 

  399. All signs point in the direction that standards involved in a public institution shall be "'''open'''" &lt;ref>For a very large collection of reference in this regard [http://www.opengovstandards.org/ Opengovstandards.org] is probably the best source. Quoting from it "Transparency means that information about the activities of public bodies is created and is available to the public, with limited exceptions, in a timely manner, in open data formats and without restrictions on reuse. Transparency mechanisms must include the disclosure of information in response to requests from the public and proactive publication by public bodies. Key information about private bodies should be available either directly or via public bodies."
    400. 

  400. &lt;/ref> Quite in the same direction goes the seminal work of De Nardis and Tam &lt;ref>DeNardis, Dr. Laura and Tam, Eric, Open Documents and Democracy: A Political Basis for Open Document Standards (November 1, 2007). Available at SSRN: http://ssrn.com/abstract=1028073 or http://dx.doi.org/10.2139/ssrn.1028073&lt;/ref> from which a citation is indeed appropriate:
    401. 

  401. 

  402. &lt;blockquote>With regard to standards that directly affect conditions relevant to democracy, the most prominent examples consist of standards that affect citizens’ access to information concerning government decisions as well as standards concerning government records. The importance of accountability renders openness of implementation and use similarly important in this context.
    403. 

  403. 

  404. [...]
    405. 

  405. 

  406. Consequently, the standards that affect such conditions must be continuously free of barriers to the widespread use of the relevant access technology. Democratic values are inconsistent with differential costs in the form of royalty fees or interoperability barriers that potentially result in unequal citizen access to such information. &lt;/blockquote>
    407. 

  407. 

  408. 

  409. It is also quite self-evident that transmitting information to an outlet that cannot be used by the intended recipient equals to opaqueness, as openness must be a characteristic of the entire space between the object and the observer. As said before, while having total openness – which means totally unencumbered space – is more a reference than a realistic goal, getting as close as practically possible to it is the yardstick of compliance with the rule in hand.&lt;ref>{{cite web|last1=Updegrove|first1=Andrew|title=With Access and Information for All|url=http://www.consortiuminfo.org/bulletins/feb09.php#editorial|website=Consortium Info|accessdate=25 July 2014}}&lt;/ref> &lt;ref>{{cite web|last1=Updegrove|first1=Andrew|title=How Open Must an Open Government Platform be?|url=http://www.consortiuminfo.org/bulletins/feb09.php#feature|accessdate=25 July 2014}}&lt;/ref>
    410. 

  410. 

  411. It is reasonable that the means and infrastructure to be used to achieve the goal of openness are a matter of technical decisions in a scenario of non-unlimited resources. It also seems reasonable that once a high level decision on which channel is more conveniently adopted, at an early stage of the decisional process, and throughout the life cycle of the adopted solutions, the decision makers shall measure how easily accessible the channel is.
    412. 

  412. 

  413. As soon as the radio broadcasting was shown to be a practical way to spread information, institutions found it convenient to use the radio channel to increase the outreach of their messages. When television came along, and become a widespread medium, that channel was also used, both directly and through facilitating reporting by the press. Because today Internet is one of the most used source of information, all institutions use the various communication avenues that Internet allows to increase, at exponential rates, access and feedback, including the European Parliament.
    414. 

  414. 

  415. Internet is a showcase of open standards, because as such Internet is nothing more than a collection of protocols one stacked upon the other. &lt;ref>For an historical perspective of how Internet developed and was defined, see {{cite journal | author=Barry M. Leiner, Vinton G. Cerf, David D. Clark, Robert E. Kahn, Leonard Kleinrock, Daniel C. Lynch, Jon Postel, Larry G. Roberts, Stephen Wolff | title=A Brief History of Internet | year=2003 | url=http://www.isoc.org/internet/history/brief.shtml | accessdate= 25 July 2014}}&lt;/ref> so that information and services are exchanged between and through an arbitrary set of networks through common interfaces. It is hard to think of something more accessible and widely available and efficient. No doubt any openness must involve Internet distribution.
    416. 

  416. 

  417. But while it is true that Internet means a stack of protocols and interfaces, due to its anarchic and agnostic nature, it is possible that some of the chosen protocols are less easily available and widespread. In theory, parties can agree upon proprietary protocols and still have a way to communicate. Privacy-aware protocols, like those enabling VPNs are just there for that, creating a privileged channel that excludes all others not part of the conversation. Encryption is a way to transmit a confidential message over a public channel, introducing a secret and private element that allows only those privy to something to make sense of the message.&lt;ref>A good list of sources on cryptography and the problem it solves can be found at {{cite web|url=http://en.wikipedia.org/wiki/Cryptography|title=Cryptography|accessdate=9 December 2014}}&lt;/ref> On the other end of the spectrum are those protocols, widespread, available and unencumbered standards that any entity is able to intercept and interpret to the fullest without any kind of restriction, where nothing, being it a technical, economic or legal element, hindering the access to the message. This is one possible way of defining open standards. Which is the subject of the next section.
    418. 

  418. 

  419. = Free and open in technology =
    420. 

  420. 

  421. In the last paragraph of the previous section we have concluded that free and open is a proxy for "transparency". &lt;ref>See also {{cite book|last1=Lathrop|first1= Daniel|last2=Ruma|first2=Laurel|title=Open government : [collaboration, transparency, and participation in practice]|date=2010|publisher=O'Reilly|isbn=978-0-596-80435-0|edition=1st ed.|url=http://books.google.it/books?id=JQJ5LF3h4ikC&amp;dq=open+data+democracy+transparency&amp;lr=&amp;hl=it&amp;source=gbs_navlinks_s|accessdate=14 October 2014}}&lt;/ref> Here we will describe what "Free and Open" mean from a technology point of view with reference to commonly accepted, yet controversial at times, sources.
    422. 

  422. 

  423. == Free and Open Standards ==
    424. 

  424. 

  425. There is no legal and binding definition on what an Open Standard is. All the attempts made so far within the EU legislature and policy documents have faced strong debate and criticism from either side of the spectrum ranging from those who claim that "Open" applies to all standards that are available to every concerned entity, to those who claim that "Open" needs a far stricter definition and the list of requirements for a standard to be called "open" extend beyond the nature of a technical document of the standard to encompass the legal restrictions to its implementations (first and foremost patents) and the independence from a single implementation, especially coming from the main proponent of the standard.
    426. 

  426. 

  427. The debate around the European Interoperability Framework in its two incarnations (v.1 and v.2) is particularly illustrative of this dualism.
    428. 

  428. 

  429. === The European Interoperability Framework V.1 ===
    430. 

  430. 

  431. The European Interoperability Framework was conceived in 2003 and defined as "[an] overarching set of policies, standards and guidelines which describe the way in which organisations have agreed, or should agree, to do business with each other." &lt;ref name=IDABC>{{cite web|title=EIF - European Interoperability Framework for pan-European eGovernment services|url=http://ec.europa.eu/idabc/en/document/2319/5644.html|accessdate=7 August 2014}}&lt;/ref> In essence, it is an effort put in place to have one reference for public administrations as well as private entities within Europe to seamlessly share services and data with each other, by means of agreed practices and standards, as an action from eEurope 2005 Action Plan.
    432. 

  432. 

  433. One of the tasks of the project was indeed to find some common ground as to what "standard" means and what an "open standard" also means:
    434. 

  434. 

  435. &lt;blockquote>
    436. 

  436. To attain interoperability in the context of pan-European eGovernment services, guidance needs to focus on open standards 17. The following are the minimal characteristics that a specification and its attendant documents must have in order to be considered an open standard:
    437. 

  437. 

  438. * The standard is adopted and will be maintained by a not-for-profit organisation, and its ongoing development occurs on the basis of an open decision-making procedure available to all interested parties (consensus or majority decision etc.).
    439. 

  439. 

  440. * The standard has been published and the standard specification document is available either freely or at a nominal charge. It must be permissible to all to copy, distribute and use it for no fee or at a nominal fee.
    441. 

  441. 

  442. * The intellectual property - i.e. patents possibly present - of (parts of) the standard is made irrevocably available on a royalty-free basis.
    443. 

  443. 

  444. * There are no constraints on the re-use of the standard.&lt;ref name=EIFv1>{{cite book|title=European Interoperability Framework For Pan-European eGovernment Services|isbn=92-894-8389-X|page=9|url=http://ec.europa.eu/idabc/servlets/Docd552.pdf?id=19529|accessdate=7 August 2014}}&lt;/ref>
    445. 

  445. &lt;/blockquote>
    446. 

  446. 

  447. Note that the recommendation did not prescribe the use of only open standards, but only advised to "focus" on open standards. There was also no ethical or ideological implication in the recommendation, which came from an objective and functional analysis.
    448. 

  448. 

  449. To our knowledge, that was the first attempt to define open standards in an official, albeit non legislative, document from the European Union. The document was officially adopted in 2004.
    450. 

  450. 

  451. === The European Interoperability Framework V.2 ===
    452. 

  452. 

  453. In 2006, the European Commission has started the revision of the European Interoperability Framework.&lt;ref>{{cite web|title=Revision of the EIF and AG|url=http://ec.europa.eu/idabc/en/document/7728.html|accessdate=7 August 2014}}&lt;/ref>
    454. 

  454. 

  455. The effort was completed on December 2010.&lt;ref name=EIFv2>{{cite web|title=Annex 2 to the Communication from the Commission to the European Parliament, the Council, the European Economic and Social Committee and the Committee of Regions 'Towards interoperability for European public services' COM(2010) 744 final
    456. 

  456. |url=http://ec.europa.eu/isa/documents/isa_annex_ii_eif_en.pdf|accessdate=7 August 2014}}&lt;/ref>
    457. 

  457. 

  458. Reportedly due to intense lobbying by industry representatives,&lt;ref>{{cite web|title=European Commission Betrays Open Standards|url=http://blogs.computerworlduk.com/open-enterprise/2010/05/european-commission-betrays-open-standards/index.htm|website=ComputerWorld UK - Blog|accessdate=7 August 2014}}&lt;/ref> &lt;ref>{{cite web|title=European Interoperability Framework supports openness|url=http://opensource.com/government/10/12/european-interoperability-framework-supports-openness|website=Opensource.com|accessdate=7 August 2014}}&lt;/ref> notably in the new document there is no reference to standards at all, let alone to open standards, but more vaguely to "open specifications". &lt;ref>EIFv2 , page 26&lt;/ref>
    459. 

  459. 

  460. The relevant language starts with "'''''If''''' the openness principle is applied in full" [emphasis added], therefore it is not even a recommendation that of applying openness in full, but only a trajectory is envisaged and made an hypothesis. Consequently Recommendation 22 of the EIFv2 states:
    461. 

  461. 

  462. &lt;blockquote>
    463. 

  463. Recommendation 22. When establishing European public services, public administrations '''''should prefer''''' open specifications, taking due account of the coverage of functional needs, maturity and market support. [emphasis added]
    464. 

  464. &lt;/blockquote>
    465. 

  465. 

  466. The very definition of open specification in the EIFv2 is far more vague than the one found in the EIFv1:
    467. 

  467. 

  468. &lt;blockquote>
    469. 

  469. If the openness principle is applied in full:
    470. 

  470. 

  471. * All stakeholders have the same possibility of contributing to the development of the specification and public review is part of the decision-making process;
    472. 

  472. 

  473. * The specification is available for everybody to study;
    474. 

  474. 

  475. * Intellectual property rights related to the specification are licensed on FRAND terms or on a royalty-free basis in a way that allows implementation in both proprietary and open source software.
    476. 

  476. &lt;/blockquote>
    477. 

  477. 

  478. "FRAND" is an acronym of "Free, Reasonable And Non Discriminatory" conditions, and is a term of the trade in the standardisation world, and beyond. However, it is not clear what it really means &lt;ref>Most telling the EU-commissioned study for the European Commission - Directorate-General for Enterprise and Industry {{cite web|title=Patents and Standards - A modern framework for IPR-based standardization|url=http://ec.europa.eu/DocsRoom/documents/4843/attachments/1/translations/en/renditions/pdf|accessdate=14 October 2014}}, cfr pag. 130.&lt;/ref>, as for instance it can be argued that imposing a per copy royalty is discriminatory against Free Software or software with (other) strong ''"copyleft"'' licensing conditions. Therefore it is open to question whether FRAND conditions that do not allow "implementation in both proprietary and open source software" are indeed FRAND as per the very definition of open specifications.
    479. 

  479. 

  480. This is not the place to resolve the issue, but it is indicative of how there is a tension between those who oppose extending the definition of Open Standards to something that is not as open as it can be (mainly, some of the biggest patent holders, yet not all of them), and those who advocate a stricter definition to include only something that is really open to be adopted, without the need to take affirmative steps to obtain a license, even from a patent pool.&lt;ref>For a dissertation of the topic in general, please see {{cite journal|last1=Dolmans|first1=Maurits|last2=Piana|first2=Carlo|title=A Tale of Two Tragedies – A plea for open standards, and some comments on the RAND report|journal=International Free and Open Source Software Law Review|date=2010|volume=2|issue=2|pages=115-138|doi=10.5033/ifosslr.v2i2.46|url=http://www.ifosslr.org/ifosslr/article/view/46|accessdate=7 August 2014}}&lt;/ref> &lt;ref>Also with useful analyses on openness of standards a more dated article: {{cite journal|last1=Krechmer|first1=Ken|title=Open Standards Requirements|journal=The International Journal of IT Standards and Standardization Research|date=7 February 2005|volume=4|issue=1|url=http://www.csrstds.com/openstds.pdf|accessdate=7 August 2014}}&lt;/ref>
    481. 

  481. 

  482. === The UK definition ===
    483. 

  483. 

  484. Whether it is advisable or not to adopt a firm stance on Royalty Free standard can be debated at length. However because there are policies and rules that take that approach, means that at least it is ''possible'' to come to a stricter definition of Open Standards.
    485. 

  485. 

  486. One clear Royalty Free stance with really far reaching requirements case is the one adopted by the UK Government.&lt;ref>{{cite web|last1=UK Cabinet|title=Open Standards principles|url=https://www.gov.uk/government/publications/open-standards-principles/open-standards-principles#open-standard---definition|accessdate=11 November 2014|ref=UK-open}}&lt;/ref>
    487. 

  487. 

  488. &lt;blockquote>
    489. 

  489. '''12. Open standard - definition'''
    490. 

  490. 

  491. Open standards for software interoperability, data and document formats, which exhibit all of the following criteria, are considered consistent with this policy:
    492. 

  492. 

  493. Collaboration - the standard is maintained through a collaborative decision-making process that is consensus based and independent of any individual supplier. Involvement in the development and maintenance of the standard is accessible to all interested parties.
    494. 

  494. 

  495. Transparency - the decision-making process is transparent and a publicly accessible review by subject matter experts is part of the process.
    496. 

  496. 

  497. Due process - the standard is adopted by a specification or standardisation organisation, or a forum or consortium with a feedback and ratification process to ensure quality. (The European Regulation enabling specification of fora or consortia standards will enter into force 20 days after its publication in the EU Official Journal and will apply directly in all EU member states from 1 January 2013.)
    498. 

  498. 

  499. Fair access - the standard is published, thoroughly documented and publicly available at zero or low cost. Zero cost is preferred but this should be considered on a case by case basis as part of the selection process. Cost should not be prohibitive or likely to cause a barrier to a level playing field.
    500. 

  500. 

  501. Market support - other than in the context of creating innovative solutions, the standard is mature, supported by the market and demonstrates platform, application and vendor independence.
    502. 

  502. 

  503. Rights - rights essential to implementation of the standard, and for interfacing with other implementations which have adopted that same standard, are licensed on a royalty free basis that is compatible with both open source (see a list of open source licences approved by the Open Source Initiative via their License Review Process) and proprietary licensed solutions. These rights should be irrevocable unless there is a breach of licence conditions.
    504. 

  504. &lt;/blockquote>
    505. 

  505. 

  506. === The Indian definition (an example of strictest approach) ===
    507. 

  507. Another very strict definition is the one for India's Government &lt;ref name="Policy in India">{{cite web|last1=Government of India|title=Policy on Open Standards for e-Governance|url=https://egovstandards.gov.in/sites/default/files/Published_Policy_Framework_Document/Policy%20on%20Open%20Standards%20for%20e-Governance.pdf|accessdate=25 July 2014|ref=india}}&lt;/ref>
    508. 

  508. 

  509. &lt;blockquote>
    510. 

  510. '''4.1 Mandatory Characteristics'''
    511. 

  511. An Identified Standard will qualify as an “Open Standard”, if it meets the following criteria:
    512. 

  512. *4.1.1 Specification document of the Identified Standard shall be available with or without a nominal fee.
    513. 

  513. * 4.1.2 The Patent claims necessary to implement the Identified Standard shall be made available on a Royalty-Free basis for the life time of the Standard.
    514. 

  514. * 4.1.3 Identified Standard shall be adopted and maintained by a not-for-profit organization, wherein all stakeholders can opt to participate in a transparent, collaborative and consensual manner.
    515. 

  515. * 4.1.4 Identified Standard shall be recursively open as far as possible.
    516. 

  516. * 4.1.5 Identified Standard shall have technology-neutral specification.
    517. 

  517. * 4.1.6 Identified Standard shall be capable of localization support, where applicable, for all Indian official Languages for all applicable domains.
    518. 

  518. &lt;/blockquote>
    519. 

  519. 

  520. === Many more definitions ===
    521. 

  521. 

  522. These are just samples to show how strong the debate on Open Standards is and what the centerpoint of the discussion is: patents, or patent holders trying to extract royalty revenues for any time a standard is used; and claiming that a patent license, with attached conditions for use, should be agreed upon, even though on a "FRAND" basis. As of August 2014, Wikipedia counted no less than 20 different definitions, and undoubtedly many more exist. &lt;ref>{{cite web|title=Open Standard|url=https://en.wikipedia.org/wiki/Open_standard#Specific_definitions_of_an_open_standard|website=Wikipedia|accessdate=7 August 2014}}&lt;/ref>
    523. 

  523. 

  524. === The RFCs ===
    525. 

  525. 

  526. "RFCs" (shorthand for "Request For Comments") are specifications which do not qualify as ''de iure'' standards (standards adopted by internationally recognised standard setting bodies after a formal process"), but nonetheless are respected and complied with as if they were formal standards. RFCs which is one of the ways that many of the most used Internet protocols have born and evolve.
    527. 

  527. 

  528. RFCs are akin to formal standards, because an authoritative and documented source of normative and explanatory text exists. They have been adopted since the times of the ARPANET project ("Advanced Research Projects Agency Network" the initial network from which Internet originated) &lt;ref>{{cite news|url=http://www.nytimes.com/2009/04/07/opinion/07crocker.html?_r=1&amp;em |title=Stephen D. Crocker, '&amp;#39;How the Internet Got Its Rules'&amp;#39;, The New York Times, 6 April 2009 |publisher=Nytimes.com |date= April 7, 2009|accessdate=2014-07-25}}&lt;/ref> and evolved over the times. RFCs are now a body of standards collected and organised by the IETF (Internet Engineering Task Force)&lt;ref>IETF (Internet Engineering Task Force) http://ietf.org/&lt;/ref> and by the less famous Internet Society&lt;ref>Internet Society http://www.internetsociety.org/&lt;/ref>.
    529. 

  529. 

  530. They should not be underestimated, as they are at the foundation of some of the most important and widely used protocols, such as the protocols that make the Internet email system &lt;ref>e.g., the IMAP Protocols, see among them {{cite web|title=IMAP protcol, RFC1064|url=http://tools.ietf.org/html/rfc1064|accessdate=25 July 2014}}&lt;/ref>
    531. 

  531. 

  532. IETF's RFCs are generally considered Open Standards, and are commonly understood as "Royalty Free" Open Standards, although the "IPR policies" (the rules according to which technologies can be introduced into the RFCs depending on the "Intellectual Property Rights" – mostly patents rights – are claimed by the contributing party) allow for royalty-bearing licensing of the included technologies. &lt;ref>See IETF RFC 3979{{cite web|title=IETF, RFC 3979,|url=https://datatracker.ietf.org/doc/rfc3979/?include_text=1|accessdate=25 July 2014}}&lt;/ref>
    533. 

  533. 

  534. == Free and Open Source Software (FOSS) ==
    535. 

  535. 

  536. ==== Definitions ====
    537. 

  537. 

  538. There are two separate definitions on what is Free and what is Open Source Software. &lt;ref name=piana_eup_juri>For an historical and general overview of Free and Open Source Software we refer to a briefing paper prepared for the Juri Commitee by Carlo Piana, which covers much of the background of Free Software {{cite journal|last1=Piana|first1=Carlo|title=A discussion of the different software licensing regimes|journal=WORKSHOP ON LEGAL ASPECTS OF FREE AND OPEN SOURCE SOFTWARE|pages=30-49|url=http://www.europarl.europa.eu/document/activities/cont/201307/20130708ATT69346/20130708ATT69346EN.pdf|accessdate=7 August 2014}}&lt;/ref>
    539. 

  539. 

  540. * The Free Software Definition (by the Free Software Foundation) &lt;ref>{{cite web|title=What is free software - The Free Software Definition|url=https://gnu.org/philosophy/free-sw.html|accessdate=7 August 2014}}&lt;/ref>
    541. 

  541. 

  542. &lt;blockquote>
    543. 

  543. A program is free software if the program's users have the four essential freedoms:
    544. 

  544. 

  545. * The freedom to run the program as you wish, for any purpose (freedom 0).
    546. 

  546. * The freedom to study how the program works, and change it so it does your computing as you wish (freedom 1). Access to the source code is a precondition for this.
    547. 

  547. * The freedom to redistribute copies so you can help your neighbor (freedom 2).
    548. 

  548. * The freedom to distribute copies of your modified versions to others (freedom 3). By doing this you can give the whole community a chance to benefit from your changes. Access to the source code is a precondition for this.&lt;/blockquote>
    549. 

  549. 

  550. * The Open Source Definition (by the Open Source Initiative)
    551. 

  551. 

  552. This is a slightly more verbose definition (only headlines are provided, for brevity):&lt;ref name=OSD>Full text at {{cite web|title=The Open Source Definition|url=http://opensource.org/osd|website=OSI|accessdate=7 August 2014}}&lt;/ref>
    553. 

  553. 

  554. &lt;blockquote>
    555. 

  555. # Free Redistribution
    556. 

  556. # Source Code
    557. 

  557. # Derived Works
    558. 

  558. # Integrity of The Author's Source Code
    559. 

  559. # No Discrimination Against Persons or Groups
    560. 

  560. # No Discrimination Against Fields of Endeavor
    561. 

  561. # Distribution of License
    562. 

  562. # License Must Not Be Specific to a Product
    563. 

  563. # License Must Not Restrict Other Software
    564. 

  564. # License Must Be Technology-Neutral
    565. 

  565. 

  566. &lt;/blockquote>
    567. 

  567. 

  568. Although the two definitions are different, it is difficult – nay impossible ‒ to find a subset of licenses that qualify under one definition and are outside the other definition, therefore, for our scopes, we will treat Free Software and Open Source Software (i.e., software licensed under either definition) as synonyms.
    569. 

  569. 

  570. ==== Is that about it? ====
    571. 

  571. 

  572. There is no serious contention as to whether Free Software is the golden standard for openness in software.
    573. 

  573. 

  574. Yet, if openness is a continuum, there are lesser forms of openness also in the software making. For instance, claims can exist that proprietary platforms that implement standard interfaces are "open", and indeed some form of openness exists also in ultra-proprietary software like Microsoft Windows. &lt;ref>Or at least it has been claimed. See for instance {{cite book|last1=Jansen|first1=Slinger|last2=Cusumano|first2=Michael A.|last3=Brinkkemper|first3=Sjaak|title=Software Ecosystems: Analyzing and Managing Business Networks in the Software Industry|publisher=Edward Elgar Publishing|date=2013|page=163}}&lt;/ref> Interoperability is a form of openness, standards are a form of openness, also in software.
    575. 

  575. 

  576. However, when it comes to software, the four freedoms granted by Free Software are not an easy yardstick with which to be measured. Full access to code, especially when it is enforceable through the ''"copyleft"'' conditions, has many advantages that go beyond the much touted "bazaar model" of development. &lt;ref>{{cite web|last1=Raymond|first1=Eric S.|title=The Cathedral and the Bazaar|url=http://www.catb.org/esr/writings/cathedral-bazaar/|accessdate=11 August 2014}}&lt;/ref> Access to code and the legal permissions that the license provide mean anyone with sufficient skills can take over the program and "fork" it (forking means that someone parts from the current development and starts a new independent development branch). In other words, while full access to code does not mean that backdoors and insecurities cannot be inserted, they are quite easily discovered and easily fixed. But in essence, full access to code and the legal permissions that the license convey means that there is an assurance that the software development can proceed even in the event that for any reason relationships with the original developer become problematic.
    577. 

  577. 

  578. The most important point is that in a Free Software environment, where the user benefits from the four freedoms and the legal permissions that this brings to them, from an economic point of view a new game (as in the Gaming Theory) is created, compared to what happens in a proprietary environment. This game creates a reassurance against lock-in, because most of the techniques that have been so far used to force clients to stay with one vendor have little meaning where an exact replica of the entire set of applications can be obtained from other sources, and further development of them can be taken over from any arbitrary point. Let us discuss it in more depth.
    579. 

  579. 

  580. == Lock in ==
    581. 

  581. 

  582. So far we have dealt with Free and Open from the perspective of having an unimpaired access to information and data. In other words, to have communication channels that allow content to flow without impairment from one point of the channel to the other. We have seen that certain decisions should be taken to maximize the chances of this happening.
    583. 

  583. 

  584. However, as with any decision, decision-makers are not always at liberty to choose what is theoretically best. '''Budgetary restrictions''', for instance, are an obvious obstacle to this freedom, therefore choices need to be made under the condition of best allocation of non-unlimited resources. '''Time''' is another constraint. If, due to circumstances, choosing a solution requires considerable time, a quicker solution might be preferable, albeit suboptimal in other terms. '''Technical constraints''' also exist, and interact heavily with both of the previously mentioned ones.
    585. 

  585. 

  586. "Technical constraints" deriving from what already is in place (technical infrastructures, previous investments in technology, archives) is what is usually called '''"lock-in"'''.
    587. 

  587. 

  588. Lock-in is a phenomenon where previous choices reduce the freedom to make future choices, because making them would mean relinquishing a seizable part of the investment made in the past. Therefore, it seems to make sense to choose the solution that best adapts to the existing environment, albeit suboptimal in general terms, because the best option would be anti-economical due to the need to change substantial parts of the existing environment. This also generates, and most of the time increases, the lock-in.
    589. 

  589. 

  590. Locked-in solutions might not allow achievement of the goal of transparency, because budgetary and time constraints work against it.
    591. 

  591. 

  592. The Commission has analysed this phenomenon with a lot of care, although sometimes it proved itself unwilling to take the medicine it prescribed to others,&lt;ref>{{cite web|title=European Commission renews controversial Microsoft contract|url=http://www.computerweekly.com/news/1280095047/European-Commission-renews-controversial-Microsoft-contract|accessdate=9 December 2014}}&lt;/reF> within Action 23 of the Digital Agenda. &lt;ref>{{cite web|title=Action 23: Provide guidance on ICT standardisation and public procurement|url=http://ec.europa.eu/digital-agenda/content/action-23-provide-guidance-ict-standardisation-and-public-procurement|accessdate=8 August 2014}}&lt;/ref> The Commission identified lock-in as an important problem that can only be cured with the adoption of open standards ‒ although, as we have seen before, it failed to define properly what an open standard is and it showed a weak spine in taking the concept of openness where others took it.
    593. 

  593. 

  594. &lt;blockquote>
    595. 

  595. The Digital Agenda for Europe identified "lock-in" as a problem. Building open ICT systems by making better use of standards in public procurement will improve and prevent the lock-in issue. &lt;ref>{{cite web|title=Open Standards|url=http://ec.europa.eu/digital-agenda/en/open-standards|accessdate=8 August 2014}}&lt;/ref>
    596. 

  596. &lt;/blockquote>
    597. 

  597. 

  598. Therefore standards are a way to avoid lock-in. The Commission carefully avoids using the wording "open standards", but many indications and references make it clear that it points to that when it refers to "standard based procurement". The two main working documents describing how public procurement should be done to avoid lock-in are in
    599. 

  599. 

  600. * A Communication titled "Against lock-in: building open ICT systems by making better use of standards in public" &lt;ref>{{cite web|title=Against lock-in: building open ICT systems by making better use of standards in public|url=http://ec.europa.eu/digital-agenda/news/against-lock-building-open-ict-systems-making-better-use-standards-public|accessdate=8 August 2014}}&lt;/ref>
    601. 

  601. 

  602. * A staff working document "Guide for the procurement of standards-based ICT — Elements of Good Practice" &lt;ref>{{cite web|title=Guide for the procurement of standards-based ICT — Elements of Good Practice|url=http://ec.europa.eu/digital-agenda/news/guide-procurement-standards-based-ict-%E2%80%94-elements-good-practice|accessdate=8 August 2014}}&lt;/ref>
    603. 

  603. 

  604. Proceeding from the above, we can safely take a few conclusions:
    605. 

  605. 

  606. * in order be free to adopt the best tools available, now and in a medium to long term, the Parliament has a special burden to avoid lock-in.
    607. 

  607. * Because the best tool to avoid lock-in, according to the Commission (but with the agreement of a vast literature, as cited in the two above documents), is a standard-based approach, the Parliament is especially bound to adopt a standard-based approach in procurement.
    608. 

  608. * Not only transparency mandates the use of open standards for the outward channel, but transparency leans heavily towards the use of standard-based decisions and modular, vendor independent, lock-in averted solutions.
    609. 

  609. 

  610. The cited documents take no stance towards (or against, for that matter) '''Free Software''' in the lock-in avoidance context. However it seems that one cannot take any conclusions from this omission, only that the lock-in avoidance shall be taken into consideration with all kind of licensing regimes or development environment or technology. At the same time there seems to be no contradiction in the principle we have introduced that Free Software enhances the anti-lock-in power of the user (so much that even the user has the permission to be developer). And we reiterate the fundamental concepts:
    611. 

  611. 

  612. * Truly Free Software solutions are outside the control of the vendor. The vendor can have a temporary control or even have a stronghold over one solution, but examples exist that when this control is too tight and against the interests of the Community, the ability to "fork" is an essential tool that exerts a constraint on any dictatorial vendor. &lt;ref>A useful discussion on what the ability to fork means in terms of relieving competition concerns can be found in {{cite web|title=Commission Decision of 21.01.2010 declaring a concentration to be compatible with the common market and the functioning of the EEA Agreement(Case No COMP/M.5529 - Oracle/ Sun Microsystems)|url=http://ec.europa.eu/competition/mergers/cases/decisions/m5529_20100121_20682_en.pdf|accessdate=10 November 2014}}, Section 4.4.3 (pag. 118 onwards).&lt;/ref>
    613. 

  613. * The availability of source code, and possibly a healthy and diverse development community, is a guarantee that there is no orphan work or constrained upgrade path. Free Software allows the choice to buy or make, or to have made by others unrelated to the copyright holder.
    614. 

  614. * Proprietary software vendors have incentives and abilities to lock clients in &lt;ref> The most striking example is probably the ''Microsoft'' case {{cite web|title=Commission Decision of 24.03.2004 relating to a proceeding under Article 82 of the EC Treaty (Case COMP/C-3/37.792 Microsoft)|url=http://ec.europa.eu/competition/antitrust/cases/dec_docs/37792/37792_4177_1.pdf|accessdate=10 November 2014}} &lt;/ref>. Free Software vendors have less, or even no incentives toward locking their clients in, because efforts would be largely ineffective or impossible. De facto, most of Free Software project tend to use open standards,and non open standards and format only if network effects make the former non viable.
    615. 

  615. * The European Parliament should use IT solutions guaranteed to be independent from IT vendors. Instead of making IT decision based on cost, it should prefer technologies that allow others to work with it.
    616. 

  616. 

  617. == Free and Open data and content ==
    618. 

  618. 

  619. If transparency means being able to receive information, in a legal environment that means "data" and "content". Protection of data and content under European law occurs under three main headlines:
    620. 

  620. * Secrecy (or confidentiality)
    621. 

  621. * Copyright (or ''"droit d'auteur"''), which may or may not include "moral rights"
    622. 

  622. * Data base (or ''"sui generis"'') protection
    623. 

  623. 

  624. We can safely exclude "secrecy" from our analysis. Except for the matters that, in case, must be kept secret for any reasons, the transparency rule is the opposite of the secrecy rule.
    625. 

  625. 

  626. Copyright and data base protection require more in depth analysis.
    627. 

  627. 

  628. === Copyright ===
    629. 

  629. 

  630. Copyright is uniformly regulated across Europe, under the general umbrella of the Berne Convention, by the implementation at member states' level the "Copyright Directive" &lt;ref>Directive 2001/29/EC of the European Parliament and of the Council [http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=CELEX:32001L0029:EN:HTML].&lt;/ref>. Fully analysing the working of copyright is beyond the scope of the research, as it is discussing the slight differences in the single Member States implementations, particularly in terms of exceptions to copyright.
    631. 

  631. 

  632. Law texts are generally recognised as not bearing copyright. However, all preparatory works, studies, briefing papers, analyses and other documents can have a different status according to whom has prepared them and under which arrangement with the Parliament.
    633. 

  633. 

  634. Under the default copyright regime, the copyright holder has a number of rights to prevent others from performing certain actions, including copying, transforming, translating the copyrighted content. This right arises with the making of the copyrightable subject without the need of any affirmative step or claim. Silence is sufficient.
    635. 

  635. 

  636. Under such regime, irrespectively of the actual copyright status under which certain material is being served onto the public, even uncertainty as to the copyright status of certain works can have a chilling effect on the transparency and prevent it from achieving its fullest implementation.
    637. 

  637. 

  638. One of the enablements of the Internet (and open standards) is the ability to re-use and transform content to produce new service that provide the same content in innumerable new ways. That could include a "syndication" of content, mash-ups, translations &lt;ref>"A mash-up, in web development, is a web page, or web application, that uses content from more than one source to create a single new service displayed in a single graphical interface." See http://en.wikipedia.org/wiki/Mashup_%28web_application_hybrid%29. Similarly, syndication means aggregation of content from various sources. See for reference http://en.wikipedia.org/wiki/Web_syndication&lt;/ref>. Anywhere there is unmet demand for services containing the same information, there can be a service from an unexpected source. Sometimes this service is brought by private, amateur service providers, who have no resources or knowledge to fully inspect all sources to verify if they are freely re-usable in automatically aggregated content. Some do it nonetheless, other might be discouraged from re-sharing the (modified) content on copyright grounds. This is not unexpected in an environment where prohibition is the rule and free use is an exception.
    639. 

  639. 

  640. It is therefore important, in the view of the authors, that any time when the rules would allow free re-use of the content, including translation, transformation, aggregation, it is explicitly stated in a clear and irrevocable way. Absent a clear and final rule that puts the content in "public domain", there should be a default "licensing statement" to clarify the legal status of it. We submit that removing any uncertainties is a step in the right direction. That is, ensuring that all information subject to transparency be '''Open Content'''.
    641. 

  641. 

  642. Legal instruments exist to this effect. The most known set of these instruments with regard to creative content is the Creative Commons&lt;ref>Creative Commons http://creativecommons.org/&lt;/ref> one. In particular, the Creative Commons Attribution - only license and the Creative Commons CC-zero (or CC-0) seem to be the most appropriate for implementing an affirmative open content strategy where the copyright status of the work so permits. In order for it to be possible, all material prepared for and upon instruction of the Parliament needs to be licensed by their authors under the same or compatible licenses.
    643. 

  643. 

  644. Because this is an analysis of open content only from the point of view of transparency, we defer to the many studies on the open content in the public sector for a more detailed discussion.
    645. 

  645. 

  646. === (Open) Data ===
    647. 

  647. 

  648. The same reasoning is applicable to the data. The ability to drill into data to distil information is generally understood to be a key to transparency. &lt;ref>{{cite web|title=Democracy and open data: are the two linked?|url=http://congressionaldata.org/democracy-and-open-data-are-the-two-linked/|accessdate=14 October 2014}}&lt;/ref> In order to perform actions on data it is necessary that not only data are made available, i.e., disclosed, but that all the actions necessary to perform the analysis and meta-analysis are permitted. This might not always be the case or uncertainty could exist on it.
    649. 

  649. 

  650. Datasets are protected in Europe by the Database Directive, as implemented by member states. &lt;ref>{{cite web|title=Directive 96/9/EC of the European Parliament and of the Council of 11 March 1996 on the legal protection of databases|url=http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=CELEX:31996L0009:EN:HTML|accessdate=8 August 2014}}&lt;/ref>
    651. 

  651. 

  652. The Database Directive provides a protection of database on which the maker has put a significant investment in the obtaining, verification or presentation of the contents. This protection is a different kind from copyright or patent protection, and therefore is called ''"sui generis"'' (of its own kind) and, like the copyright, is granted without any affirmative action, including issuing an express claim, by the maker. Therefore, in default of an express license or waiver, the principle is that the extraction, duplication and dissemination of the dataset (or of a substantial part thereof) is reserved to the maker.
    653. 

  653. 

  654. Therefore, in order for datasets to be re-used, and thus to enhance their availability, id est, transparency, data should be treated as long as possible as "Open Data". &lt;ref>An open data definition, modelled upon the Open Source Definition can be found at {{cite web|title=Open Definition|url=http://opendefinition.org/od/}}&lt;/ref> Open data in the public sector is such a common ground that many states have stated in full the principle that data by default should be open. &lt;ref>See for instance US's {{cite web|title=Executive Order -- Making Open and Machine Readable the New Default for Government Information|url=http://www.whitehouse.gov/the-press-office/2013/05/09/executive-order-making-open-and-machine-readable-new-default-government-|accessdate=8 August 2014}}&lt;/ref> Among them the G8 countries have adopted a clear document favouring the use of Open Data. &lt;ref>{{cite web|title=Open Data Charter|url=https://www.gov.uk/government/publications/open-data-charter|accessdate=8 August 2014}}&lt;/ref> &lt;ref>A useful resource for information on open data in a governmental environment can be found at {{cite web|title=Citizens, democratic accountability and governance|url=https://okfn.org/opendata/why-open-data/citizenship-and-governance/|website=Open Knowledge|accessdate=8 August 2014}}&lt;/ref> &lt;ref>{{cite web|title=Open Data: unleashing the potential|url=https://www.gov.uk/government/publications/open-data-white-paper-unleashing-the-potential|website=Gov.UK|accessdate=10 November 2014}}&lt;/ref> Across Europe, a drive towards open data is given also by the PSI Directive, which prescribes that certain data held and produced by the Public Administration at large be made available for industry perusal &lt;ref name=psi>{{cite web|title=European legislation on reuse of public sector information|url=https://ec.europa.eu/digital-agenda/en/european-legislation-reuse-public-sector-information}}&lt;/ref>.
    655. 

  655. 

  656. The European Commission, not bound to the PSI Directive, recognising the importance that all data produced by it be available to the general public as much as possible in an open and unencumbered fashion, and possibly also in a machine-readable format , has adopted a Decision on re-use of Commission documents (2011/833/EU)&lt;ref>{{cite web|title=Rules for the re-use of Commission information|url=https://ec.europa.eu/digital-agenda/en/news/rules-re-use-commission-information|accessdate=14 October 2014}}&lt;/ref>, adopting an open by default rule (Art. 9). As for the formats, Art. 8 of said Decision provides:
    657. 

  657. 

  658. &lt;blockquote>Article 8
    659. 

  659. Formats for documents available for reuse
    660. 

  660. 

  661. 1. Documents shall be made available in any existing format or language version, in machine-readable format where possible and appropriate.
    662. 

  662. 

  663. 2. This shall not imply an obligation to create, adapt or update documents in order to comply with the application, nor to provide extracts from documents where it would involve disproportionate effort, going beyond a simple operation.
    664. 

  664. 

  665. 3. This Decision does not create any obligation for the Commission to translate the requested documents into any other official language versions than those already available at the moment of the application.
    666. 

  666. 

  667. 4. The Commission or the Publications Office may not be required to continue the production of certain types of documents or to preserve them in a given format with a view to the reuse of such documents by a natural or legal person.&lt;/blockquote>
    668. 

  668. 

  669. While fully analysing the licensing of data goes beyond the scope of this study, and while the discussion on open standards also covers the ''way'' (or format) in which data are made available for non-intermediated consumption, we suggest that not only for transparency purpose, but in order to generally remove unnecessary confusion, that instead of '''licensing''' data, a '''waiver''' on database right is adopted as default legal release tool. &lt;ref>One of the authors has explained this finding in {{cite web|title=FreeGIS.net Data Licence 1.0|url=https://freegis.net/documents/10157/14646/FreeGIS+data+licence+1?version=1.0}} [ITA], but see also {{cite web|last1=Morando|first1=Federico|title=http://leo.cineca.it/index.php/jlis/article/view/5461|url=http://leo.cineca.it/index.php/jlis/article/view/5461|accessdate=8 August 2014}}&lt;/ref>
    670. 

  670. 

  671. = Practical applications =
    672. 

  672. 

  673. Here we will use the findings in the previous sections to analyse what in practice the principles mean in different areas of the Parliament's IT systems.
    674. 

  674. 

  675. == Email system ==
    676. 

  676. 

  677. Despite the emergence of social networks and other public, semipublic and semiprivate communications tools, emails remain by and large a ubiquitous way of communicating, both individually (one-to-one) and on a larger scale (one-to-many, many-to-many) for example via discussion lists.
    678. 

  678. 

  679. All the Members of the European Parliament and their staff are given a personal mailbox that they can use for their institutional activities. The addresses of the MEP are public and the public uses them to reach the MEPs, e.g., for campaigning purposes.
    680. 

  680. 

  681. Meanwhile, the email system is threatened by all sort of attacks, because of its very nature of being decentralised, lightweight and unverified. These attacks range from simple "spam" (unsolicited emails) to scams (email messages trying to illegally induce the recipient to perform certain activities), to conveying malicious code. In addition, email is often used to illegally collect information pertaining to the recipient (from simple profiling up to "phishing", an attack that strives to collect sufficient information to actually steal money or overcome protections), if not compromising the secrecy of the communication by intercepting the flow of email exchange (e.g, through "man-in-the-middle" attacks).
    682. 

  682. 

  683. === Basic introduction to the standard infrastructure ===
    684. 

  684. 

  685. The email system, which is basically made of two server components (one for sending the outbound emails, one for receiving, storing and forwarding to the recipient) and one client component.
    686. 

  686. 

  687. The standard server components are
    688. 

  688. * the Simple Mail Transfer Protocol (SMTP)&lt;ref>http://tools.ietf.org/html/rfc5321&lt;/ref> for relaying and sending the messages out;
    689. 

  689. * and the Internet Message Access Protocol (IMAP)&lt;ref>http://tools.ietf.org/html/rfc3501&lt;/ref> and the Post Office Protocol (POP)&lt;ref>http://tools.ietf.org/html/rfc1939&lt;/ref> for accepting, storing and making available the inbound message.
    690. 

  690. 

  691. The client component can be a local application, installed on a computer, or a web application ‒ often referred to as "webmail" ‒ which offers retrieving, reading, composing and sending services that replicate those of the local application, without the need to locally download the message.
    692. 

  692. 

  693. Some providers have developed proprietary extensions to these protocols and services, probably the most popular is the MAPI protocol that links together the client Microsoft Outlook (and other clients that implement the protocol) with Microsoft Exchange Server &lt;ref>{{cite web|url=http://msdn.microsoft.com/en-us/library/cc307725%28EXCHG.80%29.aspx|accessdate=7 October 2014|title=Exchange Server Protocols}}&lt;/ref> , but also Google's Gmail and Apple's Mail use proprietary protocols, especially for mobile consumption of the email services.
    694. 

  694. 

  695. If for the outside world, using those proprietary client/server protocols makes very little difference, as the email is sent and received through standard protocols (although compliance with content and transport standards can vary), it is important that their adoption does not impair the ability of clients that do not implement them to access the email without impairment.
    696. 

  696. 

  697. === A standard secure layer from client to server ===
    698. 

  698. 

  699. It is important that the email can only be sent and received by authenticated users. In other words, email shall receive a high degree of protection.
    700. 

  700. 

  701. IMAP requires userid and password to access the email, and offers secure connection between the client and the server so that the flow of communication cannot be intercepted between the server and the client (most commonly with SSL/TSL)&lt;ref>http://tools.ietf.org/html/rfc5246&lt;/ref>
    702. 

  702. 

  703. Similarly SMTP allows both user authentication and encryption of the flow, although many publicly available SMTP servers do not require either.
    704. 

  704. 

  705. On privacy concerns, it is highly recommendable that both are in use, as they create a readily available layer of security at virtually no expense. According to art. 22.1 of Regulation (EC) No 45/2001, the data controller (as well as a third party processor or service provider) shall comply with the following rule:
    706. 

  706. 

  707. &lt;blockquote>Having regard to the state of the art and the cost of their implementation, the controller shall implement appropriate technical and organisational measures to ensure a level of security appropriate to the risks represented by the processing and the nature of the personal data to be protected.&lt;/blockquote>
    708. 

  708. 

  709. As TLS is a publicly available standard, using it is highly recommendable.&lt;ref>This is very basic advice, securing an email system is well beyond the scope of this work and the expertise of the authors. Many guidelines can be found online, supporting this finding and more, like http://www.cisco.com/web/about/security/intelligence/bpiron.html or https://otalliance.org/best-practices/transport-layered-security-tls-email&lt;/ref>
    710. 

  710. 

  711. TLS only protects the data stream from the originating point (the client for outbound and SMTP for incoming email) to the first endpoint (the SMTP server for outbound and the client for incoming email). Once the email has left the internal system, it is bound to be transmitted in clear over the Internet. In order to secure the content from the sender to the recipient, the only way is full encryption of the message, as the message itself will be relayed through an arbitrary number of servers as plain text.
    712. 

  712. 

  713. The two most used ways of (directly)&lt;ref>Obviously an email message can have arbitrary encoded files, including encrypted ones, here we are only dealing with encrypted messages that are recognised directly by the client application without the need to open them outside, and with the ability to have a "seamless" email discussion&lt;/ref> encrypting the messages are S/MIME&lt;ref>http://tools.ietf.org/html/rfc5751&lt;/ref> and OpenPGP&lt;ref>http://tools.ietf.org/html/rfc4880&lt;/ref>, neither of which is an approved standard, although they are implemented directly or through third parties in many email clients, so they satisfy many of the requirements for being open standards (fully public and available standard text, independently managed, multiple independent implementations, no known IPR). Although the adoption of email encryption seems to be very limited, the case for allowing encrypted emails to flow through the servers is clear also from a transparency point of view (no pun intended).
    714. 

  714. 

  715. Encrypted email cannot be scanned by security systems and therefore they are likely to be intercepted by them. This would be a ''false positive'', though, since it would be a legitimate email. In order to preserve the viability of an encrypted channel of communication, this kind of messages should be whitelisted, at least at the user request, and in any case any such blocked message should be notified to the user, put into a quarantine and the user should be enabled to open it.
    716. 

  716. 

  717. === Mailing lists ===
    718. 

  718. 

  719. Emails are complementary to the use of mailing lists, which are particularly useful discussion fora when discussion occurs by threading them via an email discussion. To do so certain rules in both RFC5321 (section 3.9) and RFC2369 &lt;ref>http://www.ietf.org/rfc/rfc2369.txt&lt;/ref> should be implemented.
    720. 

  720. 

  721. From a discussion in a Freedom Of Information access request &lt;ref>Interoperability with the EP's mail systems http://www.asktheeu.org/en/request/interoperability_with_the_eps_ma &lt;/ref> it looks like any such request coming from an external mailing list is outright refused by the European Parliament's systems, on the grounds that the address is considered not genuine ("spoofed"). However, a message sent by a member of a mailing list to the mailing list and relayed by the mailing list to its subscribers (including the sender) needs to contain the from: and reply-to: address of the originating email message must not be modified, and obviously this would cause the address of the incoming email being considered not genuine (again, "spoofed") according to the criterion that all messages from a European Parliament address must come from a European Parliament SMTP server. However, this is absolutely not mandated by the standard protocols (it is indeed ''normal'' that an address comes from an SMTP in a domain different from the domain of the originating address) and impedes the users of the European Parliament system to participate in external discussion mailing lists.
    722. 

  722. 

  723. This seems in stark contradiction with the principle of transparency.
    724. 

  724. 

  725. == Publishing and archiving documents ==
    726. 

  726. 

  727. Publishing information in the form of documents can be achieved through numerous ways, the most common of which is through the World Wide Web and its HTML/XML standards. These standards are mainly meant for files being uploaded to or generated by content management services and be read via a browser by the general public.
    728. 

  728. 

  729. However, people rarely work with web pages and web pages are most of the time not just documents. Individuals and working groups still use "standalone" documents that they share, edit, print, archive and make available to a larger audience, and these documents are still largely based on the same model of paper documents and are made using document applications (such as wordprocessors, spreadsheets, presentations applications). As the bulk of the documents produced by public institutions are generated, kept and electronically exchanged in their original form, or "printed" and exchanged as if they were on paper, many times it has been suggested that the use of proprietary and non standard documents tilt the table in favour of the proponents of those documents and at the same time limit the access to those document by those who do not use the applications made by the same proponents.
    730. 

  730. 

  731. The state of Massachusetts has perhaps been the first taking action to solve this situation and mandate the use of open standards in document files made and exchanged by the public administration. &lt;ref>{{cite web|title=Massachusetts moves ahead sans Microsoft|url=http://news.cnet.com/Massachusetts-moves-ahead-sans-Microsoft/2100-1012_3-5878869.html|accessdate=13 October 2014}}&lt;/ref>. It will take too long to narrate the discussion that ensued. At the time of writing, the last large government to take action in this regard has been the UK Cabinet, which has opened a very large consultation and performed a thorough analysis of the best way to achieve "transparency and accountability of government and its services".&lt;ref>{{cite web|title=Improving the transparency and accountability of government and its services|url=https://www.gov.uk/government/policies/improving-the-transparency-and-accountability-of-government-and-its-services|accessdate=13 October 2014}}&lt;/ref> Citing from the premises of this study:
    732. 

  732. 

  733. &lt;blockquote> [...] in order for data to be used this way, it has to be released in a format that will allow people to share it and combine it with other data to use it in their own applications. This is why transparency isn't just about access to data, but also making sure that it is released in an open, reusable format. &lt;/blockquote>
    734. 

  734. 

  735. In terms of publishing documents, the conclusion has been: &lt;ref>{{cite web|title=Open document formats selected to meet user needs|url=https://www.gov.uk/government/news/open-document-formats-selected-to-meet-user-needs|accessdate=13 October 2014}}&lt;/ref>
    736. 

  736. 

  737. &lt;blockquote>
    738. 

  738. * '''PDF/A''' or '''HTML''' for viewing government documents
    739. 

  739. * '''Open Document Format''' (ODF) [ISO/IEC IS26300] for sharing or collaborating on government documents&lt;/blockquote>
    740. 

  740. 

  741. 

  742. == Surveillance and privacy ==
    743. 

  743. 

  744. Electronic communications via Internet are exposed to mass surveillance and the privacy of those who use it is constantly at risk.
    745. 

  745. 

  746. The use of open standards goes in the direction of enabling multiple parts to interoperate and access to the source of information. Whereas recently it has been alleged that a few subjects (mainly governments and governmental agencies) may have achieved the ability to scan and retain information on virtually any electronic communications -- whether through the collection of "metadata" or actual recordings of content exchanged -- the use of open standards is a way to minimize the chances that other subjects may also achieve a similar control.
    747. 

  747. 

  748. Internet was born and has grown as a deeply decentralised ecosystem. Market forces may or may not lead to a less decentralised situation in the future, with concentration in the hands of few. The European Parliament, as any public institution, should be aware of the impact that its decision have in exposing the privacy of their citizens that interact with their services by forcing them to use technologies which are available only through certain operators. Or worse, through services directly in the hands of them.
    749. 

  749. 

  750. Similar conclusions seem to have been taken by the European Parliament Resolution of 12 March 2014 on the US NSA surveillance programme, surveillance bodies in various Member States and their impact on EU citizens’ fundamental rights and on transatlantic cooperation in Justice and Home Affairs (2013/2188(INI)):&lt;ref>http://www.europarl.europa.eu/oeil/popups/ficheprocedure.do?lang=en&amp;reference=2013/2188%28INI%29&lt;/ref>
    751. 

  751. 

  752. &lt;blockquote> 91. Takes the view that the mass surveillance revelations that have initiated this crisis can be used as an opportunity for Europe to take the initiative and build up, as a strategic priority measure, a strong and autonomous IT key-resource capability; stresses that in order to regain trust, such a European IT capability should be based, as much as possible, on open standards and open-source software and if possible hardware, making the whole supply chain from processor design to application layer transparent and reviewable;&lt;/blockquote>
    753. 

  753. 

  754. = Conclusions =
    755. 

  755. 

  756. The Court of Justice has reminded us, the European citizenry, that openness contributes to strengthening our democracy, by enabling us to scrutinise all the information which has formed the basis for a legislative act. This means that we, the citizens of Europe, should be able to see, evaluate and analyse all the information used in the drafting of any EU law. The possibility we have to scrutinise the considerations underpinning legislative action is in fact a precondition for the effective exercise of our democratic rights.
    757. 

  757. 

  758. Going beyond the constitutional requirement of openness laid down by the Treaties, the European Parliament has imposed upon itself a further commitment to conduct its activities with the utmost transparency. Our study suggests that ensuring this "utmost transparency" is not only an essential procedural requirement but actually a fundamental democratic principle which brings precise duties.
    759. 

  759. 

  760. Thus, the principle of openness should guide Parliament's choices of IT hardware and software systems and, as technology evolves, these choices should be continuously and pro-actively reassessed. By its own standard, Parliament should choose the systems and technologies that are the most open and the most accessible to the public.
    761. 

  761. 

  762. But beyond that, the principle also concerns possible legal restrictions on further distribution and use of the resources made available, including independent analysis, aggregation, re-use and redistribution of the data. Such restrictions should never undermine the basic requirements of openness and utmost transparency. On the contrary, Parliament must use systems, technologies and software that allow for the free-est analyses, re-uses and re-releases of its data: these are essential activities in a modern democratic society.
    763. 

  763. 

  764. We therefore conclude that it follows from the principle of openness and of "utmost transparency" that when Parliament decides to make a given set of data or information available to the public, this must be done through non-discriminatory, transparent and up-to-date means of communication, and in open formats that support such further analyses, uses and releases.
    765. 

  765. 

  766. We find that lock-in and vendor dependence are difficult to reconcile with the principle of openness and of "utmost transparency" to which Parliament has committed itself. In our view, Parliament should not take lowest costs as an absolute metric in its strategic choices of IT systems. Rather, technologies that allow others to work with Parliament's own systems and data should be privileged, even if they were to incur some extra costs.
    767. 

  767. 

  768. This view is fully in line with new EU rules on public procurement that allow for the taking into account of environmental and social considerations and innovation in the awarding of public contracts. In our view, promoting Free Software and Open Standards through proportionate and calibrated specifications also serves the general economic interest of the EU, in the true sense of the term.
    769. 

  769. 

  770. Finally, we have shown that other public bodies in certain Member States provide measurable benchmarks for the adoption of Free Software and Open Standards. We believe that the European Parliament should follow those leads, and exceed them.
    771. 

  771. 

  772. We conclude that the Rules of Procedure of the European Parliament should whenever possible make Free Software and Open Standards mandatory for all systems and data used for the work of Parliament. In our view, that is the most appropriate way for the Parliament to meet its own standard of "utmost transparency".
    773. 

  773. 

  774. = Notes =
    775. 

  775. 

  776. &lt;references />
    777. 

  777. </textarea><div class="templatesUsed"><div class="mw-templatesUsedExplanation"><p>Templates used on this page:
    778. 

  778. </p></div><ul>
    779. 

  779. <li><a href="/Template:Cite_book" title="Template:Cite book">Template:Cite book</a> (<a href="/w/index.php?title=Template:Cite_book&amp;action=edit" title="Template:Cite book">view source</a>) </li><li><a href="/Template:Cite_journal" title="Template:Cite journal">Template:Cite journal</a> (<a href="/w/index.php?title=Template:Cite_journal&amp;action=edit" title="Template:Cite journal">view source</a>) </li><li><a href="/Template:Cite_news" title="Template:Cite news">Template:Cite news</a> (<a href="/w/index.php?title=Template:Cite_news&amp;action=edit" title="Template:Cite news">view source</a>) </li><li><a href="/Template:Cite_web" title="Template:Cite web">Template:Cite web</a> (<a href="/w/index.php?title=Template:Cite_web&amp;action=edit" title="Template:Cite web">view source</a>) </li><li><a href="/Module:Citation/CS1" title="Module:Citation/CS1">Module:Citation/CS1</a> (<a href="/w/index.php?title=Module:Citation/CS1&amp;action=edit" title="Module:Citation/CS1">view source</a>) </li><li><a href="/Module:Citation/CS1/Configuration" title="Module:Citation/CS1/Configuration">Module:Citation/CS1/Configuration</a> (<a href="/w/index.php?title=Module:Citation/CS1/Configuration&amp;action=edit" title="Module:Citation/CS1/Configuration">view source</a>) </li><li><a href="/Module:Citation/CS1/Date_validation" title="Module:Citation/CS1/Date validation">Module:Citation/CS1/Date validation</a> (<a href="/w/index.php?title=Module:Citation/CS1/Date_validation&amp;action=edit" title="Module:Citation/CS1/Date validation">view source</a>) </li><li><a href="/Module:Citation/CS1/Whitelist" title="Module:Citation/CS1/Whitelist">Module:Citation/CS1/Whitelist</a> (<a href="/w/index.php?title=Module:Citation/CS1/Whitelist&amp;action=edit" title="Module:Citation/CS1/Whitelist">view source</a>) </li></ul></div><p id="mw-returnto">Return to <a href="/EUT/2nd-edition" title="EUT/2nd-edition">EUT/2nd-edition</a>.</p>
    780. 

  780. </div><div class="printfooter">
    781. 

  781. Retrieved from "<a href="http://en.euwiki.org/EUT/2nd-edition">http://en.euwiki.org/EUT/2nd-edition</a>"</div>
    782. 

  782.         <div id='catlinks' class='catlinks catlinks-allhidden'></div>       <!-- end content -->
    783. 

  783.                 <div class="visualClear"></div>
    784. 

  784.     </div>
    785. 

  785. </div></div>
    786. 

  786. <div id="column-one">
    787. 

  787.     <h2>Navigation menu</h2>
    788. 

  788.     <div id="p-cactions" class="portlet" role="navigation">
    789. 

  789.         <h3>Views</h3>
    790. 

  790.         <div class="pBody">
    791. 

  791.             <ul>
    792. 

  792.                 <li id="ca-nstab-main" class="selected"><a href="/EUT/2nd-edition" title="View the content page [c]" accesskey="c">Page</a></li>
    793. 

  793.                 <li id="ca-talk" class="new"><a href="/w/index.php?title=Talk:EUT/2nd-edition&amp;action=edit&amp;redlink=1" title="Discussion about the content page [t]" accesskey="t">Discussion</a></li>
    794. 

  794.                 <li id="ca-viewsource" class="selected"><a href="/w/index.php?title=EUT/2nd-edition&amp;action=edit" title="This page is protected.&#10;You can view its source [e]" accesskey="e">View source</a></li>
    795. 

  795.                 <li id="ca-history"><a href="/w/index.php?title=EUT/2nd-edition&amp;action=history" rel="archives" title="Past revisions of this page [h]" accesskey="h">History</a></li>
    796. 

  796.             </ul>
    797. 

  797.         </div>
    798. 

  798.     </div>
    799. 

  799.     <div class="portlet" id="p-personal" role="navigation">
    800. 

  800.         <h3>Personal tools</h3>
    801. 

  801.         <div class="pBody">
    802. 

  802.             <ul>
    803. 

  803.                 <li id="pt-login"><a href="/w/index.php?title=Special:UserLogin&amp;returnto=EUT%2F2nd-edition&amp;returntoquery=action%3Dedit" title="You are encouraged to log in; however, it is not mandatory [o]" accesskey="o">Log in</a></li>
    804. 

  804.                 <li id="pt-createaccount"><a href="/Special:RequestAccount">Request account</a></li>
    805. 

  805.             </ul>
    806. 

  806.         </div>
    807. 

  807.     </div>
    808. 

  808.     <div class="portlet" id="p-logo" role="banner">
    809. 

  809. <a href="/Main_Page" style="background-image: url(http://commons.euwiki.org/images/logo.png);" title="Visit the main page"></a>
    810. 

  810.     </div>
    811. 

  811.     <div class="generated-sidebar portlet" id="p-navigation" role="navigation">
    812. 

  812.         <h3>Navigation</h3>
    813. 

  813.         <div class='pBody'>
    814. 

  814.             <ul>
    815. 

  815.                 <li id="n-mainpage-description"><a href="/Main_Page" title="Visit the main page [z]" accesskey="z">Main page</a></li>
    816. 

  816.                 <li id="n-recentchanges"><a href="/Special:RecentChanges" title="A list of recent changes in the wiki [r]" accesskey="r">Recent changes</a></li>
    817. 

  817.                 <li id="n-randompage"><a href="/Special:Random" title="Load a random page [x]" accesskey="x">Random page</a></li>
    818. 

  818.                 <li id="n-help"><a href="https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents" title="The place to find out">Help</a></li>
    819. 

  819.             </ul>
    820. 

  820.         </div>
    821. 

  821.     </div>
    822. 

  822.     <div id="p-search" class="portlet" role="search">
    823. 

  823.         <h3><label for="searchInput">Search</label></h3>
    824. 

  824.         <div id="searchBody" class="pBody">
    825. 

  825.             <form action="/w/index.php" id="searchform">
    826. 

  826.                 <input type='hidden' name="title" value="Special:Search"/>
    827. 

  827.                 <input type="search" name="search" placeholder="Search" title="Search EU-wiki [f]" accesskey="f" id="searchInput" />
    828. 

  828.                 <input type="submit" name="go" value="Go" title="Go to a page with this exact name if exists" id="searchGoButton" class="searchButton" />&#160;
    829. 

  829.                 <input type="submit" name="fulltext" value="Search" title="Search the pages for this text" id="mw-searchButton" class="searchButton" />
    830. 

  830.             </form>
    831. 

  831. 

  832.                     </div>
    833. 

  833.     </div>
    834. 

  834.     <div class="portlet" id="p-tb" role="navigation">
    835. 

  835.         <h3>Tools</h3>
    836. 

  836.         <div class="pBody">
    837. 

  837.             <ul>
    838. 

  838.                 <li id="t-whatlinkshere"><a href="/Special:WhatLinksHere/EUT/2nd-edition" title="A list of all wiki pages that link here [j]" accesskey="j">What links here</a></li>
    839. 

  839.                 <li id="t-recentchangeslinked"><a href="/Special:RecentChangesLinked/EUT/2nd-edition" title="Recent changes in pages linked from this page [k]" accesskey="k">Related changes</a></li>
    840. 

  840.                 <li id="t-upload"><a href="http://commons.euwiki.org/Special:Upload" title="Upload files [u]" accesskey="u">Upload file</a></li>
    841. 

  841.                 <li id="t-specialpages"><a href="/Special:SpecialPages" title="A list of all special pages [q]" accesskey="q">Special pages</a></li>
    842. 

  842.                 <li id="t-info"><a href="/w/index.php?title=EUT/2nd-edition&amp;action=info">Page information</a></li>
    843. 

  843.             </ul>
    844. 

  844.         </div>
    845. 

  845.     </div>
    846. 

  846. </div><!-- end of the left (by default at least) column -->
    847. 

  847. <div class="visualClear"></div>
    848. 

  848. <div id="footer" role="contentinfo">
    849. 

  849.     <div id="f-poweredbyico">
    850. 

  850.         <a href="//www.mediawiki.org/"><img src="/w/skins/common/images/poweredby_mediawiki_88x31.png" alt="Powered by MediaWiki" width="88" height="31" /></a>
    851. 

  851.     </div>
    852. 

  852.     <ul id="f-list">
    853. 

  853.         <li id="privacy"><a href="/EU-wiki:Privacy_policy" title="EU-wiki:Privacy policy">Privacy policy</a></li>
    854. 

  854.         <li id="about"><a href="/EU-wiki:About" title="EU-wiki:About">About EU-wiki</a></li>
    855. 

  855.         <li id="disclaimer"><a href="/EU-wiki:General_disclaimer" title="EU-wiki:General disclaimer">Disclaimers</a></li>
    856. 

  856.     </ul>
    857. 

  857. </div>
    858. 

  858. </div>
    859. 

  859. <script>/*<![CDATA[*/window.jQuery && jQuery.ready();/*]]>*/</script><script>if(window.mw){
    860. 

  860. mw.loader.state({"site":"ready","user":"ready","user.groups":"ready"});
    861. 

  861. }</script>
    862. 

  862. <script>if(window.mw){
    863. 

  863. mw.loader.load(["mediawiki.action.edit.collapsibleFooter","mediawiki.user","mediawiki.hidpi","mediawiki.page.ready","mediawiki.searchSuggest"],null,true);
    864. 

  864. }</script>
    865. 

  865. <script>if(window.mw){
    866. 

  866. mw.config.set({"wgBackendResponseTime":284});
    867. 

  867. }</script></body></html>
    868.
generated by cgit v1.2.3 (git 2.46.0) at 2024-11-25 09:01:18 +0000