2. Country-Specific Extensions

While the standard is structured to be meaningful on an international level, there are additional information that can be added that makes sense in specific countries, such as declaring compliance with local laws or regulations. The provided extension mechanism is the usage of country-specific sections.

All country-specific extensions are contained in a section named with the two-letter lowercase ISO 3166-1 alpha-2 country code. For instance spid is a property for Italian software declaring whether the software is integrated with the Italian Public Identification System.

If a software is compliant I will find:

it:
  countryExtensionVersion: "0.2"
  piattaforme:
   - spid: yes

Notice that country-specific extensions within international sections are not allowed. Countries that want to extend the format should add a country-specific section instead.

2.1. Italy

All the extensions listed below are specific for Italy and, as such, they must be inserted in a section named with the it code. Every Country is specified using a two letters country code following the ISO 3166-1 alpha-2 standard.

2.1.1. Key countryExtensionVersion

  • Type: string

  • Presence: mandatory

  • Example: "1.0"

This key specifies the version to which the current extension schema adheres to, for forward compatibility.

Please note how the value of this key is independent from the top-level publiccodeYmlVersion one (see The Standard (core)). In such a way, the extensions schema versioning is independent both from the core version of the schema and from every other Country.

2.1.2. Key conforme

This section contains the keys for auto-declaring the compliance with the current legislation, with respect to the following sections. Not including these keys implies that the compliance is not known or not declared.

2.1.2.1. Key conforme/lineeGuidaDesign

  • Type: boolean

  • Presence: optional

If present and set to yes, the software is compliant with the Italian accessibility laws (L. 4/2004), as further explained in the linee guida di design (Italian language).

2.1.2.2. Key conforme/modelloInteroperatibilita

  • Type: boolean

  • Presence: optional

If present and set to yes, the software is compliant with the linee guida sull’interoperabilità.

Regulatory reference: Art. 73 del CAD (Italian language).

2.1.2.3. Key conforme/misureMinimeSicurezza

  • Type: boolean

  • Presence: optional

If present and set to yes, the software is compliant with the Misure minime di sicurezza ICT per le Pubbliche amministrazioni (Italian language).

2.1.2.4. Key conforme/gdpr

  • Type: boolean

  • Presence: optional

If present and set to yes, the software respects the GDPR.

2.1.3. Section piattaforme

2.1.3.1. Key piattaforme/spid

  • Type: boolean

  • Presence: optional

If present and set to yes, the software interfaces with SPID - il Sistema Pubblico di Identità Digitale.

2.1.3.2. Key piattaforme/cie

  • Type: boolean

  • Presence: optional

If present and set to yes, the software interfaces with the Italian electronic ID card (Carta di Identità Elettronica).

2.1.3.3. Key piattaforme/anpr

  • Type: boolean

  • Presence: optional

If present and set to yes, the software interfaces with ANPR.

2.1.3.4. Key piattafome/pagopa

  • Type: boolean

  • Presence: optional

If present and set to yes, the software interfaces with pagoPA.

2.1.4. Section riuso

This section contains a set of keys related to the publication of the software inside the reuse catalog of Developers Italia.

2.1.4.1. Chiave riuso/codiceIPA

  • Type: string (iPA code)

  • Presence: mandatory if repoOwner is a Public Administration

  • Example: c_h501

This key represents the administration code inside the Public Administration index (codice IPA).