Entation to Be Used by Developers and Webmasters

Total Page:16

File Type:pdf, Size:1020Kb

Entation to Be Used by Developers and Webmasters Programming with SPIP DOCUMENTATION TO BE USED BY DEVELOPERS AND WEBMASTERS SPIP’s version 2.1.0+ / May 2010 SPIP’s version 2.1.0+ / May 2010 SPIP is both a publication system and a development platform. After a quick tour of SPIP’s features, we will describe how it works and explain how to develop with it using helpful examples wherever possible. This documentation targets webmasters with knowledge of PHP, SQL, HTML, CSS and JavaScript. Contents Preface..................................................................................... 7 Notes about this documentation............................................... 9 Introduction ............................................................................ 11 The templates ........................................................................ 15 Contents of the directories ..................................................... 87 Extending SPIP .................................................................... 101 Functionalities ...................................................................... 195 Forms ................................................................................... 227 SQL access.......................................................................... 251 Creating your own plugins.................................................... 301 Examples ............................................................................. 313 Glossary ............................................................................... 319 Index .................................................................................... 323 Table of contents.................................................................. 333 Preface The beginnings of this book date back to late 2008. Matthieu was starting his work on this documentation for developers, and said to us : “... whatever we do, let’s do it with an open licence so that other people will be able to take over after I’ve done my part and then take it even further ... perhaps one day it could even be published in hard copy”. A SPIP book with an open licence : a dream nurtured for years was now showing its first signs of taking solid form. The idea had become firmly sounded out and recent new technologies were available to help make it a reality. Anyone who wants to print a book can now find all kinds of simple tools on the internet to help with the task. It’s great to think that at a modest cost you can order a one-off copy of any text. And the feeling when you first receive the printed copy — can you imagine ? The first version of this book is coming out in the magical atmosphere of the Troglos meeting, and that is a positive sign. Version 1.0 of the book can be seen as the end of one adventure, but it is also the beginning of another. All the technical elements required are now in place for other books. They only need to be written — on a SPIP site, of course ! Add a cover, and send it all to the printer. SPIP SPIP HOORAY ! Ben. Notes about this documentation License and rights The fruits of long hours of writing, this documentation is a combination of knowledge from the SPIP community. All of this work is distributed under the open Creative Commons license - Attribution - Share Alike (cc-by-sa). You may use these texts for any purpose whatsoever (including commercial), modify them and redistribute them on the condition that you allow your readers the same rights to share. Continuous improvements This work - still in progress - has been subject to numerous proofreadings but is certainly not guaranteed exempt from any error. Please don’t hesitate to offer improvements or point out mistakes by using the suggestion form available on the documentation internet site (http://programmer.spip.org). You may also discuss the organisation (of the content or technical presentation) and the translations by using the discussion list "spip-programmer" (requires subscription). Write a chapter If you feel motivated by this project, you may offer to write a chapter about a subject that you have mastered, or rework an existing chapter to make it clearer or more complete. We will do our best to accommodate your efforts and support you in such activities. Translations You may also participate in the translation of this documentation into English or Spanish. The site’s private zone (http://programmer.spip.org) is used for discussing the translations that are currently being prepared. Having said that, it’s not expected to translate the documentation into other languages until such time as the organisation of the various chapters has been stabilised, which might yet take several months. Computer code and properties of languages With the aim of retaining compatibility, the computer code segments which serve as examples only contain ASCII characters. This means, among other things, that you will not find any language diacritic marks in the comments that accompany the examples anywhere in the documentation, a matter normally of considerable importance in French, and almost none in English. Therefore, we ask that you expect such absences to occur and ignore them. Happy reading! Introduction An introduction to SPIP and a presentation of its general principles 11 What is SPIP? SPIP 2.0 is a free software package distributed under the GNU/GPL3 licence. Originally a Content Management System, it has gradually become a development platform making it possible to create maintainable and extensible interfaces independently of the structure of the managed data. What can SPIP be used for? SPIP is particularly suitable for websites and portals with regular community contributions, but it can also be used for a blog, a wiki, or a social network. More generally, SPIP can manage the storage and presentation of any data stored in MySQL, Postgres or SQLite databases. Extensions are available which also offer interaction with XML. Requirements and basic description SPIP 2.1 requires PHP version 5.0 or higher and at least 10MB of memory. It also requires a database (MySQL, Postgres or SQLite are supported). The public website (front-office) is visible to all visitors by default, but it can be restricted to certain users, by section, if required. The private interface (back- office) is accessible only to persons authorised to manage the software or site content. The templates The whole website and its private area are calculated from templates that are composed of static code (mainly HTML) and SPIP elements. These templates are, by default, stored in the directories squelettes-dist and prive. For example, when a visitor makes a request for the home page, SPIP creates an HTML page based on the template named sommaire.html. Each type of object in SPIP has a default template to display it, such as article.html for articles and rubrique.html for sections (or "rubriques" in French) 12 # Introduction SPIP transforms these templates into PHP code which it stores in a cache. These cached files are then used to produce the HTML pages — which are cached in their turn — and then returned to each visitor. Quick overview SPIP transforms templates into static pages. Templates are mainly composed of loops (<BOUCLE>) which select elements, typically sets of records, and tags (#TAG) which display the properties and values of those elements, typically fields from the records or system-wide functions and preconfigured values. List of 5 most recently published articles: <B_art> <ul> <BOUCLE_art(ARTICLES){!par date}{0,5}> <li><a href="#URL_ARTICLE">#TITRE</a></li> </BOUCLE_art> </ul> </B_art> In this example, this <BOUCLE_art()> loop performs a selection from the ARTICLES table in the database. It sorts the data in reverse chronological order and returns the first five elements. For each article that the loop selects, the #URL_ARTICLE tag is replaced with the URL for its page, and the #TITRE tag is replaced with its title. Typical HTML resulting from this kind of loop: <ul> <li><a href="Recursion">Recursion</a></li> <li><a href="Parameter">Parameter</a></li> <li><a href="Argument">Argument</a></li> <li><a href="Modifying-all-of-your-templates- in">Modifying all of your templates in one hit</a></li> <li><a href="Display-an-authoring-form-if">Display an authoring form, if authorised</a></li> </ul> 13 The templates SPIP generates HTML pages from templates, containing a mixture of HTML, loops and criteria, tags and filters. Its strength is the ability to extract database content using a simple and understandable language. 15 Loops A loop displays some content stored in database. It generates an optimized SQL query that extracts the desired content. The syntax of loops A loop specifies both a database table from which to extract information as well the criteria for selection. <BOUCLE_nom(TABLE){criterion1}{criterion2}> ... for each object ... </BOUCLE_nom> Every loop has a name (which must be unique within the template file), this name is used together with the word “BOUCLE” (English: "loop") to mark the start and the end of the loop. Here, the name is “_nom”. The table is specified either by an alias (written in capital letters) or by the real name of the table (written in upper and lowercase letters as the case may be), for example “spip_articles”. The example uses the “TABLE” alias. The next components of a loop are the criteria, which are written between braces. For example, the criterion {par nom} will sort the results according to the “nom” column of the database table. Example This loop lists all the images on the site. It draws its data from the database using the DOCUMENTS
Recommended publications
  • Entation to Be Used by Developers and Webmasters
    Programming with SPIP DOCUMENTATION TO BE USED BY DEVELOPERS AND WEBMASTERS SPIP’s version 2.1.0+ / August 2010 SPIP’s version 2.1.0+ / August 2010 SPIP is both a publication system and a development platform. After a quick tour of SPIP’s features, we will describe how it works and explain how to develop with it using helpful examples wherever possible. This documentation targets webmasters with knowledge of PHP, SQL, HTML, CSS and JavaScript. Contents Preface..................................................................................... 7 Notes about this documentation............................................... 9 Introduction ............................................................................ 11 The templates ........................................................................ 15 Contents of the directories ..................................................... 87 Extending SPIP .................................................................... 101 Functionalities ...................................................................... 197 Forms ................................................................................... 229 SQL access.......................................................................... 253 Creating your own plugins.................................................... 303 Examples ............................................................................. 315 Glossary ............................................................................... 321 Index ...................................................................................
    [Show full text]
  • Values and Configuration of Users in the Design of Software Source Code
    International Journal of Communication 11(2017), 1112–1132 1932–8036/20170005 Values and Configuration of Users in the Design of Software Source Code STÉPHANE COUTURE1 Glendon College, York University, Canada Based on an empirical study of two free and open source software projects, this article focuses on how choices of design within software source code are articulated with values and may favor certain categories of actors over others. After introducing the aim and approach of the study and presenting the studied projects, the article analyzes two controversies that show the articulation of values, configuration of users, and source code design. In conclusion, I argue for the importance for communication and media studies to study the use of source code and how its design may reflect values or may facilitate or constrain the agencies of certain categories of people. Keywords: software source code, free and open source software, digital technologies, configuration of users, values, science and technology studies When I am a graphic designer, my interface is Photoshop, with its buttons, its windows, etc. When I am developer, my interface is code. It is through code that I interact with what I am building, a program. (Interview sf03, July 2009) This quote from an interview I conducted in the course of this study grasps a fundamental argument I want to bring forward in this article: that software source code should be analyzed as an interface with which actors interact to build or modify software. Although metaphors of code are regularly mobilized in communication studies, few studies seem to have been done to closely and empirically investigate what source code exactly is and how its design may reflect values or may facilitate or restrain the capacity of some people to participate in the making of digital technologies.
    [Show full text]
  • Documentation SPIP
    SPIP WEBMESTRES Table des matières Où placer les fichiers de squelettes ? .................................................................................................... 5 Les squelettes par défaut : dist/ ................................................................................................... 5 Votre dossier squelettes/ .............................................................................................................. 5 Utiliser un autre dossier de squelettes ......................................................................................... 6 Priorité des dossiers de squelettes ............................................................................................... 6 Et les fichiers .php3 (ou .php) dans tout ça ? .............................................................................. 7 Principe général .................................................................................................................................... 8 Pour chaque type de page, un squelette ...................................................................................... 8 Lorsque SPIP appelle un squelette, il lui passe un contexte ....................................................... 9 Le principe de fonctionnement du cache, de manière simplifiée .............................................. 10 Le fichier .html .......................................................................................................................... 11 Une interface différente dans le même site ..............................................................................
    [Show full text]
  • Programas Incluidos En El DVD DVD-Programación 2013-10
    O 0 c 1 t - u 3 DVD-Programación 2013-10 b 1 r 0 e 2 Programas incluidos en el DVD d n e ó i (continuación) Eclipse PDT Helios SR2 - Elgg 1.8.16 - Erlang R16B02 - Etherpad Lite 1.2.11 - Euphoria 2 c 3.1.1 - eZ Publish Community 2013.07 - Feng Office 2.3.2.1 - FileZilla Server 0.9.41 - Firebird 2.5.2.26540 - 0 a 1 3 m Firebug 1.12.3 - FlameRobin 0.9.3 2013.10.03 - Free Pascal 2.6.2 - FreeBasic 0.90.1 - FreeDOS 1.1 Full CD a r - Gazpacho 0.7.2 - Geany 1.23 - gedit 2.30.1 - Git 1.8.4 - Glade 3.14.0 - GNAT Programming Studio 2013 - g GnuWin32 Indent 2.2.10 - GTK+ 2.14.7 - Guido van Robot 4.4 - gVim 7.4 - HM NIS Edit 2.0.3 - IE Tab 2.0 o r 2012.03.12 - Inno Setup 5.5.2 - Inno Setup Tool 5.3.0.1 - InstallJammer 1.2.15 - Instant Rails 2.0 - IzPack P - 4.3.5 - Java Runtime Environment 7 update 40 - jEdit 5.1.0 - Jelix Developer Edition 1.5.3 - Joomla! 2.5.11 - D Joomla! 3.1.5 - Komodo Edit 8.5.1 - Kompozer 0.8.b3 - Lazarus 1.0.12 - lightTPD 1.4.32.1 - LinkChecker 8.2 V D - MantisBT 1.2.15 - MariaDB 5.5.30 - MediaWiki 1.21.2 - Mercurial 2.7.2 - Minimum Profit 5.2.6 - MongoDB 2.4.6 - Mono 3.2.3 - monotone 1.0 - Moodle 2.5.2 - MS Windows Installer 4.5 - MySql 5.6.14 - MySQL WorkBench OSS 6.0.7 - NetBeans Java EE IDE 7.3.1 - nginx 1.5.6 - Notepad++ 6.5 - NSIS 2.46 - NumPy 1.7.1 (py 2.7) - NumPy 1.7.1 (py 3.3) - Open Watcom Fortran 1.9 - OpenLaszlo 4.9.0 - Parrot 5.7.0 - PECL 5.2.6 - pgAdmin3 1.18.0 - PHP 5.4.20 VC9 - PHP 5.5.4 VC11 - PHP-Fusion 7.02.07 - phpMyAdmin 4.0.8 - phpMyBackupPro 2.1 Castellano - phpMyBackupPro 2.4 - PIL 1.1.7 (py 2.7) -
    [Show full text]
  • Formation-P1-Spip-Utilisation.Pdf
    SPIP - Fonctionnement et utilisation - Patrick VINCENT Partie 1 [email protected] Partie 1 Les sites Web Rappels techniques et généralités Le réseau Internet Un site Internet Ensemble de documents reliés par des liens hypertextes, accessibles entre eux via Internet fichiers HTML (présentation), XML (échange de données)... ressources multimédia : image, son, video... URL (Universal Ressource Location) : permets de faire référence de manière unique à un document nom du protocole utilisé pour accèder au document nom du serveur qui l©héberge chemin d©accès, sur la machine, à la ressource numéro du port réseau Ex : http://www.spip.net/fr/index.html:80 Des liens hypertextes Consultation d©une page Web 2 port 80 http://www.spip.net http://www.spip.net 1 http 4 port 80 3 serveur Web PC+ Navigateur Internet 1. Action de l©utilisateur dans le navigateur (clic lien) 2. Requête HTTP du navigateur avec adresse 3. Réponse HTTP du serveur avec document HTML 4. Interpr étation et affichage du navigateur Un serveur Web module serveur système de fichiers Ordinateur connecté en http racine permanence à Internet Apache et chargé de servir des documents Web écoute et réception d©une requête (protocole / port) PHP / Perl / interprétation et év calcul Python transfert du document au client Web (protocole / ... port) module de calcul base de données Un navigateur Internet 3 Modules client HTTP dans une architecture client/serveur moteur de rendu des Standards du Web : HTML et CSS interface utilisateur : browser, butineur, brouteur, explorateur... Types et répartition Internet Explorer : 46,2 % / Windows (IE7 : 26%, IE6 : 20,6%) Mozilla Firefox : 44 % / GPL / multiplateforme / Google Safari : 2,7 % / Apple / proriétaire LGPL / CSS3 Opera : 2,3 % / proriétaire / multiplateforme / portable / Adobe Langages interprétés XHTML, CSS, JavaScript nativement Flash, Java, ActiveX, Flex, Silverlight..
    [Show full text]
  • Installation De SPIP
    Etape 1 : Installation de SPIP Extrait du Mission TICE 38 http://www.ac-grenoble.fr/missiontice38/spip.php?article1225 Etape 1 : Installation de SPIP - Réseaux numériques - Système de publication Web - Squelette SPIP-Bee&Co. - Date de mise en ligne : dimanche 16 janvier 2011 Description : Téléchargement, installation et configuration du logiciel Mission TICE 38 Copyright © Mission TICE 38 Page 1/5 Etape 1 : Installation de SPIP Téléchargement de SPIP 2.1.xx (section archive) • Accueil : http://www.spip.net/fr_download • Archives : http://files.spip.org/spip/archives/ • Documentation : http://www.spip.net/fr_article402.html Attention ! Cette version de SPIP installe à la racine du site un dossier nommé "prive". Veiller à ne pas écraser un dossier de même nom déjà utilisé par le site. • En cas de mise à jour du site, consulter au préalable la rubrique Mise à jour pour SPIP et notamment l'astuce de l'étape 2 qui permet de réduire le temps d'indisponibilité du site. Création des dossiers et copie des fichiers sur le serveur d'hébergement 1. Extraire le dossier "spip" de l'archive spip-v2-1.xx.zip. 2. Par FTP, transférer le contenu du dossier "spip" sur le serveur. 3. A la racine du site, créer les dossiers complémentaires : • lib • plugins Autorisations d'accès aux dossiers de SPIP sur le serveur • Définir à 777 les attributs CHMOD des dossiers : Sur le serveur académique de Grenoble, ce ne devrait plus être nécessaire compte-tenu des nouveaux paramétrages de sécurité. Copyright © Mission TICE 38 Page 2/5 Etape 1 : Installation de SPIP - config - IMG (et tous les sous-dossiers) - lib - local (et tous les sous-dossiers) - tmp (et tous les sous-dossiers) Configuration de l'installation 1.
    [Show full text]
  • Sr 002 960 V1.0.1 (2012-12)
    ETSI SR 002 960 V1.0.1 (2012-12) Special Report Working in ETSI within an OSS context: Guidance and recommendations, including usage of OSS within ETSI Secretariat, adoption/usage of elements of OSS in the elaboration of ETSI Standards and adoption of ETSI Standards within the OSS communities 2 ETSI SR 002 960 V1.0.1 (2012-12) Reference DSR/BOARD-00013 Keywords open source, Open Source Software, OSS, software ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N° 348 623 562 00017 - NAF 742 C Association à but non lucratif enregistrée à la Sous-Préfecture de Grasse (06) N° 7803/88 Important notice Individual copies of the present document can be downloaded from: http://www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http://portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http://portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by written permission.
    [Show full text]
  • Project Progress Report
    DIGIT Unit B1 FOSSA WP3 - Deliverable n. 2 Proposition of tools to perform periodic inter- institutional inventories of software assets and standards Date: 07/03/2016 Doc. Version: Final FOSSA WP3 Deliverable 2 TABLE OF CONTENTS TABLE OF FIGURES ...................................................................................................... 3 TABLE OF TABLES ........................................................................................................ 3 1. DELIVERABLE OVERVIEW ........................................................................................ 4 2. OSS PILOT INVENTORY SCENARIOS ......................................................................... 5 2.1. Pilot Scenario - Main features and constraints............................................................ 5 2.2. Target Scenario – main features .................................................................................. 6 3. GENERAL INVENTORY PROCESS ARCHITECTURE (PILOT SCENARIO) .......................... 7 3.1. Solution architecture ................................................................................................... 7 3.2. Data management patterns ......................................................................................... 8 4. OPEN SOURCE INVENTORY APPROACHES IN THE PILOT SCENARIO ........................ 14 4.1. Step 1 - Software component inventory.................................................................... 14 4.2. Step 1 - Standards inventory .....................................................................................
    [Show full text]
  • In Contributor's Guide
    LilyPond The music typesetter Contributor’s Guide The LilyPond development team ☛ ✟ This manual documents contributing to LilyPond version 2.21.82. It discusses technical issues and policies that contributors should follow. This manual is not intended to be read sequentially; new contributors should only read the sections which are relevant to them. For more information about different jobs, see Section “Help us” in Contributor’s Guide. ✡ ✠ ☛ ✟ For more information about how this manual fits with the other documentation, or to read this manual in other formats, see Section “Manuals” in General Information. If you are missing any manuals, the complete documentation can be found at http://lilypond.org/. ✡ ✠ Copyright ⃝c 2007–2020 by the authors. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with no Invariant Sections. A copy of the license is included in the section entitled “GNU Free Documentation License”. For LilyPond version 2.21.82 i Table of Contents 1 Introduction to contributing .................................. 1 1.1 Help us ................................................... ......................... 1 1.2 Overview of work flow ................................................... .......... 2 1.3 Summary for experienced developers ............................................... 2 1.4 Mentors ................................................... ........................ 3 2 Quick start..................................................
    [Show full text]
  • Gérer Un SPIP Mutualisé Avec SSH Et SVN
    Gérer un SPIP mutualisé avec SSH et SVN Extrait du Geekographie Maïeulesque http://geekographie.maieul.net/Gerer-un-SPIP-mutualise-avec-SSH Gérer un SPIP mutualisé avec SSH et SVN - SPIP - Date de mise en ligne : dimanche 5 décembre 2010 Geekographie Maïeulesque Copyright © Geekographie Maïeulesque Page 1/9 Gérer un SPIP mutualisé avec SSH et SVN Pourquoi installer trois fois SPIP lorsqu'on a trois sites chez le même hébergeur ? Pourquoi ne pas garder un seul noyau qui servirait aux trois sites ? Voici un petit tutorial sur : utiliser ssh et svn chez un hébergeur mutualiser un site SPIP. Ce tutoriel explique comment j'ai pratiqué chez l'Autre.net pour avoir un site mutualisé. Définition SSH est un protocole qui permet d'exécuter des lignes de commandes sur un ordinateur distant, via internet, et ce de manière sécurisé. SVN est un système de gestion de versions de code sources. C'est celui utilisé par SPIP. Un SPIP mutualisé, c'est la possibilité d'avoir une seul fois le code de SPIP pour plusieurs sites chez le même hébergeur. Ce qu'on cherche à faire Avoir un SPIP mutualisé. Pouvoir facilement le mettre à jour. Interêt La mutualisation permet un gain de place et de temps lors des mises à jour de SPIP : un seul SPIP à mettre à jour. L'accès SSH évite d'avoir à passer par FTP depuis votre ordinateur, et donc de subir la lenteur des connexions sortantes proposés en ADSL. Préalable Il est nécéssaire de pouvoir faire du SSH. Sur mac / linux, il faut utiliser le terminal ou l'invite de commande.
    [Show full text]
  • SPIP ­ Développement De Squelettes ­
    SPIP - développement de squelettes - Patrick VINCENT Partie 3 [email protected] Partie 1 Fonctionnement du noyau Organisation des données Les objets principaux de la BDD Manipulés par les utilisateurs : les articles les brèves les images et les documents joints les rubriques les mots clefs les sites syndiqués les auteurs les messages internes / de calendrier les forums et les pétitions Les autres objets Les objets créés automatiquement par le système : L©indexation du contenu (moteur de recherche) Les statistiques de visite Les méta-données : La version du système Les options fonctionnelles : forums, révisions, l©orthographe, prévisualisation, ect Reconnaître un objet L©identifier parmi la liste des objets. Noter son numéro d©identifiant unique : Visible dans l©URL du site public ou privé : Visible dans le Backoffice : Connaître l©interaction entre les objets de SPIP Liens entre les objets SPIP messages sites 1 1 auteurs rubriques articles N brèves N N images et N N N forums documents mots-clefs appartient à Extrait de la Base de Données table : spip_rubriques table : spip_articles table : spip_auteurs table : spip_auteurs_articles (pivot) Du point de vue fonctionnel les rubriques déterminent l©organisation du contenu du site (structure logique) les articles, brèves, sites, forums, documents représentent ce contenu les squelettes déterminent la mise en forme du contenu sur le site public les mots-clefs peuvent servir à la fois à organiser le contenu de manière transversale et à moduler la mise en forme (si intégrés dans les squelettes) les auteurs structurent la chaîne rédactionnelle Calcul des pages et modèles d©affichage Deux principes pour l©affichage La mise en page du site est effectuée au moyen de pages HTML nommées squelettes, contenant des instructions simplifiées permettant d'indiquer où et comment se placent les informations tirées de la base de données dans la page.
    [Show full text]
  • Collective Intelligence Framework
    Collective intelligence framework Decentralised Citizens ENgagement Technologies FP7 – CAPS - 2013 D-CENT D2.1 Collective intelligence framework Contents 1 Introduction ................................................................................................................................................................ 5 2 Contexts and crossroads for network movements today .............................................................................. 7 2.1 Social, economic, and political crises ............................................................................................................ 7 2.2 Network movements: some common characteristics .............................................................................. 9 2.3 Prototypes of network democracy ............................................................................................................. 12 2.4 Network movements and the internet: a sociotechnical tale ............................................................... 14 2.5 The architectures of the internet in dispute: the tendency towards fragmentation and centralization ............................................................................................................................................................... 17 2.5.1 Interoperability and portability vs fragmentation and centralization ........................................... 19 2.6 The post-Snowden scenario: massive vigilance and data control policies .......................................... 20 3 Theoretical and methodological
    [Show full text]