fix: several typos, RST structure, new schema changes (#31)

fix: removed URI from iPA
fix: modified contacts, fixes #29 and #30
fix: changed example to face new contacts dependency
fix: moved ecosistemi out of riuso
fix: changed nested level it schema
feat: added example.rst in english
fix: port the english version to match the italian one
feat: new changes to schema description

Author: libremente

.gitignore

@@ -8,3 +8,6 @@ _site
 
 # Windows generic
 Thumbs.db
+
+# Swap files
+*.swp

docs/en/example.rst

@@ -0,0 +1,24 @@
+Esempi
+==========================
+
+Below there are two examples of `publiccode.yml` files, the first one
+represents the minimum configuration, which contains the mandatory fields,
+whilst the second one represents a more extended version. 
+
+Minimum Version
+~~~~~~~~~~~~~~~
+
+.. literalinclude:: example/publiccode.minimal.yml
+   :language: yaml
+   :linenos:
+
+
+Extended Version
+~~~~~~~~~~~~~~~
+
+.. literalinclude:: example/publiccode.yml
+   :language: yaml
+   :linenos:
+
+
+

docs/en/example/publiccode.yml

@@ -91,6 +91,7 @@ maintenance:
 
   contractors:
     - name: "Fornitore Privato SPA"
+      email: "dario.bianchi@fornitore.it"
       website: "https://privatecompany.com"
       until: "2019-01-01"
 
@@ -100,16 +101,6 @@ maintenance:
       affiliation: Comune di Reggio Emilia
       phone: +39 231 13215112
 
-    - name: Dario Bianchi
-      email: "dario.bianchi@fornitore.it"
-      affiliation: Fornitore Privato S.P.A.
-      phone: +39 16 24231322
-
-    - name: Giancarlo Verdi
-      email: "dario.bianchi@fornitore.it"
-      affiliation: Fornitore Privato S.P.A.
-      phone: +39 16 24231322
-
 localisation:
   localisationReady: yes
   availableLanguages:
@@ -157,4 +148,4 @@ it:
     seo: no
     ui: yes
     web: yes
-    content: no
+    content: no

docs/en/forks.rst

@@ -1,9 +1,12 @@
+.. _forks-and-variants:
+
 Forks and variants
 ==================
 
-This document describes how to best handle software forks in the context
-of updating ``publiccode.yml``. We define two different semantics that
-require different handling: technical forks and software variants.
+As already cited before, a fork may have two different forms based on the final
+aim. As such, in order to make it clear how to handle the
+`publiccode.yml` in both cases, below we define two different
+semantics: technical forks and software variants.
 
 Technical forks (i.e. to publish patches)
 -----------------------------------------

docs/en/index.rst

@@ -1,26 +1,14 @@
-``publiccode.yml``
-==================
-
-A PublicCode file written following this specification is guaranteed to
-remain compatible with all parsers implementing any 0.x release.
-
-For more information on version numbering see
-`SemVer.org <https://semver.org/>`__.
-
-Schema documentation
---------------------
-
--  `Schema <schema.md>`__
--  `Italian extension to the schema <schema.it.md>`__
--  `List of acceptable tags <tags.md>`__
-
-Concepts and lexicon
---------------------
-
--  `How to work with forks and variants <forks.md>`__
-
-Examples
---------
-
--  `Minimal Example <example/publiccode.minimal.yml>`__
--  `Full Example <example/publiccode.yml>`__
+The ``publiccode.yml`` Standard
+===============================
+.. toctree:: 
+   :maxdepth: 2
+   :numbered:
+
+   intro.rst
+   schema.md
+   schema.it.md
+   forks.md
+   pa-types.md
+   tags.md 
+   tools.md
+   example.rst

docs/en/pa-types.rst

@@ -1,3 +1,5 @@
+.. _pa-types:
+
 Public administration types
 ===========================