# L_2017190EN.01001601.xml

| 21.7.2017 | EN | Official Journal of the European Union | L 190/16 |
| --- | --- | --- | --- |

21.7.2017

EN

Official Journal of the European Union

L 190/16

---

COMMISSION IMPLEMENTING DECISION (EU) 2017/1358

of 20 July 2017

on the identification of ICT Technical Specifications for referencing in public procurement

(Text with EEA relevance)

THE EUROPEAN COMMISSION,

Having regard to the Treaty on the Functioning of the European Union,

Having regard to Regulation (EU) No 1025/2012 of the European Parliament and of the Council of 25 October 2012 on European standardisation, amending Council Directives 89/686/EEC and 93/15/EEC and Directives 94/9/EC, 94/25/EC, 95/16/EC, 97/23/EC, 98/34/EC, 2004/22/EC, 2007/23/EC, 2009/23/EC and 2009/105/EC of the European Parliament and of the Council and repealing Council Decision 87/95/EEC and Decision No 1673/2006/EC of the European Parliament and of the Council (1) and in particular Article 13(1) thereof,

After consulting the European multi-stakeholder platform on ICT standardisation and sectoral experts

Whereas:

| (1) | Standardisation plays an important role in supporting the Europe 2020 strategy, as set out in the Communication from the Commission entitled ‘Europe 2020: A strategy for smart, sustainable and inclusive growth’. Several flagship initiatives of the Europe 2020 strategy underlined the importance of voluntary standardisation in product or services markets to assure the compatibility and interoperability between products and services, foster technological development and support innovation. |
| --- | --- |

(1)

Standardisation plays an important role in supporting the Europe 2020 strategy, as set out in the Communication from the Commission entitled ‘Europe 2020: A strategy for smart, sustainable and inclusive growth’. Several flagship initiatives of the Europe 2020 strategy underlined the importance of voluntary standardisation in product or services markets to assure the compatibility and interoperability between products and services, foster technological development and support innovation.

| (2) | Standards are essential for European competitiveness and crucial for innovation and progress. Their relevance is highlighted by the Commission in the context of the recent initiatives for the completion of Single Market (2) and the Digital Single market (3) where the role of standardisation and interoperability in creating a European Digital Economy is reinforced with the adoption of the Communication on ICT Standardisation Priorities for the Digital Single Market (4) setting out a comprehensive strategic and political approach to standardisation for priority ICT Technologies that are critical to the completion of the Digital Single Market. |
| --- | --- |

(2)

Standards are essential for European competitiveness and crucial for innovation and progress. Their relevance is highlighted by the Commission in the context of the recent initiatives for the completion of Single Market (2) and the Digital Single market (3) where the role of standardisation and interoperability in creating a European Digital Economy is reinforced with the adoption of the Communication on ICT Standardisation Priorities for the Digital Single Market (4) setting out a comprehensive strategic and political approach to standardisation for priority ICT Technologies that are critical to the completion of the Digital Single Market.

| (3) | In the digital society standardisation deliverables become indispensable to ensure interoperability of networks and systems. The Communication from the Commission entitled ‘A strategic vision for European standards: moving forward to enhance and accelerate the sustainable growth of the European economy by 2020’ (5) recognises the specificity of standardisation in the field of information and communication technologies (ICT), where solutions, applications and services are often developed by global ICT Fora and Consortia that have emerged as leading ICT standards development organisations. |
| --- | --- |

(3)

In the digital society standardisation deliverables become indispensable to ensure interoperability of networks and systems. The Communication from the Commission entitled ‘A strategic vision for European standards: moving forward to enhance and accelerate the sustainable growth of the European economy by 2020’ (5) recognises the specificity of standardisation in the field of information and communication technologies (ICT), where solutions, applications and services are often developed by global ICT Fora and Consortia that have emerged as leading ICT standards development organisations.

| (4) | Regulation (EU) No 1025/2012 aims at modernising and improving the European standardisation framework. It establishes a system whereby the Commission may decide to identify the most relevant and most widely accepted ICT technical specifications issued by organisations that are not European, international or national standardisation organisations. The possibility of using the full range of ICT technical specifications when procuring hardware, software and information technology services will enable interoperability between devices, services and applications, will help public administrations to avoid lock-in that occurs when the public procurer cannot change a provider after the expiration of the procurement contract because using ICT proprietary solutions, and will encourage competition in the supply of interoperable ICT solutions. |
| --- | --- |

(4)

Regulation (EU) No 1025/2012 aims at modernising and improving the European standardisation framework. It establishes a system whereby the Commission may decide to identify the most relevant and most widely accepted ICT technical specifications issued by organisations that are not European, international or national standardisation organisations. The possibility of using the full range of ICT technical specifications when procuring hardware, software and information technology services will enable interoperability between devices, services and applications, will help public administrations to avoid lock-in that occurs when the public procurer cannot change a provider after the expiration of the procurement contract because using ICT proprietary solutions, and will encourage competition in the supply of interoperable ICT solutions.

| (5) | For the ICT technical specifications to be eligible for referencing in public procurement they must comply with the requirements set out in Annex II to Regulation (EU) No 1025/2012. Compliance with those requirements guarantees the public authorities that the ICT technical specifications are established in accordance with the principles of transparency, openness, impartiality and consensus that are recognised by the World Trade Organisation in the field of standardisation. |
| --- | --- |

(5)

For the ICT technical specifications to be eligible for referencing in public procurement they must comply with the requirements set out in Annex II to Regulation (EU) No 1025/2012. Compliance with those requirements guarantees the public authorities that the ICT technical specifications are established in accordance with the principles of transparency, openness, impartiality and consensus that are recognised by the World Trade Organisation in the field of standardisation.

| (6) | The decision to identify the ICT specification is to be adopted after consultation of the European multi-stakeholder platform on ICT standardisation set up by Commission Decision 2011/C 349/04 (6) complemented by other forms of consultation of sectoral experts. |
| --- | --- |

(6)

The decision to identify the ICT specification is to be adopted after consultation of the European multi-stakeholder platform on ICT standardisation set up by Commission Decision 2011/C 349/04 (6) complemented by other forms of consultation of sectoral experts.

| (7) | The European multi-stakeholder platform on ICT standardisation evaluated and gave a positive advice to the identification of the following technical specifications for referencing in public procurement: ‘Simple Knowledge Organisation System’ (hereinafter referred as ‘SKOS’), and ‘Resource Description Framework’ 1.0 and 1.1 (hereinafter referred as ‘RDF 1.0 & 1.1’) developed by World Wide Web Consortium (W3C); ‘Service Metadata Publisher 1.0’ (hereinafter referred as ‘SMP 1.0’) developed by the Organization for the Advancement of Structured Information Standards (OASIS); ‘MIME-Based Secure Peer-to-Peer Business Data Interchange Using HTTP, Applicability Statement 2’, RFC 4130 (hereinafter referred as ‘AS2’) and ‘the Internationalized Resource Identifiers’ RFC 3987 (hereinafter referred as ‘IRIs’) developed by Internet Engineering Task Force (IETF); ‘Data Foundation & Terminology Model’, ‘PID Information Types API’, ‘Data Type Registries Model’ and ‘Practical Policies Recommendations’ technical specifications, all developed by Research Data Alliance (RDA) Foundation. The evaluation and advice of the platform was subsequently submitted to consultation of sectoral experts who confirmed the positive advice to its identification. |
| --- | --- |

(7)

The European multi-stakeholder platform on ICT standardisation evaluated and gave a positive advice to the identification of the following technical specifications for referencing in public procurement: ‘Simple Knowledge Organisation System’ (hereinafter referred as ‘SKOS’), and ‘Resource Description Framework’ 1.0 and 1.1 (hereinafter referred as ‘RDF 1.0 & 1.1’) developed by World Wide Web Consortium (W3C); ‘Service Metadata Publisher 1.0’ (hereinafter referred as ‘SMP 1.0’) developed by the Organization for the Advancement of Structured Information Standards (OASIS); ‘MIME-Based Secure Peer-to-Peer Business Data Interchange Using HTTP, Applicability Statement 2’, RFC 4130 (hereinafter referred as ‘AS2’) and ‘the Internationalized Resource Identifiers’ RFC 3987 (hereinafter referred as ‘IRIs’) developed by Internet Engineering Task Force (IETF); ‘Data Foundation & Terminology Model’, ‘PID Information Types API’, ‘Data Type Registries Model’ and ‘Practical Policies Recommendations’ technical specifications, all developed by Research Data Alliance (RDA) Foundation. The evaluation and advice of the platform was subsequently submitted to consultation of sectoral experts who confirmed the positive advice to its identification.

| (8) | ‘SKOS’ technical specification developed by W3C makes non-formal knowledge organisation systems available to the public online in a structured form, with the aim of organising and providing access to knowhow on the meaning and cohesion of the underlying terms. The ‘SKOS’ data model provides a standard, low-cost migration path for porting existing knowledge organization systems to the semantic web. ‘SKOS’ also provides a lightweight, intuitive language for developing and sharing new knowledge organization systems. It may be used on its own, or in combination with formal knowledge representation languages such as the Web Ontology language (OWL). |
| --- | --- |

(8)

‘SKOS’ technical specification developed by W3C makes non-formal knowledge organisation systems available to the public online in a structured form, with the aim of organising and providing access to knowhow on the meaning and cohesion of the underlying terms. The ‘SKOS’ data model provides a standard, low-cost migration path for porting existing knowledge organization systems to the semantic web. ‘SKOS’ also provides a lightweight, intuitive language for developing and sharing new knowledge organization systems. It may be used on its own, or in combination with formal knowledge representation languages such as the Web Ontology language (OWL).

| (9) | ‘RDF 1.0’ also developed by W3C is a standard model for data interchange on the Web with features that facilitate data merging even if the underlying schemas differ, and it specifically supports the evolution of schemas over time without requiring all the data consumers to be changed. ‘RDF 1.1’ is an evolution of ‘RDF 1.0’ with backward compatibility, using internationalized identifiers, fine-tuning of the use of datatypes and language tags on literals, and a number of new serialization formats. |
| --- | --- |

(9)

‘RDF 1.0’ also developed by W3C is a standard model for data interchange on the Web with features that facilitate data merging even if the underlying schemas differ, and it specifically supports the evolution of schemas over time without requiring all the data consumers to be changed. ‘RDF 1.1’ is an evolution of ‘RDF 1.0’ with backward compatibility, using internationalized identifiers, fine-tuning of the use of datatypes and language tags on literals, and a number of new serialization formats.

| (10) | ‘SMP 1.0’ technical specification developed by OASIS defines a protocol for publishing service metadata within a 4-corner network, where entities exchange business documents through intermediary gateway services (sometimes called Access Points). To successfully send a business document in a 4-corner network, an entity must be able to discover critical metadata about the recipient (endpoint) of the business document, such as types of documents the endpoint is capable of receiving and methods of transport supported. The recipient makes this metadata available to other entities in the network through a Service Metadata Publisher service. The specification describes the request/response exchanges between a Service Metadata Publisher and a client wishing to discover endpoint information |
| --- | --- |

(10)

‘SMP 1.0’ technical specification developed by OASIS defines a protocol for publishing service metadata within a 4-corner network, where entities exchange business documents through intermediary gateway services (sometimes called Access Points). To successfully send a business document in a 4-corner network, an entity must be able to discover critical metadata about the recipient (endpoint) of the business document, such as types of documents the endpoint is capable of receiving and methods of transport supported. The recipient makes this metadata available to other entities in the network through a Service Metadata Publisher service. The specification describes the request/response exchanges between a Service Metadata Publisher and a client wishing to discover endpoint information

| (11) | ‘AS2’ developed by IETF is one of the most popular methods for transporting structured business data securely and reliably over the Internet. It essentially involves two computers — a client and a server — connecting in a point-to-point manner via the web. AS2 creates an “envelope” for the structured business data, allowing them to be sent securely — using digital certificates and encryption — over the Internet. AS2 is used by private and public sector organizations and governments in several Member States for both specific use cases and general infrastructure implementations supporting secure transfer of messages and business documents'. |
| --- | --- |

(11)

‘AS2’ developed by IETF is one of the most popular methods for transporting structured business data securely and reliably over the Internet. It essentially involves two computers — a client and a server — connecting in a point-to-point manner via the web. AS2 creates an “envelope” for the structured business data, allowing them to be sent securely — using digital certificates and encryption — over the Internet. AS2 is used by private and public sector organizations and governments in several Member States for both specific use cases and general infrastructure implementations supporting secure transfer of messages and business documents'.

| (12) | ‘IRIs’ technical specification developed by IETF is a protocol element that extends upon the Uniform Resource Identifier (URI) scheme, which is based on the ASCII character set, by supporting a much wider set of characters that are used in EU Latin-based alphabets containing letters outside the ASCII set or use another script altogether (Greek, Bulgarian). |
| --- | --- |

(12)

‘IRIs’ technical specification developed by IETF is a protocol element that extends upon the Uniform Resource Identifier (URI) scheme, which is based on the ASCII character set, by supporting a much wider set of characters that are used in EU Latin-based alphabets containing letters outside the ASCII set or use another script altogether (Greek, Bulgarian).

| (13) | The Research Data Alliance (RDA) is an international organization focused on the development of infrastructure and community activities and recommendations designed to reduce barriers to data sharing and exchange and the acceleration of data driven innovation worldwide. Four technical specifications from RDA are identified. ‘RDA Data Foundation & Terminology Model’ is a core model, basic vocabulary and query tool of foundational terminology which ensures researchers use a common terminology when referring to data; ‘RDA PID Information Types API — Persistent Identifier Type Registry’ is a Conceptual model for structuring typed information to better identify PIDs, and a common interface for access to this information; ‘RDA Data Type Registries Model’ is a data type model and registry (‘MIME-types’ for data) to help tools interpret, display and process data; and ‘RDA Practical Policies recommendations’ is a set of machine actionable policies to enhance trust & interoperability. |
| --- | --- |

(13)

The Research Data Alliance (RDA) is an international organization focused on the development of infrastructure and community activities and recommendations designed to reduce barriers to data sharing and exchange and the acceleration of data driven innovation worldwide. Four technical specifications from RDA are identified. ‘RDA Data Foundation & Terminology Model’ is a core model, basic vocabulary and query tool of foundational terminology which ensures researchers use a common terminology when referring to data; ‘RDA PID Information Types API — Persistent Identifier Type Registry’ is a Conceptual model for structuring typed information to better identify PIDs, and a common interface for access to this information; ‘RDA Data Type Registries Model’ is a data type model and registry (‘MIME-types’ for data) to help tools interpret, display and process data; and ‘RDA Practical Policies recommendations’ is a set of machine actionable policies to enhance trust & interoperability.

HAS ADOPTED THIS DECISION:

Article 1

The technical specifications listed in the Annex are eligible for referencing in public procurement.

Article 2

This Decision shall enter into force on the twentieth day following that of its publication in the Official Journal of the European Union.

Done at Brussels, 20 July 2017.

For the Commission

The President

Jean-Claude JUNCKER

---

(1)  
  OJ L 316, 14.11.2012, p. 12.

1

(2)  Communication from the Commission ‘upgrading the single market: more opportunities for people and business’. COM (2015) 550 final of 28 October 2015.

2

(3)  Communication on a Digital Single Market Strategy for Europe. COM(2015) 192 final of 6 May 2015 and Communication on the Mid-Term Review on the implementation of the Digital Single Market Strategy COM(2017) 228 final of 10 May 2017.

3

(4)  COM (2016)176 final of 19 April 2016.

4

(5)  COM (2011) 311 final of 1 June 2011.

5

(6)  Commission Decision 2011/C 349/04 of 28 November 2011 setting up the European multi-stakeholder platform on ICT standardisation (OJ C 349, 30.11.2011, p. 4)

6

---

ANNEX

World Wide Web Consortium (W3C)
   (1)

| No | Title of ICT technical specification |
| --- | --- |
| 1 | Simple Knowledge Organisation System (SKOS) |
| 2 | Resource Description Framework 1.0 and 1.1 (RDF 1.0 & 1.1) |

No

Title of ICT technical specification

1

Simple Knowledge Organisation System (SKOS)

2

Resource Description Framework 1.0 and 1.1 (RDF 1.0 & 1.1)

OASIS (Advancing open standards for the information society)
   (2)

| No | Title of ICT technical specification |
| --- | --- |
| 1 | Service Metadata Publisher 1.0 (SMP 1.0) |

No

Title of ICT technical specification

1

Service Metadata Publisher 1.0 (SMP 1.0)

Internet Engineering Task Force (IETF)
   (3)

| No | Title of ICT technical specification |
| --- | --- |
| 1 | MIME-Based Secure Peer-to-Peer Business Data Interchange Using HTTP, Applicability Statement 2, RFC 4130 (AS2) |
| 2 | Internationalized Resource Identifiers, RFC 3987 (IRIs) |

No

Title of ICT technical specification

1

MIME-Based Secure Peer-to-Peer Business Data Interchange Using HTTP, Applicability Statement 2, RFC 4130 (AS2)

2

Internationalized Resource Identifiers, RFC 3987 (IRIs)

Research Data Alliance (RDA)
   (4)

| No | Title of ICT technical specification |
| --- | --- |
| 1 | TS1 Data Foundation & Terminology Model |
| 2 | TS2 PID Information Types API- Persistent Identifier Type Registry |
| 3 | TS3 Data Type Registries Model |
| 4 | TS4 Practical Policies recommendations |

No

Title of ICT technical specification

1

TS1 Data Foundation & Terminology Model

2

TS2 PID Information Types API- Persistent Identifier Type Registry

3

TS3 Data Type Registries Model

4

TS4 Practical Policies recommendations

---

(1)  http://www.w3.org/

(2)  http://www.oasis-open.org/

(3)  http://www.ietf.org/

(4)  https://rd-alliance.org/

---