Assessment of the DNS with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of DNS EIF Scenario v3.0.0
Assessment of the WS-BPEL with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of WS-BPEL EIF Scenario v1.0.0
Assessment of the ETSI TS 119 432 with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of ETSI TS 119 432 EIF Scenario v1.0.0
Assessment of the SMTP with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of SMTP EIF Scenario v1.0.0
Assessment of the SAMM with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of SAMM EIF Scenario v1.0.0
Assessment of the AMQP with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of AMQP EIF Scenario v1.0.0
"According to the 5 star Open Data model suggested by Tim Berners-Lee about how to publish linked data, the first star corresponds to the publication of data on the web as open data. The EIF specification encourages Member States to make their open government data available on the web in any format. Therefore, the specification facilitates the publication of open data. EIF reference, 'EIF brochure' document: https://ec.europa.eu/isa2/eif_en Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/en/"
Assessment of the XHTML with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of XHTML EIF Scenario v2.0.0
Assessment of the Research Data Repository Interoperability Recommendations with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of Research Data Repository Interoperability Recommendations EIF Scenario v1.0.0
Assessment of the HTTP Cookies with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of HTTP Cookies EIF Scenario v1.0.0
"There exists an EIF community where any stakeholder has the opportunity to contribute to the development of the EIF. This contribution requires to create a Joinup (European Commission's EU Login) account. Besides, there are purpose-driven consultations held from time to time, and there is the possibility to provide feedback on the specification through public channels (e.g., webinars). EIF community reference: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/solution/eif-toolbox /eif-community EIF webinars reference: https://ec.europa.eu/isa2/consultations/open-public-consultation-revision-european-interoperabilityframework_ en"
Assessment of the Xforms with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of Xforms EIF Scenario v1.0.0
Assessment of the SVG with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of SVG EIF Scenario v1.0.0
"There is a reference study on the de facto implementation of the EIF components, where a section is dedicated to the effectiveness of the EIF components. Besides, there are assessments produced by arbitrary stakeholders (public representatives) from different Member States directly addressing the specification's effectiveness (see 'EIF evaluation and strategy' initiative); however, these assessments are not finely structured, and as a consequence the reader needs to consult different stakeholder inputs. EIF components evaluation, page 35: https://op.europa.eu/en/publication-detail/-/publication/29d694d4-4696-11ec-89db-01aa75ed71a1/languageen EIF evaluation and strategy, Feedback section: https://ec.europa.eu/info/law/better-regulation/have-your-say/initiatives/12579-European-Interoperability- Framework-EIF-evaluation-and-EU-governments-interoperability-strategy"
Assessment of the ETSI EN 319 422 with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of ETSI EN 319 422 EIF Scenario v1.0.0
Assessment of the ETSI TS 119 512 with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of ETSI TS 119 512 EIF Scenario v2.0.0
"The recommentation #5 of the EIF specification is to enable the exposure of European public services interfaces. Following this recommendation, in combination with the appropriate specifications, can enable the exposure of such interfaces. EIF reference, 'EIF brochure' document: https://ec.europa.eu/isa2/eif_en"
Assessment of the LegalDocML with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of LegalDocML EIF Scenario v1.0.0
Assessment of the CPOV with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Asssessment of CPOV EIF Scenario v2.0.0
Assessment of the NUTS with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of NUTS EIF Scenario v1.0.0
"The EIF specification (recommendation #15) promotes the secure exchange of data, and provides a set of security processes and management functions to this end by means of requirements and services (recommendations #46 and #47). EIF reference, 'EIF brochure' document: https://ec.europa.eu/isa2/eif_en"
Assessment of the DQV with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of DQV EIF Scenario 1.0.0
Assessment of the EuroVoc with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of EuroVoc EIF Scenario v2.0.0
Assessment of the LDAP with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of LDAP EIF Scenario v1.0.0
Assessment of the PAdES with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of PAdES EIF Scenario v1.0.0
'There is a wide community that provides public support to the EIF specification. The ISA2 Programme deals with the specification maintenance, and offers training opportunities and public support on interoperability aspects, particularly on the EIF recommendations. Moreover, there is also the National Interoperability Framework Observatory (NIFO) that is entirely dedicated to provide support to national public administrations. ISA2 reference: https://ec.europa.eu/isa2/actions/continuously-updating-european-interoperability-strategy_en NIFO reference: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/about'
Assessment of the ETSI TS 119 614-1 with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of ETSI TS 119 614-1 EIF Scenario v1.0.0
Assessment of the IPv6 with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of IPv6 EIF Scenario v2.0.0
Assessment of the OTel with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of OTel EIF Scenario v1.0.0
Assessment of the LDES with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of LDES EIF Scenario v1.0.0
"The EIF recommendation #9 advocates for ensuring data portability within European public services. Data has to be easily transferable between different systems and applications to avoid blocking, and support free movement of data. Therefore, the EIF specification addresses and enables data portability and includes specific provisions for it. EIF reference, 'EIF brochure' document: https://ec.europa.eu/isa2/eif_en"
'Open consultations are conducted preceding any major and minor release to ensure a coherent EU interoperability picture of the interactions between European public administrations, citizens and businesses; the last open consultation was held in 2016 for the EIF v3. In addition, there is a continuous public review as part of the release lifecycle of the EIF, consisting of opinion forums and surveys from different stakeholders (see EIF home page reference), as well as final reports assessing the specification suitability (see Inception Impact Assessment reference). EIF open consultation (2016) reference: https://ec.europa.eu/isa2/node/208 EIF home page, Presentation and Links sections: https://ec.europa.eu/isa2/eif_en Inception Impact Assessment reference: https://ec.europa.eu/isa2/consultations/open-public-consultation-revision-european-interoperability-framework_en'
Assessment of the UBL with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of UBL EIF Scenario v1.0.0
Assessment of the OAS3.1.0 with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of OAS EIF Scenario v1.0.0
Assessment of the TrainingDML-AI with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of TrainingDML-AI EIF Scenario v1.0.0
"The EIF specification addresses data protecion and is fully aligned with the EU Directives 2016/680 and 2007/2/EC, and the Regulation (EU) 910/2014 and 2016/679. EIF reference, 'EIF brochure' document: https://ec.europa.eu/isa2/eif_en"
Assessment of the WSS with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of WSS EIF Scenario v1.0.0
Assessment of the AKN4EU 4.0.0 with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of AKN4EU 4.0.0 EIF Scenario v1.0.0
Assessment of the XAdES with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of XAdES EIF Scenario v1.0.0
Assessment of the ELI with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of ELI EIF Scenario v2.0.0
Assessment of the SCIM with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of SCIM EIF Scenario v1.0.0
Assessment of the ETSI EN 303 645 with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of EN 303 645 EIF Scenario v1.0.0
Assessment of the Ogg with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of Ogg EIF Scenario v1.0.0
Assessment of the CSV with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of CSV EIF Scenario v2.0.0
Assessment of the IPSec with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of IPSec EIF Scenario v3.0.0
Assessment of the TLS with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of TLS MSP Scenario v1.0.0
CAMSS Assessment of TLS EIF Scenario v1.0.0
Assessment of the FTPS with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of FTPS EIF Scenario v1.0.0
Assessment of the ShEx with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of ShEx EIF Scenario v1.0.0
Assessment of the YAML with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of YAML EIF Scenario v1.0.0
Assessment of the genericode with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of genericode EIF Scenario v1.0.0
'The EIF specification has been developed and deployed by the European Commission; therefore, the specification is a European Standard. ISA2 Programme reference: https://ec.europa.eu/isa2/eif_en'
"The EIF recommendation #17 encourages the use and application of digital channels for the delivery of European public services. Besides, the specification widely promotes its coexistence with the physical ones. EIF reference, 'EIF brochure' document: https://ec.europa.eu/isa2/eif_en"
Assessment of the DCAT with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of DCAT EIF Scenario v1.0.0
Assessment of the EIRA 6.1.0 with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of EIRA 6.1.0 EIF Scenario v1.0.0
Assessment of the DCMI with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of DCMI EIF Scenario v1.0.0
Assessment of the HTML5 with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of HTML5 EIF Scenario v1.0.0
Assessment of the WAI-ARIA with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of WAI-ARIA EIF Scenario v2.0.0
Assessment of the XACML with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of XACML EIF Scenario v2.0.0
Assessment of the CPSV-AP with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of CPSV-AP EIF Scenario v2.0.0
Assessment of the JPEG with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of JPEG EIF Scenario v1.0.0
Assessment of the LegalRuleML with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of LegalRuleML EIF Scenario v1.0.0
'There is no Member State that includes the EIF in their national catalogue with The National Interoperability Framework (NIF) in alignment with the three categories 1. Conceptual model for integrated public services provision, 2. interoperability layers, and 3. interoperability principles. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards'
CAMSS Assessment of LDAP EIF Scenario v3.0.0
Assessment of the UDDI with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of UDDI EIF Scenario v2.0.0
Assessment of the NFVI with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of NFVI EIF Scenario v1.0.0
Assessment of the PDF with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of PDF EIF Scenario v1.0.0
Assessment of the Wheat Data Interoperability Guidelines with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of Wheat Data Interoperability Guidelines EIF Scenario v1.0.0
Assessment of the ISO 639-2 with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of ISO 639-2 EIF Scenario v1.0.0
"The EIF specification began in 2005 within the IDABC Programme. The specification has gone through two major releases: the second release appeared in 2009 (see Decision 2009/9227/EC) within the ISA Programme, and the third one in 2017 (see the new EIF reference) within the ISA2 Programme. Moreover, before the ISA2 Programme completion, the publication of documentation regarding implementation guides, Member States' administrations' opinions and other dissemination materials justifies the specification maturity for its use in the development of digital solutions and services. EIF first release, 'European Interoperability Framework for eGovernment Services' document: http://www.dlorg.eu/uploads/External%20Publications/ Decision 2009/922/EC Adopting the ISA Programme (EIF second release): https://eur-lex.europa.eu/eli/dec /2009/922 Decision 2009/9227/EC reference: https://eur-lex.europa.eu/eli/dec/2009/922 The new EIF reference: https://ec.europa.eu/isa2/actions/continuously-updating-european-interoperability-strategy_en EIF reference, 'Want to know more?' section: https://ec.europa.eu/isa2/eif_en"
Assessment of the HTML with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of HTML EIF Scenario v1.0.0
Assessment of the ISO 19941 with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of ISO 19941 EIF Scenario v1.0.0
Assessment of the PROV Family with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of PROV Family EIF Scenario v1.0.0
Assessment of the Schema.org with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of Schema.org EIF Scenario v1.0.0
Assessment of the Better Regulation Toolbox with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of Better Regulation Toolbox EIF Scenario v2.0.0
Assessment of the TIFF/IT with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of TIFF/IT EIF Scenario v1.0.0
Assessment of the OWL2 with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of OWL2 EIF Scenario v1.0.0
"The EIF recommendations are a set of requirements that can be implemented incrementally or separately depending on the context of implementation. EIF reference, 'EIF brochure' document: https://ec.europa.eu/isa2/eif_en"
Assessment of the Domibus with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of Domibus EIF Scenario v1.0.0
Assessment of the XML with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of XML EIF Scenario v2.0.0
Assessment of the ODRL with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of ODRL EIF Scenario v2.0.0
Assessment of the OCSP with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of OCSP EIF Scenario v1.0.0
Assessment of the OpenPM2 with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of OpenPM2 EIF Scenario v1.0.0
CAMSS Assessment of DCAT EIF Scenario v2.0.0
Assessment of the E-ARK with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of E-ARK EIF Scenario v1.0.0
"The domain of application of the EIF is the interoperability domain in the context of the public sector. Moreover, the EIF specification could be used 'as-is' to other domains, such as the location information domain. It is the case of the European Union Location Framework (EULF) Blueprint, also within the ISA2 Programme, which is intended to provide a guidance framework for using location information in policy and digital public services. EIF reference, 'EIF brochure' document: https://ec.europa.eu/isa2/eif_en EULF Blueprint reference: https://joinup.ec.europa.eu/collection/elise-european-location-interoperability-solutions-e-government/solution/eulf-blueprint/about"
Assessment of the AAS with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of AAS EIF Scenario v1.0.0
Assessment of the UTF-8 with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of UTF-8 EIF Scenario v2.0.0
Assessment of the SMP with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of SMP EIF Scenario v2.0.0
Assessment of the ETSI TS 119 612 with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of ETSI TS 119 612 EIF Scenario v2.0.0
Assessment of the GraphQL with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of GraphQL EIF Scenario v1.0.0
Assessment of the RDF with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of RDF EIF Scenario v2.0.0
Assessment of the DIDs with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of DIDs EIF Scenario v1.0.0
"The EIF specification encourages the modelling of business processes and suggests how these processes should be aligned when delivering European public services; however, it does not facilitate any specific technique. EIF reference, 'EIF brochure' document: https://ec.europa.eu/isa2/eif_en"
'The ISA and ISA2 Programmes have been promoting the creation of cross-sectorial communities, openly creating and sharing relevant information and practices within the European Union. In the ISA2 Programme homepage, there are recorded presentations and disseminations on how EU Member States have implemented the EIF specification in their governments, and how they have perceived their experience. ISA2 Programme reference: https://ec.europa.eu/isa2/eif_en'
Assessment of the CAdES with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of CAdES EIF Scenario v1.0.0
Assessment of the NGSI-LD with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of NGSI-LD EIF Scenario v1.0.0
Assessment of the eDelivery SMP with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of eDelivery SMP EIF Scenario v1.0.0
"There is a reference study on the de facto implementation of the EIF components. In this study, the specification's effiency is not totally addressed, due mainly to the lack of dedicated resources. Nonetheless, there are assessments produced by arbitrary stakeholders (public representatives) from different Member States directly addressing the specification's efficiency (see 'EIF evaluation and strategy' initiative), although these ones are not finely structured. EIF components evaluation, page 8: https://op.europa.eu/en/publication-detail/-/publication/29d694d4-4696-11ec-89db-01aa75ed71a1/languageen EIF evaluation and strategy, Feedback section: https://ec.europa.eu/info/law/better-regulation/have-your-say/initiatives/12579-European-Interoperability- Framework-EIF-evaluation-and-EU-governments-interoperability-strategy"
'The ISA and ISA2 Programmes have been promoting the creation of domain-specific and cross-sectorial communities, openly creating and sharing their results within the European Union. There are two relevant assets coming from this community: the ISA2 Action Plan and the final study on the ISA2 Programme Evaluation, where attention was made to analyse and highlight which goals and achievements have been accomplished. ISA2 Programme reference: https://ec.europa.eu/isa2/eif_en ISA2 Programme Action reference: https://ec.europa.eu/isa2/actions/improving-digital-skills-public-sector_en ISA2 Programme evaluation, final study report, page 47: https://ec.europa.eu/isa2/news/study-supporting-final-evaluation-isa%C2%B2-programme-now-available_en'
Assessment of the TOSCA with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of TOSCA EIF Scenario v1.0.0
Assessment of the REST with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of REST EIF Scenario v1.0.0
"The EIF recommendation #17 encourages the use and simplification of digital channels for the delivery of European public services. The specification advocates for the availability of at least one digital channel for accessing a European public service, and ensures the co-existence of both the digital and physical channels in order to make digitisation progress and real. EIF reference, 'EIF brochure' document: https://ec.europa.eu/isa2/eif_en"
'The EIF specification was developed by a large community within the European Commission (EC) and all the EC patents are available with any restrictions related to (F)RAND. EC (ISA2), Communication (COM(2017)134) reference: https://ec.europa.eu/isa2/eif_en'
Assessment of the ISO 27001 with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of ISO 27001 EIF Scenario v1.0.0
Assessment of the TLS 1.3 with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of TLS 1.3 EIF Scenario v1.0.0
'The EIF specification does not provide the precise requirements in order to facilitate organisational interoperability agreements; however, the specification eases the drafting of such agreements in the CEF (Connecting Europe Facility) Building Blocks context, which is focused on the delivery of digital public services across Europe. There is no evidence, nor final report of any building block having been reviewed by the EIF though. COM(2016) 179 final, section 3; https://eur-lex.europa.eu/legal-content/en/TXT/?uri=CELEX%3A52016DC0179'
"The EIF recommendations #46 and #47 promote the secure and trustworthy processing of data, and provides a set of security processes and management functions to this end by means of requirements and services. EIF reference, 'EIF brochure' document: https://ec.europa.eu/isa2/eif_en"
Assessment of the IndexedDB with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of IndexedDB EIF Scenario v1.0.0
Assessment of the IEEE 802.3-2022 with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of IEEE 802.3-2022 EIF Scenario v1.0.0
Assessment of the WSDL with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of WSDL EIF Scenario v2.0.0
"The EIF specification started in 2004, and up to date constitutes the most relevant interoperability programme of the European Union. Every year Member States publish their National Interoperability Frameworks (NIF) with regards to the EIF recommendations. Therefore, this specification is wide-spread used. EIF first release, 'European Interoperability Framework for eGovernment Services' document: http://www.dlorg.eu/uploads/External%20Publications/ NIF reference: https://ec.europa.eu/isa2/solutions/nifo_en ISA2 Programme (EIF major releases): https://ec.europa.eu/isa2/actions/continuously-updating-european-interoperability-strategy_en"
Assessment of the SFIA with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of SFIA EIF Scenario v1.0.0
Assessment of the DWBP with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of DWBP EIF Scenario v1.0.0
Assessment of the AES with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of AES EIF Scenario v1.0.0
"The EIF specification (recommendation #18) oversees long-term preservation of electronic resources, and this is forseen and specified in all the EU Communication and Decision documentations legally supporting the preservation of data, information and knowledge from public administrations' processes. EIF reference, 'EIF brochure' document: https://ec.europa.eu/isa2/eif_en"
"The recommentation #5 of the EIF specification is to promote and provide guidance in the provision of comprehensibility in European public services. Comprehensibility is achievable by combining appropriate specifications, and such comprehensibility should manifest itself in public services interfaces as described in the EIF. EIF reference, 'EIF brochure' document: https://ec.europa.eu/isa2/eif_en"
"The EIF does not allow the amendment of any of its recommendations; recomendations are met or are not. Therefore, this criterion is not applicable to this specification. EIF reference, 'EIF brochure' document: https://ec.europa.eu/isa2/eif_en"
"According to the reference study on the EIF components evaluation, the specification pursues broad objectives, and its recommendations are rather general and lack the detail necessary for a more successful implementation of such framework. Despite the absence of measurable metrics, there are also the Cartography Tools, the Interoperability Test Bed and the IMAPS Solution that seek to facilitate the comparison and the evaluation of today's solutions in European public services. EIF components evaluation, page 8: https://op.europa.eu/en/publication-detail/-/publication/29d694d4-4696-11ec-89db-01aa75ed71a1/language-en Joinup Cartography Tools reference: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/solution/eif-toolbox /solutions-0"
Assessment of the WDS Publishing Data Services with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of WDS Publishing Data Services EIF Scenario v1.0.0
Assessment of the RegOrg with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of RegOrg EIF Scenario v2.0.0
"The EIF recommendation #9 advocates for ensuring data portability within European public services. Thus, the EIF specification explicitly addresses and enables data portability in the context of supporting the evolution of public administration services. EIF reference, 'EIF brochure' document: https://ec.europa.eu/isa2/eif_en"
Assessment of the CSS with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of CSS EIF Scenario v1.0.0
"The EIF is a set of recommendations and provides guidance to European public administrations. This specification does not rely on any specific technology, and therefore is technology agnostic. EIF reference, 'EIF brochure' document: https://ec.europa.eu/isa2/eif_en"
Assessment of the DAPS with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of DAPS EIF Scenario v1.0.0
Assessment of the OData with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of OData EIF Scenario v2.0.0
"The EIF specification encourages public services to use multilingual solutions or promotes their use. However, the specification does not provide nor suggest which solutions, information systems or technical architectures should be used. EIF reference, 'EIF brochure' document: https://ec.europa.eu/isa2/eif_en"
Assessment of the ESPD-EDM with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of ESPD-EDM EIF Scenario v1.0.0
'The EIF specification is not included in any open repository/catalogue of standards at European level, even though the former and later ISA Programmes (ISA and ISA2, respectively) has been offering relevant guidelines, and Joinup itself, the EIF Toolbox. ISA2 Programme reference: https://ec.europa.eu/isa2/eif_en Joinup EIF Toolbox: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/solution/eif-toolbox /eif-toolbox'
'The EIF specification was developed by a large community within the European Commission (EC) and all the EC patents are available on a royalty-free basis. EC (ISA2), Communication (COM(2017)134) reference: https://ec.europa.eu/isa2/eif_en'
Assessment of the IDSA Dataspace Protocol with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of IDSA Dataspace Protocol EIF Scenario v1.0.0
"The recommentation #5 of the EIF specification is to promote and provide guidance in the provision of visibility in European public services. Visibility is achievable by combining appropriate specifications, and such visibility should manifest itself in public services interfaces as described in the EIF. EIF reference, 'EIF brochure' document: https://ec.europa.eu/isa2/eif_en"
"The domain of applicability of the EIF is the interoperability domain and the context of public sector. Moreover, the EIF specification could be implemented 'as-is' to other domains, such as the smart city domain and the local context. It is the case of the Connecting the European Interoperability Framework for Smart Cities and Communities (EIF4SCC), in which the EIF specification has served as a dcatement for this initiative. EIF reference, 'EIF brochure' document: https://ec.europa.eu/isa2/eif_en EULF Blueprint reference: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/news/connecting-eif-smart-cities-communities-eif4scc"
Assessment of the SAREF with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of SAREF EIF Scenario v1.0.0
Assessment of the CLV with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of CLV EIF Scenario v2.0.0
Assessment of the Data Collections API with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of Data Collections API EIF Scenario v1.0.0
Assessment of the CCCEV with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of CCCEV EIF Scenario v2.0.0
Assessment of the HTTP with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of HTTP EIF Scenario v2.0.0
"The EIF specification (recommendation #14) can contribute and promote e-accessibility, but absolutely needs other specifications to achieve it. EIF reference, 'EIF brochure' document: https://ec.europa.eu/isa2/eif_en"
Assessment of the GITB TDL with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of GITB TDL EIF Scenario v1.0.0
Assessment of the ISAE 3402 with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of ISAE 3402 EIF Scenario v1.0.0
"The EIF specification is not included in any Member States' catalogues of recommended specifications. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards"
Assessment of the DCAT-AP with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of DCAT-AP EIF Scenario v2.0.0
Assessment of the IPv4 with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of IPv4 EIF Scenario v2.0.0
Assessment of the OAIS with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of OAIS EIF Scenario v1.0.0
"The EIF specification are a set of recommendations that can be met or not. As far as these recommendations are met, there exists the possibility of further contextualising one or other recommendation. In this sense, the EIF specification allows extension. EIF reference, 'EIF brochure' document: https://ec.europa.eu/isa2/eif_en"
Jääsaari Finnish Tax Administration
Assessment of the XSD with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of XSD EIF Scenario v2.0.0
Assessment of the publiccode.yml with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of publiccode.yml EIF Scenario v1.0.0
Assessment of the ETSI TS 119 511 with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of ETSI TS 119 511 EIF Scenario v1.0.0
Assessment of the DPV with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of DPV EIF Scenario v2.0.0
Assessment of the SHACL with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of SHACL EIF Scenario v2.0.0
Assessment of the ISO 7498-1 with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of ISO 7498-1 EIF Scenario v2.0.0
Assessment of the DoH with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of DoH EIF Scenario v1.0.0
Assessment of the ODF with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of ODF EIF Scenario v1.0.0
Assessment of the FTP with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of FTP EIF Scenario v2.0.0
"The EIF is a set of recommendations and provides guidance to European public administrations. This specification does not rely on any specific platform, and therefore is platform agnostic. EIF reference, 'EIF brochure' document: https://ec.europa.eu/isa2/eif_en"
Assessment of the HTTPS with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of HTTPS EIF Scenario v2.0.0
Assessment of the SAML with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of SAML EIF Scenario v2.0.0
Assessment of the TSP with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of TSP EIF Scenario v2.0.0
'The EIF4SCC initiative is the first adaptation of the EIF specification to a local context, which seeks to support local administrations and other actors with the challenges related to the provision of interoperability services to citizens and businesses. EIF4SCC reference: https://ec.europa.eu/isa2/actions/continuously-updating-european-interoperability-strategy_en'
Assessment of the XFDL with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of XFDL EIF Scenario v1.0.0
Assessment of the VC with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of VC EIF Scenario v1.0.0
Assessment of the JSON with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of JSON EIF Scenario v2.0.0
Assessment of the BFO with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of BFO EIF Scenario v1.0.0
Assessment of the XSLT with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of XSLT EIF Scenario v2.0.0
Assessment of the iCalendar with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of iCalendar EIF Scenario v1.0.0
Assessment of the ebXML RegRep with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of ebXML ebXML RegRep EIF Scenario v2.0.0
Assessment of the ETSI EN 319 532-3 None with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of ETSI EN 319 532-3 None EIF Scenario v1.0.0
Assessment of the ASiC with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of ASiC EIF Scenario v1.0.0
'There is no Member State recommending the EIF specification in its ICT National Catalogue. Nonetheless, there are some Member States Administrations dedicating a part or section of their websites to present or highlight their commitment to the EIF, like Spanish Digital Administration (PAe). Moreover, National NIFO Factsheets are also a sign that the specification is widely recommended. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards PAe reference: https://administracionelectronica.gob.es/pae_Home/pae_Actualidad/pae_Noticias/Anio2021/Octubre/Noticia- 2021-10-29-Publicadas-en-la-Comunidad-EIF-las-buenas-practicas-de-Espa-a-en-materia-deinteroperabilidad-.html?idioma=en NIFO factsheets: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public-administration-factsheets-2021'
Assessment of the RPKI Architecture with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of RPKI Architecture MSP Scenario v1.0.0
Assessment of the ISO 3166-1 with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of ISO 3166-1 EIF Scenario v1.0.0
Assessment of the PNG with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of PNG EIF Scenario v1.0.0
Assessment of the XBRL-GL with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of XBRL-GL EIF Scenario v1.0.0
Assessment of the XBRL GL EIF Scenario with the Common Assessment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of XBRL GL EIF Scenario v2.0.0
'XBRL GL is build on the XML standard, which is an open, text-based data format. This ensures that XBRL GL files are inherently portable and can be created, processed, and consumed on any operating system or hardware architecture without modification. The specification defines the structure of the data itself, not the platform or environment used to handle it, guaranteeing interoperability across different technological platforms._x000D_ _x000D_ XML specification:_x000D_ https://www.w3.org/TR/xml/_x000D_ _x000D_ XBRL 2015 reference: _x000D_ https://www.xbrl.org/int/gl/2015-03-25/GLTFTA-REC-2015-03-25.html_x000D_ _x000D_ XBRL 2017 reference:_x000D_ https://www.xbrl.org/int/gl/2016-12-01/gl-framework-2017-PWD-2016-12-01.html'
'XBRL is an open standard, with our specifications freely available and freely licensed. It adopt policies that are Fair, Reasonable, and Non-Discriminatory (F/RAND) to encourage widespread, open adoption and implementation of their standards. This ensures that no single entity is unfairly advantaged or restricted from using the specification._x000D_ _x000D_ XBRL 2015 reference: _x000D_ https://www.xbrl.org/int/gl/2015-03-25/GLTFTA-REC-2015-03-25.html_x000D_ _x000D_ XBRL 2017 reference:_x000D_ https://www.xbrl.org/int/gl/2016-12-01/gl-framework-2017-PWD-2016-12-01.html'
'The specification is developed as a common interface. XBRL GL facilitates the publication of open data in many ways. A primary goal of open data is that it be usable, and usability is enhanced by reliability. As an important facilitator of a seamless audit trail, XBRL GL is able to represent data from initial source events, activities or documents through to summarisation. As such, it can represent data at any level of detail, and standardise the communication of data appropriate to be open._x000D_ XBRL GL provides a single framework for information both quantitative and qualitative related to business_x000D_ reporting at any level of detail. In conjunction with any standardised code sets, it provides a single structure_x000D_ for expressing the representation of data._x000D_ _x000D_ XBRL 2015 reference:_x000D_ https://www.xbrl.org/int/gl/2015-03-25/GLTFTA-REC-2015-03-25.html_x000D_ _x000D_ XBRL 2017 reference:_x000D_ https://www.xbrl.org/int/gl/2016-12-01/gl-framework-2017-PWD-2016-12-01.html'
'By providing a common, machine-readable format for complex data, XBRL GL allows public administrations to build automated digital channels (such as web portals and APIs) to replace manual, paper-based processes. A good example could be the European Single Electronic Format (ESEF), where companies use a digital channel to submit their annual reports in XBRL._x000D_ _x000D_ European Securities and Markets Authority (ESMA) - ESEF:_x000D_ https://www.esma.europa.eu/policy-activities/corporate-disclosure/european-single-electronic-format_x000D_ _x000D_ XBRL 2015 reference: _x000D_ https://www.xbrl.org/int/gl/2015-03-25/GLTFTA-REC-2015-03-25.html_x000D_ _x000D_ XBRL 2017 reference:_x000D_ https://www.xbrl.org/int/gl/2016-12-01/gl-framework-2017-PWD-2016-12-01.html'
'The effectiveness of the XBRL GL language has been assessed by researchers from Mackenzie Presbyterian University and the University of São Paulo. In the "Use of the XBRL Language: potential benefits to brazilian companies" study, the XBRL language is proposed as a method to communicate financial information to the market, facilitating an increased perception of transparency and a reduction in informational asymmetry._x000D_ _x000D_ "Use of the XBRL Language: potential benefits to brazilian companies" study:_x000D_ https://periodicos.uninove.br/innovation/article/view/24011/10581_x000D_ _x000D_ XBRL 2015 reference: _x000D_ https://www.xbrl.org/int/gl/2015-03-25/GLTFTA-REC-2015-03-25.html_x000D_ _x000D_ XBRL 2017 reference:_x000D_ https://www.xbrl.org/int/gl/2016-12-01/gl-framework-2017-PWD-2016-12-01.html'
"The specification enables reporting for various needs from a single data source. The foundational concept behind XBRL GL's creation, driven by its chief architect Eric Cohen, was to ensure that once a piece of business information is digitally recorded, it can move through the entire reporting supply chain without ever requiring manual re-entry._x000D_ _x000D_ XBRL use cases:_x000D_ https://www.xbrl.org/the-standard/_x000D_ _x000D_ Rutgers Accounting Research Center/CARLab - The Work of Eric Cohen:_x000D_ http://raw.rutgers.edu/carlab/Cohen.html_x000D_ _x000D_ XBRL 2015 reference: _x000D_ https://www.xbrl.org/int/gl/2015-03-25/GLTFTA-REC-2015-03-25.html_x000D_ _x000D_ XBRL 2017 reference:_x000D_ https://www.xbrl.org/int/gl/2016-12-01/gl-framework-2017-PWD-2016-12-01.html"
'XBRL GL foresees sets of requirements that can be implemented separately. There are no requirements on the extent of the implementation of the specification, and the extent of the data contents being used should vary between use cases. This is achieved through its modular architecture, which allows implementers to select from a mandatory Core module and optional modules for specific needs, such as the Business module for customer details or the Tax Audit File module for providing data to tax authorities. It is recommended to publish sets of requirements per implementation._x000D_ _x000D_ XBRL use cases:_x000D_ https://www.xbrl.org/the-standard/_x000D_ _x000D_ XBRL Essentials (validation requirements):_x000D_ https://specifications.xbrl.org/xbrl-essentials.html_x000D_ _x000D_ XBRL 2015 reference: _x000D_ https://www.xbrl.org/int/gl/2015-03-25/GLTFTA-REC-2015-03-25.html_x000D_ _x000D_ XBRL 2017 reference:_x000D_ https://www.xbrl.org/int/gl/2016-12-01/gl-framework-2017-PWD-2016-12-01.html'
'XBRL GL is recommended by European Member States both directly and indirectly. The foundational XBRL specification, on which XBRL GL is based, is officially recommended in the national catalogues of Ireland, Malta, and the Netherlands, as documented in the CAMSS List of Standards. More specifically, the Estonian Tax and Customs Board recommends the use of XBRL GL for the electronic submission of general ledger data as part of its "Reporting 3.0" initiative. This initiative is a core component of Estonia's "Real-Time Economy" vision, which aims to create a seamless, automated data exchange between businesses and the government. By using XBRL GL, the project enables companies to submit transaction-level data directly from their accounting systems, with the ultimate goal of creating a "no-tax-return" environment, demonstrating a deep and innovative recommendation of the specification for a core e-government service._x000D_ _x000D_ CAMSS List of Standars:_x000D_ https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards_x000D_ _x000D_ Estonian Tax and Customs Board - Data-based reporting:_x000D_ https://www.emta.ee/en/business-client/board-news-and-contact/estonian-tax-and-customs-board/data-based-reporting_x000D_ _x000D_ XBRL 2015 reference: _x000D_ https://www.xbrl.org/int/gl/2015-03-25/GLTFTA-REC-2015-03-25.html_x000D_ _x000D_ XBRL 2017 reference:_x000D_ https://www.xbrl.org/int/gl/2016-12-01/gl-framework-2017-PWD-2016-12-01.html'
'The XBRL specification is a pillar of the European Single Electronic Format (ESEF). This regulation requires all issuers on EU regulated markets to prepare their annual financial reports in a single electronic format (based on XBRL). Also it could operate entirely within the General Data Protection Regulation (GDPR), which can include personal data of individuals._x000D_ _x000D_ European Securities and Markets Authority (ESMA) - ESEF:_x000D_ https://www.esma.europa.eu/policy-activities/corporate-disclosure/european-single-electronic-format_x000D_ _x000D_ EUR-Lex - General Data Protection Regulation (GDPR):_x000D_ https://eur-lex.europa.eu/eli/reg/2016/679/oj_x000D_ _x000D_ XBRL 2015 reference: _x000D_ https://www.xbrl.org/int/gl/2015-03-25/GLTFTA-REC-2015-03-25.html_x000D_ _x000D_ XBRL 2017 reference:_x000D_ https://www.xbrl.org/int/gl/2016-12-01/gl-framework-2017-PWD-2016-12-01.html'
'On a technical level, developers and implementers actively discuss the XBRL GL specification, sharing solutions, implementations, and questions on general programming forums such as Stack Overflow , which has a dedicated “xbrl” tag._x000D_ _x000D_ Stack Overflow - XBRL Community_x000D_ https://stackoverflow.com/questions/tagged/xbrl_x000D_ _x000D_ XBRL 2015 reference: _x000D_ https://www.xbrl.org/int/gl/2015-03-25/GLTFTA-REC-2015-03-25.html_x000D_ _x000D_ XBRL 2017 reference:_x000D_ https://www.xbrl.org/int/gl/2016-12-01/gl-framework-2017-PWD-2016-12-01.html'
'The purpose of XBRL is not related to enable the secure processing of data. Therefore, this criterion is not applicable to this specification._x000D_ _x000D_ XBRL 2015 reference: _x000D_ https://www.xbrl.org/int/gl/2015-03-25/GLTFTA-REC-2015-03-25.html_x000D_ _x000D_ XBRL 2017 reference:_x000D_ https://www.xbrl.org/int/gl/2016-12-01/gl-framework-2017-PWD-2016-12-01.html'
'The XBRL specification is defined by a precise set of measurable rules that are designed for automated validation. To facilitate this, XBRL International provides and maintains official "XBRL Conformance Suites". These are comprehensive sets of test files and supporting documentation, including both valid and invalid instances, that software developers use as a resource to automatically test whether their applications correctly implement the rules of the core XBRL 2.1 specification._x000D_ _x000D_ XBRL 2.1 Specification:_x000D_ https://www.xbrl.org/Specification/XBRL-2.1/REC-2003-12-31/XBRL-2.1-REC-2003-12-31+corrected-errata-2013-02-20.html_x000D_ _x000D_ XBRL Conformance Suites:_x000D_ https://specifications.xbrl.org/release-history-base-spec-conformance-suite.html_x000D_ _x000D_ XBRL 2015 reference: _x000D_ https://www.xbrl.org/int/gl/2015-03-25/GLTFTA-REC-2015-03-25.html_x000D_ _x000D_ XBRL 2017 reference:_x000D_ https://www.xbrl.org/int/gl/2016-12-01/gl-framework-2017-PWD-2016-12-01.html'
'The XBRL GL specification is technology agnostic because it is built upon XML. This means that an XBRL GL document is a text-based file with a defined structure that can be created, read, and processed by any software, on any operating system, and using any programming language that has XML parsing capabilities._x000D_ _x000D_ XML specification:_x000D_ https://www.w3.org/TR/xml/_x000D_ _x000D_ XBRL 2015 reference: _x000D_ https://www.xbrl.org/int/gl/2015-03-25/GLTFTA-REC-2015-03-25.html_x000D_ _x000D_ XBRL 2017 reference:_x000D_ https://www.xbrl.org/int/gl/2016-12-01/gl-framework-2017-PWD-2016-12-01.html'
'XBRL-GL is included in 3 national catalogues of recommended specifications. They belong to Ireland, Malta and Netherlands among others. The National Interoperability Framework (NIF) of Ireland and the Netherlands are aligned with at least 3 out of 4 scoreboards of the EIF Monitoring according to the National Interoperability Framework Observatory (NIFO) factsheets._x000D_ _x000D_ CAMSS List of Standars:_x000D_ https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards_x000D_ _x000D_ NIFO Factsheets:_x000D_ https://interoperable-europe.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public-administration-factsheets-2024_x000D_ _x000D_ Ireland national catalogue:_x000D_ https://interoperable-europe.ec.europa.eu/sites/default/files/inline-files/NIFO_2024_Supporting%20document_Ireland_vFINAL.pdf_x000D_ _x000D_ Netherlands national catalogue: _x000D_ https://interoperable-europe.ec.europa.eu/sites/default/files/inline-files/NIFO_2024%20Supporting%20Document_Netherlands_vFinal_1.pdf_x000D_ _x000D_ XBRL 2015 reference:_x000D_ https://www.xbrl.org/int/gl/2015-03-25/GLTFTA-REC-2015-03-25.html_x000D_ _x000D_ XBRL 2017 reference:_x000D_ https://www.xbrl.org/int/gl/2016-12-01/gl-framework-2017-PWD-2016-12-01.html'
'The primary function of XBRL GL is to create a standardised, machine-readable format for detailed financial and business data. This standardisation is the key to interoperability, allowing administrative bodies like tax agencies, regulators, and national treasuries to automate the collection, consolidation, and analysis of information. By enabling seamless data exchange and providing a clear, auditable trail from summary reports down to individual transactions, the specification inherently enhances the transparency of business operations for administrative oversight._x000D_ _x000D_ XBRL 2015 reference: _x000D_ https://www.xbrl.org/int/gl/2015-03-25/GLTFTA-REC-2015-03-25.html_x000D_ _x000D_ XBRL 2017 reference:_x000D_ https://www.xbrl.org/int/gl/2016-12-01/gl-framework-2017-PWD-2016-12-01.html'
'The purpose of XBRL is not related to enable the secure exchange of data. Therefore, this criterion is not applicable to this specification._x000D_ _x000D_ XBRL 2015 reference: _x000D_ https://www.xbrl.org/int/gl/2015-03-25/GLTFTA-REC-2015-03-25.html_x000D_ _x000D_ XBRL 2017 reference:_x000D_ https://www.xbrl.org/int/gl/2016-12-01/gl-framework-2017-PWD-2016-12-01.html'
'The XBRL GL specification is included in national catalogues and repositories. The foundational XBRL specification, on which XBRL GL is based, is officially recommended in the national catalogues of several Member States, including Ireland, Malta, and the Netherlands, as documented in the CAMSS List of Standards. Furthermore, Estonia's "Aruandlus 3.0" (Reporting 3.0) project, a key part of its national "Real-Time Economy" vision, is designed to automate data exchange between companies and the state. This project is built on the principle of using XBRL GL as the standard for machine-readable, transaction-level data for tax and statistical reporting._x000D_ _x000D_ The Baltic Course - Estonia plans wide use of XBRL-GL (Aruandlus 3.0):_x000D_ http://www.baltic-course.com/eng/good_for_business/?doc=159557_x000D_ _x000D_ Estonian Tax and Customs Board - Data-based Reporting:_x000D_ https://www.emta.ee/en/business-client/board-news-and-contact/estonian-tax-and-customs-board/data-based-reporting_x000D_ _x000D_ CAMSS List of Standars:_x000D_ https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards_x000D_ _x000D_ XBRL 2015 reference: _x000D_ https://www.xbrl.org/int/gl/2015-03-25/GLTFTA-REC-2015-03-25.html_x000D_ _x000D_ XBRL 2017 reference:_x000D_ https://www.xbrl.org/int/gl/2016-12-01/gl-framework-2017-PWD-2016-12-01.html'
'The purpose of XBRL GL is not related to the long-term preservation of data, information, or knowledge. Therefore, this criterion is not applicable to this specification._x000D_ _x000D_ XBRL 2015 reference: _x000D_ https://www.xbrl.org/int/gl/2015-03-25/GLTFTA-REC-2015-03-25.html_x000D_ _x000D_ XBRL 2017 reference:_x000D_ https://www.xbrl.org/int/gl/2016-12-01/gl-framework-2017-PWD-2016-12-01.html'
'The XBRL specification was designed to permit not only the capture and expression of business_x000D_ reporting facts in all of the languages supported by ISO 639, but also the internal capture and expression of_x000D_ regulation and guidance related to the reporting content. The specification has support already for 8_x000D_ languages and the process for adding new ones is defined._x000D_ _x000D_ XBRL International - Multilingual XBRL Guidance:_x000D_ https://www.xbrl.org/guidance/multilingual-labels/#:~:text=XBRL%20supports%20multilingual%20taxonomies%20by%20allowing%20labels%20to,reader%20to%20view%20labels%20in%20their%20preferred%20language._x000D_ _x000D_ XBRL 2015 reference: _x000D_ https://www.xbrl.org/int/gl/2015-03-25/GLTFTA-REC-2015-03-25.html_x000D_ _x000D_ XBRL 2017 reference:_x000D_ https://www.xbrl.org/int/gl/2016-12-01/gl-framework-2017-PWD-2016-12-01.html'
'The XBRL specification does not include any mechanisms for confidentiality within the specification itself. The responsibility for implementing confidentiality rests with the systems and infrastructure handling the data, not with the data format._x000D_ _x000D_ XBRL use cases:_x000D_ https://www.xbrl.org/the-standard/_x000D_ _x000D_ XBRL 2015 reference: _x000D_ https://www.xbrl.org/int/gl/2015-03-25/GLTFTA-REC-2015-03-25.html_x000D_ _x000D_ XBRL 2017 reference:_x000D_ https://www.xbrl.org/int/gl/2016-12-01/gl-framework-2017-PWD-2016-12-01.html'
'XBRL-GL is already associated with EIRA ABBs. More specifically, XBRL-GL can define the interoperability aspects of the "Accounting" ABB of the EIRA Technical view and the "Data Representation" ABB of the EIRA Semantic view._x000D_ _x000D_ EIRA Library of Interoperability Specifications (ELIS) v6.1.1:_x000D_ https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/611_x000D_ _x000D_ XBRL 2015 reference: _x000D_ https://www.xbrl.org/int/gl/2015-03-25/GLTFTA-REC-2015-03-25.html_x000D_ _x000D_ XBRL 2017 reference:_x000D_ https://www.xbrl.org/int/gl/2016-12-01/gl-framework-2017-PWD-2016-12-01.html'
'The principal purpose of the XBRL GL specification is to enable data portability. It achieves this by providing a standardised, open, and machine-readable format that is independent of any specific software or platform. This common format allows detailed business and financial data to be seamlessly moved between different applications without loss of meaning or the need for costly custom data transformations._x000D_ _x000D_ XBRL International (Global Ledger overview):_x000D_ https://www.xbrl.org/the-standard/what/global-ledger/_x000D_ _x000D_ XBRL 2015 reference: _x000D_ https://www.xbrl.org/int/gl/2015-03-25/GLTFTA-REC-2015-03-25.html_x000D_ _x000D_ XBRL 2017 reference:_x000D_ https://www.xbrl.org/int/gl/2016-12-01/gl-framework-2017-PWD-2016-12-01.html'
'The purpose of XBRL GL is not related to ensure the protection of personal data managed by_x000D_ Public Administrations. Therefore, this criterion is not applicable to this specification._x000D_ _x000D_ XBRL 2015 reference: _x000D_ https://www.xbrl.org/int/gl/2015-03-25/GLTFTA-REC-2015-03-25.html_x000D_ _x000D_ XBRL 2017 reference:_x000D_ https://www.xbrl.org/int/gl/2016-12-01/gl-framework-2017-PWD-2016-12-01.html'
'The specification is designed to be customisable. Users can customise it by choosing to implement only the optional parts they need. But it also allows users to add their own unique business terms, making it highly adaptable to specific needs._x000D_ _x000D_ XBRL Essentials (Extensibility section):_x000D_ https://specifications.xbrl.org/xbrl-essentials.html_x000D_ _x000D_ XBRL 2015 reference:_x000D_ https://www.xbrl.org/int/gl/2015-03-25/GLTFTA-REC-2015-03-25.html_x000D_ _x000D_ XBRL 2017 reference:_x000D_ https://www.xbrl.org/int/gl/2016-12-01/gl-framework-2017-PWD-2016-12-01.html'
'The purpose of XBRL is not related to provide an access control mechanism. Therefore, this criterion is not applicable to this specification._x000D_ _x000D_ XBRL 2015 reference: _x000D_ https://www.xbrl.org/int/gl/2015-03-25/GLTFTA-REC-2015-03-25.html_x000D_ _x000D_ XBRL 2017 reference:_x000D_ https://www.xbrl.org/int/gl/2016-12-01/gl-framework-2017-PWD-2016-12-01.html'
'XBRL GL specification is included in an open repository at the European level. It is mandated by the European Securities and Markets Authority (ESMA). This mandate is published in the Official Journal of the European Union (via EUR-Lex), the official and permanent repository for all EU law and referenced standards._x000D_ _x000D_ European Single Electronic Format (ESEF) Regulation:_x000D_ https://eur-lex.europa.eu/eli/reg_del/2019/815/oj_x000D_ _x000D_ XBRL 2015 reference: _x000D_ https://www.xbrl.org/int/gl/2015-03-25/GLTFTA-REC-2015-03-25.html_x000D_ _x000D_ XBRL 2017 reference:_x000D_ https://www.xbrl.org/int/gl/2016-12-01/gl-framework-2017-PWD-2016-12-01.html'
'XBRL International has a public reviewing period for all of its specifications._x000D_ XBRL GL consultations can be conducted by XBRL International members and " volunteers" using the _x000D_ "public working drafts"._x000D_ _x000D_ XBRL GL - The Standards Development Process Overview:_x000D_ https://www.xbrl.org/the-consortium/get-involved/navigating-your-journey-as-a-volunteer/the-standards-development-process-overview/_x000D_ _x000D_ XBRL GL - How to contribute or take part in the specification development:_x000D_ https://specifications.xbrl.org/faq.html_x000D_ _x000D_ XBRL 2015 reference: _x000D_ https://www.xbrl.org/int/gl/2015-03-25/GLTFTA-REC-2015-03-25.html_x000D_ _x000D_ XBRL 2017 reference:_x000D_ https://www.xbrl.org/int/gl/2016-12-01/gl-framework-2017-PWD-2016-12-01.html'
'XBRL GL is the core technology for the European Single Electronic Format (ESEF), a major cross-border initiative mandated by the European Securities and Markets Authority (ESMA). The purpose of XBRL within this project is to create a single, machine-readable format for the annual financial reports of all publicly listed companies across the entire European Union. Furthermore, specific national initiatives are using XBRL GL to build systems that facilitate cross-border interoperability; for example, Estonia's "Reporting 3.0" project uses XBRL GL to standardise the exchange of detailed transactional data with its Tax and Customs Board._x000D_ _x000D_ European Single Electronic Format (ESEF) Regulation:_x000D_ https://eur-lex.europa.eu/eli/reg_del/2019/815/oj_x000D_ _x000D_ Estonian Tax and Customs Board - Data-based Reporting:_x000D_ https://www.emta.ee/en/business-client/board-news-and-contact/estonian-tax-and-customs-board/data-based-reporting_x000D_ _x000D_ XBRL 2015 reference: _x000D_ https://www.xbrl.org/int/gl/2015-03-25/GLTFTA-REC-2015-03-25.html_x000D_ _x000D_ XBRL 2017 reference:_x000D_ https://www.xbrl.org/int/gl/2016-12-01/gl-framework-2017-PWD-2016-12-01.html'
'The XBRL GL specification enables data processing accuracy through its mandatory, built-in validation mechanisms. It uses XML Schema to ensure all data conforms to the correct structure and data types, preventing formatting errors. More powerfully, the specification includes a "Calculation Linkbase" which allows for the definition of business rules and mathematical relationships that are automatically checked by processing software._x000D_ _x000D_ XBRL 2.1 Specification - Section 5.2.5.2: Calculation validation:_x000D_ https://www.xbrl.org/Specification/XBRL-2.1/REC-2003-12-31/XBRL-2.1-REC-2003-12-31+corrected-errata-2013-02-20.html#_5.2.5.2_x000D_ _x000D_ XBRL 2015 reference: _x000D_ https://www.xbrl.org/int/gl/2015-03-25/GLTFTA-REC-2015-03-25.html_x000D_ _x000D_ XBRL 2017 reference:_x000D_ https://www.xbrl.org/int/gl/2016-12-01/gl-framework-2017-PWD-2016-12-01.html'
'The specification is explicitly designed to be extended. Users can create their own extension taxonomies to define new, specific concepts (elements) or relationships that are not included in the base XBRL GL standard._x000D_ _x000D_ XBRL Essentials (Extensibility section):_x000D_ https://specifications.xbrl.org/xbrl-essentials.html_x000D_ _x000D_ XBRL 2015 reference:_x000D_ https://www.xbrl.org/int/gl/2015-03-25/GLTFTA-REC-2015-03-25.html_x000D_ _x000D_ XBRL 2017 reference:_x000D_ https://www.xbrl.org/int/gl/2016-12-01/gl-framework-2017-PWD-2016-12-01.html'
'XBRL GL is fundamentally designed for the business and accounting domain. While it is a powerful and flexible standard within this context, its inherent semantics are not directly transferable to entirely different domains like healthcare, legal case management, or scientific research. Therefore, this specification is definetly tied to the business world._x000D_ _x000D_ XBRL 2015 reference: _x000D_ https://www.xbrl.org/int/gl/2015-03-25/GLTFTA-REC-2015-03-25.html_x000D_ _x000D_ XBRL 2017 reference:_x000D_ https://www.xbrl.org/int/gl/2016-12-01/gl-framework-2017-PWD-2016-12-01.html'
'XBRL GL specification simplifies the delivery of public services by enabling information to be exchanged between parties in a standardised way. When public administrations need to communicate with each other or with businesses, they can use a common, machine-readable format instead of relying on separate, proprietary solutions._x000D_ _x000D_ A prime example is the Danish Business Authority, which uses XBRL to receive all annual financial statements and share them with the public as open data, streamlining a core government service._x000D_ _x000D_ Danish Open Data Portal:_x000D_ https://datacvr.virk.dk/data_x000D_ _x000D_ XBRL 2015 reference: _x000D_ https://www.xbrl.org/int/gl/2015-03-25/GLTFTA-REC-2015-03-25.html_x000D_ _x000D_ XBRL 2017 reference:_x000D_ https://www.xbrl.org/int/gl/2016-12-01/gl-framework-2017-PWD-2016-12-01.html'
'XBRL GL provides the standardised, machine-readable data structure that serves as the essential payload for a public administration's digital services, such as tax filing or regulatory reporting. This standardised data format acts as the "contract" for any interface designed to receive this information. _x000D_ _x000D_ XBRL 2015 reference: _x000D_ https://www.xbrl.org/int/gl/2015-03-25/GLTFTA-REC-2015-03-25.html_x000D_ _x000D_ XBRL 2017 reference:_x000D_ https://www.xbrl.org/int/gl/2016-12-01/gl-framework-2017-PWD-2016-12-01.html'
'The efficiency of the XBRL specification has been assessed by Noor Romy Rahwani of Politeknik Negeri Banjarmasin, Indonesia. In the "Adopting XBRL Efficiently: A Learning Curve-Based Strategic Framework" study, the XBRL specification is proposed as a technology whose implementation can be optimised over time, facilitating the identification of more efficient and cost-effective approaches for companies to adopt XBRL, ultimately enhancing their compliance and financial reporting practices._x000D_ _x000D_ "Adopting XBRL Efficiently: A Learning Curve-Based Strategic Framework" study:_x000D_ https://www.researchgate.net/publication/396890163_Adopting_XBRL_Efficiently_A_Learning_Curve-Based_Strategic_Framework_x000D_ _x000D_ XBRL 2015 reference: _x000D_ https://www.xbrl.org/int/gl/2015-03-25/GLTFTA-REC-2015-03-25.html_x000D_ _x000D_ XBRL 2017 reference:_x000D_ https://www.xbrl.org/int/gl/2016-12-01/gl-framework-2017-PWD-2016-12-01.html'
'The specification facilitates business processes by providing a standard, interoperable format for the data that is exchanged at key points within those processes. While not a process modelling language itself, XBRL GL is designed to be implemented into standard business processes like "record-to-report" or "procure-to-pay." By standardising the data payload, it simplifies and enables the automation of these cross-organisational business processes._x000D_ _x000D_ XBRL 2015 reference: _x000D_ https://www.xbrl.org/int/gl/2015-03-25/GLTFTA-REC-2015-03-25.html_x000D_ _x000D_ XBRL 2017 reference:_x000D_ https://www.xbrl.org/int/gl/2016-12-01/gl-framework-2017-PWD-2016-12-01.html'
'The XBRL GL specification does not include its own mechanisms for authentication, but it does address the topic by providing a standardised way to record information about the agents involved in a transaction. This gives implementers the chance to identify which person or entity is associated with a specific data entry. While these elements are not authentication themselves, they serve as a necessary foundation or "key" upon which external authentication systems can be built._x000D_ _x000D_ XBRL 2015 reference: _x000D_ https://www.xbrl.org/int/gl/2015-03-25/GLTFTA-REC-2015-03-25.html_x000D_ _x000D_ XBRL 2017 reference:_x000D_ https://www.xbrl.org/int/gl/2016-12-01/gl-framework-2017-PWD-2016-12-01.html'
'The XBRL GL specification is developed, maintained, and published by XBRL International. This organisation itself constitutes the core community, which is composed of various member organisations, including companies, government agencies, and accounting professionals. Within XBRL International, specific working groups, such as the Global Ledger Working Group, are formally tasked with the ongoing maintenance, development, and support of the specification. _x000D_ _x000D_ XBRL 2015 reference: _x000D_ https://www.xbrl.org/int/gl/2015-03-25/GLTFTA-REC-2015-03-25.html_x000D_ _x000D_ XBRL 2017 reference:_x000D_ https://www.xbrl.org/int/gl/2016-12-01/gl-framework-2017-PWD-2016-12-01.html'
'The first drafts of XBRL GL were developed in 1999 by its chief architect and contributed to XBRL, with the standards process leading to the first official version in 2005. From its inception, the specification was not developed in isolation. To ensure broad applicability and encourage harmonisation, its chief architect and other participants actively collaborated with other international standards bodies. This collaborative history is evident in its relationship with other specifications in overlapping spaces, including the OECD Standard Audit File for Taxation and ISO 21378:2019, proving the versatile capabilities of XBRL GL._x000D_ _x000D_ OECD Standard Audit File for Taxation (SAF-T):_x000D_ https://www.oecd.org/tax/forum-on-tax-administration/publications-and-products/standard-audit-file-for-tax.html_x000D_ _x000D_ ISO 21378:2019:_x000D_ https://www.iso.org/es/contents/data/standard/07/08/70823.html_x000D_ _x000D_ The Wacoal Story;_x000D_ http://www.xbrl.org/business/companies/breathing-new-life-into-old-systems.pdf _x000D_ _x000D_ XBRL 2015 reference: _x000D_ https://www.xbrl.org/int/gl/2015-03-25/GLTFTA-REC-2015-03-25.html_x000D_ _x000D_ XBRL 2017 reference:_x000D_ https://www.xbrl.org/int/gl/2016-12-01/gl-framework-2017-PWD-2016-12-01.html'
'The specification has achieved significant global market acceptance, a fact documented in numerous independent reports and academic literature reviews that analyse its widespread adoption. This is demonstrated by deep, national-level implementations that involve the specification in core digital solutions. A prime example is Turkey, where the government mandates the use of XBRL GL for its electronic bookkeeping system (e-Defter). An even more innovative use case is found in Estonia, where XBRL GL is a cornerstone of the "Reporting 3.0" initiative, a project designed to create a real-time, automated data ecosystem for businesses and government._x000D_ _x000D_ XBRL implementations in Europe:_x000D_ https://www.revistatransparencia.com/ret/article/download/222/340/992_x000D_ _x000D_ Estonian Ministry of Economic Affairs - Real-Time Economy (Reporting 3.0):_x000D_ https://realtimeeconomy-bsr.eu/reporting-model-and-roadmap_x000D_ _x000D_ IFRS Foundation - Turkey Jurisdiction Profile (e-Defter Mandate):_x000D_ https://www.ifrs.org/content/dam/ifrs/publications/jurisdictions/filing-profiles/turkey-18-november-2015.pdf_x000D_ _x000D_ XBRL 2015 reference: _x000D_ https://www.xbrl.org/int/gl/2015-03-25/GLTFTA-REC-2015-03-25.html_x000D_ _x000D_ XBRL 2017 reference:_x000D_ https://www.xbrl.org/int/gl/2016-12-01/gl-framework-2017-PWD-2016-12-01.html'
'The purpose of XBRL is not related to enable the e-accessibility. Therefore, this criterion is not applicable to this specification._x000D_ _x000D_ XBRL 2015 reference: _x000D_ https://www.xbrl.org/int/gl/2015-03-25/GLTFTA-REC-2015-03-25.html_x000D_ _x000D_ XBRL 2017 reference:_x000D_ https://www.xbrl.org/int/gl/2016-12-01/gl-framework-2017-PWD-2016-12-01.html'
"The development of the XBRL GL specification is governed by XBRL International. Direct and ongoing participation in the XBRL GL Working Group is a benefit reserved for members of the consortium. To become a member, an organisation or individual must complete a formal application process (registration and approval) and pay an annual membership. Although non-members can contribute feedback during public review periods and participate in free Community Groups for discussion, they cannot join the working group's core development activities without formal membership._x000D_ _x000D_ XBRL GL - Benefits from been part of the consortium:_x000D_ https://www.xbrl.org/the-consortium/join/membership-benefits/_x000D_ _x000D_ XBRL GL - How to get involved in the consortium:_x000D_ https://www.xbrl.org/the-consortium/get-involved/_x000D_ _x000D_ XBRL 2015 reference: _x000D_ https://www.xbrl.org/int/gl/2015-03-25/GLTFTA-REC-2015-03-25.html_x000D_ _x000D_ XBRL 2017 reference:_x000D_ https://www.xbrl.org/int/gl/2016-12-01/gl-framework-2017-PWD-2016-12-01.html"
'The primary purpose of XBRL GL is to standardise the representation of detailed accounting and business data, not to define administrative procedures, rules, or services themselves. However, by providing a clear, unambiguous, and machine-readable structure for the data that flows through these administrative processes, it significantly contributes to making the overall process more transparent and comprehensible. _x000D_ _x000D_ XBRL 2015 reference: _x000D_ https://www.xbrl.org/int/gl/2015-03-25/GLTFTA-REC-2015-03-25.html_x000D_ _x000D_ XBRL 2017 reference:_x000D_ https://www.xbrl.org/int/gl/2016-12-01/gl-framework-2017-PWD-2016-12-01.html'
'The purpose of XBRL is not related to the protection information against unauthorised changes. Therefore, this criterion is not applicable to this specification._x000D_ _x000D_ XBRL 2015 reference: _x000D_ https://www.xbrl.org/int/gl/2015-03-25/GLTFTA-REC-2015-03-25.html_x000D_ _x000D_ XBRL 2017 reference:_x000D_ https://www.xbrl.org/int/gl/2016-12-01/gl-framework-2017-PWD-2016-12-01.html'
'XBRL 2.1, which XBRL GL is based on, is referenced in "Commission Implementing Decision (EU) 2016/120 of 28 January 2016 on the identification of the eXtensible Business Reporting Language 2.1 for referencing in public procurement". In this Implementing Decision, the XBRL 2.1 specification is identified as an ICT technical specification eligible for referencing in public procurement._x000D_ _x000D_ Commission Implementing Decision (EU) 2016/120:_x000D_ https://eur-lex.europa.eu/eli/dec_impl/2016/120/oj/eng_x000D_ _x000D_ XBRL 2015 reference: _x000D_ https://www.xbrl.org/int/gl/2015-03-25/GLTFTA-REC-2015-03-25.html_x000D_ _x000D_ XBRL 2017 reference:_x000D_ https://www.xbrl.org/int/gl/2016-12-01/gl-framework-2017-PWD-2016-12-01.html'
'The specification can be used as an annex in interoperability agreements. Through the use of XBRL GL Profiles, organisations that wish to interchange data can communicate and agree upon the scope, amount, and restrictions on the data to be interchanged and, where feasible, automate the evaluation of conformation and data quality being exchanged._x000D_ _x000D_ XBRL 2015 reference: _x000D_ https://www.xbrl.org/int/gl/2015-03-25/GLTFTA-REC-2015-03-25.html_x000D_ _x000D_ XBRL 2017 reference:_x000D_ https://www.xbrl.org/int/gl/2016-12-01/gl-framework-2017-PWD-2016-12-01.html'
Assessment of the ADMS with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of ADMS EIF Scenario v2.0.0
Assessment of the Syslog with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of Syslog EIF Scenario v1.0.0
Assessment of the Standard for Public Code with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of Standard for Public Code EIF Scenario v1.0.0
"The EIF specification supports the reuse of data (recommendation #13) for all scenarios. However, much of the effort would depend on the context where the user will make the operations and transactions. EIF reference, 'EIF brochure' document: https://ec.europa.eu/isa2/eif_en"
Assessment of the TGF with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of TGF EIF Scenario v1.0.0
'The EIF specification is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, EIF can define the interoperability aspects of the Service, Interoperability Strategy, Shared Governance Framework, Interoperability Skill, Interoperability Governance, Interoperability Framework, Interoperable Digital Public Service, Service Delivery Model ABBs of the EIRA Organisational View; and the Legislation On Data Information And Knowledge Exchange ABBs of the EIRA Semantic View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /solution/elis/release/v110'
Assessment of the PDF/A with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of PDF/A EIF Scenario v1.0.0
Assessment of the SOAP with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of SOAP EIF Scenario v2.0.0
Assessment of the ISO 19944-1 with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of ISO 19944-1 EIF Scenario v1.0.0
Assessment of the e-CF with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of e-CF EIF Scenario v1.0.0
Assessment of the MIME with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of MIME EIF Scenario v2.0.0
"According to the 5 star Open Data model suggested by Tim Berners-Lee about how to publish linked data, the first star corresponds to the publication of data on the web as open data. The EIF specification refers to open public data as the idea that all public data should be freely available for use and reuse by others, unless restrictions apply, for example, for personal data protection, confidentiality or intellectual property rights. Therefore, in addition to the requirements stated in the previous answer, the specification supports published data as Linked Data. EIF reference, 'EIF brochure' document: ttps://ec.europa.eu/isa2/eif_en Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/en/"
No evidence has been found of the specification being included in a formal interoperability agreement between organisations involved in the European public services provision.
'The specification does not relate to data authenticity, but its DNS Security Extensions (DNSSEC) can be used to ensure the authenticity of DNS responses, preventing attacks by signing DNS data cryptographically. DNS IETF reference: https://datatracker.ietf.org/doc/html/rfc8499'
The FTP is used in the context of the CIRCABC, a cross-border initiative that provides a web application enabling collaboration, communication and document exchange between European Union stakeholders. See: https://ec.europa.eu/isa2/sites/isa/files/circabc.pdf https://circabc.europa.eu/faces/jsp/extension/wai/navigation/container.jsp
'IEEE Std 802.3-2022 is included in one national catalogue of recommended specifications. This catalogue is: Malta. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards Malta List of Standards: https://www.mccaa.org.mt/Section/Content?contentId=1243'
'UDDI registries or nodes depend on WSDL to complete the data exchange transaction and provide the requester with information. Additionally, UDDI relies on SOAP to enable the service invoke by the requester. UDDI and WSDL reference: https://www.ibm.com/docs/es/rsm/7.5.0?topic=uddi-relationship-between-wsdl'
LegalRuleML is not included in any Member States' catalogues of recommended specifications. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
The specification was standardised officially in 2018 by OASIS, it was developed using the LegalDocML TC which is focused on promoting a common legal document standard (based on Akoma Ntoso-UN). The European Commission includes in its Rolling Plan for ICT Standardisation and in the related standardisation activities of the same rolling plan, more spcifically under the focus of eGovernment (1) Policy and Legislation; (2) Requested Actions. Due to this recommendation it can be considered that the specification is sufficiently mature for its use in the developments of products and services. Moreover, LEOS project and pilot wich aims to ease the creation and management of Legal text is using it as basis. Akoma Ntoso: http://www.akomantoso.org/ The European Commission includes in its Rolling Plan for ICT Standarisation: https://ec.europa.eu/digital-single-market/en/rolling-plan-ict-standardisation LEOS: https://joinup.ec.europa.eu/collection/justice-law-and-security/solution/leos-open-source-software-editing-legislation/application-architecture
The purpose of the specification is not related to the availability interfaces. Therefore, this criterion is not applicable to this specification.
'The purpose of OCSP is not related to the long-term preservation of data/information/knowledge. Therefore, this criterion is considered not applicable to this specification. OCSP reference: https://datatracker.ietf.org/doc/html/rfc2560'
The once-only principle is an e-government concept that aims to ensure that citizens, institutions, and companies only have to provide certain standard information to the authorities and administrations once. HTTP is a protocol developed to exchange information over the internet environment. Thus, HTTP eases the implementation of once-only principle by means of allowing administration's stakeholders reduce interaction. See: http://www.toop.eu/sites/default/files/D21_Federated_OOP_Architecture.pdf
'The XACML specification plays a significant role in protecting information against unauthorised changes through its detailed access control policies and enforcement mechanisms. However, XACML does not directly handle all aspects of data protection against unauthorised changes. XACML OASIS reference: https://docs.oasis-open.org/xacml/3.0/xacml-3.0-core-spec-os-en.html'
"Schema.org is not included in any Member States' catalogues of recommended specifications. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards"
'The purpose of the specification is not related to secure and trustworthy data exchange. Therefore, this criterion is not applicable to this specification. XSLT Reference: https://www.w3.org/TR/xslt-30'
'JSON is a data-interchange format is used by APIs, which are involved in the delivery of information between platforms, and in consequence service delivery. This fact makes JSON an element that fosters the delivery of European Public services, including multilingual ones. ecma JSON specification: https://www.-international.org/wp-content/uploads/ECMA-404_2nd_edition_december_2017.pdf'
SHACL has been designed to enhance the semantic and technical interoperability layers of ontologies expressed as RDF graphs. RDF is a European Standard used by public administrations. Furthermore, SHACL is implemented for data validation purposes by DCAT-AP, which is a specification that describes public sector datasets with the aim to enable cross-data portal search for datasets, and make this way public sector data easily searchable across borders and sectors. DCAT-AP is used in the Open Data Support service initiated by the European Commission. See: https://joinup.ec.europa.eu/rdf_entity/http_e_f_fdata_ceuropa_ceu_fw21_fac376c94_b74cf_b4dd7_bade7_b267d6a4ec4dc/about
The W3C Royalty-Free IPR licences granted under the W3C Patent Policy apply to all W3C specifications, including CSS v2.1. W3C Patent practice: https://www.w3.org/TR/patent-practice#ref-AC
'DCAT-AP is a common format fot data exchange that supports the sharing, discovery and reuse of public sector data, therefore, it can enable digital service delivery channels. DCAT-AP Specification: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/dcat-application-profile-data-portals-europe/release/200'
'DNS is recognised and integrated in the DNS4EU initiative, covering both European and national levels, especially those concerning privacy standards, policies and norms. DNS IETF reference: https://datatracker.ietf.org/doc/html/rfc8499 DNS4EU Initiative https://www.joindns4.eu/'
'The specification is independent from any particular software, hardware, or operating system. So, it can be said that DAPS is independent of any specific platform. DAPS: https://github.com/International-Data-Spaces-Association/IDS-G/tree/main/Components/IdentityProvider/DAPS'
OpenPM2 is publicly available for implementation and use for free on ISA2's webpage, and European Open Data Portal. Therefore, it can be reused by the organisations, administrations, open communities, etc. that developed it. OpenPM2 specification reference: https://op.europa.eu/en/publication-detail/-/publication/ac3e118a-cb6e-11e8-9424-01aa75ed71a1/language-en/format-PDF/source-83307127
'TOSCA does not impose the use of any specific mechanism or technology for the long-term preservation of data/information/knowledge; data preservation aspects should be obtainable by the user infrastructure. TOSCA reference: https://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.3/os/TOSCA-Simple-Profile-YAML-v1.3-os.html'
'The W3C Royalty-Free IPR licenses granted under the W3C Patent Policy apply to all W3C specifications, including this specification. W3C Patent practice: https://www.w3.org/TR/patent-practice#ref-AC'
'The purpose of NUTS is not related to the protection of personal data in Public Administrations. Therefore, this criterion is not applicable to this specification. EUROSTAT reference, NUTS Principles and Characteristics section: https://ec.europa.eu/eurostat/web/nuts/principles-and-characteristics'
LDAP is maintained and developed by IETF which is an international community developing open standards. Developer community IETF: https://www.ietf.org/about/
'OpenTelemetry is highly usable beyond any specific business domain due to its standardised, extensible, and flexible design. Its broad ecosystem support and applicability to various industries make it a powerful tool for achieving comprehensive observability. By enabling detailed monitoring and analysis of applications and services, OpenTelemetry facilitates improved performance, reliability, and efficiency across diverse business domains. OpenTelemetry: https://opentelemetry.netlify.app/docs/specs/otel/'
'The specification actively promotes and supports visibility as it defines how such an API enables applications to perform updates on context, register context providers which can be queried to get updates on current and historic context information and subscribe to receive notifications of context changes. GS CIM 009: https://www.etsi.org/deliver/etsi_gs/CIM/001_099/009/01.07.01_60/gs_CIM009v010701p.pdf'
SAMM is available for free on its webpage for its study and implementation by any interested party. SAMM webpage: https://owaspsamm.org/ SAMM Documentation: https://github.com/OWASP/samm/blob/master/Supporting%20Resources/v2.0/OWASP-SAMM-v2.0.pdf
'OpenTelemetry is not related to ensuring the protection of personal data managed by Public Administrations. Therefore, this criterion is considered not applicable to this specification. OpenTelemetry: https://opentelemetry.netlify.app/docs/specs/otel/'
'There is no Member State that includes ISAE 3402 in their national catalogue with The National Interoperability Framework (NIF) in alignment with the three categories 1. Conceptual model for integrated public services provision, 2. interoperability layers, and 3. interoperability principles. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
'As ECLI implements DCMI , which is a uniform identifier that has the same recognizable format for all Member States and EU courts, it can help simplify the delivery of European public services. DCMI About: https://www.dublincore.org/about/ ECLI Webpage: https://e-justice.europa.eu/175/EN/european_case_law_identifier_ecli?init=true'
'ETSI is a European standards development organisation, and as such, all the specifications developed within the organisation are available and can be accessed through its website repository. ETSI standards repository: https://www.etsi.org/standards#page=1&search=ETSI%20TS%20319%20422&title=1&etsiNumber=1&content=1&version=0&onApproval=1&published=1&withdrawn=1&historical=1&isCurrent=1&superseded=1&startDate=1988-01-15&endDate=2022-07-25&harmonized=0&keyword=&TB=&stdType=&frequency=&mandate=&collection=&sort=1'
PDF-Tools provides a conformance validation for PDF and its extensions. There are for free and under payment. See: https://www.pdf-online.com/osa/validate.aspx https://www.pdf-tools.com/pdf20/en/products/pdf-converter-validation/pdf-validator/
"The specification is about providing an access control mechanism for International Data Spaces connectors so that they can only access other connector's data when allowed to. DAPS: https://github.com/International-Data-Spaces-Association/IDS-G/tree/main/Components/IdentityProvider/DAPS"
'There is a DIDs working group tasked to provide support and contiue developing the specification. The mission of the Decentralized Identifier Working Group is two-fold. First, it maintains the Decentralized Identifiers (DIDs) specification and related Working Group Notes. Second, it seeks consensus around the best way to achieve effective interoperability through common requirements, algorithms, architectural options, and various considerations for the DID resolution and DID URL dereferencing processes. DID Working Group: https://www.w3.org/2019/did-wg/'
'No communities have been found created to share data and results of the implementation of ISO 27001 on national platforms. ISO/IEC 27001 reference website: https://www.iso.org/standard/54534.html'
The purpose of CSV is not related to security and privacy of the data exchange. Therefore, this criterion is not applicable to the specification.
"The publiccode.yml specification can indeed be associated with the European Interoperability Reference Architecture (EIRA) building blocks, particularly those related to metadata and data models. As a structured metadata schema for public sector software, publiccode.yml aligns with EIRA's Metadata Management and Data Model building blocks (and potentially others), which support the standardised description and interoperability of digital resources across public administrations. By providing a common model for software documentation, publiccode.yml enhances data discoverability, exchange, and reuse, all essential for effective interoperability within the EIRA framework."
There are several validators for ORDL that help to ensure that the implementation and description of datasets are conformant with the requirements set out in the specification. ODRL Implementation: http://odrlapi.appspot.com/ ODRL Implementation evaluator: http://odrlapi.appspot.com/apidoc/index.html
'OData offers a way to both break down data silos and increase the shared value of data (see Interoperable Europe Portal reference). The specification contributes creating an ecosystem where data consumers and producers can interoperate more than ever, allowing more applications to make sense of a broader set of data. In this sense, the specification promotes visibility, for example through the OData data model. However, no evidence was found in terms of promoting and supporting the internal nor the external visibility of European public services. Interoperable Europe Portal OASIS Open Data Protocol reference: https://interoperable-europe.ec.europa.eu/collection/ict-standards-procurement/solution/odp-oasis-open-data-protocol-odata-tc'
'The purpose of ADMS is not related to the delivery of multilingual public services. Therefore, this criterion is not applicable to this specification. ADMS Specification W3C: https://www.w3.org/TR/vocab-adms/'
ODRL is not included in any supra-national catalogue of specifications or standards.
Core Criterion and Core Evidence Vocabulary can be found for free along within the European Collaborative Platform, Joinup. CCCEV reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-criterion-and-core-evidence-vocabulary
The Better regulation toolbox is an internal European Commission resource designed as a complement to the Commission's Better regulation guideline. It provides more specific and operational guidance to those involved with various better regulation instruments. The construction of European Laws and policies aims to be proportionate to users needs, rights and duties. Also, the specification sets requirements, principles and recommendations for the development of public policies and laws supporting equality and their applicability in the most broader terms. Better Regulation Toolbox reference: https://ec.europa.eu/info/sites/info/files/better-regulation-toolbox_2.pdf
There are no disclosures of ISO IPR Database to identify the licensing under the specification. ISO 14533-2:2012 is not listed in ISO/IEC/ITU Common Patent policy, so it cannot be confirmed that the specification is licensed on a royalty-free basis. ISO patents: https://www.iso.org/iso-standards-and-patents.html ISO standards and patents IPR database: http://isotc.iso.org/livelink/livelink/13622347/Patents_database.xls?func=doc.Fetch&nodeId=13622347
'No Member State includes ETSI TS 119 511 in their national catalogue with Their National Interoperability Framework (NIF) in alignment with the three categories 1. Conceptual model for integrated public servicesprovision, 2. interoperability layers, and 3. interoperability principles. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards'
OWL2 is a business domain agnostic specification that can be reused in a cross-domain way. OWL2 W3C reference: https://www.w3.org/TR/owl2-overview/
'iCalendar has been included in EUROSTAT for the exchange of statistical indicators and their integration in different systems in ics format, which is one of the available iCalendar extensions. Euro-indicators (EUROSTAT) release calendar: https://ec.europa.eu/eurostat/news/internet-calendar iCalendar specification: https://www.rfc-editor.org/rfc/rfc5545'
The purpose of XHTML is not related to organisational interoperability. Therefore, this criterion does not apply to the specification. XHTML W3C reference: https://www.w3.org/TR/xhtml1/
'OpenTelemetry is platform-agnostic, capable of operating across various operating systems, cloud environments, on-premises infrastructures, and deployment models. Its standardised protocols, consistent APIs, modular architecture, and broad integration capabilities ensure that it can provide comprehensive observability for applications running on any platform. OpenTelemetry: https://opentelemetry.netlify.app/docs/specs/otel/'
IETF has a formal review and approval so that all the relevant stakeholders can formally appeal or raise objections to the development and approval of specifications. Each distinct version of an Internet standards-related specification is published as part of the "Request for Comments" (RFC) document series. This archival series is the official publication channel for Internet standards documents and other publications. During the development of a specification, draft versions of the document are made available for informal review and comment by placing them in the IETF's "Internet-Drafts" directory, which is replicated on a number of Internet hosts. This makes an evolving working document readily available to a wide audience, facilitating the process of review and revision. See: https://tools.ietf.org/id/draft-gutmann-tls-lts-10.html
The purpose of XAdES is not related to the delivery of multilingual public services. Therefore, this criterion is not applicable to this specification. XAdES ISO reference: https://www.iso.org/standard/56025.html XAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/101900_101999/101903/01.04.02_60/ts_101903v010402p.pdf
'The implementation of e-signature is a medium through which administrations and stakeholders can exchange digital data reducing the amount of non-digital documents exchanged. Additionally, it fosters the reuse of data across borders, which as well takes part in administrative burden reduction. ETSI EN 319 401 specification: https://www.etsi.org/deliver/etsi_en/319400_319499/319401/02.03.01_60/en_319401v020301p.pdf ETSI TS 119 511 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119511/01.01.01_60/ts_119511v010101p.pdf'
There are not explicit studies or documentation regarding the effectiveness or efficiency of the Core Vocabulary Application Profile. However, an article on the usefulness of the AP for the publication of linked data from administrations. Study about ISA2 efficiency: https://www.ceps.eu/wp-content/uploads/2019/06/NO0119341ENN.en_.pdf On using the core public sector vocabulary (CPSV) to publish a "citizen's guide" as linked data: https://www.researchgate.net/publication/325495548_On_using_the_core_public_sector_vocabulary_CPSV_to_publish_a_citizen's_guide_as_linked_data
'The PROV family of documents aims to be technology-agnostic, meaning it is designed to be compatible with various technologies and systems. It provides a conceptual model and syntax for representing provenance information that can be implemented using different technologies and programming languages. PROV Primer document: https://www.w3.org/TR/prov-primer/'
'OSI is not a European Standard nor have been adopted as such within the EU. OSI reference https://www.iso.org/standard/20269.html'
'The purpose of OAIS is not related to data portability, therefore this criterion is not applicable to the specification. OAIS specification: https://public.ccsds.org/Pubs/650x0m2.pdf'
RDF is available at the Belgian Interoperability Framework website. See: https://www.belgif.be/nl/specificatie/rdf
'W3C has a defined and publicly available Process for the Development and approval process of the specification as a recommended standard, including a public review. W3C Process document: https://www.w3.org/2018/Process-20180201/#Policies'
'The purpose of ETSI TS 119 612 is not related to enable e-accessibility. Therefore this criterion is not applicable to this specification. ETSI TS 119 612: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf'
'The ebXML specification greatly enhances the exposure of interfaces for accessing public administration services. It provides a standardised framework for electronic business information exchange, ensuring interoperability between systems. The messaging services enable reliable and secure delivery of electronic business messages. The registry and repository components help in discovering and accessing services efficiently. ebXML RegRep OASIS reference: https://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html'
'ADMS supports the evolution of European Public Services by enhancing the discoverability and reuse of interoperability solutions. ADMS on Joinup: https://joinup.ec.europa.eu/solution/asset-description-metadata-schema-adms/about ADMS Specification W3C: https://www.w3.org/TR/vocab-adms/'
'By encrypting information, access is effectively restricted to those who do not possess the decryption key. In this sense, encryption serves as a powerful form of de facto access control. This means that even if someone gains access to the encrypted data, they cannot read or use it without the correct key. This ensures that sensitive information remains confidential and secure, providing a robust layer of protection against unauthorised access. AES Standard Reference: https://csrc.nist.gov/pubs/fips/197/final'
'MIME is being used to specify the media types supported by the Europeana collections. Europeana is a cultural initiative that works towards the preservation of the patrimonial heritage. Europeana Media Formats: https://pro.europeana.eu/page/media-formats-mime-types'
"Europeana is a European Commission project which aims to create a cross-border database of all Europe's national museums artworks. For that purpose, the Europeana REST api allows the building of applications that use the wealth of the collections drawn from the major museums across Europe. Europeana REST api reference: https://pro.europeana.eu/page/intro#:~:text=The%20Europeana%20REST%20API%20allows%20you%20to%20build,from%20the%20major%20museums%20and%20galleries%20across%20Europe."
'Currently there are assessments regarding the specification effectiveness, The IDTA initiative provides the relevant information regarding the effectiveness of the specification. This assessments where presented in the Smart Production Solutions in Nuremberg in the fall of 2024. IDTA in Smart Production Solutions fair: https://industrialdigitaltwin.org/en/news-dates/idta-shows-at-sps-in-nuremberg-how-consistent-data-flow-is-ensured-throughout-the-entire-lifecycle-6600 IDTA reference: https://industrialdigitaltwin.org/en/ Details of the Asset Administration Shell (AAS) https://industrialdigitaltwin.org/en/wp-content/uploads/sites/2/2024/06/IDTA-01001-3-0-1_SpecificationAssetAdministrationShell_Part1_Metamodel.pdf'
The specification is available for its use and implementation at the Joinup platform with all its documentation. CPOV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-organisation-vocabulary
The rules on European standardisation allow the European Commission to identify information and communication technology (ICT) technical specifications - that are not national, European or international standards - to be eligible for referencing in public procurement. This allows public authorities to make use of the full range of specifications when buying IT hardware, software and services, allowing for more competition in the field and reducing the risk of lock-in to proprietary systems. After being evaluated compliant with the regulation on standardisation 1025/2012, RDF has been identified by Commission Implementing Decision. During the evaluation process, all the Member States are invited to share their doubts. The positive evaluation of RDF and its identification is considered an interoperability agreement. See: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en
The W3C Royalty-Free IPR licenses granted under the W3C Patent Policy apply to all W3C specifications, including XHTML. W3C Patent practice: https://www.w3.org/TR/patent-practice#ref-AC
'Stakeholders can contribute to IEEE Std 802.3-2022 by joining IEEE and participating in working groups focused on Ethernet. They can suggest changes, give feedback during public reviews, and vote on proposals. Through these activities, stakeholders can influence the development of the Ethernet standard. IEEE Membership-Stakeholders page: https://www.ieee.org/membership/index.html'
'The purpose of DNS is not related to the reuse of information. Therefore, this criterion is not applicable to the specification. DNS IETF reference: https://datatracker.ietf.org/doc/html/rfc8499'
"SAREF's purpose is not related to privacy. Therefore, has not been found included in any initiative neither at European nor on national level covering privacy aspects. SAREF: https://saref.etsi.org/core/v3.1.1/ "
'After checking the different standard catalogues at supra-national level, the Publication Office of the European Union has listed it within EurVocabularies with all the specifications and resources produced and used by European Institutions. EU Vocabularies: https://op.europa.eu/en/web/eu-vocabularies Joinup post linked to the EuroVoc resources: https://joinup.ec.europa.eu/collection/eu-semantic-interoperability-catalogue/news/eurovoc-freely-available'
'The purpose of ISO 3166-1 is not related to e-accessibility. Therefore, this criterion does not apply to this specification. ISO 3166-1 reference: https://www.iso.org/standard/72482.html'
There are existing mechanisms to carry out SAML 2.0 conformity. For instance, SAMLtool.com provides a SAML Response XML validation on open source that can be found at their Github. See: https://www.samltool.com/validate_response.php https://www.samltool.com/
CAdES is an open standard developed and maintained by ETSI, and it is available for free at ETSI’s webpage for everyone to study or implement. See: https://www.etsi.org/standards
'There are existing documentation and studies assessing the efficiency of IPsec. In "A cryptographic evaluation of IPsec" study, the IPsec eficiency is assessed. This study evaluates the efficiency of the IPsec protocol, specifically focusing on the ISAKMP identity protection exchange and the IKE main mode exchanges. It points out that the ISAKMP identity protection exchange can be shortened to four messages, and this reduction can also be applied to IKE main modes using signature or pre-shared key authentication. "A cryptographic evaluation of IPsec" study: https://idorosen.com/mirrors/schneier.com/paper-ipsec.pdf'
The adoption of OpenPM2 as a mechanism for the standardisation of processes and steps within a project can help to reduce the harm when the size of projects varies increasing the volume. The use of OpenPM can ease the scalability of projects since it defines standardised methods for management independently of the scale of projects. OpenPM2 specification reference: https://op.europa.eu/en/publication-detail/-/publication/ac3e118a-cb6e-11e8-9424-01aa75ed71a1/language-en/format-PDF/source-83307127
'DCAT is not included in any supranational catalogue of specifications or standards. DCAT (v2.0.0) reference: https://www.w3.org/TR/vocab-dcat-2/ '
'ETSI TS 119 614-1 is a European standard, delivered by a European Standardisation organisation (ETSI), according to the specification documentation. ETSI TS 119 614-1 reference: https://www.etsi.org/deliver/etsi_ts/119600_119699/11961401/01.01.01_60/ts_11961401v010101p.pdf'
'Domibus is already mapped in the EIRA Library of Interoperability Specifications. More specifically Domibus covers the "Enterprise Service Bus" ABB from the ELIS Technical Interoperability view. ELIS in Joinup: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/v501'
'ISAE 3402 has been selected as the basis for the Cloud Computing Compliance Controls Catalogue (C5), which outlines prerequisites for a conformity assessment using international standards (ISAE 3000, ISAE 3402), adding cloud-specific requirements, especially for transparency. Joinup Cloud Computing (RP 2020): https://joinup.ec.europa.eu/collection/rolling-plan-ict-standardisation/cloud-computing-rp2020'
'There are two Member States recommending OData in their catalogues of recommended specifications. These Member States are The Netherlands and France. Netherlands Catalogue reference: https://www.forumstandaardisatie.nl/open-standaarden/aanbevolen France catalogue reference: https://www.numerique.gouv.fr/uploads/Referentiel_General_Interoperabilite_V2.pdf CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
'YAML can be customized by adjusting key-value pairs, lists, and nested structures. Moreover, settings can be configured, and data structures can be defined and constructed. YAML specification: https://yaml.org/spec/1.2.2/#31-processes'
'OData.org provides a OData Service Validation Tool for free to validate OData implementations. OData Service Validation Tool: https://www.odata.org/blog/odata-service-validation-tool/'
XML is used to encode all communications to web services. Therefore, it fosters the availability of public administrations interfaces. Additionally, the benefit of using XML is that web services are not tied to any one operating system or programming. See: https://esentool.ted.europa.eu/
'The protocol for remote digital signature creation can be domain-agnostic as it can be applicable across various industries and use cases. Standards for digital signatures have generally been developed for a long time considering solutions tailored to the characteristics of devices, therefore they could be implemented and/or used in any domain. ETSI TS 119 432: https://www.etsi.org/deliver/etsi_ts/119400_119499/119432/01.02.01_60/ts_119432v010201p.pdf'
'Verifiable Credentials is developed by W3C, a standard development organisation based in the US. Moreover, Verifiable Credentials specification does not appear in any of the main European standard development bodies, therefore, the specification is not a European standard. CEN-CENELEC homepage: https://www.cencenelec.eu/ ICT technical specifications: https://single-market-economy.ec.europa.eu/single-market/european-standards/ict-standardisation/ict-technical-specifications_en'
'OData promotes the sharing of data and results, and begs for its approval as an ISO/IEC Standard to help accelerate the specification adoption throughout the international community, particularly within government agencies. In this sense, the specification encourages both the creation of communities and the sharing of their data and results on national platforms. OData referenece, data exchange: https://www.oasis-open.org/news/pr/iso-iec-jtc-1-approves-oasis-odata-standard-for-open-data-exchange/'
The last version of the specification was released in 2003 by ETSI’s Technical Committee Electronic Signatures and Infrastructures (ESI). ASiC Baseline profile is linked to the development of ASiC, evolving at the same time. As well, is worth to note that all ETSI standards are focused on market needs ensuring its market acceptance. Moreover, its selection in European initiatives demonstrates its maturity for the development of products and services.
'The purpose of Registered Organization Vocabulary is not related to e-accessibility. Therefore, this criterion is considered not applicable to this specification. Registered Organization Vocabulary reference: https://www.w3.org/TR/vocab-regorg/'
"Although the EN 16234-1 e-CF specification does not make any reference to interoperability issues, the CEN/TC 428 results are aligned with different models and frameworks, and attention has been paid to ensure that these relationships are well defined and published. For example, according to Joinup's Rolling Plan for ICT Standardisation, an update of EN-16234-1 e-CF is in progress, which is intended to add references to the SFIA (Skills Framework for the Information Age) model. Joinup-2021 Rolling Plan for ICT Standardisation reference, Education, Digital skills and Digital learning section: https://joinup.ec.europa.eu/collection/rolling-plan-ict-standardisation/education-digital-skills-and-digital-learning Skills Framework for the Information Age (SFIA) reference: https://www.sfia-online.org/en?msclkid=3c1ee036b64d11ec990d0b2d87d7154a"
'The specification can use extension as it is explained in the specification reference. As an example it can use DCAT-AP which is an aplication profile that works as an extension of the own specification. DCAT (v2.0.0) reference: https://www.w3.org/TR/vocab-dcat-2/ DCAT-AP & European Data Portals reference: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/dcat-application-profile-data-portals-europe '
'XML can be used to represent the data related to business processes, such as the steps involved, the roles and responsibilities of stakeholders, and the inputs and outputs of each step. XML Reference: https://www.w3.org/TR/2006/REC-xml11-20060816/'
'There is no reference to WAI-ARIA and a European use case explicitly stating that the specification allows relevant information and data to be reused. However, since WAI-ARIA can extend a host language, a grid can reuse the elements and attributes of an HTML table element. WAI-ARIA reference: https://www.w3.org/TR/wai-aria/'
The main objective of WS-BPEL is the business process execution for web services, which helps to retrieve and consume data from different sources. However, the availability of interfaces is not the purpose of the specification, so this criterion is not applicable for this specification.
'The roles, state and properties that are defined in this specification do not form a complete web language or format. The implementation of WAI-ARIA relies on the context of a host language, like HTML, and can be partially implemented. WAI-ARIA Authoring Practice reference: https://www.w3.org/TR/wai-aria-practices/ WAI-ARIA User Agent Implementation Guide: https://www.w3.org/TR/wai-aria-implementation/'
'WSDL allows for flexibility in implementing web services. Service providers can choose which operations and features to implement based on their specific requirements. It can define the messages, port types, bindings, and service elements that make up the service contract. However, it does not mandate the inclusion or implementation of every defined operation or feature. W3C WSDL specification: https://www.w3.org/TR/wsdl20/ '
'While the OpenTelemetry specification itself does not directly simplify the delivery of European public services, it provides essential tools and practices for enhancing the observability, reliability, and performance of digital systems underlying these services. OpenTelemetry can improve the delivery of public services as monitoring telemetry data can help improve the systems used to provide citizens with public services. OpenTelemetry: https://opentelemetry.netlify.app/docs/specs/otel/'
'XHTML last update was in the 2000s and is compatible with the way browsers renders HTML5, aside from that the specification might hinder the implementation of CSS and other component that improves the accessibility of users with disabilities. XHTML does not ensure compliance with accessibility standards, such as WAI-ARIA. XHTML does not include features like proper semantic elements, alternative text for images, and ARIA roles, which prevents it from any type of adaptation. Moreover, the Regional Government of Bizkaia developed his website to promote the integration of groups with disabilities into the Public Administration of Bizkaia. This organisation used XHTML 1.0 recommendations and CSS2. XHTML 1.0 implemented in e-accessability project: https://interoperable-europe.ec.europa.eu/collection/einclusion/document/eaccesibility-public-administrationbizkaia-bizkaianet WAI-ARIA Reference: https://www.w3.org/TR/wai-aria/ CSS2 Reference: https://www.w3.org/TR/CSS2/'
'Like all the IETF standards, this specification is a free and open technical specification, built on IETF standards and licenses from the Open Web Foundation. Therefore it is licensed on a royalty-free basis. No IPR disclosures have been submitted directly on this RFC. Intellectual Property Rights in IETF: https://tools.ietf.org/doc/html/rfc8179'
'NUTS classification is not dependent on any other specification, operating system or web platform; therefore, NUTS is platform-agnostic. EUROSTAT reference, NUTS Principles and Characteristics section: https://ec.europa.eu/eurostat/web/nuts/principles-and-characteristics'
'According to the NFV home page, services are deployed by complementing Software Defined Networking (SDN) and NFVI. The NFVI specification highly recommends to adopt other protocols for security and other function aspects. Therefore, NFVI is not technology-agnostic. NFV reference: https://www.etsi.org/technologies/nfv/nfv https://www.etsi.org/deliver/etsi_gs/NFV-INF/001_099/001/01.01.01_60/'
After carrying out research on the efficiency and effectiveness of PNG, no study or documentation assessing the specification has been found to justify this criterion. However, there are many articles comparing PNG with JPG characteristics in terms of effectiveness and efficiency, for example: JPEG vs. PNG: https://www.digitaltrends.com/photography/jpeg-vs-png/
'NUTS is already associated with EIRA ABBs in the EIRA Library Of Specifications (ELIS). More specifically, NUTS can define the interoperability aspects of the Controlled Vocabulary ABB of the EIRA Semantic View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/v110 '
The purpose of SAML 2.0 is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification.
The purpose of HTTP is not related to e-accessibility. Therefore this criterion is considered not applicable specification.
'TOSCA enhances the interoperability capabilities of multiple components, as the specification describes well-defined messages and protocols in different use cases. This allows components from different vendors to be combined and services to be managed seamlessly. TOSCA reference, Artifact Processing and creating Portable Service Templates section: https://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.3/os/TOSCA-Simple-Profile-YAML-v1.3-os.html#_Toc26969502'
'DAPS is not a European Standard as it is not mentioned in any European-level open repository nor catalogue. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards'
'The XACML specification primarily focuses on providing a framework for fine-grained access control, which indirectly contributes to the secure exchange of data. However, it does not directly address the mechanics of data exchange such as encryption, secure transmission protocols, or data integrity. XACML OASIS reference: https://docs.oasis-open.org/xacml/3.0/xacml-3.0-core-spec-os-en.html'
'The specification does not allow any extension to be made. See: https://www.w3.org/TR/2006/REC-xml11-20060816/ '
'While MIME itself does not provide means to enable access control mechanisms, they can always be implemented at the email server, application or network level. MIME specification: https://tools.ietf.org/html/rfc2045'
MIME is being used to specify the media types supported by the Europeana collections. Europeana is a cultural initiative that works towards the preservation of the patrimonial heritage. Europeana Media Types: https://pro.europeana.eu/about-us/mission
"ISO 369-2 is intended to server as a code to identify a language name. Although this collection can be mapped against this same collection to test the specification's implementation conformance, the specification does not publicly provide conformance testing requirements (see ISO 639 reference); the user may opt for their own techniques or for third-party software conformance services. ISO 639-2 reference: https://www.loc.gov/standards/iso639-2/faq.html#13 ISO 639 reference: https://www.iso.org/standard/4767.html"
HTML5 is already associated to an EIRA ABB in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, HTML5 can define the interoperability aspects of the "Human Interface" and "Representation" ABBs from the EIRA Semantic and Technical views. See: https://joinup.ec.europa.eu/solution/elis/distribution/eliscataloguev100betaxlsx
'OData follows REST principles and there exists some kind of data protection, but it is not an integral part of the specification. In this sense the specification relies on the security considerations of the HTTP specification. OData reference: https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#_Toc31358832 HTTP specification security considerations: https://datatracker.ietf.org/doc/html/rfc7231#section-9 '
'The DCAT-AP specification has a section on which multilingual aspects are covered. This section provides a mechanism for indicating the language(s) in which the metadata is available. This is done using the ""dct:language"" property, which can be used to specify the language(s) of the metadata, and also provides guidance on hou to use language tags in metadata fields. DCAT-AP Specification: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/dcat-application-profile-data-portals-europe/release/200'
'As an internet standard, IPv4 promotes a common framework for communication. This can help facilitate agreements between organisations to define a unique method for communicating. Moreover, the IPsec protocol allows organisations to share information safely. IPv4 IETF: https://www.rfc-editor.org/rfc/rfc791'
'The Advanced Encryption Standard is designed to be implemented and used in any domain, allowing its usability in different sectors and applications. In this context, AES is designed to protect data; thus, the standard can be implemented to protect data of any type. AES Standard Reference: https://csrc.nist.gov/pubs/fips/197/final'
'XHTML allows for partial implementations as long as users meet key requirements. In comparison to HTML5, XHTML requires a much more structured document which adds difficulties when performing partial implementations. XHTML W3C reference: https://www.w3.org/TR/xhtml1/#C_2'
The specification is a protocol focused on the transaction of data involved in the email exchange. Even though it is related to data exchange, and it is aimed to ensure the delivery within email services, it is not involved in data portability amongst systems fostering the European Public Services.
'DID Rotation project refers to the process of updating or changing a Decentralized Identifier (DID) while maintaining the continuity and integrity of the digital identity it covers. This procedure is essential for various reasons, including enhancing security, adhering to emerging standards, or transitioning to a more sophisticated infrastructure. This project has received funding from the European Union’s Horizon 2020 research and innovation program. DID Rotation project: https://www.ownyourdata.eu/en/did-rotation/'
The specification is included in 3 Member States' catalogues of recommended specifications. Examples of Member States including ASiC in their catalogues are France or the Netherlands. See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
"TOSCA is not included in any Member States' catalogues of recommended specifications. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards"
"Syslog is not designed specifically for modeling business processes. Syslog's primary purpose is to facilitate the transmission and storage of log messages, typically related to system events, errors, or activities. It doesn't provide the necessary features or structures for representing business processes in a visual or diagrammatic way. Syslog Protocol: https://datatracker.ietf.org/doc/html/rfc5424"
'No royalties are to be paid for the usage of the specification. XBRL GL was developed by an international consortium with a major focus on financial regulators and administrators; the specifications are freely licensed and royalty free. The only restrictions are those imposed by XBRL’s intellectual property policies and trademark rules. https://xbrl.us/home/about/legal/'
Every new version of the specification goes through a defined process with open and public consultations. Request for comments are not restricted to the RDA members but are open to all.
'The specification does not allow any kind of customisation. ETSI EN 319 422 reference: https://www.etsi.org/deliver/etsi_en/319400_319499/319422/01.01.01_60/en_319422v010101p.pdf '
'OData services return URLs to identify resources that may be later requested by clients. Where possible, data reusability increases by exploiting the information found in the route part of the URL, or by easing datasets management. However, data reusability might be limited. There is no evidence of any European solution confirming this aspect. OData reference on extensibility: https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#_Toc31358848'
'The Asset Administration Shell (AAS) is tied up to REST APIs communication. Although the Asset Administration Shell (AAS) service declares its own data model in a machine-readable form, which allows customers to interact with the service on a generic basis, the Asset Administration Shell (AAS) relies on REST APIs in order to be implemented. In this sense the specification has some dependencies on some data formats used by the AAS, mainly with the OPC UA format, that is present in other specifications that usually are implemented along the main one. So, the specification is not technology agnostic. Details of the Asset Administration Shell (AAS) https://industrialdigitaltwin.org/en/wp-content/uploads/sites/2/2024/06/IDTA-01001-3-0-1_SpecificationAssetAdministrationShell_Part1_Metamodel.pdf'
'The NUTS classification has been developed by a lage community within the European Commission (EC) and all the EC patents are available with any restrictions related to royalty-free basis. EC reference, Regulation (EC) No 1059/2003 document: https://eur-lex.europa.eu/legal-content/EN/TXT/?qid=1405939838475&uri=CELEX:32003R1059'
'The GITB TDL documentation does not deal at any point with e-accessibility issues. Therefore, this criterion is not applicable. GITB TDL reference: https://www.itb.ec.europa.eu/docs/tdl/latest/introduction/index.html#introduction'
DCAT-AP allows the exchange of metadata across borders which, in some cases can reduces administrative burden.
'The IPsec specification can enable mechanisms to ensure that data has not been modified and that it is accurately transferred between public administrations or organisations and citizens. In this context, the specification supports authentication methods that enable data encryption and ensure that data has not been modified since its initial form when sent by the sender. In addition, there are some mechanisms such as message authentication code (MAC), which allow for checking whether data has been altered while in transit. This mechanisms can help to enhance data accuracy and guarantee that transferred data is the same as that sent by the original entity. IPSec reference: https://www.rfc-editor.org/rfc/rfc6071.html AH and ESP protocols: https://netseccloud.com/ah-vs-esp-understanding-the-core-differences-in-ipsec-protocols Message Authentication Code mechanism: https://www.twingate.com/blog/ipsec'
'The Dataspace Protocol uses Apache License 2.0 therefore, software developers area allowed to alter the source code of existing software’s source code, copy the original source code or update the source code. Furthermore, developers can then distribute any copy or modification that they make of the software’s source code. The specification is maintained by International Data Spaces Global (IDS-G) and any user can modify it on GitHub. IDSA Dataspace Protocol Specification: https://docs.internationaldataspaces.org/ids-knowledgebase/v/dataspace-protocol/overview/readme Apache License 2.0: https://www.apache.org/licenses/LICENSE-2.0'
'The IETF is a consensus-based group, and authority to act on behalf of the community requires a high degree of consensus and the continued consent of the community. The process of creating and Internet Standard is straightforward: a specification undergoes a period of development and several iterations of review by the Internet community and revision based upon experience, is adopted as a Standard by the appropriate body... and is published. In practice, the process is more complicated, due to (1) the difficulty of creating specifications of high technical quality; (2) the need to consider the interests of all the affected parties; (3) the importance of establishing widespread community consensus; and (4) the difficulty of evaluating the utility of a particular specification for the Internet community. The goals of the Internet Standards Process are: - Technical excellence; - prior implementation and testing; - clear, concise, and easily understood documentation; - openness and fairness; and - timeliness. The goal of technical competence, the requirement for prior implementation and testing, and the need to allow all interested parties to comment all require significant time and effort. The Internet Standards Process is intended to balance these conflicting goals. The process is believed to be as short and simple as possible without sacrificing technical excellence, thorough testing before adoption of a standard, or openness and fairness. Standard process IETF: https://www.ietf.org/standards/process/'
'Regarding the realisation of GITB (Global eBusiness Interoperability Test Beds) as a network of multiple Test Beds, SHACL supports the validation and interoperability of Test Bed components. Moreover, the robust validation mechanisms provided by SHACL contribute to the overall integrity and security of the data being tested. CEN Workshop Agreement Global eBusiness Interoperability Test Beds GITB Phase 3: https://interoperable-europe.ec.europa.eu/collection/european-committee-standardization-cen/solution/cen-workshop-agreement-global-ebusiness-interoperability-test-beds-gitb-phase-3 SHACL W3C reference: https://www.w3.org/TR/shacl/'
'XACML can be used independently from any other operating system. However, it is worth noting that since it is based on XML, it can be dependent on conventions and rules for the correct XML usage. XACML OASIS reference: https://docs.oasis-open.org/xacml/3.0/xacml-3.0-core-spec-os-en.html'
The purpose of OWL2 is not related to security and privacy of the data exchange. Therefore, this criterion is not applicable to this specification. OWL2 W3C reference: https://www.w3.org/TR/owl2-overview/
'CSV has documentation regarding Use Cases and Requirements which analyses its effectiveness & efficiency. CSV on the Web Use Case Reference: https://www.w3.org/TR/csvw-ucr/ CSV reference: https://datatracker.ietf.org/doc/html/rfc4180'
'Although the Indexed Database API is addressed to the storage of information, it can also contribute to enabling certain aspects of data protection from unknown sources. In this context, the Indexed Database API follows a same-origin policy. While you can access stored data within a domain, you cannot access data across different domains. This helps to reduce unwanted user access. Indexed Database API: https://www.w3.org/TR/IndexedDB/ Indexed Dataase API same-origin policy: https://developer.mozilla.org/en-US/docs/Web/API/IndexedDB_API/Basic_Terminology'
'DCAT-AP, as a cross-border and cross-sector vocabulary that increases government-to-government reuse of data and therefore can prevent citizens or businesses from providing standard information several times. Like all common vocabularies, DCAT-AP facilitates the implementation of the once-only principle. DCAT-AP - a key for European data publishers to reach the data consumers and create a European open data ecosystem: https://ec.europa.eu/isa2/dcat-ap-key-european-data-publishers-reach-data-consumers-and-create-european-open-data-ecosystem_en DCAT-AP Specification: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/dcat-application-profile-data-portals-europe/release/200'
'IETF has a formal review and approval so that all the relevant stakeholders can formally appeal or raise objections to the development and approval of specifications. Each distinct version of an Internet standards-related specification is published as part of the "Request for Comments" (RFC) document series. This archival series is the official publication channel for Internet standards documents and other publications. During the development of a specification, draft versions of the document are made available for informal review and comment by placing them in the IETF's "Internet-Drafts" directory, which is replicated on a number of Internet hosts. This makes an evolving working document readily available to a wide audience, facilitating the process of review and revision. Standard process IETF: https://www.ietf.org/standards/process/ Internet Best Current Practices IETF: https://tools.ietf.org/html/rfc2026'
FTP allows public administration to exchange information and therefore to avoid requesting standard information to citizens or businesses several times. FTP is used by MAGA, an initiative from the Flemish Region of Belgium consisting in a common platform for data reuse between administrations. See: https://joinup.ec.europa.eu/solution/magda-platform/about
'ISO/IEC 7498:1 is included in the standards catalogue of UNE, which is the sole Standardization Organization in Spain. UNE has been designated by the Spanish Ministry of Economy, Industry, and Competitiveness to represent Spain to the European Commission. Through its initiatives, UNE actively contributes to the advancement of a quality infrastructure by facilitating knowledge transfer and elevating business standards. UNE: https://www.en.une.org//'
'The purpose of genericode is not related to enabling the secure processing of data. Therefore, this criterion is considered not applicable to this specification. Code List Representation (genericode): https://docs.oasis-open.org/codelist/genericode/v1.0/os/genericode-v1.0-os.html'
Even though at the moment of elaborating the assessment the specification is used, the specification in itself does not give any innovative solution since it is a document format.
There are no assessments regarding the compliance of the specification with European Standardisation Regulation 1025/2012.
The W3C Royalty-Free IPR licenses granted under the W3C Patent Policy apply to all W3C specifications, including RDF. See: https://www.w3.org/TR/patent-practice#ref-AC
'All releases of the EIRA are publicly available and there are mechanisms and channels for providing feedback. Even though there is no creation of a public consultation of each release, the logic and philosophy of the action is that every stakeholder is able to provide feedback for improvements or fixes. Additionally, the Interoperable Europe Solutions action conducts Public Policy Support actions (pilots) with different Member States and its different levels, that are used to gather feedback while implementing the EIRA. EIRA reference: https://interoperable-europe.ec.europa.eu/collection/european-interoperability-reference-architecture-eira /solution/eira/release/610 EIRA Github Repository: https://github.com/CarTool-EC/EIRA '
'The purpose of ETSI TS 119 612 is not related to the reuse of information. Therefore this criterion is not applicable to the specification. ETSI TS 119 612: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf'
'The purpose of Registered Organization Vocabulary is not related to ensure the protection of personal data managed by Public Administrations. Therefore, this criterion is considered not applicable to this specification. Registered Organization Vocabulary reference: https://www.w3.org/TR/vocab-regorg/'
'The purpose of BFO is not related to secure processing of data. Therefore, this criterion is not applicable to the specification. BFO reference: https://www.iso.org/standard/74572.html'
"ELI is not included in any Member States' catalogues of recommended specifications. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards"
'OSI is not recommended by a European Member State. OSI reference https://www.iso.org/standard/20269.html CAMSS list of standards: https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
After checking the assessments performed by CAMSS and the list of specifications identified by the MSP Multi-stakeholder-platform, no assessment verifying the compliance of the specification with the European standardisation regulation has been found. ICT technical specifications: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en
'By means of validating if XML files are conformant with the schema established, the specification helps to ensure the availability of internal information systems of public administrations. It is worth to note that it is possible due to the fact that XML is used to encode communications over the internet. XSD Reference: https://www.w3.org/TR/2012/REC-xmlschema11-1-20120405/'
W3C has a defined and publicly available Process for the Development and approval process of the specification as a recommended standard, including a public review. W3C Process document: https://www.w3.org/2018/Process-20180201/#Policies
XHTML is a family of current and future document types and modules that reproduce, subset, and extend HTML 4. XHTML is a full programming environment for cross-platform applications with access to device capabilities and accepts all types of files to be published. It is intended to be used as a language for content that is both XML-conforming and, if some simple guidelines are followed, operates in HTML 4 conforming user agents. XHTML W3C reference: https://www.w3.org/TR/xhtml1/
'The publiccode.yml could indirectly contribute to the preservation of software information by providing a consistent framework for cataloguing software metadata. Although it does not explicitly address archival standards, this structured metadata can serve as a useful record of software assets, ensuring that key information about software—such as its purpose, licensing, and dependencies—is retained for informational and historical purposes. This can aid in archiving efforts, as it preserves essential descriptive data that may support long-term retrieval and reference needs. While publiccode.yml provides a useful framework for cataloguing software, using it for long-term preservation would require adaptation to meet archival standards. Publiccode.yaml documentation: https://docs.italia.it/italia/developers-italia/publiccodeyml-en/en/master/index.html'
'The purpose of Advanced Encryption Standard is not related to the publication of public data as open data. Therefore this criterion is not applicable to the specification. AES Standard Reference: https://csrc.nist.gov/pubs/fips/197/final'
'IEEE Std 802.3-2022 itself does not guarantee authentication; it provides a framework that can be enhanced with additional protocols to ensure the authenticity and authentication of agents involved in data transactions. Therefore, this criterion is not applicable to this specification. IEEE Std 802.3-2022 Reference: https://ieeexplore.ieee.org/document/9844436'
There is no Member State that includes Core Criterion and Core Evidence Vocabulary in their national catalogue with the National Interoperability Framework (NIF) aligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'After researching for implementations of ETSI TS 119 614-1 that justify market acceptance, no disclousures have been found. ETSI TS 119 614-1 reference: https://www.etsi.org/deliver/etsi_ts/119600_119699/11961401/01.01.01_60/ts_11961401v010101p.pdf'
'ISO/IEC 19944-1 can be mapped to the EIRA Library of Interoperability Specifications (ELIS), more specifically, it is associated with the "Semantic Agreement" and the "Semantic Interoperability Agreement" from the EIRA semantic view. ELIS in Joinup: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/v501'
WS-BPEL is a business domain agnostic specification. The specification: http://docs.oasis-open.org/wsbpel/2.0/OS/wsbpel-v2.0-OS.html
The specification defines an XML based data model for describing web services. This data-model can be reused as a cross-sector data model on how to proceed with a web service description and all elements that it should contain.
UDDI has been selected several times for European administrations in order to make their web services available and discoverable for each other, and their stakeholders An example of this kind UDDI use case is SELIS project, which aims to ease the eInvoicing processes. It is included within the Digital Single Market framework. See: https://joinup.ec.europa.eu/collection/eprocurement/document/secure-electronic-invoicing-service-selis
"In accordance with Common Patent Policy for ITU-T/ITU-R/ISO/IEC the ISO 639-2 is licensed under royalty-free basis. Although there are terms included that allow patent holder to apply specific costs. It is defined in IPR disclosures that can be found at ISO's webpage. ISO patents: https://www.iso.org/iso-standards-and-patents.html ISO standards and patents IPR database: http://isotc.iso.org/livelink/livelink/13622347/Patents_database.xls?func=doc.Fetch&nodeId=13622347"
'The purpose of IPsec is not related to the delivery of multilingual European public services. Therefore this criterion is considered not applicable to this specification. IPSec reference: https://datatracker.ietf.org/doc/html/rfc4301'
'ODRL has been used in several use cases developed in the context of data protection related solutions as SPECIAL (Scalable Policy-aware Linked Data Architecture For Privacy, Transparency and Compliance), an H2020 European project which involves ODRL for compliance check. Approaches for GDPR compliance utilising Semantic Web: https://harshp.com/research/publications/035-representing-activities-processing-personal-data-consent\x02semweb-gdpr-compliance SPECIAL Deliverable: https://www.specialprivacy.eu/images/documents/SPECIAL_D17_M17_V10.pdf'
'Standards are developed by groups of experts called technical committees. These experts are put forward by ISO’s national members. If a user interested in getting involved, they ought to contact their national standards body. Companies and individuals are not eligible to join ISO as members. ISO Technical committees: https://www.iso.org/get-involved.html'
'OpenTelemetry is developed by the Cloud Native Computing Foundation (CNCF), an organisation based in the US that hosts and promotes open source projects for cloud native computing. Moreover, OTel does not appear in any of the main European standard development bodies, therefore, the specification is not a European standard. OpenTelemetry: https://opentelemetry.netlify.app/docs/specs/otel/'
'OData is a recommendation and protocol for data exchange. Therefore, the specification enables the authentic exchange of data among users. Odata reference: https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#_Toc3135883'
By allowing the description of catalogues and datasets, aggregated DCAT metadata can serve as a manifest file as part of the digital preservation process. See: https://www.w3.org/TR/vocab-dcat-2/
Xforms 2.0 is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, Xforms can define the interoperability aspects of the Forms Management Component", and "Forms Management Service" ABBs of the EIRA Technical Infraestructure View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/solution/elis/release/v100
'There is no evidence of the inclusion of EN 303 645 in an open repository/catalogue of standards at European level. EUOS repository of standards: https://www.standict.eu/standards-repository CENELEC and CEN search tool catalogue: https://standards.cencenelec.eu/dyn/www/f?p=CEN:105::RESET::::'
'The purpose of ETSI TS 119 4612 is not related to enabling e-accessibility. Therefore this criterion is not applicable to this specification. ETSI TS 119 612 specification: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf '
'This is an ISO International Standards. In this context, standards are developed by groups of experts called technical committees. These experts are put forward by ISO’s national members. If a user interested in getting involved, they ought to contact their national standards body. Companies and individuals are not eligible to join ISO as members OASIS ebXML Registry Technical Committee reference: https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=regrep Mail Lists and Comments reference: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=regrep#feedback ebXML RegRep OASIS reference: https://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html ebXML RegRep ISO reference: https://www.iso.org/standard/83479.html'
The purpose of WSDL is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification.
'ETSI TS 119 512 is being used in the eIDAS project, which focuses on the creation of e-signature services aiming to enable secure cross-border transactions. eIDAS is based on the Regulation (EU) No 910/2014 of the European Parliament and of the Council of 23 July 2014 on electronic identification and trust services for electronic transactions in the internal market. Regulation (EU) No 910/2014 of the European Parliament and of the Council of 23 July 2014 on electronic identification and trust services for electronic transactions in the internal market: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv:OJ.L_.2014.257.01.0073.01.ENG ETSI TS 119 512 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.02_60/ts_119512v010102p.pdf'
ELI is not included in any Member States' catalogues of recommended specifications. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'The purpose of WAI-ARIA is not related to the secure processing of data. Therefore, this criterion is not applicable to this specification. WAI-ARIA reference: https://www.w3.org/TR/wai-aria/'
'The purpose of ShEx is not related to the visibility of administrative procedures; therefore, this criterion is not applicable to the specification. ShEx primer document: https://shexspec.github.io/primer/ ShEx Community Group: https://www.w3.org/community/shex/ ShEx Github: https://github.com/shexSpec/spec/issues'
'SCIM is listed in the national catalogue of the Netherlands. The National Interoperability Framework (NIF) of these Member States is fully aligned with all the 3 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards NIFO factsheets: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public-administration-factsheets-2023'
"ISO 639-2, and specifically ISO 639, enables to ensuring the display of web content, and therefore addresses e-accessibility. For example, the HTML 'lang' attribute declares the language of a website or a part of it. ISO 369-2 FAQs: https://www.loc.gov/standards/iso639-2"
'The purpose of ISO 639-2 is not related to the secure processing of data. Therefore, this criterion is not applicable to this specification. ISO 639-2 reference: https://www.iso.org/standard/4767.html'
The W3C Royalty-Free IPR licences granted under the W3C Patent Policy apply to all W3C specifications, including HTML. W3C Patent practice: https://www.w3.org/TR/patent-practice#ref-AC
The adoption of the specification aims to foster interoperability between public administrations and cross-border exchange of wheat-related data. Although the specification is not applicable to several business domains, the several implementations are evidence that there is a need for the exchange of wheat-related data across borders.
WS-Security is a SOAP extension, concequently it cannot be reusable for other purposes.
'After searching through different catalogues, no evidence of the Extensible Forms Description Language specification being included in the catalogue of any Member State was found. Extensible Forms Description Language reference: https://www.w3.org/TR/NOTE-XFDL'
'ebXML RegRep is an enabler of digital service delivery channels as the specification contributes to the adoption of Collaboration Protocol Agreements (CPA), which describes how trading partners engage in electronic business collaborations through the exchange of electronic messages (see OASIS CPA reference). Open source CPA toolkit reference: http://ebxml.xml.org/news/open-source-cpa-toolkit Joinup CPA toolkit reference: https://joinup.ec.europa.eu/collection/ict-security/solution/cpa-creation-toolkit CPA reference: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ebxml-cppa'
The purpose of XAdES is not related to the implementation of the once-only principle. Therefore, this criterion does not apply to this specification. XAdES ISO reference: https://www.iso.org/standard/56025.html XAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/101900_101999/101903/01.04.02_60/ts_101903v010402p.pdf
'WAI ARIA provides a set of attributes that can be added to HTML elements to convey additional information to assistive technologies about the roles, states, and properties of those elements. The Spanish "Accessibility Observatory" offers a methodology to ensure the monitoring and evolution of eaccessibility services, and includes WAI-ARIA as one of the elements reporting the current status of eAccessibility in digital public services. The WAI-ARIA specification is implemented in this methodology and scopes comprehensibility of website contents when combined mainly with HTML. WAI-ARIA reference: https://www.w3.org/TR/wai-aria/#intro_ria_accessibility PAe reference, Survey Methodology PDF: https://administracionelectronica.gob.es/pae_Home/en/pae_Estrategias/pae_Accesibilidad/pae_Observatorio_de_Accesibilidad.html?idioma=en'
'The TGF emphasises the importance of comprehensibility in the design and delivery of administrative procedures and services, and provides guidance and best practices for achieving this goal by promoting user-centric design principles such as user testing and feedbach to ensure that services are comprehensible and meet the need of users. TGF specification: http://docs.oasis-open.org/tgf/TGF/v2.0/cs01/TGF-v2.0-cs01.html'
'The OASIS Royalty-Free IPR licenses granted under the OASIS Patent Policy apply to all OASIS specifications, including SMP. OASIS Case Study Guidelines: https://www.oasis-open.org/policies-guidelines/casestudies'
'AMQP provides for the establishment of authenticated and/or encrypted transport through security layers such as TLS (Transport Layer Security) and SASL (Simple Authentication and Security Layer). These layers can be tunneled through one another, allowing for both authentication and encryption. OASIS AMQP Reference: http://docs.oasis-open.org/amqp/core/v1.0/amqp-core-complete-v1.0.pdf SASL Reference: https://www.rfc-editor.org/rfc/rfc2444 TLS Reference: https://www.rfc-editor.org/rfc/rfc8446.html'
'OASIS has defined a clear process where all the stakeholders involved have the opportunity to participate in the development of the specification development process. Moreover, there is a public review in the TC process. SMP OASIS reference: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505009'
At the moment of performing the assessment, Linked Data and Open Data repositories and initiatives are a key point, and public administrations are putting efforts to develop a cross-border environment for open data exchange and reuse. Many initiatives and projects are raising using RDF as a foundation to collide their purpose and objectives. The creation of Linked Open Data solutions can be considered as innovative solutions as they help to evolve the eGoverment.
'As XML is used to encode all communications all over the internet, XSD fosters the visibility and comprehensibility of administrations by providing validation of exchanged data. XSD Reference: https://www.w3.org/TR/2012/REC-xmlschema11-1-20120405/'
There are no disclosures of ISO IPR Database to identify the licensing under the specification. ISO 15948:2004 (PNG) is not listed in ISO/IEC/ITU Common Patent policy, so it cannot be confirmed that the specification is licensed on a royalty-free basis. ISO patents: https://www.iso.org/iso-standards-and-patents.html ISO standards and patents IPR database: http://isotc.iso.org/livelink/livelink/13622347/Patents_database.xls?func=doc.Fetch&nodeId=13622347
There is documentation stating that CCCEV is a good asset for efficient and effective data exchange across-border. The information found remarks on the importance of the CCCEV in the implementation of the Once-Only Principle. Joinup news page "CCCEV - a key enabler of the Once-Only Principle": https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/news/cccev-and-once-only-principle
UDDI is a sector agnostic specification that can be used under any business domain.
The purpose of the specification is to facilitate the exchange of structured data. By allowing to make the data available to other persons or organisations, this Core Vocabulary reduces the administrative burden. CPSV-AP reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-service-vocabulary-application-profile
'The purpose of SAML 2.0 is not related to the delivery of multilingual public services. Therefore, this criterion is not applicable to the specification. SAML 2.0 Reference: http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-tech-overview-2.0.html'
'ISO 639-2 has been adopted by different specifications and used in different contexts. According to the Summer Institute of Linguistics (SIL), regristration authority in charge of the ISO 639-3, ISO 639-3 and ISO 639-2 are complementary and compatible, although having been conceived for different purposes. Moreover, the IETF BCP 47 language tags (generally used when working with HTML and XML) has included all ISO 639 codes in their code suite, indicating market acceptance. ISO 639-2 Registration Authority reference: https://www.loc.gov/standards/iso639-2/develop.html SIL reference: https://iso639-3.sil.org/about/relationships IETF BCP 47 langage tags reference: https://tools.ietf.org/search/bcp47'
'The ebXML specification allows for the registration of information, making it accessible to other organisations or users. Additionally, the specification supports the use of the Collaboration Protocol Profile (CPP), which provides information that can also be stored and accessed by other users. ebXML information reuse: https://www.tutorialspoint.com/ebxml/ebxml_quick_guide.htm ebXML RegRep OASIS reference: https://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html'
'YAML has been used in OpenModel project. In this project, YAML is used as structured data format in which AiiDA workflows are based. AiiDA is an open-source Python framework designed to assist researchers in automating, managing, preserving, sharing, and replicating complex workflows and the data involved in contemporary computational science. The development of this project is focused on the high level API which facilitates the ability to dynamically generate AiiDA workflows based on a YAML structured data format. OpenModel project: https://cordis.europa.eu/project/id/953167/reporting'
By allowing the encoding of data and information through the different information systems and the internet, UTF-8 fosters the visibility of administration services and eases the decision-making of public administrations.
The purpose of WS-BPEL is not related to organisational interoperability. Therefore, this criterion is not applicable to the specification.
OpenPM2 is a business domain agnostic specification that can be reused in a cross-domain way. The implementation of OpenPM2 can help projects from any business domain to ensure the proper development while increasing efficiency and effectiveness. OpenPM2 specification reference: https://op.europa.eu/en/publication-detail/-/publication/ac3e118a-cb6e-11e8-9424-01aa75ed71a1/language-en/format-PDF/source-83307127
"According to the official schema.org blog, the specification addresses e-accessibility to some extent. The specification worked along with the IMS Global Learning Consortium's Access For All Specification and the Accessibility Metadata Project in order to provide accessibility of content for a wide range of users. Therefore, the specification can enable e-accessibility when combined with a set of recommendations taken from such collaborations (see Schema.org Accessibility Properties for Discoverability Vocabulary reference). Official blog for schema.org reference, Content Accessibility post: http://blog.schema.org/2013/12/content-accessibility.html IMS Global Learning Consortium's Access For All Specification homepage reference: http://www.imsglobal.org/activity/accessibility Accessibility Metadata Project reference: http://www.a11ymetadata.org/about/ Schema.org Accessibility Properties for Discoverability Vocabulary reference: https://www.w3.org/2021/a11y-discov-vocab/latest/#intro"
The application of the once-only principle in all EU Member States public administrations aims at reducing the administrative burden. This Core Vocabulary fosters interoperability between public administrations, easing the exchange of business information. An example of this is business registers, which describing legal entities eases its reuse and exchange helping to implement the Once-Only Principle. RegOrg Joinup reference: https://joinup.ec.europa.eu/solution/registered-organization-vocabulary
The W3C Royalty-Free IPR licences granted under the W3C Patent Policy apply to all W3C specifications, including OWL2. W3C Patent practice: https://www.w3.org/TR/patent-practice#ref-AC
SOAP 1.2 has been included within several European cross-border initiatives as can be read in the European Interoperability Architecture (EIA) called Common Vision for an EIA. e-SENSE, e-PSOS or SPOCS are initiatives that implemented SOAP 1.2 in order to carry out their purposes. All the projects are related to the enhancement of interoperability between European administrations across borders and across sectors. See: https://ec.europa.eu/isa2/sites/isa/files/isa_2.1_eia-finalreport-commonvisionforane https://www.etsi.org/deliver/etsi_sr/019000_019099/019050/01.01.01_60/sr_019050v010101p.pdf
Like all the IETF standards, TSP is a free and open technical specification, built on IETF standards and licenses from the Open Web Foundation. FTP is licensed on a F(RAND) basis. TSP IETF reference: https://tools.ietf.org/html/rfc3161
'ISO/IEC 7498:1 does not explicitly address the authenticity and authentication of roles or agents involved in data transactions. Ensuring the authenticity and authentication is typically addressed at higher layers of the OSI model, such as the presentation layer, session layer, and application layer. ISO/IEC 7498:1: https://www.iso.org/standard/20269.html'
"OGC standards appear in Joinups 2024 ICT Rolling Plan. When a specification is included in Joinup's ICT Rolling Plan, it usually means that it is of current relevance and has significant implications for interoperability. This naturally attracts the attention of developer communities, generating debates and discussions to explore its effective implementation, impact and possible improvements. OGC Community: https://www.ogc.org/about-ogc/community/ ICT Rolling plan 2024: Smart sustainable cities and communities: https://joinup.ec.europa.eu/collection/rolling-plan-ict-standardisation/smart-and-sustainable-cities-and-communities-rp2024"
After checking the different standard catalogues at supra-national level, there is no evidence of the inclusion of XHTML within any European catalogue of standards. ICT technical specifications: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en CEN search tool catalogue: https://standards.cen.eu/dyn/www/f?p=CENWEB:105::RESET:::: CENELEC search tool catalogue: https://www.cenelec.eu/dyn/www/f?p=104:107:0::::FSP_LANG_ID:25
Core Criterion and Core Evidence Vocabulary has been used to develop some European projects, for example, ESPD-EDM (European Single Procurement Document - Exchange Data Model) which is the technical representation of the legal European Single Procurement Document. It is used to support interoperability between ESPD services provided all over Europe. ESPD documentation: https://docs.peppol.eu/pracc/espd/edm/ Core Criterion and Core Evidence Vocabulary reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-criterion-and-core-evidence-vocabulary
'while ISO/IEC 19944-1 does not specifically address data processing accuracy, it provides a foundation for organizations to establish data governance practices and security controls that indirectly promote the use of access control mechanisms. ISO/IEC 19944-1 specification: https://www.iso.org/standard/60545.html'
'E-ARK CSIP does not specifically address data processing accuracy mechanisms, nonetheless, it indirectly support such issue by promoting best practices that may contribute to the maintenance of information accuracy such as metadata documentation, preservation planning and the recommendation of standard file formats. E-ARK CSIP specification: https://earkcsip.dilcis.eu/#introduction'
'The purpose of XSD 1.1 is not related to define organisational interoperability aspects. Therefore this criterion is considered not applicable to this specification. XSD Reference: https://www.w3.org/TR/2012/REC-xmlschema11-1-20120405/'
'There are several parts in the specification from 1 to 4 that we can find on the official ETSI webpage. REM services enable cross-border recognition between existing national legal systems related to electronic registered delivery services. Also, the eIDAS regulation is one of the top directives and regulations for the digitalisation of the European environment. ENISA recommendation: https://www.enisa.europa.eu/events/tsforum-caday-2018/presentations/C03_Rock.pdf ETSI Web: https://www.etsi.org/ eIDAS Regulation: https://digital-strategy.ec.europa.eu/en/policies/eidas-regulation'
ISO has defined a clear procedure to develop its standards. It consists in a 6-steps process where everyone who is interested can participate. However, if you want to participate, you have to contact your national standards body and you have to be approved for joining the Technical committee (TC) who will develop the standard. ISO has defined the roadmap of standards, it is composed of 6 steps as before said. For the approval of a standard the two-thirds majority of P-members of TC is needed. If the result is negative, the document is returned to TC/SC to be further studied. The ISO standardization process: https://www.iso.org/stages-and-resources-for-standards-development.html
Although Ogg’s purpose is not to foster the visibility of administrative data or services, it can help to enhance the visualization and visibility of public administrations by providing multimedia content. In fact, the specification helps to store and eases the visualization of media content in any platform of a public administration. Ogg XIPH reference: https://xiph.org/ogg/doc/rfc3533.txt
SHACL was designed to enhance the semantic and technical interoperability layers of ontologies expressed as RDF graphs. RDF is a European Standard used by public administrations in projects for sharing Linked Open Data. This means that the validation carried out with SHACL on RFD graphs fosters their use for the publication of data as Linked Open Data.
Not enough information has been gathered to determine that the specification impacts positively or negatively to long-term preservations. Therefore, it seems that the specification's purpose is not related to the preservation of electronic resources. The Standard for Public Code webpage: https://standard.publiccode.net/
'No, the specification is not a European Standard. XSD Reference: https://www.w3.org/TR/2012/REC-xmlschema11-1-20120405/'
'The ebXML specification extends XML standard. In this context, XML is platform agnostic, therefore ebXML can also be considered as a platform agnostic specification. ebXML RegRep OASIS reference: https://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html'
'The Time Stamping Protocol (TSP), utilizing TSA authentication mechanisms, can enable entities to access certain fields or restrict access, and validate signatures with Time-Stamp Tokens. The assignation of precise timestamps to each transaction or data modification ensures that the sequence and timing of data changes are accurately recorded. This is an important capability for establishing when data was altered or accessed, which can help verify its authenticity. TSP/TSA IETF reference: https://www.rfc-editor.org/rfc/rfc3161'
'OAS has many functionalities that can simplify the delivery of European public services. One of the most notable aspects of OAS is its conformity with REST architectural style, which means it allows for the connection of components in microservices applications. This OAS characteristic, is a key enabler for the simplification of European public services, as it eases the digitalisation and accessibility of RESTful APIs design, documentation and functionalities. OAS specification: https://spec.openapis.org/oas/latest.html#openapi-specification OAS in Github: https://github.com/OAI/OpenAPI-Specification/#participation '
'One of the design goals of YAML is data portability between programming languages. An example can be found in the processes and models section, where it is explained that one measure to maximize data portability is separating properties needed for serialization and presentation. Once it has been done, YAML representations of application information will be consistent and portable between various programming environments. YAML specification: https://yaml.org/spec/1.2.2/#32-information-models'
'The NFVI specification is composed of different virtualised resources that activates depending on the task. Nonetheless, this does not imply that the NFVI specification can be extended. NFVI Deliver, Infrastructure Overview: https://www.etsi.org/deliver/etsi_gs/NFV-INF/001_099/001/01.01.01_60/ '
'The specification is available without any restrictions related to Fair, Reasonable, and Non-Discriminatory ((F)RAND) licensing terms. The specification is published under an open source license. EUPL 1.2 reference: https://eupl.eu/1.2/es/'
The CPSV-AP allows describing public services in a standarised human and machine-readable format. This fact fosters the discoverability of the datasets containing the information of public services. Therefore, it enhances its reuse and visibility. That is the reason why CPSV-AP is implementing the EU Catalogue of Services. Moreover, it is recommended in the CarTool 3.1.0 as one of the Operational enablers for the Catalogue of Services Solution Architecture Template (SAT). CPSV-AP Joinup webpage: https://joinup.ec.europa.eu/solution/core-public-service-vocabulary-application-profile/release/22 Catalogue of Services news page: https://ec.europa.eu/isa2/catalogue-services-helping-eu-countries-catalogue-and-describe-public-services_en
There is no conformity test coming from the IETF, but there are existing IPv4 test suits for free and underpayment. See: http://www.qkdnetsim.info/doc/html/ipv4-test_8cc.html
After carrying out a specific retrieval, no evidence has been found regarding already existing studies or documentation assessing PAdES Baseline Profile’s efficiency and effectiveness.
'The specification has 14 previous releases, which is indicative of sufficient market acceptance for its use in the development of digital solutions/services. There exists relevant independent reports which provide its market acceptance as an example the one on the European Case Law Identifier (ECLI). Independent report from ECLI: https://e-justice.europa.eu/175/EN/european_case_law_identifier_ecli DCMI Version History: https://www.dublincore.org/specifications/dublin-core/dcmi-terms/release_history/'
'OData follows REST principles and there exists some data integrity mechanisms. Any modification of the data must respect the data integrity and as such is referred on the specification. In this sense the header return serves this purpose. OData data modification reference: https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#sec_DataModification'
'The purpose of CSV is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification. CSV reference: https://datatracker.ietf.org/doc/html/rfc4180'
"The specification is associated with EIRA ABB's in the EIRA Library of Interoperability Specifications (ELIS). It is associated with Data Access Service, Access Management Component from Technical Infrastructure and Access Management Service, Authentication Service, Identification Component, Identity Management Service from Technical Application. ELIS link: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /solution/elis/release/v501"
'ISO 27001 has restricted IPR disclosures and requires payment to access it. ISO 27001 foreword: https://www.iso.org/obp/ui/#iso:std:54534:en '
ASiC Baseline Profile is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). Specifically, ASiC Baseline Profile can define the interoperability aspects of “e-Seal Creation Service”, “e-Seal Verification and Validation Service”, “e-Signature Creation Service”, and “e-signature Verification and Validation Service” ABBs of the EIRA Technical View. See: https://joinup.ec.europa.eu/solution/elis/distribution/eliscataloguev100betaxlsx
'The IPsec specification offers mechanisms to guarantee the authenticity of agents involved in data transactions. In this sense IPsec also provides mechanisms to allow or deny access to data. Moreover, the specification also provides mechanisms such as authenticating that data originates from a known sender. IPSec reference: https://www.rfc-editor.org/rfc/rfc6071.html IPsec authenticity: https://www.geeksforgeeks.org/ip-security-ipsec/'
"EuroVoc is not included in any Member States' catalogues of recommended specifications. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards"
HTTPS (Hypertext Transfer Protocol Over TLS) is a Transfer Protocol used for communication over a computer network. It is used to transfer data between administrations.
'By using the specification, digital service delivery channels can be guaranteed aswell as the quality. ETSI EN 319 422 reference: https://www.etsi.org/deliver/etsi_en/319400_319499/319422/01.01.01_60/en_319422v010101p.pdf'
'While the PROV family of documents does not directly address data processing accuracy, nonetheless, some of its specifications that can be serialised such as PROV-XML or PROV-JSON can indirectly contribute to assessing accuracy through traceability, decision-making transparency, and error detection. Ensuring data processing accuracy comprehensively involves utilizing appropriate techniques, processes, and methods specific to the domain or application requirements. PROV Primer document: https://www.w3.org/TR/prov-primer/ PROV Ontology: https://www.w3.org/TR/2013/REC-prov-o-20130430/ PROV Data Model: https://www.w3.org/TR/2013/REC-prov-dm-20130430/'
ASiC Baseline profile has been selected within the CEF Digital Signature Service (hereby DSS), along with CAdES, XAdES and PAdES Baseline profiles. Digital Signature Service is an open-source software library for electronic signature creation and validation supporting the interoperability of electronic signatures. The initiative is an enabler for cross borders interoperability between administrations and businesses. See: https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/Standards+and+specifications https://ec.europa.eu/cefdigital/DSS/webapp-demo/doc/dss-documentation.html https://ec.europa.eu/cefdigital/wiki/pages/viewpage.action?pageId=82773260
'There is no Member State that includes TOSCA in their national catalogue with The National Interoperability Framework (NIF) in alignment with the three categories: 1. Conceptual model for integrated public services provision, 2. interoperability layers, and 3. interoperability principles. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
SMP is not included in any Member States' catalogues of recommended specifications. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
The purpose of Xforms is not related to the publication of public data as linked open data. Therefore, this criterion is not applicable to this specification. Xforms 2.0 W3C reference: https://www.w3.org/community/xformsusers/wiki/XForms_2.0 5-star linked open data: https://www.w3.org/DesignIssues/LinkedData.html
The initial members of the RDA WG have implemented and widely promoted the adoption of the data framework. The most relevant evidence of the market acceptance of is the adoption of the Wheat Data Interoperability Guidelines by WheatIS , an International Wheat Information System that provides a single-access web base system to seamlessly access to a wealth of distributed wheat-related data resources. The WheatIS relies on several data nodes which are representatives of the most important players in wheat research. Other organisations which implemented the specification are: • USDA ARS and Cold Spring Harbor Laboratory • EMBL European Bioinformatics Institute • Australian Center for Plant Functional Genomics • The Genome Analysis Center • Munich Information Center for Protein Sequences (MIPS), Helmholtz Center Munich • INRIA URGI Adoption of the Wheat Data Interoperability Guidelines • Rothamsted Research • James Hutton Institute • CIMMYT Wheat program • Creation of a Query interface for phenotyping data The wide implementation of the specification by these organisations demonstrate that the specification is widely accepted by the very specific market it addresses, the exchange of wheat-related data.
'IPsec is maintained and developed by IETF which is an international community developing open standards. IETF Landing Page: https://www.ietf.org/about/ IPSec reference, Conclusions: https://datatracker.ietf.org/doc/html/rfc4301#appendix-D.8 '
OASIS has defined a clear Technical Committee (hereby TC) process where all the stakeholders involved have the opportunity to participate in the development of the specification development process. OASIS guideline: https://www.oasis-open.org/policies-guidelines/tc-process-2017-05-26
'The Technical Committee (TC) CYBER (Cybersecurity) provides public support to members and non-members alike, with different conditions depending on ETSI membership status. Besides, it dedicates a wiki page to disseminate the Global cybersecurity Ecosystem (constituted in a specification itself, TR 103 306) to help stakeholders, and anyone, discover and identify the components of global cybersecurity. ETSI TC CYBER reference: https://portal.etsi.org/tb.aspx?tbid=824#/5068-home ETSI TC CYBER wiki: https://cyberpublicwiki.etsi.org/index.php?title=ETSI ETSI TR 103 306 reference: https://www.etsi.org/deliver/etsi_tr/103300_103399/103306/'
'After carrying out information retrieval, no document or study has been found assessing the CLV in terms of efficiency or effectiveness. However, there is an ISA2 documentation where there are defined use cases and benefits of using its solutions, including the different Core Vocabularies. Use cases and benefits of ISA² specifications: https://ec.europa.eu/isa2/sites/isa/files/docs/publications/isa2_study_use_cases_and_benefits_of_isa2_specifications_january_2019.pdf Core Location Vocabulary: https://interoperable-europe.ec.europa.eu/collection/semic-support-centre/solution/core-location-vocabulary/release/100'
'According to section 5.3.2 of this specification, security is a key concern for all Cloud Service Commerces (CSCs) when using cloud services, both in terms of interoperability and also, in terms of data portability and application portability thus, it addresses the issue and proposes different recommendations. ISO 19941: https://www.iso.org/obp/ui/en/#iso:std:iso-iec:19941:ed-1:v1:en'
'The purpose of DNS is not related to Data accuracy. Therefore this criterion is not applicable to the specification. DNS IETF reference: https://datatracker.ietf.org/doc/html/rfc8499'
'The Advanced Encryption Standard has been published and is maintained by the National Institute of Standards and Technology (NIST). Moreover, there are specifications that extend AES in Internet Engineering Task Force (IETF). IETF AES Reference: https://mailarchive.ietf.org/arch/browse/smime/?q=Advanced%20Encryption%20Standard National Institute of Standards and Technology (NIST): https://www.nist.gov/ AES Standard Reference: https://csrc.nist.gov/pubs/fips/197/final'
There is no Member State that includes CAdES (ISO 14533-1:2014) in their national catalogue with The National Interoperability Framework (NIF) aligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
The term of PAdES was first introduced in 2009 as PDF Advanced Electronic Signatures (PAdES) on ETSI Technical specifications. The specification has got some updates and the latest version is 1.2.1, it was published in 2010. So, it is mature enough for its use in the development of products and services. ETSI TS 101 733 V1.6.3 (2009-07): https://www.etsi.org/deliver/etsi_ts/102700_102799/10277801/01.01.01_60/ts_10277801v010101p.pdf
After searching in the different official European websites, there is no evidence of any cross-border project that uses XAdES (ISO 14533-2:2012) nor explicit agreements involving the usage of the specification. However, the specification XAdES from ETSI, is involved in some cross-border projects as "Analysis of standards related to Trust Service Providers" developed by ENISA (European Union Agency for Network and Information Security) which is a centre of network and information security expertise for the EU, its member states, the private sector and Europe’s citizens. ENISA project: https://www.enisa.europa.eu/publications/tsp_standards_2015/at_download/fullReport XAdES ISO reference: https://www.iso.org/standard/56025.html XAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/101900_101999/101903/01.04.02_60/ts_101903v010402p.pdf
Ogg is one of the most used free media container to publish videos using HTML5. HTML5 is an important mark-up language which is used to develop websites. So Ogg can be considered a specification that fosters the creation of innovative solutions. Ogg XIPH reference: https://xiph.org/ogg/doc/rfc3533.txt Ogg with HTML5: https://designcoral.com/tips/what-formats-are-needed-to-publish-html5-videos/
'There are existing studies assessing HTTPS in terms of efficiency. Some of the studies found assess HTTPS in comparison with the HTTP specification, or an empirical study of the cost of DNS-over-HTTPS. A COMPARISON OF HTTP AND HTTPS PERFORMANCE: https://citeseerx.ist.psu.edu/documentrepid=rep1&type=pdf&doi=1cd89de5cf0e618924c73ac2b060104b7076f0b7 A Survey on HTTPS Implementation by Android Apps: Issues and Countermeasures: https://www.sciencedirect.com/science/article/pii/S2210832716300722 An Empirical Study of the Cost of DNS-over-HTTPS: https://dl.acm.org/doi/abs/10.1145/3355369.3355575'
'The DCAT specification explicitly mentions a section in its documentation about rights and obligations that can guarantee the protection against unauthorised changes. It can use the properties dcat:rights, dcat:accessRights and dcat:license to ensure this protection. DCAT (v2.0.0) reference (section 8): https://www.w3.org/TR/vocab-dcat-2/ '
'The fifth part of the MIME specification defines the conformance criteria to define a certain level of implementation that allows the useful interworking of messages with content that differs from US-ASCII text. Moreover, there are some free online validators for MIME to check the compliance of MIME messages with the IETF standards. MIME Part Five: Conformance Criteria and Examples https://datatracker.ietf.org/doc/html/rfc2049 MIME online validator: https://www.mimevalidator.net/'
'IndexedDB API can play a supportive role in enabling digital service delivery channels, particularly for web-based services. While IndexedDB itself is not a comprehensive solution for service delivery, it offers a crucial set of capabilities that can help optimise the performance and functionality of digital platforms used in delivering public services. Indexed Database API: https://www.w3.org/TR/IndexedDB/'
'There is no such assessment and evidences found addressing the effectiveness of the specification. GITB TDL reference: https://www.itb.ec.europa.eu/docs/tdl/latest/introduction/index.html#introduction'
'Initially IPsec was designed to be part of the IPv6 specification, but as security became important, it was finally designed to be an independent internet protocol for security. Therefore, this specification is technology agnnostic. IPSec reference: https://www.rfc-editor.org/rfc/rfc6071.html IPsec in IPv4 and IPv6: https://networkengineering.stackexchange.com/questions/37025/ipsec-in-ipv4-and-ipv6'
CSV is included in the ICT Standards List identified for its use in eProcurent at Joinup. Despite the specification cannot be downloaded directly from the European Platform, CSV is a IETF specification that can be reused for free. See: https://tools.ietf.org/html/rfc4180
'The EN 303 645 specification, through ETSI, participates in cooperative projects at the European level. In particular, the EU Agency for Cybersecurity (ENISA), together with ETSI and the CEN and CENELEC "Cybersecurity and Data Protection" technical committee (see J. Pandza's presentation on the ENISA Cybersecurity Standardisation Event, and CEN-CLC/JTC 13 reference), are part of several European initiatives (see Official Journal of the European Union reference) to develop "home-grown" European standards in the field of cybersecurity. For example, the specification has direct implications in the context of European certification systems. ENISA Cybersecurity Standardisation Event 2021, Jasper Pandza presentation: https://www.enisa.europa.eu/events/cybersecurity_standardisation_2021/std-2021-presentations CEN-CLC/JTC 13 reference: https://www.cencenelec.eu/areas-of-work/cenelec-sectors/digital-society-cenelec/cybersecurity-and-data-protection/ Official Journal of the European Union reference: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A52020XG1210%2801%29'
LegalRuleML promotes formal features specific to legal norms, guidelines, policies and reasoning defining a set of aspects and elements that enhance the shareability of data and information. Moreover, the capability to structure the information and model it according to common requirements allow the representation of information, including the fact of fostering the availability of internal interfaces. LEOS implementation is an example of how the specification together with other elements in the structure can represent the information consistently and foster collaborative work. LegalRuleML reference: http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/legalruleml-core-spec-v1.0.html
The specification is included in Slovakia’s catalogue of recommended specifications. Slovakia’s Catalogue: http://www.informatizacia.sk/standardy-is-vs/596s CAMSS List of standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'After searching in different catalogues and repositories, there is no evidence found of ETSI EN 319 422 being included in the catalogue of any Member State. ETSI EN 319 422 reference: https://www.etsi.org/deliver/etsi_en/319400_319499/319422/01.01.01_60/en_319422v010101p.pdf'
'IPv4 is already associated to EIRA ABBs in the EIRA Library of Interoperability Specifications (ELIS). More specifically, IPv4 can define the interoperability aspects of the "Data Exchange" and "Firewall" ABBs of the EIRA Technical View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /solution/elis/release/v610'
The purpose of XHTML is not related to long term preservation of electronic records. Therefore, this criterion is considered not applicable to this specification. XHTML W3C reference: https://www.w3.org/TR/xhtml1/
The ISO 32000-1:2008 which refers to PDF 1.7 is not available for free for everyone to study. Payment is needed to reach access to the standard. See: https://www.iso.org/standard/51502.html
CAdES is a group of extensions to Cryptographic Message Syntax (CMS) signed data which purpose is to make advanced electronic signatures. One profile of CAdES is CAdES-LTA, it is a signature conformant which has one or more long-term-validation attributes that guarantee the preservation of the authenticity of the signature. Moreover, a resulting property of CAdES is that electronically signed documents can remain valid for long periods, even if the signer or verifying party later attempts to deny the validity of the signature. CAdES ISO reference: https://www.iso.org/standard/64756.html CAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/101700_101799/101733/02.01.01_60/ts_101733v020101p.pdf
The Web Services Security (WS-Security) main function is to reinforce integrity and confidentiality of the messages used by SOAP specification. SOAP 1.2 is a protocol intended for exchanging structured information in a decentralized, distributed environment. SOAP uses XML technologies to define an extensible messaging framework providing a message construct that can be exchanged over a variety of underlying protocols. It can be concluded that it is proportionate to the users' needs as it helps to the well functioning of citizens, businesses and administrations.
The rules on European standardisation allow the European Commission to identify information and communication technology (ICT) technical specifications - that are not national, European or international standards - to be eligible for referencing in public procurement. This allows public authorities to make use of the full range of specifications when buying IT hardware, software and services, allowing for more competition in the field and reducing the risk of lock-in to proprietary systems. After being evaluated compliant with the regulation on standardisation 1025/2022, IPSec has been identified by Commission Implementing Decision. During the evaluation process, all the Member States are invited to share their doubts. The positive evaluation of IPSec and its identification is considered an interoperability agreement. See: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en
SMP is publicly available for implementation and study for free on OASIS's webpage. The specification: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505009
'Registered Organization Vocabulary specification is designed to allow for reuse of relevant information. As an example, a case of reuse is the utilisation of the adms:Identifier class from the Asset Description Metadata Schema (ADMS) to represent legal and other identifiers associated with a registered organisation. Registered Organization Vocabulary reference: https://www.w3.org/TR/vocab-regorg/ Asset Description Metadata Schema (ADMS) reference: https://www.w3.org/TR/vocab-adms/'
'ETSI TS 119 512 specifies policy and security protocols for trust service providers providing long-term preservation of digital signatures and of general data using digital signature techniques. The specification performance is closely related to the different specifications involved in electronic signatures across borders. In the context of the European internal market, it can be considered as an asset for the creation of solutions enhancing the interoperability between administrations and businesses when eSignature, and long preservation of electronic records is needed. ETSI TS 119 512 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.02_60/ts_119512v010102p.pdf ETSI TS 119 512 Working group: https://portal.etsi.org/webapp/workprogram/Report_WorkItem.asp?WKI_ID=61427 "Towards a standardised preservation service for qualified electronic signatures and qualified electronic seals" article: https://dl.gi.de/bitstream/handle/20.500.12116/20980/proceedings-01.pdf?sequence=1&isAllowed=y'
'There are two Member States recommending ebXML in their ICT National Catalogues. These Member States are Germany and Norway. Catalogue reference Germany: https://www.cio.bund.de/Web/DE/Architekturen-und-Standards/SAGA/SAGA%205-aktuelle%20Version/saga_5_aktuelle_version_node.html Catalogue reference Norway: https://www.difi.no/fagomrader-og-tjenester/digitalisering-og-samordning/standarder CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
'The purpose of this Core Vocabulary is not related to e-accessibility. Therefore, this criterion is considered not applicable to this specification. CPSV-AP Joinup webpage: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/core-public-service-vocabulary-application-profile/release/22'
The purpose of RDF is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification.
'SFIA is a framework for the ICT community that defines the skills and competencies required by business and technology professionals. The specification is intended to serve as an organisational framework within companies and public administrations as a kind of facilitator for the comprehensibility of organisational procedures. SFIA reference: https://sfia-online.org/en/sfia-8'
'Customizing timestamping protocols involves setting up a publicly available, trusted timestamp management infrastructure. Moreover, this infrastructure collects, processes, and renews timestamps, and there is a list of schemes that offer customisation. The Security Evaluation of Time Stamping Schemes: The Present Situation and Studies: https://www.imes.boj.or.jp/research/papers/english/01-E-18.pdf Timestamp based Concurrency Control: https://www.geeksforgeeks.org/timestamp-based-concurrency-control/'
After checking the assessments performed by CAMSS and the list of specifications identified by the MSP Multi-stakeholder-platform, no assessment verifying the compliance of the specification with the European standardisation regulation has been found. However, since is a specification developed by a European Institution it can be assumed that the asset has been developed and maintain in compliance with European Regulations. EuroVoc webpage: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/eurovoc EU Vocabularies: https://op.europa.eu/en/web/eu-vocabularies ICT technical specifications: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en
'The specification has not been selected for its use in a European Cross-border project. Extensible Forms Description Language reference: https://www.w3.org/TR/NOTE-XFDL'
This Core Vocabulary is a business domain agnostic specification that can be reused in a cross-domain way. CCCEV reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-criterion-and-core-evidence-vocabulary
'By allowing the encoding of data and information through the different information systems and the internet, UTF-8 fosters the visibility of administration services and eases the decision-making of public administrations. UTF-8 specification: https://tools.ietf.org/html/rfc3629 '
'ESPD can facilitate the publication of procurement data on the web given that the document information it provides can be easily processed and shared electronically by public authorities. The ESPD can play a role in facilitating the publication of procurement data on the web, which can help to increase transparency, promote competition, and improve the efficiency of public procurement processes. Moreover, the ESPD can be modeled in XML, an open standard developed by the IETF. Tim Berners-Lee 5 stars open data: https://5stardata.info/en/ ESPD Business handbook https://docs.ted.europa.eu/ESPD-EDM/latest/xml_business_handbook.html'
'8 Member States are recommending XSD in their ICT National Catalogues. See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
The specification is independent from any software, hardware, or operating system. So it can be said that EuroVoc is independent of any specific technology or platform. EuroVoc webpage: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/eurovoc
'The Asset Administration Shell (AAS) allows the stakeholders to adequate the specification to their needs, in this sense the specifications makes provisions for the customisation of identifiers in order to make easier the sharing of information and asset models. This can be seen described on the 4.3.5 section where the composition of the identifiers is explained. Details of the Asset Administration Shell (AAS) https://industrialdigitaltwin.org/en/wp-content/uploads/sites/2/2024/06/IDTA-01001-3-0-1_SpecificationAssetAdministrationShell_Part1_Metamodel.pdf'
XSLT has provided a of applying different XSLT transformations to the XML raw report and generating HTML pages. See: https://signatures-conformance-checker.etsi.org/pub/ASiCConformanceTestChecker_v1.0.pdf
HTML5 is publicly available for implementation and study for free on W3C's webpage. See: https://www.w3.org/TR/2010/WD-html5-20100624/
The purpose of SMTP is not related to the publication of public data as linked open data. Therefore, this criterion is not applicable to this specification. SMTP IETF reference: https://tools.ietf.org/html/rfc5321 Five star linked open data: https://www.w3.org/DesignIssues/LinkedData.html
'WAI-ARIA primarily focuses on improving the accessibility of web content, including interfaces, it does not inherently enable the visibility of administrative procedures, rules data, and services in terms of structuring or organizing data. WAI-ARIA is more concerned with providing additional information to assistive technologies about the semantics and behavior of user interface components. The inclusion of WAI-ARIA in the French "General framework for improving accessibility" (RGAA) within e-accessibility policies reflects a commitment to making digital interfaces more accessible to people with disabilities. This specification facilitates effective interaction for individuals using assistive technologies like screen readers, speech recognition systems, or keyboard commands. Web Accessibility ARIA: https://doit.illinois.gov/initiatives/accessibility/guides/web/introduction-to-aria.html Cornell University: https://it.cornell.edu/accessibility/developers-learn-how-wai-aria-can-improve-accessibility RGAA reference: https://www.numerique.gouv.fr/publications/rgaa-accessibilite/methode-rgaa/criteres/'
'The SFIA Foundation is a collaborative organisation responsible for the maintenance and distribution of SFIA. The entire SFIA maintenance process is open to public consultation. The organisation offers users various channels of communication, namely the SFIA User Forum via the LikedIn job platform. SFIA reference, About SFIA section: https://sfia-online.org/en/about-sfia SFIA reference, LinkedIn: https://www.linkedin.com/groups/1934300/'
'The specification is not related to the prevention of data portability. Therefore it neither prevents nor supports data portability. ECLI implements Dublin Core Ontology, as ECLI is a uniform identifier that has the same recognizable format for all Member States and EU courts. To make it easier to understand and find case law, each document containing a judicial decision should have a set of metadata as described in this paragraph. These metadata should be described according to the standards set by the Dublin Core Metadata Initiative. DCMI About: https://www.dublincore.org/about/ ECLI Information: https://e-justice.europa.eu/175/EN/european_case_law_identifier_ecli?init=true '
XAdES Baseline Profile is a business sector agnostic specification which is reusable beyond the domain for which it was developed. Specifically, implemented to facilitate the electronic signature in compliance with eIDAS.
HTML does not define a cross-sector reusable data model, but defines a markup language to develop web documents.
CSV makes sure content is available on the web, structures data and makes it usable in a non-proprietary open format. So it can be said that CSV is independent from any technology or platform.
No evidence has been found of the specification being included in a formal interoperability agreement between organisations involved in the European public services provision. However, OWL is widely used and implemented among the different European Public Administrations for the publications of open data. The European Data Portal which has the DCAT-AP as the basis, it is reusing OWL elements for the representation of the information.
'Syslog protocol is associated with EIRA ABB's in the EIRA Library of Interoperability Specifications (ELIS). More specifically, it is associated with the “Event Manager”, "Logger" and "Cloud Private Network" ABBs from the Technical-Infrastructure View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /solution/elis/release/600rf'
'The iCalendar specification is technology agnostic. It is designed to be independent of any specific technology or platform, allowing it to be used across various software applications and systems for exchanging calendar data in a standardized format. iCalendar specification: https://www.rfc-editor.org/rfc/rfc5545'
'The ELI specification enables e-accessibility. It is designed to facilitate the access, exchange, and interconnection of information published in European, national, and global information systems. BOE ELI reference: https://www.boe.es/legislacion/eli.php Technical Specification for the implementation of ELI in Spain reference: https://www.elidata.es/documentacion_tecnica/especificacion_tecnica.php?lang=en'
The purpose of the specification is not related to business process modelling. Therefore, this criterion is not applicable to this specification.
After carrying out information retrieval, no document or study has been found assessing the CAdES in terms of efficiency or effectiveness.
'The purpose of OSI is not related to authenticity and authentication therefore the criterion is not applicable. OSI reference https://www.iso.org/standard/20269.html'
'ETSI TS 119 612 is meant to be used as a whole and it does not specify anywhere that it can be partially implemented. ETSI TS 119 612 specification: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf'
'By allowing the exchange of datasets metadata, DCAT increases the searchability, visibility, discoverability, comprehensibility and reuse of existing data, including information on processes and administrative rules. DCAT (v2.0.0) reference: https://www.w3.org/TR/vocab-dcat-2/ '
There is no national or European platform with the specification Ogg available for free.
'SAML 2.0 can be used independently from any other technical specifications or operating system. The specification has been developed by OASIS Security Services Technical Committee independently from any specific platforms or technologies. Even though SAML 2.0 is XML based specifications, as XML is a well-known specification it does not cause technological dependency. Overview of SAML Reference: https://developers.onelogin.com/saml SAML 2.0 Reference: http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-tech-overview-2.0.html'
'The DCAT specification has incorporated the dcat:DataService class which inherits some other properties, among those inherited properties there is the dcat:accessrights class that can provide a mean for restriction of access to information/data. DCAT (v2.0.0) reference ( section 6.8 ): https://www.w3.org/TR/vocab-dcat/ '
'The Better Regulation Guidelines and Toolbox provide a common methodology for planning, developing, assessing, and monitoring the implementation of policies and laws. These specifications are utilised by various EU institutions involved in lawmaking and can be transposed to the national level to ensure that laws and policies uphold the rights of EU citizens. Additionally, through the Regulatory Fitness and Performance Programme (REFIT), the framework seeks to enhance regulatory effectiveness by ensuring that existing regulations remain fit for purpose, reducing unnecessary burdens while maintaining high standards of protection. This alignment with REFIT reinforces the commitment to better regulation by promoting simplification and efficiency across EU and national legislative processes. Better Regulation Guidelines and Toolbox reference: https://commission.europa.eu/law/law-making-process/better-regulation/better-regulation-guidelines-and-toolbox_en Better Regulation Toolbox reference: https://commission.europa.eu/document/download/9c8d2189-8abd-4f29-84e9-abc843cc68e0_en?filename=BR%20toolbox%20-%20Jul%202023%20-%20FINAL.pdf Law-making process: https://ec.europa.eu/info/law/law-making-process_en'
'The Core Location Vocabulary defines a core data model that allows the description of locations, geographical elements in a common way. In this sense, the use of a standardised vocabulary helps maintain the integrity of the data during exchange. This fact ensures a trustworthy reuse and data exchange among administrations and stakeholders. Core Location Vocabulary: https://interoperable-europe.ec.europa.eu/collection/semic-support-centre/solution/core-location-vocabulary/release/100'
Better Regulation Toolbox includes references to the relevance of Linked Open Data for the development of public policies. It is one of the principles or basis for the evidence-based development that the specification defines, however, the purpose of the specification is not related to the development and publication of Linked Open Data. Betterr Regulation Toolbox reference: https://ec.europa.eu/info/sites/info/files/better-regulation-toolbox_2.pdf 5-star linked open data: https://www.w3.org/DesignIssues/LinkedData.html
'The OASIS decision-making process for the approval of a specification is clearly defined. Decisions are taken based on votes requiring a Simple Majority Vote to pass. Furthermore, a public review is included in the TC process. Review process OASIS: https://www.oasis-open.org/policies-guidelines/tc-process-2017-05-26'
'XSLT specification includes several mechanisms for assessing its effectiveness, primarily through testing and implementation reports. There are document of the European Commission assessing the suitability of XSLT specification. XSLT Reference: https://www.w3.org/TR/xslt-30 Digital Signature Service: https://ec.europa.eu/cefdigital/DSS/webapp-demo/doc/dss-documentation.html#_xades_profiles '
ETSI’s standards-making process has been clearly defined after years of experience. The organisation has adopted the open approach which means direct participation and consensus as a basis to develop standards. All the stakeholders have the opportunity to participate directly in the process of standardisation through the technical committees created to develop ETSI’s technical specifications and standards. The decision-making process includes a public review, where stakeholders involved can provide technical feedback in order to enhance and maximize the quality and accuracy of the standards. See: https://www.etsi.org/standards/standards-making
'HTTPS is maintained by IETF which is an international community developing open standards. About IETF: https://www.ietf.org/about/ '
'The purpose of DNS is not related to the reuse of information. Therefore, this criterion is not applicable to the specification. DNS IETF reference: https://www.ietf.org/rfc/rfc1034.txt'
'RDF N-Triples is a lined-based plain text format that performs encoding RDF graphs, this encoding is carried out by using UTF-8. As RDF is the main technology used to publish Linked Open Data (LOD), therefore, the specification which is an open standard, could help to the publication of data as LOD, ensuring the correct representation and processing of characters from a wide range of scripts. N-triples specification: https://www.w3.org/TR/n-triples/ '
MIME does not define a common reusable data model, it is a standard mail format for the exchange of data. MIME reference: https://tools.ietf.org/html/rfc2045
'While ISO/IEC 19944-1 does not explicitly define or prescribe authenticity features, it recognizes its importance in the context of data management and governance. To such purpose, ISO/IEC 19944-1 promotes the use of security controls (such as authentication mechanisms) and data governance best practices, such as documentation and labelling, to ensure the authenticity and integrity of data by mantaining audit trails, version controls, and metadata. ISO/IEC 19944-1 specification: https://www.iso.org/standard/60545.html'
'The E-ARK CSIP has support from the The Digital Information LifeCycle Interoperability Standards Board (DILCIS Board), an international group of experts committed to maintain and sustain all the E-ARK specifications. About E-ARK https://dilcis.eu/about'
The application of the once-only principle in all EU Member States public administrations aims at reducing the administrative burden. To achieve this, interoperability between public administrations is a sine qua non condition. XSLT is a language for transforming XML documents, consequently it can be concluded that through this functions it promotes the once-only principle
FTP is published on Joinup, the collaborative platform for reusable IT Solutions funded by the European Commission. See: https://joinup.ec.europa.eu/solution/file-transfer-protocol/distribution/file-transfer-protocol
'RDF is maintained by W3C which is an international community developing open standards. W3C: https://www.w3.org/Consortium/ RDF primer document: https://www.w3.org/TR/rdf11-primer/'
'This specification provides a conceptual model of roles, states and properties that can be used to increase the accessibility and interoperability of web content and web applications. In this sense, the specification eases the implementation process of European public services. WAI-ARIA reference: https://www.w3.org/TR/wai-aria/'
'EIRA includes mechanism to ensure that security and privacy is ensured when designing digital public services. It is done by providing architecture building blocks that address these specific topics, and also by considering all LOST views, ensuring traceability from legal requirements to technical. To go further in detail, there are specific enablers related to identify the requirements for identity and access management, which are the building blocks that will ensure that access to data is controlled. Additionally, elements such Trust enablers or blockchain can be consider assets and components that can help to ensure data integrity and data authenticity. EIRA reference: https://interoperable-europe.ec.europa.eu/collection/european-interoperability-reference-architecture-eira /solution/eira/release/610 EIRA Github Repository: https://github.com/CarTool-EC/EIRA'
'As an extension of DCAT, DCAT-AP by allowing the description of catalogues and datasets, aggregated DCAT-AP metadata can serve as a manifest file as part of the digital preservation process. DCAT specification: https://www.w3.org/TR/vocab-dcat-2/ DCAT-AP Specification: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/dcat-application-profile-data-portals-europe/release/200"'
'The specification strongly encourages data publishers to read the section on Cross-Syntax Expression in the Strings on the Web: Language and Direction Metadata document to ensure that the expression of language and base direction information is possible across multiple expression syntaxes. Verifiable Credentials Internationalization Considerations: https://www.w3.org/TR/vc-data-model/#internationalization-considerations'
DCAT is included in the national catalogues of the Netherlands and Spain. Both Member States comply with at least 4 out of 5 sections of the EIF according to the NIFO factsheets. See: https://administracionelectronica.gob.es/pae_Home/dam/jcr:9e2c2877-5103-4934-8440-c60ba2e10c48/Catalogue_of_Standards_NIF_Spain.pdf https://www.forumstandaardisatie.nl/open-standaarden/lijst
ADMS is used as the basis for the ADMS-AP, which is the backbone of the European cross-border platform for the reuse of interoperability solutions Joinup. ADMS on Joinup: https://joinup.ec.europa.eu/solution/asset-description-metadata-schema-adms/about
'SAML 2.0 is not included in any catalogue of standards at supra-national level. SAML 2.0 Reference: http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-tech-overview-2.0.html'
DNS is a sector agnostic specification.
'One of the key features of the ESPD is the digital signature functionality, which provides a mechanism to verify that the document has not been tampered with, and that the information contained within it is authentic and accurate. The digital signature ensures that the data has not been modified or altered in transit, and that it is the same data that was originally sent. It is important to note that the e-signature functionality is something that is built on top of the ESPD model, and each Member State is responisble of implementing it on their respective procurement digital services platform. Commission Decision (EU, Euratom) 2017/46 of 10 January 2017 on the security of communication and information systems in the European Commission: https://eur-lex.europa.eu/legal-content/EN/TXT/?qid=1548093747090&uri=CELEX:32017D0046 ESPD business handbook: https://docs.ted.europa.eu/ESPD-EDM/latest/xml_business_handbook.html'
'The purpose of XML is to store, transport and exchange data through interoperable systems. Additionally, the specification provides the means to validate XML documents using XML schemas. XML Reference: https://www.w3.org/TR/xml/ Fog and Edge Computing in 5G’ ENISA report: https://www.enisa.europa.eu/publications/fog-and-edge-computing-in-5g '
'OData is a protocol of querying and sharing, and as such is not supposed to offer long-term preservation of data. Therefore, this criterion is considered not applicable to this specification. OData reference: https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html'
"LDAP can use SASL or simple bind for authentication. SASL is an extensible framework that can enhance security when accessing by binding requests and responses between the user and the server. If we try to access without permission, we may receive various errors. The most accurate way for anyone, whether they are in the server or external to the organisation, to authenticate is by following these steps. If the user is not a member of the server and attempts to bind, they will receive an error message stating either 'invalidCredentials' or 'noSuchObject'. If the user attempts to bind with incorrect credentials, they will receive an error message stating 'invalidCredentials'. LDAP Authentication methods and security mechanisms: https://www.rfc-editor.org/rfc/rfc4513.txt LDAP reference: https://ldap.com/the-ldap-bind-operation/ "
CAMSS Assessment of UTF-8 EIF Scenario v1.0.0
'ETSI TS 119 512 does not rely on any specific platform. ETSI TS 119 512 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.02_60/ts_119512v010102p.pdf'
The purpose of the specification is to facilitate the exchange of structured data. By allowing to make the data available to other persons or organisations, this Core Vocabulary reduces the administrative burden. CCCEV reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-criterion-and-core-evidence-vocabulary
'UTF-8 encoding can enable data processing accuracy by ensuring that characters from a wide range of scripts are correctly represented and processed. UTF-8 specification: https://datatracker.ietf.org/doc/html/rfc3629 '
"WAI-ARIA is not currently listed in its Information and Communication Technology (ICT) National Catalogue. Spain, as a Member State, recommends WAI-ARIA as an accessibility standard. This signifies Spain's recognition and endorsement of WAI-ARIA as a valuable framework for promoting web accessibility within the country. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards PAe Accessibility Standards reference: https://administracionelectronica.gob.es/pae_Home/pae_Estrategias/pae_Accesibilidad/pae_normativa/pae_eInclusion_Normas_Accesibilidad.html?idioma=en"
The Core Public Organisation Vocabulary facilitates the process for institutions publishing data about public organisations. This Core Vocabulary fosters interoperability and impacts positively on the development of eGovernment. CPOV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-organisation-vocabulary
'OpenTelemetry explicitly addresses and guarantees data accuracy through data sampling. The idea behind sampling is to control the spans sent to an observability backend, resulting in lower ingest costs. Different organisations will have their own reasons for not just why they want to sample, but also what they want to sample. Consequently, end-users can focus on interesting traces for them (e.g: frontend team may only want to see traces with specific user attributes). OTel Sampling: https://opentelemetry.io/docs/concepts/sampling/'
'XSLT specification ensures data processing accuracy through mechanisms like templates, which define rules for matching XML elements and applying transformations. In XSLT, functions and operators are type-safe, meaning data types are strictly managed. If incompatible types are used together (e.g., adding a string to a number), an error occurs, reducing the chances of inaccurate transformations XSLT Reference: https://www.w3.org/TR/xslt-30'
'ORDL can be mapped to the EIRA Library of Interoperability Specifications (ELIS). More specifically, ODRL is associated with the "European Legal Interoperability Agreeement", "Legal Agreement, "Legal Interoperability Agreement" and "National Legal Interoperability Agreement" ABBs from the Legal View, "Semantic Interoperability Agreement" ABBs from the Semantic View, "Technical Interoperability Agreement" ABBs from the Technical Application View. EIRA: https://joinup.ec.europa.eu/collection/european-interoperability-reference-architecture-eira/solution/eira/release/600 ELIS Solution: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis ELIS v6.0.0: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/600'
'The specification has a validation schema to test conformance. Also automated check rules can be implemented. https://www.xbrl.org/int/gl/2016-12-01/gl-framework-2017-PWD-2016-12-01.html'
'After searching in the different official European websites and repositories, there is no evidence that ISAE 3402 is included in an open repository/catalogue of standards at a national level. CAMSS list of standards reference: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards'
"DCAT-AP can contribute to the delivery of European public services by facilitating the discovery and access to data services provided by public administrations and by supporting the implementation of the European Union's digital single market strategy. DCAT-AP Specification: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/dcat-application-profile-data-portals-europe/release/200 "
'The main purpose of the specification is about Testing the Conformance and Interoperability of Trusted Lists, so in each one of the test that are performed in the specification, conformance is assessed. ETSI TS 119 614-1 reference: https://www.etsi.org/deliver/etsi_ts/119600_119699/11961401/01.01.01_60/ts_11961401v010101p.pdf'
The W3C Royalty-Free IPR licenses granted under the W3C Patent Policy apply to all W3C specifications, including SOAP 1.2. See: https://www.w3.org/TR/patent-practice#ref-AC
'ISO 639-2 cannot be changed, and therefore does not allow customisation. ISO 639-2 reference: https://www.loc.gov/standards/iso639-2/'
'The Joinup platform holds several discussion forums about the implementation and usage of UTF-8. UTF-8 discussion forums in Joinup: https://joinup.ec.europa.eu/search?keys=utf-8&sort_by=relevance&f%5B0%5D=type%3Adiscussion'
"By adhering to the E-ARK CSIP's metadata guidelines, organizations can enhance the portability of their data by ensuring that relevant information about the data is included in the information packages. E-ARK CSIP specification: https://earkcsip.dilcis.eu/#introduction"
'Taking the initial purpose of the specification, it can be considered that the specification is involved in fostering the comprehensibility of Public Administrations data, as well as relevant data produced for the decision-making process. EuroVoc: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource /dataset/eurovoc'
'Through the recommendation of the use of open standards and interoperability principles, TGF enables the exposure of interfaces, as it gives guidance and promotes best practices, such as the development of APIs to provide access to government services and data or the Service-Oriented Architecture (SOA) principles, which enable the development of modular and reusable services that can be easily integrated into other systems and platforms. TGF specification: http://docs.oasis-open.org/tgf/TGF/v2.0/cs01/TGF-v2.0-cs01.html'
'Being an international standard that encompasses the internal security framework of all private and public administrations, ISO/IEC 27001 helps to create digitally by default services that reduce the administrative burden on both sides, public administrations and stakeholders. ISO/IEC 27001 reference website: https://www.iso.org/standard/54534.html'
'Cryptographic algorithms are the basis of e-signatures encryption. ETSI TS 119 512 is furthermore developed for trust service providers for the storing and retrieval of information and data that require a high degree of security in their processing and exchange. ETSI TS 119 512 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.02_60/ts_119512v010102p.pdf'
'ETSI EN 319 532-3 has the support of various communities listed in the following link as "Supporting Organizations", including Universities, private and public companies. Portal ETSI reference: https://portal.etsi.org/webapp/workprogram/Report_WorkItem.asp?WKI_ID=56725'
'DCAT-AP is included in the national catalogue of Belgium, Denmark, Sweden and Malta. The National Interoperability Framework of these countries is aligned with al least 2 out of 3 sections of the EIF according to NIFO factsheets. NIFO factsheets: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public-administration-factsheets-2022 Belgium National Catalogue: https://www.belgif.be/page/specifications.en.html'
"ODRL does not dictate the use of specific communication protocols. For secure data processing, especially during data exchange, it's important to implement secure communication protocols, such as HTTPS, to protect data in transit. W3C specification reference: https://www.w3.org/TR/odrl-vocab/#vocab-core"
LegalRuleML is aimed to define a common data and metadata model towards the maximisation of information reuse. It provides a set of requirements and aspects that foster modelling data supporting data exchange and semantics. LegalRuleML reference: http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/legalruleml-core-spec-v1.0.html
'XSLT is not a European standard. The specification was developed by the W3C as part of its work on XML technologies, which are used worldwide for web and data interoperability. XSLT W3C Homepage: https://www.w3.org/community/xslt-40/'
'The TGF does not assume any particular language or script and is designed to be language- and script-neutral. This means that it can be applied in any linguistic or cultural context, and can be adapted to support multilingual content and user interfaces. TGF specification: http://docs.oasis-open.org/tgf/TGF/v2.0/cs01/TGF-v2.0-cs01.html'
HTML5 is one of the main pillars for Open Web Platform, a full programming environment for cross-platform applications with access to device capabilities; video and animations; graphics; style, typography, and other tools for digital publishing; extensive network capabilities, among others. Moreover, developers can have stability in to implement and plan through HTML5. See: https://www.w3.org/2012/12/html5-cr.html.en
'The Core Location Vocabulary specification significantly facilitates organisational interoperability agreements by providing a standardised framework for describing location data. This standardisation ensures that different organisations can seamlessly exchange and understand location information, reducing semantic conflicts and enhancing collaboration. Core Location Vocabulary: https://interoperable-europe.ec.europa.eu/collection/semic-support-centre/solution/core-location-vocabulary/release/100'
'YAML can be used to document the steps involved in administrative procedures in a structured way. By breaking down procedures into hierarchical tasks, it can improve clarity. Moreover, YAML can help listing rules and services. YAML specification: https://yaml.org/spec/1.2.2/'
'The purpose of YAML is not related to ensure the protection of personal data managed by Public Administrations. Therefore, this criterion is considered not applicable to this specification. YAML specification: https://yaml.org/spec/1.2.2/'
'ETSI ES 119 612 has the support of various communities listed in the following link as "Supporting Organizations", including universities, private and public companies. The ESI technical committee provides public support to members and non-members alike, with different conditions depending on ETSI membership status. This support helps to increase the use of the specification and the specification itself by detecting weaknesses in implementation or any other relevant aspect of the specification's functionalities. ETSI oranisation: https://www.etsi.org/about'
Ogg is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, Ogg can define the interoperability aspects of the "Representation" ABB of the EIRA Semantic View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/solution/elis/release/v100
After carrying out information retrieval, no document or study has been found assessing the TIFF/IT in terms of efficiency or effectiveness.
'The specification is place in the very beginning of the Digital Public Service Life-cycle, specifically in the analysis where requirements are set. At this stage, the solution includes and remarks the need for the Organisational Agreements and the Organisational Interoperability Agreements. The Organisational includes a set of relevant aspects and agreements that are key to ensure interoperability at organisational level, these building blocks are, for instance, agreements on privacy, agreements on reuse of infrastructure, agreement on data sharing amongst others. By providing this granularity, the EIRA helps public administrations on the process of defining solutions and the organisational agreements that will need to be put in place. EIRA reference: https://interoperable-europe.ec.europa.eu/collection/european-interoperability-reference-architecture-eira /solution/eira/release/610 EIRA Github Repository: https://github.com/CarTool-EC/EIRA'
'Registered Organization Vocabulary does not enable the long-term preservation of data/information/knowledge (electronic records included). The main purpose of the specification is to define a standardised way of describing organisations that have gained legal entity status through a formal registration process. Therefore, this criterion is considered not applicable to this specification. Registered Organization Vocabulary reference: https://www.w3.org/TR/vocab-regorg/'
'The ETSI and any of its committees, in charge of the development of ETSI TS 119 612, operates under the ETSI Intellectual Property Rigths (IPRs) and IPR Policy. The specification is licensed on a (F)RAND basis. ETSI ownership of IPRs section: https://www.etsi.org/intellectual-property-rights'
'There are platforms to share results and information about IPv6. The IPv6 Forum is a world-wide consortium of worldwide leading Internet vendors, Industry Subject Matter Experts, Research & Education Networks, with a clear mission to advocate IPv6 by dramatically improving technology, market, and deployment user and industry awareness of IPv6. "IPv6 Forum" reference: https://ipv6forum.com/?module=News&type=user&func=display&sid=9'
HTTPS is maintained by IETF which is an international community developing open standards. See: https://www.ietf.org/about/
HTTP allows the access to websites providing information on administrative rules, procedures and services.
'The specification has been updated to its third version, introducing several improvements in functionality. As a result, it is now regarded as one of the most valuable tools for managing data and facilitating easier access. For example, IndexedDB is employed in projects such as Health360 to store data, enhancing both data integrity and availability. Moreover, IndexedDB also complies with the GDPR framework, addressing security concerns related to the processing of personal data. Indexed Database API: https://www.w3.org/TR/IndexedDB/ Health360 project GDPR: https://www.mdpi.com/2076-3417/12/17/8441'
"The XFDL specification supports data processing accuracy by providing a structured, standardised format for forms, which minimises data entry errors. It ensures the integrity of the data through digital signatures, confirming that the data hasn't been tampered with after submission. This aligns with the XML Signature Syntax and Processing specification, which outlines how digital signatures can be applied to XML data to guarantee its integrity and authenticity, offering a reliable method for verifying that the data remains unchanged throughout the processing cycle. XML Signature Syntax and Processing reference: https://www.w3.org/TR/xmldsig-core1/ XFDL security reference: https://www.w3.org/TR/NOTE-XFDL#button"
The purpose of Xforms is not related to the implementation of the once-only principle. Therefore, this criterion does not apply to this specification. Xforms 2.0 W3C reference: https://www.w3.org/community/xformsusers/wiki/XForms_2.0
'XML can be used independently from any other technical specifications or operating system. See: https://www.w3.org/TR/2006/REC-xml11-20060816/ '
'The Advanced Encryption Standard can be found in the VeraCrypt project. VeraCrypt encrypts partitions or storage devices, including those where Windows is installed. In this sense, encryption is automatic and fast, with hidden volumes for plausible deniability. VeraCrypt AES project: https://veracrypt.eu/en/Home.html AES Standard Reference: https://csrc.nist.gov/pubs/fips/197/final'
'The purpose of SHACL is not related to the publication of public data as open data. Therefore this criterion is not applicable to the specification. SHACL W3C reference: https://www.w3.org/TR/shacl/'
'According to the 5 star Open Data model suggested by Tim Berners-Lee about how to publish linked data, DPV is a vocabulary enabling information systems to query data in a structured manner. As well as supporting the publication of data as open data, the specification facilitates the publication of public data (under the user consent) as open data since it fulfils all the requirements to generate Linked Data. DPV specification: https://w3c.github.io/dpv/dpv/ Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/en/ '
After being evaluated compliant with the regulation on standardisation 1025/2012, LDAPv3 has been identified by Commission Implementing Decision. During the evaluation process, all the Member States are invited to share their doubts. The positive evaluation of LDAPv3 and its identification is considered an interoperability agreement. ICT technical specifications: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en
'After checking the different standard catalogues at supra-national level, there is no mention of ISO 3166-1 in any official document stating its conformance in regards to Regulation 1025/2012. ICT technical specifications: https://ec.europa.eu/growth/single-market/european-standards/ict-standardisation/ict-technicalspecifications_en CENELEC and CEN search tool catalogue: https://standards.cencenelec.eu/dyn/www/f?p=CEN:105::RESET::::'
'The inclusion of JSON processing in XSLT is crucial for data portability. JSON being a common data exchange format, the ability to transform between XML and JSON directly using XSLT increases its utility across different environments (see Section 22). XSLT Reference: https://www.w3.org/TR/xslt-30/#json'
'All solutions developed in ISA² Programme are under ISA Open Metadata Licence which is perpetual, royalty-free and non-exclusive license to Use and re-Use the Works. ISA open metadata license: https://joinup.ec.europa.eu/licence/isa-open-metadata-licence-v11 '
'The ETSI and any of its committees, in charge of the development of NFVI, operates under the ETSI Intellectual Property Rigths (IPRs) and IPR Policy. The specification is licensed on a (F)RAND basis. Intellectual Property Rights Policy, ETSI ownership of IPRs section: https://www.etsi.org/intellectual-property-rights'
The purpose of XML is not related to the long-term preservation of electronic records and other kinds of information. Therefore, this criterion is not applicable to the specification.
CSS v2.1 is included in 3 national catalogues of recommended specifications. They belong to the Netherlands, Spain and Sweden. The National Interoperability Framework (NIF) of these Member States is fully aligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. National catalogue the Netherlands: https://www.forumstandaardisatie.nl/open-standaarden National catalogue Spain: https://administracionelectronica.gob.es/pae_Home/pae_Estrategias/pae_Interoperabilidad_Inicio/pae_Normas_tecnicas_de_interoperabilidad.html#CATALOGOESTANDARES National catalogue Sweden: https://www.avropa.se/globalassets/dokument/open-it-standards.pdf?_t_id=1B2M2Y8AsgTpgAmY7PhCfg%3d%3d&_t_q=standards&_t_tags=language%3asv%2csiteid%3a95d515a5-23ca-47bf-87a9-07b10d8ac360&_t_ip=178.139.72.144&_t_hit.id=Avropa_Core_Models_Media_GenericMedia/_ff07d720-f793-44b0-994d-27e79b28f6bd&_t_hit.pos=7 NIFO factsheets: https://joinup.ec.europa.eu/collection/national-interoperability-framework-observatory-nifo/nifo-factsheets
The Registered Organization Vocabulary which was developed by ISA2, and later it was standardised by W3C, has support from both organisations. It is worth to note that both organisations aim to enhance the ICT environment in private and public business. W3C Community: https://www.w3.org/Consortium/ RegOrg Joinup reference: https://joinup.ec.europa.eu/solution/registered-organization-vocabulary
'The Better Regulation Guidelines and Toolbox in its essence aims to provide a road-map for the construction of global, coherent and fair policies and laws. In several of the tools proposed within the specification, multilingualism is considered as part of the requirements that ICT platforms developed for public services need to comply with and ensure. Therefore, the Better Regulation Guidelines and Toolbox fosters the creation of policies and laws according the multilingualism context of European citizenship. Better Regulation Guidelines and Toolbox reference: https://commission.europa.eu/law/law-making-process/better-regulation/better-regulation-guidelines-and-toolbox_en Better Regulation Toolbox reference: https://commission.europa.eu/document/download/9c8d2189-8abd-4f29-84e9-abc843cc68e0_en?filename=BR%20toolbox%20-%20Jul%202023%20-%20FINAL.pdf'
The specification is available for its use and implementation at the OASIS's webpage. The specification: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505009
'The iCalendar specification has support from many communities, notably iCalendar.org, which is a site devoted to the promotion of the standard, as well as offering resources and validation tools. iCalendar.org: https://icalendar.org/Home.html iCalendar specification: https://www.rfc-editor.org/rfc/rfc5545'
One of the main purposes of the specification and the OASIS TC in charge of its development is to be extensible, moreover, the specification aims to propose a set of requirements that allow the modelling of legal resources and their exchange. It can help users to provide their specific semantic rules or adapt the xml representation to specific needs following the specification requirements. Therefore, it can be applied or implemented without sacrificing interoperability with other systems. LegalRuleML reference: http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/legalruleml-core-spec-v1.0.html
The purpose of SAMM is not related to the comprehensibility of administrative information, data or services. Therefore, this criterion is not applicable to this specification. SAMM webpage: https://owaspsamm.org/ SAMM documentation: https://github.com/OWASP/samm/blob/master/Supporting%20Resources/v2.0/OWASP-SAMM-v2.0.pdf
'DPV has not been found to be included in any open repository or catalogue of standards at national level. DPV specification: https://w3c.github.io/dpv/primer/'
'REST has been included in the catalogue of Finland and Slovakia. The National Interoperability Framework (NIF) of these Member States is fully aligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. National catalogue of Finland: https://joinup.ec.europa.eu/sites/default/files/inline-files/Finland%20Factsheet%20Validated.pdf National catalogue of Slovakia: https://joinup.ec.europa.eu/sites/default/files/inline-files/NIFO%20-%20Factsheet%20Slovakia_2016_v1_0.pdf NIFO factsheets: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public-administration-factsheets-2021'
'While the BFO is an upper level ontology that is designed for being used in supporting information retrieval, analysis and integration in scientific and other domains, currently there is no sharing of data among users due to the wide variety of applications. BFO is the core element of the European Materials Modeling Ontology (EMMO) used to organise the top level ontology that leads to a better integration of business processes related to material processing. https://emmo-repo.github.io/ BFO reference: https://www.iso.org/standard/74572.html'
The purpose of TLS 1.2 is not related to the definition of a data model. Therefore this criterion is not applicable to this specification. See: https://tools.ietf.org/html/rfc959
'XHTML supports XML namespaces, which allow users to use elements from different vocabularies within the same document and has strict syntax that prevents the user from customising their product. In this sense, HTML5 offers a larger set of possibilities when creating web interfaces. XHTML W3C reference: https://www.w3.org/TR/xhtml1/#well-formed'
'The ITPE conducts conferences and webinars within various communities using the specification to give a voice to anyone who wants to give their opinion on the EN 16234-1 e-CF specification, including national participation. IT Professionalism Europe (ITPE) reference, Events: https://itprofessionalism.org/events/'
'After searching the different national catalogues, there has not been found any European Member State recommending ETSI TS 119 612. ETSI TS 119 612 specification: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf'
'GraphQL is a generic and flexible engine that defines a schema syntax, query syntax, and a query execution reference for centralised databases. It is therefore domain-agnostic and is designed to be used in any domain. GraphQL specification: https://spec.graphql.org/October2021/#sec-Overview'
"NUTS introduced the ISO 2-letter codes in 1999, a specification designating country codes (for example, BE3 for the Walloon region in Belgium, where BE corresponds to the ISO-2 letter code of Belgium) (see EUROSTAT reference, History of NUTS section, 'NUTS 1981 - MUTS 1999' document). However, the NUTS classification is not dependent on the ISO 2 specification, and the UK code ('UK') is a clear counterexample to the ISO standard ('GB' according to ISO 2). Therefore, NUTS is technology-agnostic. EUROSTAT reference, History of NUTS section, 'NUTS 1981 - MUTS 1999' document: https://ec.europa.eu/eurostat/web/nuts/history EUROSTAT reference, NUTS Principles and Characteristics section: https://ec.europa.eu/eurostat/web/nuts/principles-and-characteristics"
Although HTML is aligned with the first levels of maturity of Tim Berners-Lee's 5-star schema for Open Data, it does not support the different principles of Linked Open Data. HTML W3C reference: https://www.w3.org/TR/html401/ 5-star linked open data: https://www.w3.org/DesignIssues/LinkedData.html https://www.w3.org/wiki/LinkedData
"All specifications developed by the Publication's office of the EU are royalty-free and its IPR policies are alligned with the FRAND principles. Publications Office of the EU IPR: https://op.europa.eu/en/web/about-us/legal-notices/publications-office-of-the-european-union-copyright"
The specification is included in 10 Member States' catalogues of recommended specifications. They belong to the Croatia, Estonia, France, Germany, Malta, Netherlands, Norway, Poland, Spain and Sweden. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
The specification is maintained and developed by the CEF eDelivery Team and all the information related to the specification and its implementation can be found at CEF’s webpage. See: https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery+SMP+-+1.10
'While the OGC TrainingDML-AI Standard does not directly model business processes, its contribution to standardizing geospatial training data for AI/ML applications indirectly supports more efficient, reliable, and collaborative business processes within organizations that depend on geospatial analysis and AI/ML technologies. OGC TrainingDML-AI: https://www.ogc.org/standard/trainingdml-ai/'
'Dataspaces provide a way to integrate heterogeneous data from multiple sources. In many organisations, data is often scattered across different databases, systems, and formats. Dataspaces help create a unified view of this distributed data, enabling more effective analysis and decision-making. By integrating data, sharing and collaboration is easier. This can improve communication and data portability. IDSA Dataspace Protocol Specification: https://docs.internationaldataspaces.org/ids-knowledgebase/v/dataspace-protocol/overview/readme'
'The header parameter of the CSV specification indicates the presence or absence of the header line. Some valid values for this header are "present" or "absent", which can enable data processing accuracy. CSV reference: https://datatracker.ietf.org/doc/html/rfc4180'
'The specification foresees that it can be implemented separately. Being a reference model based on layers, it offers the users the possibility to work with any amount of layers. This can be seen on the Microsoft implementation, where only 5 of the 7 layers are in use. Microsoft and OSI: https://learn.microsoft.com/en-us/windows-hardware/drivers/network/windows-network-architecture-and-the-osi-model OSI reference https://www.iso.org/standard/20269.html'
'The ETSI and any of its committees, in charge of the development of ETSI EN 319 532-3, operate under the ETSI Intellectual Property Rights (IPRs) and IPR Policy. The specification is licensed on a Royalty-free basis. Intellectual Property Rights Policy, ETSI ownership of IPRs section: https://www.etsi.org/intellectual-property-rights'
'In accordance with ISO/IEC JTC 1 and the ISO and IEC Councils, these International Standards are publicly available for Standardization purposes. Publicly Available Standards: https://standards.iso.org/ittf/PubliclyAvailableStandards/index.html'
'HTTP specification allows customisation for flexibility to accommodate diverse use cases and evolving technologies. HTTP relies on a set of "methods" to indicate the intended action to be performed on a resource. HTTP /1.1 RFC 2616 Reference: https://www.rfc-editor.org/rfc/rfc2616.html HTTP/1.1 Semantics, RFC 7231 Reference: https://www.rfc-editor.org/rfc/rfc7231'
'Different existing reports point out the benefits of implementing ISAE 3402 in terms of efficiency. An example of such assessment can be found in the following link. Report on ISAE 3402: https://isae3402.co.uk/sites/default/files/Whitepaper_ISAE_3402.pdf'
'BFO is currently only available in English and Portuguese. BFO reference: https://www.iso.org/standard/74572.html Portuguese version: https://mba.eci.ufmg.br/legal/bfo-pt'
'After searching through different catalogues, no evidence of the Indexed Database API being included in the catalogue of any Member State was found. Indexed Database API: https://www.w3.org/TR/IndexedDB/'
'By providing a standardised way to validate RDF (Resource Description Framework) graphs, SHACL ensures that data conforms to specific shapes and constraints, making it easier to share and integrate data across different systems and platforms. SHACL W3C reference: https://www.w3.org/TR/shacl/'
'Customisation is an important part of the GraphQL functionalities. For instance, in order to introduce additional semantic meaning, the specification supports the addition of custom scalars, or even to define custom directives beyond those provided by the specification. GraphQL custom scalars: https://spec.graphql.org/October2021/#sec-Scalars.Custom-Scalars GraphQL Custom directives: https://spec.graphql.org/October2021/#sec-Type-System.Directives.Custom-Directives'
'Web Services Description Language (WSDL) itself primarily focuses on describing the interfaces and operations of web services, and it does not provide specific mechanisms for ensuring the secure processing of data. Security considerations, including secure processing, are typically addressed at other layers of the web services architecture and are influenced by the implementation choices made by service providers and consumers. W3C WSDL specification: https://www.w3.org/TR/wsdl20/'
'SOAP 1.2 is a sector domain agnostic specification that can be used independently from the business domain. SOAP Reference: https://www.w3.org/TR/soap12/ '
'The purpose of the GITB TDL is not related to long term preservation of electronic record. Therefore, this criterion is considered not applicable to this specifcation. GITB TDL reference: https://www.itb.ec.europa.eu/docs/tdl/latest/introduction/index.html#introduction'
'OData queries and shares data accross different systems via RESTful interfaces. RESTful APIs may be platform-agnostic, without any dependency on the environment or programming language being used; however, this use case is not always applied. Therefore, the specification is not platform-agnostic. OData reference: http://docs.oasis-open.org/odata/odata/v4.0/odata-v4.0-part1-protocol.html RESTful reference, Use cases section: https://restfulapi.io/'
'Although it is mostly suited for public administrations, ETSI TS 119 512 protocols can be implemented in any business domain. For example, the specification uses different preservation schemes that build the so called preservation profiles (see eIDAS reference). ETSI TS 119 511 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119511/01.01.01_60/ts_119511v010101p.pdf eIDAS blog, New APIs for the eIDAS-Ecosystem: https://blog.eid.as/tag/etsi-ts-119-512-en/'
'REM provides an e-mail service and security controls and mechanisms to protect transactions. Also REM Signature enables the secure exchange of data between both parts. ETSI EN 319 532-3 reference, section 6.2.7: https://www.etsi.org/deliver/etsi_en/319500_319599/31953203/01.02.01_60/en_31953203v010201p.pdf'
'ISO/IEC 27001 is included in the Catalogue of standards of Norway. Norway catalogue of standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
'The purpose of DCAT-AP is not related to the modelling of business processes, therefore, this criterion is not applicable to the specification. DCAT-AP Specification: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/dcat-application-profile-data-portals-europe/release/200'
"There are some assessment evaluating the specification's digital solution effectiveness and efficiency which involve SMP2.0. OOTS eDelivery Access Point Reference: https://ec.europa.eu/digital-building-blocks/wikis/pages/viewpage.action?pageId=647955048"
'The specification is focused on testing implementation of Trusted List according to ETSI TS 119 612. ETSI TS 119 614-1 reference: https://www.etsi.org/deliver/etsi_ts/119600_119699/11961401/01.01.01_60/ts_11961401v010101p.pdf'
'As part of the ""IP Stack"", IPsec has been selected by several public administrations for secure data exchange over the internet. By allowing the secure exchange of data, the specification fosters the visibility of data across borders. An example of its implementation is the TESTA project, which provides a secure cross-border data communication network service for public administrations. Interoperable Delivery of European Egovernment Services to Public Administrations, Businesses and Citizens (IDABC) Reference Link: https://ec.europa.eu/idabc/en/document/2097.html TESTA Service: https://ec.europa.eu/isa2/solutions/testa_en'
'DCAT is not a European Standard in the sense of a formal standard developed and recognized by the European standards organisations. DCAT (v2.0.0) reference: https://www.w3.org/TR/vocab-dcat-2/ '
'A significant amount of the data collected never gets leveraged because of the challenges in interpreting data models and API standards for utilizing the data across platforms. This specification enables close to real-time (right-time) access to context/digital twin information coming from many different sources (not only IoT data sources), thus scoping comprehensibly administrative procedures, rules data, and services. GS CIM 009: https://www.etsi.org/deliver/etsi_gs/CIM/001_099/009/01.07.01_60/gs_CIM009v010701p.pdf'
As defined on the TC standardisation, only TC members are involved in the development of ISO standards. A review is carried out to arrange the consensus firstly within the TC members and subsequently is reviewed by the different ISO member bodies. However, it cannot be considered a public review, because only TC members can participate. The ISO standardization process: https://www.iso.org/stages-and-resources-for-standards-development.html
The specification is a key enabler for the metadata exchange. It is part of the eDelivery Building Block defined by CEF, which aims to foster data exchange and reuse across borders enhancing the interoperability in Europe. Moreover, eDelivery SMP 1.10 helps in the decision-making process by allowing data exchange between administrations. See: https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/Benefits+of+eDelivery
'SHACL can significantly enhance policy-based access control systems by defining precise rules for data access and modification. These rules can be specifically designed to protect personal data managed by public administrations, ensuring that only authorised personnel can access or alter this sensitive information. By implementing stringent access control policies, SHACL helps mitigate the risk of unauthorised access and data breaches. In addition SHACL can implement access control mechanisms to regulate data access, using SHACL-ACL, thereby enhancing security. "SHACL-ACL: Access Control with SHACL" study: https://link.springer.com/chapter/10.1007/978-3-031-43458-7_4 SHACL W3C reference: https://www.w3.org/TR/shacl/'
No up to date mechanism to assess the IPsec conformity has been found. The existing conformity tests provided in the past by the IETF IPSec working group are outdated. See: https://tools.ietf.org/html/draft-hoffman-ipsec-testing-01
'The SFIA Foundation intends to align the SFIA specification with different models and frameworks. At present, there are some workgroups that prove this trend, for example through the development of the EU ICT Role Profiles (see SFIA reference, Tools and resources section, Standard skills profiles subsection, European Union-EU ICT Role Profiles, CEN/CENELEC Workshop Agreements (CWA) 16458-1:2018 European ICT Professional Role Profiles – Part 1: 30 ICT). However, there is no explicit provisions to achieve this end. SFIA reference, Tools and resources section, Standard skills profiles subsection, European Union-EU ICT Role Profiles, CEN/CENELEC Workshop Agreements (CWA) 16458-1:2018 European ICT Professional Role Profiles – Part 1: 30 ICT: https://sfia-online.org/en/tools-and-resources/standard-industry-skills-profiles/european-union/eu-ict-role-profiles'
The rules on European standardisation allow the European Commission to identify information and communication technology (ICT) technical specifications - that are not national, European or international standards - to be eligible for referencing in public procurement. This allows public authorities to make use of the full range of specifications when buying IT hardware, software and services, allowing for more competition in the field and reducing the risk of lock-in to proprietary systems. After being evaluated compliant with the regulation on standardisation 1025/2012, HTTPS has been identified by Commission Implementing Decision and included in the European list of ICT Standards for e-procurement. See: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en
'MIME extends the format of email messages to support text in ASCII and non-ASCII characters, as well as attachments of audio, video, images, and application programs. MIME specification: https://tools.ietf.org/html/rfc2045'
'CPSV-AP is a reusable and extensible data model for harmonising the way public services are described in a machine-readable format. So it describes the public administrations and eases their visualisation and comprehensibility. CPSV-AP Joinup webpage: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/core-public-service-vocabulary-application-profile/release/22'
'The purpose of the specification is not related to business process modelling, therefore this criterion does not apply to this specification. W3C specification reference: https://www.w3.org/TR/odrl-vocab/#vocab-core'
'WAI-ARIA is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, WAI-ARIA can define the interoperability aspects of the Human Interface ABB of the EIRA Technical View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/v110'
Like all the IETF standards, IPv6 is a free and open technical specification, built on IETF standards and licenses from the Open Web Foundation. IPv6 is therefore licensed on a royalty-free basis. No IPR disclosures have been submitted directly on the IPv6 specification (RFC 2818). See: https://tools.ietf.org/html/rfc3668
OpenPM2 can be found for free in several European websites, for instance joinup, the European Open Data Portal, or the Publications Office website. OpenPM2 specification reference: https://op.europa.eu/en/publication-detail/-/publication/ac3e118a-cb6e-11e8-9424-01aa75ed71a1/language-en/format-PDF/source-83307127 OpenPM2 Joinup: https://joinup.ec.europa.eu/collection/open-pm2-project-management-methodology
"ebXML provides a set of components enabling users (data users) to store and work with any type of electronic content, fostering the comprehensibility of administrations' rules and processes. When combined with other specifications, ebXML can enable the exposure of interfaces. For example, the specification in combination with the ebXML Business Process Specification (ebXML CCTS ISO/TS 15000-5:2005) fosters interoperability between eForms and ESPD services (see ESPD-EDM UBL adoption reference). ebXML reference, Conformance section: http://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html#__RefHeading__53396_365468741 ESPD-EDM UBL Codes and identifiers reference: https://docs.ted.europa.eu/ESPD-EDM/3.0.1/xml_technical_handbook.html#_compulsory_attributes"
'Schema.org is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, schema.org can define the interoperability aspects of the Ontologies Catalogue ABB of the EIRA Semantic View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/v110'
'IEEE Std 802.3-2022 focuses on the technical specifications for Ethernet and does not specifically address privacy aspects. However, any implementation of Ethernet technology must comply with broader privacy regulations and standards in the EU, such as the General Data Protection Regulation (GDPR). Additionally, the ICT Rolling Plans do recommend the use of Ethernet due to its widespread adoption, reliability, and performance. These plans help guide the development and deployment of ICT infrastructures across Europe, ensuring they meet current and future needs. Rolling Plan for ICT standardisation: https://joinup.ec.europa.eu/collection/rolling-plan-ict-standardisation GDPR Regulation Reference: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=celex%3A32016R0679 IEEE Std 802.3-2022 Reference: https://ieeexplore.ieee.org/document/9844436'
'EIRA includes mechanism to ensure that security and privacy is ensured when designing digital public services. It is done by providing architecture building blocks and organising them as viewpoints that address these specific topics, and also by considering all LOST views, ensuring traceability from legal requirements to technical. To go further in detail, there are specific enablers related to identify the requirements for identity and access management, which are the building blocks that will ensure that access to data is controlled. EIRA reference: https://interoperable-europe.ec.europa.eu/collection/european-interoperability-reference-architecture-eira /solution/eira/release/610 EIRA Github Repository: https://github.com/CarTool-EC/EIRA'
The purpose of the specification is not related to foster the availability and comprehensibility of public administrations services or making-decision process.
'The Registered Organization Vocabulary facilitates the publication of data on the web by providing a structured vocabulary for describing organisations that have gained legal entity status through formal registration. Registered Organization Vocabulary reference: https://www.w3.org/TR/vocab-regorg/'
Even though SVG is supporting the first level of maturity from the Tim Berners-Lee 5-star schema for the Open data, it is not supporting the main principles for the publication of data as Linked Open Data. W3C Linked Data: https://www.w3.org/wiki/LinkedData 5 Stars sc: https://5stardata.info/en/
'The specification can be deployed in any operating system, thus the IPsec specification is platform agnostic. IPSec reference: https://www.rfc-editor.org/rfc/rfc6071.html'
'The Genericode specification can contribute to data portability between systems and applications. Genericode can be aligned with other European standards and initiatives related to data interoperability and portability. By adopting genericode as part of a broader strategy for standardising data formats and structures, European public services can ensure consistency, compatibility, and portability of data across different systems and organizations. Code List Representation (genericode): https://docs.oasis-open.org/codelist/genericode/v1.0/os/genericode-v1.0-os.html'
'AMQP specification does not guarantee protection against unauthorized changes. Therefore, this criterion is not applicable to this specification. OASIS AMQP Reference: http://docs.oasis-open.org/amqp/core/v1.0/amqp-core-complete-v1.0.pdf'
"The specification is associated with EIRA ABB's in the EIRA Library of Interoperability Specifications (ELIS). It is associated with API Catalogue Component, API Discovery And Catalogue Service, Data Publication Component, Data Publication Service, Metadata Management Component, Metadata Management Service, Shared Platform from the Technical View, and the Controlled Vocabulary Data, Data Model, Data Syntax, Forms Structure, Hash Code, Metadata, Ontology, Semantic Interoperability Agreement from Semantic View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/v501"
'The publiccode.yml specification does not address data processing accuracy, nor does it include mechanisms to ensure data completeness and correctness. Its purpose is solely to document metadata for public code projects, and it lacks provisions for controlling or validating data accuracy during entry or dissemination. Therefore, it does not align with the data accuracy requirements referenced in EIF Recommendation 15. Publiccode.yaml documentation: https://docs.italia.it/italia/developers-italia/publiccodeyml-en/en/master/index.html'
'According to the 5 star Open Data model suggested by Tim Berners-Lee about how to publish linked data, the second star corresponds to make data available as structured data, an area of application of SOAP 1.2. In addition, SOAP 1.2 serialisation provides several advantages, especially if the Semantic Web is not just about providing meta data for existing web pages, but also about exchange of content that is machine-readable. Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/en/ RDF vs SOAP Paper Reference: https://pdfs.semanticscholar.org/dbf2/6496e5b3087b708d4c00883c6470b53ff8d8.pdf'
The information on (new) standardisation activities is widely announced via the IETF websites and working group activities. There also is a mailing list one can subscribe to for announcements. This so-called IETF Announce list receives announcements about IETF meetings, the activities and actions of the IESG, the RFC Editor, the NomCom, and other announcements of interest to the IETF community._x000D_ See:_x000D_ https://www.ietf.org/how/lists/announcement/
'DQV is mentioned in Data quality in an e-Government perspective, from Norwegian Digitalistation Agency. In order to evaluate if a dataset is reusable, it is proposed descriptions of data quality. To establish standards/specifications for machine-readable description of quality of datasets it is suggested to extend DCAT-AP-NO with W3C/DQV (Data Quality Vocabulary). Norwegian Digitalistation Agency: https://eurogeographics.org/app/uploads/2019/06/6-SDQ2020-Data-quality-in-an-e-Government-perspective.pdf'
'Although the Advanced Encryption Standard is designed to encrypt and securely store data, it is not related to the long-term preservation of electronic resources. AES Standard Reference: https://csrc.nist.gov/pubs/fips/197/final'
As protocol for data exchange, FTP can be used for the exchange of documents solving administrative burden. Additionally, it can avoid the exchange of non-digital documents that are generally source of administrative burden. See: https://tools.ietf.org/html/rfc959
Xforms 2.0 is maintained by W3C which is an international community developing open standards. Developer community W3C: https://www.w3.org/Consortium/
The OASIS TC in charge of LegalRuleML operates under the Royalty Free on Limited Terms IPR mode as defined in the OASIS Intellectual Property Rights (IPR) Policy. LegalRuleML reference: http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/legalruleml-core-spec-v1.0.html
'ETSI TS 119 512 allows time-stamp authority to be used. Typically, a time-stamp authority includes mechanisms to authenticate people who wants access to timestamped information. Thus, using time-stamp authority, it is possible to implement authenticity mechanisms to access shared information between organisations, for example. ETSI TS 119 512: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.01_60/ts_119512v010101p.pdf'
LegalDocML has no requirement recognizing and executing the content on the receiving end. The receiving agents must ignore executable content coming from unsecured channels and/or unknown sources. However, the specification is XML based and it provides a set of common elements that are used to validate the information and the structure of the information exchange. This fact contributes to the trustworthy data exchange between parties. LegalDocML reference: https://www.oasis-open.org/committees/legaldocml/charter.php Akoma Ntoso Media Type Version 1.0: http://docs.oasis-open.org/legaldocml/akn-media/v1.0/csprd01/akn-media-v1.0-csprd01.html#_Toc417907373
'DCAT is recommended by five states, some one those are the Netherlands and Spain, which includes DCAT in their national catalogues of recommended specifications. Netherlands National Catalogue Reference: https://www.forumstandaardisatie.nl/open-standaarden/lijst Spanish National Catalogue Reference: https://administracionelectronica.gob.es/pae_Home/dam/jcr:9e2c2877-5103-4934-8440-c60ba2e10c48/Catalogue_of_Standards_NIF_Spain.pdf '
The Standard for Public Code gives public organizations a model for building their own open source solutions to enable successful future reuse by similar public organizations in other places. It includes guidance for policy makers, city administrators, developers and vendors. This fact can help organisations to make their information and rules available while improving the decission-making process. The Standard for Public Code webpage: https://standard.publiccode.net/
'A public review is part of the decision-making process defined by the change and release management policy. DCAT-AP change and release management policy: https://joinup.ec.europa.eu/solution/dcat-application-profile-data-portals-europe/document/change-and-release-management-policy-dcat-ap'
'The specification is available for its implementation in any business domain. By contrast, when there exist some difficulties to connect to the certificate status service provider, certificate-using systems could implement CRL (certificate revocation list) processing logic as a fall-back position. OCSP reference: https://datatracker.ietf.org/doc/html/rfc2560'
The specification is included in 5 Member States' catalogues of recommended specifications. These Member States are Estonia, Germany, Spain, Sweden and UK. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
UDDI Specification Technical Committee was composed by members coming from the most important IT companies as are IBM, Microsoft, SAP or Oracle. UDDI is along with SOAP and WSDL stack the pillars for the implementation of web services. UDDI is a key enabler for creating an effective service ecosystem. Additionally, the main market share companies support the use and implementation of UDDI, so it is demonstrated its maturity and market acceptance.
'W3C has a defined and publicly available Process for the Development and approval process of the specification as a recommended standard. Also, a clear Release Notes tracking the changes of the different versions is archived. W3C Process document: https://www.w3.org/2021/Process-20211102/'
The purpose of DCAT-AP it to support the evolution of European Public Services by enhancing the searchability and discoverability of datasets across borders. DCAT-AP is an interoperability enabler. See: https://ec.europa.eu/isa2/dcat-ap-key-european-data-publishers-reach-data-consumers-and-create-european-open-data-ecosystem_en
As a vocabulary to describe assets within a Repository, it provides concepts and properties identifying the content creators and other informative metadata such as dates involved in the release of the solutions described. These facts increase the reliability of the exchanged data. _x000D_ _x000D_ ADMS Specification W3C:_x000D_ https://www.w3.org/TR/vocab-adms/
According to the 5-star Open Data model suggested by Tim Berners-Lee about how to publish linked data, FTPS as an internet protocol for the exchange of data, supports the first level of maturity which corresponds to make data available as structured data. FTPS IETF reference: https://tools.ietf.org/html/rfc4217 5-star linked open data: https://www.w3.org/DesignIssues/LinkedData.html
JSON is a text format that is completely language independent. The specification uses conventions that are familiars to C-family of languages, including C, C++, C#, Java, JavaScript, Perl, Python, and many others. For these reasons, JSON is an optimum data exchange and interchange language.
By allowing to gather different objects signed with electronic signatures in one single ZIP file fosters the implementation of the once-only principle. Moreover, it is included in the context of the Connect Europe Facility’s (CEF) as one of the specifications covering the eSignature Building Block. At the same time, it is implemented in the Digital Signature Services (DSS), across borders initiative which aims to enhance the interoperability and data reuse. See: https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/Services+eSignature
'The purpose of ETSI TS 119 612 is not related to the long-term preservation of data. Therefore this criterion is not applicable to the specification. ETSI TS 119 612: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf'
'The DID specification is highly usable beyond business-specific domains due to its standardized, interoperable, and decentralized nature. Its applications span government, healthcare, education, finance, IoT, and more, providing secure, verifiable, and user-controlled identity management. DIDs W3C: https://www.w3.org/TR/did-core/ DID use cases: https://www.w3.org/TR/did-use-cases/'
FTP is used as the main protocol for file exchange by many public organisations. By allowing public administration to share information with others, it fosters the visibility of data (e.g. Administrative rules, processes etc.) and facilitates public administrations decision-making. An example of implementation supporting this fact would be CIRCABC, a project with the purpose of enhancing the collaboration, communication and document exchange between different European Union's stakeholders. See: https://ec.europa.eu/isa2/sites/isa/files/circabc.pdf https://circabc.europa.eu/faces/jsp/extension/wai/navigation/container.jsp
CAMSS Assessment of WAI-ARIA EIF Scenario v1.0.0
'IEEE Std 802.3-2022 can enable data portability between systems and applications supporting European public services. Its flexibility, scalability, and backward compatibility promote data sharing and interoperability. IEEE Std 802.3-2022 Reference: https://ieeexplore.ieee.org/document/9844436'
'The specification was carried out in 2001 and has been developed and maintained by OASIS. It has suffered 1 minor update (SAML 1.1) and a major one (SAML 2.0). This fact demonstrates the maturity of the specification that is being assessed. Moreover, it is also implemented by IT vendors and suppliers having a market dominance. For instance, SAML 2.0 is implemented by Microsoft for the Microsoft Azure Active Directory and by Amazon for Amazon Web Services. Therefore, it is demonstrated that SAML 2.0 has enough maturity and market acceptance for its use in the development of products and services. SAML 2.0 Reference: http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-tech-overview-2.0.html Microsoft Azure Active using SAML 2.0 Reference: https://learn.microsoft.com/en-us/azure/active-directory/develop/single-sign-on-saml-protocol'
'Slovakia and Portugal are the only European Member States that recommend the specification in their ICT National Catalogues. CAMSS List of Standards Reference: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
'The specification is a widely used de-facto standard. It was launched for the first time in 1998 by engineers from Microsoft. Other companies with a wide market share are contributed to the development of the specification. Additionally, SOAP is developed and maintained by W3C and its working group. Thus, it is sufficiently mature for the development of products and services. SOAP Reference: https://www.w3.org/TR/soap12/ '
'HTTPS itself does not directly address the specific accessibility needs of users with disabilities, it is an essential component for providing secure and accessible online services. Nonetheless, it can contribute to the enabling of e-accessibility. By establishing a secure foundation upon which they can build and ensure inclusive e-accessibility for all users, regardless of their abilities. HTTPS specification: https://tools.ietf.org/html/rfc2818'
'The flexiblity of DCAT-AP makes it possible for organisations to choose the parts of the specification they want to implement. For example, an organisation may choose to implement only the core elements of DCAT-AP in order to describe and publish metadata about their datasets. Alternatively, they may choose to implement additional elements of the standard, such as those related to access control or provenance, in order to support more advanced use cases. DCAT-AP Specification: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/dcat-application-profile-data-portals-europe/release/200'
The implementation of eSignature is a mean that allows administrations and stakeholders to exchange digital data reducing the amount of non-digital documents exchanged. Additionally, it fosters the reuse of data across borders, which as well takes part on the administrative burden reduction.
'Open reviews are an essential part of the verification process for eArchiving Building Block specification documentation. A review is a systematic examination of a document by experts and other stakeholders to find and remove errors early on in the specification life cycle. In addition, the release notes published in the E-ARK website keep track of the changes applied to the specifications over time. Open review guidelines for eArchiving Building Block specifications and documentation: https://dilcis.eu/images/procedures/LC-001390244_CEF-TC_2019-3_M23c.pdf E-ARK CSIP release notes: https://earkcsip.dilcis.eu/release-notes/'
'There is no Member State that includes the ETSI TS 119 512 in their national catalogue with Their National Interoperability Framework (NIF) in alignment with the three categories 1. Conceptual model for integrated public servicesprovision, 2. interoperability layers, and 3. interoperability principles. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
According to the 5 star Open Data model suggested by Tim Berners-Lee about how to publish linked data, the second star corresponds to make data available as structured data, an area of application of SOAP 1.2. In addition, SOAP 1.2 serialisation provides several advantages, especially if the Semantic Web is not just about providing meta data for existing web pages, but also about exchange of content that is machine-readable. See: https://5stardata.info/en/ https://pdfs.semanticscholar.org/dbf2/6496e5b3087b708d4c00883c6470b53ff8d8.pdf
'The purpose of the specification is not related to supporting the evolution of European public services, therefore it does not promote or hinder it. ETSI EN 319 422 reference: https://www.etsi.org/deliver/etsi_en/319400_319499/319422/01.01.01_60/en_319422v010101p.pdf'
The purpose of PAdES is not related to the availability of interfaces with internal information systems. Therefore, this criterion is not applicable to this specification. PAdES ISO reference: https://www.iso.org/standard/67937.html PAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/102700_102799/10277801/01.01.01_60/ts_10277801v010101p.pdf
'ISAE 3402 depends on NIA 402 and ISAE 3000. ISAE 3402 states that assurance engagements should be performed in accordance with the ISAE 3000 standard. ISAE 3402 exposure draft: https://www.ifac.org/system/files/uploads/Trans/ISAE%203402%20(definitiva%202013).pdf '
The specification defines an XML-based service metadata data model and a REST binding to retrieve service metadata. Even being XML-based, as XML is a widely adopted and supported specification, it does not hamper the interoperability of systems. Additionally, is independent of any other specific vendor product and it is supported by open and commercial solutions https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/Background
'ISO 19941 was released in 2017 and a second major release (ISO/IEC AWI 19941) is under development. While all stages of the life cycle of the specification are public, its details are not. ISO 19941: https://www.iso.org/standard/66639.html '
'The specification can be used as a global ledger by any domain. It can capture a broad set of business transaction related data e.g. accounting and taxation related details, parties involved, products or services traded. From the beginning of the development of XBRL, the recognition that financial reporting was vitally important but not meant to be the complete scope of XBRL led to the rebranding of its first name, XFRML, to XBRL. XBRL GL from its inception was designed to be a representation of detailed data across all business reporting domains. XBRL participants include financial regulators, sustainability reporting groups, and any other area of interest to business reporting stakeholders. XBRL GL was designed to represent holistically any area of business reporting, quantitative and qualitative data, in any level of detail from source events and business documents to more aggregated and summarized information, using a single, holistic, generic and global specification.'
eDelivery provide guidelines for the implementations of OASIS SMP 1.0, which has the goal to define the protocol and binding to a REST interface. Therefore, a conformant implementation of the eDelivery fosters the availability of interfaces with internal information systems.
'The DCAT specification explicitly mentions a section in its documentation about rights and obligations that can guarantee the authenticity and authentication of the roles agents involved in data transactions. It can use the properties dcat:rights, dcat:accessRights and dcat:license to ensure this authenticity. DCAT (v2.0.0) reference (section 8): https://www.w3.org/TR/vocab-dcat-2/ '
The purpose of DNS is not related to the delivery of multilingual services. Therefore this criterion is not applicable specification.
"CSV is one of the main points on the publication of Open Data. Using the specification 3 out of 5 stars from Tim Berners Lee's schema for open data are supported. Moreover, some initiatives for the publication of European Organisations data as open data, consequently Linked Open Data have their datasets stored in CSV format. An example of it is the EU Open Data Portal. CSV can be considered a facilitator to publish public administrations data as open data. As 5 Stars Open Data model of Tim Berners-Lee states, CSV makes sure content is available on the web, structures data and makes it usable in a non-proprietary open format. Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/en/ CSV reference: https://datatracker.ietf.org/doc/html/rfc4180 EU Open Data Portal: https://data.europa.eu/euodp/en/home"
'The main purpose of CPOV is to provide a reusable data model for describing public organisations in the European Union. The CPOV helps to identify where responsibilities and functions are duplicated or overlapped. So, it helps to comprehend the administrative rules and data of public administration. CPOV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-organisation-vocabulary'
The purpose of SAML 2.0 is not related to the long-term preservation of electronic records and other kinds of information. Therefore, this criterion is not applicable to the specification.
'ODRL allows the expression of permissions, prohibitions, and obligations related to the use of digital content. When used in systems that involve the exchange of digital content, ODRL can be employed to define and enforce secure access controls, ensuring that only authorized entities can access and use the data. W3C specification reference: https://www.w3.org/TR/odrl-vocab/#vocab-core'
WS-BPEL is one of the main pillars for Open Web Platform, a full programming environment for cross-platform applications with access to device capabilities. Moreover, developers can have stability into implement and plan through WS-BPEL. The specification: http://docs.oasis-open.org/wsbpel/2.0/OS/wsbpel-v2.0-OS.html
'The specification is independent from any particular software, hardware, or operating system. So, it can be said that EuroVoc is independent of any specific technology. Verifiable Credentials: https://www.w3.org/TR/vc-data-model/'
After checking the assessments performed by CAMSS and the list of specifications identified by the MSP Multi-stakeholder-platform, no assessment verifying the compliance of the specification with the European standardisation regulation has been found.
'The XACML specification ensures that access control policies are not only well-defined and consistently enforced but also transparent and auditable, meeting the needs of administrators and compliance requirements. XACML OASIS reference: https://docs.oasis-open.org/xacml/3.0/xacml-3.0-core-spec-os-en.html'
Implementing SMP within a eDelivery environment does not hamper the interoperability of systems since SMP is compatible with the scalability of networks and users. The development of these environments can be sustainable and adapt to the user needs without harming implementations. The specification: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505000
OWASP defines and evolves specifications on a community-driven basis, where all the stakeholders have the opportunity to contribute to the development of the specification. The assets of the specifications are publically available on Github and all users can create issues or add modifications. SAMM webpage: https://owaspsamm.org/ SAMM documentation: https://github.com/OWASP/samm/blob/master/Supporting%20Resources/v2.0/OWASP-SAMM-v2.0.pdf Contribute page: https://owaspsamm.org/contributing/
No assessment in terms of efficiency or effectiveness has been found regarding ASiC Baseline Profile performance.
'DPV enables expressing machine-readable metadata about use and processing of personal data based on legislative requirements such as the GDPR. Modelling of the GDPR concepts by the DPV contributes to the once-only principle given that it is meant to be an interoperable vocabulary for representing information about the use and processing of personal data. DPV specification: https://w3c.github.io/dpv/primer/'
The application of the once-only principle in all EU Member States public administrations aims at reducing the administrative burden. This Core Vocabulary fosters interoperability between public administrations, cross border services and impacts positively the development of eGovernment. CPSV-AP reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-service-vocabulary-application-profile
'The ETSI and any of its committees, in charge of the development of ETSI TS 119 512, operates under the ETSI Intellectual Property Rigths (IPRs) and IPR Policy. The specification is licensed on a Royalty-free. ETSI ownership of IPRs section: https://www.etsi.org/intellectual-property-rights'
'Assessments of the efficiency of CIM NGSI-LD API primarily involve evaluating the performance, scalability, and practicality of implementations. A 2021-paper focuses on enhancing the semantic capabilities of the oneM2M architecture by providing solid contributions to the oneM2M standards. During the study phase where possible approaches to a discovery and data aggregation solution are analysed with respect to the use cases and requirements, there are also looks to the query and discovery mechanisms already available, starting from the ones defined by CIM NGSI-LD API. ETSI SmartM2M Technical Report 103716: https://inria.hal.science/hal-03261059/document'
Although FTPS is an alternative of FTP for a secure communication internet protocol and it has been supported by some commercial file transfer tools, SFTP is easier to implement and it works better over NATs and firewalls without the issues that hamper FTPS implementations. So, it does not have a complete market acceptance. FTPS - Obsolescent Secure FTP: https://www.ssh.com/ssh/ftp/ftps FTPS IETF reference: https://tools.ietf.org/html/rfc4217
'The Advanced Encryption Standard (AES) is a solution used to encrypt data, making it more secure against attacks or attempts to access data in an unauthorised way. In this context, the standard not only addresses data protection but also interoperability and collaboration. Moreover, AES has been assessed in many papers and discussed in terms of how it can be implemented in different contexts. Finally, it has been integrated into solutions such as VeraCrypt. VeraCrypt AES project: https://veracrypt.eu/en/AES.html AES Standard Reference: https://csrc.nist.gov/pubs/fips/197/final'
The specification was produced in 2004, and it has been followed at European level. These Best Practices have been evolved together with the application profile used in the European Platform for the reusability of interoperability Solutions, Joinup. W3C Reference: https://www.w3.org/TR/dwbp/
'The purpose of SFIA is not related to the secure processing of data. Therefore, this criterion does not apply to this specification. SFIA reference: https://sfia-online.org/en/sfia-8'
'FTP is developed and maintained by IETF, a widely recognised open international community developing standards to enhance the internet. IETF Reference: https://www.ietf.org/ FTP Specification Reference: https://datatracker.ietf.org/doc/html/rfc959'
XSLT is a language for transforming XML documents. Therefore, it fosters the visibility and comprehensibility of public administrations data and services as it facilitates the visibility of the documents.
'While the primary focus of W3C Verifiable Credentials (VC) is on secure and privacy-preserving credential exchange, they can play a role in supporting and enhancing the modeling of certain business processes. Verifiable Credentials provide a standardized way to express and exchange claims, and this capability can be leveraged in various business contexts. Verifiable Credentials: https://www.w3.org/TR/vc-data-model/'
OpenPM2 establishes a common methodology for the development of processes. The adoption of this methodology can positively impact the organisational interoperability between organisations developing services or products under this methodology since they would be acting and carrying out similar steps that would allow the cooperation between them. Cooperation in cross-border projects is a powerful feature enhancing efficiency and effectiveness. OpenPM2 specification reference: https://op.europa.eu/en/publication-detail/-/publication/ac3e118a-cb6e-11e8-9424-01aa75ed71a1/language-en/format-PDF/source-83307127
'The ETSI TS 119 612 specification establishes mechanisms such as digital signatures that allow to ensure data authenticity and integrity. In this sense, such mechanisms allow public administrations and organisations to share data in its original form. ETSI TS 119 612: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf'
'The Shape Expressions (ShEx) language provides a structural schema for RDF data. This can be used to document APIs or datasets, aid in development of API-conformant messages, minimize defensive programming, guide user interfaces, or anything else that involves a machine-readable description of data organization and typing requirements. ShEx primer document: https://shexspec.github.io/primer/ ShEx Community Group: https://www.w3.org/community/shex/ ShEx Github: https://github.com/shexSpec/spec/issues'
"As it can be seen in the example of 'data protection aspects of online shopping - a use case', DPV specifies the personal data that an order delivery has to take from the client, meaning that it provides the standard data that can be collected following European privacy regulations such as GDPR, thus, becoming an asset for the digitalisation with conformity to such regulations. DPV specification: https://w3c.github.io/dpv/primer/ Data protection aspects of online shopping - a use case: https://www.w3.org/community/dpvcg/2019/12/12/data-protection-aspects-of-online-shopping-a-use-case/"
'The purpose of BFO is not related to data integrity. Therefore, this criterion is not applicable to the specification. BFO reference: https://www.iso.org/standard/74572.html'
'E-ARK CSIP has clearly defined guidelines that detail the processes for managing changes, and how releases are handled. E-ARK supporting guidelines: https://dilcis.eu/guidelines/supporting-guidelines'
"The purpose of SFIA is not related to the exposure of interfaces to access the public administration's services. Therefore, this criterion is not applicable to this specification. SFIA reference: https://sfia-online.org/en/sfia-8"
Better Regulation Toolbox is an internal European Commission resource designed as a complement to the Commission's Better regulation guideline. Even though it could be extended or modified to fit other business requirements at the National level, for instance, there are no implementations that evidence the possibility of extension to other business domains than the development of public policies and laws. Betterr Regulation Toolbox reference: https://ec.europa.eu/info/sites/info/files/better-regulation-toolbox_2.pdf
'DNS over HTTPS (DoH) is designed to be platform agnostic. It operates at the application layer of the networking stack, and its implementation is independent of specific operating systems or platforms. This platform agnosticism allows for consistent usage across various devices and environments. DoH specification: https://datatracker.ietf.org/doc/html/rfc8484'
'OpenTelemetry is not included in any initiative at European or National level covering privacy aspects. Therefore, this criterion is considered not applicable to this specification. OpenTelemetry: https://opentelemetry.netlify.app/docs/specs/otel/'
"There are not specific assessments nor any deployment use case evaluating the specification's efficiency. TOSCA reference: https://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.3/os/TOSCA-Simple-Profile-YAML-v1.3-os.html"
'The use of HTTPS not only ensures that the communication between the user and the service is protected, but also provides the exposure interface of the message that will be sent to the requester. HTTPS specification: https://tools.ietf.org/html/rfc2818'
CSS v2.1 is dependent from HTML, its main function is to describe how HTML elements should be displayed on web documents. CSS v2.1 W3C reference: https://www.w3.org/TR/2011/REC-CSS2-20110607/
'IEEE Std 802.3-2022 covers data transmission, media access control, and network performance; however, it does not directly address security. Its design, though, facilitates the implementation of robust security measures alongside higher-layer protocols and practices, enabling secure data exchange. IEEE Std 802.3-2022 Reference: https://ieeexplore.ieee.org/document/9844436'
After searching in the different official European websites, there is no evidence of any cross-border project that uses CAdES (ISO 14533-1:2014) nor explicit agreements involving the usage of the specification. However, the specification CAdES from ETSI, is involved in some cross-border projects as "Analysis of standards related to Trust Service Providers" developed by ENISA (European Union Agency for Network and Information Security) which is a centre of network and information security expertise for the EU, its member states, the private sector and Europe’s citizens. ENISA project: https://www.enisa.europa.eu/publications/tsp_standards_2015/at_download/fullReport CAdES ISO reference: https://www.iso.org/standard/64756.html CAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/101700_101799/101733/02.01.01_60/ts_101733v020101p.pdf
'The purpose of HTTPS is not related to the provision of access control mechanisms. Therefore this criterion is not applicable to the specification. HTTPS specification: https://tools.ietf.org/html/rfc2818'
The purpose of FTPS is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification. FTPS IETF reference: https://tools.ietf.org/html/rfc4217
Not enough pieces of evidence have been found to answer if the specification purpose fits negatively or positively the one stated by the criterion. ELI reference: https://eur-lex.europa.eu/eli-register/about.html
"Some European projects using UBL have been found to conduct effectiveness assessments. Such is the case of PEPPOL BIS Billing or ESPD. In addition, There has been found an article assessing the impact of UBL implementation among SME's in developing countries. Suitable EAI architectures are necessary to fit interoperability challenges of SME's in less developed countries: https://www.academia.edu/10858900/Suitable_EAI_architectures_are_necessary_to_fit_interoperability_challenges_of_SMEs_in_less_developed_countries Peppol BIS Billing 3.0 https://docs.peppol.eu/poacc/billing/3.0/"
"A review of catalogues found no evidence of RegOrg being formally included in Member States' recommended specifications or recognised at a European supra-national level. Despite this, the Belgian Interoperability Framework (Belgif) includes the OSLO framework, which is used for semantic interoperability in Belgium. Within OSLO, various key elements and properties from RegOrg are still being utilised. Registered Organization Vocabulary reference: https://www.w3.org/TR/vocab-regorg/ CAMSS list of standards: https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-andspecifications-camss/camss-list-standards Belgian Interoperability Framework (Belgif): https://www.belgif.be/page/specifications.en.html OSLO Smart City Distribution - Application profile Reference: https://data.vlaanderen.be/doc/applicatieprofiel/slimme-stadsdistributie/"
'The purpose of ETSI EN 319 532-3 is not related to the reuse of information. ETSI EN 319 532-3 reference: https://www.etsi.org/deliver/etsi_en/319500_319599/31953203/01.02.01_60/en_31953203v010201p.pdf'
The purpose of IPsec is not related to e-accessibility. Therefore this criterion is considered not applicable specification.
Transparency of the development process is evidenced by a defined and publicly available documentation on the development and maintenance of the specification.
"The OData protocol is an application layer protocol for exchanging data through RESTful interfaces. In this sense, the specification enables exposure of any interface, including those interfaces providing access to public administration's services. OData reference: http://docs.oasis-open.org/odata/odata/v4.0/errata03/os/complete/part1-protocol/odata-v4.0-errata03-os-part1-protocol-complete.html#_Toc453752201"
'IEEE Std 802.3-2022 itself does not guarantee the protection against unauthorised changes since it focuses primarily on the physical and data link layers of Ethernet networks. Therefore, this criterion is not applicable to this specification. IEEE Std 802.3-2022 Reference: https://ieeexplore.ieee.org/document/9844436'
'The specification clearly encourages the creation of communities along with the sharing of their data and results as its purpose is to improve cloud computing portability and interoperability, thus improving communication between different actors. Furthermore, ISO/IEC 7498:1 has been included in different catalogues of ICT standards in a European level therefore, it is an important standard to consider. ISO/IEC 7498:1: https://www.iso.org/standard/20269.html'
At the time of elaborating this assessment, MIME is not included in any EIRA ABB in the current EIRA Library Of Interoperability Specifications (ELIS). EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/solution/elis/release/v100
By allowing the digital document exchange including eSignatures, the CAdES Baseline profile avoids the non-digital data exchange. This fact is a key point in the reduction of administrative burden.
'Although MIME itself does not foresee mechanisms for keeping the data integrity, its security extension (S/MIME) does include features that help guarantee data integrity, such as cryptographic techniques, to ensure that the content of an email messange remains unchanged during transmission. MIME specification: https://tools.ietf.org/html/rfc2045 S/MIME specification: https://www.rfc-editor.org/rfc/rfc5751.html'
Better Regulation Toolbox includes accessibility within the ICT requirements that ICT systems and solutions should cover for the proper implementation of a specific public policy (Tool #27). Therefore, it can be considered that taking the tools and methods, the specification can positively impact the e-accessibility of public services and solutions. Betterr Regulation Toolbox reference: https://ec.europa.eu/info/sites/info/files/better-regulation-toolbox_2.pdf
There is no national or European platform with the document, Data on the web best practices, available for free.
'E-ARK CSIP is not related to e-accessibility, therefore this criterion is not applicable to the specification. E-ARK CSIP specification: https://earkcsip.dilcis.eu/#introduction'
'ISO/IEC 18844-1 has been found included in the European Cybersecurity Certification Scheme for Cloud Services (EUCS) project, which uses components from ISO/IEC 17788 and ISO/IEC 17789, standards from which ISO19944-1 is derived and extended. ISO/IEC 19944-1 specification: https://www.iso.org/standard/60545.html EUCS project: https://www.enisa.europa.eu/publications/eucs-cloud-service-scheme'
'The purpose of SHACL is not related to the reuse of information when needed. Therefore this criterion is considered not applicable to the specification. SHACL W3C reference: https://www.w3.org/TR/shacl/'
'The TrainingDML-AI Standard allows for customisation in terms of how the training data is prepared, how different metadata is used for different ML tasks, and how to introduce external classification schemes. OGC TrainingDML-AI Standard: https://docs.ogc.org/is/23-008r3/23-008r3.html'
'After checking the different standard catalogues at supra-national level, there is no evidence of the inclusion of ISO/IEC 27001 within any European catalogue of standards. ICT technical specifications: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en CEN search tool catalogue: https://standards.cen.eu/dyn/www/f?p=CENWEB:105::RESET:::: CENELEC search tool catalogue: https://www.cenelec.eu/dyn/www/f?p=104:107:0::::FSP_LANG_ID:25'
'The primary goal of HTTPS is to establish a secure and encrypted connection between a client and a server, ensuring the confidentiality, integrity, and authenticity of data during transit. The secure processing of data involves additional considerations beyond the scope of HTTPS such as the compliance with data protection regulations between others. HTTPS specification: https://tools.ietf.org/html/rfc2818'
After checking the different standard catalogues at supra-national level, there is no evidence of the inclusion of the Standard for Public Code within any European catalogue of standards. ICT technical specifications: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en CEN search tool catalogue: https://standards.cen.eu/dyn/www/f?p=CENWEB:105::RESET:::: CENELEC search tool catalogue: https://www.cenelec.eu/dyn/www/f?p=104:107:0::::FSP_LANG_ID:25
'The specification as it describes public administration services and procedures it allows to contribute to the exposure of interfaces if combined with other specifications. CPSV-AP reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-service-vocabulary-application-profile'
Anyone developing software or policy for a public purpose can use this standard to work towards higher quality public services that are more cost effective, with less risk and more control, so it can be said that Standard for Public Code can be applied and developed in different domains and purposes without harming the interoperability of functinality of systems. The Standard for Public Code webpage: https://standard.publiccode.net/
'The FTP specification allows for extensions to add additional functionality and capabilities beyond the core protocol commands and behaviors. FTP Specification Reference: https://tools.ietf.org/html/rfc959'
The LegalDocML is developed by OASIS using the technical commities (TC). The goal of the TC in charge of LegalDocML development is to collect requirements from the community of the stakeholders who create, manage and use legislative and legal documents in order to extend and refine the standard. The main objective of the OASIS community is to promote individuals, organizations, and governments come together to solve some of the world’s biggest technical challenges through the development of open code and open standards LegalDocML reference: https://www.oasis-open.org/committees/legaldocml/charter.php OASIS home page: https://www.oasis-open.org/
'There are already existing studies and documents assessing and documenting DQV features and providing possible improvements of its performance among other aspects. In "DQAF: Towards DQV-Based Dataset Quality Annotation Using the Web Annotation Data Model" it is proposed to use the DQV specification for a Dataset Quality Annotation Framework (DQAF). Furthermore, there are ducumentation such as "Introducing the Data Quality Vocabulary (DQV)", which makes and assessment of DQV and explains its components as well as how it works. "DQAF: Towards DQV-Based Dataset Quality Annotation Using the Web Annotation Data Model" reference: https://ieeexplore.ieee.org/document/7799649 "Introducing the Data Quality Vocabulary (DQV)" reference: https://www.semantic-web-journal.net/system/files/swj2079.pdf'
'UTF-8 is already associated with the Controlled Vocabulary, data, Data Model, Data Syntax, Forms Structure, Hash Code and Metadata ABBs from the EIRA Library of Interoperability Specifications (ELIS) Semantic view. ELIS in Joinup: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/v501'
The specification is aimed to represent information in order to be readable in both formats, machine-readable, and human-readable format. Despite this, RDF does not help the availability of interfaces with internal information.
'While OpenTelemetry itself is not specifically designed for e-accessibility, its observability capabilities can indirectly support the development, monitoring, and improvement of accessible digital services. By providing insights into performance, errors, user behavior, compliance, and integration with accessibility tools, OpenTelemetry contributes to creating a more inclusive digital environment where individuals with disabilities can access and interact with services effectively. OpenTelemetry: https://opentelemetry.netlify.app/docs/specs/otel/'
As it happens with core vocabularies, the specification can be extended to cover specific business needs. An example of this extension is the work done within the scope of SERAMIS project, which is a GDPR validation tool that uses an ODRL extended model as basis for the validation. SERAMIS: https://cordis.europa.eu/docs/projects/cnect/2/612052/080/deliverables/001-D55v4GDPR.pdf W3C specification reference: https://www.w3.org/TR/odrl-vocab/#vocab-core
'BFO is a core element of multitude of existing implementations that address the effectiveness of the criterion. BFO reference: https://www.iso.org/standard/74572.html BFO users: https://basic-formal-ontology.org/users.html'
After carrying out information retrieval, no document or study has been found assessing the XAdES in terms of efficiency or effectiveness.
'Cryptographic algorithms are the basis of e-signatures encryption. ETSI TS 119 511 is furthermore developed for trust service providers for the storing and retrieval of information and data that require a high degree of security in their processing and exchange. ETSI TS 119 511 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119511/01.01.01_60/ts_119511v010101p.pdf'
'The implementation of the specification relies on the HTML or SVG2 specifications. Therefore, WAI-ARIA is not technology-agnostic. WAI-ARIA reference: https://www.w3.org/TR/wai-aria/'
'The purpose of XSLT is not related to the long-term preservation of electronic records and other kinds of information. Therefore, this criterion is not applicable to the specification. XSLT Reference: https://www.w3.org/TR/xslt-30'
There is no Member State that includes Standard for Public Code in their national catalogue with The National Interoperability Framework (NIF) aligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
"One of IDS' underlying objectives is to improve data interoperability and integrity. Therefore, it encourages the creation of communities along with the sharing of their data and results at European platforms (e.g. DBSA). Furthermore, IDS-G has public channels such as GitHub where users can discuss and ask any matter at hand. The Data Spaces Business Alliance (DSBA): https://data-spaces-business-alliance.eu/ IDS-G DISCUSSIONS: https://github.com/International-Data-Spaces-Association/IDS-G/discussions"
'iCalendar does not provide specific provisions for the secure exchange of data; however, the specification introduces certain aspects that an implementer or an owner of the Personal Information Manager (PIM) should consider to secure the processing of data (e.g., when accepting and parsing such information). iCalendar Security Considerations: https://www.rfc-editor.org/rfc/rfc5545#section-7'
DCAT-AP has been developed to facilitate the publication of linked open data.
5 Member States are recommending JSON in their ICT National Catalogues. See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'Following the completion of the research into conformity tests and certifications, an open-source tool has been identified that enables the testing of implementations with time-stamping commands. This tool is designed to ensure that the implementations are developed in an appropriate manner. TSP certification tool: https://www.freetsa.org/index_en.php OpenSSL: https://www.openssl.org/docs/manmaster/man1/ts.html'
'ODRL is a specification that provides a core vocabulary that allows the description and representation of information in a standardised and machine-readable format fostering the data exchange and the interoperability of organisations and resources using it. Moreover, the specification offers serialisation in common formats for open data publication and shareability such as RDF or JASON-LD. W3C specification: https://www.w3.org/TR/odrl-vocab/#vocab-core'
'The purpose of ADMS is not related to restricting access to information or data. Therefore, this criterion is not applicable to the specification. ADMS Specification W3C: https://www.w3.org/TR/vocab-adms/'
'The purpose of Core Location Vocabulary is not related to the long-term preservation of data. Therefore this criterion is not applicable to this specification. Core Location Vocabulary: https://interoperable-europe.ec.europa.eu/collection/semic-support-centre/solution/core-location-vocabulary/release/100'
OASIS has defined a clear process where all the stakeholders involved have the opportunity to participate in the development of the specification development process. Moreover, there is a public review in the TC process. The specification: http://docs.oasis-open.org/xacml/3.0/xacml-3.0-core-spec-os-en.html
'The publiccode.yml specification accommodates extensions, particularly through its structure for country-specific customisations, which allows jurisdictions to incorporate fields aligned with local regulatory, legal, or operational requirements. This flexibility ensures that publiccode.yml can adapt to diverse administrative contexts while maintaining a standardised core, promoting both local relevance and broad interoperability. The specification thus supports extended functionality in a manner that upholds international compatibility and adaptability to specific national needs. Publiccode.yml documentation: https://docs.italia.it/italia/developers-italia/publiccodeyml-en/en/master/index.html Publiccode.yml section 2, Country-Specific Extensions https://docs.italia.it/italia/developers-italia/publiccodeyml-en/en/master/country.html#country-specific-extensions'
'If a DID method specification is written for a public-facing verifiable data registry where corresponding DIDs and DID documents might be made publicly available, it is critical that those DID documents contain no personal data. Personal data can instead be transmitted through other means such as Verifiable Credentials [VC-DATA-MODEL], or service endpoints under control of the DID subject or DID controller. DIDs restriction of access W3C: https://www.w3.org/TR/did-core/#keep-personal-data-private'
'There are no Member States recommending SMP in their ICT National Catalogues. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards'
The purpose of HTTP is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification.
PAdEs and PAdES Baseline profile are maintained by ETSI, one of the European Agencies for Standardisation. See: https://www.etsi.org/about
W3C has a defined and publicly available Process for the Development and approval process of the specification as a recommended standard. Also, a clear Release Notes tracking the changes of the different versions is archived. W3C Process document: https://www.w3.org/2018/Process-20180201/#Policies Technical reports: https://www.w3.org/standards/history/shacl
JSON is a lightweight specification that allows data exchange between different applications fostering interoperability and data visibility. The specification is scarcely used for document exchange. Therefore, JSON adoption does not hamper the interoperability and scalability of systems. See: https://www.json.org/xml.html
'This specification can be considered a European Standard as it is listed in the European Union Observatory for ICT Standardisation (EUOS). The EUOS will thoroughly monitor the global Standardisation landscape, providing a comprehensive and accurate coverage of the most important ICT Standards, Working Groups and Technical Committees that affect the key ICT topics of the Digital Single Market and the EU ICT Rolling Plan for Standardisation. EUOS: https://standict.eu/euos'
DCAT-AP has been selected for the description of datasets by three European Initiatives The European Data Portal, The European Open Data Portal and the JRC Data Catalogue. See: https://joinup.ec.europa.eu/solution/dcat-application-profile-data-portals-europe/about
ETSI TTC3+ Conformance test suit is available to test several features of the protocol. See: http://www.ttcn-3.org/index.php/about/introduction
'DCAT-AP has a significant market acceptance. The specification has been successfully implemented by several European Union Institutions such as the European Commission DG CONNECT with the European Data Portal, The Publications Office of the European Union with the European Union Open Data Portal or The German GovData Business Office with the German Data Portal. About DCAT Application Profile for data portals in Europe: https://joinup.ec.europa.eu/solution/dcat-application-profile-data-portals-europe/about'
nan
Better regulation provides a set of guidelines to guarantee that policies and laws development, implementation and evaluation are properly established. At this point, the Better regulation toolbox includes a set of recommendations, best practices and requirements whose purpose is to ensure and enhance the cross-border application and organisational interoperability as much as possible. Betterr Regulation Toolbox reference: https://ec.europa.eu/info/sites/info/files/better-regulation-toolbox_2.pdf
'iCalendar can support the visibility of certain administrative procedures, rules data, and services by providing a comprehensive set of mechanisms to enable the exchange and management of calendar-related data such as envent descriptions, services availability, and location information. iCalendar specification: https://www.rfc-editor.org/rfc/rfc5545'
"XFDL is based on XML, which is inherently a portable data format. XML allows data to be easily shared across different systems and platforms because it's a text-based, standardised format that can be parsed and processed by a wide range of applications. Extensible Forms Description Language reference: https://www.w3.org/TR/NOTE-XFDL"
'REST has a wide-spread market acceptance as it is a common method to connect components in microservice architectures. Among the top businessess who implement it we can find IBM or Amazon Web services. Amazon Web Services reference: https://docs.aws.amazon.com/apigateway/latest/developerguide/apigateway-rest-api.html REST IBM reference: https://www.ibm.com/es-es/cloud/learn/rest-apis'
'The specification addresses semantic aspects thus data security and data privacy issues are addresses by other means. The specification does not prevent the use of any security means. Issues related to authorization and authentication of data are key to its secure processing, and XBRL GL was designed with secure processing in mind.'
'W3C has a defined and publicly available Process for the Development and approval process of the specification as a recommended standard. Also, a clear Release Notes tracking the changes of the different versions is archived. W3C Process document: https://www.w3.org/2018/Process-20180201/#Policies'
The European Union (EU) Member States are currently implementing the INSPIRE Directive and related regulations, included in the ISA programme. So it should be used by all member states.
This common data model has been defined as a core vocabulary for criteria and evidences. A Core Vocabulary is a simplified, reusable, and extensible data model that captures the fundamental characteristics of an entity in a context-neutral fashion. CCCEV reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-criterion-and-core-evidence-vocabulary
'The purpose of CPOV is not related to the provision of access control mechanism. Therefore, this criterion is considered not applicable to this specification. CPOV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-organisation-vocabulary'
'After searching the different national catalogues, no European Member State has been found to recommend the Core Location Vocabulary specification. Core Location Vocabulary: https://interoperable-europe.ec.europa.eu/collection/semic-support-centre/solution/core-location-vocabulary/release/100'
'HTTP Cookies can be customised by changing the attributes that define, for example, the lifetime of a Cookie, or by adding the "secure" attribute, which is meant to keep cookie communication limited to encrypted transmission. HTTP Cookies reference: https://datatracker.ietf.org/doc/html/rfc6265#section-5.2'
The purpose of this specification is not related to e-accessibility. Therefore, this criterion is not applicable to the specification. SAMM webpage: https://owaspsamm.org/ SAMM documentation: https://github.com/OWASP/samm/blob/master/Supporting%20Resources/v2.0/OWASP-SAMM-v2.0.pdf
'The purpose of genericode is not related to covering privacy aspects at European nor National level. Therefore, this criterion is considered not applicable to this specification. Code List Representation (genericode): https://docs.oasis-open.org/codelist/genericode/v1.0/os/genericode-v1.0-os.html'
"The purpose of Advanced Encryption Standard is not related to enabling the exposure of interfaces to access the public administration's services. Therefore this criterion is not applicable to the specification. AES Standard Reference: https://csrc.nist.gov/pubs/fips/197/final"
"In the specification's documentation there is no mention to partial implementations, only the use of it as a whole. SMP OASIS reference: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505009"
"HTTP does contribute to secure data processing by enabling the implementation of security measures, primarily focused on controlling access and protecting data during transmission. However, they don't provide a complete framework for secure data processing. HTTP/1.1, RFC 2616 Reference: https://www.rfc-editor.org/rfc/rfc2616 HTTP/1.1 Authentication, RFC 9110 Reference: https://www.rfc-editor.org/rfc/rfc9110#name-http-authentication"
MIME extends the format of email messages to support text in ASCII and non-ASCII characters, as well as attachments of audio, video, images, and application programs. MIME reference: https://tools.ietf.org/html/rfc2045
'The ELI system allows for the reuse of material free of charge, even for commercial purposes, without having to request permission. The information can be reproduced, adapted, translated, etc. However, this reuse may be subject to conditions. ELI reference: https://eur-lex.europa.eu/eli-register/about.html'
'The specification can be migrated from older CSV versions to newer formats or standards to ensure that the data remains accessible and usable in the future. CSV can also implement robust storage and backup strategies, including redundancy, data replication, and regular backups, helps mitigate the risk of data loss or corruption. It is crucial to store CSV files in reliable and secure storage systems to ensure their long-term preservation. CSV reference: https://datatracker.ietf.org/doc/html/rfc4180'
'While the specification provides a framework for describing service endpoints, capabilities, and other relevant details, it does not specifically address the protection of personal data managed by public administrations. SMP OASIS reference: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505009'
'OAIS has currently undergone three major releases, the changes of whom are published in the CCSDS website, and in the ISO website. OAIS overview and release management: https://cwe.ccsds.org/fm/Lists/Projects/DispFormDraft.aspx?ID=581'
Like all the IETF standards, TLS 1.2 is a free and open technical specification, built on IETF standards and licenses from the Open Web Foundation. FTP is licensed on a F(RAND) basis. See: https://tools.ietf.org/id/draft-gutmann-tls-lts-10.html
'Linked Data Event Streams (LDES) itself is a specification for representing and publishing real-time event data on the web using Linked Data principles. While the specification provides a framework for structuring event data, the multilingual support may be influenced by how the data within the events is represented and linked. LDES specification: https://joinup.ec.europa.eu/collection/semic-support-centre/linked-data-event-streams-ldes'
The specification is a protocol focused on the transaction of data. Even though it is related to data exchange, and it is aimed to ensure the delivery of data, it is not involved in data portability amongst systems fostering the European Public Services. The specification: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505000
'Verifiable Credentials is not included in any national catalogue of recommended specifications whose Member State NIF has a high performance on interoperability according to NIFO factsheets. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards'
No evidences have been found of existing assessments regarding effectiveness or efficiency of the specification that allow to answer positively to this criterion.
In the context of eSignatures and Seals, the European Commission has stated an Implementing decision (2015/1506) where urged the Member States and other Public services providers to recognise CAdES, PAdES, XAdES, and ASIC as formats for electronic signatures purposes.
'ESPD is platform-agnostic, which means that it can be used with a wide range of digital platforms and systems. The ESPD is available in various formats, including electronic forms, PDF documents, and structured data formats such as XML, which allows it to be integrated into different digital platforms. ESPD Business handbook: https://docs.ted.europa.eu/ESPD-EDM/latest/xml_business_handbook.html'
HTML was the first standard markup language to develop web resources. HTML files are used to exchange information through the web, and they foster data portability between systems and applications. HTML W3C reference: https://www.w3.org/TR/html401/
'The Core Location Vocabulary can help to facilitate the modelling of business processes. The Core Vocabularies can become the basis of a context-specific data model used to exchange data among existing information systems. Core Vocabularies: https://interoperable-europe.ec.europa.eu/collection/semic-support-centre/core-vocabularies Core Location Vocabulary: https://interoperable-europe.ec.europa.eu/collection/semic-support-centre/solution/core-location-vocabulary/release/100'
'Since EuroVoc has been developed and published by the Publications Office of the European Union, it can be assumed that the specification is a European Standard. EuroVoc: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource /dataset/eurovoc'
'The GITB TDL major releases are public for anyone to use and review in GITHUB. There is also published documentation on its supporting processes and change management on its website. Being the first release on 2017, GITB TDL has undergone several improvements and overcome possible issues until the last version 1.15, which has been released on 2022. GITB TDL reference: https://www.itb.ec.europa.eu/docs/tdl/latest/changelog/index.html'
The purpose of this Core Vocabulary is related to the delivery of multilingual public services. The use of this Core Vocabulary for electronic criterion and evidence allows for removing language barriers thereby improving the cross border exchange of information. CCCEV reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-criterion-and-core-evidence-vocabulary
'By easing the creation of secured web services, XACML contributes to the increment of digital public services between administrations and stakeholders and among administrations. This public services can include Secure Data Transfer amongst other services. One of the services that can help to simplify this delivery public services is Semiramis, which is a pilot infrastructure to provide e-services. XACML OASIS reference: https://docs.oasis-open.org/xacml/3.0/xacml-3.0-core-spec-os-en.html SEMIRAMIS project: https://joinup.ec.europa.eu/solution/semiramis/about'
HTML5 is a business domain agnostic specification.
'Verifiable Credentials include several features to protect against unauthorized changes and ensure the integrity and security of the credentials. Verifiable Credentials are typically signed using digital signatures and its content is often hashed before signing. Also, the specification insists on the selective disclosure feature, which allows the holder to present only specific claims or attributes from a credential. This specification describes mechanisms for ensuring integrity of Verifiable Credentials and similar types of constrained digital documents using cryptography, especially through the use of digital signatures and related mathematical proofs. Verifiable Credentials Data Integrity: https://www.w3.org/TR/vc-data-integrity/'
"All SFIA releases are subject to public review. Although anyone can contribute to the development of the SFIA specification, it is worth to note that only the SFIA team and key stakeholders are involved in final decisions. The entire process is transparent, meaning that changes and all the supporting documents are publicly available in the dedicated SFIA-release section (see SFIA reference, Start of SFIA 8 consultation section). SFIA release reference, SFIA version 8, 'The story behind the content' section: https://sfia-online.org/en/sfia-8#autotoc-item-autotoc-7 SFIA reference, Start of SFIA 8 consultation section: https://www.sfia-online.org/en/sfia-8/start-of-sfia-8-consultation?msclkid=59a790c2ba5711eca7d3c3c3b117d15a"
LDAP is an application protocol for accessing and maintaining distributed directory information services over the net, it is independent of implementation. The specification allows many applications and services to connect to the LDAP server to validate users, which reduces the administrative burden of the system administrators and the users. As it is widely supported the implementation of the LDAP would not hamper the interoperability between systems and services. LDAP IETF reference: https://tools.ietf.org/html/rfc4511
'ETSI EN 319 532-3 can be found on the specifications and standards repository of its own standards development organization, the European Telecommunication Standards Institute (ETSI). ETSI Standards Repository: https://www.etsi.org/standards#page=1&search=ETSI%20EN%20319%20532- 3&title=1&etsiNumber=1&content=1&version=0&onApproval=1&published=1&historical=1&startDate=1988- 01-15&endDate=2022-07- 25&harmonized=0&keyword=&TB=&stdType=&frequency=&mandate=&collection=&sort=1'
'ISAE 3402 is mainly focused on establishing quality control processes in private sector companies, administrations could benefit from implementing it for those procedures that require payments. This would allow public administrations to clearly define and expose how their procedures are carried out and therefore, enhance transparency and comprehensibility of data. ISAE 3402 website: https://www.isae3402.com/ISAE3402_overview#'
'XML is used to encode all communications between web services. Therefore, it fosters the visibility and comprehensibility of public administrations data and services. See: https://esentool.ted.europa.eu/'
'UBL is independent of any specification and can be implemented without any dependency on platforms. UBL v2.3 reference: http://docs.oasis-open.org/ubl/os-UBL-2.3/UBL-2.3.html'
'The publiccode.yml specification can indeed foster the creation of collaborative communities that share software information on national and European platforms. By standardising metadata for public sector software, it allows for easy exchange and visibility of projects, which can encourage collaboration, co-creation, and reuse among different administrations and sectors. This structured approach aligns with EIF Recommendation 32, as it provides a consistent way to document and share software, promoting transparency and joint development efforts at various levels. Publiccode.yaml documentation: https://docs.italia.it/italia/developers-italia/publiccodeyml-en/en/master/index.html EIF: https://ec.europa.eu/isa2/sites/isa/files/eif_brochure_final.pdf'
'At the moment of performing the assessment, no initiative at national or European level has been found to use ISO/IEC 7498:1 to cover privacy aspects. ISO/IEC 7498:1: https://www.iso.org/standard/20269.html'
'The purpose of Registered Organization Vocabulary is not related to provide means for restriction of access to information/data. Therefore, this criterion is considered not applicable to this specification. Registered Organization Vocabulary reference: https://www.w3.org/TR/vocab-regorg/'
'The specification allows for checking that the data transmited by data providers includes the compulsory and syntactically correct data elements. XSD Reference: https://www.w3.org/TR/2012/REC-xmlschema11-1-20120405/'
'As defined by the OASIS Technical Committee (TC), the UBL TC is involved in the release lifecycle of the specification. External contribution to this committee is possible through open channels. Up-to-date, the UBL TC has announced three public reviews; however, the topic selection of these reviews is independent of the external contributors. UBL OASIS Technical Committee reference: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ubl'
Although JPEG is supporting the first level of maturity from the Tim Berners-Lee 5-star schema for the Open data, it is not supporting the main principles for the publication of data as Linked Open Data. JEPG ISO reference: https://www.iso.org/standard/18902.html JPEG public reference: https://jpeg.org/jpeg/ 5-star linked open data: https://www.w3.org/DesignIssues/LinkedData.html
"There are some comparative reports of SFIA and other ICT skills and competence frameworks such as the e-Competence Framework (see SFIA reference, Tools and Resources section, Collaborations subsection, 'SFIA – e-CF Comparison & Mapping Review' document), which indirectly assesses the SFIA specification's effectiveness. SFIA reference, Tools and Resources section, Collaborations subsection: https://sfia-online.org/en/tools-and-resources/collaborations SFIA reference, Tools and Resources section, Collaborations subsection, 'SFIA – e-CF Comparison & Mapping Review' document: https://sfia-online.org/en/assets/documents/e-cf/sfia-e-cf-comparison-mapping-report-v1-0.pdf"
'The TGF is an open framework that is freely available for use and adaptation by governments and other stakeholders, without any licensing or patent restrictions. The TGF is based on open standards and interoperability, and its development has been guided by principles of openness, transparency, and inclusivity. The TGF specification is published and made available under a royalty-free license, which allows users to copy, distribute, and transmit the specification, and to adapt it for their own use, as long as they give appropriate credit to the original source. OASIS IPR policy: https://www.oasis-open.org/policies-guidelines/ipr/'
'ETSI TS 119 511 offers some provisions on the portability of documents containing digital signatures. This can be provided by preservation and validation services, whose main functions are to authenticate and preserve the chain of evidence of official documents. Nonetheless, ETSI TS 119 511 only specifies the requirements of these functionalities, while its companion document ETSI TS 119 512 provides the protocols to implement these services. Therefore, ETSI TS 119 511 supports the evolution of European public services. ETSI TS 119 511 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119511/01.01.01_60/ts_119511v010101p.pdf ETSI TS 119 512 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.02_60/ts_119512v010102p.pdf eIDAS blog, New APIs for the eIDAS-Ecosystem: https://blog.eid.as/tag/etsi-ts-119-512-en/'
7 Member States are recommending TLS 1.2 in their ICT Catalogues. See CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'SFIA is intended to serve as a device to represent skills and competences of any ICT professional workforce. There is no possibility of tailoring the SFIA specification, nor any kind of authorising process is allowed, since SFIA has a single purpose. SFIA reference: https://sfia-online.org/en/sfia-8'
'When it comes to services related to the access of any kind of archives, OAIS can simplify the delivery of public services insofar it provides a framework from which to model archiving systems that facilitate the comprehension of information to the designated community, as well as it also guides on the processes to follow for the accessing of information in the context where it applies. OAIS specification: https://public.ccsds.org/Pubs/650x0m2.pdf'
The specification was initially developed in 2017 with its initial version 1.0. It was used as the basis for the development of European Specifications and building blocks enhancing the development of public services. However, the version analysed is 2.0 which was released by January 2020. For this reason the specification is not sufficiently mature for its use. The specification: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505009
The IETF is a consensus-based group, and authority to act on behalf of the community requires a high degree of consensus and the continued consent of the community. The process of creating and Internet Standard is straightforward: a specification undergoes a period of development and several iterations of review by the Internet community and revision based upon experience, is adopted as a Standard by the appropriate body... and is published. In practice, the process is more complicated, due to (1) the difficulty of creating specifications of high technical quality; (2) the need to consider the interests of all of the affected parties; (3) the importance of establishing widespread community consensus; and (4) the difficulty of evaluating the utility of a particular specification for the Internet community. The goals of the Internet Standards Process are: - Technical excellence; - prior implementation and testing; - clear, concise, and easily understood documentation; - openness and fairness; and - timeliness. The goal of technical competence, the requirement for prior implementation and testing, and the need to allow all interested parties to comment all require significant time and effort. The Internet Standards Process is intended to balance these conflicting goals. The process is believed to be as short and simple as possible without sacrificing technical excellence, thorough testing before adoption of a standard, or openness and fairness. See: https://www.ietf.org/standards/process/
TLS 1.2 is independent of any specification and can be implemented without dependencies with technologies or platforms. Moreover, IETF is a neutral-vendor Standard Developing Organisation that has developed the technical specification independently of any vendor product.
'The purpose of ISAE 3402 is not related to enabling digital service delivery channels, therefore, this criterion is not applicable to this specification. ISAE 3402 handbook reference: https://www.ifac.org/system/files/downloads/b014-2010-iaasb-handbook-isae-3402.pdf'
W3C provides a Markup Validation Service for free to validate CSS, and (X)HTML using style sheets. W3C Markup Validation Service: https://validator.w3.org/ Online CSS validator: https://jigsaw.w3.org/css-validator/
'The ETSI TS 119 512 specification complements ETSI TS 119 511 and specifies protocols for trust service providers providing long-term data preservation services of digital signatures and of general data. Moreover, the preservation service may include a long-term storage, or a temporary storage. Thus, long-term preservation can be guaranteed with long-term storage service of the specification. ETSI TS 119 512 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.02_60/ts_119512v010102p.pdf'
There are document of the European Comission assessing the suitability of XAdES specification. See: https://ec.europa.eu/cefdigital/DSS/webapp-demo/doc/dss-documentation.html#_xades_profiles
There are no Member States recommending EuroVoc in their ICT National Catalogues. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'Several projects, such as "A Prototype Cross-Border GML Data Service," have created new opportunities for integrating cross-border spatial data services using Geography Mark-up Language (GML) and XSLT for schema transformations. Additionally, the INSPIRE Directive and its related regulations form a key cross-border EU initiative, supported by the ISA programme. Schema Translations by XSLT For GML-Encoded Geospatial Data In Heterogeneous Web-Service Environment: https://www.researchgate.net/publication/237698411_SCHEMA_TRANSLATIONS_BY_XSLT_FOR_GML-ENCODED_GEOSPATIAL_DATA_IN_HETEROGENEOUS_WEB-SERVICE_ENVIRONMENT Infrastructure for Spatial Information in Europe: https://ies-svn.jrc.ec.europa.eu/projects/registry-development/wiki/Re3gistry_1_0_documentation#_cp3 '
OpenPM2 offers a set of guidelines and methods for the development of projects and aims to ensure the efficiency and effectiveness from the Project Management perspective. Since it is based on European Union and National Knowledge it can be useful when creating eGovernment innovative solutions. OpenPM2 specification reference: https://op.europa.eu/en/publication-detail/-/publication/ac3e118a-cb6e-11e8-9424-01aa75ed71a1/language-en/format-PDF/source-83307127
' There are assessments that evaluate the efficiency by evaluating digital solutions that involve the specification, as it shows in the following link: ADMS in Joinup: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/adms '
'ETSI EN 319 422 can be applied in any domain and context where the use of time-stamping protocol is realized. Therefore, the specification is usable beyond any business-specific domain and ensures its implementation across business domains. ETSI EN 319 422 reference: https://www.etsi.org/deliver/etsi_en/319400_319499/319422/01.01.01_60/en_319422v010101p.pdf'
'The Semantic Interoperability Community (SEMIC) develops solutions to help European public administrations perform seamless and meaningful cross-border and cross-domain data exchanges. They develop semantic specifications and interoperability solutions under the ISA² Programme. When a new solution release is finished, it is submitted for a public review with a minimum period of four weeks. Specification development process by the ISA Programme: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/document/description-change-management-release-and-publication-process-structural-metadata-specifications Detailed document ISA Programme: https://joinup.ec.europa.eu/sites/default/files/document/2016-10/description_of_a_change_management_release_and_publication_process_for_structural_metadata_specifications_developed_by_the_isa_progr.pdf'
'SCIM plays a foundational role in identity management, and its implementation can contribute to digital service delivery channels. Efficient identity provisioning and management through SCIM can support operations for creating, updating, and deactivating user identities, ensuring that users can quickly access and utilise digital services. SCIM: https://scim.cloud/'
The business domain in which the specification was developed was mainly the legal resources, political/administrative and contract management. It can be applied across sectors since the management of these aspects and the interaction between normative institutions and stakeholders are based and regulated by legal text and resources. LegalRuleML reference: http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/legalruleml-core-spec-v1.0.html
'HTTPS plays a crucial role in ensuring the protection of personal data transmitted over the internet. It provides several key mechanisms that enhance the security and privacy of user that range from encryption to authentication mechanisms in order to prevent data interception and enhance user privacy. HTTPS specification: https://tools.ietf.org/html/rfc2818'
OWL2 is publicly available for implementation and use for free on W3C's webpage. Therefore, it can be reused by the organisations, administrations, open communities, etc. that developed it. OWL2 W3C reference: https://www.w3.org/TR/owl2-overview/
The LegalDocML is available for free at the SDO's webapge but it is also accessible through LEOS project and sofware application documentation, which can be found in joinup. LEOS: https://joinup.ec.europa.eu/collection/justice-law-and-security/solution/leos-open-source-software-editing-legislation LegalRuleML reference: http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/legalruleml-core-spec-v1.0.html
'A Linked Data Event Stream (LDES) is a new data publishing approach which allows you to publish any dataset as a collection of immutable objects. Each object is described in RDF. The focus of an LDES is to allow clients to replicate the history of a dataset and efficiently synchronise with its latest changes. LDES specification: https://joinup.ec.europa.eu/collection/semic-support-centre/linked-data-event-streams-ldes'
There is no conformity test coming from the IETF. However, there are several free online and offline tools to test an SMTP implementation which will prove its compliment. For example, Online Domain Tool, which can test an SMTP mail server implementation. Online Domain Tool: http://mail-server-test.online-domain-tools.com/
'There is only one Member State recommending NUTS in its ICT National Catalogue. This Member State is Ireland. National catalogue Ireland: https://data.gov.ie/pages/opendatatechnicalframework#recommended-standards-for-open-data'
The purpose of IPsec is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification.
'The goal of ETSI TS 119 511 is to provide the legal framework for the conformity of the Electronic Signatures against European regulations. ETSI TS 119 511 cannot be understood without its companion documents, insofar the suite of specifications ESI forms the basis for the conformity assessment of trust services following the eIDAS regulation. ETSI TS 119 511 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119511/01.01.01_60/ts_119511v010101p.pdf'
'After researching there has been no success finding any assessments about the specification effectiveness. How the specification can help ensuring trustworthiness of information: https://script-ed.org/article/blockchain-based-electronic-time-stamps-and-the-eidas-regulation-the-best-of-both-worlds/'
'ETSI, the SDO/SSO that created and currently maintains the specification, explains that most ETSI test specifications are developed according to the well-proven methodology defined in ISO/IEC 9646. This standard, which covers the entire test development process, provides an excellent basis for the production of high-quality test frameworks and specifications. ETSI Conformance Testing: https://portal.etsi.org/Services/Centre-for-Testing-Interoperability/ETSI-Approach/Conformance ISO/IEC 9646: https://www.iso.org/standard/17473.html'
The implementation of the specification fosters interoperability between administrations across borders. Moreover, it is a European interoperability solution component included in the eDelivery building block. The purpose of the building block is to enhance the eGovernment in the context of the interoperability and the reuse of administrations’ data.
'The ESPD has not been found included in the catalogue of any Member State. CAMSS List of standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards NIFO factsheets: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public-administration-factsheets-2022'
CAdES has sufficient market acceptance for its use in the development of products. In the following link there is an example of integrating digital signatures like CAdES in a framework. Digital signature service: https://ec.europa.eu/cefdigital/DSS/webapp-demo/doc/dss-documentation.html
OpenPM2 is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, OpenPM2 can define the interoperability aspects of the "Service Delivery Model" ABBs of the EIRA Organisational View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/v100
HTTP has ben in use by the World-Wide Web global information initiative since 1990. That fact evidences that the standard has the sufficient market acceptance and is sufficiently maturity. See: https://tools.ietf.org/html/rfc2616
In the maintenance and development process that the Publications Office has developed there is no public consultation foreseen in the development process of the specification. However, it is worth to note that users can contribute to a previous phase. EuroVoc https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/eurovoc
'DIDs is used in Self-sovereign identity (SSI) in eIDAS project. This, is the next step beyond user-centric identity. Both concepts are based on the idea that a user must be central to the administration of his/her digital identity, which requires not only a user’s ability to use an identity across multiple locations but also true control over that digital identity, creating user autonomy. SSI eIDAS: https://joinup.ec.europa.eu/collection/ssi-eidas-bridge'
'SFIA is already associated with EIRA ABBs in the EIRA Library Of Specifications (ELIS). More specifically, the specification can define the interoperability aspects of the Interoperability Skill ABB of the EIRA Organisational View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /solution/elis/release/v110 '
"JSON is a specification used for data exchange between different platforms, this fact facilitates the visibility and comprehensibility of administration's data. Moreover, it eases the communication between administrations enhancing the decision-making process. JSON specification: https://www.ecma-international.org/wp-content/uploads/ECMA-404_2nd_edition_december_2017.pdf"
'DPV enables expressing machine-readable metadata about use and processing of personal data based on legislative requirements such as the GDPR. Modelling of the GDPR concepts by the DPV contributes to the once-only principle given that it is meant to be an interoperable vocabulary for representing information about the use and processing of personal data. DPV specification: https://w3c.github.io/dpv/dpv/ DPV primer document: https://w3c.github.io/dpv/primer/#introduction'
'The purpose of GraphQL is not related to enabling the secure processing of data. Therefore, this criterion is not applicable to this specification. GraphQL specification: https://spec.graphql.org/October2021/#sec-Overview'
'NIST asserts rights outside of the United States. The public is granted the non-exclusive, perpetual, paid-up, royalty-free, worldwide right to reprint works in all formats, including print, electronically, and online, and in all subsequent editions and derivative works. NIST IRP and F/RAND principles: https://www.nist.gov/open/copyright-fair-use-and-licensing-statements-srd-data-software-and-technical-series-publications#:~:text=To%20the%20extent%20NIST%20may%20assert%20rights%20outside,and%20in%20all%20subsequent%20editions%2C%20and%20derivative%20works. AES Standard Reference: https://csrc.nist.gov/pubs/fips/197/final'
'The purpose of Core Location Vocabulary is not related to ensure the protection of personal data managed by Public Administrations. Therefore this criterion is considered not applicable to the specification. Core Location Vocabulary: https://interoperable-europe.ec.europa.eu/collection/semic-support-centre/solution/core-location-vocabulary/release/100'
After carrying out information retrieval, no document or study has been found assessing the CPOV in terms of efficiency or effectiveness.
'The purpose of HTTPS is not related to the modelling of business processes. Therefore this criterion is not applicable to the specification. HTTPS specification: https://tools.ietf.org/html/rfc2818'
'The purpose of NFVI is not related to e-accessibility. Therefore, this criterion is considered not applicable to this specification. NFVI Deliver, Infrastructure Overview section 4: https://www.etsi.org/deliver/etsi_gs/NFV-INF/001_099/001/01.01.01_60/'
'OSI is independent of any platform and can be implemented without dependencies with technologies. Furthermore, OSI is designed to support information system interconnection, enhancing interoperability by definition. OSI reference https://www.iso.org/standard/20269.html'
'NUTS is included within a national catalogue of recommended specifications. It belongs to Ireland. The National Interoperability Framework (NIF) of this Member State is partially aligned with the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. There is middle-low performance in the Interopearability Governance, Legal and Organisational layers, and there exist some shorcuts in the Conceptual Model with regards to Internal Information sources and services, Base Registries and the conceptual model, compared to the EU average. National catalogue Ireland: https://data.gov.ie/pages/opendatatechnicalframework#recommended-standards-for-open-data NIFO factsheets: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public-administration-factsheets-2021'
'The purpose of TSP is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification. TSP IETF reference: https://tools.ietf.org/html/rfc3161'
One of the main purposes of the specification and the OASIS TC in charge of its development is to be extensible, that is to allow modifications to the models within the AKOMA NTOSO framework so that local customisation can be achieved without sacrificing interoperability with other systems. Moreover, the European Commission includes in its Rolling Plan for ICT Standardisation and the related standardisation activities of the same rolling plan. Referencing it as a good candidate to support the eGovernment. LegalDocML reference: https://www.oasis-open.org/committees/legaldocml/charter.php
'XACML is the basis of the Policy Management impelemented by the cross-border project SEMIRAMIS. This project aims to provide e-services with the required underlying secure authentication and management approach. Semiramis home page: https://joinup.ec.europa.eu/solution/semiramis/about'
"The specification is included in 9 Member States' catalogues of recommended specifications. This Member States are Cyrpus, Estonia, France, Germany, Greece, Norway, Poland, Slovenia and Spain. National Catalogue of Cyprus: https://dits.dmrid.gov.cy/dmrid/dits/dits.nsf/all/B83AA8E4EB4EFD19C225855800288B10/$file/Cyprus% 20eGovernment%20Interoperability%20Framework_new%20EIF_v2.0-To%20Publish.pdf National Catalogue of Spain: https://administracionelectronica.gob.es/pae_Home/pae_Estrategias/pae_Interoperabilidad_Inicio /pae_Normas_tecnicas_de_interoperabilidad.html#CATALOGOESTANDARES CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards"
Even though no explicit evidence has been found of any implementation of the ODF at the European Level, there are several recommendations from the EC and member states for the usage of the specification when sharing or collaborating between and with administrations. No formal project has been found where ODF is used for this purpose. EC recommends supporting open document format: https://joinup.ec.europa.eu/collection/open-source-observatory-osor/news/ec-recommends-supporting-open UK Sharing and collaborating with government documents https://www.gov.uk/government/publications/open-standards-for-government/sharing-or-collaborating-with-government-documents
'OAIS reference model provides means for the restriction of access to information or data through its access control mechanisms. Access controls are a fundamental part of the OAIS architecture, and they allow archive managers to control who has access to the digital objects and metadata stored in the system. OAIS specification: https://public.ccsds.org/Pubs/650x0m2.pdf'
At the time of elaborating this assessment, this specification is not included in any EIRA ABB in the current EIRA Library Of Interoperability Specifications (ELIS)._x000D_ _x000D_ EIRA Library of Interoperability Specifications (ELIS):_x000D_ https://joinup.ec.europa.eu/solution/elis/release/v100
'Changes to the YAML language itself will be made using a Requrest For Comments (RFC) process. The project has an active core team but they do all changes publicly and take some direction from issues and pull requests. Despite this, the working group is still working out the final details of this process, so for now there are no details about how it will be this public review. Contribution to YAML: https://github.com/yaml/yaml-spec/blob/main/.github/contributing.md'
'ETSI TS 119 512 specifies policy and security protocols for trust service providers providing long-term preservation of digital signatures and of general data using digital signature techniques. The specification performance is closely related to the different specifications involved in electronic signatures across borders. In the context of the European internal market (see article below) , it can be considered as an asset for the creation of solutions enhancing the interoperability between administrations and businesses when eSignature, and long preservation of electronic records is needed. ETSI TS 119 512 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.02_60/ts_119512v010102p.pdf ETSI TS 119 512 Working group: https://portal.etsi.org/webapp/workprogram/Report_WorkItem.asp?WKI_ID=61427 Article: Towards a standardised preservation service for qualified electronic signatures and qualified electronic seals: https://dl.gi.de/bitstream/handle/20.500.12116/20980/proceedings-01.pdf?sequence=1&isAllowed=y'
OpenPM2 was developed with the purpose to support the development of projects within European Institutions and to ensure maximum efficiency and effectiveness. Currently, it is used for the development of a huge variety of projects underlying from the different General Directories, concretely the DIGIT, who is the corporate author. The fact of being a tool used for European Institutions for the development of different types of projects ensures its market acceptance and usefulness for developing products and services, specifically public ones. OpenPM2 specification reference: https://op.europa.eu/en/publication-detail/-/publication/ac3e118a-cb6e-11e8-9424-01aa75ed71a1/language-en/format-PDF/source-83307127
'NUTS is intended to serve as a device to identify administrative zones in the EU and non-EU regions. There is no possibility to extend the coding system as NUTS was conceived for a unique purpose. EUROSTAT reference, NUTS Principles and Characteristics section: https://ec.europa.eu/eurostat/web/nuts/principles-and-characteristics'
The RDA specifications address and will facilitate interoperability between public administrations and repositories, public and private providers. The 4 specifications listed here as well as the others in the evaluation process are all components necessary and essential for data sharing, access, re-use, preservation, citation, etc. All of them contribute to data interoperability in the new digital economy irrespective of the organisation who implements / uses them.
'The PROV family of documents provides a general-purpose framework for representing and exchanging provenance information, which can be applied across various domains and industries. Therefore they are domain-agnostic. PROV Primer document: https://www.w3.org/TR/prov-primer/'
'GITB TDL is a language created to express test cases against any given specification. Therefore it can be used in any domain. JOINUP reference: https://joinup.ec.europa.eu/collection/interoperability-test-bed-repository/solution/interoperability-test-bed/detailed-information#domainagnostic'
'ETSI TS 119 612 is part of the Electronic Signatures and Infrastructure (ESI) family of specifications and is dependent on some of the protocols and semantics they convey, therefore, this specification is not technology agnostic (See Annex B for an example). ETSI TS 119 612: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf'
'The flexible approach of UBL makes it an adaptable specification, that can change based on future business and administrative needs, therefore supporting the evolution of European Public Services. UBL v2.3 reference: http://docs.oasis-open.org/ubl/os-UBL-2.3/UBL-2.3.html'
After carrying out an exhaustive search concerning LegalDocML validation, conformance and certification, no tool has been found available for free for these purposes.
'IPv4 is a sector agnostic specification that allows its implementation independently form the business domain. IPv4 domain-agostic reference: https://link.springer.com/chapter/10.1007/978-1-4842-8603-6_3'
HTTPS was adopted as web standard in May 2000 by IETF. Moreover, Google is promoting the usage of HTTPS for the improvement of security in terms of transfer data. In the latest report of Google about the usage of HTTPS, it shows that the usage of HTTPS is increasing significantly. See: https://transparencyreport.google.com/https/overview?hl=en
'TLS 1.3 restricts access at the connection establishment phase by verifying the identities of the communicating peers. Once a secure and authenticated connection is established, TLS 1.3 ensures the confidentiality and integrity of the data exchanged within that session. TLS 1.3 Reference: https://www.rfc-editor.org/rfc/rfc8446.html'
TIFF fosters the interoperability between systems by having a TIFF Tag Interoperability IFD (Image File Directory) which has multiple tags that store the information to ensure the Interoperability. TIFF Tag Interoperability IFD reference: https://www.awaresystems.be/imaging/tiff/tifftags/interoperabilityifd.html
'The ETSI and any of its committees, in charge of the development of ETSI TS 119 614-1, operates under the ETSI Intellectual Property Rights (IPRs) and IPR Policy. The specification is licensed on a royalty-free basis. Intellectual Property Rights Policy, ETSI ownership of IPRs section: https://www.etsi.org/intellectual-property-rights'
XSLT has an open-source framework processor (XT-Speedo), so it is independent from any technology or platform.
The specification is included in 10 Member States' catalogues of recommended specifications. Some examples of Member States including XSD on their catalogues are the Netherlands, Slovenia, Spain or Portugal. See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
"The Syslog Protocol standard is maintained by the Internet Engineering Task Force (IETF). The development and maintenance of The Syslog protocol is carried out within the IETF's Syslog working group, which can be contacted according to section 10 of the protocol. IETF Working Groups: https://www.ietf.org/how/wgs/ Syslog Protocol Working Group: https://datatracker.ietf.org/doc/html/rfc5424#section-10"
'Registered Organization Vocabulary provides a standardised vocabulary for describing organisations, facilitating data exchange and interoperability, particularly within the European context. Its successor, CBV, is now the more actively supported specification for this purpose, encouraging data sharing and the creation of communities on national and European platforms. Registered Organization Vocabulary specification reference: https://www.w3.org/TR/vocab-regorg/ CBV GitHub Reference: https://github.com/SEMICeu/Core-Business-Vocabulary'
'CPSV-AP is independent of any software, hardware, or operating system. So it can be said that the specification is independent of any specific technology or platform. CPSV-AP Joinup webpage: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/core-public-service-vocabulary-application-profile/release/22'
'SCIM encourages collaboration in the realm of identity management as it was created by IETF, a non-profit and open organisation dedicated to standardisation. IETF encourages collaborative efforts that extend beyond the specifications themselves and include discussions, forums, and knowledge-sharing platforms where users can exchange ideas, experiences, and best practices related to SCIM. For instance, IETF has created discussions lists for their specifications that improve the development and specification of Internet technology through the general discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist. SCIM: https://scim.cloud/ IETF Discussion Lists: https://www.ietf.org/how/lists/discussion/'
There are no Member States recommending LegalRuleML in their ICT National Catalogues. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
"According to the schema.org project website, the schema.org specification provides a specific vocabulary that can be used by applications that publish, discover or integrate various types of data. Although the main purpose of schema.org is not related to data preservation, the specification can enable long-term preservation of data through additional file export mechanisms or by integrating schema.org into other data markup schemes (see Zotero reference, Forums section) that enable data preservation.. Schema.org homepage reference, 'Data and Datasets overview' section: https://schema.org/docs/data-and-datasets.html Zotero reference, Forums section: https://forums.zotero.org/discussion/35992/export-to-schema-org-rdfa-and-or-microdata"
'ETSI EN 319 532-3 ensures the protection of data due to a new object (according to the REM message structure) generated by the REM Service enclosing the original message and other contents generated by the REM Service, who is responsible only for part of its contents (it is not responsible for the contents of the original message). If Trusted List (TL) is used to publish trust information about a REMS, then the section describing a REM service shall be populated in conformance to ETSI TS 119 612. ETSI EN 319 532-3, Message/Dispatch, Page 9 and Page 25: https://www.etsi.org/deliver/etsi_en/319500_319599/31953203/01.02.01_60/en_31953203v010201p.pdf'
CLV is not included in any Member States' catalogues of recommended specifications. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'ETSI EN 319 422 does simplify European public services by making the process of time-stamping secure by the side of both client and server. ETSI EN 319 422 reference: https://www.etsi.org/deliver/etsi_en/319400_319499/319422/01.01.01_60/en_319422v010101p.pdf'
'The purpose of genericode is not related to ensuring the protection of personal data. Therefore, this criterion is considered not applicable to this specification. Code List Representation (genericode): https://docs.oasis-open.org/codelist/genericode/v1.0/os/genericode-v1.0-os.html'
'OAIS has not been found in any initative covering privacy aspects neither at national, nor at European level. OAIS specification: https://public.ccsds.org/Pubs/650x0m2.pdf'
Even HTML 5 is fostering the first level of maturity provided by Tim Berners-Lee's 5 stars schema for publication of Open data, it is not supports the principles to be considered as fostering actor on pubilishing Linked Open Data.
OASIS has defined a clear process where all the stakeholders involved have the opportunity to participate in the development of the specification development process. Moreover, there is a public review in the TC process. OASIS guideline: https://www.oasis-open.org/policies-guidelines/tc-process-2017-05-26 The Akoma Ntoso review process: http://www.akomantoso.org/?p=141
'Linked Data Event Streams could be used to maintain and open up reference datasets to foster interoperability by advocating the reuse of the identifiers for which they are the authoritative source. LDES provides a robust framework to ensure that data can be easily shared, understood and used across systems. Therefore, it could contribute to enabling data portability. LDES specification: https://joinup.ec.europa.eu/collection/semic-support-centre/linked-data-event-streams-ldes'
'The current version of the specification was released back in 2018 and has been tested with real implementors to demonstrate its usefulness and application. For certain industries and scenarios, ODRL has been successfully implemented to manage digital rights and permissions effectively. It is particularly well suited for applications involving content distribution, intellectual property management, and digital rights management. W3C specification: https://www.w3.org/TR/odrl-vocab/#vocab-core W3C Working Group Github space: https://github.com/w3c/odrl'
'The specification is not related to the publication of public data as open data. Therefore this criterion is not applicable to this specification. IPv6 IETF: https://www.rfc-editor.org/rfc/rfc2460'
'This specification provides a message format that allows vendor-specific extensions to be provided in a structured way. Structured data is a feature introduced in the syslog protocol that enables the inclusion of additional, machine-readable information within syslog messages. This mechanism allows for extensibility, as custom key-value pairs can be added to provide supplementary context or metadata related to the log event. Syslog Protocol: https://datatracker.ietf.org/doc/html/rfc5424'
'There are already existing documents and studies about the XACML performance in different environments. The research article "Approaches for Testing and Evaluation of XACML Policies" concentrates on the examination of XACML policies, offering various methods to enhance their efficiency. Approaches for Testing and Evaluation of XACML Policies: https://www.researchgate.net/publication /279192661_Approaches_for_Testing_and_Evaluation_of_XACML_Policies'
Like all the IETF standards, IPv6 is a free and open technical specification, built on IETF standards and licenses from the Open Web Foundation. IPv6 is therefore licensed on a royalty-free basis. See: https://tools.ietf.org/html/rfc3668
By providing a standardised method for the description of legal entities, RegOrg helps to ensure that the information provided and exchanged is properly structured. At this point, it helps the trustworthy data exchange between citizens and businesses, and administrations. RegOrg Joinup reference: https://joinup.ec.europa.eu/solution/registered-organization-vocabulary
EuroVoc is used for the EU Open Data Portal, the site where EU Institutions publish their datasets for their reuse. In there, it is also used the classification of EuroVoc in order to improve the shareability, researchability and interoperability when processing the data. It helps to link data under knowledge domains. EuroVoc webpage: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/eurovoc 5-star linked open data: https://www.w3.org/DesignIssues/LinkedData.html
'Verifiable Credentials was included in the European Blockchain Services Infrastructure (EBSI), the first pan-European, public-driven blockchain initiative of its kind. EBSI VC/VP data models build upon W3C Verifiable Credentials, which defines the standard way to present credentials/certificates on the internet in a common digital way, improving the efficiency, interoperability, and readability of all documents/certificates. Verifiable Credentials Privacy Considerations: https://www.w3.org/TR/vc-data-model/#privacy-considerations'
'As it is mentioned in the specification's documentation, ETSI TS 119 612 allows the extension in various parts, such as Scheme, TSP and XML Schemas. This can be checked out in the section "5.3.17 Scheme extensions". ETSI TS 119 612 specification: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf '
'Although the Indexed Database API is not itself customisable, some elements can be modified. For example, object stores, which are the primary storage for data in a database, can be changed. Indexed Database API: https://www.w3.org/TR/IndexedDB/'
'The purpose of TSP is not related to organisational interoperability. Therefore, this criterion is not applicable to the specification. TSP IETF reference: https://tools.ietf.org/html/rfc3161'
'There are platforms for sharing results, information, and discussing IPsec. One of these platforms, where people can discuss implementations and new versions of IPsec, is the Netgate forum. Many entries addressing issues with implementing IPsec and discussions about IPsec can be found there. In addition, IPsec is also available in the Joinup repository (Interoperable Europe Portal). Netgate IPsec forum: https://forum.netgate.com/category/17/ipsec'
'WSDL, as a specification, does not inherently address administrative procedures, rules, or data visibility. Its main purpose is to facilitate the interoperability of web services by defining the contract between the service provider and the service consumer. W3C WSDL specification: https://www.w3.org/TR/wsdl20/'
'ISO/IEC 27001 is structured to be compatible with other management system standards, such as ISO 9001 and is technology and vendor neutral, meaning that it is completely independent of the IT platform. ISO 27001 reference: https://www.iso.org/obp/ui/#iso:std:iso-iec:27001:ed-2:v1:en'
"Currently there is widespread use of the specification in the context of industrial manufacturing, in this sense the groups Bosch and Siemens have dedicated efforts in the spread of the specification among it's members. Bosch review: https://www.boschrexroth.com/en/dc/asset-administration-shell-unlocking-the-power-of-data/ Siemens review: https://www.marketscreener.com/quote/stock/SIEMENS-AG-56358595/news/Siemens-Nine-partners-demonstrate-an-interoperable-digital-twin-based-on-the-Asset-Administration-43543391/ Details of the Asset Administration Shell (AAS) https://industrialdigitaltwin.org/en/wp-content/uploads/sites/2/2024/06/IDTA-01001-3-0-1_SpecificationAssetAdministrationShell_Part1_Metamodel.pdf"
'The purpose of FTP is not related to the delivery of multilingual European public services. Therefore this criterion is considered not applicable specification. FTP Specification Reference: https://datatracker.ietf.org/doc/html/rfc959'
Even though at the moment of elaborating the assessment the specification is widely used, no evidence has been found to demonstrate the specification can be used on the development of innovative solutions.
After carrying out an exhaustive research, no evidence has been found of an established agreement between organisations involved in European public services provision.
The purpose of XAdES is not related to e-accessibility. Therefore, this criterion is considered not applicable to this specification. XAdES ISO reference: https://www.iso.org/standard/56025.html XAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/101900_101999/101903/01.04.02_60/ts_101903v010402p.pdf
EuroVoc is a public asset developed by a European Institution and can be accessed and reused without any payment conditions. Therefore, it can be considered that the specification is licensed under royalty-free basis and (F)RAND basis. EuroVoc reference: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/eurovoc
The purpose of TLS 1.2 is to provide communication security regarding privacy and data integrity. It can be concluded that TLS 1.2 collaborates in a way to proper data portability.
'The Dataspace Protocol enables the interaction between participants of a Dataspace. All data follows a series of requirements so that they can be reused as needed. The Dataspace Information Model, which forms the foundation of this specification, enables the interaction between participants of a Dataspace and specifies how they should do it in the most effective and efficient way. IDSA Dataspace Protocol Information Model: https://docs.internationaldataspaces.org/ids-knowledgebase/v/dataspace-protocol/overview/model'
"Assessments of the efficiency of DNS over HTTPS (DoH) primarily involve evaluating the performance, scalability, and practicality of implementations. For instance, a 2020-paper related to the 3rd International Conference on Information and Computer Technologies (ICICT) describes the impact of DoH on cyber systems. The assessment explains that DoH is one of the latest enhancements implemented to address security against malware and other vulnerabilities, which proves the specification's efficiency. On the Impact of DNS Over HTTPS Paradigm on Cyber Systems: https://ieeexplore.ieee.org/abstract/document/9092077"
The purpose of the specification is not related to the publication of data as linked open data. Therefore, this criterion is not applicable for this criterion.
The purpose of SOAP 1.2 is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification.
SMTP can be implemented in any platform and it is independent of any technology. SMTP IETF reference: https://tools.ietf.org/html/rfc5321
The purpose of LDAP is not related to e-accessibility. Therefore, this criterion is considered not applicable specification. LDAP IETF reference: https://tools.ietf.org/html/rfc4511
UTF-8 was launched at the beginning of 2000s, and currently is one of the three encoding methods recognised by Unicode or web languages. It demonstrates the maturity and the market acceptance for development of products and services. See: https://w3techs.com/technologies/overview/character_encoding/all
'The SMP specification describes also the binding of the specification with the REST interfaces for the Service Metadata Publication within a 4-Corner network. Therefore, the specification fosters the availability of interfaces containing information from the different parties involved in a 4-corner network. Specification Reference, section 5 mentioning REST binding: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505042'
'Users can create domain-specific extensions or profiles of DQV that focus on particular domains or industries. These extensions can include domain-specific terminology, quality metrics, and constraints that are not covered by the core DQV vocabulary. By defining domain-specific extensions, users can ensure that DQV aligns with the terminology and requirements of their particular domain. Data Quality Vocabulary: https://www.w3.org/TR/vocab-dqv/'
"WAI-ARIA is not included in any Member States' catalogues of recommended specifications. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards"
DCAT-AP does no directly help for the provision of application programming interfaces (APIs) or Web services. However, DCAT-AP aims to ensure consistency by providing a standard description of the catalogues and datasets published by data portals across Europe. This description makes datasets more searchable and accessible for data reusers and encourages the data providers to use open data portals for dissemination of reusable data.
'While OpenTelemetry is not directly related to enabling the secure processing of data, OTel configuration should ensure sensitive configuration information is managed securely. Sensitive information should be stored securely such as on an encrypted filesystem or secret store. Environment variables can be used to handle sensitive and non-sensitive data as the Collector must support environment variable expansion. In addition, the Collector should be configured to obfuscate or scrub sensitive data before exporting. OTel Security Best Practices: https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/security-best-practices.md'
The OASIS TC in charge of LegalDocML operates under the Royalty Free on Limited Terms IPR mode as defined in the OASIS Intellectual Property Rights (IPR) Policy. LegalDocML reference: https://www.oasis-open.org/committees/legaldocml/charter.php
Although PDF/A supports the first level of maturity from the Tim Berners-Lee 5-star schema for the Open data, it is not supporting the main principles for the publication of data as Linked Open Data. PDF/A reference: https://www.iso.org/standard/38920.html https://www.iso.org/standard/50655.html 5-star linked open data: https://www.w3.org/DesignIssues/LinkedData.html
'By defining schemas for XML documents, which are involved in the data exchange across borders, XSD utilizes a limited reuse and implementation of the once-only principle. XSD Reference: https://www.w3.org/TR/2012/REC-xmlschema11-1-20120405/'
The purpose of EuroVoc is not related to security and privacy of the data exchange. Therefore, this criterion is not applicable to this specification. EuroVoc webpage: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/eurovoc
CAMSS Assessment of EuroVoc EIF Scenario v1.0.0
The OpenPM2 is the open version of the Project Management Methodology developed by the Commission back in 2007 and that has been evolving according to the experience gained over time. Within the PM2 Alliance, different stakeholders have the opportunity to contribute to the development of the specification in the different domains. PM2 alliance and advisory committees: https://www.pm2alliance.eu/advisory-committees/
'The purpopse of Indexed Database API is not related to enabling the visibility of administrative procedures, rules data, and services. Therefore this criterion is not applicable to the specification. Indexed Database API: https://www.w3.org/TR/IndexedDB/'
"DNS facilitates the visibility of public administrations. As an example of ensuring their visibility, DNS might enhance the transparency of public administrations' networks. The European Commission is developing its own DNS service, the DNS4EU, which will allow the access to global Internet and will comply with EU regulations. DNS IETF reference: https://tools.ietf.org/html/1034 Domain Names - Implementation and Specification: https://tools.ietf.org/html/1035 "
CSV is a commonly used format for data exchange. It allows to provide data in a simple way. Moreover, as is structured data and non-proprietary format it eases data consumption by different stakeholders. An example of initiative relaying on CSV to provide data to users is ESCO, that allows the download data sets in CSV format. See: https://ec.europa.eu/esco/portal/escopedia/Comma-separated_values__40_CSV_41_#ESCO_data_in_CSV_files
DNS is widely used for EU cross-border projects. For instance, it is used by TESTA, the data communication network service operated by the European Commission. See: https://ec.europa.eu/isa2/sites/isa/files/testa_overview_-_july_2018.pdf
'TOSCA does not allow for partial implementation. In fact, the Cloud Service ARchive (CSAR) is an archive format that is meant to guarantee the availability of all specification artefacts as well as the successful execution of services. In other words, in order to support the execution and lifecycle management of a cloud application in a given environment, all corresponding artefacts have to be available in that environment, preventing partial implementation. TOSCA reference, Cloud Service Archive (CSAR) reference: https://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.3/os/TOSCA-Simple-Profile-YAML-v1.3-os.html#_Toc26969474'
PAdES is a set of restrictions and extensions to PDF and ISO 32000-1 making it suitable for advanced electronic signatures. One profile of PAdES is PAdES-LTV (Long Term Validation), it is a signature conformant which has one or more long-term-validation attributes that guarantee the preservation of the authenticity of the signature. PAdES ISO reference: https://www.iso.org/standard/67937.html PAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/102700_102799/10277801/01.01.01_60/ts_10277801v010101p.pdf
'With a REST protocol you can do the following operations with data POST (creation), GET, PUT, DELETE. So in some way, it facilitates the publication of public data as open data. See this link for the justification: https://www.bbvaapimarket.com/es/mundo-api/api-rest-que-es-y-cuales-son-sus-ventajas-en-el-desarrollo-de-proyectos/ '
'Section 9 from the TGF specification defines some conformance statements that indicate whether, and if so to what extent, each of the patterns and requirements described is to be used in a conformant transformational government program. TGF specification: http://docs.oasis-open.org/tgf/TGF/v2.0/cs01/TGF-v2.0-cs01.html'
As it happens with all the e-Government Vocabularies, it has the SEMIC action from the ISA2 as responsible for the maintenance of the development. SEMIC in Joinup: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic
'As a vocabulary to describe assets within a Repository, it provides concepts and properties identifying the content creators and other informative metadata such as dates involved in the release of the solutions described. These facts increase the reliability of the exchanged data. ADMS Specification W3C: https://www.w3.org/TR/vocab-adms/'
'OASIS has defined a clear Technical Committee (hereby TC) process where all the stakeholders involved have the opportunity to participate in the development of the specification development process. OASIS guideline: https://www.oasis-open.org/policies-guidelines/tc-process-2017-05-26'
The purpose of PDF 1.7 is not related to organisational interoperability. Therefore, this criterion is not applicable to the specification.
'CPSV-AP is a reusable and extensible data model for harmonising the way public services are described in a machine-readable format. So it describes the public administrations and eases their visualisation and comprehensibility. An example to clarify this past point is the CPSV-AP Mapping Editor, which allows European public administrations to create mappings for harmonising the different data models used to describe public services, either within a country or across borders. CPSV-AP Joinup webpage: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/core-public-service-vocabulary-application-profile/release/22 CPSV-AP Mapping Editor reference: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/cpsv-ap-mapping-editor'
'There are existing studies assessing the efficiency of DNS. Particularly, there seems to be a general interest on the efficiency of DNS security extension mechanisms, and on the DNS Tunneling tools. Exploring Domain Name-Based Features on the Effectiveness of DNS Caching: https://ccronline.sigcomm.org/wp-content/uploads/2017/01/p36-hao.pdf A Comparative Performance Evaluation of DNS Tunneling Tools: https://www.researchgate.net/profile/Alessio_Merlo/publication/221271469_A_Comparative_Performance_Evaluation_of_DNS_Tunneling_Tools/links/00b4951c1e5065b0e6000000/A-Comparative-Performance-Evaluation-of-DNS-Tunneling-Tools.pdf Performance assessment and analysis ofDNS tunneling tools: https://www.researchgate.net/publication/235996771_Performance_assessment_and_analysis_of_DNS_tunneling_tools A survey of domain name system vulnerabilities and attacks: https://www.researchgate.net/publication/345017736_A_survey_of_domain_name_system_vulnerabilities_and_attacks '
PNG is a business domain agnostic specification that can be reused in a cross-domain way. PNG W3C reference: https://www.w3.org/TR/PNG/
"Although the NFVI specification went through a modification in the context of the third NFV release (see NFV Release 3 Reliability, section 6.3.3.4), this specification assesses its conformance following predefined methods for pre-deployment testing of NFV functional components (see NFV Release 3 Reliability, subsection 6.5.3). These methods are manually applied. NFV Release 3 Reliability, 'NFV-REL 006v3.1.1 - GS - SW Upgrade spec.pdf' document: https://docbox.etsi.org/ISG/NFV/Open/Publications_pdf/Specs-Reports"
'W3C provides a Markup Validation Service for free to validate Web documents including XHTML implementations. W3C Markup Validation Service: https://validator.w3.org/'
'Even though the purpose of this specification is not related to the protection against unauthorised changes directly, LDES inherently helps maintain data integrity through the immutability of events, a principle that allows keeping track of data alterations. LDES specification: https://joinup.ec.europa.eu/collection/semic-support-centre/linked-data-event-streams-ldes'
'DNS Queries over HTTPS (DoH) is recommended by the Spanish Agency of Data Protection. According to this public institution, to provide confidentiality in DNS queries, different alternatives have been developed, including DNS over TLS (DoT) and DNS over HTTPS (DoH). Both solutions are designed to mitigate the risk that DNS queries can be intercepted, and if they are that the information is illegible, contributing to improve confidentiality. AEPD Technical Note on DNS Privacy: https://www.aepd.es/guides/technical-note-dns-privacy.pdf'
'While XACML provides robust mechanisms for access control based on authenticated attributes, the specification itself does not directly handle the authentication of users or guarantee the authenticity of the roles and agents involved in data transactions. However, the specification provides features that in combination with other specifications enhances authentication methods. XACML OASIS reference: https://docs.oasis-open.org/xacml/3.0/xacml-3.0-core-spec-os-en.html'
ELI is a public asset developed by a European Institution with the participation of interested parties like the Member States. To foster the implementation across public administrations it can be accessed for free without any payment restrictions. Therefore, it can be considered that the specification is licensed under royalty-free basis and (F)RAND basis. ELI reference: https://eur-lex.europa.eu/eli-register/about.html
'The Indexed Database API specification does not make specific provisions for partial implementations. However, it is mentioned that some operations can be performed separately. In this context, different operations can be found, such as index retrieval operations or object store retrieval operations, which can be utilised separately. Indexed Database API: https://www.w3.org/TR/IndexedDB/'
"NUTS releases do not foresee public reviews. Any amendment to the NUTS classification is a Member States' competence (see European Commission reference, Regulation (EC) No 1059/2003 document, provision 13). In case of any revision concerning the NUTS classification, the Member State in question has to replace historical data set by time series according to the new classification within a two-years period (see European Commission reference, Regulation (EC) No 1059/2003 document, Article 2(5)). EU adoption of the new classification and its duration are subject to a feasibility evaluation. EUROSTAT reference, History of NUTS section: https://ec.europa.eu/eurostat/web/nuts/history European Commission reference, Regulation (EC) No 1059/2003 document, provision 13: https://eur-lex.europa.eu/legal-content/EN/TXT/?qid=1405939838475&uri=CELEX:32003R1059"
'ISO 639-2 has been extensively used in the library industry and can also be used for any domain that requires the expression of language in codes. The EU Official Language codelist and the SCL-language classification provides the outline of standard code lists for languages in Europe. They draw on the ISO 639-2 alpha3 codes (among others) with a focus on European languages. ISO 369-2 FAQs: https://www.loc.gov/standards/iso639-2/faq.html#5 Language codelist reference: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/language SCL-languages referece: https://joinup.ec.europa.eu/collection/eu-semantic-interoperability-catalogue/solution/scl-languages?f%5B0%5D=solution_content_bundle%3Aasset_distribution'
'DCAT is a W3C standard, indicating its endorsement and support by the W3C organisation. As a result, the specification is subject to ongoing management and maintenance by the W3C. DCAT (v2.0.0) reference: https://www.w3.org/TR/vocab-dcat-2/ '
'The Internet Protocol is a necessary specification for the implementation of the once-only-principle as it allows cross-border communications over the internet. For example, the mobile IPv6 protocol provides mobility support for IPv6. It allows you to keep the same internet address all over the world, and allows applications using that address to maintain transport and upper-layer connections when changing locations. IPv6 IETF: https://www.rfc-editor.org/rfc/rfc2460 Mobile IPv6 protocol: https://www.ibm.com/docs/en/aix/7.1?topic=protocol-mobile-ipv6'
'GraphQL has the mutation functionality. However, despite the fact that there are some extensions for GraphQL to query linked open data (GraphQL-LD), there has not been found any evidence proving the capacity of the specification to publish open data. GraphQL specification: https://graphql.org/learn/schema/ GraphQL-LD: https://comunica.github.io/Article-ISWC2018-Demo-GraphQlLD'
"The establishment and implementation of an organization’s information security management system is influenced by the organization’s needs and objectives, security requirements, the organizational processes used and the size and structure of the organization. All of these influencing factors are expected to change over time. ISO/IEC 27001, therefore, is designed to be implemented in accordance of any given organization's needs, allowing its customisation. ISO 27001 reference: https://www.iso.org/obp/ui/#iso:std:iso-iec:27001:ed-2:v1:en"
"The motivation of DPV is to provide a 'data model' or a 'taxonomy' of concepts that act as a vocabulary for the interoperable representation and exchange of information about personal data and its processing. DPV specification: https://w3c.github.io/dpv/dpv/ DPV primer document: https://w3c.github.io/dpv/primer/#introduction"
'Joinup offers several services that aim to help e-Government professionals share their experience with each other. Joinup supports them to find, choose, re-use, develop and implement interoperability solutions. DIDs appears in many Joinup entries as a discussion topic. Joinup DIDs: https://joinup.ec.europa.eu/collection/ssi-eidas-bridge'
The purpose of WSDL is not related to the long-term preservation of electronic records and other kinds of information. Therefore, this criterion is not applicable to the specification.
The purpose of LDAP is not related to long term preservation of electronic records. Therefore, this criterion is considered not applicable to this specification. LDAP IETF reference: https://tools.ietf.org/html/rfc4511
'The ETSI TS 119 612 specification can enable mechanisms to ensure that data has not been modified and that it is accurately transferred between public administrations or organisations and citizens. In this context, the specification supports authentication methods, such as digital signatures, which ensure that signed data is in its original form, and it is accurate. ETSI TS 119 612: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf'
'The PROV XML specification allows for an XML serialisation of a PROV model, a fact that explicitly proves that the PROV family of docuents can provide means for the long-term preservation of information. PROV Primer document: https://www.w3.org/TR/prov-primer/ PROV Ontology: https://www.w3.org/TR/2013/REC-prov-o-20130430/ PROV Data Model: https://www.w3.org/TR/2013/REC-prov-dm-20130430/'
The purpose of XAdES is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification. XAdES ISO reference: https://www.iso.org/standard/56025.html XAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/101900_101999/101903/01.04.02_60/ts_101903v010402p.pdf
By allowing the exchange of datasets metadata, DCAT increases the searchability, visibility, discoverability and reuse of existing data, including information on processes and administrative rules.
FTP is known to negatively impact the scalability of systems using it. The protocol faces problems when transferring high volumes of data. See: https://sapinsider.wispubs.com/Assets/Articles/2012/January/Using-FTP-Know-The-Risks
'The purpose of CSV is not related to e-accessibility. Therefore, this criterion is not applicable to the specification. CSV reference: https://datatracker.ietf.org/doc/html/rfc4180'
'The specification is not included in any national catalogue of recommended specifications. '
There are not many studies assessing the specification in terms of effectiveness and efficiency. The document provided is an empirical study on the testing of WS-BPEL web services in the current environment of web services based on the cloud. Study about WS-BPEL: https://ieeexplore.ieee.org/document/8204552
'DNS Queries over HTTPS (DoH) is associated with EIRA ABB's in the EIRA Library of Interoperability Specifications (ELIS). More specifically, DoH is associated with the "Integrity Verification” ABB from the Technical Application view, and the “Domain Name Service” ABB from the Technical-Infrastructure View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /solution/elis/release/600rf'
'While ISO standards, including ISO/IEC 7498:1, are internationally recognized and widely used, they are not European Standards in the sense of being developed and published by CEN or CENELEC specifically for the European region. ISO/IEC 7498:1: https://www.iso.org/standard/20269.html'
'The specification was developed in 2015, and it has been evolving together with all the related European projects where CCCEV has an active role. Moreover, at the moment of performing the assessment, version 2.0 has not yet been developed in order to ensure that the CCCEV covers the needs of the different cross-border projects (e.g. eCertis, ESPD, etc). Core Criterion and Core Evidence Vocabulary reference (v1.0.0): https://joinup.ec.europa.eu/release/core-criterion-and-core-evidence-vocabulary-v100 '
'Being an international standard that encompasses the internal security framework of all private and public administrations, ISAE 3402 helps to create digitally by default services that reduce the administrative burden on both sides, public administrations and stakeholders. ISAE 3402 handbook reference: https://www.ifac.org/system/files/downloads/b014-2010-iaasb-handbook-isae-3402.pdf'
After checking the different standard catalogues at supra-national level, there is no evidence of the inclusion of XACML within any European catalogue of standards. ICT technical specifications: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en CEN search tool catalogue: https://standards.cen.eu/dyn/www/f?p=CENWEB:105::RESET:::: CENELEC search tool catalogue: https://www.cenelec.eu/dyn/www/f?p=104:107:0::::FSP_LANG_ID:25
XHTML is one of the main markup languages to develop web resources. XHTML files are used to exchange information through the web. So this fact proves that XHTML fosters data portability between systems and applications. XHTML W3C reference: https://www.w3.org/TR/xhtml1/
XHTML has been used to publish some online documents of the European Commission. For example, Eur-lex used XHTML to publish a proposal for a regulation on a mechanism to resolve legal and administrative obstacles in a cross-border context. XHTML implementation by Eur-lex: https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:52018PC0373&from=EN
OASIS is a non-profit consortium that drives the development, convergence and adoption of open standards for the global information society, SAML 2.0 is developed and maintained by OASIS consortium. See: https://www.oasis-open.org/org
'Although iCalendar defines an access classification for ensuring authentication, authorization, access rights, or calendar user access role, the specification does not ensures, but neither prevents, data processing accuracy. iCalendar Classification: https://www.rfc-editor.org/rfc/rfc5545#section-3.8.1.3'
'NFVI facilitates organisational interoperability agreements thanks to the diversification of the ETSI NFV working groups and their respective publications on testing, benchmarking and other descriptive assets. ETSI NFVI working groups reference: https://portal.etsi.org/TB-SiteMap/NFV/NFV-WGs-amp-EGs-ToR'
The specification includes security features that were included to ensure and avoid the vulnerabilities while exchanging data. Therefore, by adopting the main features in terms of security, the implementation of HTML5 fosters the secure and trustworthy data exchange between administrations and stakeholders.
'IETF 3161 Time Stamp Protocol (TSP) is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, IETF 3161 Time-Stamp Protocol (TSP) can define the interoperability aspects of the " e-Timestamp Creation Service", and “e-Timestamp Verification and Validation Service” ABBs of the EIRA Technical View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/distribution/elis-v600xlsx'
"ISO/IEC 19944 does not explicitly support multilingualism, nonetheless, its implementation could incorporate multilingual support based on the user's needs of a given organisation. ISO/IEC 19944-1 specification: https://www.iso.org/standard/60545.html"
'TSP tracks the creation and modification time of digital documents. Therefore, it fosters the creation and digitalisation of services at the same time that guarantees the data trustworthy exchange. By providing these capabilities to administrations, allows the reduction of administrative burden avoiding non-digital exchanges and the procedures for ensuring data reliability. TSP IETF reference: https://tools.ietf.org/html/rfc3161'
'The specification is complemented by a conformance testing platform to allow testing of implementations. Moreover, the ARIA initiative proposes tools and methods to evaluate such implementations. WAI reference, Test & Evaluate: https://www.w3.org/WAI/test-evaluate/ WAI-ARIA reference: https://www.w3.org/TR/wai-aria/'
'After checking the different standard catalogues at supra-national level, there is no mention of ebXML in any official document stating its conformance in regards to Regulation 1025/2012. ICT technical specifications: https://ec.europa.eu/growth/single-market/european-standards/ict-standardisation/ict-technical-specifications_en CENELEC and CEN search tool catalogue: https://standards.cencenelec.eu/dyn/www/f?p=CEN:105::RESET::::'
'OAIS is focused on the long-term preservation of digital information, including the storage, management, and retrieval of digital objects. It defines a set of concepts and principles that can be used to guide the development of digital preservation systems, but it does not provide guidance on the publication of open data. That being said, the concepts and principles defined in the OAIS reference model can be applied in the development of open data repositories, to ensure that the data is preserved and maintained over the long term. OAIS provides a framework for managing digital objects, including the management of metadata, which can be used to describe the data and make it discoverable. OAIS specification: https://public.ccsds.org/Pubs/650x0m2.pdf OAIS and the preservation of Linked Data: http://giaretta.org/digital-preservation/consultancy/oais-and-the-preservation-of-linked-data/ '
'No tools assessing the conformity of implementations with the specification have been found. However, there are tools developed by the FTP community assessing FTP servers access. FTP Tool Assessing Server Performance: https://ftptest.net/'
HTTP is an internet protocol for the data exchange over an Internet network. It supports the first level of maturity defined in the Tim Berners-Lee´s 5 stars Open Data deployment scheme, "Make your data accessible on the web". See: https://5stardata.info/en/
"The purpose of EN 16234-1 e-CF is not related to the exposure of interfaces to access the public administration's services. Therefore, this criterion is not applicable to this specification. CEN reference, CEN/TC 428 - ICT Professionalism and Digital Competences (Published standards), EN 16234-1 e-CF: https://standards.cencenelec.eu/dyn/www/f?p=205:110:0::::FSP_PROJECT:67073&cs=15E62ED24D608A5F10D6BEE8E6D50FA10"
'The ebXML specification plays a crucial role in enabling digital services delivery channels by providing a standardised framework for exchanging XML-based business messages. This framework ensures secure and reliable communication between different systems, facilitating seamless integration and interoperability. ebXML techtarget: https://www.techtarget.com/searchcio/definition/ebXML ebXML RegRep OASIS reference: https://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html'
'The ETSI ESI Portal provides public access to drafts review activity and contributions. However, drafts are only publicly available over a registration process. The decision-making process includes a public review, where stakeholders involved can provide technical feedback in order to enhance and maximize the quality and accuracy of the standards. ETSI ESI Portal: https://portal.etsi.org/tb.aspx?tbid=607&SubTB=607#/'
PDF/A is highly adopted as a document format for exchange information, which is technological independent. These facts demonstrate the maturity and market acceptance for its use in the development of products and services. PDF/A reference: https://www.iso.org/standard/38920.html https://www.iso.org/standard/50655.html
'Nowadays, at the moment of performing the assessment WSDL is widedy used specification involved in the implementation of the Service-Oriented Architectures (SOAs). SOAP along with REST are the main ways to build web services, the first one uses WSDL to describe services and guaranteeing access to them. Therefore, WSDL is involved in the development of solutions, including innovative ones. SOAP IBM Documentation: https://www.ibm.com/docs/en/radfws/9.7?topic=standards-soap REST IBM Documentation: https://www.ibm.com/topics/rest-apis '
'GraphQL is itself a platform, since it provides the means to query mutliple databases through a unified interface which is indeed friendly to product development and useful for tool-building. GraphQL specification: https://spec.graphql.org/October2021/#sec-Overview'
'Through the centralised databases that GraphQL is able to provide, comprehensibility of administrative procedures and ruling of data is considerably improved by facilitating the maintenance of a coherent governance, defining efficient processes, and ensuring final consumers leverage the data available in a given organisation. GraphQL specification: https://spec.graphql.org/October2021/#sec-Overview'
'After checking the different standard catalogues at supra-national level, there is no mention of Odata in any official document stating its conformance in regards to Regulation 1025/2012. ICT technical specifications: https://ec.europa.eu/growth/single-market/european-standards/ict-standardisation/ict-technical-specifications_en CENELEC and CEN search tool catalogue: https://standards.cencenelec.eu/dyn/www/f?p=CEN:105::RESET::::'
'Such means as enabling the secure processing of data can be provided as SOAP extensions using the SOAP extensibility mode. The SOAP Messaging Framework does not directly provide any mechanism for dealing with it directly. SOAP Reference, section 7 Security Considerations: https://www.w3.org/TR/soap12/#secconsiderations'
'The purpose of BFO is not related to the reuse of information. Therefore, this criterion is not applicable to the specification. BFO reference: https://www.iso.org/standard/74572.html'
'ETSI TS 119 511 has been developed to provide services for the long-term preservation of data in general. The specification fosters the implementation of the once-only principle by ensuring data is well preserved and stored, and it can also be retrieved when needed. ETSI TS 119 511 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119511/01.01.01_60/ts_119511v010101p.pdf'
There are existing studies assessing the effectiveness of DNS. See: https://ccronline.sigcomm.org/wp-content/uploads/2017/01/p36-hao.pdf https://www.researchgate.net/profile/Alessio_Merlo/publication/221271469_A_Comparative_Performance_Evaluation_of_DNS_Tunneling_Tools/links/00b4951c1e5065b0e6000000/A-Comparative-Performance-Evaluation-of-DNS-Tunneling-Tools.pdf https://www.researchgate.net/publication/235996771_Performance_assessment_and_analysis_of_DNS_tunneling_tools https://ccronline.sigcomm.org/wp-content/uploads/2017/01/p36-hao.pdf
'The purpose of this Core Vocabulary is not related to long term preservation of electronic records. Therefore, this criterion is considered not applicable to this specification. Core Criterion and Core Evidence Vocabulary reference (v1.0.0): https://joinup.ec.europa.eu/release/core-criterion-and-core-evidence-vocabulary-v100 '
'The ebXML specification can help with the reuse of information by defining different mechanisms. In this sense, the specification provides a way to register business process sequences with related message exchanges. Additionally, in the context of OOTS (Once-Only Technical System) the ebXML specification provides the standardised structure necessary for relevant information to be identifiable, efficiently transported, and usable by receiving systems. ebXML information reuse OOTS: https://code.europa.eu/oots/tdd/tdd_chapters/-/tree/86290aa801fb9a8e56486fc49019addcc1321a95/OOTS-EDM/xml/Request-Response%20Samples ebXML RegRep OASIS reference: https://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html'
'The specification does facilitate the publication of open data as it is a technical markup language which derives from the XML standard for representing legislative, executive and judicial documents in a structured manner. 5-star linked open data: https://www.w3.org/DesignIssues/LinkedData.html AKN4EU reference: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/akn4eu '
'There are already existing studies and documents assessing and documenting DIDs features and providing possible improvements of its performance among other aspects. In "A Survey on Decentralized Identifiers and Verifiable Credentials" it is provided the background on DIDs and VCs. Moreover, it is analyzed available implementations and offer an in-depth review of how these technologies have been employed across different use-case scenarios. In addition, there are presented some challenges that hinder their adoption in real-world scenarios and future research directions. And in "Methods for Decentralized Identities: Evaluation and Insights" it is provided an evaluation of a selection of distributed identity methods, and it is analyzed their properties based on the categorization specified in the W3C recommendation rubric. A Survey on Decentralized Identifiers and Verifiable Credentials: https://arxiv.org/pdf/2402.02455 Methods for Decentralized Identities: Evaluation and Insights: https://eprint.iacr.org/2021/1087.pdf'
'Currently the specification is widely used in diverse group of projects and institutions and in particular in the Elementary Multiperspective Material Ontology (EMMO): List of ontologies and institutions/groups using BFO: https://basic-formal-ontology.org/users.html Elementary Multiperspective Material Ontology (EMMO) GitHub: https://github.com/emmo-repo/EMMO BFO reference: https://www.iso.org/standard/74572.html '
'While genericode itself is not a comprehensive solution for negotiating and implementing organisational interoperability agreements, its standardised representation of code lists and controlled values can provide a foundation for interoperability discussions. By adopting genericode-compliant formats and structures, organisations can establish common ground for data exchange, facilitate communication, and support interoperability efforts. Code List Representation (genericode): https://docs.oasis-open.org/codelist/genericode/v1.0/os/genericode-v1.0-os.html'
'No, the specification is not yet a European Standard. See W3C Reference: https://www.w3.org/TR/2006/REC-xml11-20060816/'
'The Asset Administration Shell (AAS) is not related to the data processing accuracy. Therefore the criterion is not applicable. Details of the Asset Administration Shell (AAS) https://industrialdigitaltwin.org/en/wp-content/uploads/sites/2/2024/06/IDTA-01001-3-0-1_SpecificationAssetAdministrationShell_Part1_Metamodel.pdf'
'This Core Vocabulary is a business domain agnostic specification that can be reused in a cross-domain way. Core Criterion and Core Evidence Vocabulary reference (v1.0.0): https://joinup.ec.europa.eu/release/core-criterion-and-core-evidence-vocabulary-v100 '
'Estonian Tax and Customs board: https://www.emta.ee/en/business-client/e-services-training-courses/how-use-e-services/x-tee-services#xbrl-gl'
The W3C Royalty-Free IPR licences granted under the W3C Patent Policy apply to all W3C specifications, including Xforms 2.0. W3C Patent practice: https://www.w3.org/TR/patent-practice#ref-AC
'OData is a recommendation and protocol for data exchange. Therefore, the specification enables the secure exchange of data. OData reference: http://docs.oasis-open.org/odata/odata/v4.0/odata-v4.0-part1-protocol.html'
MIME is included in 8 national catalogues of recommended specifications. They belong to Croatia, France, Germany, Greece, Malta, the Netherlands, Spain and Sweden. CAMSS List of standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
The purpose of the specification is not related to the preservation of information. Therefore, this criterion is not applicable to the specification. SVG W3C reference: https://www.w3.org/TR/SVG11/
'The DCAT vocabulary supports the attribution of data and metadata to various participants such as resource creators, publishers and other parties. In addition, it also supports the association of rights and licenses with catalogued Resources and Distributions. Such metadata improves the reliability of data exchanged between citizens, businesses and public administrations. DCAT (v2.0.0) reference: https://www.w3.org/TR/vocab-dcat-2/ '
'There are clear guidelines for customisation and extensions for the specification. http://www.xbrl.org/int/gl/2015-03-25/GLTFTA-REC-2015-03-25.html#section-how-to-create-extensions-within-the-gl-taxonomy-framework'
'According to the 5 star Open Data model suggested by Tim Berners-Lee about how to publish linked data, the second star corresponds to the availability of data as structured data. ebXML is an XML family standard and therefore incorporates XML, allowing the publication of public data as open data. ebXML reference, section 1: http://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html#__RefHeading__8798_474791649 Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/en/'
'The purpose of ADMS is not related to providing an access control mechanism. Therefore, this criterion is not applicable to the specification. ADMS Specification W3C: https://www.w3.org/TR/vocab-adms/'
'iCalendar is included in 5 national catalogues of recommended specifications. They belong to Croatia, France, Malta, the Netherlands and Sweden. The National Interoperability Framework (NIF) of France and the Netherlands is fully aligned with at least 2 out of 3 sections of the European Interoperability Framework (EIF) according to the National Interoperability Frameweork Observatory (NIFO) factsheets. CAMSS List of standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards NIFO Factsheets: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digitalpublicadministration-factsheets-2022 National Catalogue of France: https://www.numerique.gouv.fr/uploads/Referentiel_General_Interoperabilite_V2.pdf'
JSON is included in 2 national catalogues of recommended specifications. They belong to the Netherlands and Slovenia. The National Interoperability Framework (NIF) of these Member States is fully aligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. See: https://joinup.ec.europa.eu/collection/national-interoperability-framework-observatory-nifo/nifo-factsheets
The specification can be used independently from specific operating systems and hardware platforms.
XML 1.1 is publicly available for implementation and use for free on W3C's webpage. Therefore it can be reused by the organisations, administrations, open communities, etc. that developed it. See: https://www.w3.org/TR/2006/REC-xml11-20060816/
The purpose of CSV is not related to the long-term preservation of electronic records and other kinds of information. Therefore, this criterion is not applicable to the specification.
"NUTS started to be used within the European Union's territory as a reference coding system in 1999, although its use dates back to the 1970's (see EUROSTAT reference, History of NUTS section, 'NUTS 1981 - MUTS 1999' document). This specification has gone through different amendments since1999, some of these changes resulting from the adhesion of new Member States and the consequent addition of new codes. All the documentation on NUTS releases is publicly available (see EUROSTAT reference, History of NUTS section, NUTS versions documents). EUROSTAT reference, History of NUTS section, 'NUTS 1981 - MUTS 1999' document: https://ec.europa.eu/eurostat/web/nuts/history EUROSTAT reference, History of NUTS section, NUTS versions documents: https://ec.europa.eu/eurostat/web/nuts/history"
The purpose of JPEG is not related to long term preservation of electronic records. Therefore, this criterion is considered not applicable to this specification. JEPG ISO reference: https://www.iso.org/standard/18902.html JPEG public reference: https://jpeg.org/jpeg/
'There is no Member State that includes the DPV in their national catalogue with Their National Interoperability Framework (NIF) in alignment with the three categories 1. Conceptual model for integrated public servicesprovision, 2. interoperability layers, and 3. interoperability principles. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards NIFO Factsheets: https://joinup.ec.europa.eu/collection/national-interoperability-framework-observatory-nifo/nifo-factsheets'
The application of the once-only principle in all EU Member States public administrations aims at reducing the administrative burden. To achieve this, interoperability between public administrations is a sine qua non condition. XML addresses and facilitates interoperability between public administrations, cross border services and impacts positively the development of eGovernment. This is due to the fact that it has been designed to store, transport data, and to exchange data through interoperable systems. Moreover, XML defines a set of rules for encoding documents in a human-readable format and machine-readable format enhancing the reusability of data and stimulating the interoperability of systems and services.
The purpose of HTTPS is not related to the delivery of multilingual European public services. Therefore this criterion is considered not applicable specification.
'Schema.org has the W3-schema.org project website, as well as a dedicated platform in Github for sharing results and best practices. Therefore, the specification encourages the creation of open information about the specification and encourages relevant communities from the EU (as well as from non-EU communities) to share their results. W3 community reference, Important links section: https://www.w3.org/community/schemaorg/ Schema.org-W3 Github, Wiki section: https://github.com/schemaorg/schemaorg/wiki'
The purpose of JPEG is not related to the delivery of multilingual public services. Therefore, this criterion is not applicable to this specification. JEPG ISO reference: https://www.iso.org/standard/18902.html JPEG public reference: https://jpeg.org/jpeg/
'The purpose of ESI/REM is not related to supporting the implementation of European public services, therefore it does not promote or hinder it. ETSI EN 319 532-3 reference: https://www.etsi.org/deliver/etsi_en/319500_319599/31953203/01.02.01_60/en_31953203v010201p.pdf'
The purpose of CPOV is not related to e-accessibility. Therefore, this criterion is considered not applicable to this specification. CPOV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-organisation-vocabulary
"The Asset Administration Shell (AAS) facilitates the publication of data on the web since it is based on open standards and additionally the usage of URI's in order to facilitate the exchange of the digital versions of industrial assets among partners. Details of the Asset Administration Shell (AAS) https://industrialdigitaltwin.org/en/wp-content/uploads/sites/2/2024/06/IDTA-01001-3-0-1_SpecificationAssetAdministrationShell_Part1_Metamodel.pdf"
By allowing the exchange of digital documents, PDF/A avoids sharing non-digital documents and then helps to the reduction of administrative burden. Additionally, as a format fostering the preservation of digital information, ensures the possible reuse and exchange of data over time. PDF/A reference: https://www.iso.org/standard/38920.html https://www.iso.org/standard/50655.html
'The purpose of WAI-ARIA is not related to long term preservation of electronic records. Therefore, this criterion is considered not applicable to this specification. WAI-ARIA reference: https://www.w3.org/TR/wai-aria/'
CAdES Baseline profile is being used in the context of the European internal market to ensure interoperability across borders when AdES signatures are required. Hence, it can be considered as an element fostering the creation of innovative solutions fostering the implementation of Once-only Principle along with other capabilities enhancing the relationship between public administrations and stakeholders.
'The DPV is based on the legislative requirements of the European Union, such as the GDPR, which aims to harmonize data privacy laws across Europe. Therefore, the DPV promotes the comprehensibility of administrative procedures by providing a clear vocabulary that defines all levels at which personal data will be processed. DPV specification: https://w3c.github.io/dpv/dpv/ DPV primer document: https://w3c.github.io/dpv/primer/#introduction GDPR reference: https://gdpr.eu/'
'The Better Regulation Guidelines and Toolbox only refers to the authentication protocols on certain elements (tool 28) and only recommended as best practice. In this sense the specification sets the legal framework for the provision of authenticity features but does not set a definitive guide. Better Regulation Guidelines and Toolbox reference: https://commission.europa.eu/law/law-making-process/better-regulation/better-regulation-guidelines-and-toolbox_en Better Regulation Toolbox reference: https://commission.europa.eu/document/download/9c8d2189-8abd-4f29-84e9-abc843cc68e0_en?filename=BR%20toolbox%20-%20Jul%202023%20-%20FINAL.pdf'
'There are some general implementation guidelines that a user must follow in order to implement the specification, explained in the following link. DCMI Point 3, General Implementation Guidelines: https://www.dublincore.org/specifications/dublin-core/dc-xml-guidelines/ DCMI About: https://www.dublincore.org/about/ '
After checking the different standard catalogues at supra-national level, there is no evidence of the inclusion of ODF within any European catalogue of standards. ICT technical specifications: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en CEN search tool catalogue: https://standards.cen.eu/dyn/www/f?p=CENWEB:105::RESET:::: CENELEC search tool catalogue: https://www.cenelec.eu/dyn/www/f?p=104:107:0::::FSP_LANG_ID:25
'The specification itself has created a community that share and develop as well as a dedicated platform in Github for sharing results and best practices. Therefore, the specification encourages the creation of open information about the specification and encourages relevant communities from the EU (as well as non-EU communities) to share their results. DCMI About: https://www.dublincore.org/about/ DCMI Github: https://github.com/dcmi'
'DoH encrypts DNS queries, making it more challenging for third parties, including Internet Service Providers (ISPs), to intercept and analyse the content of DNS requests. This encryption adds a layer of confidentiality to the communication, but it does not directly address other aspects of data protection, such as data retention or access policies. It does not extend its protection to other layers of the communication stack or to the handling of personal data within applications or services. DoH specification: https://datatracker.ietf.org/doc/html/rfc8484'
XHTML can be found for free along within the European Collaborative Platform, Joinup. XHTML in Joinup platform: https://joinup.ec.europa.eu/solution/xhtmltm-10-extensible-hypertext-markup-language-second-edition
'The Dataspace Protocol is not involved in protection against unauthorised changes. Therefore, this criterion does not apply to this specification. IDSA Dataspace Protocol: https://docs.internationaldataspaces.org/ids-knowledgebase/v/dataspace-protocol/overview/readme'
'ISO/IEC 19944-1 has support from its ISO/IEC technical committee, which is a working group in charge of proposing changes and reach out to stakeholders in order improve the specification. ISO/IEC 19944-1 Joint Technical Committee: https://www.iso.org/committee/601355.html'
'The purpose of genericode is not related to enabling digital service delivery channels. Therefore, this criterion is considered not applicable to this specification. Code List Representation (genericode): https://docs.oasis-open.org/codelist/genericode/v1.0/os/genericode-v1.0-os.html'
'There are not communities nor platforms for sharing and publishing iCalendar-related issues at national or European platforms. Therefore, this criterion is not applicable to the specification. iCalendar specification: https://www.rfc-editor.org/rfc/rfc5545'
'The purpose of REM message structure on these header fields is to give immediate access to important identification information instead of forcing the REMS to process the ERDS evidence. Also, ENISA is recommending the specification in a Signature Verification document. ENISA document: https://www.enisa.europa.eu/events/tsforum-caday-2018/presentations/C03_Rock.pdf ETSI EN 319 532-3 reference, section 6.2.1: https://www.etsi.org/deliver/etsi_en/319500_319599/31953203/01.02.01_60/en_31953203v010201p.pdf'
The Research Data Alliance (RDA) is a non-profit organisation See: https://www.rd-alliance.org
SOAP 1.2 is a protocol intended for exchanging structured information in a decentralized, distributed environment. SOAP uses XML technologies to define an extensible messaging framework providing a message construct that can be exchanged over a variety of underlying protocols. It can be concluded that it is proportionate to the users' needs as it helps to the well functioning of citizens, businesses and administrations. See: https://www.w3.org/TR/soap12/
'WAI-ARIA was conceived for assistive web technologies. As it was created to enhance e-accessibility and to simplify web navigation, it can be used in any other domain as a visibility enhancement. It is the case of Google Extensions with which the user can customise web content by means of the HTML Document Object Model (HTML DOM). WAI-ARIA reference: https://www.w3.org/TR/wai-aria/ WAI-ARIA Chrome Extension reference: https://developer.chrome.com/docs/extensions/mv3/a11y/#aria'
'The purpose of the specification is not related to provide an access control mechanism. Therefore, this criterion is not applicable to this specification. XSLT Reference: https://www.w3.org/TR/xslt-30'
'The OAS points out some essential security aspects addressing the protection of personal data. For example, the specification mentions security schemes that can be used by the operations, such as HTTP authentication, API key or OAuth. Nonetheless, these personal data protection mechanisms rely on external protocols not specified by OAS. OAS specification: https://spec.openapis.org/oas/latest.html#openapi-specification OAS in Github: https://github.com/OAI/OpenAPI-Specification/#participation'
The purpose of LegalDocML is not related to e-accessibility. Therefore, this criterion is not applicable to this specification. LegalDocML reference: https://www.oasis-open.org/committees/legaldocml/charter.php
'The WAI-ARIA actively promotes collaboration and knowledge-sharing through the Web Accessibility Initiative - Communities of Practice (WAI-COOP) platform. This platform serves as a hub for sharing results and best practices related to WAI-ARIA, encouraging open information exchange about the specification. By facilitating collaboration at the European level, WAI-ARIA seeks to engage relevant communities and encourage the sharing of outcomes and insights. WAI-COOP reference: https://www.w3.org/WAI/about/projects/wai-coop/'
'The purpose of the PROV family of documents is not related to e-accessibility. Therefore this criterion is not applicable to the specification. PROV Primer document: https://www.w3.org/TR/prov-primer/ PROV Ontology: https://www.w3.org/TR/2013/REC-prov-o-20130430/ PROV Data Model: https://www.w3.org/TR/2013/REC-prov-dm-20130430/'
"Domibus allows for customisation, enabling developers to tailor the platform to meet the organization's specific requirements and integrate it effectively into your existing infrastructure. Customisation in Domibus involve aspects such as User Interface, integration with backend systems or security configuration, between others. Domibus specification: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/Domibus"
'The ISO/IEC 7498:1 focuses on organising communication functions into layers to enhance interoperability of network protocols. Organisational interoperability involves the ability of different organizations or entities to work together efficiently and effectively, sharing information and resources. In that sense, the OSI model may contribute by providing standardised communication protocols and interoperability at the network layer. ISO/IEC 7498:1: https://www.iso.org/standard/20269.html'
'DNS Queries over HTTPS (DoH) is included in the 2023 Rolling Plan for ICT standardisation, specifically the ePrivacy part of the plan. The ePrivacy Directive and the General Data Protection Regulation provide the legal framework to ensure digital privacy for EU citizens. DoH is presented as standardised encodings for DNS queries and responses that are suitable for use in HTTPS. This enables the domain name system to function over certain paths where existing DNS methods experience problems. ePrivacy (RP2023): https://joinup.ec.europa.eu/collection/rolling-plan-ict-standardisation/eprivacy-rp2023'
All Outputs packages have been published under the Creative Commons Attribution (CC-BY) licence. RDA’s IPR policy: See: http://dx.doi.org/10.15497/DA8C2CC2-A7AF-4E3A-A4D6-C100E5C27492
'While not explicitly addressed in SCIM, the use of secure transport mechanisms (such as HTTPS) contributes to data integrity during transmission, preventing unauthorized tampering and ensuring the accuracy of the exchanged data. SCIM: https://scim.cloud/'
'There have been found some academic papers assessing the use of DPV in terms of effectiveness. These documents describe the use of DPV personal data handling policies and information about consent (see Personal Data Handling in Multi-Agent Systems Interaction) or assess the effectiveness when it comes to discover the relevant information in privacy policies by means of integrating the knowledge represented in the DPV with the information modelled in BabelNet. Personal Data Handling in Multi-Agent Systems Interaction: https://link.springer.com/chapter/10.1007/978-3-030-49778-1_5 The role of Vocabulary Mediation to Discover and Represent Relevant Information in Privacy Policies: http://ebooks.iospress.nl/doi/10.3233/FAIA200851,'
RDF is maintained by W3C which is an international community developing open standards. See: https://www.w3.org/TR/rdf11-primer
'The purpose of DIDs is not related to e-accessibility. Therefore, this criterion is considered not applicable to this specification. DIDs W3C: https://www.w3.org/TR/did-core/'
'REST architectural style is mainly defined by its architectural constraints. Any system that does not conform to all of RESTs constraints cannot be considered as RESTful. Therefore, the specification does not support partial implementtions. REST architectural constraints reference: https://restfulapi.net/rest-architectural-constraints/'
eDelivery SMP 1.10 is not included in any official supra-national catalogue. However, it is included in the full stack catalogue of eDelivery at CEF’s webpage. See: https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/Services+eDelivery
'The purpose of EuroVoc is not related to guaranteeing the authenticity and authentication of roles agents involved in the data transactions. Therefore, this criterion is not applicable to this specification. EuroVoc: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource /dataset/eurovoc'
'This specificaton presents the standard to which all digital documents conform to improve the efficiency, interoperability, and readability of all documents/certificates. For instance, since it plays a major role within the European Blockchain Services Infrastructure (EBSI) ecosystem, it is helpful fostering the visibility of administrative data and supporting the decision-making process. Verifiable Credentials: https://www.w3.org/TR/vc-data-model/ EBSI W3C Verifiable Credentials: https://ec.europa.eu/digital-building-blocks/wikis/pages/viewpage.action?pageId=555222155'
'The purpose of BFO is not related to e-accessibility. Therefore, this criterion is not applicable to the specification. BFO reference: https://www.iso.org/standard/74572.html'
"Conformance to ISO/IEC 19944 is only achieved if the clauses and vocabulary definitions are followed. Nonetheless, there has not been found any tool or guideline with the purpose of conforming to the specification, nor is there a conformance statement within the specification's document. ISO/IEC 19944-1 specification: https://www.iso.org/standard/60545.html"
The specification is used to encode and structure legal documents as XML, therefore it can help to the structured data exchange and the availability of interfaces with internal information. LEOS allows a common interface where this XML content is displayed in a user-friendly way to allow the creation and management of legal documents. LegalDocML reference: https://www.oasis-open.org/committees/legaldocml/charter.php LEOS: https://joinup.ec.europa.eu/collection/justice-law-and-security/solution/leos-open-source-software-editing-legislation
'The purpose of LDAP is not related to e-accessibility. Therefore, this criterion is considered not applicable specification. LDAP IETF reference: https://tools.ietf.org/html/rfc4511'
XML is already associated to an EIRA ABB in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, XML can define the interoperability aspects of the "Machine to Machine Interface" and "Representation" ABBs from the EIRA Semantic and Technical views. See: https://joinup.ec.europa.eu/solution/elis/distribution/eliscataloguev100betaxlsx
OASIS has defined a clear Technical Committee (hereby TC) process where all the stakeholders involved have the opportunity to participate in the development of the specification development process. All the information related to a TC activity is hosted and can be consulted. See: https://www.oasis-open.org/policies-guidelines/tc-process-2017-05-26
'IEEE Std 802.3-2022 is currently included in the catalogue of standards of one Member State: Malta. CAMSS list of standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards Malta List of Standards: https://www.mccaa.org.mt/Section/Content?contentId=1243 IEEE Std 802.3-2022 Reference: https://ieeexplore.ieee.org/document/9844436'
The purpose of the specifications is not related to the visibility of administrative information, data or services. Therefore, this criterion is not applicable to this specification. SMTP IETF reference: https://tools.ietf.org/html/rfc5321
The purpose of CSS is not related to the once-only principle. Therefore, this criterion is not applicable to the specification. CSS v2.1 W3C reference: https://www.w3.org/TR/2011/REC-CSS2-20110607/
As a solution developed by the SEMIC action of the ISA2 Programme funded by the European Commission, DCAT-AP is part of their supra-national catalogue of reusable solutions. See: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/our-solutions https://ec.europa.eu/isa2/solutions_en
'HTTPS is used for any solution using internet, including innovative solutions. HTTPS specification: https://tools.ietf.org/html/rfc2818 '
'The IndexedDB allows to store information locally, and access data without the need of being connected to the internet. In this context, public administrations can store information locally, and continue delivering public services in poor connection moments. Thus, public services can be delivered in many complicated situations. Indexed Database API: https://www.w3.org/TR/IndexedDB/'
'ISO/IEC 7498:1 has a specific section called "Session Layer" whose purpose is to provide the means necessary for cooperating presentation-entities to organise and to synchronise their dialogue and to manage their data exchange. One of the services provided is token management, which allows the presentation-entities to control explicitly whose turn it is to exercise certain control functions. ISO/IEC 7498:1: https://www.iso.org/standard/20269.html'
'Since its first release, ISO/IEC 19944-1 has been widely accepted and adopted by major stakeholders and Member States given that it extends a standard that has already been recommended by many cloud-computing organisations such as the Storage Networking Industry Association (SNIA), and standardisation bodies such as UNE. UNE digitalisation report: https://www.une.org/normalizacion_documentos/Informe%20Transformaci%C3%B3n%20Digital_20201127.pdf SNIA Best Practices for Cloud Security and Practices: https://www.snia.org/sites/default/files/Hibbard_Best-Practices-for-Cloud-Security-and-Privacy_V2_Final_0.pdf '
'Being in a low maturity level of development DPV is being developed under the guidelines proposed by W3C. Consequently, DPV is still not a standard nor is it in the W3C standards track, and it is not a European Standard. DPV specification: https://w3c.github.io/dpv/primer/'
'As defined on the OASIS Technical Committee (TC), the OData TC are involved in the release lifecycle of the specification. External contribution to this committee is possible through open channels. Up-to-date, the OData TC has announced three public reviews; however, the topic selection of these reviews is independent of the external contributors. OData OASIS Technical Committee reference: https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=odata OData OASIS Technical Committee, Overview reference: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=odata#overview OData TC third review reference: https://www.oasis-open.org/2023/07/19/invitation-to-comment-on-odata-extension-for-data-aggregation-v4-0/ OData TC fourth review reference: https://www.oasis-open.org/2024/04/08/invitation-to-comment-on-four-odata-v4-02-specification-drafts/'
'As REST is an architectural style, it is designed to be compatible with any software, and does not rely on any other standard or specification. REST reference: https://restfulapi.net/rest-architectural-constraints/'
'The specification is in a very early stage, has been implemented and it is being implemented in Italy and Germany. However, at the moment of performing the assessment, there are no assessment of the specifications effectiveness. Publiccode.yaml documentation: https://docs.italia.it/italia/developers-italia/publiccodeyml-en/en/master/index.html Italian National Software Catalogue: https://developers.italia.it/ Open CoDE: https://opencode.de/en '
The ISO/IEC 26300-1:2015 which refers to ODF v1.2 is not available for free for everyone to study. Payment is needed to reach access to the standard. ODF ISO reference: https://www.iso.org/standard/66363.html
The specification is included in 10 Member States' catalogues of recommended specifications. Some examples of Member States including PDF on their catalogues are the Netherlands, Slovenia, Spain or Sweden. See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
"HTTP Cookies is the most widely-used tool to enable web servers to store stateful information on the user's device or to track the user's browsing activity. They can also be used to save for subsequent use information that the user previously entered into form fields, such as names addresses and passwords. Therefore, HTTP Cookies help simplify the delivery of European Public services by rendering their websites operational and gather (anonymised) analytics data abut user behaviour. HTTP Cookies reference: https://datatracker.ietf.org/doc/html/rfc6265#section-1 European Commission cookies policy: https://ec.europa.eu/info/cookies_en"
'IEEE Std 802.3-2022 does not explicitly ensure data processing accuracy, as it primarily focuses on the physical and data link layers of Ethernet networking. However, it does facilitate accuracy through its features that support reliable data exchange. Therefore, this criterion is not applicable to this specification. IEEE Std 802.3-2022 Reference: https://ieeexplore.ieee.org/document/9844436'
After being evaluated compliant with the regulation on standardisation 1025/2012, UTF-8 has been identified by Commission Implementing Decision. See: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en
The purpose of this Core Vocabulary is not related to long term preservation of electronic records. Therefore, this criterion is considered not applicable to this specification. CPSV-AP reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-service-vocabulary-application-profile
'No, the specification is not yet an European Standard, it is though a recommended specification. Core Criterion and Core Evidence Vocabulary reference (v1.0.0): https://joinup.ec.europa.eu/release/core-criterion-and-core-evidence-vocabulary-v100 '
At the moment of performing the assessment, PDF is widely used in across sector manner. One of the main document format used for the document exchange between different parties. A clear example of this are public administrations and the high usage of PDF as a document format to exchange information. However, it cannot be considered as an asset to build innovative solutions.
'The specification is not included in any repository or catalogue of standards at national level. CAMSS Lists Of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
CAdES Baseline profile is an independent standard that can be implemented without dependencies on other technologies or platforms. Therefore, the specification can be implemented without hampering the interoperability but avoiding vendor lock-in.
'There are existing documentation and studies assessing the effectiveness and efficiency of LDAP. It is a comparison between LDAP 2 and LDAP 3. As well, the study shows the improvement of the different versions over time as resulting in more efficient protocol. Moreover, there is documentation about the language used by LDAP and how it improves responses to user queries, as well as the effectiveness to access and organize data. Difference between LDAP2 and LDAP3: https://learn.microsoft.com/en-us/previous-versions/windows/desktop/ldap/differences-between-ldap-2-and-ldap-3 Assessment of LDAP services in high availability environment: https://www.semanticscholar.org/paper/ASSESSMENT-OF-LDAP-SERVICES-IN-HIGH-AVAILABILITY-Marchel-Boldak/8c27ba354d6b70d803b2f56c4f3bcc2193efa879 Language efficiency of LDAP: https://www.fortinet.com/uk/resources/cyberglossary/ldap-authentication Effectiveness of LDAP: https://www.securew2.com/blog/ldap-explained'
The ISO specifications are published to be able to respond to a market need which represent a consensus of an expert group. In 2005 PDF/A was published which specifies how to use the Portable Document Format (PDF) 1.4 for long-term preservation of electronic documents. These facts demonstrate the maturity and market acceptance for its use in the development of products and services. PDF/A reference: https://www.iso.org/standard/38920.html https://www.iso.org/standard/50655.html
HTTP (Hypertext Transfer Protocol ) is a Transfer Protocol used for communication over a computer network. It is used to transfer data between administrations.
W3C has a defined and publicly available Process for the Development and approval process of the specification as a recommended standard. Also, a clear Release Notes tracking the changes of the different versions is archived. W3C Process document: https://www.w3.org/2018/Process-20180201/#Policies
"By implementing DQV, public administrations can assess the quality of the data they manage, including personal data. Ensuring high data quality is essential for maintaining the integrity and reliability of personal data, which contributes to protecting individuals' privacy and rights. DQV enables public administrations to identify and address data quality issues that could compromise the security or privacy of personal data. Data Quality Vocabulary: https://www.w3.org/TR/vocab-dqv/"
'The specification is designed to be platform-agnostic, which means that it can be implemented on any platform or operating system, such as Windows, Linux, or macOS. The specification is based on open standards and uses XML-based schemas to represent legal documents, which can be processed by a wide range of software systems and applications. AKN4EU reference: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/akn4eu'
The specification has been constantly evolving to adapt to users needs and to ensure the effective development of projects funded with public funds. Besides, its evolution is translated into several releases where improvements have been put in the focal point. The current version was released more than two years ago, by mid-2018. This fact together with its first publication in 2016 provides enough maturity for its use in the development of public products and services. Additionally, it is worth to note that this OpenPM has been evolved from previous Project Management Methodology, and therefore it contains a high level of lessons learned to improve its added value. OpenPM2 first edition reference: https://op.europa.eu/en/publication-detail/-/publication/0e3b4e84-b6cc-11e6-9e3c-01aa75ed71a1/language-en OpenPM ISA2: https://ec.europa.eu/isa2/solutions/open-pm2_en
Like all the IETF standards, IPsec is a free and open technical specification, built on IETF standards and licenses from the Open Web Foundation. IPsec is therefore licensed on a royalty-free basis. No IPR disclosures have been submitted directly on the IPsec specification (RFC 4301). See: https://tools.ietf.org/html/rfc3668 https://tools.ietf.org/html/rfc4301
"The Dataspace Protocol can simplify the delivery of European public services as it offers a framework for the management of International Data Spaces, which aligns with Europe's vision of data. It standardises secure environments for data exchange between government entities, service providers and citizens, improving interoperability and data flow, etc. IDSA Dataspace Protocol: https://docs.internationaldataspaces.org/ids-knowledgebase/v/dataspace-protocol/overview/readme"
The specification is not related to the publication of public data as open data. Therefore this criterion is not applicable to this specification.
CAMSS Assessment of RegOrg EIF Scenario v1.0.0
'While the PROV family of documents does not explicitly address data protection, its use in systems or applications can indirectly support data protection efforts through transparency, accountability, auditing, consent tracking, and security incident investigation. However, comprehensive data protection requires considering broader factors beyond the scope of PROV. PROV Primer document: https://www.w3.org/TR/prov-primer/ PROV Ontology: https://www.w3.org/TR/2013/REC-prov-o-20130430/ PROV Data Model: https://www.w3.org/TR/2013/REC-prov-dm-20130430/ PROV-AQ Security cosiderations: https://www.w3.org/TR/2013/NOTE-prov-aq-20130430/#security-considerations'
'Better Regulation Guidelines and Toolbox provides a set of guidelines to guarantee that policies and laws development, implementation and evaluation are properly established. Therefore, the Better Regulation Guidelines and Toolbox includes a set of recommendations, best practices and requirements whose purpose is to ensure and enhance the cross-border application and organisational interoperability as much as possible. Better Regulation Guidelines and Toolbox reference: https://commission.europa.eu/law/law-making-process/better-regulation/better-regulation-guidelines-and-toolbox_en'
The purpose of UTF-8 is not related to the implementation of the once-only principle. Therefore this criterion is not applicable specification.
'ESPD hasa been developed by the Publications Office of the EU. The specification can be accessed through the European platdorm Joinup, and also through the Ted Developer Docs. ESPD business handbook: https://docs.ted.europa.eu/ESPD-EDM/latest/xml_business_handbook.html Ted mainpage: https://ted.europa.eu/TED/main/HomePage.do ESPD joinup: https://joinup.ec.europa.eu/collection/eprocurement/solution/european-single-procurement-document'
'Together with other models or initiatives like eCertis, the ESPD fosters the cross-border participation in procurement, increasing competition and supporting economic growth. eCertis is a tool that helps to understand what kind of evidence can be used to fulfill a specific public procurement requirement in a European country. ESPD business handbook: https://docs.ted.europa.eu/ESPD-EDM/latest/xml_business_handbook.html European single procurement document and eCertis: https://single-market-economy.ec.europa.eu/single-market/public-procurement/digital-procurement/european-single-procurement-document-and-ecertis_en'
As the internet protocol stack, it allows connections and data exchange all over the internet. The internet protocol is the main enabler element to perform communications over networks. This fact together with its long haul demonstrates the market acceptance and the maturity for its use development of services and products. Moreover, the European Regional Internet Registry has a high number of IPs available in order to provide them when necessary. Even though, it is worth mentioning that IPv6 it is being gradually adopted by suppliers, vendors and public services. However, there are existing translation and transition methods between both versions that allow the normal connection between nodes using different Internet Protocol versions See: https://www.ripe.net/publications/news/about-ripe-ncc-and-ripe/getting-ready-for-ipv4-run-out
'Specification has the support of many communities listed in the following link as "Supporting Organizations", including Universities, private and public companies. Portal ETSI reference: https:// portal.etsi.org/webapp/workprogram/Report_WorkItem.asp?WKI_ID=56725'
No evidences have been found of the specification being included in a formal interoperability agreement between organisations involved in the European public services provision.
OASIS has defined a clear Technical Committee (hereby TC) process where all the stakeholders involved have the opportunity to participate in the development of the specification development process. OASIS guideline: https://www.oasis-open.org/policies-guidelines/casestudies
The purpose of CAdES is not related to the publication of public data as linked open data. Therefore, this criterion is not applicable to this specification. 5-star linked open data: https://www.w3.org/DesignIssues/LinkedData.html CAdES ISO reference: https://www.iso.org/standard/64756.html CAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/101700_101799/101733/02.01.01_60/ts_101733v020101p.pdf
The purpose of Ogg is not related to the availability of interfaces with internal information systems. Therefore, this criterion is not applicable to this specification. Ogg XIPH reference: https://xiph.org/ogg/doc/rfc3533.txt
As specification fostering the interoperability between public administrations, RDF helps to enhance the data exchange and reuse in a cross-border way and impacts positively on the development of eGovernment. This fact includes the support to Once-only principle implementation.
'The Open Data Protocol (OData) supports the creation of data services based on REST, which allow resources to be published and edited by web clients via HTTP messages. OData could allow a third-party information system to act on behalf of citizens who cannot, permanently or temporarily, make direct use of public services. In this sense, it can contribute to e-accessiblity. OData reference: https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#_Toc31358832 '
"EuroVoc is used to technogically maintain a single consistent definition of various domains (eg. Politics, Euopean Union). Therefore, EuroVoc's users such as the European Union institutions and the Publications Office of the EU use it consistently. EuroVoc Browser: https://eur-lex.europa.eu/browse/eurovoc.html?locale=en EuroVoc: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu /resource/dataset/eurovoc"
WSDL is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). Specifically, WSDL can define the interoperability aspects of the "Machine to machine interface" ABB of the EIRA Technical View. See: https://joinup.ec.europa.eu/solution/elis/distribution/eliscataloguev100betaxls
The purpose of the specifications is not related to the publication of Open Data. Therefore, this criterion is not applicable to this specification.
IPsec can be found for its use and implementation at IETF's website. See: https://tools.ietf.org/html/rfc4301
'TGF is designed to facilitate the modelling of business processes as it provides guidance for government organisations on how to transform their operations and services to be more citizen-centric, efficient and effective. It also provides guidance for process analysis, optimisation and optimization. TGF Specification: http://docs.oasis-open.org/tgf/TGF/v2.0/cs01/TGF-v2.0-cs01.html'
'The purpose of Core Location Vocabulary is not related to guarantee the authenticity and authentication of the roles agents involved in the data transactions. Therefore this criterion is considered not applicable to the specification. Core Location Vocabulary: https://interoperable-europe.ec.europa.eu/collection/semic-support-centre/solution/core-location-vocabulary/release/100'
The LegalDocML can be related also to contracts with legal bindings or relevance for the administration and regulatory boards. The specification can allow public administrations to define XML schemas for the reuse of information across borders including reference to contracts or other legal documents without requiring the submission or provision more than once. LegalDocML reference: https://www.oasis-open.org/committees/legaldocml/charter.php
'The application of the once-only principle in all EU Member States public administrations aims at reducing the administrative burden. EuroVoc fosters interoperability between public administrations, cross border services and impacts positively the development of eGovernment. EuroVoc: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource /dataset/eurovoc'
"EU Member States' trusted lists were established in EU and aimed primarily at supporting the validation of advanced electronic signatures supported by a qualified certificate and advanced electronic signature supported by both a qualified certificate and by a secure signature creation device, as far as they included as a minimum trust service providers supervised/accredited for issuing qualified certificates. This method can explicitly enable the secure and trustworthy processing of data as it is using an advanced electronic signature which is supported by a qualified certificate and a secure signature creation device. ETSI TS 119 612 specification: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf "
'DNS over HTTPS (DoH) is not directly designed to enable digital service delivery channels. Instead, DoH contributes to the security of DNS transactions. Therefore, this criterion is considered not applicable to this specification. DoH specification: https://datatracker.ietf.org/doc/html/rfc8484'
'E-ARK CSIP has not been found included in within the catalogue of recommended specifications of any Member State. CAMSS List of standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards'
'EIRA includes a whole set of enablers related to security at different levels. In this line, the specification includes specific set of requirements oriented to ensure data management, data exchange and collaboration upon data, while ensuring privacy and security. By providing specific perspectives and viewpoints related to security and privacy and how they include the data exchange, EIRA helps users when working on analysing the requirements for digital public services. There are specific enablers related to data exchange and data collaboration, such as Data Space related. These are related and complemented by security and privacy components. Additionally, elements such Trust enablers or blockchain can be consider assets and components that can help to ensure data integrity and data authenticity. EIRA reference: https://interoperable-europe.ec.europa.eu/collection/european-interoperability-reference-architecture-eira /solution/eira/release/610 EIRA Github Repository: https://github.com/CarTool-EC/EIRA'
'The specification was developed in 2012 and has been implemented at European level, and it has been evolved together with the application profile used in the European Platform for the reusability of interoperability Solutions, Joinup. ADMS in Joinup: https://joinup.ec.europa.eu/solution/asset-description-metadata-schema-adms/about'
The Working Group in charge of developing the specification initially provides a light-weight maintenance plan however, it is not a complete maintenance and support process. Additionally, it is worth noting that the projects who adopted the specification, are planning to maintain the specification. For instance, the EOSC-pillar project will contribute to the maintenance of the specification for 3 years (from July 2019 to June 2022). However, such contributions are not enough to consider that the maintenance of the specification is guaranteed over a long time period
"TOSCA fosters and simplifies digital exchange in network specific domains. It is the case of CELAR and Indigo-DataCloud projects, which aim to provide a contact point for European research centers to discover, access, use and reuse a wide range of resources for advanced data-driven activities. TOSCA reference: https://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.3/os/TOSCA-Simple-Profile-YAML-v1.3-os.html CELAR reference, 'Translational cancer detection pipeline over CELAR Application and Evaluation' document: https://cordis.europa.eu/project/id/317790/reporting Indigo-DataCloud reference: https://www.indigo-datacloud.eu/#history"
'Apart from the TOSCA Technical Committee, there is active participation from external open communities that creates open information and encourages the publication of such data on international platforms (e.g. Github, Confluence), including European platforms. TOSCA-Github reference: https://github.com/oasis-open/tosca-community-contributions TOSCA-Confluence reference: https://wiki.onap.org/display/DW/TOSCA+Task+Force'
"Although the EN 303 645 specification is not a Harmonised European Standard (HEN) following Radio Equipment Directive (RED) specification (see J. Pandza's presentation on the ENISA Cybersecurity Standardisation Event, and HEN reference), the specification is a European Standard (see EN 303 645 reference). EN 303 645 reference: https://www.etsi.org/deliver/etsi_en/303600_303699/303645/02.01.01_60/en_303645v020101p.pdf ENISA Cybersecurity Standardisation Event 2021, Jasper Pandza presentation: https://www.enisa.europa.eu/events/cybersecurity_standardisation_2021/std-2021-presentations HEN reference: https://ec.europa.eu/growth/single-market/european-standards/harmonised-standards_en#:~:text=A%20harmonised%20standard%20is%20a%20European%20standard%20developed,the%20European%20Commission%20to%20one%20of%20these%20organisations."
'By implementing the ISO 19944-1 classification scheme consistently, organizations can establish a structured and standardized approach to data management. This can make it easier to identify, retrieve, and reuse relevant information when needed. ISO/IEC 19944-1 specification: https://www.iso.org/standard/60545.html'
7 Member States are recommending TLS 1.2 in their ICT Catalogues. See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'The primary goal of the Open Archival Information System (OAIS) is to provide a reference model for digital preservation systems, not for modeling business processes. However, the OAIS reference model can be used as a framework for developing digital preservation strategies and workflows, which may include business processes. OAIS specification: https://public.ccsds.org/Pubs/650x0m2.pdf'
'Only Member States, in collaboration with the European Commission, are in charge of sumbitting any amendment on the NUTS classification. Therefore, NUTS has support from several communities which provide public support and manage its maintenance. European Commission reference, Regulation (EC) No 1059/2003 document, Article 5: https://eur-lex.europa.eu/legal-content/EN/TXT/?qid=1405939838475&uri=CELEX:32003R1059'
'The ETSI and any of its committees, in charge of the development of ETSI EN 319 422, operates under the ETSI Intellectual Property Rights (IPRs) and IPR Policy. The specification is licensed on a (F)RAND basis. Intellectual Property Rights Policy, ETSI ownership of IPRs section: https://www.etsi.org/intellectual-property-rights'
'HTTP can contribute to the secure exchange of data by providing a foundation for implementing basic security measures. For example, The Cache-Control directives, offer a mechanism to restrict the unintended storage or reuse of sensitive information. For instance, the "no-store" directive prevents caches from storing sensitive data, contributing to data security. However, they don't provide a complete framework for secure data processing. HTTP/1.1, RFC 2616 Reference: https://www.rfc-editor.org/rfc/rfc2616 HTTP/1.1 Authentication, RFC 9110 Reference: https://www.rfc-editor.org/rfc/rfc9110#name-http-authentication'
'As an organisational enabler, EN 16234-1 e-CF aims to provide a standard that includes some other essentials for any IT professional, such as their basic skill set, their education and training qualification and certification, and the ethics around worker development. In this sense, the specification is not only usable beyond the business-specific domain, but also is designed to be implemented in any other domain. Joinup-2021 Rolling Plan for ICT Standardisation reference, Education, Digital skills and Digital learning section: https://joinup.ec.europa.eu/collection/rolling-plan-ict-standardisation/education-digital-skills-and-digital-learning'
IETF has a formal review and approval so that all the relevant stakeholders can formally appeal or raise objections to the development and approval of specifications. Each distinct version of an Internet standards-related specification is published as a "Request for Comments" (RFC) document. During the development of a specification, draft versions of the document are made available for informal review and comment by placing them in the IETF's "Internet-Drafts" directory. IETF therefore makes available the working documents to a wide audience, facilitating the process of review and revision. See: https://www.ietf.org/standards/process/ https://tools.ietf.org/html/rfc2026
'ETSI TS 119 511 specifies the policy and security requirements of the preservation services schemes applicable to a given preservation storage model which outlines how preservation evidences are to be created and validated by defining the relationships among the preservation schemes, preservation profiles and they are related on a given business-specific trust service. ETSI TS 119 511 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119511/01.01.01_60/ts_119511v010101p.pdf'
"This specification contains a specific section that addresses interfaces, APIs and interoperability regarding cloud services. By promoting an international standard for cloud services, the specification enables the exposure of interfaces to access the public administration's services. The standard guides the structuring of these interfaces to facilitate interoperability, taking into account different aspects like transport protocols, data formats, and principles for effective communication and integration. ISO 19941: https://www.iso.org/obp/ui/en/#iso:std:iso-iec:19941:ed-1:v1:en"
'The purpose of ShEx is not related to the long-term preservation of information; therefore, this criterion does not apply to this specification. ShEx primer document: https://shexspec.github.io/primer/ ShEx Community Group: https://www.w3.org/community/shex/ ShEx Github: https://github.com/shexSpec/spec/issues'
The purpose of the specification is not related to the delivery of multilingual services. Therefore, this criterion is not applicable to this specification.
Like all the IETF standards, HTTPS is a free and open technical specification, built on IETF standards and licenses from the Open Web Foundation. HTTPS is therefore licensed on a royalty-free basis. See: https://tools.ietf.org/html/rfc3668
'JSON can be an integral part of the data layer within the digital service delivery channels, facilitating the exchange of structured information between different components or layers of a digital service delivery system. JSON specification: https://www.ecma-international.org/wp-content/uploads/ECMA-404_2nd_edition_december_2017.pdf'
'The OAIS reference model has been widely adopted by the digital preservation community worldwide, including in Europe, where it is used as a framework for digital preservation activities in many organizations. However, it is not a formal European standard, nor is it recognized as a standard by the European Union. OAIS specification: https://public.ccsds.org/Pubs/650x0m2.pdf'
'ISAE 3402 was developed to provide an international standard of assurance in the context of information security and confidentiality that could enable accountants to issue a report for use by user organizations and their (user) auditors on controls of outsourced services that have an impact on financial information. In this context, these same consultants / auditors also offer recommendations to improve the control of the confidentiality of these services, improving, for example, software applications such as SAP. SAP trust center: https://www.sap.com/about/trust-center/certification-compliance/sap-application-management-services-soc-isae3402-audit-report-2020-h1.html ISAE 3402 reference: https://www.ifac.org/system/files/downloads/b014-2010-iaasb-handbook-isae-3402.pdf'
There are documents that compare different audio formats that forms Ogg. From there, it can be assessed the efficiency and effectiveness of the usage of Ogg. Audio formats comparison: https://stsaz.github.io/fmedia/audio-formats/ Ogg XIPH reference: https://xiph.org/ogg/doc/rfc3533.txt
'The ebXML specification is a family of XML-based standards that provides an open, XML-based infrastructure that enables the interoperable use of electronic business information. In this sense, ebXML is independent of any platform because XML it is so. Therefore, ebXML is platform-agnostic. ebXML reference: http://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html'
'The specification does not provide specific provisions for such agreements, but the core of the OSI is based on the idea to facilitate the interconnection of systems/processes via multiple layers, therefore it is possible to reach interoperability agreements per each layer (specially on the top ones like representation). OSI reference https://www.iso.org/standard/20269.html'
'W3C provides a Markup Validation Service for free to validate XML 1.1 implementations. See: https://validator.w3.org/'
The purpose of PAdES is not related to the delivery of multilingual public services. Therefore, this criterion is not applicable to this specification. PAdES ISO reference: https://www.iso.org/standard/67937.html PAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/102700_102799/10277801/01.01.01_60/ts_10277801v010101p.pdf
'Registered Organization Vocabulary is designed to be extensible by allowing the inclusion of terms from other vocabularies and through the creation of application profiles that can introduce new classes and properties. Registered Organization Vocabulary reference: https://www.w3.org/TR/vocab-regorg/'
IETF has a formal review and approval process so that all the relevant stakeholders can formally appeal or raise objections to the development and approval of specifications._x000D_ _x000D_ Each distinct version of an Internet standards-related specification is published as part of the Request for Comments (RFC) document series. This archival series is the official publication channel for Internet standards documents and other publications. _x000D_ _x000D_ During the development of a specification, draft versions of the document are made available for informal review and comment by placing them in the IETF's Internet-Drafts directory, which is replicated on a number of Internet hosts. This makes an evolving working document readily available to a wide audience, facilitating the process of review and revision. _x000D_ _x000D_ See:_x000D_ https://www.ietf.org/standards/process/ _x000D_ https://tools.ietf.org/html/rfc2026
'Although OAIS is not directly related to security issues, annex F from the specification provides some guidelines for the secure exchange of data such as for the validation of the Information Producer identity, or electronic signatures in order to safeguard communications between the Archive and the Producer. OAIS specification: https://public.ccsds.org/Pubs/650x0m2.pdf'
'The purpose of this Core Vocabulary is to harmonise public services (information) stored in different local, regional and national information sources, allowing the information to be searched and shared easily within and across public administrations all over Europe. CPSV-AP Joinup webpage: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/core-public-service-vocabulary-application-profile/release/22'
'TLS 1.3 reduces the risk of unauthorised access and data breaches by guaranteeing that all post-handshake data is encrypted and visible only to the communicating endpoints. This is achieved through the secure encryption negotiated during the handshake. Server authentication is mandatory, while client authentication, using mechanisms like client certificates, is optional. TLS 1.3 Cryptographic Computations Reference: https://www.rfc-editor.org/rfc/rfc8446.html#section-7'
According to the 5 star Open Data model suggested by Tim Berners-Lee about how to publish linked data, the second star corresponds to make data available as structured data, an area of application of XML. Additionally, RDF is a W3C specification that defines XML syntax for RDF, the de facto standard for publishing Open Data. See: https://5stardata.info/en/ https://www.w3.org/TR/rdf-syntax-grammar/
XHTML is a business domain agnostic specification that can be reused in a cross-domain way. XHTML W3C reference: https://www.w3.org/TR/xhtml1/
'The specification is not related to the publication of public data as open data. Therefore this criterion is not applicable to this specification. IPSec reference, What IPSec Does: https://datatracker.ietf.org/doc/html/rfc4301#section-3.1'
The specification is available for free at the European Collaborative platform Joinup. See: https://joinup.ec.europa.eu/solution/web-services-description-language-wsdl-version-20-part-0-primer
JSON is available for its use, study and implementation at ECMA International and EITF's webpages. See: https://www.ecma-international.org/publications/standards/Ecma-404.htm https://tools.ietf.org/html/rfc8259
"The purpose of schema.org is not related to the protection of personal data managed by public administrations. Therefore, this criterion is not applicable to this specification. Schema.org homepage reference, 'About Schema.org' section: https://schema.org/docs/about.html"
The purpose of FTP is to allow the exchange of documents between systems and applications.
'The purpose of REST is not related to the reuse of information. Therefore, this criterion is not applicable to this specification. REST reference: https://restfulapi.net/'
IPSec is publicly available for implementation and use, and therefore for everyone to study, for free on IETF's webpage. See: https://tools.ietf.org/html/rfc4305
'Registered Organization Vocabulary is associated to "Controlled Vocabulary", "Data", "Data Model", "Hash Code", "Linked Data", "Linked Open Data", "Metadata" and "Open Data" ABB under the Semantic view in the EIRA Library of Interoperability Specifications (ELIS). Registered Organization Vocabulary reference: https://www.w3.org/TR/vocab-regorg/ EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/v610'
'The purpose of MIME is to allow the exchange of documents between systems and applications. MIME specification: https://tools.ietf.org/html/rfc2045'
'The XFDL specification is based on an XML structure, providing a standardised format for data collection and form submission. However, there are other modern technologies, such as HTML5, which are easier to implement. Finally, the specification does not simplify the delivery of public services. Extensible Forms Description Language reference: https://www.w3.org/TR/NOTE-XFDL'
'Insufficient information is available to conclusively determine whether this criterion is met. Furthermore, the specification does not appear to be designed with the explicit goal of enhancing data exchange security and privacy. Therefore, this criterion is considered not applicable to this specification. ELI reference: https://eur-lex.europa.eu/eli-register/about.html'
'NFVI is intended to be used in virtualised ecosystems. Because the NFVI is a distribution set of NFVI-nodes in multiple locations that supports the locality and latency requirements of NFV use cases, the specification also provides network connectivity, and therefore can be implemented in different business domains. NFVI Deliver, Infrastructure Overview: https://www.etsi.org/deliver/etsi_gs/NFV-INF/001_099/001/01.01.01_60/ ISG NFV Deliver, Terminology for main concepts: https://www.etsi.org/deliver/etsi_gr/NFV/001_099/003/01.06.01_60/'
SHACL is a specification developed and maintained by W3C and identified by the MSP for its use in public procurement in Europe. As the specification is available for free and on a FRAND basis, this reduces the administrative burden.
WS-BPEL is available for its study and use at OASIS’s webpage. Therefore, it can be reused by the organisations, administrations, open communities, etc. that developed it. WS-BPEL OASIS reference: http://docs.oasis-open.org/wsbpel/2.0/OS/wsbpel-v2.0-OS.html
The purpose of Data on the Web Best Practices is not related to the comprehensibility of administrative information, data or services. Therefore, this criterion is not applicable to this specification. Data on the Web Best Practices W3C: https://www.w3.org/TR/dwbp/
'The SHACL specification is developed by a non-European organisation. Therefore, the specification cannot be considered a European standard. SHACL W3C reference: https://www.w3.org/TR/shacl/'
'Accessibility is a quality dimension in DQV as the degree to which data can be accessed in a specific context of use, particularly by people who need supporting technology or special configuration because of some disability. Besides, accessibility is mentioned across the specification for different examples of the vocabulary. Data Quality Vocabulary: https://www.w3.org/TR/vocab-dqv/'
"Being an ISO standard, OAIS has restricted IPR disclosures and requires payments to access the specification's documentation. OAIS foreword: https://www.iso.org/obp/ui/#iso:std:iso:14721:ed-2:v1:en"
The W3C Royalty-Free IPR licenses granted under the W3C Patent Policy apply to all W3C specifications, including XSD. See: https://www.w3.org/TR/patent-practice#ref-AC
'Back in 2021, The AMQP Technical Committee (TC) released specifications for public review, during which they actively invite and encourage feedback from stakeholders. AMQP TC Release Announcement: https://groups.oasis-open.org/communities/tc-community-home2?CommunityKey=969c2da1-55c4-4bba-92d2-018dc7d3efe9#announcements Invitation to comment on three new AMQP specifications: https://www.oasis-open.org/2021/04/01/invitation-to-comment-on-three-new-amqp-specifications/ OASIS AMQP Reference: http://docs.oasis-open.org/amqp/core/v1.0/amqp-core-complete-v1.0.pdf'
'The specification is included in Belgium national catalogue of recommended specifications. Belgium National Catalogue: https://www.belgif.be/page/specifications.en.html'
As a document exchange format, PDF is a valuable tool for sharing information through the internet. Allowing to share data and information the standard foster the visibility of administration data and services. Additionally, it eases the decision-making process within administrations.
The main purpose of CCCEV is to ease the creation of a repository of reusable criteria in machine-readable formats. The CCCEV together with other common vocabularies fosters the publication of datasets representing criterion, evidence and evidence issuers. Core Criterion and Core Evidence Vocabulary reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-criterion-and-core-evidence-vocabulary Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/en/
'The purpose of IPsec is not related to the delivery of multilingual services. Therefore this criterion is not applicable to this specification. IPSec reference: https://www.rfc-editor.org/rfc/rfc6071.html'
Like all the IETF standards, IPv4 is a free and open technical specification, built on IETF standards and licenses from the Open Web Foundation. IPv4 is therefore licensed on a royalty-free basis. See: https://tools.ietf.org/html/rfc3668
'The Core Criterion and Core Evidence Vocabulary is designed to support the exchange of information between organisations or persons (more generally Agents) defining Requirements and organisations or persons responding to these Requirements by means of structured or unstructured Evidences. Core Criterion and Core Evidence Vocabulary reference (v1.0.0): https://joinup.ec.europa.eu/release/core-criterion-and-core-evidence-vocabulary-v100 '
ELI is adopted as a system to make legislation available online in a standardised format. ELI progresses toward making legal metadata more reusable, it should lower the barrier for data consumers to retrieve the ELI metadata from an ELI provider. A way of achieving this is by legislation publishers describing and publishing ELI datasets. ELI reference: https://eur-lex.europa.eu/eli-register/about.html
The specification is currently implemented in several initiatives in the public sector. This is a key point that reflects the market acceptance of the specification by the public administrations and institutions in Europe. Some implementations of the ADMS are Metadata Registry (MDR), ADMS-enabled description of a vocabulary implemented in PoolParty Thesaurus Manager 3.1.0, and the Implementation for the XRepository of the German Federal Ministry of the interior. ADMS in Joinup: https://joinup.ec.europa.eu/solution/asset-description-metadata-schema-adms/about
The Council Conclusion where ELI is defined sets out conclusions involving how Member States are called on to implement ELI to properly allow other administrations, business and citizens access the legal documentation. ELI reference: https://eur-lex.europa.eu/eli-register/about.html Council Conclusion https://eur-lex.europa.eu/eli-register/about.html
'There are already existing documents and studies assessing WSDL performance and its features. The main topic are effectiveness while discovering, automatically classify web services or the poor query results. Improving Web Service descriptions for effective service discovery: https://core.ac.uk/download/pdf/82569095.pdf Towards Effective Service Discovery using Feature Selection and Supervised Learning Algorithms: https://thesai.org/Downloads/Volume10No5/Paper_25-Toward_Effective_Service_Discovery.pdf'
'E-ARK CSIP can indirectly scope comprehesibility of administrative procedures and services by promoting the use of descriptive metadata. Descriptive metadata can provide information about the administrative context of records, such as their origin, creator, date of creation, and other relevant administrative details. This metadata helps users understand the administrative procedures and services associated with the records. E-ARK CSIP specification: https://earkcsip.dilcis.eu/#introduction'
'At the time being TOSCA provides a default XML or YAML-based file dedicated to its implementation (that is, the Cloud Service Archive -CSAR, or TOSCA metadata file, and the TOSCA Simple Profile in YAML Objective section). In this sense, the specification is not technology-agnostic. TOSCA reference, Cloud Service Archive (CSAR) reference: https://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.3/os/TOSCA-Simple-Profile-YAML-v1.3-os.html#_Toc26969474 TOSCA reference, TOSCA Simple Profile in YAML Objective section: https://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.3/os/TOSCA-Simple-Profile-YAML-v1.3-os.html#_Toc26969412'
'ODRL provides a flexible and expressive framework for access control by allowing the definition of sophisticated policies governing the use of digital content. Implementers can leverage these features to create access control mechanisms tailored to their specific use cases and requirements. W3C specification reference: https://www.w3.org/TR/odrl-vocab/#vocab-core'
'WAI-ARIA enhances web accessibility, it is not designed to handle authentication and authorization concerns. Therefore, this criterion is not applicable to this specification. WAI-ARIA reference: https://www.w3.org/TR/wai-aria-1.2/'
The purpose of WS-BPEL is not related to the delivery of multilingual public services. Therefore, this criterion is not applicable to the specification.
DCAT is publicly available for implementation and use for free on Github. See: https://github.com/w3c/dxwg/ https://www.w3.org/TR/vocab-dcat-2/
'Section 6.4 of the specification is dedicated to the Authorization and Access Control. The role of authorization in the context of access control is to ensure that a custodian can verify that a requestor is allowed to perform a requested action. Access may be restricted by requestor identity, by requestor location, by requestor role, by date and time and so forth. As part of the access control policy the custodian may require that the requestor proves she has authorization. Authorization may be granted directly based on attributes of the requestor or may be granted only after 3rd party verification of authority. ETSI Context Information Management (CIM); Security and Privacy: https://www.etsi.org/deliver/etsi_gr/CIM/001_099/007/01.01.02_60/gr_cim007v010102p.pdf'
As a protocol for data exchange, HTTP allows the exchange of information with interfaces of public administration systems.
'There are Directives regulating participation on the development of standards. Participation is limited to membership approval and sometimes the payment of a fee. ETSI’s standards-making process has been clearly defined after years of experience. The organisation has adopted the open approach which means direct participation and consensus as a basis to develop standards. All the stakeholders have the opportunity to participate directly in the process of standardisation through the technical committees created to develop ETSI’s technical specifications and standards. The decision-making process includes a public review, where stakeholders involved can provide technical feedback in order to enhance and maximize the quality and accuracy of the standards. ETSI Portal reference: https://portal.etsi.org/TB-SiteMap/esi/esi-activities'
'The Asset Administration Shell (AAS) has no relation to e-accesibility, therefore the criterion is not applicable. Details of the Asset Administration Shell (AAS) https://industrialdigitaltwin.org/en/wp-content/uploads/sites/2/2024/06/IDTA-01001-3-0-1_SpecificationAssetAdministrationShell_Part1_Metamodel.pdf'
'The purpose of this CIM NGSI-LD API is not related to e-accessibility. Therefore, this criterion is considered not applicable to this specification. GS CIM 009: https://www.etsi.org/deliver/etsi_gs/CIM/001_099/009/01.07.01_60/gs_CIM009v010701p.pdf'
DNS is a de-facto standard. Therefore, it is sufficiently mature and has sufficient market acceptance for its use in the development of products and services. See: https://tools.ietf.org/html/1034 https://tools.ietf.org/html/1035 https://developers.google.com/speed/public-dns https://www.opendns.com/
'After researching there has been no success finding any assessments about the specification effectiveness. ETSI TS 119 614-1 reference: https://www.etsi.org/deliver/etsi_ts/119600_119699/11961401/01.01.01_60/ts_11961401v010101p.pdf'
'Since EIRA is a reference architecture and covers all LOST views, it can help to plan the digital public services in alignment with transparency implications such as making visible the different data, rues and services ensuring that users and public servants can clearly identify what happens with and within the public services. EIRA reference: https://interoperable-europe.ec.europa.eu/collection/european-interoperability-reference-architecture-eira /solution/eira/release/610 EIRA Github Repository: https://github.com/CarTool-EC/EIRA '
'ISO 3166-1 is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, ISO 3166-1 can define the interoperability aspects of the Data Set ABB of the EIRA Semantic View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/v110'
'FTP is an exclusive protocol created solely for transferring files, but it lacks security for the transmitted data. Nevertheless, there are extensions available for FTP that address this issue by providing secure information delivery. One such extension is FTP over TLS, commonly referred to as FTPS, which employs Transport Layer Security (TLS) to safeguard FTP communications over a network. FTP Specification Reference: https://datatracker.ietf.org/doc/html/rfc959 Securing FTP with TLS Reference: https://tools.ietf.org/html/rfc4217'
'While DoH enhances the confidentiality of DNS queries, visibility into administrative procedures, rules data, and services is more closely associated with other technologies and standards. For visibility into web services, you might consider protocols like HTTP, HTTPS, or APIs that define how data and services are accessed and interacted with over the web. DoH specification: https://datatracker.ietf.org/doc/html/rfc8484'
"The EN 303 645 specification addresses the most significant and widespread security weaknesses. Due to the large consumer IoT landscape, it is inevitable that the applicability of the provisions (recommendations) will depend on the device, which gives the specification a degree of flexibility (see 'Reporting implementation' section). In this sense, the specification allow for partial implementation. EN 303 645 reference, 'Reporting implementation' section: https://www.etsi.org/deliver/etsi_en/303600_303699/303645/02.01.01_60/en_303645v020101p.pdf"
The application of the once-only principle in all EU Member States public administrations aims at reducing the administrative burden. To achieve this, interoperability between public administrations is a sine qua non condition. XAdES function is to facilitate the electronic signature in compliance with eIDAS, campliant with the European Directive of electronic signature of the European Parliament and the Council. Concequently it can be concluded that through this functions it promotes the once-only principle
'Although the Advanced Encryption Standard cannot be found in any repository of standards at European level, the standard is mentioned in the "Cryptographic security: Critical to Europe's digital sovereignty" document, from the European Parliment, as a main cryptographic algorithm. In addition, the Advanced Encryption Standard can also be found in the eDelivery specification. "Cryptographic security: Critical to Europe's digital sovereignty" document: https://www.europarl.europa.eu/RegData/etudes/BRIE/2024/766237/EPRS_BRI(2024)766237_EN.pdf eDelivery specification encryption: https://ec.europa.eu/digital-building-blocks/sites/pages/viewpage.action?pageId=866025549 AES Standard Reference: https://csrc.nist.gov/pubs/fips/197/final'
After checking the different standard catalogues at supra-national level, there is no evidence of the inclusion of ADMS within any European catalogue of standards. ICT technical specifications: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en CEN search tool catalogue: https://standards.cen.eu/dyn/www/f?p=CENWEB:105::RESET:::: CENELEC search tool catalogue: https://www.cenelec.eu/dyn/www/f?p=104:107:0::::FSP_LANG_ID:25
'Like the IPv6 specification, IPv4 can utilise many mechanisms, some included in IPsec and others not, that can enhance data accuracy. Examples of these include the authentication of agents involved in data transactions, access control lists to deny unwanted access, and the AH and ESP protocols, which help transfer data securely. All of these mechanisms combined can contribute to achieving data processing accuracy. IPsec protocol: https://www.cloudflare.com/learning/network-layer/what-is-ipsec/ AH and ESP protocols: https://www.ibm.com/docs/en/zos/2.1.0?topic=ipsec-ah-esp-protocols IPv4 ACL: https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst2960l/software/15-2_6_e/configuration_guide/b_1526e_consolidated_2960l_cg/m_sec_acls_cg_danube_2960l_cdb.html IPv4 authentication agent: https://community.rsa.com/s/article/IPv4-IPv6-Authentication-Agents-aa7bd0d4'
The purpose of UDDI is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification.
'The PROV family of documents allows for the reuse of relevant information by capturing and representing provenance information in a standardized and structured manner. It facilitates the capture of context, traceability, decision-making processes, and enables discovery and retrieval, supporting the reuse of data, processes, and decisions when needed. PROV Primer document: https://www.w3.org/TR/prov-primer/ PROV Ontology: https://www.w3.org/TR/2013/REC-prov-o-20130430/ PROV Data Model: https://www.w3.org/TR/2013/REC-prov-dm-20130430/'
"SMP is not included in any Member States' catalogues of recommended specifications. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards"
There is not an explicit assessment of the effectiveness and efficiency of OWL2. However, in the following link, there is a comparison of the different OWL2 profiles. This document describes three profiles of OWL2, each of which achieves efficiency differently and is useful in different application scenarios. _x000D_ Also, there are studies not directly related to the OWL effectiveness or efficiency that include disclosures about the relevance of OWL for the effective representation of knowledge in different knowledge domains._x000D_ OWL2 Profiles W3C reference: https://www.w3.org/TR/owl2-profiles/ Use of ontologies for the effective representation of Knowledge: https://www.sciencedirect.com/science/article/pii/S2210832717300649
XAdES does not define a cross-sector reusable data model, but defines an electronic signature format. XAdES ISO reference: https://www.iso.org/standard/56025.html XAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/101900_101999/101903/01.04.02_60/ts_101903v010402p.pdf
The purpose of WS-Security is not related to the reduction of administrative burderns. Therefore, this criterion is not applicable to the specification.
'The purpose of DNS is not related to e-accessibility. Therefore this criterion is not applicable specification. DNS IETF reference: https://www.ietf.org/rfc/rfc1034.txt'
'MIME is designed to handle various types of content, including text, and it provides mechanisms for specifying character sets and language information to support multilingual communication. MIME specification: https://tools.ietf.org/html/rfc2045'
XAdES is part of the electronic signature stack of specifications, this group of specifications are aimed to ensure the availability and validation of signed data. Concquently, the implementation of eSignatures reduces the administratives burdens of the administration.
IPv6 is available at Joinup, the European collaborative platform for reusable solutions. See: https://joinup.ec.europa.eu/solution/ietf-rfc-2460-1998-internet-protocol-version-6-ipv6-specification/distribution/ietf-rfc-2460-1998-internet-protocol-version-6-ipv6-specification
EuroVoc is not included in any national catalogue of recommended specifications whose Member State NIF is fully aligned with at least 4 out of 5 sections of the EIF according to NIFO factsheets. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'Within the Roy Fielding dissertation of REST you can find a chapter that addresses the experience and lessons learned from applying REST. The evaluation of effectiveness, as outlined in the dissertation, is based on the versatility and domain-agnostic nature of REST. R. Fielding dissertation. Chapter 6: experience and evaluation. https://www.ics.uci.edu/~fielding/pubs/dissertation/evaluation.htm'
XSLT is a language for transforming XML documents, compliant with the European Directive and included to the ISA programme. It is available for its reuse to developed it. See: https://www.w3.org/TR/xslt-30/
At the moment of performing the assessment, SAML 2.0 is widely used to secure and authenticate access to the internal and external platforms as eases the single sign-on (SSO). These types of resources are included in the development of platforms and services, including innovative solutions.
'While DCAT-AP is not specifically designed to facilitate organizational interoperability agreements, the specification can contribute to this goal by providing a standardized way to describe and share data, making it easier for organisations to discover and use data that is published by others. DCAT-AP Specificatio: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/dcat-application-profile-data-portals-europe/release/200'
'The GITB TDL is used in the GITB test bed software, nonetheless it is not tied to it. It can also be processed by any test bed implementation that conforms to the GITB specifications. Therefore, the GITB TDL can be platform-agnostic as long as the platform is TDL compliant. GITB TDL reference: https://www.itb.ec.europa.eu/docs/tdl/latest/introduction/index.html#where-is-it-used'
'EuroVoc ensures and enables data processing accuracy as its original purpose was to provide the information management and dissemination services with a coherent indexing tool for the effective management of documentary resources produced by EU institutions. Moreover, its standardized terms helps ensure consistent and clear information categorization, indirectly improving data accuracy. EuroVoc: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource /dataset/eurovoc'
CSS is currently being used by the EUR-Lex, the European gateway to EU Law for the presentation of the different types of documents that it includes. EUR-Lex is run by the Publications Office of the European Union with the aim to provide official and comprehensive access to EU legal documents. Presentation style sheets EU Vocabulary: https://op.europa.eu/en/web/eu-vocabularies/presentation-style-sheets EUR-Lex: https://eur-lex.europa.eu/homepage.html?locale=en
The European Union considers the IPv6 as very important to "ensure the cross-border interoperability of online services and the digitisation of European public administrations for the ISA2 goals" See: https://ec.europa.eu/isa2/sites/isa/files/ipv6_framework_for_european_governments_0.pdf
There are no Member States recommending W3C Best Practices in their ICT National Catalogues as it is a document related to the publication and usage of data on the Web designed to help support a self-sustaining ecosystem. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
ASiC Baseline Profile is part of the electronic signature stack of specifications, this group of specifications are aimed to ensure the availability and validation of signed data. Therefore, the implementation of eSignatures involving ASiC Baseline Profile fosters secure and trustworthy data exchange.
'TrainingDML-AI Standard allows for extension. It provides a high-level training data information model and allows for extended information models specific to various ML applications. OGC TrainingDML-AI Standard: https://docs.ogc.org/is/23-008r3/23-008r3.html'
'The TGF is designed to provide a framework that can fit any domain within the digital government transformation management, allowing for its usage and implementation across business domains. TGF specification: http://docs.oasis-open.org/tgf/TGF/v2.0/cs01/TGF-v2.0-cs01.html'
'The specification can support the semantic layer by offering a taxonomy for business data on transactional level. EIRA Library of Interoperability Specifications (ELIS), these semantic layer would comprise the following ABBs: Semantic View: Representation Applicable Profile Technical View: Data Transformation Component Data Transformation Service'
The purpose of Ogg is not related to the implementation of the once-only principle. Therefore, this criterion does not apply to this specification. Ogg XIPH reference: https://xiph.org/ogg/doc/rfc3533.txt
"There is no evidence of available studies directly assessing the specification's effectiveness. However, there are some use case evaluations submitted by (non-)European administrations where effectiveness is analysed. It is the case of Croatia, which sponsored a study (through the Ekonomski institut, Zagreb) on the implementation of NUTS in its territory (see EconStor Publications reference, NUTS implementation document); and more specifically, on the implementation and suitability of NUTS level 2, which raised a lot of debate at the time of the study. EUROSTAT reference, NUTS Principles and Characteristics section: https://ec.europa.eu/eurostat/web/nuts/principles-and-characteristics EconStor Publications reference, Croatia's NUTS implementation document: https://www.econstor.eu/bitstream/10419/115958/1/ERSA2003_096.pdf Ekonomski institut reference, Ivana Rasic document authoring: https://www.eizg.hr/about-us/employees/researchers/ivana-rasic-phd/218"
'ESPD is primarily designed for use in public procurement, nonetheless, its basic principles and approach could potentially be adapted to support data collection and standardization in other domains as well. However, any such adaptations would require careful consideration of the specific requirements and needs of the domain in question. ESPD Business handbook: https://docs.ted.europa.eu/ESPD-EDM/latest/xml_business_handbook.html'
'OAS is included in the catalogues of Malta and The Netherlands. The national interoperability framework of The Netherlands is fully alligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. Malta, nonetheless, does not have a high performance, being aligned only with two sections of the EIF. National Catalogue of The Netherlands: https://www.forumstandaardisatie.nl/open-standaarden National Catalogue of Malta: https://mccaa.org.mt/Section/Content?contentId=1243 NIFO Factsheets: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public-administration-factsheets-2021'
'Web Services Description Language (WSDL) itself does not inherently include features or mechanisms for ensuring the protection of personal data managed by public administrations or any other entities. WSDL is primarily focused on describing the interfaces and operations of web services, providing a standardized way to define the contract between service providers and consumers. W3C WSDL specification: https://www.w3.org/TR/wsdl20/'
'Currently, JSON is a widely used specification for data interchange between applications and platforms. It is used in a REST API applications in order to ensure data exchange, this application is extensively used for the creation of solutions, including innovative ones. JSON API specification: https://jsonapi.org/ Best practices for REST API design: https://stackoverflow.blog/2020/03/02/best-practices-for-rest-api-design/ '
HTTPS is publicly available for implementation and use for free on IETF's webpage. See: https://tools.ietf.org/html/rfc2818
'There are several studies and documentation analysing the use of the IETF Time Stamp Protocol with different purposes and putting emphasis on its usage as an efficient way to implement Time-stamp services. In "Design and Implementation of a RFC3161-Enhanced Time-Stamping Service" it is designed and implemented a RFC3161-compliant trusted time-stamping service (TTS) over the Internet. Moreover, in "Study about the impementation of Secure Time Stamp Device", it is discussed the design of a Secure Time Stamp device used to securely timestamp digital data, such as computer documents, files, and raw binary data of arbitrary format. Design and Implementation of a RFC3161-Enhanced Time-Stamping Service: https://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.101.7115&rep=rep1&type=pdf Study about the impementation of Secure Time Stamp Device: https://www.sans.org/reading-room/whitepapers/vpns/analysis-secure-time-stamp-device-746'
'Requirements stated by ETSI TS 119 511 have been thought to enable the long-term preservation of electronic signatures, in which case it also includes the retrieval of these electronic signatures through a storage system. The features provided by this specification are considered very valuable in reducing the administrative burden, as it facilitates the storage and preservation of data, ensuring that document signatures remain valid over time. ETSI TS 119 511 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119511/01.01.01_60/ts_119511v010101p.pdf '
'Domibus supports the capability to configure and display user interfaces, messages, and notifications in different languages, thus, making it possible to use in a mulitlingual context. Domibus specification: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/Domibus '
'The specification improves the co-operation and interoperability of different organizational systems and domains, taking advantage of the capabilities of dids such as the guarantee of reliable data exchanges or compliance with privacy regulations. DIDs W3C: https://www.w3.org/TR/did-core/#design-goals'
The purpose of the specification is not related to business process modelling, therefore this criterion does not apply to this specification. W3C specification reference: https://www.w3.org/TR/odrl-vocab/#vocab-core
'No Member States are recommending ELI in their ICT National Catalogues. Despite this, the Ministry of Justice in Denmark, the Ministry of State in Luxembourg, the Office of the Attorney General in Ireland, Central Legislation Service, Ministry of State in Luxembourg, the National Printing Office and Mint/ Imprensa Nacional-Casa da Moeda in Portugal and the State Agency for the Official State Gazette in Spain are hardly recommending ELI and the common benefits of implementing it. ELI Testimonials reference: https://eur-lex.europa.eu/eli-register/testimonials.html CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards'
No Member States are recommending ELI in their ICT National Catalogues. Despite this, the Ministry of Justice in Denmark, the Ministry of State in Luxembourg, the Office of the Attorney General in Ireland, the National Printing Office and Mint/ Imprensa Nacional-Casa da Moeda in Portugal and the State Agency for the Official State Gazette in Spain are hardly recommending ELI and the common benefits of implementing it. ELI reference: https://eur-lex.europa.eu/eli-register/about.html CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'1 Member State is recommending CPOV in their ICT National Catalogue. It Member State is Spain. Moreover, OSLO extension is used by Belgium. OSLO extension: https://joinup.ec.europa.eu/collection/oslo-open-standards-local-administrations-flanders Belgium Catalogue: https://www.belgif.be/page/specifications.en.html Spain Catalogue: https://administracionelectronica.gob.es/ctt/verPestanaActivosSemanticos.htm?idIniciativa=3351 Joinup Catalogue: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards'
'IEEE Std 802.3-2022 itself does not provide the restriction of access to information or data, since it focuses primarily on the physical and data link layers of Ethernet networks. IEEE Std 802.3-2022 Reference: https://ieeexplore.ieee.org/document/9844436'
The purpose of the specification is not related to the comprehensibility of administrative rules, data, services, and the decision-making process. Therefore, this criterion does not apply to this specification. XACML OASIS reference: http://docs.oasis-open.org/xacml/3.0/errata01/xacml-3.0-core-spec-errata01.html
'Genericode can be used on any computing platform or operating system without requiring modifications. As an XML-based standard, it is independent of any specific hardware or software platform. It defines a structured format for representing code lists and controlled values using XML elements and attributes, which can be processed and interpreted by any system that supports XML parsing. Code List Representation (genericode): https://docs.oasis-open.org/codelist/genericode/v1.0/os/genericode-v1.0-os.html'
'AMQP defines a standard message format, including properties and sections for structuring data. This supports interoperability when exchanging information with public administration services. OASIS AMQP Reference: http://docs.oasis-open.org/amqp/core/v1.0/amqp-core-complete-v1.0.pdf'
'The purpose of LDAP is not related to the delivery of multilingual public services. Therefore, this criterion is not applicable to the specification. LDAP IETF reference: https://tools.ietf.org/html/rfc4511'
Even though SVG is supporting the first and second level of maturity from the Tim Berners-Lee 5-star schema for the Open data, it can be considered that could foster the publication of open data but not directly, as the SVG is compatible with XSL. SVG W3C reference: https://www.w3.org/TR/SVG11/ Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/en/
'The ESPD is designed to ensure the protection of personal data by complying with data protection regulations, providing transparent information to suppliers and their representatives, and requiring contracting authorities to implement appropriate measures to ensure the security and confidentiality of personal data. ESPD data protection: https://op.europa.eu/en/web/espd-seminar-2020/privacy-statement ESPD business handbook: https://docs.ted.europa.eu/ESPD-EDM/latest/xml_business_handbook.html'
'The specification follows an Open Consensus Building, participation in the DCMI community is open to all interested groups or individuals with expertise or interests in metadata. DCMI de facto standards, specifications and best practice documents reflect consensus arrived at through consultative debate and review. No fees are assessed for use of such information, inasmuch as the value of such materials is enhanced by their wide adoption DCMI About, Open Consensus Building: https://www.dublincore.org/about/ '
'The DCAT vocabulary defines the "Distribution" concept which can be used for publishing datasets in different languages. DCAT (v2.0.0) reference: https://www.w3.org/TR/vocab-dcat-2/ '
The purpose of TSP is not related to the publication of public data as linked open data. Therefore, this criterion is not applicable to this specification. TSP IETF reference: https://tools.ietf.org/html/rfc3161 Five star linked open data: https://www.w3.org/DesignIssues/LinkedData.html
The purpose of JSON is not related to e-accessibility. Therefore this criterion is not applicable to this specification.
The LegalDocML TC works to advance worldwide best practices for the use of XML within a Parliaments', Assembly's or Congress' document management processes, within courts' and tribunals' judgment management systems, and generally in legal documents including contracts. It can be concluded that the specification fosters defining organisational interoperability aspects LegalDocML reference: https://www.oasis-open.org/committees/legaldocml/charter.php
The specification is available for its use and implementation on Joinup platform with all its documentation. CLV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-location-vocabulary
'The ESPD is a single self-delcaration form enabling the participation in public procurement, thus providing means to preserve data in electronic format. ESPD Business handbook: https://docs.ted.europa.eu/ESPD-EDM/latest/xml_business_handbook.html'
'SCIM is an HTTP-based protocol that makes managing identities in multi-domain scenarios easier to support via a standardized service. Therefore, its use improves the interoperability and standardization of the exchange of user identity information between identity domains, or IT systems, which can contribute to some extent for the visibility of administrative procedures, rules data, and services. SCIM: https://scim.cloud/'
Coherence of the technical specification is evidenced by the fact that there is no existing European standard or technical specifications being under consideration to become a European standard that has a similar area of application.
'ShEx is not a European standard, and nor is yet a W3C standard (the SDO developing the specification). ICT technical specifications: https://ec.europa.eu/growth/single-market/european-standards/ict-standardisation/ict-technical-specifications_en EUOS repository of standards: https://www.standict.eu/standards-repository CENELEC and CEN search tool catalogue: https://standards.cencenelec.eu/dyn/www/f?p=CEN:105::RESET:::: CENELEC and CEN search tool catalogue: https://standards.cencenelec.eu/dyn/www/f?p=CEN:105::RESET:::: CENELEC and CEN website: https://www.cencenelec.eu/ '
"After conducting a thorough search, no documents or studies were found that assess XHTML in terms of its effectiveness. However, it is important to note that HTML5 now fulfills many of the same functions as XHTML, leading to a decline in XHTML's usage. There is a good amount of research, studies, and resources available about HTML5, demonstrating its value in supporting modern and more efficient web environments. XHTML W3C reference: https://www.w3.org/TR/xhtml1/ HTML5 W3C Reference: https://html.spec.whatwg.org/multipage/ HTML5 Research Reference: https://www.researchgate.net/publication/271329059_RESEARCH_ON_HTML5_DEVELOPMENT"
'Transformational Government Framework (TGF) does facilitate the publication of open data. The TGF emphasises the use of information and communication technologies (ICT) to improve government operations and service delivery, including the use of open data to improve transparency, accountability, and citizen engagement. The TGF recognizes that making data open and accessible to the public is a key part of transforming government operations and service delivery, and it encourages governments to adopt open data policies and practices. TGF Specification: http://docs.oasis-open.org/tgf/TGF/v2.0/cs01/TGF-v2.0-cs01.html Tim berners-lee 5 star open data: https://5stardata.info/en/'
XAdES as an electronic signature will proportionate a secure and trustworthy eSignature for the data exchange between citizens and administrations. XAdES ISO reference: https://www.iso.org/standard/56025.html XAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/101900_101999/101903/01.04.02_60/ts_101903v010402p.pdf
'Organisations can extend DCAT-AP by defining additional metadata elements that are specific to their use case or domain. Most of the European Union Member States has made a number of adjustments to meet its own specific needs, thus creating the so called ""the National Extensions of DCAT-AP"". DCAT-AP Specification: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/dcat-application-profile-data-portals-europe/release/200 DCAT-AP and its extensions: https://datos.gob.es/sites/default/files/doc/file/report_dcat-ap_and_its_extensions.pdf'
'Although the Advanced Encryption Standard focuses on confidentiality, encryption significantly hinders unauthorised modification of data without detection upon decryption. This means that while AES primarily ensures that data remains private, it also makes it much harder for anyone to alter the data without being noticed, adding an extra layer of security. Geeksforgeeks AES reference: https://www.geeksforgeeks.org/advanced-encryption-standard-aes/ AES Standard Reference: https://csrc.nist.gov/pubs/fips/197/final'
SVG is a business agnostic document format that can be reused in a cross-domain way. SVG W3C reference: https://www.w3.org/TR/SVG11/
The RDA website also collects expressions of interest from potential adopters via “Become an RDA Adopter” section and encourages adopters to submit “Adoption Stories” . RDA has organised a series of webinars focused on the adoption of the RDA Outputs & Recommendations encouraging dialogue and interaction and facilitating uptake.
XAdES Baseline Profile does not foster the creation of innovative solutions.
No conformity tool has been found belonging to OASIS in order to provide the means to evaluate UDDI implementation.
' REST is included in the ICT national catalogues of Slovakia and Finland. Finland national catalogue: https://joinup.ec.europa.eu/sites/default/files/inline-files/Finland%20Factsheet%20Validated.pdf Slovakia national catalogue: https://joinup.ec.europa.eu/sites/default/files/inline-files/Slovakia%20Factsheet_0.pdf'
'The OASIS Technical Committee, in charge of the development of ebXML, operates under RF (royalty-free) on RAND (reasonable and non-discriminatory) Mode of the OASIS IPR Policy. Therefore, the specification is licensed on a (F)RAND basis. ebXML reference, Notice section: http://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html OASIS Intellectual Property Rights Policy, section 10.2.2: https://www.oasis-open.org/policies-guidelines/ipr/'
'The purpose of ETSI TS 119 612 is not related to facilitate the modelling of business processes. Therefore this criterion is not applicable to the specification. ETSI TS 119 612: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf'
There are many free online tools that perform numerous checking processes in order to verify the conformity of the ETSI Advanced Electronic Signatures which include CAdES. CAdES conformance testing: https://signatures-conformance-checker.etsi.org/pub/index.shtml CAdES conformance testing 2: https://www.guru99.com/conformance-testing.html
After being evaluated compliant with the regulation on standardisation 1025/2012, CSV has been identified by Commission Implementing Decision. During the evaluation process, all the Member States are invited to share their doubts. The positive evaluation of CSV and its identification is considered an interoperability agreement. See: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en
'The specification OSI is primarily concerned with systems comprising terminals, computers, and associated devices and the means for transferring information between such systems, in this sense this reference model can provide a wide scope on how processes, data and services operate at different layers. OSI identifies 7 layers (Physical, Data Link, Network, Transport, Session, Presentation and Application) each layer deals with an aspect of the information transfer among systems, from the physical medium to the presentation and application end. OSI reference https://www.iso.org/standard/20269.html'
As a business domain agnostic specification, TLS 1.2, contributes with the security during the exchange of documents addressing any domain.
'The application of the once-only principle in all EU Member States public administrations aims at reducing the administrative burden. XACML addresses and facilitates interoperability between public administrations, cross-border services, and impacts positively the development of eGovernment. This is because it has been designed to evaluate and control access by ensuring the compliance of security policies. Also, the project SEMIRAMIS, uses this specification to ensure secure channels for the exchange and reuse of information. XACML OASIS reference: https://docs.oasis-open.org/xacml/3.0/xacml-3.0-core-spec-os-en.html SEMIRAMIS project: https://joinup.ec.europa.eu/solution/semiramis/about'
'The standardised terms and concepts within SAREF can facilitate clearer communication and understanding between systems, which is beneficial for secure data exchange protocols. When different entities use the same standardised terms and classifications, it can reduce ambiguity and errors during data transmission, contributing to more secure and accurate exchanges. SAREF: https://saref.etsi.org/core/v3.1.1/ '
IETF has a formal review and approval process so that all the relevant stakeholders can formally appeal or raise objections to the development and approval of specifications. Each distinct version of an Internet standards-related specification is published as part of the Request for Comments (RFC) document series. This archival series is the official publication channel for Internet standards documents and other publications. During the development of a specification, draft versions of the document are made available for informal review and comment by placing them in the IETF's Internet-Drafts directory, which is replicated on a number of Internet hosts. This makes an evolving working document readily available to a wide audience, facilitating the process of review and revision. See: https://www.ietf.org/standards/process/ https://tools.ietf.org/html/rfc2026
"The specification aims to accurately communicate user interface behaviors and structural information to assistive technologies within document-level markup. The Spanish Public Administration, under the initiative of the Observatory of Web Accessibility, is currently modernizing the mobile user interfaces across all its services. WAI-ARIA reference, Abstract section: https://www.w3.org/TR/wai-aria/ PAe reference, 'Proceedings of the Observatory of Web Accessibility' section: https://administracionelectronica.gob.es/pae_Home/en/pae_Estrategias/pae_Accesibilidad /pae_Observatorio_de_Accesibilidad.html?idioma=en "
WS-Security is available for free at the European Collaborative platform for the development of ICT solutions. See: https://joinup.ec.europa.eu/solution/web-services-security
PNG is used by 76.6% of all the websites as image extension. It is not only used over the Internet, PNG is commonly used to store images, so they can be visualized anytime. So it is demonstrated that PNG has enough market acceptance as image extension. Usage of image file formats broken down by ranking: https://w3techs.com/technologies/cross/image_format/ranking
'XSLT can be mapped to the EIRA Library of Interoperability Specifications (ELIS) in the "Data Mapping", "Data Mapping Catalogue", "Metadata Catalogue" and "Software Components Catalogue" under the Semantic View. EIRA Library of Interoperability Specifications (ELIS): https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and- specifications-camss/solution/elis/release/v610'
'As can be seen on the Oracle documentation about ebXML MCD implementation, the specification can implement additional functionalities such as Message Control Documents (MCD), which serve as an interface between a back-end system and WebLogic Integration Business Connect for processing business messages. In this context, this implementation is optional and can be carried out incrementally to achieve new functions. ebXML MCD implementation: https://docs.oracle.com/cd/E13215_01/wlibc/docs81/admin/xml_protocols.html#1032357 ebXML RegRep OASIS reference: https://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html'
'IPsec enables implementation of different profiles, which involve a set of specific requirements depending on the context of implementation: integration into the native IP stack, or "underneath" an existing implementation of an IP protocol stack. IPSec reference: https://www.rfc-editor.org/rfc/rfc6071.html'
'IPsec is already associated to EIRA ABBs in the EIRA Library of Interoperability Specifications (ELIS). More specifically, IPsec can define the interoperability aspects of the "Data Exchange" and "Virtual Private Network" ABBs of the EIRA Technical View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /solution/elis/release/v610'
The purpose of this Core Vocabulary is not related to long term preservation of electronic records. Therefore, this criterion is considered not applicable to this specification. CCCEV reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-criterion-and-core-evidence-vocabulary
'The purpose of EuroVoc is related to the delivery of multilingual public services. It contains terms in 24 EU languages, plus in three languages of countries which are candidate for EU accession. By establishing language equivalences between identical concepts expressed in different languages, it allows documents to be indexed in the language of the documentalist and searches to be made in the user’s language. EuroVoc: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource /dataset/eurovoc'
'As a reference architecture, the specification covers all LOST views, which means from legal requirements to how technically are there implemented. This can help to ensure that EIRA covers from administrative procedures and actors involved, the rules at legal, semantic, and technical level. Also, how to handle data and requirements related to data, data models and services themselves. EIRA reference: https://interoperable-europe.ec.europa.eu/collection/european-interoperability-reference-architecture-eira /solution/eira/release/610 EIRA Github Repository: https://github.com/CarTool-EC/EIRA '
"ISAE 3402 is part of the International Federation of Accountants (IFAC) standard providing companies in the financial sector with an independent assessment tool on user entities' controls over financial reporting. The ISAE 3402 auditing tools, therefore, are ony meant to be used as a whole. ISAE 3402 handbook reference: https://www.ifac.org/system/files/downloads/b014-2010-iaasb-handbook-isae-3402.pdf"
The purpose of FTPS is not related to e-accessibility. Therefore, this criterion is considered not applicable to this specification. FTPS IETF reference: https://tools.ietf.org/html/rfc4217
"There is no evidence of any assessment of the SFIA specification's efficiency. SFIA reference: https://sfia-online.org/en/sfia-8"
The purpose of SAMM is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification. SAMM webpage: https://owaspsamm.org SAMM documentation: https://github.com/OWASP/samm/blob/master/Supporting%20Resources/v2.0/OWASP-SAMM-v2.0.pdf
'The purpose of the specifications is not related to the availability of interfaces with internal information systems. Therefore, this criterion is not applicable to this specification. TSP IETF reference: https://tools.ietf.org/html/rfc3161'
'The Asset Administration Shell (AAS) queries and shares data across different systems via REST interfaces. REST APIs may be platform-agnostic, without any dependency on the environment or programming language being used, and in this case the Asset Administration Shell (AAS )primarily exists to expose data in a platform agnostic manner so that .NET, Java, Php, Python, REST, etc clients can all access the data. So, the specification is platform-agnostic. Details of the Asset Administration Shell (AAS) https://industrialdigitaltwin.org/en/wp-content/uploads/sites/2/2024/06/IDTA-01001-3-0-1_SpecificationAssetAdministrationShell_Part1_Metamodel.pdf'
'The purpose of the specification is to facilitate the exchange of structured event data. By allowing to make the data available to other persons or organisations, this specification reduces the administrative burden and enables digital service delivery channels. LDES specification: https://joinup.ec.europa.eu/collection/semic-support-centre/linked-data-event-streams-ldes'
JSON is available for free at the European Collaborative Platform Joinup. See: https://joinup.ec.europa.eu/solution/json-rfc7159-javascript-object-notation-json/distribution/json-rfc7159-javascript-object-notation-json
"The IPsec specification is a key protocol for data security and privacy. This protocol has been integrated into the latest version of the Internet protocol (IPv6), and it can also be integrated with IPv4 as an extension. In addition, it is used to configure VPNs and to encrypt IP packets. IPSec reference: https://www.rfc-editor.org/rfc/rfc6071.html IPsec VPN's: https://www.cloudflare.com/es-es/learning/network-layer/what-is-ipsec/ IPsec IPv6: https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ipv6/configuration/xe-3s/ipv6-xe-3s-book/ip6-ipsec.pdf Ipsec IPv4: https://www.twingate.com/blog/ipsec"
'The Asset Administration Shell (AAS) has some provisions for data protection at technical level but no mentions to the regulations applied is to be found. In particular, the specification refers to the IEC 63278 as basis for the data protection protocols in place. Data protection on the AAS: https://admin-shell-io.github.io/aas-specs-antora/IDTA-01004/v3.0/introduction.html#_iec_63278 Details of the Asset Administration Shell (AAS) https://industrialdigitaltwin.org/en/wp-content/uploads/sites/2/2024/06/IDTA-01001-3-0-1_SpecificationAssetAdministrationShell_Part1_Metamodel.pdf'
The specification ODF 1.2 from ISO is not available for free as all the ISO standards have to be paid. However, it can be checked out the OASIS documentation referring to the ODF, as the content is aligned. ODF ISO reference: https://www.iso.org/standard/66363.html ODF OASIS reference: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office
'The Semantic Interoperability Community (SEMIC) develops solutions to help European public administrations perform cross-border and cross-domain data exchanges. They develop semantic specifications and interoperability solutions under the ISA² Programme. When a new solution release is finished, it is submitted for a public review with a minimum period of four weeks. Specification development process by the ISA Programme: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/document/description-change-management-release-and-publication-process-structural-metadata-specifications Detailed document ISA Programme: https://joinup.ec.europa.eu/sites/default/files/document/2016-10/description_of_a_change_management_release_and_publication_process_for_structural_metadata_specifications_developed_by_the_isa_progr.pdf'
'DPV has been found to contribute to the development of the SPECIAL project (Scalable Policy-aware Linked Data Architecture For Privacy, Transparency and Compliance), a European-funded project that aims to advance the state of the art by delivering technology to reconcile the contradiction between Big Data innovation and data protection compliance requirements. DPV specification: https://w3c.github.io/dpv/primer/ SPECIAL project: https://specialprivacy.ercim.eu/'
'The NIST organisation offers a guide on how to contribute to the development of new solutions. Tools and use cases can be contributed via GitHub pull requests, while feedback can be provided via GitHub issues. Contributed tools and use cases can be hosted directly in the NIST repository, or they can be hosted elsewhere online and linked to from the NIST repository. NIST collaboration space: https://www.nist.gov/itl/applied-cybersecurity/privacy-engineering/collaboration-space AES Standard Reference: https://csrc.nist.gov/pubs/fips/197/final'
'The purpose of OAS is to help to the development and documentation of APIs, with any kind of restrictions related to the domain it is to be applied; therefore, OAS is domain-agnostic and can be implemented in any domain. OAS specification: https://spec.openapis.org/oas/latest.html#openapi-specification OAS in Github: https://github.com/OAI/OpenAPI-Specification/#participation'
By establishing a common method to model rules for accessing and consuming digital content, it can help administrations to describe intellectual property rights for their information fostering the digital readiness of the materials and services provided. In this sense, the specification can help to reuse and exchange valuable information and services increasing the digitalisation of administrations reducing the related administrative burden. Moreover, it is a powerful tool for the development of legislation and its compliance with privacy aspects, as it demonstrates the SERAMIS project. SERAMIS: https://cordis.europa.eu/docs/projects/cnect/2/612052/080/deliverables/001-D55v4GDPR.pdf W3C specification reference: https://www.w3.org/TR/odrl-vocab/#vocab-core
'The purpose of SAML 2.0 is not related to e-accessibility. Therefore, this criterion is not applicable to the specification. SAML 2.0 Reference: http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-tech-overview-2.0.html'
'One of REST's architectural properties is the modifiability of components to meet changing needs. The REST constraint "code on demand" applies when returning executable code is needed in order to support a part of the application. Therefore the server can extend or customize the functionality of a client by transferring executable code: for example, compiled components such as Java applets, or client-side scripts such as JavaScript. REST "code on demand" reference: https://restfulapi.net/rest-architectural-constraints/#code-on-demand REST R. Fielding dissertation: Chapter 5 https://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm'
'The purpose of IPsec is not related to e-accessibility. Therefore this criterion is considered not applicable to the specification. IPSec reference: https://www.rfc-editor.org/rfc/rfc6071.html'
'The purpose of CPOV is not related to the restriction of access to information/data. Therefore, this criterion is considered not applicable to this specification. CPOV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-organisation-vocabulary'
"TGF provides guidance for the identity and privacy management on a digital government. Among some of the recommendations that TGF gives in this regard, there can be found the proposal for a federated identity trust framework, the depoloying of technical architecture with designed-in security and privacy features, supporting identity management lifecycle processes and the self-control of people's data. TGF specification: http://docs.oasis-open.org/tgf/TGF/v2.0/cs01/TGF-v2.0-cs01.html"
'DPV provides a data model of concepts that act as a vocabulary for the interoperable representation and exchange of information about personal data and its processing. It can help to facilitate interoperability agreements when it comes to applying privacy-friendly policies, as it represents concepts associated with privacy and data protection, primarily derived from GDPR. DPV specification: https://w3c.github.io/dpv/dpv/ DPV primer document: https://w3c.github.io/dpv/primer/#introduction'
'There is documentation stating that CCCEV is a good asset for efficient and effective data exchange across-border. The information found remarks on the importance of the CCCEV in the implementation of the Once-Only Principle. Joinup news page "CCCEV - a key enabler of the Once-Only Principle": https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/news/cccev-and-once-only-principle'
The purpose of the specification is not related to e-accessibility. Therefore, this criterion is not applicable to this specification.
W3C provides a test suit for WSDL 2.0 implementations. Moreover, the specification document contains a reference to verify the conformity of a WSDL document. It can be found in section 1.3 of the specification. See: https://dev.w3.org/2002/ws/desc/test-suite/index.html https://www.w3.org/TR/wsdl/#markup
There is no Member State that includes Xforms 2.0 in their national catalogue with The National Interoperability Framework (NIF) aligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'At the moment of performing the assessment, no initiative at national or European level has been found to use UTF-8 to cover privacy aspects. UTF-8 specification: https://datatracker.ietf.org/doc/html/rfc3629'
'The UDDI public registers allow to have a public register of web services in a human-redeable manner and it also guarantees a framework to describe, discover and integrate web services. Therefore, UDDI can contribute to comprehensibility of data because it allows access to different web services in an open way, although it is not its main purpose. UDDI OASIS reference: https://www.oasis-open.org/committees/uddi-spec/doc/spec/v3/uddi-v3.0.2-20041019.htm#_Toc85907967 UDDI techtarget reference: https://www.techtarget.com/whatis/definition/UDDI-Universal-Description-Discovery-and-Integration'
SVG is developed by the W3C community, an international organisation aimed to develop open standards and specifications. SVG W3C reference: https://www.w3.org/TR/SVG11/
The once-only principle is an e-government concept that aims to ensure that citizens, institutions, and companies only have to provide certain standard information to the authorities and administrations once. IPSec is a set of open standards and protocols for securing the exchange of data packets over a computer network. By allowing the secure exchange of standard data, IPSec reduced the need to provide the information several times Therefore, IPSec eases the implementation of the once-only principle.
The purpose of XACML is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification. XACML OASIS reference: http://docs.oasis-open.org/xacml/3.0/errata01/xacml-3.0-core-spec-errata01.html
'TLS 1.3 specification offers robust tools for establishing the authenticity and performing the authentication of the agents involved in data transactions, with server authentication being a fundamental requirement and client authentication being a configurable option. TLS 1.3 Handshake Protocol Reference: https://www.rfc-editor.org/rfc/rfc8446.html#section-4'
'The specification can be found, for instance, in one site at national level in Poland. It is present at different levels, the site includes information related to the new releases, access to them, new courses, etc. In general terms, EIRA is present at national level in Poland. Portal Gov: https://www.gov.pl/web/ia/czym-jest-eira-nowy-kurs-online-w-akademii-interoperacyjnosci EIRA reference: https://interoperable-europe.ec.europa.eu/collection/european-interoperability-reference-architecture-eira /solution/eira/release/610 EIRA Github Repository: https://github.com/CarTool-EC/EIRA '
'While the OpenAPI Specification tries to accommodate most use cases, additional data can be added to extend the specification at certain points. The extensions may or may not be supported by the available tooling, but if tools are internal or open-sourced, those may be extended as well to add requested support. OAS Extensions: https://spec.openapis.org/oas/latest.html#specification-extensions OAS specification: https://spec.openapis.org/oas/latest.html#openapi-specification OAS in Github: https://github.com/OAI/OpenAPI-Specification/#participation'
'Understanding data exchange as the publication by the administration of data for its later consumption by citizens, the specification facilitates the trustworthy data exhange in RDF format by providing the means to validate RDF data graphs. ShEx primer document: https://shexspec.github.io/primer/ ShEx Community Group: https://www.w3.org/community/shex/ ShEx Github: https://github.com/shexSpec/spec/issues'
'The specification allows extension. It provides a framework that enables the addition of new functionality beyond the core features defined in the standard. SOAP 1.2 introduces the concept of SOAP features and SOAP modules, which are mechanisms for extending the SOAP framework. SOAP features define optional capabilities that a SOAP node may support, such as message transmission optimization, reliable messaging, or security features. These features can be defined and implemented by extending the SOAP specification. SOAP Reference: https://www.w3.org/TR/soap12/ '
RDA Research Data Repository Interoperability Recommendations is a common format for research data. It is an area of application which is not covered by any other technical specification being under consideration to become a European standard. This conclusion has been drawn from the examination of all the programming mandates addressed to CEN, CENELEC and ETSI to the date, CEN’s webpage , CENELEC’s webpage , CEN-CENELEC’s webpage ICT section , the EC Information Providers Guide, Directive (EU) 2016/2102 of the European Parliament and of the Council of 26 October 2016 on the accessibility of the websites and mobile applications of public sector bodies , the standards and tools for exchange and processing of actionable information inventory of ENISA and the ENISA Programming Document 2018-2020
'The effectiveness of ETSI TS 119 432 is often evaluated through various means, including practical implementations and pilot projects. For instance, a 2020-paper about learned lessons from implementing an android client for the Cloud Signature Consortium API highlights the ETSI protocol as the one to be respected for communication between SCA/SIC and SSA/SAM. Learned Lessons from Implementing an Android Client for the Cloud Signature Consortium API: https://link.springer.com/chapter/10.1007/978-3-030-41025-4_15'
SHACL is implemented for data validation purposes by DCAT-AP, which is a specification that describes public sector datasets with the aim to enable cross-data portal search for datasets, and make public sector data easily searchable across borders and sectors. DCAT-AP is used in the Open Data Support service initiated by the European Commission.
'This specification is supported by ISO. In order to participate in creating standards, the user must be part of their national standards body (assuming their country is part of ISO). On the other hands, other groups that also support cloud computing standardisation include the Object Management Group (OMG). OMG: https://www.omg.org/cloud/deliverables/interoperability-and-portability-for-cloud-computing-a-guide.htm ISO Technical committees: https://www.iso.org/get-involved.html'
There is no national or European platform with the specification PDF/A available for free.
CAdES and CAdES Baseline profile are maintained by ETSI, one of the European Agencies for Standardisation. See: https://www.etsi.org/about
'Although the specification cannot be found in any repository of standards at the European level, ebXML is mentioned in the "Commission Implementing Decision (EU) 2022/2519 of 20 December 2022 on the technical specifications and standards for the e-CODEX system, including for security and methods for integrity and authenticity verification" as a specification to improve the security and privacy of data. "Commission implementing decision (EU) 2022/2519 of 20 December 2022 on the technical specifications and standards for the e-CODEX system, including for security and methods for integrity and authenticity verification" document: https://eur-lex.europa.eu/legal-content/ES/TXT/?uri=CELEX%3A32014D0771&qid=1743495780482 ebXML RegRep OASIS reference: https://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html'
'The IPsec protocol, which is included in the IPv6 protocol, can help securely transfer data to ensure data accuracy. IPv6 specification can help accurately exchange information between public administrations or between public administrations and citizens. IPv6 supports authentication methods, verifying that the data received by the receiver from the sender is exactly what the sender sent and only came through the sender and not from a third party. In addition, IPv6 can encrypt the message at network layer even if the protocols of application layer at user level does not encrypt the message. These implementations can be useful to guarantee data processing accuracy. Redhat IPsec protocol: https://www.redhat.com/en/blog/ipv6-packets-and-ipsec IPv6 encryption and authentication: https://www.geeksforgeeks.org/internet-protocol-version-6-ipv6/'
All of the RDA specifications are openly available and free of charge.
'LDAP was created in 1993 and quickly became one of the foundational authentication protocols used by IT network. The fact that in 1998, OpenLDAP 1.0 was implemented as an open source version of LDAP made it very popular. Therefore, it is demonstrated that LDAP has enough maturity for its use in the development of digital solutions and services. LDAP IETF reference: https://tools.ietf.org/html/rfc4511 OpenLDAP: https://www.openldap.org/'
'There is one Member States that currently has AMQP in their catalogues of recommended specifications. These Member State is France. France catalogue reference: https://www.numerique.gouv.fr/uploads/Referentiel_General_Interoperabilite_V2.pdf CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards'
'There is no Member State recommending TOSCA in its ICT National Catalogue. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
'The purpose of Core Location Vocabulary is not related to provide an access control mechanism. Therefore this criterion is considered not applicable to the specification. Core Location Vocabulary: https://interoperable-europe.ec.europa.eu/collection/semic-support-centre/solution/core-location-vocabulary/release/100'
'The purpose of IPv6 is not related to the modelling of business processes. IPv6 is primarily a network protocol designed to facilitate communication over the internet, and it does not inherently focus on modelling business processes. IPv6 IETF: https://www.rfc-editor.org/rfc/rfc2460'
SVG does not define a cross-sector reusable data model. It defines a common XML schem using XML based tools. By being written in XML, SVG builds on this strong foundation and gains many advantages such as a sound basis for internationalization, powerful structuring capability, an object model, and so on.
'When it comes to the preservation mechanisms, ETSI TS 119 512 specifies a data structure "EvidenceExchange", which contains preservation objects and preservation evidences to support seamless export and import from one preservation service to another one using evidence records, As an example, ETSI TS 119 512 is implemented in Germany and its TR-ESOR middleware, therefore proving it can support the evolution of European public services. ETSI TS 119 512 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.02_60/ts_119512v010102p.pdf TR-ESOR Preservation of Evidence of Cryptographically Signed Document: https://www.bsi.bund.de/EN/Service-Navi/Publications/TechnicalGuidelines/TR03125/TechnicalGuidelines_03125_node.html'
"As ECLI implements DCMI, where ECLI is a uniform identifier that has the same recognizable format for all Member States and EU courts, it can be significant of the specification's effectiveness, if used together with other specifications. ECLI Webpage: https://e-justice.europa.eu/175/EN/european_case_law_identifier_ecli?init=true"
'There is no such assessments addressing the effectiveness of the specification. This might be due to the early-stage development of the specification. Besides, the ARIA initiative proposes tools and methods to evaluate e-accessibility. In this sense, in the future there might exist such reports. WAI-ARIA github, issue tracking: https://github.com/w3c/aria-practices/issues/ WAI-ARIA reference: https://www.w3.org/TR/wai-aria/'
By allowing the exchange of datasets metadata, DCAT-AP increases the searchability, visibility, discoverability and reuse of existing data, including information on processes and administrative rules.
'Overall translation is done to the tags in the optional message content such as "Entity Name" or "Postal Adress", although information in free text shall be written in UK English. ETSI EN 319 532-3 reference: https://www.etsi.org/deliver/etsi_en/319500_319599/31953203/01.02.01_60/en_31953203v010201p.pdf'
'The ESPD supports data portability between systems and applications that are used to implement public services by providing a standard format for collecting and sharing procurement-related information. The use of a standard format for procurement-related information enables the exchange of data between different systems and applications, which can help to improve the efficiency and effectiveness of public procurement processes. ESPD Business handbook https://docs.ted.europa.eu/ESPD-EDM/latest/xml_business_handbook.html'
'The purpose of TLS is not related to the publication of public data as open data. The main purpose TLS is to provide a secure channel between two communicating peers. Therefore this criterion is not applicable to this specification. TLS Reference: https://www.rfc-editor.org/rfc/rfc8446.html'
'The purpose of UDDI is not related to organisational interoperability. Therefore, this criterion is not applicable to the specification. UDDI OASIS reference: https://www.oasis-open.org/standard/uddi/'
"The first version of the EN 303 645 specification was published in 2019 and up to date has reached version 2.1.1. The specification's predecessor was TS 103 645, prior to its designation as a European Standard (EN) (see EN 303 645 homepage reference, OUR ROLE & ACTIVITIES section). All the specification releases can be found in the TC CYBER website or at the EN 303 645 homepage. EN 303 645 homepage reference: https://www.etsi.org/technologies/consumer-iot-security"
'YAML’s structured format allows to exchange data between different systems and services, facilitating interoperability and integration. Moreover, public services can use YAML to define workflows and automation scripts, improving efficiency and reducing manual intervention. This is particularly useful in public services where multiple agencies and systems need to work together. YAML specification: https://yaml.org/spec/1.2.2/'
'The purpose of SAREF is not related to providing an access control mechanism. Therefore, this criterion is not applicable to this specification. SAREF: https://saref.etsi.org/core/v3.1.1/ '
"Schema.org can be deployed in any platform since the specification can be coded into RDF and JSON-LD, which are compatible with the vast majority of information systems. Therefore, the specification is platform-agnostic. Schema.org reference, Getting started section: https://schema.org/docs/gs.html Schema.org-W3 Github reference, 'Improving schemas' section: https://github.com/schemaorg/schemaorg/blob/main/README.md"
'At the time of elaborating this assessment, this specification is included in the "Machine Learning" ABB under the Technical Insfraesctructure View and "Artificial Intelligence" ABB under the Technical Application View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /solution/elis/release/600'
'YAML is designed to be extensible. One of the extensions available is the Core schema which is an extension of the JSON schema, allowing for more human-readable presentation of the same types. Core Schema YAML: https://yaml.org/spec/1.2.2/#103-core-schema'
The Dutch National Cyber Security Centre prescribes the use of TLS 1.3 in the latest version of their Security Guidelines (advice on purchasing, drafting and reviewing configurations): https://www.ncsc.nl/documenten/publicaties/2019/mei/01/ict-beveiligingsrichtlijnen-voor-transport-layer-security-tls
DCAT-AP is recommended by Italy, The Netherlands, Sweden, Belgium, and Spain. These Member States extended DCAT-AP to meet the specific national needs. See: https://datos.gob.es/sites/default/files/doc/file/report_dcat- https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'DIDs allows to control digital identities, as well as authenticate identities without dependence on centralized authorities. Therefore, DIDs simplifies administrative processes allowing people to manage their digital identities, and also supporting the principle of digital-first. DIDs W3C: https://www.w3.org/TR/did-core/'
'The OpenTelemetry specification allows extensive customisation to meet the specific needs and requirements of different applications and environments. OpenTelemetry provides SDKs for multiple programming languages where each SDK is designed to be modular, allowing developers to include only the components they need. On the other hand, developers can define custom spans and add custom attributes to spans to capture specific details about their application’s behavior. OpenTelemetry - Create custom traces and metrics: https://opentelemetry.io/docs/zero-code/net/custom/ OpenTelemetry - Building custom components: https://opentelemetry.io/docs/collector/building/'
'ELI fosters a community of nations working together to standardize legal information, and it encourages the sharing of this data on national and European platforms. This makes it easier to exchange and reuse legal information across borders EU Open Data Portal Data sets: https://data.europa.eu/euodp/en/data/group/eli?groups=eli ELI reference: https://eur-lex.europa.eu/eli-register/about.html 5-star linked open data: https://www.w3.org/DesignIssues/LinkedData.html'
'Even though there have been several implementation at different levels of EIRA and its specialisations, there are no studies so far evaluating the effectiveness or efficiency of the specification. EIRA reference: https://interoperable-europe.ec.europa.eu/collection/european-interoperability-reference-architecture-eira /solution/eira/release/610 EIRA Github Repository: https://github.com/CarTool-EC/EIRA'
'The Data on the Web Best Practices Community Group continues the work started by the Data on the Web Best Practices Working Group in investigating topics such as data versioning, subsetting, data access and metadata. It will promote discussions about Data on the Web challenges and best practices, evaluating its benefits and any drawbacks. In doing so, the CG will collect new evidence of the DWBP implementation globally and will offer additional material to promote the adoption of DWBP, while needs for further standardisation will be identified. Needs for further standardisation will be identified. Data on the Web Best Practices Working Group: https://www.w3.org/community/dwbp/'
'The implementation of XHTML relies on the specific business requirement which is not necessarily aligned with the reuse of information. The reuse of information might be limited to the definition of variables and this is much more strict in XHTML in comparison to a more flexible languages, such as HTML5. XHTML W3C reference: https://www.w3.org/TR/xhtml1/'
'While the OAIS reference model does not in itself facilitate the reuse of relevant information, it provides a framework for the management and preservation of digital objects over time, which can enable the reuse of information by ensuring that it remains accessible and usable over the long term. The metadata and descriptive information associated with digital objects can also be used to facilitate their discovery and reuse. OAIS specification: https://public.ccsds.org/Pubs/650x0m2.pdf'
'WAI-ARIA is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, WAI-ARIA can define the interoperability aspects of the "Human Interface" ABB and the "Public Administration Single Window" of the EIRA Technical View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis'
'ISO 3166-1 provides a collection of codes for the names of countries, dependent territories and special areas of geographical interest, regardless of any specific domain. Therefore, the specification can be used in any domain. ISO 3166-1 reference: https://www.iso.org/standard/72482.html '
'There has not been found any article or study assessing the efficiency of the ISO/IEC 19944-1. ISO/IEC 19944-1 specification: https://www.iso.org/standard/60545.html'
IETF has a formal review and approval so that all the relevant stakeholders can formally appeal or raise objections to the development and approval of specifications. Each distinct version of an Internet standards-related specification is published as part of the "Request for Comments" (RFC) document series. This archival series is the official publication channel for Internet standards documents and other publications. During the development of a specification, draft versions of the document are made available for informal review and comment by placing them in the IETF's "Internet-Drafts" directory, which is replicated on a number of Internet hosts. This makes an evolving working document readily available to a wide audience, facilitating the process of review and revision. IETF Reference: https://www.ietf.org/standards/process/ https://tools.ietf.org/html/rfc3161
'Such means as providing an access control mechanism can be provided as SOAP extensions using the SOAP extensibility mode. The SOAP Messaging Framework does not directly provide any mechanism for dealing with it directly. SOAP Reference, section 7 Security Considerations: https://www.w3.org/TR/soap12/#secconsiderations'
'The purpose of IPsec is not related to the exchange of data and therefore, it can not ease the implementation of the once-only principle. Therefore this criterion is considered not applicable to this specification. IPSec reference, What IPSec Does: https://datatracker.ietf.org/doc/html/rfc4301#page-7'
'The SMP 2.0 specification developed by OASIS does not directly address the authenticity and authentication of roles or agents involved in data transactions but can contributes to enabling authenticity features as described in section 5.6.2. SMP OASIS reference: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505009 SMP OASIS reference, section 5.6.2 about contribution to enabling authenticity features: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505052'
The Xforms 2.0 includes data structures and models that can be considered as reusable models for establishing data policies, the data involved and the processes involved. Xforms 2.0 W3C reference: https://www.w3.org/community/xformsusers/wiki/XForms_2.0
The purpose of XAdES is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification.
'The ELI TF is the body in charge of the maintenance and development of the specification. In the ELI Governance document, it is defined how and by who the specification is evolved. Member States are open to participate in the evolution of the specification only with soft requirements like having implemented the specification at a national level and having the knowledge to contribute to the evolution of ELI. ELI reference: https://eur-lex.europa.eu/eli-register/about.html Governance Rules: https://eur-lex.europa.eu/content/eli-register/governance_rules.pdf'
In the context of eSignatures and Seals, the European Commission has stated an Implementing decision where urged the Member States and other Public services providers to recognise CAdES, PAdES, XAdES, and ASIC as formats for electronic signatures purposes. See: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32015D1506
"YAML is included in 1 Member States' catalogues of recommended specifications. It Member State is France. CAMSS list of standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards"
'GraphQL processes all data requests but only extensions (GraphQL-JS) or third APIs could be asked to resolve a response over an access control mechanism. GraphQL specification: https://graphql.org/learn/schema/'
'At the moment of performing the assessment, UTF-8 is widely adopted in environments developing and implementing ICT solutions including innovative solutions. UTF-8 specification: https://tools.ietf.org/html/rfc3629 '
Even though the specification is related to the use and publication of metadata, it is not directly related to the publication of open data. The relation with metadata and its publication is focused on the availability and discoverability of access points and different parties for the exchange of data. SMP OASIS reference: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505009 Five star linked open data: https://www.w3.org/DesignIssues/LinkedData.html
"DQV enables the representation of information about the quality of a set using the “Multilingual importing” quality metric. This metric applies to linksets between datasets that include SKOS concepts. It considers the concepts that have been matched and quantifies the information gain the links provide if one adds the preferred labels or the alternative labels of the concepts from the object dataset to the descriptions of the concepts from the subject dataset. Therfore, DQV supports multilingual metadata, using RDF's language tags to provide labels and descriptions in various languages. Data Quality Vocabulary: https://www.w3.org/TR/vocab-dqv/#ExpressQualLinkset"
As an encoding specification it is being highly used by public administrations in order to encode data and services. An example of its use is ESCO, the vocabulary generated regarding the standardisation of the skills, competences, qualifications, and occupations at European level. See: https://ec.europa.eu/esco/api/doc/esco_api_doc.html
OWL2 is based on elements of RDF and it adds more vocabulary for describing properties and classes. RDF is one of the proposed standards for the publication of data as Linked Open Data. OWL2 and RDF are highly aligned with the principles for Linked Data promoted by W3C and Tim Berners-Lee. OWL2 W3C reference: https://www.w3.org/TR/owl2-overview/ 5-star linked open data: https://www.w3.org/DesignIssues/LinkedData.html
'The purpose of GraphQL is not related to e-accessibility. Therefore, this criterion is not applicable to this specification. GraphQL specification: https://spec.graphql.org/October2021/#sec-Overview'
'Better Regulation Guidelines and Toolbox has the support of the European Commission which is endorsed by the member states. The tool set is updated and distributed by the Commission for its use on the EU institutions and other stakeholders. On the Report produced by the European Parliamentary Research Service multiple institutions in the UE have provided valuable feedback regarding the Better Regulation Framework, institutions such as the European Committee of the Regions called for a better representation of local and regional perspectives throughout the policy cycle. Better Regulation Guidelines and Toolbox reference: https://commission.europa.eu/law/law-making-process/better-regulation/better-regulation-guidelines-and-toolbox_en European Parliamentary Research Service briefing https://www.europarl.europa.eu/RegData/etudes/BRIE/2022/699463/EPRS_BRI(2022)699463_EN.pdf European Comission webpage: https://commission.europa.eu/law/law-making-process/better-regulation_en'
HTTPS is an internet protocol for the data exchange over an Internet network. It supports the first level of maturity defined in the Tim Berners-Lee´s 5 stars Open Data deployment scheme, "Make your data accessible on the web". See: https://5stardata.info/en/
"According to the 5 star Open Data model suggested by Tim Berners-Lee about how to publish linked data, the forth star corresponds to represent data with URIs. OData follows REST principles, and as a consequence this specification supports the publication of data as open data. Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/en/ Odata reference, section 2 Overview: http://docs.oasis-open.org/odata/odata/v4.0/errata03/os/complete/part1-protocol/odata-v4.0-errata03-os-part1-protocol-complete.html#_Toc453752201 REST reference, 'What is a resource?' section: https://restfulapi.net/"
There are existing documentation and studies assessing the effectiveness and efficiency of IPv4. It is a constant in studies the comparison between both versions, IPv4 and IPv6. As well, the studies show the relevance of coexisting before finding the most efficient method to move on from one protocol to another. See: https://www.researchgate.net/publication/317135434_A_STUDY_ON_IPv4_and_IPv6_THE_IMPORTANCE_OF_THEIR_CO-EXISTENCE https://pdfs.semanticscholar.org/3455/fdc0741edc3263295ae8d0c226119613db81.pdf https://www.researchgate.net/publication/224593091_A_comparative_review_of_IPv4_and_IPv6_for_research_test_bed
'The purpose of NUTS is not related to the visibility of administrative procedures, rules data and services. Therefore, this criterion is not applicable to this specification. EUROSTAT reference, History of NUTS section: https://ec.europa.eu/eurostat/web/nuts/history'
The purpose of SOAP 1.2 is not related to the delivery of multilingual public services. Therefore, this criterion is not applicable to the specification.
'The SHACL specification allows to introduce modelling techniques and also conduct processes in alignment with delivery standards. SHACL W3C reference: https://www.w3.org/TR/shacl/'
ODRL has been selected for a European H2020 project called SPECIAL which aims to use ODRL to validate GDPR compliance of Legislation being produced. Its use has also been implemented within SERAMIS a project which extended ODRL for the validation of GDPR aspects. SERAMIS: https://cordis.europa.eu/docs/projects/cnect/2/612052/080/deliverables/001-D55v4GDPR.pdf SPECIAL Deliverable: https://www.specialprivacy.eu/images/documents/SPECIAL_D17_M17_V10.pdf Representing Activities associated with Processing of Personal Data and Consent using Semantic Web for GDPR Compliance: https://harshp.com/research/publications/035-representing-activities-processing-personal-data-consent-semweb-gdpr-compliance#ref-agarwal_legislative_2018
The purpose of TIFF/IT is not related to the delivery of multilingual public services. Therefore, this criterion is not applicable to this specification. TIFF/IT ISO reference: https://www.iso.org/standard/34342.html
The purpose of DCAT is not related to the medullisation of business processes. Therefore this criterion is not applicable to this specification.
'ISO/IEC 27001 is included in a national catalogue of recommended specifications, the Norway ICT Catalogue. The National Interoperability Framework (NIF) of this Member State is fully aligned with the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets, with a performance above the EU average. Norway catalogue of standards: https://www.difi.no/fagomrader-og-tjenester/digitalisering-og-samordning/standarder NIFO factsheets: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public-administration-factsheets-2021'
OASIS has defined a clear Technical Committee (hereby TC) process where all the stakeholders involved has the opportunity to participate in the development of the specification being formulated. All the information related to a TC activity is hosted and can be consulted. See: https://www.oasis-open.org/policies-guidelines/tc-process-2017-05-26
'E-ARK CSIP can indirectly support the modeling of business processes by providing a framework for managing and preserving the digital information associated with those processes. By utilizing the CSIP guidelines alongside business process modeling approaches, organizations can ensure that the digital information packages are aligned with the modeled business processes, enabling a more comprehensive representation of the end-to-end process. E-ARK CSIP specification: https://earkcsip.dilcis.eu/#introduction'
'There has not been found any community sharing their data and results on national platforms. However, ETSI TS 119 512 indirectly encourages the creation of communities on national platforms through ETSI membership and directives. ETSI TS 119 512 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.02_60/ts_119512v010102p.pdf'
'The specification is domain agnostic, it is made to describe software independently from the domain of the solution. The Publiccode.yaml provide a basic but useful metadata schema that makes easy to describe solutions. Publiccode.yaml documentation: https://docs.italia.it/italia/developers-italia/publiccodeyml-en/en/master/index.html'
'While XHTML was once the recommended standard for web development, it has been largely replaced by HTML5, which offers significant improvements in flexibility, functionality, and user experience. In fact, HTML5 is now the dominant web standard for creating digital services. XHTML W3C reference https://www.w3.org/TR/xhtml1/'
'The iCalendar specification has many known implementations, and currently being used by some of the top leading technologic companies such as Apple or Google. From this fact it is evident that the iCalendar has widespread market acceptance, as well as it is being used for the creation of innovative solutions. iCalendar implementations: https://microformats.org/wiki/icalendar-implementations iCalendar specification: https://www.rfc-editor.org/rfc/rfc5545'
'The simplification of the delivery of public services is not on how they are deliver, it starts with the analysis and design phase of these services. There is where EIRA is meant to focus and support the simplification of European public services. The holistic approach of the specification ensures that there is a translation between legal requirements into the technical implementations. By providing different perspectives to different aspects such identification and access management, EIRA can help public administrations to develop services considering simplification by design. EIRA reference: https://interoperable-europe.ec.europa.eu/collection/european-interoperability-reference-architecture-eira /solution/eira/release/610 EIRA Github Repository: https://github.com/CarTool-EC/EIRA'
The purpose of TLS 1.2 is not related to fostering visibility and comprehensibility of administrative rules, processes, data, services and decision-making of a public administration. . Therefore this criterion is considered not applicable specification.
'The syslog protocol provides a standardized framework for logging messages, and to a considerable extent, it supports the reuse of relevant information when needed. Some aspects of the syslog protocol that facilitate information include structured data, standardised message format, integration with logging systems, etc. Syslog Protocol: https://datatracker.ietf.org/doc/html/rfc5424'
IPSec is maintained and developed by IETF which is an international community developing open standards See: https://www.ietf.org/about/ https://tools.ietf.org/html/rfc4301
IETF is a vendor neutral standard developing organisation and HTTP is independent from any technology or platform. See: https://tools.ietf.org/html/rfc2616
'Each test performed by the specification has a tag EUMS (European Union Member State) that varies depending on the Member State or not Member State using the specification, so although not explicitly recommended, there are Member States that use it. This is supporting eIDAS implementations especifically for validating the requirements from ETSI TS 119 614-1 V1.1.1 ETSI TS 119 614-1 reference: https://www.etsi.org/deliver/etsi_ts/119600_119699/11961401/01.01.01_60/ts_11961401v010101p.pdf'
'AMQP specification is included in the StandICT European catalogue of standards. StandICT Catalog Reference: https://standict.eu/standards-repository/standard/advanced-message-queueing-protocol-amqp-v10'
The main purpose of OWL2 is to allow accessing, importing, sharing, and reusing public ontologies. The data described by an ontology in the OWL family is interpreted as a set of "individuals" and a set of "property assertions" which relate these individuals to each other. _x000D_ Following this logic, the specification helps to improve the comprehensibility of the administration’s data. By allowing to infer knowledge from sets of data and information, OWL provides meaning to the represented data. Therefore, it fosters the comprehensibility of administrative data while helps the decision-making process of administrations._x000D_ _x000D_ OWL2 W3C reference:_x000D_ https://www.w3.org/TR/owl2-overview/
'EuroVoc was developed for the first time in 1982 and has full support from the European Union, since it was developed to support and help European and National institutions on their functions. The thesaurus categorises knowledge domains close to the European Institution. Therefore, it can be considered with market acceptance at eGovernment level for the development of products and services. EuroVoc over the time: https://op.europa.eu/es/web/eu-vocabularies/th-dataset/-/resource/dataset/eurovoc?target=About#Time Eurovoc: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource /dataset/eurovoc'
CSS is a simple mechanism for adding style (fonts, colours, spacing...) to web documents, but by itself, it does not publish data on the web. It also does not comply with the other levels of maturity of Tim Berners-Lee's 5 stars for open data nor the principles of the linked open data. CSS v2.1 W3C reference: https://www.w3.org/TR/2011/REC-CSS2-20110607/ Five star linked open data: https://www.w3.org/DesignIssues/LinkedData.html
'The TrainingDML-AI standard aims to maximize the interoperability and reusability of geospatial training data. It provides detailed metadata for formalizing the information model of training data. This includes aspects such as how the training data is prepared, how to specify different metadata used for different ML tasks, and how to differentiate the high-level training data information model and extended information models specific to various ML applications. OGC TrainingDML-AI Standard: https://docs.ogc.org/is/23-008r3/23-008r3.html'
'GITB TDL promotes an environment for the adoption and implementation of e-business standards and specifications. Therefore GITB TDL impacts positively in the creation or adoption of organisational interoperability agreements. GITB TDL promotes the adoption of common validation syntax within multiple services testbed APIS (e.g. ESPD and AS4 messaging) GITB reference: https://www.itb.ec.europa.eu/docs/tdl/latest/_downloads/0dc573d06adafa1a273edd793577016d/CEN_WS_GITB3_CWA_Final.pdf GITB TDL examples: https://www.itb.ec.europa.eu/docs/tdl/latest/examples/index.html#examples'
"IEEE Std 802.3-2022 effectiveness is evaluated through industry feedback, testing, research, adoption, and ongoing updates. It's being tested in IEEE projects to ensure it meets requirements. The standard's adaptability allows the working group to address evolving needs. As a result, numerous new projects are currently being developed to leverage its capabilities. IEEE Working Group Projects: https://www.ieee802.org/3/ IEEE Working Group Details: https://standards.ieee.org/ieee/802.3/10422/ IEEE Std 802.3-2022 Reference: https://ieeexplore.ieee.org/document/9844436"
'The purpose of IPsec is not related to the modelling of business processes. Therefore, this criterion is not applicable to this specification. IPSec reference, What IPSec Does: https://datatracker.ietf.org/doc/html/rfc4301#page-7 IPSec reference, How IPSec Works: https://datatracker.ietf.org/doc/html/rfc4301#section-3.2 IPSec reference, Where IPSec Can Be Implemented: https://datatracker.ietf.org/doc/html/rfc4301#section-3.3'
'The purpose of UBL is not related to e-accessibility. Therefore this criterion is not applicable to this specification. UBL v2.3 reference: http://docs.oasis-open.org/ubl/os-UBL-2.3/UBL-2.3.html'
"The Dataspace Protocol is not included in any Member States' catalogues of recommended specifications. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards"
'The specification itself does not explicitly include mechanisms for ensuring or enabling data processing accuracy. The responsibility for ensuring data processing accuracy lies with the implementers and the systems that use it. ETSI Context Information Management (CIM); Security and Privacy: https://www.etsi.org/deliver/etsi_gr/CIM/001_099/007/01.01.02_60/gr_cim007v010102p.pdf'
'The XACML (eXtensible Access Control Markup Language) specification allows for partial implementations to varying degrees, offering flexibility depending on the specific needs and requirements of an organization or system. XACML OASIS reference: https://docs.oasis-open.org/xacml/3.0/xacml-3.0-core-spec-os-en.html'
"After carrying out information retrieval, an expert group from The Netherlands has been assessing the OData in terms of efficiency. These experts announced a fast data processing at the core of the specification. Microsoft also has released some solutions that mention the specification's efficiency. Microsoft: https://learn.microsoft.com/en-us/power-apps/developer/data-platform/webapi/query/optimize-performance Expert group's OData analysis: https://www.forumstandaardisatie.nl/open-standaarden/odata Netherlands OData Advisory report reference: https://www.forumstandaardisatie.nl/open-standaarden/odata"
Slovakia is recommending ADMS in its ICT National Catalogues. Slovakia’s Catalogue: http://www.informatizacia.sk/standardy-is-vs/596s CAMSS List of standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'There are no requirements for compliance and conformance analysis testing defined by the EN 16234-1 e-CF specification. CEN reference, CEN/TC 428 - ICT Professionalism and Digital Competences (Published standards), EN 16234-1 e-CF: https://standards.cencenelec.eu/dyn/www/f?p=205:110:0::::FSP_PROJECT:67073&cs=15E62ED24D608A5F10D6BEE8E6D50FA10'
The purpose of DCAT-AP is not related to the multilingual delivery of European public services. Therefore, this criterion is not applicable to this specification.
"Given that EuroVoc is a multidisciplinary thesaurus that contains keywords organized in 21 domains and 127 subdomains, it is possible to partially implement them depending on the user's needs. Its modular structure enables users to adopt specific segments or categories that align with their needs or systems without the need of incorporation of the entire thesaurus. EuroVoc Browser: https://eur-lex.europa.eu/browse/eurovoc.html"
'ISO 3166-1 does not explicitly enable data portability but does contribute to the expanding the sharing of data among public administrations at national and European level. It is the case of the INSPIRE (Infrastructure for Spatial Information in the European Community) project which makes use of ISO 3166-1 to ensure the maintenance of spatial data sets and corresponding data services in the EU (see INSPIRE Legislation reference, Directive 2007/2/EC document, Article 14). ISO 3166-1 reference: https://www.iso.org/standard/72482.html INSPIRE reference, Directive 2007/2/EC document, Article 14: https://inspire.ec.europa.eu/inspire-legislation/26'
"ebXML provides a set of components enabling users (data users) to store and work with any type of electronic content, fostering the comprehensibility of administrations' rules and processes. As well as providing an electronic data interchange model (that is, the ebRIM and the ebRS core components), the specification contributes and promotes to the comprehensibility of public services' implementations (see ebXML reference, Conformance section). For instance, there there is the ESPD-EDM on EU procurement, which relies on the Universal Business Language (UBL) and facilitates the implementation of the ESPD service over the Member States. ebXML reference, Conformance section: http://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html#__RefHeading__53396_365468741 ESPD-EDM ebXML reference: https://docs.ted.europa.eu/ESPD-EDM/3.0.1/xml_technical_handbook.html#_adoption_of_ubl_2_3"
'There is no Member State that includes EN 16234-1 e-CF in their national catalogue with its National Interoperability Framework (NIF) in alignment with the three categories: 1. Conceptual model for integrated public services provision, 2. interoperability layers, and 3. interoperability principles. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
"Schema.org does not rely on other specifications, except for derivative projects such as Microdata, which leverages support from other specifications to extend its functionality. However, the specification can be considered technology-agnostic. Schema.org reference, Getting started with schema.org using Microdata section: https://schema.org/docs/gs.html Schema.org-W3 Github reference, 'Improving schemas' section: https://github.com/schemaorg/schemaorg/blob/main/README.md"
The purpose of XAdES is not related to the availability of interfaces with internal information systems. Therefore, this criterion is not applicable to this specification. XAdES ISO reference: https://www.iso.org/standard/56025.html XAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/101900_101999/101903/01.04.02_60/ts_101903v010402p.pdf
After checking the different standard catalogues at supra-national level, there is no evidence of the inclusion of LegalDocML within any European catalogue of standards. ICT technical specifications: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en CEN search tool catalogue: https://standards.cen.eu/dyn/www/f?p=CENWEB:105::RESET:::: CENELEC search tool catalogue: https://www.cenelec.eu/dyn/www/f?p=104:107:0::::FSP_LANG_ID:25
'OpenTelemetry is designed to be highly extensible. This extensibility allows developers to add custom functionality, integrate with various tools and systems, and adapt the observability framework to meet specific needs. Developers can create custom spans and add attributes to capture detailed information about specific operations or transactions within their applications. OpenTelemetry: https://opentelemetry.netlify.app/docs/specs/otel/'
Like all the IETF standards, HTTP is a free and open technical specification, built on IETF standards and licenses from the Open Web Foundation. HTTP 1.1 is therefore licensed on a royalty-free basis. See: https://tools.ietf.org/html/rfc3668 https://tools.ietf.org/html/rfc2616
'XSD 1.1 is an Open specification which is implied in the validation of XML documents. As XML is a de-facto standard implied in the creation of solutions, including innovative ones, XSD is also fostering the creation of innovative solutions. XSD Reference: https://www.w3.org/TR/2012/REC-xmlschema11-1-20120405/'
PNG has the ISO community that supports the development of International standards. Moreover, it is published and supported in W3C website which is an international community developing open standards. The ISO standardization process: http://www.isotc292online.org/projects/iso-process/ W3C PNG reference: https://www.w3.org/TR/PNG/
The purpose of XHTML is not related to the modelling of business processes. Therefore, this criterion does not apply to the specification. XHTML W3C reference: https://www.w3.org/TR/xhtml1/
'Section 4 of the specification talks about multiple best practices on how to annotate that a newly published collection derived from an LDES. By taking into account the existence of future collections derived from LDES, it is clear that extensions are possible. LDES GitHub: https://semiceu.github.io/LinkedDataEventStreams/'
'DNS is maintained by IETF which is an international community developing open standards. About IETF: https://www.ietf.org/about/'
'The European Commission (EC) ISA2 Programme provides an Interoperability Testbed where Stakeholders can freely test these validation artefacts. All the ESPD-EDM artefacts necessary to perform the validation are set up in the testbed. Thus developers and integrators can test the validity of the ESPD-Request and ESDP-Response XML instances by uploading the instances in the testbed and launching the validation. Interoperability Testbed: https://joinup.ec.europa.eu/collection/interoperability-test-bed-repository/solution/interoperability-test-bed ESPD Technical Handbook testbed: https://docs.ted.europa.eu/ESPD-EDM/latest/xml_technical_handbook.html#_interoperability_testbed'
'DNS is a de-facto standard. Therefore, it is sufficiently mature and has sufficient market acceptance for its use in the development of products and services. DNS Domain Names: https://tools.ietf.org/html/1034 DNS - implementation and specification: https://tools.ietf.org/html/1035 '
'LDAP is not related to the publication of open data, therefore this criterion is not applicable to the specification. LDAP v3.0 https://datatracker.ietf.org/doc/html/rfc4511'
'DNS is a de-facto standard. Therefore, it is sufficiently mature and has sufficient market acceptance for its use in the development of products and services. DNS Domain Names: https://datatracker.ietf.org/doc/html/rfc8499 DNS - implementation and specification: https://tools.ietf.org/html/1035'
'The purpose of SFIA is not related to the protection of personal data in Public Administrations. Therefore, this criterion is not applicable to this specification. SFIA reference: https://sfia-online.org/en/sfia-8'
'The purpopse of Indexed Database API is not related to the publication of public data as open data. Therefore this criterion is not applicable to the specification. Indexed Database API: https://www.w3.org/TR/IndexedDB/'
The purpose of this Core Vocabulary is not related to e-accessibility. Therefore, this criterion is considered not applicable to this specification. CCCEV reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-criterion-and-core-evidence-vocabulary
ETSI has provided a conformance testing tool for electronic signatures according to the European Commission Mandate 460. The conformity testing tool involves different standards applied in the development of eSignatures, including PAdES, CAdES, XAdES, and ASiC. See: https://signatures-conformance-checker.etsi.org/pub/PAdESConformanceTestChecker_v1.0.pdf https://signatures-conformance-checker.etsi.org/pub/index.shtml
'OData is maintained and developed by OASIS, which is an international community developing open standards; specifically, by the Technical Committee (TC). The specification maintenance is transparent, and even if its development and the approval process is restricted to the specification TC, anyone can contribute by submitting feedback to the mailing list. All the contributions are publicly available. Developer community OASIS: https://www.oasis-open.org/org/ OData Technical Committee: http://www.oasis-open.org/committees/odata/'
'The Extensible Forms Description Language is based on an XML structure, which provides a standardised format for forms and data. Moreover, the specification allows for the implementation of some security and privacy mechanisms, such as digital signatures. This enables public administrations and service providers to collect, process, and exchange data electronically, facilitating the provision of digital services. Extensible Forms Description Language reference: https://www.w3.org/TR/NOTE-XFDL'
OASIS is a non-profit consortium that drives the development, convergence and adoption of open standards for the global information society, WS-Security is developed and maintained by OASIS consortium. See: https://www.oasis-open.org/org
"ISO/IEC 7498:1 is part of the UNE's catalogue of standards. UNE is Spain's only Standardisation Organisation, designated by the Spanish Ministry of Economy, Industry and Competitiveness to the European Commission. Through its activities, it fosters the development of an infrastructure of quality by promoting knowledge transfer and raising business standards. UNE: https://www.en.une.org//"
'ETSI TS 119 512 is not related to e-accessibility. Therefore this criterion is not applicable to this specification. ETSI TS 119 512 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.02_60/ts_119512v010102p.pdf'
SMP is not included in any national catalogue of recommended specifications whose Member State NIF is fully aligned with at least 4 out of 5 sections of the EIF according to NIFO factsheets. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
The Core Location Vocabulary is a simplified, reusable and extensible data model that captures the fundamental characteristics of a location, represented as an address, a geographic name, or a geometry. CLV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-location-vocabulary
"After some research, there has not been found anything regarding the specification's effectiveness. ETSI TS 119 612 specification: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf"
'The purpose of JSON is not related to data or information confidetiality. Therefore, this criterion is not applicable to the specification. JSON specification: https://www.ecma-international.org/wp-content/uploads/ECMA-404_2nd_edition_december_2017.pdf'
'One of the main purposes of YAML is to establish a common language that facilitates the exchange of data between organizations. Although YAML can contribute to improve the exchange of data, it is not adressed to guarantee security in this exchange. Despite this, YAML together with other specifications and applications can improve the security in data exchange. YAML specification: https://yaml.org/spec/1.2.2/#11-goals'
The W3C Royalty-Free IPR licenses granted under the W3C Patent Policy apply to all W3C specifications, including ADMS. Patent policy: https://www.w3.org/TR/patent-practice#ref-AC
'ADMS was developed and it is maintained by W3C which is an international community developing open standards. ADMS in W3C: https://www.w3.org/TR/vocab-adms/ ADMS in Joinup: https://joinup.ec.europa.eu/solution/asset-description-metadata-schema-adms/about'
'The ebXML specification was started in 1999 as a joint initiative between the United Nations Centre for Trade facilitation and Electronic Business (UN/CEFACT) and Organization for the Advancement of Structured Information Standards (OASIS). A joint coordinating committee composed of representatives from each of the two organisations led the effort. In this context, four different versions have been launched since 1999, and each release can be found in the OASIS web. The current and latest version (4.0) was launched in 2012. However, the specification has joined ISO recently, and in future releases it is possible that release management will not be available publicly. ebXML RegRep OASIS reference: https://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html ebXML RegRep ISO reference: https://www.iso.org/standard/83479.html'
WSDL is maintained by W3C which is an international community developing open standards. See: https://www.w3.org/Consortium/ https://www.w3.org/TR/wsdl20/
'HTTPS security features can indirectly contribute to building trust, protecting against tampering, and ensuring privacy, which can enhance the visibility and accessibility of such information and services on the web. HTTPS specification: https://tools.ietf.org/html/rfc2818 '
CSS v2.1 is publicly available for implementation and use for free on W3C's webpage. Therefore, it can be reused by the organizations, administrations, open communities, etc. that developed it. CSS v2.1 W3C reference: https://www.w3.org/TR/2011/REC-CSS2-20110607/
'XSLT includes features that allow extension by implementers or users, designed to maintain interoperability (see Section 3.2). XSLT Reference: https://www.w3.org/TR/xslt-30/#extension-attributes'
'Schema.org is open to any interested party who has agreed to the W3C Community Contributor License Agreement (CLA) (see Schema.org homepage reference, Community Group and Steering Group section). The W3C Royalty-Free IPR licences granted under the W3C Patent Policy apply to the schema.org specification. Schema.org homepage reference, Community Group and Steering Group section: https://schema.org/docs/about.html W3C Patent Policy reference: https://www.w3.org/TR/patent-practice#ref-AC'
'SHACL can significantly contribute to policy-based access control systems by defining rules that determine whether access to certain data should be granted or denied. By establishing these rules, SHACL indirectly helps protect information against unauthorised changes. "SHACL-ACL: Access Control with SHACL" study: https://link.springer.com/chapter/10.1007/978-3-031-43458-7_4 SHACL W3C reference: https://www.w3.org/TR/shacl/'
After being evaluated compliant with the regulation on standardisation 1025/2012, DNS has been identified by Commission Implementing Decision. See: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en
The purpose of EuroVoc is not related to long term preservation of electronic records. Therefore, this criterion is considered not applicable to this specification. EuroVoc webpage: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/eurovoc
'The NGSI-LD Information Model prescribes the structure of context information that shall be supported by an NGSI-LD system. The NGSI-LD Information Model is defined at two levels: the foundation classes which correspond to the Core Meta-model and the Cross-Domain Ontology. The latter is a set of generic, transversal classes which are aimed at avoiding conflicting or redundant definitions of the same classes in each of the domain-specific ontologies. GS CIM 009: https://www.etsi.org/deliver/etsi_gs/CIM/001_099/009/01.07.01_60/gs_CIM009v010701p.pdf'
'NUTS could be used in a multilingual context beyond a statistical purpose. The specification could be useful in determining the linguistic and dialectical areas when establishing a specific European public service. EUROSTAT reference, NUTS Principles and Characteristics section: https://ec.europa.eu/eurostat/web/nuts/principles-and-characteristics'
The specification is currently implemented in several initiatives in the public sector. The ODF helps to avoid vendor lock-in, which is part of the recommendations of EIF. Additionally, LibreOffice implements natively different versions of the Open Document Format. This is a key point that reflects the market acceptance of the specification. ODF ISO reference: https://www.iso.org/standard/66363.html ODF OASIS reference: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office ODF in a UK government project: https://www.gov.uk/government/publications/open-standards-for-government/sharing-or-collaborating-with-government-documents
One of the pillars of ELI is the usage of URIs templates patterns that ensure that resources are accessible in a persistent way over time. This fact fosters the long-term preservation of electronic documents ensuring their availability. Moreover, since it provides access to legal documentation in a machine-readable format, it also fosters its reuse and evolution towards other formats ensuring the evolution of European Public Services. ELI reference: https://eur-lex.europa.eu/eli-register/about.html
XACML is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, XACML can define the interoperability aspects of the "Access Management Component", and "Access Management Service" ABBs of the EIRA Technical View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/solution/elis/release/v100
At the moment of performing the assessment, the IPv4 is widely adopted as a key point on making data, information, and resources available on the internet. However, it is worth to point out that the new version recently is being gradually adopted including several innovative solutions. Furthermore, there are already transition mechanisms to connect nodes using different versions of the Internet protocol. Nevertheless, the European Commission has endorsed the adoption of IPv6 in new initiatives in order to ease the transition to the new version of the protocol. See: https://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=CELEX:52002DC0096:EN:HTML
'Estonia reporting 3.0 program and Nordic smart government. https://nordicsmartgovernment.org/ https://www.stat.ee/en/reporting-30 https://realtimeeconomy.ee/ https://www.dropbox.com/sh/b5i8ehpnzzymowl/AACpTH-mWRwOFGIQkUYDbWoWa/29.10.2021%20Presentations?dl=0&preview=004_Estonian+reporting+mapping+and+a+new+model+copy.pdf&subfolder_nav_tracking=1 '
'The purpose of DCAT is not related to the modullisation of business processes. Therefore this criterion is not applicable to this specification. DCAT (v2.0.0) reference: https://www.w3.org/TR/vocab-dcat-2/ '
There is no Member State that includes WS-BPEL in their national catalogue with The National Interoperability Framework (NIF) aligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'XACML is maintained and developed by OASIS which is an international community developing open standards. Developer community OASIS: https://www.oasis-open.org/org/'
The purpose of Xforms is not related to e-accessibility. Therefore, this criterion is considered not applicable to this specification. Xforms 2.0 W3C reference: https://www.w3.org/community/xformsusers/wiki/XForms_2.0
The OASIS TC in charge of LegalRuleML operates under the Royalty Free on Limited Terms IPR mode as defined in the OASIS Intellectual Property Rights (IPR) Policy. LegalDocML reference: https://www.oasis-open.org/committees/legaldocml/charter.php
LDAP is not related to the publication of public data as open data. Therefore, this criterion is not applicable to this specification. LDAP IETF reference: https://tools.ietf.org/html/rfc4511
"The purpose of TLS 1.3 is not related to the exposure of interfaces to access the public administration's services. Therefore this criterion is not applicable to this specification. TLS 1.3 2018 Reference: https://www.rfc-editor.org/rfc/rfc8446.html"
'SCIM has not been found included in any initiative neither at European nor on national level covering privacy aspects. SCIM: https://scim.cloud/'
The specification includes guidelines, recommendations and requirements with regards to the internal market (tool 24) and how policies and laws could benefit European citizens, business and institutions development reducing barriers and developing the once-only principle. Betterr Regulation Toolbox reference: https://ec.europa.eu/info/sites/info/files/better-regulation-toolbox_2.pdf
'After checking the different standard catalogues at supra-national level, there is no evidence of the Dublin Core Ontology as European standard. ICT technical specifications: https://single-market-economy.ec.europa.eu/single-market/european-standards/ict-standardisation/ict-technical-specifications_en'
By allowing the association of information with domain names, DNS facilitates their comprehension and enhances their visibility in a network.
The purpose of JPEG is not related to e-accessibility. Therefore, this criterion is considered not applicable to this specification. JEPG ISO reference: https://www.iso.org/standard/18902.html JPEG public reference: https://jpeg.org/jpeg/
After carrying out information retrieval, no document or study has been found assessing the RegOrg in terms of efficiency or effectiveness.
There are no technical specifications being under consideration to become a European standard that have the same application area.
'MIME is maintained and developed by IETF which is an international community developing open standards. Developer community IETF: https://www.ietf.org/about/'
After searching for a certification or conformity test to validate ADMS no tool has been found that assess the conformity of the specification.
'The purpose of this Core Vocabulary is related to the delivery of multilingual public services. The use of this Core Vocabulary for electronic criterion and evidence allows for removing language barriers thereby improving the cross border exchange of information. Core Criterion and Core Evidence Vocabulary reference (v1.0.0): https://joinup.ec.europa.eu/release/core-criterion-and-core-evidence-vocabulary-v100 '
'At the time of elaborating this assessment, this specification is not included in the EIRA Library of Interoperability Specifications (ELIS). EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /solution/elis/release/600'
'After searching through different catalogues, no evidence of the Core Location Vocabulary specification being included in the catalogue of any Member State was found. Core Location Vocabulary: https://interoperable-europe.ec.europa.eu/collection/semic-support-centre/solution/core-location-vocabulary/release/100'
According to the 5 star Open Data model suggested by Tim Berners-Lee about how to publish linked data, HTML5 is supporting the first level of maturity the which corresponds to make data available on the internet. HTML5 is the center of the Open Web Platform, it allows programming application. See: https://5stardata.info/en/ https://www.w3.org/2012/12/html5-cr.html.en
'ETSI TS 119 612 is not included in any national catalogue of recommended specifications whose Member State NIF has a high performance on interoperability according to NIFO factsheets. NIFO Factsheets: https://interoperable-europe.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public-administration-factsheets-2024 CAMSS list of standards: https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
'The specification has one major release published on the 6th of September of 2023. At the same time, the specification has a GitHub where change and release management is published. LDES specification: https://joinup.ec.europa.eu/collection/semic-support-centre/linked-data-event-streams-ldes LDES GitHub: https://github.com/SEMICeu/LinkedDataEventStreams '
'The main purpose of IPv6 is not to enhance visibility of administrative procedures, rules data, and services, but can contribute to it. For example, the specification provides a larger address space compared to IPv4, enabling more hierarchical addressing. This can simplify network management and enhance visibility, making it easier to organise and categorise network resources. IPv6 IETF: https://www.rfc-editor.org/rfc/rfc2460'
The specification contributes to enchance and simplify the process of drafting legal documents. This fact helps to save time and resources by removing administrative burden that have been related to regulation drafting over the years. An example of this is the LEOS software. LegalDocML reference: https://www.oasis-open.org/committees/legaldocml/charter.php LEOS: https://joinup.ec.europa.eu/collection/justice-law-and-security/solution/leos-open-source-software-editing-legislation
'CIM NGSI-LD API is developed and maintained by the European Telecommunications Standards Institute (ETSI). Its development involves contributions from industry experts and collaboration within ETSI working groups, particularly ETSI Technical Committee CIM. This standardisation body provides a foundational level of support for the ontology. ETSI takes into account the impact of users as they improve their standards and their relevancy. ETSI Technical Committee CIM: https://www.etsi.org/committee/cim'
'The purpose of SAREF is not related to ensuring the protection of personal data managed by Public Administrations. Therefore, this criterion is not applicable to this specification. SAREF: https://saref.etsi.org/core/v3.1.1/ '
"The EuroVoc Hanbook contains important information about the concept scheme, disambiguation of thesaurus terms, their relationships, EuroVoc maintenance etc. thus, defining requirements to conform to the specification's implementation. EuroVoc Hanbook: https://publications.europa.eu/resource/cellar/a2723a83-574f-11eb-b59f-01aa75ed71a1.0001.01/DOC_1"
ETSI’s Intellectual Property Rights Policy is based on Standard Essential Patents (SEP). The policy implemented by the standardisation organisation seeks to reduce risks and ensures that the standards are available under (F) RAND basis and Royalty-free, meaning that there are free of charge. See: https://www.etsi.org/intellectual-property-rights
'The purpose of the specification is to facilitate the exchange of structured data. By allowing to make the data available to other persons or organisations, this Core Vocabulary reduces the administrative burden. CPSV-AP Joinup webpage: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/core-public-service-vocabulary-application-profile/release/22'
SHACL is not included in any Member State standards catalogue but it was presented by Spain for its identification in the MSP.
'SAML 2.0 itself is a neutral, global standard that focuses on facilitating secure single sign-on and the exchange of authentication and authorization data. However, the features it offers can indeed simplify the delivery of public services, including those in the European context, when integrated appropriately. SAML 2.0 Reference: http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-tech-overview-2.0.html'
'IPv4 is mentioned in the "Communication from the Commission to the European Parliament, the Council, the European Economic and Social Committee and the Comittee of the Regions - Advancing the Internet : action plan for the deployment of Internet Protocol version 6 (IPv6) in Europe", as a specification that has been updated to provide enhanced security services, similar to those in IPv6. Communication from the Commission to the European Parliament, the Council, the European Economic and Social Committee and the Comittee of the Regions - Advancing the Internet : action plan for the deployment of Internet Protocol version 6 (IPv6) in Europe: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:52008DC0313&qid=1730898345313'
Even though it is a very recent standard produced in 2019, it has a strong community supporting it with a clear process of development. However, there are not relevant implementations supporting a wide market acceptance of the specification at the moment of performing the assessment. The Standard for Public Code webpage: https://standard.publiccode.net
The purpose of the specification is not related to data portability. Therefore, this criterion is not applicable to this specification.
XML 1.1 is publicly available for implementation and use for free on W3C's webpage. See: https://www.w3.org/TR/2006/REC-xml11-20060816/
At the moment of performing the assessment, there is no Member State that includes XACML in their national catalogue with The National Interoperability Framework (NIF) aligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards National Interoperability Framework Observatory: https://joinup.ec.europa.eu/collection/national-interoperability-framework-observatory-nifo/nifo-factsheets
'While MIME itself is not a comprehensive solution for e-accessibility, it can be part of a broader strategy to create digital content and services that are inclusive and accessible to a wide range of users, including those with disabilities. MIME specification: https://tools.ietf.org/html/rfc2045'
'The rules on European standardisation allow the European Commission to identify information and communication technology (ICT) technical specifications - that are not national, European or international standards - to be eligible for referencing in public procurement. This allows public authorities to make use of the full range of specifications when buying IT hardware, software and services, allowing for more competition in the field and reducing the risk of lock-in to proprietary systems. After being evaluated compliant with the regulation on standardisation 1025/2012, RDF has been identified by Commission Implementing Decision. During the evaluation process, all the Member States are invited to share their doubts. The positive evaluation of RDF and its identification is considered an interoperability agreement. Regulation on standardisation 1025/2012: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en'
Like all the IETF standards, FTPS is a free and open technical specification, built on IETF standards and licenses from the Open Web Foundation. FTPS is therefore licensed on a royalty-free basis. No IPR disclosures have been submitted directly on the FTPS specification (RFC 4217). Intellectual Property Rights in IETF: https://tools.ietf.org/html/rfc3668
'The specification is mentioned in "Metadata Quality Assessment Methodology" from "data.europa.eu". The Metadata Quality Assessment (MQA) measures the quality of various indicators, and the results of the checks are stored as Data Quality Vocabulary (DQV). "Metadata Quality Assessment Methodology" reference: https://data.europa.eu/mqa/methodology?locale=en World Wide Web Consortium (W3C) reference: https://www.w3.org/'
WS-Security is available for its study and use at OASIS’s webpage. Therefore it can be reused by the organisations, administrations, open communities, etc. that developed it. See: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=WS-Security
'One of the goals of YAML is to ensure portability between programming languages. Its specification facilitates data exchange between organizations, promoting interoperability. This makes YAML ideal for implementing digital services, supporting the principle of digital-first by enabling seamless integration and efficient communication across various platforms and systems. YAML specification: https://yaml.org/spec/1.2.2/'
'WAI-ARIA was conceived for assistive web technologies. Since this specification complements both HTML and SVG2, it can be implemented in any domain where one of these two other specifications coexist with. A good example is the Mozilla developer community, which has implemented this specification for HTML4 and HTML5, along with the functional specificities that characterise both implementations. WAI-ARIA reference: https://www.w3.org/TR/wai-aria/ Mozilla reference, ARIA section: https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA'
The W3C Royalty-Free IPR licenses granted under the W3C Patent Policy apply to all W3C specifications, including XML 1.1. See: https://www.w3.org/TR/patent-practice#ref-AC
'TLS is included in the national catalogues of recommended specifications for Cyprus, France, Germany, Greece, Malta, the Netherlands, Norway, and Spain. The National Interoperability Frameworks (NIF) of France and the Netherlands are aligned with at least three out of four scoreboards of the EIF Monitoring, according to the National Interoperability Framework Observatory (NIFO) factsheets. France National Catalogue of Standards (Referentiel General Interoperabilite) Reference: https://www.numerique.gouv.fr/uploads/Referentiel_General_Interoperabilite_V2.pdf Netherlands National Catalogue of Standards TLS Reference: https://www.forumstandaardisatie.nl/open-standaarden/tls CAMSS list of standards: https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-andspecifications-camss/camss-list-standards NIFO factsheets: https://interoperable-europe.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public-administration-factsheets-2024'
'The European Commission eArchiving community holds many events on which they discuss and promote the use of the eArchiving model. Among some of the standards this community shares their knowledge about their implementation results we can find the E-ARK specifications. eArchiving community: https://digital-strategy.ec.europa.eu/en/activities/earchiving-community eArchiving latest news: https://digital-strategy.ec.europa.eu/en/related-content?topic=192'
'No projects have been found that use XFDL and cover privacy aspects. Extensible Forms Description Language reference: https://www.w3.org/TR/NOTE-XFDL'
The specification is focused on providing guidelines, recommendations and mechanisms for the proper development of public policies and laws. Within the recommendations and mechanisms, there are no implications for long-term preservation or e-archiving. Therefore, it can be said that this is not the purpose of the specification and this criterion is considered not applicable to this specification. Better Regulation Toolbox reference: https://ec.europa.eu/info/sites/info/files/better-regulation-toolbox_2.pdf
'There has not been found any assessment addressing the effectiveness of the TGF specification. TGF specification: http://docs.oasis-open.org/tgf/TGF/v2.0/cs01/TGF-v2.0-cs01.html'
'The specification is recommended in 8 ICT Catalogues. FTP Specification Reference: https://datatracker.ietf.org/doc/html/rfc959 CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards'
'The application of the once-only principle in all EU Member States public administrations aims at reducing the administrative burden. To achieve this, interoperability between public administrations is a sine qua non condition. XML addresses and facilitates interoperability between public administrations, cross border services and impacts positively the development of eGovernment. This is due to the fact that it has been designed to store, transport data, and to exchange data through interoperable systems. Moreover, XML defines a set of rules for encoding documents in a human-readable format and machine-readable format enhancing the reusability of data and stimulating the interoperability of systems and services. See: https://www.w3.org/TR/2006/REC-xml11-20060816/'
'No forum or debate has been found that can contribute to the creation of communities along with the exchange of their data and results. However, it is possible to find some issues that speak of the TSA but without exchanging information or results. Joinup TSA reference: https://joinup.ec.europa.eu/collection/belgian-interoperability-catalogue/solution/tunnel-setup-protocol/distribution/rfc3161-internet-x509-public-key-infrastructure-time-stamp-protocol-tsp'
'The specification can be found distributed in the Joinup repository. Joinup UDDI reference: https://joinup.ec.europa.eu/collection/belgian-interoperability-catalogue/solution/universal-description-discovery-and-integration'
'GraphQL processes all data requests but only extensions (GraphQL-JS) or third APIs could be asked to resolve a response over an access control mechanism that ensures data confidentiality. GraphQL specification: https://graphql.org/learn/schema/'
DCAT-AP is included only in the national catalogue of Belgium and its NIF is not aligned with 4 out of 5 sections of the EIF according to NIFO factsheets.
'While the Dataspace Protocol is not involved in guaranteeing the authenticity and authentication of the roles agents involved in the data transactions, the Transfer Process Protocol section of the specification outlines the key elements of a set of allowable Message Type sequences defined as a state machine. The endpointProperties property of the Transfer Request Message may contain two optional values related to the term authorisation, which is an opaque authorisation token that clients must present when accessing the transport-specific endpoint address, and its type. IDSA Dataspace Protocol Transfer Process Protocol: https://docs.internationaldataspaces.org/ids-knowledgebase/v/dataspace-protocol/transfer-process/transfer.process.protocol'
The adoption of this Core Vocabulary as data model does not hamper the scalability of systems. CCCEV reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-criterion-and-core-evidence-vocabulary
'There is no mention of OData in any official document stating its conformance in regards to Regulation 1025/2012. It does not appear in any of the main European standard development bodies, therefore, the specification is not a European standard. ICT technical specifications: https://ec.europa.eu/growth/single-market/european-standards/ict-standardisation/ict-technicalspecifications_en CENELEC and CEN search tool catalogue: https://standards.cencenelec.eu/dyn/www/f?p=CEN:105::RESET::::'
'ETSI TS 119 512 is not directly related to data protection, as its main purpose is to specify protocols for trust service providers providing long-term data preservation services for digital signatures and general data. Data protection considerations are overlooked given that they are addressed by its companion document ETSI TS 119 511 (Policy and security requirements for trust service providers providing long-term preservation of digital signatures or general data using digital signature techniques) ETSI TS 119 512 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.02_60/ts_119512v010102p.pdf ETSI TS 119 511 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119511/01.01.01_60/ts_119511v010101p.pdf'
'The specification enables the visibility of administrative procedures as ISO 19941 is about cloud computing interoperability and data portability. Integration and portability of administrative data is crucial in enhancing its visibility. ISO 19941: https://www.iso.org/obp/ui/en/#iso:std:iso-iec:19941:ed-1:v1:en'
'XML is used to encode all communications to web services. Therefore, it fosters the availability of public administrations interfaces. Additionally, the benefit of using XML is that web services are not tied to any one operating system or programming. See: https://esentool.ted.europa.eu/ '
'UDDI registries can implement enhanced security measures to ensure controlled access and protect personal data. For instance, the WebSphere Application Server facilitates access to UDDI records based on user categories, ensuring that sensitive information is accessible only to authorized users. IBM security reference: https://www.ibm.com/docs/en/was/8.5.5?topic=curs-configuring-uddi-registry-use-websphere-application-server-security'
The German Climate Computing Center (DKRZ) has used the recommendation to deploy an operative service that enables data users to create custom research data collections ("data carts") as part of the global Earth System Grid Federation (ESGF): https://esgf-data.dkrz.de/projects/esgf-dkrz/datacart_pid
'This specification is included in the solutions catalogue of ICT Standards for Procurement created by the European Commision. The European Catalogue will contribute to these objectives by offering a one-stop-shop for procurers on guidelines for procurement, including on vendor lock-in, on the use of standards, and a lifecycle costing scheme that accounts for the often neglected interoperability costs. It will streamline the numerous guidelines and provide for a platform of exchange and dissemination. ICT Standards for Procurement: https://joinup.ec.europa.eu/collection/ict-standards-procurement'
'While the OpenTelemetry specification itself is not a direct enabler of digital service delivery channels, it provides essential observability and monitoring capabilities that support the reliability, performance, security, and compliance of the underlying digital systems. OpenTelemetry can ensure the effective delivery of digital services through various channels, including web applications, APIs, mobile apps, and IoT devices. OpenTelemetry: https://opentelemetry.netlify.app/docs/specs/otel/'
The specification defines a flexible model, vocabulary and encoding mechanism for the representation of statements regarding de usage of datasets, services or other digital content. These mechanisms are reusable, extensible allowing their implementation independently of the business domain. Moreover, the Working Group in charge of its development has the aim to promote ODRL V2.2 to existing and new sectors/industries. W3C ODRL Community: https://github.com/w3c/odrl
"As the specification's community foresee a review of every release, it also encourages the creation of communities to help review the content is released each time. Core Criterion and Core Evidence Vocabulary reference (v1.0.0): https://joinup.ec.europa.eu/release/core-criterion-and-core-evidence-vocabulary-v100 CCCEV Github Reference: https://github.com/SEMICeu/CCCEV"
The purpose of JSON is not related to ensuring the availability of interfaces. Therefore this criterion is not applicable to this specification.
'XHTML complies with the five principles of Open Data since it publishes data in a structured, machinereadable format, is XML-compliant for easy viewing, editing, and validation of documents, and supports new elements and extensions to ensure interoperability across different environments. Built on open standards, XHTML is compatible with open-source tools and facilitates the publication of data under open licenses, eliminating the need for proprietary software. XHTML Reference: https://www.w3.org/TR/xhtml1/#xhtml'
'The specification is at the core of multiple usecases complied on the IDTA initiative. Some of them are Collaborative Engineering and Product Carbon Footprint. Both use the AAS as way to facilitate the traceability of data (carbon footprint or desing changes) among partners and the creation of communities/working groups associated with this tasks. Product Carbon Footprint use case https://industrialdigitaltwin.org/en/use-cases/product-carbon-footprint Collaborative Engineering use case: https://industrialdigitaltwin.org/en/use-cases/collaborative-engineering-the-technological-basis-for-the-digitalized-value-chain IDTA use cases: https://industrialdigitaltwin.org/en/use-cases IDTA Github https://github.com/admin-shell-io Details of the Asset Administration Shell (AAS) https://industrialdigitaltwin.org/en/wp-content/uploads/sites/2/2024/06/IDTA-01001-3-0-1_SpecificationAssetAdministrationShell_Part1_Metamodel.pdf'
JPEG is independent of any software, hardware, or operating system. So it can be said that JPEG is independent of any specific technology or platform. JEPG ISO reference: https://www.iso.org/standard/18902.html JPEG public reference: https://jpeg.org/jpeg/
'However, the E-ARK CSIP can indirectly support the publication of data on the web in structured and machine-readable formats. By following the CSIP guidelines, organizations can create well-structured information packages that include descriptive metadata. This metadata can provide valuable information about the content of the package, making it easier for users to discover and understand the data within. Moreover, the specification also outlines the the importance of using open standards such as XML. E-ARK CSIP specification: https://earkcsip.dilcis.eu/#introduction'
The purpose of CAdES is not related to the comprehensibility of administrative information, data or services. Therefore, this criterion is not applicable to this specification. CAdES ISO reference: https://www.iso.org/standard/64756.html CAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/101700_101799/101733/02.01.01_60/ts_101733v020101p.pdf
The OASIS Royalty-Free IPR licenses granted under the OASIS Patent Policy apply to all OASIS specifications, including SMP. OASIS Case Study Guidelines: https://www.oasis-open.org/policies-guidelines/casestudies
'EN 16234-1 first appeared as a common framework of professional digital and IT competences, skills and knowledge in 2008, known as CEN Workgroup Agreement (CWA) 15893-1:2008 (see CEN Workshop on ICT Skills reference, List of CWAs section). EN 16234-1 v2.0 of the standard was launched in 2010 (known as CWA 16234-1:2010), and a third release in 2014 (CWA 16234-1:2014). In 2016, EN 16234-1 e-CF (EN 16234-1:2016) was adopted as a European Standard (see CEN/TC 428 "ICT Professionalism and Digital Competences" Business Plan 2022 reference, section 1.1). The official lastest version of the EN 16234-1 e-CF specification was published in 2019 (EN 16234-1:2019), which corresponds to version 4.0. Although the specification meets the requirements for a mature specification, there is no documentation on its development processes. CEN Workshop on ICT Skills reference, List of CWAs section: http://relaunch.ecompetences.eu/cen-ict-skills-workshop/ CEN/TC 428 "ICT Professionalism and Digital Competences" Business Plan 2022 reference, section 1.1: https://standards.cencenelec.eu/BPCEN/1218399.pdf'
'SFIA is intended to serve as a device to represent the skills and competences of any ICT professional workforce which largely benefits the reuse of relevant information in all information systems. There is no evidence of any relationship between SFIA and the One Time One Principle (OOP). SFIA reference: https://sfia-online.org/en/sfia-8'
'One of the focuses of the specification is to define a profile for the safe time-stamping protocol that ensures the protection of the information treated. The specification is compliant with Regulation (EU) No. 919/2014 ETSI EN 319 422 reference: https://www.etsi.org/deliver/etsi_en/319400_319499/319422/01.01.01_60/en_319422v010101p.pdf'
The Standard for Public code aims to provide a set of elements that can help public administrations to build open-source solutions that can be reused across borders and amongst organisations. It provides great scalability which can help to build alternatives and systems fostering and ensuring data portability. The Standard for Public Code webpage: https://standard.publiccode.net/
The purpose of WS-Security is not related to e-accessibility. Therefore, this criterion is not applicable to the specification.
'Data processing accuracy in RDF can be ensured using a variety of techniques, such as data validation, error checking, and data quality assessment. These techniques can be integrated with RDF data processing workflows to ensure that the data being processed is accurate and meets specific quality standards. ABECTO: Assessing Accuracy and Completeness of RDF Knowledge Graphs: https://www.semantic-web-journal.net/content/abecto-assessing-accuracy-and-completeness-rdf-knowledge-graphs RDF primer document: https://www.w3.org/TR/rdf11-primer/'
WS-BPEL is one of the programming language that aims to make any process possible. Moreover, developers can have stability to implement and plan through WS-BPEL as it is one of the most used programming languages in web services. WS-BPEL OASIS reference: http://docs.oasis-open.org/wsbpel/2.0/OS/wsbpel-v2.0-OS.html
'The purpose of SHACL is not related to enable the secure processing of data. Therefore this criterion is not applicable to this specification. SHACL W3C reference: https://www.w3.org/TR/shacl/'
The purpose of LDAP is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification. LDAP IETF reference: https://tools.ietf.org/html/rfc4511
'While the XBRL specification explicitly notes that security, privacy and confidentiality are not directly in scope for XBRL, the chief architect of XBRL GL developed the structure of XBRL GL based on more than 10 years working with the XML security efforts of the W3C and is a named contributor to the XML Encryption specification. In particular, personally identifiable information is segregated and standardized to simplify encryption and other protection efforts. This issue of data protection is dependent on other specifications or technologies like the XML Encryption. '
The purpose of the specification is not related to the publication of public data as Open Data. IETF Reference: https://5stardata.info/en/ https://tools.ietf.org/html/rfc3161
'Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility at any moment. In addition, both members and non-members of the Code List Representation TC are welcome to participate in the unmoderated Code List Representation Developer Mail List by subscribing at the OASIS mail list manager. However, official comments still must be submitted to the TC by any person through the use of the OASIS TC Comment Facility. OASIS Code list Representation TC: https://groups.oasis-open.org/communities/tc-community-home2?CommunityKey=7558fd85-f7ac-4dd7-b57b-018dc7d3f6f7'
The Semantic Interoperability Community (SEMIC) has established Working Groups. These Working Groups are open to the participation of everyone interested in semantic solutions working for public administrations in the Member States or in EU institutions. SEMIC working groups: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/about
'WAI-ARIA has the Web Accessibility Initiative - Communities of Practice (WAI-COOP) platform for sharing results and best practices. Therefore, the specification encourages the creation of open information about the specification and encourages relevant communities from the EU to share their results; therefore, this platform also extends at national level. WAI-COOP reference: https://www.w3.org/WAI/about/projects/wai-coop/'
'There has not been found any platform to test conformance to ETSI TS 119 512. Nonetheless, the specification lists a set of requirements needed to comply with in order to be conformant can be checked manually wether or not applied. ETSI TS 119 512 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.02_60/ts_119512v010102p.pdf'
"CIM NGSI-LD API can contribute to improving data portability in various ways. It defines a standardised way to represent entities, their properties, and relationships, which makes it easier to understand and exchange data consistently across different systems and applications. Moreover, the use of JSON-LD's @context enables the definition of fully qualified names (URIs) for terms used in data payloads, which helps in disambiguating the meaning of the data when shared between different systems. Consequently, this standardisation promotes interoperability by ensuring that systems using the API can exchange data seamlessly. GS CIM 009: https://www.etsi.org/deliver/etsi_gs/CIM/001_099/009/01.07.01_60/gs_CIM009v010701p.pdf"
'XSLT specification facilitates the publication of data on the web through its ability to transform XML documents into various formats suitable for web display. XSLT Reference: https://www.w3.org/TR/xslt-30/#what-is-xslt'
The purpose of PDF/A is not related to organisational interoperability. Therefore, this criterion is not applicable to the specification. PDF/A reference: https://www.iso.org/standard/38920.html https://www.iso.org/standard/50655.html
'The purpose of Advanced Encryption Standard is not related to the delivery of multilingual services. Therefore this criterion is not applicable to this specification. AES Standard Reference: https://csrc.nist.gov/pubs/fips/197/final'
SVG is publicly available for everyone to study and free of charge at the W3C webpage. W3C Specification: https://www.w3.org/TR/SVG11/
'At least 12 Member States are recommending HTTP. HTTP is included in 12 national catalogues. The Member States that includes the specification are Bulgaria, Croatia, Cyprus, Finland, France, Germany, Greece, Netherlands, Norway, Portugal, Spain and Sweden. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
MIME is publicly available for implementation and use, and therefore for everyone to study, for free on IETF webpage. MIME reference: https://tools.ietf.org/html/rfc2045
'The specifications is in constant development by its community, and the documentation is published on OpenLDAP. OpenLDAP 1.0 was implemented as an open source version of LDAP made it very popular. Therefore, it is demonstrated that LDAP has enough maturity for its use in the development of digital solutions and services. LDAP IETF reference: https://tools.ietf.org/html/rfc4511 OpenLDAP: https://www.openldap.org/'
'The specification is in a very early stage, has been implemented and it is being implemented in Italy and Germany. However, at the moment of performing the assessment, there are no assessment of the specifications efficiency. Publiccode.yaml documentation: https://docs.italia.it/italia/developers-italia/publiccodeyml-en/en/master/index.html Italian National Software Catalogue: https://developers.italia.it/ Open CoDE: https://opencode.de/en'
'CPOV is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, CPOV can define the interoperability aspects of the "Core Data Model" and "Data" ABBs of the EIRA Semantic View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications camss/solution/elis/distribution/elis-v600xlsx'
'ETSI TS 119 432 is not related to enabling the long-term preservation of data (electronic records included). Therefore, this criterion is considered not applicable to this specification ETSI TS 119 432: https://www.etsi.org/deliver/etsi_ts/119400_119499/119432/01.02.01_60/ts_119432v010201p.pdf'
The W3C Royalty-Free IPR licenses granted under the W3C Patent Policy apply to all W3C specifications, including ADMS. W3C Patent practice: https://www.w3.org/TR/patent-practice#ref-AC
'The use of precomputed responses allows replay attacks in which an old (good) response is replayed prior to its expiration date but after the certificate has been revoked. Deployments of OCSP should carefully evaluate the benefit of precomputed responses against the probability of a replay attack and the costs associated with its successful execution. OCSP reference, section 5: https://datatracker.ietf.org/doc/html/rfc2560'
'This specification refers to the Dynamic Attribute Provisioning Services so, it is inherently abstract and can be implemented and/or used in any domain as long as it fulfills the requirements. Therefore, its use goes beyond a specific business domain. DAPS: https://github.com/International-Data-Spaces-Association/IDS-G/tree/main/Components/IdentityProvider/DAPS'
'According to the official documentation, ISO 3166-1 was first published in 1974, and subsequent editions in 2003, 2013 and 2020. ISO 3166-1 is the Part 1 of the ISO 3166 family of standards, which was divided in three parts in 1997. Part 1 was created on the basis of country names obtained from the United Nations. In 2013 the specification was integrated in an ISO "standard as a database" (see ISO 3166-1 reference, Country Codes on the Online Browsing Platform), easing its accessibility on the web and integrating all the specification's supporting processes (e.g. change history of country codes). Besides, the specification has published documentation on its supporting processes (see ISO 3166-1 reference, Public Information on ISO 3166-1). ISO 3166-1 reference, Introduction section: https://www.iso.org/obp/ui/#iso:std:72482:en ISO 3166-1 reference, Country Codes on the Online Browsing Platform: https://www.iso.org/obp/ui/#search/code/ ISO 3166-1 reference, Public Information on ISO 3166-1: rg/livelink/livelink?func=ll&objId=16944257&objAction=browse&viewType=1'
'ISO 19941 is chosen as one of the specifications recommended for the creation of dataspace infrastructures in the Data Space Support Center, which typically supports this type of projects. DSSC: https://dssc.eu/space/SE1/185794608/Data+Interoperability+standards+and+technologies+landscape'
'WSDL is more about the "what" and "how" of a web service—what operations it supports and how to communicate with it. The Web Services Description Language (WSDL) is primarily focused on describing the interface and operations of web services, emphasizing the contract between the service provider and consumer. It provides a standardized way to specify the location of a web service, the operations it supports, the format of the messages, and the protocols for communication. W3C WSDL specification: https://www.w3.org/TR/wsdl20/'
The purpose of the specification is not related to foster the availability and comprehensibility of public administrations services or the decision-making process.
The Standard for Public Code aims to be a reference resource for making public administration efficient when creating public services and products reusable. Its usage can benefit European Institutions of a common method for the development of software solutions to be deployed all around Europe. The flexibility and capacity to adapt the code for a specific purpose and the general guidelines for its creation and documentation can foster the creation of software solutions supporting multilingualism. Moreover, it could be used together with other already existing resources as the CEF Translation Building Block to ensure multilingual service delivery. The Standard for Public Code webpage: https://standard.publiccode.net/
The specification purpose is to enable communications over the internet. IPv6 is the new version of IPv4 which is a widely used protocol therefore it is not dependent of any specific platform or technology. Thus, the adoption of IPv6 does not hamper the interoperability.
'The Core Location Vocabulary is a simplified, reusable and extensible data model that captures the fundamental characteristics of a location, represented as an address, a geographic name, or a geometry. By describing locations (addresses, geographical names, etc) in a common way using both human and machine-readable format, it allows the publication of information as open data for its consultation and reuse. In addition, the specification resorts to the usage of an open standard such as JSON-LD. In addition, this vocabulary is also aligned with the 5 stars of tim.berners. Tim.berners 5stardata: https://5stardata.info/en/ Core Location Vocabulary: https://interoperable-europe.ec.europa.eu/collection/semic-support-centre/solution/core-location-vocabulary/release/100'
As a document format, PDF/A helps to make data available on the internet. This fact demonstrates that the standard is supporting the first level of maturity from Tim Berners-Lee's 5-star schema for Open data. PDF/A reference: https://www.iso.org/standard/38920.html https://www.iso.org/standard/50655.html Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/es/
The purpose of PDF 1.7 is not related to e-accessibility. Therefore, this criterion is not applicable to the specification.
'HTTP primary role is to provide a standardized framework for web communication by using a request response functions between servers and clients facilitating the access to websites .However, it does not specify how to scope comprehensibly administrative procedures, rules data, and services. Therefore, this criterion is not applicable to the specification. HTTP /1.1 RFC 2616 Reference: https://www.rfc-editor.org/rfc/rfc2616.html'
OpenPM2 is a public asset designed and developed by the European Commission and can be accessed and reused without any payment conditions. Therefore, it can be considered that the specifications is licensed under royalty-free basis and (F)RAND basis. OpenPM2 specification reference: https://op.europa.eu/en/publication-detail/-/publication/ac3e118a-cb6e-11e8-9424-01aa75ed71a1/language-en/format-PDF/source-83307127
"Schema.org opted for a flexible data model and introduced 'hosted extensions' (see Schema.org Hosted Extensions reference), as a way of adding more detailed descriptive vocabulary building on the schema.org core vocabulary (see Schema.org reference, Organization of Schemas section, Extensions subsection). The specification allows extension and encourages users to share their work through through the GS1 Web Vocabulary platform; external extensions are, however, out of the scope of the schema.org development community. Schema.org Hosted Extensions reference: https://schema.org/docs/extension.html Schema.org reference, Organization of Schemas section, Extensions subsection: https://schema.org/docs/schemas.html GS1 Web Vocabulary platform: https://www.gs1.org/voc/"
"ebXML facilitates organisational interoperability agreements, since one of the specification's objectives is to boost interoperability within organisations. For example, ebXML enables the creation of Collaboration Protocol Agreement (CPA). ebXML reference: http://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html Joinup CPA toolkit reference: https://joinup.ec.europa.eu/collection/ict-security/solution/cpa-creation-toolkit"
In some cases, the specification uses ambiguous and misleading terms such as “data-data” and “literature-data” which hampers the understanding of the recommendations. The specification has been adopted by different organisations and initiatives and it demonstrates that the specification has sufficient completeness and consistency for the use and development of products and services.
SAMM was defined with flexibility in mind so that small, medium, and large organizations using any style of development can customize and adopt it. It provides a means of knowing where your organization is on its journey towards software assurance and understanding what is recommended to move to the next level of maturity. So it can be said that SAMM can be applied and developed in different domains and purposes without harming the interoperability of functionality of systems. SAMM webpage: https://owaspsamm.org/ SAMM documentation: https://github.com/OWASP/samm/blob/master/Supporting%20Resources/v2.0/OWASP-SAMM-v2.0.pdf
'After searching in the different official European websites and repositories, there is no evidence that the GITB TDL is included in an open repository/catalogue of standards at a national level. GITB TDL reference: https://www.itb.ec.europa.eu/docs/tdl/latest/introduction/index.html#introduction'
'The purpose of TSP is not related to e-accessibility. Therefore, this criterion is considered not applicable specification. TSP IETF reference: https://tools.ietf.org/html/rfc3161'
'The XFDL specification is a high-level, XML-based language. In this context, the XML entities allows to store information to reuse it again and again by referring to it, avoiding writing that information multiple times. XML reuse of information reference: https://www.geeksforgeeks.org/dtd-entities/'
'The purpose of DNS is not related to Access Control. Therefore this criterion is not applicable to the specification. DNS IETF reference: https://datatracker.ietf.org/doc/html/rfc8499'
'Since OAS is a tool that serves as a guide for the development and documentation of APIs, it can be said that customisation is always allowed as long as it complies with the structure set by the specification. OAS specification: https://spec.openapis.org/oas/latest.html#openapi-specification OAS in Github: https://github.com/OAI/OpenAPI-Specification/#participation '
Hypertext Transfer Protocol Secure is a more secure extension of the Hypertext Transfer Protocol. It is used for secure communication over a computer network.
PaDes fosters data portability by allowing electronically signed documents to be exchanged across borders and to be compatible with different systems.
'HTTP can be mapped to the EIRA Library of Interoperability Specifications (ELIS) in the "Data Exchange" under the Technical Application View. EIRA Library of Interoperability Specifications (ELIS): https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/v610'
5 Member States are recommending Ogg in their ICT National Catalogues. These Member States are France, Germany, Norway, Poland and Spain. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'The puropse of ETSI TS 119 512 is not related to the publication of open data, therefore this criterion is not applicable to the specification. ETSI TS 119 512 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.02_60/ts_119512v010102p.pdf'
'Taking the initial purpose of the specification, which is to establish a set of guiding principles as a foundation for data spaces, it can be considered that the specification is involved in fostering the comprehensibility of Public Administrations data as well as relevant data produced for the decision-making process. IDSA Dataspace Protocol Specification: https://docs.internationaldataspaces.org/ids-knowledgebase/v/dataspace-protocol/overview/readme'
'The specification is not included in any open repository/catalogue of standards at European level. Extensible Forms Description Language reference: https://www.w3.org/TR/NOTE-XFDL'
The purpose of XML is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification.
'The specification is included in the EU Vocabularies repository. EU Vocabularies reference: https://op.europa.eu/en/web/eu-vocabularies/schemas'
The purpose of MIME is not related to e-accessibility. Therefore, this criterion is considered not applicable to this specification. MIME reference: https://tools.ietf.org/html/rfc2045
IETF has a formal review and approval so that all the relevant stakeholders can formally appeal or raise objections to the development and approval of specifications. Each distinct version of an Internet standards-related specification is published as part of the "Request for Comments" (RFC) document series. This archival series is the official publication channel for Internet standards documents and other publications. During the development of a specification, draft versions of the document are made available for informal review and comment by placing them in the IETF's "Internet-Drafts" directory, which is replicated on a number of Internet hosts. This makes an evolving working document readily available to a wide audience, facilitating the process of review and revision. Standard process IETF: https://www.ietf.org/standards/process/ Internet Best Current Practices IETF: https://tools.ietf.org/html/rfc2026
All solutions developed in ISA² Programme are under ISA Open Metadata Licence which is perpetual, royalty-free and non-exclusive license to Use and re-Use the Works. ISA open metadata license: https://joinup.ec.europa.eu/licence/isa-open-metadata-licence-v11
'There are different documentation and information that takes into account EuroVoc as part of the narrative and includes it as valuable. An example of a use case is for the Italian Chamber of Deputies. In here, the use case was presented in a EuroVoc conference to show the result and the effectiveness of using EuroVoc as the basis for the semi-automatic classification of documents. Eurovoc and parliamentary documents: A semi-automatic classification experience at the Italian Chamber of Deputies: https://expertsystem.com/expert-systems-cogito-semantic-platform-to-be-featured-at-eurovoc-conference'
'The purpose of the EN 303 645 is not related to the publication of open data. Therefore, this criterion is not applicable to this specification. EN 303 645 homepage reference: https://www.etsi.org/technologies/consumer-iot-security'
'The European Space Agency is implementing ISO/IEC 27001 to ensure its data is protected and properly managed to reduce ISMS risks. European Space Agency case study: https://publicsectorassurance.org/case-study/european-space-agency-uses-iso-27001-to-protect-its-data/'
The purpose of this document is not related to the once-only principle. Therefore, this criterion is not applicable to the specification. W3C reference: https://www.w3.org/TR/dwbp/
" While SAREF's scope is not explicitly directed towards administrative procedures, rules data, and services, the use of ontologies in general, including SAREF, can contribute to certain aspects of visibility in administrative procedures and related domains if they happen to describe smart appliances. SAREF: https://saref.etsi.org/core/v3.1.1/"
7 Member States are recommending UDDI in their ICT National Catalogues. See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
Although the specification defines a set of principles to help implementers to be consistent, and even tools for this purpose, there are no conformity test or certifications that allow users to check the level of compliance with the requirements established.
Xiph.Org Foundation is a non-profit corporation dedicated to protecting the foundations of Internet multimedia from control by private interests. Their main purpose is to support and develop free, open protocols and software to serve the public, developer, and business markets. All stakeholders can contribute in the development of their specifications. XIPH contribution: https://wiki.xiph.org/How_to_help
TIFF/IT is one of the safest image file types available. The most important security benefit is the transparent data of every TIFF image file. This fact makes possible to evaluate the information about the photo before opening and it prevents the chance of a virus hiding in the file. So the specification makes data exchange between citizens and public administrations secure and trustworthy. TIFF/IT ISO reference: https://www.iso.org/standard/34342.html TIFF Image file explanation: https://www.canto.com/blog/tiff-image-file/
W3C has provided a validator which allows testing and validate web documents including web documents in HTML. W3C validator: https://validator.w3.org/
'While Verifiable Credentials themselves do not guarantee long-term preservation, their use within a broader framework of standards and data archiving best practices can contribute to the sustainability and preservation of electronic records and information. Verifiable Credentials: https://www.w3.org/TR/vc-data-model/'
"All major and minor releases foresee a public review during which collected feedback is publicly visible through Dataspace Protocol's GitHub, accesible to any user. The current version of the specification (2024-1) is the release candidate and considered to be stable. Further changes shall not affect conformity. The Dataspace Protocol is being constantly reviewed and improved thanks to the input of its users, who are invited to provide feedback as Issue in their GitHub repository. IDSA Dataspace Protocol Specification: https://docs.internationaldataspaces.org/ids-knowledgebase/v/dataspace-protocol/overview/readme IDSA Open Source: https://internationaldataspaces.org/make/open-source/ Dataspace Protocol GitHub Issues: https://github.com/International-Data-Spaces-Association/ids-specification/issues"
'OCSP defines a protocol useful in determining the current status of a digital certificate without requiring CRLs. Therefore, it does not explicitly enable the delivery of any service, but can implicitly reduce the administrative burden. OCSP reference: https://datatracker.ietf.org/doc/html/rfc2560'
'The purpose of the Dataspace Protoccol is not related to e-accessibility. Therefore, this criterion is considered not applicable to this specification. IDSA Dataspace Protocol: https://docs.internationaldataspaces.org/ids-knowledgebase/v/dataspace-protocol/overview/readme'
'One Member State is recommending WAI-ARIA as an accessibility standard. However, the specification is not listed in its ICT National Catalogue. This Member State is Spain. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards PAe Accessibility Standards reference: https://administracionelectronica.gob.es/pae_Home/pae_Estrategias/pae_Accesibilidad/pae_normativa/pae_eInclusion_Normas_Accesibilidad.html?idioma=en'
'LDAP is an application protocol for accessing and maintaining distributed directory information services over the net, it is independent of implementation. The specification allows many applications and services to connect to the LDAP server to validate users, which reduces the administrative burden of the system administrators and the users. As it is widely supported the implementation of the LDAP would not hamper the interoperability between systems and services. LDAP IETF reference: https://tools.ietf.org/html/rfc4511 '
The purpose of SAML 2.0 is not related to the availability of interfaces. The specifications aim to authenticate and authorise access to resources or services.
'ISO 3166-1 may help easing the creation and formalisation of Interoperability agreements; for example, the Reference And Management Of Nomenclatures (RAMON) is a self-declared organisational interoperability agreement which integrates ISO 3166-1 along with other international specifications. EUROSTAT reference, RAMON data server: https://ec.europa.eu/eurostat/ramon/nomenclatures/index.cfm?TargetUrl=LST_CLS_DLD&StrNom=CL_GEO&StrLanguageCode=EN&msclkid=5b294654b00e11ecb0cfbc45e6ce9d20'
'WAI-ARIA specification allows customization. WAI-ARIA provides a set of roles, states, and properties that can be applied to HTML elements to enhance the accessibility of web content. WAI-ARIA reference: https://www.w3.org/TR/wai-aria/'
RegOrg is available for its use and implementation at the Joinup platform with all its documentation. Moreover, it is also available in W3C webpage. RegOrg Joinup reference: https://joinup.ec.europa.eu/solution/registered-organization-vocabulary RegOrg W3C reference: https://www.w3.org/TR/vocab-regorg/
"SAREF has not been found included in any Member States' catalogues of recommended specifications. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards"
Core Criterion and Core Evidence Vocabulary has a good market acceptance. Some parts of this vocabulary have been used to develop European solutions, for example, ESPD-EDM (European Single Procurement Document - Exchange Data Model) which is the technical representation of the legal European Single Procurement Document. It is used to support interoperability between ESPD services provided all over Europe. Additionally, other projects/initiatives like The Once-Only Principle (TOOP), and the eCertis are based on the CCCEV. ESPD documentation: https://docs.peppol.eu/pracc/espd/edm/ Core Criterion and Core Evidence Vocabulary reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-criterion-and-core-evidence-vocabulary TOOP: http://wiki.ds.unipi.gr/display/TOOP/Core+Vocabularies+and+Application+Profiles eCertis: https://ec.europa.eu/tools/ecertis/#/about
This Core Vocabulary offers several services that aim to help e-Government professionals share their experience, and reuse data and services across borders. Specifically, the RegOrg vocabulary was used in the Business Registries Interconnection System (BRIS), which is aimed to facilitate the distribution of information from each of the Member States’ business registers to the registers of other Member States in a standard message format and in the relevant language version. JoinUp Webpage: https://joinup.ec.europa.eu/ Core Vocabularies in action: https://joinup.ec.europa.eu/sites/default/files/news/attachment/eu_core_vocabularies_in_action_using_core_business_vocabulary_in_the_eu_.pdf
The application of the once-only principle in all EU Member States public administrations aims at reducing the administrative burden. To achieve this, interoperability between public administrations is a sine qua non condition. Zaragoza's City Townhall using HTML5 exemplifies the promotion of the once-only principle work towards unifying the services offered regardless of the platform. See: https://www.w3.org/2012/12/html5-cr.html.en
'In the Introduction of the documentation, is it explicitly named that in some European Union Member States (Italy, Belgium, etc.) regulation(s) and application(s) are being developed, if not already in place. Also as mentioned in a previous criteria, Italia is using ESI/REM for their own purposes, reference in the following link: REM Services- Criteri di adozione degli standard ETSI- Italy Policy IT: https:// www.agid.gov.it/sites/default/files/repository_files/rem_services_- _criteri_di_adozione_degli_standard_etsi_-_policy_it_1.0_28_maggio_2021.pdf ETSI EN 319 532-3 reference: https://www.etsi.org/deliver/etsi_en/319500_319599/31953203/01.02.01_60/en_31953203v010201p.pdf'
'DNS over HTTPS (DoH) provides protection against unauthorized changes to DNS information by encrypting DNS queries and responses, thereby ensuring the integrity of the data during transmission and preventing DNS spoofing and tampering. However, the HTTPS connection does not provide the response integrity of DNS data provided by DNSSEC. DoH specification: https://datatracker.ietf.org/doc/html/rfc8484'
'BFO is not yet been included in an open repository/catalogue of standards at national level. BFO reference: https://www.iso.org/standard/74572.html'
'The ETSI and any of its committees, in charge of the development of EN 303 645, operates under the ETSI Intellectual Property Rigths (IPRs) and IPR Policy. The specification is licensed on a Royalty-free. IPR Policy, ETSI ownership of IPRs section: https://www.etsi.org/intellectual-property-rights'
'Assessments of the efficiency of this asssessment primarily involve evaluating the performance, scalability, and practicality of implementations. The European Committee for Interoperable Systems wrote a paper in 2016 highlighting how important portability and interoperability is in the cloud computing field. ISO 19941 is mentioned as an example of a cloud solution that vendors can adopt, showing how efficient the specification can be. Special Paper on Cloud Computing - Portability and Interoperability: https://www.ecis.eu/wp-content/uploads/2010/10/ECIS-Special-Paper-on-Cloud-Computing-Portability-and-Interoperability-16-06-27.pdf ISO 19941: https://www.iso.org/obp/ui/en/#iso:std:iso-iec:19941:ed-1:v1:en'
In accordance with Common Patent Policy for ITU-T/ITU-R/ISO/IEC the ISO 32000-1:2008 is licensed under (F)RAND basis and Royalty-free basis. Although there are terms included that allow patent holder to apply specific costs. It is defined in IPR disclosures that can be found at ISO's webpage. See: https://www.iso.org/iso-standards-and-patents.html https://isotc.iso.org/livelink/livelink/fetch/2000/2122/3770791/16231513/2008-04-20_AdobeSystemsIncorporated_32000-1.pdf?nodeid=17314064&vernum=-2
'The specification contains specific requirements regarding the different facets of cloud interoperability and data portability, which can be implemented incrementally or separately, even though it is advisable to implement all of them in order to be aligned with the ISO completely. ISO 19941: https://www.iso.org/obp/ui/en/#iso:std:iso-iec:19941:ed-1:v1:en'
'The ESPD Data Exchange Model (ESPD-EDM) is designed specifically to enable the integration of the eESPD service into national e-procurement solutions and/or pre-qualification services, therfore, facilitating the modelling of e-procurement business processes in each member state that applies it. ESPD business handbook: https://docs.ted.europa.eu/ESPD-EDM/latest/xml_business_handbook.html European single procurement document and eCertis: https://single-market-economy.ec.europa.eu/single-market/public-procurement/digital-procurement/europeansingle-procurement-document-and-ecertis_en'
'Domibus is open-source and can be used and implemented without any restrictions related to (F)RAND principles. Moreover, it is released under the European Union Public License, which entails Royalty-free IPR policies. Domibus specification: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/Domibus'
'OGC-TrainingDML-AI and some other OGC specifications have been found being implemented in the EO2HEAVEN (Earth Observation and ENVironmental modelling for the mitigation of HEAlth risks) project, moreover, the Open Geospatial Consortium (OGC) works globally, including in Europe, to create and promote geospatial data and technology standards. OGC Implementations: https://www.ogc.org/resources/implementations/ Project: EO2HEAVEN (Earth Observation and ENVironmental modelling for the mitigation of HEAlth risks): https://cordis.europa.eu/project/id/244100/reporting OGC TrainingDML-AI Standard: https://docs.ogc.org/is/23-008r3/23-008r3.html'
'With the goal of facilitating a seamless audit trail, XBRL GL is designed to provide an unambiguous linkage from underlying events and activities to reporting information and can therefore be used as necessary to increase visibility and provide greater comfort in the trustworthiness of underlying content. The XBRL specification itself is uniquely designed to provide definitions, descriptions and linkages to regulation, practice and guidance for reported data. XBRL GL Profiles, XBRL Formula, and other rules communication languages, such as ISO Schematron (as leveraged by Turkey) provides a means for those responsible for communicating procedures and requirements in a standardized manner, facilitating “data quality at the front door”. https://specifications.xbrl.org/specifications.html https://www.edefter.gov.tr/edeftermevzuat.html'
'As a standard protocol, DNS helps to ensure interoperability when it comes to define processes for setting internet domain names, thus easing interoperability between devices, applications, data repositories, services and networks, this is why, among other reasons, it appears as one of the setting standards for the "Commission Implementing Decision of 3 April 2014 on the identification of ICT technical specifications eligible for referencing in public procurement" Commission Implementing Decision of 3 April 2014 on the identification of ICT technical specifications eligible for referencing in public procurement : https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32014D0188'
CAMSS Assessment of ELI EIF Scenario v1.0.0
As a protocol for data exchange, HTTPS allows the exchange of information with interfaces of public administration systems.
According to the 5-star Open Data model suggested by Tim Berners-Lee about how to publish linked data, Ogg does not support the main principles for the publication of data as Linked Open Data. Ogg XIPH reference: https://xiph.org/ogg/doc/rfc3533.txt 5-star linked open data: https://www.w3.org/DesignIssues/LinkedData.html
As a protocol which allows the data exchange over the internet, IPv4 contributes to the information and data exchange between administrations. Therefore, avoids the non-digital exchange of data reducing the administrative burden. Additionally, as it is available for free contributes to the reduction of administrative burden.
'The publiccode.yml specification can significantly facilitate the simplification of public administration processes while supporting the digitalisation and modernisation of public services. By establishing a standard for documenting public sector software, it enhances interoperability and encourages reuse among various administrations. This shared framework helps to mitigate administrative complexity, enabling public entities to adopt, adapt, and integrate software more efficiently, thus reducing duplication of efforts and promoting consistency. Consequently, it aids in the seamless delivery of European public services, aligning with the EIF’s objectives for simplification and digital responsiveness. Publiccode.yaml documentation: https://docs.italia.it/italia/developers-italia/publiccodeyml-en/en/master/index.html Italian National Software Catalogue: https://developers.italia.it/ Open CoDE: https://opencode.de/en '
'The purpose of ISO 639-2 is not related to the publication of public data as open data. Therefore, this criterion is not applicable to this specification. ISO 639-2 reference: https://www.iso.org/standard/4767.html Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/en/'
'ELI is in continuous development with the primary goal of facilitating and improving interoperability when exchanging legal documentation among different Member States. Presently, it has already been successfully implemented by 20 countries, including Finland, Italy, Luxembourg, Norway, Portugal, and Spain, with the latter fully incorporating the system, while others are in various stages of partial or ongoing implementation. The ELI documentation includes valuable resources that offer insights into use cases and implementations by various stakeholders, providing visibility and guidance for those engaging with the framework. ELI reference: https://eur-lex.europa.eu/eli-register/about.html ELI Testimonials: https://eur-lex.europa.eu/eli-register/testimonials.html ELI highlights: https://eur-lex.europa.eu/eli-register/index.html ELI Implementation Overview: https://eur-lex.europa.eu/eli-register/implementation.html'
The IPv6 has a 25% of share in internet-connected network advertise. 49 country report 5% of the traffic through IPv6 and 24 countries exceed the 15%. See: https://www.internetsociety.org/resources/2018/state-of-ipv6-deployment-2018/
No formal agreement has been found established between organisations or administrations involved in European public service provision including the usage of PDF 1.7.
XSD is a business domain agnostic specification that can be used at any business domain.
'The implementation of the WAI-ARIA relies on specifications, such as HTML, and also on specialised APIs developed by some operating systems, such as the Microsoft Active Accessibility API. Dependence on these Accessibility APIs is a sign of platform dependence. WAI-ARIA reference, section 1.1: https://www.w3.org/TR/wai-aria/'
"The specification is included in 8 Member States' catalogues of recommended specifications. Some examples of Member States including UDDI on their catalogues are the Netherlands, Spain or Belgium. Joinup reference: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards"
'OpenTelemetry, also known as OTel, is a vendor-neutral open source Observability framework for instrumenting, generating, collecting, and exporting telemetry data such as traces, metrics, and logs. As an industry-standard, OpenTelemetry is supported by more than 40 observability vendors, integrated by many libraries, services, and apps, and adopted by numerous end users. OpenTelemetry Vendors: https://opentelemetry.io/ecosystem/vendors/ OpenTelemetry Integrations: https://opentelemetry.io/ecosystem/integrations/ OpenTelemetry Adopters: https://opentelemetry.io/ecosystem/adopters/'
'The Joinup platform hosts several discussion forums about the implementation and usefulness of JSON regarding technical interoperability aspects and serialization methods. JSON discussion forums in Joinup: https://joinup.ec.europa.eu/search?keys=json&sort_by=relevance&f%5B0%5D=type%3Adiscussion'
'HTTP makes communication between clients and servers better, by establishing the basis for various digital channels, including websites, mobile applications, and APIs. It supports a wide range of content types, such as text, images, audio, and video, enabling public services to deliver diverse forms of digital content effectively. HTTP /1.1 RFC 2616 Reference: https://www.rfc-editor.org/rfc/rfc2616.html HTTP/1.1 Semantics, RFC 9110 Reference: https://www.rfc-editor.org/rfc/rfc9110#name-routing-http-messages'
'The ETSI and any of its committees, in charge of the development of ETSI TS 119 512, operates under the ETSI Intellectual Property Rigths (IPRs) and IPR Policy. The specification is licensed on a (F)RAND basis. ETSI ownership of IPRs section: https://www.etsi.org/intellectual-property-rights'
"A Linked Data Event Stream is a collection of immutable objects described in RDF (such as version objects, sensor observations or archived representations). LDES aims to allow clients to replicate the history of a dataset and efficiently synchronise with its latest changes, it improves the public administration's comprehensibility. LDES specification: https://joinup.ec.europa.eu/collection/semic-support-centre/linked-data-event-streams-ldes"
The implementation of SMTP does not hamper the scalability and interoperability of systems. For example, SMTP allows to synchronize a Smarthost server which helps to synchronize any number of machines so you don't have to configure SMTP on each machine. The Smarthost server will manage all email accounts. Advantages and disadvantages of an SMTP: https://blog.mailrelay.com/en/2017/04/25/what-is-smtp-advantages-and-disadvantages-of-an-smtp-server
The scalability and broad character of the specification can make possible the creation and the availability of solutions fostering the reuse and availability of information between administrations and citizens. This fact demonstrates that the specification can foster the implementation of the once-only principle while ensuring the security and trustworthy data exchanges. SAMM webpage: https://owaspsamm.org/ SAMM Documentation: https://github.com/OWASP/samm/blob/master/Supporting%20Resources/v2.0/OWASP-SAMM-v2.0.pdf
'WSDL itself does not address organizational interoperability agreements directly, it plays a key role in fostering technical interoperability between systems and services. W3C WSDL specification: https://www.w3.org/TR/wsdl20/'
XSLT is publicly available for implementation and study for free on W3C's webpage. See: https://www.w3.org/TR/xslt-30/
'The specification is relevant for administrations and services providers to be compliant with eIDAS. It is recommended and used in several services related to eIDAS compliance. Therefore, it is a clear specification that can be the center of discussions for the improvement of it and the services implementing it. ETSI EN 319 422 reference: https://www.etsi.org/deliver/etsi_en/319400_319499/319422/01.01.01_60/en_319422v010101p.pdf '
As a schema for office documents it is an exchange format that allows sharing information over the internet, including content from the public administrations fostering the visibility of administration data and services. ODF ISO reference: https://www.iso.org/standard/66363.html ODF OASIS reference: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office
'The purpose of ebXML is not related to the delivery of multilingual public services. Therefore, this criterion is not applicable to this specification. ebXML reference: http://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html'
'UTF-8 is not related to the restriction of access to information. Therefore this criterion is not applicable to the specification. UTF-8 specification: https://datatracker.ietf.org/doc/html/rfc3629'
"After having checked different sources, there is no evidence of the existence of studies directly assessing the schema.org specification's efficiency. This contrasts with the fact that there is a large community making use of this specification. Schema.org reference, Community Group and Steering Group section: https://schema.org/docs/about.html Schema.org reference, Additional Resources section: https://schema.org/docs/documents.html"
'ISO/IEC 27001 is an international information security standard that aims to ensure the confidentiality, integrity and availability of the information of an organization and of the systems and applications that treat it. ISO/IEC 27001 reference website: https://www.iso.org/standard/54534.html'
'BFO is still not recommended by a European Member State. BFO reference: https://www.iso.org/standard/74572.html CAMSS list of standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
'Being a software architectural style based on http methods, REST principles can be applied in any case, and therefore, is a resource not subject to royalties or any kind of propietary restrictions. REST reference: https://restfulapi.net/ '
The purpose of SMP seems to not be related to fostering the e-accessibility. Moreover, no information regarding this topic has been found to answer positively or negatively to the criterion. Therefore, this criterion does not apply to this specification. The specification: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505000
"Most of the public administration services use HTTP Cookies to measure site traffic in order to improve its operation and administration and, with the user's consent, to evaluate the performance of government information campaigns and improve user experience, therefore, we can say that HTTP Cookies enables the exposure of interfaces. French government website: https://www.gouvernement.fr/en/coming-to-france HTTP Cookies reference: https://developer.mozilla.org/en-US/docs/Web/HTTP/Cookies#creating_cookies"
'An ebXML RegRep stores any type of electronic content, such as text documents, images, sound or video, and provides a set of protocols enabling data transfer among systems. ebXML is an active asset in the development of The Once-Only Principle Project (TOOP project). Therefore, the specification enables data portability between systems supporting the evolution of European public services. ebXML reference: http://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html TOOP project reference: https://toop.eu/info'
'By allowing communications over the internet, IPv4 contributes to the exchange of information between public administrations. Therefore, it reduces administrative burden. IPv4 IETF: https://www.rfc-editor.org/rfc/rfc791'
JPEG does not define a reusable cross-sector data model, but it defines a standardised manner to deal with images while sharing, creating, or editing. JEPG ISO reference: https://www.iso.org/standard/18902.html JPEG public reference: https://jpeg.org/jpeg/
'The main purpose of TLS 1.3 specification is to enable a secure and trustworthy exchange of data by providing a set of cryptographic mechanisms and protocols that, when implemented and used correctly, enable a very high degree of security for data exchange over a network. TLS 1.3 Cryptographic Negotiation Reference: https://www.rfc-editor.org/rfc/rfc8446.html#section-4.1.1'
'ETSI TS 119 511 is independent of any specification and can be implemented without any dependency on platforms. ETSI TS 119 511 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119511/01.01.01_60/ts_119511v010101p.pdf'
The purpose of SAML 2.0 is not related to the publication of data as Linked Open Data. Therefore, this criterion is not applicable to this specification.
"The majority of web browsers and applications are using TLS 1.3 which offers significant security and performance enhancements over TLS 1.2, including a faster handshake, symmetric encryption, which provides both confidentiality and integrity and streamlined cipher suites (a combination of authentication, encryption, and message authentication code algorithms used to negotiate the security settings for a network connection). Consequently, it is widely adopted by major corporations: AWS uses it in their Application Load Balancer, Google Cloud supports it since 2020, and Microsoft integrates it into SQL Server 2022 and Windows 11. This adoption reflects TLS 1.3's superior security and efficiency. At the time of doing this assessment, there is currently a draft from February 2025 pending to review. This draft aims to refine and improve the existing TLS 1.3 standard, ensuring it remains secure, efficient, and interoperable in the long term. Google Cloud TLS 1.3 Reference: https://cloud.google.com/blog/products/networking/tls-1-3-is-now-on-by-default-for-google-cloud-services Windows TLS 1.3 Support Reference: https://learn.microsoft.com/en-us/sharepoint/security-for-sharepoint-server/tls-support-1.3 AWS Application Load Balancer Reference: https://aws.amazon.com/elasticloadbalancing/application-load-balancer/ TLS 1.3 2025 Draft Reference: https://www.ietf.org/archive/id/draft-ietf-tls-rfc8446bis-12.html TLS 1.3 2018 Reference: https://www.rfc-editor.org/rfc/rfc8446.html"
'The purpose of XSD 1.1 is not related to guaranteeing the authenticity and authentication of the roles agents involved in data transactions. Therefore this criterion is considered not applicable to this specification. XSD Reference: https://www.w3.org/TR/2012/REC-xmlschema11-1-20120405/'
By making legislation open and accessible in a machine-readable format it fosters the creation and delivery of new public services. Moreover, it establishes a standardised terminology to ensure that when legal text or information is translated the nature of the document is not harmed nor modified. ELI reference: https://eur-lex.europa.eu/eli-register/about.html Study on how users of legislation access transposition information: https://eur-lex.europa.eu/content/eli-register/ELI_usability_study_results-final.pdf
'There is no such assessment addressing the efficiency of the specification. This might be due to the early-stage development of the specification. Besides, the ARIA initiative proposes tools and methods to evaluate e-accessibility. In this sense, in the future there might exist such reports. WAI-ARIA github, issue tracking: https://github.com/w3c/aria-practices/issues/ WAI-ARIA reference: https://www.w3.org/TR/wai-aria/'
'There exists assessments addressing the efficiency of the DCAT specification. Referenced Article: https://www.sciencedirect.com/science/article/abs/pii/S1570826818300532'
The purpose of SMTP is not related to long term preservation of electronic records. Therefore, this criterion is considered not applicable to this specification. SMTP IETF reference: https://tools.ietf.org/html/rfc5321
'IEEE Std 802.3-2022 does not directly address relevant data protection policies, but it supports the protection of personal data in public administrations by enabling secure communication protocols for encryption and reliable data transfer. IEEE Std 802.3-2022 Reference: https://ieeexplore.ieee.org/document/9844436'
W3C has a defined and publicly available Process for the Development and approval process of the specification as a recommended standard, including a public review. W3C Process document: https://www.w3.org/2018/Process-20180201/#Policie
XACML is maintained and developed by OASIS which is an international community developing open standards. Developer community OASIS: https://www.oasis-open.org/org/
'UBL design is its support for customization to meet the needs of individual organizations while maintaining complete interoperability within the standard framework. UBL simplifies the delivery of European public services as it provides a universally understood and recoginzed syntax for legally binding business documents, and therefore, reduces the administrative burden. A European Example is the ESPD project. UBL v2.3 reference: http://docs.oasis-open.org/ubl/os-UBL-2.3/UBL-2.3.html ESPD project document: https://docs.ted.europa.eu/ESPD-EDM/3.0.1/xml_technical_handbook.html'
'No member state has been found including BFO in its national catalogue of recommended specifications. CAMSS list of standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
'Schema.org has the W3-schema.org project website, as well as a dedicated platform in Github for sharing results and best practices. Therefore, the specification encourages the creation of open information about the specification and encourages relevant communities from the EU (as well as non-EU communities) to share their results; therefore, this platform also extends at national level. W3 community reference, Important links section: https://www.w3.org/community/schemaorg/ Schema.org-W3 Github, Wiki section: https://github.com/schemaorg/schemaorg/wiki'
'The Advanced Encryption Standard is included in 4 national catalogues of recommended specifications. They belong to Cyprus, Germany, Malta and The Netherlands. The National Interoperability Framework (NIF) of The Netherlands is aligned with at least 3 out of 4 scoreboards of the EIF Monitoring according to the National Interoperability Framework Observatory (NIFO) factsheets. NIFO Factsheets: https://interoperable-europe.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public-administration-factsheets-2024 National Catalogue of Cyprus: https://dits.dmrid.gov.cy/dmrid/dits/dits.nsf/all/B83AA8E4EB4EFD19C225855800288B10/$file/Cyprus%20eGovernment%20Interoperability%20Framework_new%20EIF_v2.0-To%20Publish.pdf National Catalogue of Germany: https://www.cio.bund.de/Web/DE/Architekturen-und-Standards/SAGA/SAGA%205-aktuelle%20Version/saga_5_aktuelle_version_node.html National Catalogue of Malta: https://mccaa.org.mt/Section/Content?contentId=1243 National Catalogue of The Netherlands: https://www.forumstandaardisatie.nl/open-standaarden/lijst AES Standard Reference: https://csrc.nist.gov/pubs/fips/197/final'
PDF/A is an ISO standard and as all ISO standards, they have to be paid to access its content. PDF/A reference: https://www.iso.org/standard/38920.html https://www.iso.org/standard/50655.html
'DNS queries over HTTPS (DoH) encourages collaboration as it was created by IETF, a non-profit and open organisation dedicated to standardisation. For instance, IETF has created discussions lists for their specifications that improve the development and specification of Internet technology through the general discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist. IETF Discussion Lists: https://www.ietf.org/how/lists/discussion'
The purpose of XACML is not related to the long-term preservation of electronic records and other kinds of information. Therefore, this criterion is not applicable to the specification. XACML OASIS reference: http://docs.oasis-open.org/xacml/3.0/errata01/xacml-3.0-core-spec-errata01.html
'Schema.org has been selected for its use to be implemented in existing solutions (see ELI reference) and as a semantic asset in the European Union Location Framework (EULF) project (see JRC repository reference, Architectures and Standards for Spatial Data Infrastructures and Digital Government document). ELI-Joinup reference: https://joinup.ec.europa.eu/collection/eli-european-legislation-identifier/solution/eli-legislation-extension-schemaorg/about JRC repository reference, Architectures and Standards for Spatial Data Infrastructures and Digital Government document: https://publications.jrc.ec.europa.eu/repository/handle/JRC121025 European Union Location Framework (EULF) reference: https://e3p.jrc.ec.europa.eu/publications/european-union-location-framework'
There are no Member States recommending RegOrg in their ICT National Catalogues. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'The YAML is broadly useful for programming needs ranging from configuration files to internet messaging to object persistence to data auditing and visualization. YAML has been used in "Integrated Open Access Materials Modelling Innovation Platform for Europe" project to generate workflows based on a structured YAML data format. YAML specification: https://yaml.org/spec/1.2.2/ "Integrated Open Access Materials Modelling Innovation Platform for Europe" project: https://cordis.europa.eu/project/id/953167'
'CSIP addresses the implementation of authenticity features within information packages. It provides guidance on the documentation of relevant metadata to ensure the authenticity and trustworthiness of digital information. E-ARK CSIP specification: https://earkcsip.dilcis.eu/#introduction'
'Modelling data with RDF-based vocabularies is known to enhance digital public services. An example would be the Core Public Service Vocabulary (CPSV) which is a data model describing public services aiming to enhance interoperability between systems and therefore simplifying the delivery of public services. Core Public Service Vocabulary: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/core-public-service-vocabulary RDF Description services: https://www.w3.org/1999/11/02-RDFServices/'
'After being evaluated compliant with the Regulation on Standardisation 1025/2012, IPsec has been identified by Commission Implementing Decision and included in the European list of ICT Standards for eprocurement. The specification can also be found in the Joinup repository (Interoperable Europe Portal). ICT Technical Specifications: https://single-market-economy.ec.europa.eu/single-market/european-standards/ict-standardisation/ict-technical-specifications_en'
XAdES Baseline profile has been selected within the CEF Digital Signature Service (hereby DSS) along with CAdES, ASiC and PAdES Baseline profiles. Digital Signature Service is an open-source software library for electronic signature creation and validation supporting the interoperability of electronic signatures. The initiative is an enabler for cross borders interoperability between administrations and businesses. See: https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/Standards+and+specifications https://ec.europa.eu/cefdigital/DSS/webapp-demo/doc/dss-documentation.html https://ec.europa.eu/cefdigital/wiki/pages/viewpage.action?pageId=82773260
'Currently OData is not included on any initiative covering privacy aspects. OData reference: https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#_Toc31358832'
'CIM NGSI-LD API is not related to enabling the long-term preservation of data (electronic records included). Therefore, this criterion is considered not applicable to this specification. GS CIM 009: https://www.etsi.org/deliver/etsi_gs/CIM/001_099/009/01.07.01_60/gs_CIM009v010701p.pdf'
'The purpose of DNS is not related with data portability. Therefore, this criterion is not applicable for this specification. DNS IETF reference: https://tools.ietf.org/html/1034 Domain Names - Implementation and Specification: https://tools.ietf.org/html/1035 '
ELI offers many different possibilities for e-Government development focused on the reuse of information across borders reducing administrative burden while fostering collaboration between European public administrations. Since it is based on the European Union and National Knowledge it can be useful when creating eGovernment innovative solutions. ELI reference: https://eur-lex.europa.eu/eli-register/about.html ELI Testimonials: https://eur-lex.europa.eu/eli-register/testimonials.ht ELI highlights: https://eur-lex.europa.eu/eli-register/index.html
'In the specification documentation, there is no reference to the possibility of extension, so it is asumed that it is not possible. CSV reference: https://datatracker.ietf.org/doc/html/rfc4180'
The purpose of SMTP is not related to the implementation of the once-only principle. Therefore, this criterion does not apply to this specification. SMTP IETF reference: https://tools.ietf.org/html/rfc5321
'After checking the different standard catalogues at supra-national level, there is no evidence of the inclusion of OCSP within any European catalogue of standards. ICT technical specifications: https://ec.europa.eu/growth/single-market/european-standards/ict-standardisation/ict-technicalspecifications_ en CENELEC and CEN search tool catalogue: https://standards.cencenelec.eu/dyn/www/f?p=CEN:105::RESET::::'
Not enough information has been found to answer negatively or positively to this criterion. Moreover, it seems that the specification is not aimed to foster the implementation of the once-only principle amongst the European Institutions. Therefore, this criterion is considered not applicable to this specification. ELI reference: https://eur-lex.europa.eu/eli-register/about.html
FTP is included in the ICT national catalogues of the Netherlands and Spain. These Member States comply with at least 4 out of 5 sections of the EIF according to the NIFO factsheets. See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
The purpose of CLV is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification. CLV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-location-vocabulary
"The Better Regulation Toolbox is an internal European Commission resource designed as a complement to the Commission's Better regulation guideline. It provides more specific and operational guidance to those involved with different elements regarding EU legislation, not being possible to be modified but adopted in a manner that aligns with the constraints and needs of the local context.. Better Regulation Guidelines and Toolbox reference: https://commission.europa.eu/law/law-making-process/better-regulation/better-regulation-guidelines-and-toolbox_en Better Regulation Toolbox reference: https://commission.europa.eu/document/download/9c8d2189-8abd-4f29-84e9-abc843cc68e0_en?filename=BR%20toolbox%20-%20Jul%202023%20-%20FINAL.pdf"
'AMQP specification type system defines a set of commonly used types for interoperable data representation. This ensures that data is exchanged in a consistent format, regardless of the underlying system. OASIS AMQP Reference: http://docs.oasis-open.org/amqp/core/v1.0/amqp-core-complete-v1.0.pdf'
'All OpenTelemetry Specification contributions will be licensed under its Apache 2.0 License. It is a permissive license whose main conditions require preservation of copyright and license notices. Contributors provide an express grant of patent rights. Licensed works, modifications, and larger works may be distributed under different terms and without source code. OpenTelemetry License: https://github.com/open-telemetry/opentelemetry-specification/blob/main/LICENSE'
'ISAE 3402 in itself is a method to audit the information systems. As it is available for free it can be used to assess and audit the performance of organisations against the requirements it establishes. ISAE 3402 handbook reference: https://www.ifac.org/system/files/downloads/b014-2010-iaasb-handbook-isae-3402.pdf'
There is no adoption of competing, new European Standards foreseen covering the same area as RPKI.
'The specification has been developed and is currently maintained by the IETF, which means it is not a European standard. UTF-8 specification: https://datatracker.ietf.org/doc/html/rfc3629'
At the time of elaborating this assessment, there is not a direct link to the specification in the European Collaborative Platform, Joinup. However, there is an available extension of OWL2 called OWL 2 Web Ontology Language XML Serialization. OWL2 XML Serialization: https://joinup.ec.europa.eu/solution/owl-2-web-ontology-language-xml-serialization/distribution/owl-2-web-ontology-language-xml-serialization
'The purpose of the specification is not related to the facilitation of modelling business processes, therefore this criterion is not applicable to this specification. ETSI TS 119 614-1 reference: https://www.etsi.org/deliver/etsi_ts/119600_119699/11961401/01.01.01_60/ts_11961401v010101p.pdf'
'There is no evidence of the inclusion of EN 16234-1 e-CF in an open repository/catalogue of standards at European level. EUOS repository of standards: https://www.standict.eu/standards-repository CENELEC and CEN search tool catalogue: https://standards.cencenelec.eu/dyn/www/f?p=CEN:105::RESET::::'
The purpose of FTP is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification.
'There is no evidence of the use of SFIA in any European Cross-border project or initiative. SFIA reference: https://sfia-online.org/en/sfia-8'
'ISO 639-2 helps easing the creation and formalisation of Interoperability agreements. E.g., the Interinstitutional Style Guide (*). Interinstitutional Style Guide reference: https://publications.europa.eu/code/en/en-370200.htm#an1-cand (*) Note that the site refers to ISO 639-1, but actually links to the ISO 639-2 home page.'
'ETSI TS 119 511 is not related to the publication of open data; therefore, this criterion does not apply to the specification. ETSI specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119511/01.01.01_60/ts_119511v010101p.pdf'
XAdES is often adopted as a specification to preserve electronic documents for a long period of time. In the following link there is an example of integrating digital signatures like XAdES in a framework. These facts demonstrate the maturity and market acceptance for its use in the development of products and services. Digital signature service: https://ec.europa.eu/cefdigital/DSS/webapp-demo/doc/dss-documentation.html XAdES ISO reference: https://www.iso.org/standard/56025.html XAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/101900_101999/101903/01.04.02_60/ts_101903v010402p.pdf
'There are existing studies assessing the effectiveness of DNS. Particularly, there seems to be a general interest on the effectiveness of DNS security extension mechanisms, and on the DNS Tunneling tools. Exploring Domain Name-Based Features on the Effectiveness of DNS Caching: https://ccronline.sigcomm.org/wp-content/uploads/2017/01/p36-hao.pdf A Comparative Performance Evaluation of DNS Tunneling Tools: https://www.researchgate.net/profile/Alessio_Merlo/publication/221271469_A_Comparative_Performance_Evaluation_of_DNS_Tunneling_Tools/links/00b4951c1e5065b0e6000000/A-Comparative-Performance-Evaluation-of-DNS-Tunneling-Tools.pdf Performance assessment and analysis ofDNS tunneling tools: https://www.researchgate.net/publication/235996771_Performance_assessment_and_analysis_of_DNS_tunneling_tools A survey of domain name system vulnerabilities and attacks: https://www.researchgate.net/publication/345017736_A_survey_of_domain_name_system_vulnerabilities_and_attacks '
'Following the completion of the research into conformity tests and certifications, a tool has been identified that enables the testing of implementations. The YAML Test Suite repository contains data for testing the correctness of YAML processors. The tests come in two formats. The src directory contains files that encode all the YAML data using YAML. Additionally, the data from these tests is accessible in a format where each test is contained within its own directory. YAML Test Suite: https://github.com/yaml/yaml-test-suite'
There are no existing European standards with market uptake covering the same area with the same level of security as TLS 1.3.
'The purpose of XHTML is not related to the availability of interfaces with internal information systems. Therefore, this criterion does not apply to this specification. XHTML W3C reference: https://www.w3.org/TR/xhtml1/'
SHACL has not been included in any catalogue of standards at national level.
'NUTS designates geographical areas within a legal and institutional framework in which an administrative authority is empowered to take administrative or policy decisions. In this sense, the specification facilitates the modelling of business processes by defining administrative or policy requirements within a legal and institutional framework. EUR-LEX reference, REGULATION (EC) No 1059/2003: https://eur-lex.europa.eu/legal-content/EN/ALL/?uri=CELEX:02003R1059-20180118&qid=1519136753473'
'The purpose of XACML is not related to the long-term preservation of electronic records and other kinds of information. Therefore, this criterion is not applicable to the specification. XACML OASIS reference: https://docs.oasis-open.org/xacml/3.0/xacml-3.0-core-spec-os-en.html'
'SHACL can be effectively used in systems that control access to information or data. In this context, the specification can establish a type of an access control using SHACL-ACL to determine the access to data, and make it more secure. "SHACL-ACL: Access Control with SHACL" study: https://link.springer.com/chapter/10.1007/978-3-031-43458-7_4 SHACL W3C reference: https://www.w3.org/TR/shacl/'
The specification is included in 8 Member States' catalogues of recommended specifications. These Member States are Estonia, France, Germany, Greece, Norway, Poland, Slovenia and Spain. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'By allowing the description of catalogues and datasets, aggregated DCAT metadata can serve as a manifest file as part of the digital preservation process. DCAT Reference: https://www.w3.org/TR/vocab-dcat-2/'
"ISO 3166-1 can enable scope the comprehensibility of administrations when combined with other specifications, notably when referencing to public services' data models and recommendations (see EU Vocabularies reference, Authority tables section). The Core Person Vocabulary recommendation of the Semantic Interoperability Community (Semic) is a clear example of spatial data understanding at European level, as in combination with ISO 3166-1 a person or organisation's identity can be traced in detail. ISO 3166-1 reference: https://www.iso.org/standard/72482.html EU Vocabularies reference, Authority tables section: https://op.europa.eu/en/web/eu-vocabularies/authority-tables EU Seminc Github reference, Core Person Vocabulary, Location section: https://semiceu.github.io/Core-Person-Vocabulary/releases/2.00/?msclkid=7f4a3d0ca9ca11ec99845e3a63e37998#Location"
ODF is a business agnostic document format that can be reused in a cross-domain way. ODF ISO reference: https://www.iso.org/standard/66363.html ODF OASIS reference: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office
'Extensible Forms Description Language is an extension of XML and does not rely on any specific technology. Therefore, it is technology agnostic. Extensible Forms Description Language reference: https://www.w3.org/TR/NOTE-XFDL'
"There can be found many articles and research papers addressing e-procurement and assessing the efficiency and effectiveness of the ESPD in the context of the digilalisation of e-procurement process. A sample of these assessments can be accessed below: Improving Electronic Public Procurement Using the Once-Only Principle: Connecting the Greek Electronic Single Procurement Document System to the Once-Only Principle Project's Infrastructure, Implementing the eProcurement Pilot: https://dl.acm.org/doi/abs/10.1145/3494193.3494226 Employing the Once-Only Principle in the Domain of the Electronic Public Procurement: https://link.springer.com/chapter/10.1007/978-3-030-44322-1_18 E-Procurement in the European Union: https://www.researchgate.net/profile/Sebastian-Bobowski/publication/329322569_EProcurement_ in_the_European_Union/links/5c86d5d392851c831973a589/E-Procurement-in-the-European- Union.pdf Accelerating Transparency and Efficiency in the Public Procurement Sector for a Smarter Society: eNotification and ESPD Integration for Developing E-procurement: https://link.springer.com/chapter/10.1007/978-981-19-3112-3_25"
'The AKN4EU specification is designed to be modular, which means that it allows for partial implementations as it is explained in section 1.1.2.1 (structural mode). This modularity allows implementers to adopt and use only those components of the specification that are relevant to their specific use case or application. AKN4EU reference: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/akn4eu'
'As an Internet Protocol, IPv4 has been adopted by many countries and member states. It is the most widely used protocol for data exchange over the internet. Moreover, it enables the establishment of IP connectivity to a network by assigning an IP address to an interface, which helps to enhance administrative procedures in a comprehensible manner. IPv4 IETF: https://www.rfc-editor.org/rfc/rfc791 IPv4 interfaces: https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ipaddr_ipv4/configuration/xe-3s/ipv4-xe-3s-book/configuring_ipv4_addresses.html#GUID-3D93A3CD-26A6-4128-9573-8A545064F899'
'The Advanced Encryption Standard (AES) was established by the U.S. National Institute of Standards and Technology (NIST) in 2001. The Rijndael submission by Daemen and Rijmen won an open competition organized by NIST in 2000. Then, in 2001, the submission was standardised as AES. However, the first version of the standard began to be discussed in 1997, although its original name was not AES. Since then, all releases have been published. And since its first version, one minor release addressing some formal aspects of the standard document has been launched. NIST AES Reference: https://www.nist.gov/publications/review-advanced-encryption-standard AES Standard Reference: https://csrc.nist.gov/pubs/fips/197/final'
By allowing electronic signatures, the specification helps to avoid the administrative burden related to the non-digital communications. XAdES ISO reference: https://www.iso.org/standard/56025.html XAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/101900_101999/101903/01.04.02_60/ts_101903v010402p.pdf
All the IETF standards are free and open technical specification, built on IETF standards and licenses from the Open Web Foundation._x000D_ _x000D_ See:_x000D_ https://www.ietf.org/rfc/rfc6749.txt
'Extesion mechanisms are provided by ETSI TS 119 512. For example, there can be found preservation-specific extensions for ASiC-related components (see section 5.5) and extensions for other preservation object formats (see section 5.6) ETSI TS 119 512 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.02_60/ts_119512v010102p.pdf '
'XACML is developed by OASIS which is based in the Europe. Therefore, the specification can be regarded as a European Standard. OASIS reference: https://www.oasis-open.org/org/'
'If different systems or apps, even those made by different groups in different European countries, use AES following the technical guide of the standard, they will be able to encrypt data so that other systems using the same guide can decrypt it correctly, and the other way around. AES Standard Reference: https://csrc.nist.gov/pubs/fips/197/final'
'The IPsec specification can use extension headers to secure data exchange. These extension headers allow for data encryption, making it secure when exchanged between users. Moreover, IPsec provides a network layer security for authentication and data encryption. IPSec reference: https://www.rfc-editor.org/rfc/rfc6071.html IPsec data exchange mechanisms: https://www.geeksforgeeks.org/ip-security-ipsec/'
'The EIRA is the basis for the creation of digital public services, and it provides the common and basic components for it, but any Solution Architecture Template or Solution can extend them to ensure that their needs are covered. The Interoperability Architecture Solutions Validator can help to ensure that extensions are aligned with modelling guidelines and requirements of EIRA. Examples of extensions of EIRA are any of the eGovERAs, from the Business Agnostic to the Domain Specific. EIRA reference: https://interoperable-europe.ec.europa.eu/collection/european-interoperability-reference-architecture-eira /solution/eira/release/610 EIRA Github Repository: https://github.com/CarTool-EC/EIRA '
'The purpose of SOAP 1.2 is not related to the delivery of multilingual public services. Therefore, this criterion is not applicable to the specification. SOAP Reference: https://www.w3.org/TR/soap12/ '
"The specification does provide an access control mechanism for the credentials. A credential's repository is a program, such as a storage vault or personal verifiable credential wallet, that stores and protects access to holders' verifiable credentials. This helps minimize the risk of exposing unnecessary information, reducing the potential impact of unauthorized changes or disclosures. Verifiable Credentials: https://www.w3.org/TR/vc-data-model/ "
'The ESPD Github repository hosts all feedback given by stakeholders. As it is stated in the ESPD release notes, changes and updates of the specification are carried out following Member States and stakeholders comments in the Github repository issues workspace. ESPD Issues in Github: https://github.com/OP-TED/ESPD-EDM/issues ESPD release notes: https://docs.ted.europa.eu/ESPD-EDM/latest/release_notes.html'
'IPsec is a set of open standards and protocols for securing the exchange of data packets over a computer network, including data confidentiality, integrity, origin authentication and anti-replay. However, there is no specific provision to this end. IPSec reference, Where Can IPSec Be Implemented: https://datatracker.ietf.org/doc/html/rfc4301#page-11'
'The specification enable the processing of data but not its security. To cover security aspects or issues, it is possible to enable external mechanisms like encryption or implementing security mechanisms on the systems processing the YAML data. YAML specification: https://yaml.org/spec/1.2.2/'
'Syslog has published documentation regarding change management (section 6.3.4) and release management following the IETF internet standards process. The process of creating a standard under IETF is clear: a specification undergoes a period of development and several iterations of review by the Internet community and revision based upon experience are taken place. Furthermore, The IETF welcomes the critical evaluation of protocols and has provided guidance for it. Syslog Protocol Change Control: https://datatracker.ietf.org/doc/html/rfc5424#section-6.3.4 Standard process IETF: https://www.ietf.org/standards/process/ Protocol Vulnerabilities IETF: https://www.ietf.org/standards/rfcs/vulnerabilities/'
The specification is included in 8 Member States' catalogues of recommended specifications. Some examples of Member States including CSV on their catalogues are the Netherlands, Slovenia or Sweden. See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'ELI is a European Specification developed for its common reuse and to foster the shareability of legal document across borders. It is used within the EU Open Data Portal for the provision of data sets described using the main requirements established by ELI. Doing so, European institutions, businesses and citizens can access and reuse it in a machine-readable format. Moreover, since ELI was developed taking Common Data Model (CMD) from the OP and the implementations require to be compliant with it, it ensures that the content is available from CELLAR, which is an access point to all the open data generated by the Publications office. ELI reference: https://eur-lex.europa.eu/eli-register/about.html ELI technical Information: https://eur-lex.europa.eu/eli-register/technical_information.html EU Open Data Portal Data sets: https://data.europa.eu/euodp/en/data/group/eli?groups=eli'
The purpose of CAdES is to foster the use of electronic signature. Therefore, it is clear that it reduces the administrative burden by making signing possible electronically. CAdES ISO reference: https://www.iso.org/standard/64756.html CAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/101700_101799/101733/02.01.01_60/ts_101733v020101p.pdf
FTP is an internet protocol for the exchange of data over an Internet network. It supports the first level of maturity defined in the Tim Berners-Lee´s 5 stars Open Data deployment scheme, "Make your data accessible on the web". See: https://www.w3c.es/Eventos/2013/Uruguay/Presentaciones/W3CdayMVD_LOD_LorenaEtcheverry2013.pdf
'The Extensible Forms Description Language specification can enable e-accessibility by its XML structure. In this context, the specification allows to structure data in a consistent, predictable way that can be easily interpreted and processed. Extensible Forms Description Language reference: https://www.w3.org/TR/NOTE-XFDL'
'Domibus can be integrated into the flow of business processes where secure communication and data exchange are required. Moreover, Domibus can perform data transformation as part of the message exchange process. It can help ensure that data exchanged between systems aligns with the requirements of the business processes involved. Domibus specification: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/Domibus'
The Semantic Interoperability Community (SEMIC) develops solutions to help European public administrations perform seamless and meaningful cross-border and cross-domain data exchanges. They develop semantic specifications and interoperability solutions under the ISA² Programme. When a new solution release is finished, it is submitted for a public review with a minimum period of four weeks. Specification development process by the ISA Programme: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/document/description-change-management-release-and-publication-process-structural-metadata-specifications Detailed document ISA Programme: https://joinup.ec.europa.eu/sites/default/files/document/2016-10/description_of_a_change_management_release_and_publication_process_for_structural_metadata_specifications_developed_by_the_isa_progr.pdf
'DCAT-AP has not been found included in any European or national initiative covering privacy aspects. DCAT-AP Specification: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/dcat-application-profile-data-portals-europe/release/200'
'Publiccode.yml is included in the Italian repository for public documents, which includes standards and specifications. The repository in not explicitly dedicated to standards and specifications, but was created to be a reference. Therefore, this can be considered and official and feasible source. Moreover, the specification has serve as the basis for the creation of the Italian Catalogue of Software. Publiccode.yaml documentation: https://docs.italia.it/italia/developers-italia/publiccodeyml-en/en/master/index.html'
This document does not define a cross-sector reusable data model, but it defines a Best Practices on how to publish data on the web. W3C Reference: https://www.w3.org/TR/dwbp/
'The purpose of IPsec is not related to e-accessibility. Therefore this criterion is considered not applicable to this specification. IPSec reference, What IPSec Does: https://datatracker.ietf.org/doc/html/rfc4301#page-7'
'The Advanced Enryption Standard allows implementations to support at least one of the three key lengths, established by the standard guide. A "key length" refers to the size of the cryptographic key used to encrypt and decrypt data, measured in bits. In this context, the standard allows optional support for two or three key lengths, but it's not required to support all three. AES Standard Reference: https://csrc.nist.gov/pubs/fips/197/final'
This Core Vocabulary Application Profile offers the possibility of describing public services in a standarised way easing their reuse and discoverability. It can be translated into Federated Catalogues of Public Services that can be accessed across-borders. As the "Evaluation Study supporting the interim evaluation of the programme on interoperability solutions for European public administrations, businesses and citizens (ISA²)" states, there are several MS like Italy or Finland that are using CPSV-AP to create Public Services Catalogues. JoinUp Webpage: https://joinup.ec.europa.eu/ Evaluation Study supporting the interim evaluation of the programme on interoperability solutions for European public administrations, businesses and citizens (ISA²): https://www.ceps.eu/wp-content/uploads/2019/06/NO0119341ENN.en_.pdf
'No evidences have been found of existing studies or documentation assessing HTTP Cookies in terms of effectiveness to justify this criterion. HTTP Cookies reference: https://datatracker.ietf.org/doc/html/rfc6265#section-1'
'The Transformational Government Framework (TGF) is technology-agnostic, meaning it does not promote nor endorse any specific technology or vendor solution. Instead, it provides guidance and best practices for the design and delivery of government services using open standards and interoperability principles. TGF specification: http://docs.oasis-open.org/tgf/TGF/v2.0/cs01/TGF-v2.0-cs01.html'
DCAT-AP, as a cross-border and cross-sector vocabulary increases government-to-government reuse of data and therefore can prevent citizens or businesses from providing standard information several times. Like all common vocabularies, DCAT-AP facilitates the implementation of the once-only principle. See: https://ec.europa.eu/isa2/dcat-ap-key-european-data-publishers-reach-data-consumers-and-create-european-open-data-ecosystem_en
SHACL can describe the interoperability aspects of the Data Validation Service or Data Validation Component ABBs from EIRA's Technical View.
'7 Member States are recommending IPv6 in their ICT National Catalogues. This Member States are Austria, Croatia, France, Germany, Netherlands, Norway and Sweden. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
'SFIA is a framework that is not aligned to any specific technology, provider or industry. Therefore, the specification is technology agnostic. SFIA reference: https://sfia-online.org/en/sfia-8'
'No formal agreements have been found established between organisations or administrations involved in European public service provision including the usage of WAI-ARIA. ICT Technical Specifications reference: https://ec.europa.eu/growth/single-market/european-standards/ict-standardisation/ict-technical-specifications_en'
The W3C Royalty-Free IPR licenses granted under the W3C Patent Policy apply to all W3C specifications, including SOAP 1.2. WS-Security is a an extension of SOAP 1.2 it can be considered that is royalty-free basis. See: https://www.w3.org/TR/patent-practice#ref-AC
'The specification is currently implemented in several initiatives in the public sector. This is a key point that reflects the market acceptance of the specification by the public administrations and institutions in Europe. Some implementations of the ADMS are Metadata Registry (MDR), ADMS-enabled description of a vocabulary implemented in PoolParty Thesaurus Manager 3.1.0, and the Implementation for the XRepository of the German Federal Ministry of the interior. ADMS in Joinup: https://joinup.ec.europa.eu/solution/asset-description-metadata-schema-adms/about'
'The Core Criterion and Core Evidence Vocabulary is designed to support the exchange of information between organisations or persons (more generally Agents) defining Requirements and organisations or persons responding to these Requirements by means of structured or unstructured Evidences. The specification also uses codelists which are a valuable feature to provide authentication. Core Criterion and Core Evidence Vocabulary reference (v1.0.0): https://joinup.ec.europa.eu/release/core-criterion-and-core-evidence-vocabulary-v100 '
The purpose of XML is to store, transport and exchange data through interoperable systems. Moreover, XML defines a set of rules for encoding documents in a human-readable format and machine-readable format enhancing the reusability of data and stimulating the interoperability of systems and services. Additionally, W3C develops its specification independently from any vendor. Thus, the adoption of XML does not hamper the data portability of data expressed with it. In fact, the adoption of XML fosters data portability, especially between REST APIs. See: https://www.w3.org/TR/2006/REC-xml11-20060816/
The purpose of PDF/A is not related to the delivery of multilingual public services. Therefore, this criterion is not applicable to this specification. PDF/A reference: https://www.iso.org/standard/38920.html https://www.iso.org/standard/50655.html
The implementation of the Core Location Vocabulary can enhance and foster the provision of digital services, avoiding the non-digital document exchange. CLV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-location-vocabulary
'CPSV-AP is included in the SEMIC community in Joinup. The Semantic Interoperability Community (SEMIC) develops solutions to help European public administrations perform seamless and meaningful cross-border and cross-domain data exchanges. CPSV-AP Joinup webpage: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/core-public-service-vocabulary-application-profile/release/22 SEMIC working groups: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/about'
The standard for Public Code gives public organizations a model for building their open source solutions to enable successful future reuse by similar public organizations in other places. The open-source for public code can, therefore, be considered as an asset in the creation of innovative solutions. The reusability and capacity to adapt and develop in such different ways ensure its reusability improving the effectiveness and efficiency. The Standard for Public Code webpage: https://standard.publiccode.net/
Although at the moment of elaborating the assessment, the specification is widely used, the specification in itself does not foster the creation of innovative solutions. JEPG ISO reference: https://www.iso.org/standard/18902.html JPEG public reference: https://jpeg.org/jpeg/
'ISO 3166-1 is intended to identify a country, dependencies and special areas of geographical interest. There is no possibility to extend the coding system as ISO 3166-1 was conceived for a unique purpose. ISO 3166-1 reference: https://www.iso.org/standard/72482.html '
'ETSI TS 119 512 has been developed by the European Telecommunication Standards Institute (ETSI), an independent, not-for-profit, standardization organization in the field of information and communications. About ETSI: https://www.etsi.org/about/about-us'
'The ETSI IPR Policy which is part of the ETSI directives seeks to reduce the risk that our standards-making efforts might be wasted if SEPs are unavailable under Fair, Reasonable and Non-Discriminatory (FRAND) terms and conditions. The main objective of the ETSI IPR Policy is to balance the rights and interests of IPR holders to be fairly and adequately rewarded for the use of their SEPs in the implementation of ETSI standards and the need for implementers to get access to the technology defined in ETSI standards under FRAND terms and conditions. ETSI’s intellectual property rights policy: https://www.etsi.org/intellectual-property-rights'
"Access to the Indexed Database API is controlled by the browser's security mechanisms. For example, scripts can only access the Indexed Database API if they are from the same origin/domain. This prevents unauthorised cross-origin access to the stored data. Indexed Database API: https://www.w3.org/TR/IndexedDB/"
'Genericode, being a flexible and modular standard, allows for partial implementations based on specific use cases and requirements. Its modular structure allows developers to implement only the components that are necessary for their particular use case. For example, if an application only needs to represent simple code lists without metadata, it can choose to implement only the core elements of Genericode without incorporating metadata-related features. Code List Representation (genericode): https://docs.oasis-open.org/codelist/genericode/v1.0/os/genericode-v1.0-os.html'
XML is used by XML Gate, the EU DG SANCO single entry point for Member States submissions of structured data in XML format via web services. See: https://webgate.ec.europa.eu/sanco-xmlgate/Login.jsp
'The specification has a section dedicated to conformance. Conformance requirements are expressed with a combination of descriptive assertions and RFC 2119 terminology. The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in the normative parts of this document are to be interpreted as described in RFC 2119. However, for readability, these words do not appear in all uppercase letters in this specification. Furthermore, Interoperability Test Bed (ITB) can also be used to test LDES. LDES GitHub: https://semiceu.github.io/LinkedDataEventStreams/#conformance RFC 2119: https://datatracker.ietf.org/doc/html/rfc2119 ITB LDES: https://joinup.ec.europa.eu/collection/interoperability-test-bed-repository/solution/interoperability-test-bed/news/itb-support-digital-flanders'
After being evaluated compliant with the regulation on standardisation 1025/2012, LDAPv3 has been identified by Commission Implementing Decision and included in the European list of ICT Standards for e-procurement. ICT technical specifications: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en
SAML 2.0 is available for its study and use at OASIS’s webpage. Therefore it can be reused by the organisations, administrations, open communities, etc. that developed it. See: http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-tech-overview-2.0.html
UTF-8 is included in 2 national catalogues of recommended specifications, concretely of the Netherlands and Sweden. The National Interoperability Framework (NIF) of these Member States is fully aligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards https://joinup.ec.europa.eu/collection/national-interoperability-framework-observatory-nifo/nifo-factsheets
'By providing information about quality data sets, DQV can help avoid administrative burden. Although it is not a unique quality version, it can offer a first impression of it, and it can be useful to obtaining information about the quality of datasets. DQV reference: https://www.w3.org/TR/vocab-dqv/'
'To be able to make access control related decisions that are based on reliable identities and properties of Participants, a concept for Identity and Access Management (IdAM) is mandatory. The primary means for controlling access in SCIM are based on authentication and authorization mechanisms. SCIM: https://scim.cloud/'
'OSI has been included in an open repository/catalogue of standards at European level, the Interoperable Europe Portal. This specification is included in the solutions catalogue of ICT Standards for Procurement created by the European Commision. The European Catalogue will contribute to these objectives by offering a one-stop shop for procurers on guidelines for procurement, including on vendor lock-in, on the use of standards, and a lifecycle costing scheme that accounts for the often neglected interoperability costs. OSI on the Interoperable Europe Portal https://interoperable-europe.ec.europa.eu/collection/ict-standards-procurement/solution/isoiec-7498-11994-information-technology-open-systems-interconnection-basic-reference-model-basic ICT Standards for Procurement: https://joinup.ec.europa.eu/collection/ict-standards-procurement OSI reference https://www.iso.org/standard/20269.html'
'E-ARK CSIP is already mapped into the EIRA Library of Interoperability Specifications (ELIS). More specifically, it can define the interoperability aspects of the "e-archiving component" and "e-archiving service", ABB from the ERIA Technical Application poit of view. ELIS reference: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /solution/elis/release/v501'
'ETSI TS 119 612 main focus is not to ensure the protection of personal data, but it ensures the establishment, location, access and authentication of a trusted list that may contain personal data, so indirectly it does ensure it. ETSI TS 119 612 specification: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf'
'The XFDL specification might rely on specialised software such as IBM Forms to transform XFDL files into other formats such as PDF and HTML. XFDL files format: https://www.lifewire.com/xfdl-file-2622489#:~:text=A%20file%20with%20the%20XFDL%20file%20extension%20is,way%20to%20create%20secure%20and%20legal%20electronic%20forms. Extensible Forms Description Language reference: https://www.w3.org/TR/NOTE-XFDL'
The purpose of ODF is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification. ODF ISO reference: https://www.iso.org/standard/66363.html ODF OASIS reference: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office
'No Member States have been found recommending DAPS in their ICT National Catalogues. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards'
'Accessibility in the context of this DCAT-AP is limited to information about the technical format of distributions of datasets. The properties dcat:mediaType and dct:format provide information that can be used to determine what software can be deployed to process the data. The accessibility of the data within the datasets needs to be taken care of by the software that processes the data and is outside of the scope of this Application Profile. DCAT-AP Specification: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/dcat-application-profile-data-portals-europe/release/200'
The Core Location Vocabulary allows managing cross-border repositories of public services and organisations. So, it fosters data portability between systems and applications supporting the implementation and evolution of European public services. CLV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-location-vocabulary
'The XACML specification provides a robust framework for implementing access control mechanisms, like fine-grained access control by enabling policies that specify precise conditions under which access is granted or denied. Moreover, XACML enables organisations to enforce secure and consistent access control across their applications and resources. XACML OASIS reference: https://docs.oasis-open.org/xacml/3.0/xacml-3.0-core-spec-os-en.html'
"Schema.org contains a specific vocabulary that can be used in applications that publish, discover or integrate different types of data. That is, not only does it provide schemas for describing collections of structured data, but also the specification's capability complements many other data-related formats and standards which facilitates organisational interoperability agreements. Schema.org reference, Data and Datasets overview section: https://schema.org/docs/data-and-datasets.html"
The rules on European standardisation allow the European Commission to identify information and communication technology (ICT) technical specifications - that are not national, European or international standards - to be eligible for referencing in public procurement. This allows public authorities to make use of the full range of specifications when buying IT hardware, software and services, allowing for more competition in the field and reducing the risk of lock-in to proprietary systems. After being evaluated compliant with the regulation on standardisation 1025/2012, XML has been identified by Commission Implementing Decision. During the evaluation process, all the Member States are invited to share their doubts. The positive evaluation of XML and its identification is considered an interoperability agreement. See: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en
'IPv4 is the previous version of the Internet Protocol, but it is widely adopted and still prevailing. The newest has specific features and improves security aspects. Thus, it is not dependent of any specific technology and the adoption of IPv4 does not hamper the interoperability. IPv4 IETF: https://www.rfc-editor.org/rfc/rfc791'
'The purpose of ISO 19941:2017 is not related to e-accessibility. Therefore, this criterion is considered not applicable to this specification. ISO 19941: https://www.iso.org/obp/ui/en/#iso:std:iso-iec:19941:ed-1:v1:en'
IPv6 is maintained and developed by IETF which is an international community developing open standards Moreover, the deployment of IPv6 is rapidly expanding in the Internet. Support for IPv6 in applications is lagging behind and endorse such as Apple are taking steps to rectify this situation and raise awareness to the problem. See: https://www.ietf.org/about/ https://community.cisco.com/t5/jive-developer-archive-documents/ipv6-for-application-developers-whitepaper/ta-p/3647032
'The purpose of UBL is not related to te secure exchange of data. Therefore this criterion is not applicable to this specification. UBL v2.3 reference: http://docs.oasis-open.org/ubl/os-UBL-2.3/UBL-2.3.html'
XHTML is publicly available for implementation and use for free on W3C's webpage. Therefore, it can be reused by the organisations, administrations, open communities, etc. that developed it. XHTML W3C reference: https://www.w3.org/TR/xhtml1/
Time-Stamp Protocol (TSP) was defined in 2001 and is a cryptographic protocol for certifying timestamps using X.509 certificates and public key infrastructure. Therefore, it is demonstrated that TSP has enough maturity for its use in the development of products and services. TSP IETF reference: https://tools.ietf.org/html/rfc3161
'TOSCA does not impose the use of any specific mechanism or technology for enabling data portability; data portability aspects should be obtainable by the user infrastructure. TOSCA reference: https://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.3/os/TOSCA-Simple-Profile-YAML-v1.3-os.html'
DNS is recommended by 7 Member States. See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
The fact that the specification is documented in several IETF request for comments (RFCs) since 2012 and that it has been widely and successfully implemented is evidence that the specification is stable and sufficiently developed for the development of products and services.
'No Member State includes GraphQL in their national catalogue with Their National Interoperability Framework (NIF) in alignment with the three categories 1. Conceptual model for integrated public servicesprovision, 2. interoperability layers, and 3. interoperability principles. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards'
'The purpose of genericode is not related to providing means for restriction of access to data. Therefore, this criterion is considered not applicable to this specification. Code List Representation (genericode): https://docs.oasis-open.org/codelist/genericode/v1.0/os/genericode-v1.0-os.html'
Although no formal agreements have been found on the usage of TIFF, there are different projects and initiatives at European level, that use TIFF files for the data exchange. Some examples of Agencies and projects involving the specification are the European Environment Agency and its Evaluation map of Europe, which is available on TIFF format. Also, the initiative founded by the European Commission, OpenAire, which is aimed to foster cooperation among researchers over Europe and the discoverability of their data. This initiative defines guidelines for data management in the context of H2020 Programme: Guidelines on FAIR Data Management in Horizon 2020. OpenAire Preservation Guidelines: https://www.openaire.eu/data-formats-preservation-guide Elevation Map of Europe: https://www.eea.europa.eu/data-and-maps/data/digital-elevation-model-of-europe Digital Elevation Model over Europe: https://www.eea.europa.eu/data-and-maps/data/eu-dem
6 Member States are recommending IPv6 in their ICT National Catalogues. See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'Web Services Description Language (WSDL) itself primarily focuses on describing the interfaces and operations of web services, and it does not provide specific mechanisms for ensuring the secure processing of data. Security considerations, including secure processing, are typically addressed at other layers of the web services architecture and are influenced by the implementation choices made by service providers and consumers. W3C WSDL specification: https://www.w3.org/TR/wsdl20/ '
'The syslog protocol encourages collaboration in the field of message logging as it was created by IETF, a non-profit and open organisation dedicated to standardisation. IETF encourages collaborative efforts that extend beyond the specifications themselves and include discussions, forums, and knowledge-sharing platforms where users can exchange ideas, experiences, and best practices related to syslog. For instance, IETF has created discussions lists for their specifications that improve the development and specification of Internet technology through the general discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist. Syslog Protocol: https://datatracker.ietf.org/doc/html/rfc5424'
'OGC Training DML-AI has been found included in the 2024 ICT Rolling Plan standards catalogue. More specifically in the Smart and sustainable cities and communitiessection, where it appears as one of the geospatial standards underpinning the INSPIRE (Infrastructure for Spatial Information in the European Community) directive and CityGML, an international standard for spatial data exchange. ICT Rolling plan 2024: Smart sustainable cities and communities: https://joinup.ec.europa.eu/collection/rolling-plan-ict-standardisation/smart-and-sustainable-cities-and-communities-rp2024'
IPv4 is included in 2 national catalogues, which belong to Member States which comply with at least 4 out of 5 sections of the EIF according to the NIFO factsheets. These two Member States are the Netherlands and Sweden. See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards https://joinup.ec.europa.eu/collection/national-interoperability-framework-observatory-nifo/nifo-factsheets
Like all the IETF standards, UTF-8 is a free and open technical specification, built on IETF standards and licenses from the Open Web Foundation. DNS is therefore licensed on a royalty-free basis. See: https://tools.ietf.org/html/rfc3629 https://trustee.ietf.org
HTTPS is available on Joinup, the collaborative platform for Reusable IT Solutions funded by the European Commission. See: https://joinup.ec.europa.eu/solution/http-rfc-2616-hypertext-transfer-protocol
'One mitigation against unauthorized changes to a DID document is monitoring and actively notifying the DID subject when there are changes. This is analogous to helping prevent account takeover on conventional username/password accounts by sending password reset notifications to the email addresses on file. In the case of a DID, there is no intermediary registrar or account provider to generate such notifications. However, if the verifiable data registry on which the DID is registered directly supports change notifications, a subscription service can be offered to DID controllers. Notifications could be sent directly to the relevant service endpoints listed in an existing DID. DIDs data integrity W3C: https://w3c.github.io/did-core/#notification-of-did-document-changes'
'The specification is developed as a common interface. XBRL GL facilitates the publication of open data in many ways. A primary goal of open data is that it be usable, and usability is enhanced by reliability. As an important facilitator of a seamless audit trail, XBRL GL is able to represent data from initial source events, activities or documents through to summarization. As such, it can represent data at any level of detail, and standardize the communication of data appropriate to be open. XBRL GL provides a single framework for information both quantitative and qualitative related to business reporting at any level of detail. In conjunction with any standardized code sets, it provides a single structure for expressing the representation of data. '
'The W3C Verifiable Credentials specification allows for customization to a certain extent. This means that users can tailor the structure of the credentials to their specific needs. For example, if they are dealing with educational credentials, they might define a credential type specific to educational achievements. Verifiable Credentials: https://www.w3.org/TR/vc-data-model/'
'DNS appears in Joinup as one of the identified ICT specifications for procurement. Joinup ICT standards for procurement: https://joinup.ec.europa.eu/collection/ict-standards-procurement/identified-ict-specifications-procurement'
'ETSI TS 119 512 is part of the Electronic Signatures and Infrastructure (ESI) family of specifications, and is dependent on some of their protocols and semantics they convey, therefore, this specification is not technology agnostic. ETSI TS 119 512 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.02_60/ts_119512v010102p.pdf'
No evidence has been found of the specification being included in an interoperability agreement between organisations involved in the European public services provision.
'ISO 639-2 is intended to serve as a device to identify a language name. Users might mix different ISO 639 collections or create tailored code suites from this specification depending on their needs, but there does not exist any partial implementation as such. ISO 369-2 FAQs: https://www.loc.gov/standards/iso639-2/faq.html#7 SIL reference: https://iso639-3.sil.org/about/relationships'
'ISO/IEC 19944-1 has not been found included in the National Catalogue of recommended specifications of any Member State. CAMSS List of standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards'
'It could serve as a valuable facilitator of European organizational agreements regarding geospatial data by providing a common framework for data management and exchange. This support can help reduce barriers to interoperability and promote collaboration among entities involved in geospatial data processing. Additionally, integrating machine learning capabilities within this framework could further enhance data analysis, decision-making, and innovation in geospatial applications across Europe. OGC TrainingDML-AI: https://www.ogc.org/standard/trainingdml-ai/ OGC TrainingDML-AI Implementations: https://github.com/opengeospatial/TrainingDML-AI_SWG/tree/main/Implementations'
'The Core Location Vocabulary specification provides classes to describe elements, such as geometries, which can be understable by different languages. In this sense, this vocabulary describes other information, such as administratives territorial units, or times, whih are defined in codes and numbers, making them understable in any language. Core Location Vocabulary: https://interoperable-europe.ec.europa.eu/collection/semic-support-centre/solution/core-location-vocabulary/release/100'
CAMSS Assessment of XSD EIF Scenario v1.0.0
W3C has a defined and publicly available Process for the Development and the approval process of the specification as a recommended standard. Also, a clear Release Notes tracking the changes of the different versions is archived. W3C Process document: https://www.w3.org/TR/xslt-30/
'While genericode itself does not provide mechanisms for protecting information against unauthorised changes. Organizations can implement various measures to protect information against unauthorised changes which are included in genericode. Genericode supports the inclusion of metadata alongside code values, providing additional context and information. This metadata enhances the semantic clarity of the codes and ensures data integrity. Code List Representation (genericode): https://docs.oasis-open.org/codelist/genericode/v1.0/os/genericode-v1.0-os.html'
'The Interoperability Test Bed Team of DIGIT D.2. foresees the maintenance of the GITB software and specification based on the needs of the testing community and carries out evolutive maintenance with regular releases. In addition, the Test Bed team always prioritises user feedback for its change management. There is an open email whom anyone can address to propose a new issue or report a problem. JOINUP reference: https://joinup.ec.europa.eu/collection/interoperability-test-bed-repository/solution/interoperability-test-bed/detailed-information#releases GITB TDL reference: https://www.itb.ec.europa.eu/docs/tdl/latest/introduction/index.html#how-is-it-maintained '
ASiC Baseline Profile is not directly related to the long-term preservation of electronic records or other items. Despite this, according to its purpose of ease the signed data, ASiC Baseline Profile has three level of conformance and the last one is the Long-Term Profile. In the case of the assessed specification, it does not include the profile in itself but invokes the requirements from CAdES and XAdES. Therefore, it helps to ensure the availability of electronic signatures over long time periods, easing interactions between administrations and stakeholders.
The purpose of UDDI is not related to organisational interoperability. Therefore, this criterion is not applicable to the specification.
'This specification is mentioned in the European Union Agency for Cybersecurity (ENISA) 2022 study about Digital Identity. OpenID is an open standard and decentralised authentication protocol and FastFed WG33 is one of its working groups, whose purpose is to develop a meta-data document specification, APIs, and workflow to enable an administrator to federate an identity provider and a hosted application that supports one or more of OpenID Connect, SAML, and SCIM and enable configuration changes to be communicated between the identity provider and hosted application. ENISA Digital Identity: https://www.enisa.europa.eu/publications/digital-identity-leveraging-the-ssi-concept-to-build-trust'
'After searching in different catalogues, there is no evidence found of ETSI TS 119 612 being included in the catalogue of any Member State. ETSI TS 119 612: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf'
'ADMS is a vocabulary based on DCAT for the description of Assets, specifically interoperability solutions). In this sense, the ADMS helps the publication and reusability of solutions and their data. ADMS on Joinup: https://joinup.ec.europa.eu/solution/asset-description-metadata-schema-adms/about ADMS Specification W3C: https://www.w3.org/TR/vocab-adms/'
'Syslog itself is not designed for the purpose of facilitating the publication of data on the web. Syslog is a standard protocol used for the collection and forwarding of log messages from various devices, applications, and systems in a network. It is commonly used for system management and security auditing. Syslog Protocol: https://datatracker.ietf.org/doc/html/rfc5424'
'The purpose of XHTML is not related to long term preservation of electronic records. Therefore, this criterion is considered not applicable to this specification. XHTML W3C reference: https://www.w3.org/TR/xhtml1/'
"HTTPS cannot be partially implemented. HTTPS is a holistic security protocol that ensures end-to-end encryption and secure communication between a user's web browser and a website or web application. It is an all-or-nothing approach, meaning that once HTTPS is implemented, it applies to the entire website or application. HTTPS specification: https://tools.ietf.org/html/rfc2818"
'The purpose of XSLT is not related with enabling digital service delivery channels. Therefore this criterion is considered not applicable specification. XSLT Reference: https://www.w3.org/TR/xslt-30'
'Although OAIS is not directly related to security issues, annex F from the specification provides some guidelines for the secure processing of data such as the CCSDS general guidance for security considerations found in the Informational Report "The application of CCSDS Protocols to Secure Systems". OAIS specification: https://public.ccsds.org/Pubs/650x0m2.pdf Application of CCSDS Protocols to Secure Systems: http://mtc-m16c.sid.inpe.br/col/sid.inpe.br/mtc-m18@80/2009/07.16.19.31/doc/CCSDS%20350.0-G-2.pdf'
'Domibus has an active and engaged community that provides support, contributions, and collaboration to the project. Domibus is an open-source software solution developed and maintained by a community of users, developers, and contributors who are interested in secure electronic message exchange and interoperability. eDelivery Developers community: https://ec.europa.eu/digital-building blocks/wikis/display/DIGITAL/eDelivery+Developers+Community+management Domibus specification: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/Domibus'
'The message formating may vary, depending on the transport method used (HTTP, SMTP, LDAP, etc.). Therefore, a response may include information on the revocation status of certificates that were not included in the request, so this protocol can be customised. OCSP reference, sections 1 and 4.2: https://datatracker.ietf.org/doc/html/rfc2560'
'By creating a standardized taxonomy for data privacy concepts and terms, the DPV is enabling the exposure of interfaces as it is intended to enhance semantic interoperability about personal data processing and enable data portability for data subjects. DPV specification: https://w3c.github.io/dpv/dpv/ DPV primer document: https://w3c.github.io/dpv/primer/#introduction '
The purpose of W3C Best Practices is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification. W3C reference: https://www.w3.org/TR/dwbp/
The purpose of UDDI is not related to the delivery of multilingual services. Therefore this criterion is not applicable to this specification.
'ISO 639-2 does not encourage the creation of communities nor promotes the sharing of data and results in any European platform. The Library of Congress reference: https://www.loc.gov/standards/iso639-2/'
'UDDI allow publishers to restrict access to logs. It is possible to enable the WebSphere Application Server to obtain more security, especially in the areas of data authorization and confidentiality in a UDDI registry. Using WebSphere Application Server, UDDI can classify users into two groups: one in which all users have access and another in which only users authenticated to WebSphere Application Server have access. On the other hand, at UDDI it is also possible to register privately. IBM security reference: https://www.ibm.com/docs/en/was/8.5.5?topic=curs-configuring-uddi-registry-use-websphere-application-server-security'
'The widespread adoption and use of the ESPD in public procurement processes, along with its integration into e-procurement platforms and tools, suggests that it has sufficient market acceptance for its use in the development of digital solutions. Moreover, The use of the ESPD has been mandated by the EU for all public procurement procedures since 2018, which has helped to increase its adoption and acceptance in the market. In addition, the ESPD has been integrated into several e-procurement platforms and tools, which demonstrates its suitability for use in digital solutions. ESPD Business handbook: https://docs.ted.europa.eu/ESPD-EDM/latest/xml_business_handbook.html'
WS-Security is publicly available for free on OASIS Webpage. See: https://www.oasis-open.org/org/testimonials
'The website from where Domibus is distributed has all the documentation about its supporting processes and the change and release management. In addition, all major and minor changes on the specification are tracked on the "roadmap and previous releases" section. Domibus releases: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/Domibus+releases'
'The purpose of XSD 1.1 is not related to delivery of multilingual European public services. Therefore this criterion is considered not applicable to this specification. XSD Reference: https://www.w3.org/TR/2012/REC-xmlschema11-1-20120405/'
"There are many tools assessing the conformance of DNS's implementations. For instance, the DNS Compliance Testing provides tools to allow Registries and Registrars (amongst others) to check the DNS protocol compliance of the servers they are delegating zones to. GITHUB DNS Compliance Testing: https://gitlab.isc.org/isc-projects/DNS-Compliance-Testing "
"The SHACL specification has gained significant market acceptance and is driving innovative solutions across various industries. In this context, there are a lot of open solutions that implements shacl, such as dcat-ap validator (based in shacl) and shacl-based validator (iTestBed). In addition, other private solutions using SHACL can be found. Therefore, this highlights SHACL's versatility and its critical role in advancing data integrity and safety in diverse fields. Netage projects reference: https://blog.netage.nl/ Wimmics SHACL: https://wimmics.github.io/corese/cli_ref/cli_shacl.html SHACL W3C reference: https://www.w3.org/TR/shacl/"
IETF has a formal review and approval so that all the relevant stakeholders can formally appeal or raise objections to the development and approval of specifications. Each distinct version of an Internet standards-related specification is published as part of the "Request for Comments" (RFC) document series. This archival series is the official publication channel for Internet standards documents and other publications. During the development of a specification, draft versions of the document are made available for informal review and comment by placing them in the IETF's "Internet-Drafts" directory, which is replicated on a number of Internet hosts. This makes an evolving working document readily available to a wide audience, facilitating the process of review and revision. See: https://www.ietf.org/standards/process/ https://tools.ietf.org/html/rfc2026
At least 11 Member States are recommending HTTP in their ICT National Catalogues. See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'DPV has not been found to be included in any open repository or catalogue of standards at European level. DPV specification: https://w3c.github.io/dpv/primer/'
'The W3C Verifiable Credentials (VC) specification is designed to be modular and flexible, allowing for partial implementations based on specific use cases and requirements. Verifiable Credentials provide a standard way to express and exchange credentials on the web in a secure and privacy-preserving manner. Verifiable Credentials: https://www.w3.org/TR/vc-data-model/'
'AMQP enables different organizations to interconnect their systems seamlessly, by ensuring that messages can be exchanged reliably and efficiently between disparate systems, regardless of the underlying technology or platform used by each organization. Oasis AMQP Reference: http://docs.oasis-open.org/amqp/core/v1.0/amqp-core-complete-v1.0.pdf'
There are no disclosures of ISO IPR Database to identify the licensing under the specification. ISO 14533-3:2017 (PAdES) is not listed in ISO/IEC/ITU Common Patent policy, so it cannot be confirmed that the specification is licensed on a (F)RAND basis. ISO patents: https://www.iso.org/iso-standards-and-patents.html ISO standards and patents IPR database: http://isotc.iso.org/livelink/livelink/13622347/Patents_database.xls?func=doc.Fetch&nodeId=13622347
The purpose of the specifications is not related to the comprehensibility of administrative information, data or services. Therefore, this criterion is not applicable to this specification. TSP IETF reference: https://tools.ietf.org/html/rfc3161
'JSON sector agnostic specification that can be reused in any business domain requiring a common format to exchange data between different programs. JSON specification: https://www.ecma-international.org/wp-content/uploads/ECMA-404_2nd_edition_december_2017.pdf'
'OData promotes the sharing of data and results, and begs for its approval as an ISO/IEC Standard to help accelerate the specification adoption throughout the international community, particularly within government agencies. In this sense, the specification encourages both the creation of communities and the sharing of their data and results on European and national platforms. OData referenece, data exchange: https://www.oasis-open.org/news/pr/iso-iec-jtc-1-approves-oasis-odata-standard-for-open-data-exchange/'
The adoption of the specification facilitates interoperability between public administrations and cross-border data exchange by allowing a seamless exchange of collections across borders. More specifically, the specification fosters technical interoperability by providing functional requirements for APIs foreseen to exchange collections. The wide adoption of the specification would contribute to a harmonisation of the APIs provided by the various data portals and therefore, enhance the data discoverability of the datasets currently isolated within data portals, across borders
In Xiph organisation, there is a monthly meeting where everyone can assist and give their opinions about changes or improvements of the specifications. However, the final decision belongs to a committee that has to approve it. Monthly XIPH meetings: https://wiki.xiph.org/MonthlyMeeting Admin process XIPH: https://wiki.xiph.org/AdminProcesses
'SOAP 1.2 can be used independently from any other technical specifications or operating system. SOAP can also be adopted by without problems by the OGC service. SOAP Reference: https://www.w3.org/TR/soap12/ Inspire Network Services SOAP Framework, OGC service Reference: https://op.europa.eu/en/publication-detail/-/publication/54a89f97-0835-48e8-bf3c-37239e982fbd/language-en'
"There exist some studies assessing digital solutions' effectiveness that are based on iCalendar; however, most of them are restricted to learning environments. For example, one of these assessments involves Google calendar and their effectiveness in how this Google application improves a learning platform. Google calendar in learning environments - Design and Implementation of a Study Room Reservation System: Lessons from a pilot program using Google Calendar: https://research.library.fordham.edu/cgi/viewcontent.cgi?article=1002&context=lib_staffpubs iCalendar specification: https://www.rfc-editor.org/rfc/rfc5545"
IPv4 is the previous version of the Internet Protocol, but it is widely adopted and still prevailing. The newest has specific features and improves security aspects. Even the IPv6 it is being gradually implemented and included in new initiatives, the existing translation and transition mechanisms between versions avoid the interoperability hampering.
The European Union promotes the usage of IPv6 and the public administration are able to reuse it. "MS as for instance Germany could bring strong support to the deployment of IPv6 within the European public administrations." Source: https://ec.europa.eu/isa2/sites/isa/files/ipv6_framework_for_european_governments_0.pdf
'The purpose of UTF-8 is not related to the modelling of business processes, therefore this criterion is not applicable to the specification. UTF-8 specification: https://datatracker.ietf.org/doc/html/rfc3629'
'There is no evidence found that the ISAE 3402 encourages the creation of communities along with the sharing of their data and results on European platforms. ISAE 3402 handbook reference: https://www.ifac.org/system/files/downloads/b014-2010-iaasb-handbook-isae-3402.pdf'
'All releases of the specification are publicly reviewed but the feedback is not visible. It is worth mentioning that minor releases (fixes,..) are approved with minimal review while major releases have a more structured and well defined process. Asset Administration Shell (AAS) Github https://github.com/admin-shell-io/aas-specs/blob/master/CONTRIBUTING.md Details of the Asset Administration Shell (AAS) https://industrialdigitaltwin.org/en/wp-content/uploads/sites/2/2024/06/IDTA-01001-3-0-1_SpecificationAssetAdministrationShell_Part1_Metamodel.pdf'
HTML was the first mark up language to develop web resources. Its main purpose is to publish data on the web. By allowing the publication of administrative data on the web with various formats, HTML foster the visibility of administration data, and services. HTML W3C reference: https://www.w3.org/TR/html401/
The purpose of the specification is to facilitate the exchange of structured data. By allowing to make the data available to other persons or organisations, XML reduces the administrative burden.
'There exists assessments addressing the effectiveness of the DCAT specification. Referenced Article: https://www.sciencedirect.com/science/article/abs/pii/S1570826818300532'
'XSLT is maintained by W3C which is an international community developing open standards. W3 Community Reference: https://www.w3.org/Consortium/ '
The specification is included in 12 Member States' catalogues of recommended specifications. This Member States are Croatia, Cyprus, Estonia, Germany, Greece, Malta, Norway, Poland, Slovenia, Spain, Sweden and UK. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'DCMI itself has built a community around the specification which is continuously supporting the specification. DCMI About: https://www.dublincore.org/about/ DCMI Github: https://github.com/dcmi'
'The specification is not related to the publication of public data as open data. Therefore this criterion is not applicable to this specification. XACML OASIS reference: https://docs.oasis-open.org/xacml/3.0/xacml-3.0-core-spec-os-en.html'
'The DPV working group was created as an outcome of the W3C Workshop on Data Privacy Controls and Vocabularies in Vienna in 2017, and started on 25th May 2018 – the date of the enforcement of GDPR. Since then, the DPVCG has worked to fulfil its aims and objectives, and produced the Data Privacy Vocabulary (DPV) as a deliverable. DPV primer document: https://w3c.github.io/dpv/primer/#introduction'
'This specification mentions in section 5.3.3 that cloud services employ an identity and access management system to control access to the interfaces offered by a cloud service and also to control access to resources inside a cloud service. The authentication of the role agents involved in the data transactions is likely to be in the hands of the Cloud Service Provider (CSP). ISO 19941: https://www.iso.org/obp/ui/en/#iso:std:iso-iec:19941:ed-1:v1:en'
'UBL is designed to plug directly into existing business, accounting, legal, auditing, and records management practices, eliminating the re-keying of data required by traditional fax, scanned-image and paper-based supply chains and in doing so provides an entry point into electronic business for small and medium-sized businesses. Therefore UBL actively supports comprehensibility as is the case of the ESPD project. Developer community OASIS. UBL functionalities: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ubl#functionality UBL v2.3 reference: http://docs.oasis-open.org/ubl/os-UBL-2.3/UBL-2.3.html ESPD reference, Legal framework and context section: https://docs.ted.europa.eu/ESPD-EDM/3.0.1/xml_business_handbook.html#_i_1_1_legal_framework_and_context'
'SFIA is intended to serve as a device to represent the European e-Competence Framework, which focuses on skills and competences of the ICT professional workforce. There is no possibility to extend the specification, since SFIA has a single purpose. SFIA reference: https://sfia-online.org/en/sfia-8'
'There is no evidence that the GITB TDL encourages the creation of communities along with the sharing of their data and results on national platforms. GITB TDL reference: https://www.itb.ec.europa.eu/docs/tdl/latest/introduction/index.html#introduction'
'There is no conformance tool for the Registered Organization Vocabulary. However, the vocabulary defines conformance in terms of correct semantic usage and vocabulary prioritisation. Registered Organization Vocabulary reference: https://www.w3.org/TR/vocab-regorg/'
'UDDI allows to publish data in a public registry and can be useful for other people who is looking for solutions. However, UDDI is not intended for data exchange and does not provide many mechanisms to ensure a secure and correct exchange of data. Therefore, data exchange is possible, and there are some mechanisms to guarantee security, but it is not its main purpose. UDDI OASIS reference: https://www.oasis-open.org/standard/uddi/ IBM security reference: https://www.ibm.com/docs/en/was/8.5.5?topic=curs-configuring-uddi-registry-use-websphere-application-server-security'
'After checking the different standard catalogues at supra-national level, there is no evidence of the inclusion of ISAE 3402 within any European catalogue of standards. ICT technical specifications: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en CEN search tool catalogue: https://standards.cen.eu/dyn/www/f?p=CENWEB:105::RESET:::: CENELEC search tool catalogue: https://www.cenelec.eu/dyn/www/f?p=104:107:0::::FSP_LANG_ID:25'
'By focusing on citizen-centric service design and delivery, and leveraging digital channels and technologies, the TGF aims to improve the visibility and accessibility of administrative procedures and services, and to enhance the overall user experience for citizens and businesses. An example of it is the promotion of the health profile. TGF Specification: http://docs.oasis-open.org/tgf/TGF/v2.0/cs01/TGF-v2.0-cs01.html TGF health profile: https://lists.oasis-open.org/archives/tgf-comment/201406/msg00001.html'
'Like all the IETF standards, HTTP Cookies is a free and open technical specification, built on IETF standards and licenses from the Open Web Foundation. HTTPS is therefore available with any restrictions related to (F)RAND. HTTP Cookies reference: https://datatracker.ietf.org/doc/html/rfc6265'
'[TO BE CHECKED] The specification is intended solely for documenting metadata related to public code projects and does not aim to support or regulate secure data exchange. It lacks provisions for security or privacy frameworks and does not establish protocols for handling sensitive data or ensuring secure communications. Therefore, its scope does not align with the data exchange security and privacy requirements outlined in EIF Recommendation 15. Publiccode.yaml documentation: https://docs.italia.it/italia/developers-italia/publiccodeyml-en/en/master/index.html '
'The purpose of XACML is not related to e-accessibility. Therefore, this criterion is not applicable to the specification. XACML OASIS reference: https://docs.oasis-open.org/xacml/3.0/xacml-3.0-core-spec-os-en.html'
DCAT is recommended by the Netherlands and Spain within their national catalogues of recommended specifications. See: https://www.forumstandaardisatie.nl/open-standaarden/lijst https://administracionelectronica.gob.es/pae_Home/dam/jcr:9e2c2877-5103-4934-8440-c60ba2e10c48/Catalogue_of_Standards_NIF_Spain.pdf
'HTTP cookies is the most widely used standard protocol serving essential functions on the web such as storing stateful information on the user's device or tracking the user's browsing activity. For example, the Google Analytics JavaScript libraries use HTTP cookies to "remember" what a user has done on previous pages and interactions with the website. HTTP Cookies reference: https://datatracker.ietf.org/doc/html/rfc6265 Google Analytics reference: https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage?hl=es#analyticsjs'
JPEG is an international standard worldwide used as an image format. It is supported as a standard way for the treatment and exchange of image files. JEPG ISO reference: https://www.iso.org/standard/18902.html JPEG public reference: https://jpeg.org/jpeg/
'iCalendar enables the sharing and exchange of scheduling and event information between different systems and applications. This reusability ensures that calendar-related data can be easily imported, exported, and integrated into various software, promoting interoperability and reducing the need for data duplication or manual data entry. As a result, relevant information can be efficiently reused when needed, streamlining processes and enhancing data consistency across different platforms and services. iCalendar specification: https://www.rfc-editor.org/rfc/rfc5545'
'TLS itself is the foundation of a safe and secure internet. It ensures that data is transmitted privately and without modifications, loss or theft. Without TLS, many online public services would be vulnerable to data tampering and impersonation, making their delivery unreliable and untrustworthy. TLS 1.3 Reference: https://www.rfc-editor.org/rfc/rfc8446.html'
'The purpose of ADMS is not related to e-accessibility. Therefore, this criterion is considered not applicable to this specification. ADMS Specification W3C: https://www.w3.org/TR/vocab-adms/'
'The purpose of NUTS is not related to the secure processing of data. Therefore, this criterion does not apply to this specification. EUROSTAT reference, NUTS Principles and Characteristics section: https://ec.europa.eu/eurostat/web/nuts/principles-and-characteristics'
'As the description of the specification states, the Core Location Vocabulary is an extensible data model. In this context, the specification can be extended to achieve new functionalities, such as validating data with the SHACL shapes validator. SHACL shapes validator: https://semiceu.github.io/Core-Location-Vocabulary/releases/2.1.0/shacl/core-location-ap-SHACL.ttl Core Location Vocabulary: https://interoperable-europe.ec.europa.eu/collection/semic-support-centre/solution/core-location-vocabulary/release/100'
'WAI-ARIA specification allows for extension. Developers can extend the set of roles, states, and properties defined by WAI-ARIA to accommodate specific needs in their web applications. WAI-ARIA reference: https://www.w3.org/TR/wai-aria/'
UTF-8 is already associated to an EIRA ABB in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, UTF-8 can define the interoperability aspects of the "Data" ABB of the EIRA Semantic View. See: https://joinup.ec.europa.eu/solution/elis/distribution/eliscataloguev100betaxlsx
'OCSP is a a protocol that determines the status of a digital certificate. Therefore, this criterion is not applicable to the specification. OCSP reference: https://datatracker.ietf.org/doc/html/rfc2560'
ELI can be found for free on EUR-Lex. ELI reference: https://eur-lex.europa.eu/eli-register/about.html
'The first version of the EN 303 645 specification was published in 2019 and superseded the ETSI TS 103 645 specification for consumer Internet of Things (CIoT); the latter was the first standard for cybersecurity in the Internet of Things, which was considered as a security baseline for Internet-connected consumer products and a basis for future IoT certification schemes. As a proof of market acceptance, at present EN 103 701 is meant to serve as an input to a forthcoming EU cybersecurity certification system, as proposed in the Cybersecurity Act (see ETSI Work Programme reference). EN 303 645 homepage reference: https://www.etsi.org/technologies/consumer-iot-security TS 103 645 reference: https://www.etsi.org/newsroom/press-releases/1549-2019-02-etsi-releases-first-globally-applicable-standard-for-consumer-iot-security TS 103 701 reference: https://www.etsi.org/deliver/etsi_ts/103700_103799/103701/01.01.01_60/ts_103701v010101p.pdf ETSI Work Programme reference: https://portal.etsi.org/webapp/WorkProgram/Report_WorkItem.asp?WKI_ID=58434&curItemNr=39&totalNrItems=296&optDisplay=100000&qSORT=TB&qETSI_ALL=&SearchPage=TRUE&qINCLUDE_SUB_TB=True&qINCLUDE_MOVED_ON=&qEND_CURRENT_STATUS_CODE=11+WI%3BM58&qSTOP_FLG=N&qKEYWORD_BOOLEAN=OR&qCLUSTER_BOOLEAN=OR&qCLUSTER=19&qFREQUENCIES_BOOLEAN=OR&qSTOPPING_OUTDATED=&butExpertSearch=Search&includeNonActiveTB=FALSE&includeSubProjectCode=FALSE&qREPORT_TYPE='
The specification can be used independently from specific vendor products.
As a way to compress images and easing the communication of graphic information, it can ease the comprehensibility of the administration's data, rules, and services. By allowing a more visual representation of the information, it contributes to the easy understanding of bucks of different data. JEPG ISO reference: https://www.iso.org/standard/18902.html JPEG public reference: https://jpeg.org/jpeg/
CAMSS Assessment of SOAP EIF Scenario v1.0.0
"In those procedures where it's crucial to have a clear record of when certain actions were taken or when documents were modified, TSP can be a good visibility enabler given its capability to assig timestamps to each event or change, allowing administrators to create a detailed and verifiable log of the sequence of actions. This log can then be used to review procedures, and maintain historical records. TSP IETF reference: https://tools.ietf.org/html/rfc3161"
'Registered Organization Vocabulary does not enable the secure exchange of data. The main purpose of the specification is to define a standardised way of describing organisations that have gained legal entity status through a formal registration process Therefore, this criterion is considered not applicable to this specification. Registered Organization Vocabulary reference: https://www.w3.org/TR/vocab-regorg/'
'OAIS has become very popular between institutions and entities that require large amounts of archives to be stored and preserved. Among the most important organisations that use OAIS reference data model we can find the Library of Congress, the British National Library, or the Networked European Deposit Library (NEDLIB), find below a list of organisations implementing OAIS. The NEDLIB project: http://www.dlib.org/dlib/september99/vanderwerf/09vanderwerf.html OAIS usage: http://www.oais.info/oais-usage/'
CAMSS Assessment of HTTPS EIF Scenario v1.0.0
'ISO/IEC 7498:1 does not directly facilitate the publication of data on the web, but it contributes to the broader goal of providing a common conceptual framework for the development and understanding of network protocols and communication systems. ISO/IEC 7498:1: https://www.iso.org/standard/20269.html'
'The specification includes several authenticity considerations. In this context, although the specification does not implement TLS, it recommends it. In this sense, only pages using TLS with certificates that identify them as being from the same domain can access their respective databases. As a result, unauthorized pages cannot access these databases and are thus protected. Indexed Database API: https://www.w3.org/TR/IndexedDB/'
The European Union (EU) Member States are currently implementing the INSPIRE Directive and related regulations, included in the ISA programme. This projects includes the usage of XSLT included in a catalogue of standards at EU level too. See: https://ies-svn.jrc.ec.europa.eu/projects/registry-development/wiki/Re3gistry_1_0_documentation#_cp3
"ISO/IEC 7498:1 primarily focuses on providing a conceptual framework for network communication. It does not explicitly address the exposure of interfaces to access public administration's services. The OSI model is more concerned with the abstraction of functions into layers to facilitate interoperability and communication between different systems. ISO/IEC 7498:1: https://www.iso.org/standard/20269.html"
'The specification makes use of optional classes that allow it to be more flexible towards the purpose it is working for. An example can be the Participation class that allows to define roles within a certain context. CPSV-AP Joinup webpage: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/core-public-service-vocabulary-application-profile/release/22'
9 Member States are recommending PNG in their ICT National Catalogues. This Member States are Croatia, Estonia, France, Germany, Greece, Norway, Poland, Spain and Sweden. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'This specification is not currently included in the EIRA Library of Interoperability Specifications (ELIS), but will be included in the next release of the ELIS. The response to this criterion is positive because EN 303 645 is mappable to the European Interoperability Reference Architecture (EIRA). EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/v110'
'LDES is included in the SEMIC community in Joinup. The Semantic Interoperability Community (SEMIC) develops solutions to help European public administrations perform seamless and meaningful cross-border and cross-domain data exchanges. LDES specification: https://joinup.ec.europa.eu/collection/semic-support-centre/linked-data-event-streams-ldes SEMIC working groups: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/about'
W3C provides a Markup Validation Service for free to validate SOAP 1.2 implementations. See: https://validator.w3.org/feed/docs/soap.html
'The standardized terms and concepts within EuroVoc can facilitate clearer communication and understanding between systems, which is beneficial for secure data exchange protocols. When different entities use the same standardized terms and classifications, it can reduce ambiguity and errors during data transmission, contributing to more secure and accurate exchanges. EuroVoc: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource /dataset/eurovoc'
'The Joinup platform comprises a large European community of developers, some of who are focused on UBL implementations. Among the different issues addressed we can find tutorials, or discussion forums related to the specification. Joinup: About OASIS Universal Business Language (UBL) https://joinup.ec.europa.eu/collection/eprocurement/solution/oasis-universal-business-language-ubl/about UBL in Github: https://github.com/oasis-tcs/ubl'
'ebXML does not allow customisation nor provides any guidelines to customise any of the specification features. ebXML reference: http://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html'
After being evaluated compliant with the regulation on standardisation 1025/2012, LDAPv3 has been identified by Commission Implementing Decision. ICT technical specifications: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en
'DNS is included in 9 national catalogues of recommended specifications. They belong to Coratia, Cyprus, France, Germany, Greece, Malta, the Netherlands, Spain and Sweden. The National Interoperability Framework of France, Germany and Spain is fully aligned with the 3 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. NIFO Factsheets France: https://joinup.ec.europa.eu/sites/default/files/inline-files/DPA_Factsheets_2021_France_vFinal.pdf NIFO Factsheets Germany: https://joinup.ec.europa.eu/sites/default/files/inline-files/DPA_Factsheets_2021_Germany_vFinal.pdf NIFO Factsheets Spain: https://joinup.ec.europa.eu/sites/default/files/inline-files/DPA_Factsheets_2021_Spain_vFINAL_0.pdf CAMSS list of standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
After checking the different standard catalogues at supra-national level, there is no evidence of the inclusion of FTPS within any European catalogue of standards. ICT technical specifications: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en CEN search tool catalogue: https://standards.cen.eu/dyn/www/f?p=CENWEB:105::RESET:::: CENELEC search tool catalogue: https://www.cenelec.eu/dyn/www/f?p=104:107:0::::FSP_LANG_ID:25
'The purpose of the EN 303 645 specification is not related to the visibility of administrative procedures, rules data, and services. EN 303 645 reference: https://www.etsi.org/deliver/etsi_en/303600_303699/303645/02.01.01_60/en_303645v020101p.pdf'
'OAS is independent of any specification and can be implemented without any dependency on platforms. OAS specification: https://spec.openapis.org/oas/latest.html#openapi-specification OAS in Github: https://github.com/OAI/OpenAPI-Specification/#participation'
The specification has been listed within the EUOS project, that provides a list of ICT specifications and standards according to the ICT Rolling plan. EU Observatory for ICT Standardisation: https://www.standict.eu/standards-repository
"Schema.org was originally conceived for the semantic web. Nonetheless, the specification project has successfully extended schema.org to other domains because of the variety of attributes and types it presents (see Schema.org reference, Data model section). Besides, schema.org also offers additional domain-related schema extensions that may differ from each other (see Schema.org homepage reference, 'Organization of Schemas' section), improving the specification capability to be implemented in other domains prior to a deliberate selection of the schema. Schema.org homepage reference, 'About Schema.org' section: https://schema.org/docs/about.html Schema.org reference, Data model section: https://schema.org/docs/datamodel.html Schema.org homepage reference, 'Organization of Schemas' section: https://schema.org/docs/schemas.html"
After carrying out a exhaustive reserch, no evidence has been found of an established agreement between organisations involved in European public services provision.
The purpose of CAdES is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification. CAdES ISO reference: https://www.iso.org/standard/64756.html CAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/101700_101799/101733/02.01.01_60/ts_101733v020101p.pdf
CEF’s Action has developed a tool for testing the conformance of eDelivery Access Point and SMP specifications. This tool include eDelivery SMP 1.10 as it can be read in the CEF eDelivery Conformance Testing Document Service. See: https://ec.europa.eu/cefdigital/wiki/download/attachments/82773210/%28CEFeDelivery%29%20%28ConformanceTesting%29%20%28SOD%29%20%28v2%2010%29.pdf?version=1&modificationDate=1538392192100&api=v2
'The specification is recommended in 8 ICT Catalogues, among those the Netherlands. FTP Specification Reference: https://datatracker.ietf.org/doc/html/rfc959 CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards Netherlands NIFO Factsheets: https://joinup.ec.europa.eu/sites/default/files/inline-files/DPA_Factsheets_2022_Netherlands_vFinal_0.pdf'
EuroVoc is a public asset developed by a European Institution and can be accessed and reused without any payment conditions. Therefore, it can be considered that the specifications is licensed on a royalty-free basis. EuroVoc reference: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/eurovoc
The purpose of PAdES is not related to organisational interoperability. Therefore, this criterion is not applicable to the specification. PAdES ISO reference: https://www.iso.org/standard/67937.html PAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/102700_102799/10277801/01.01.01_60/ts_10277801v010101p.pdf
'The specification is included in an initiative at European level covering privacy aspect. As an example, the implementation of CESOP Legislative Package , which monitor the payees of cross-border payments and transmit information. XSD Reference: https://www.w3.org/TR/2012/REC-xmlschema11-1-20120405/ Legislative Package CESOP Reference: https://taxation-customs.ec.europa.eu/taxation-1/central-electronic-system-payment-information-cesop_en'
'The purpose of the Better Regulation Guideline and Toolbox is not related to the business process definition, and therefore, this criterion does not apply to the specification. Better Regulation Guidelines and Toolbox reference: https://commission.europa.eu/law/law-making-process/better-regulation/better-regulation-guidelines-and-toolbox_en'
ASiC and ASiC Baseline profile is referenced in the ETSI collection at the European Platform Joinup. Moreover, it can be found for free at ETSI’s webpage See: https://joinup.ec.europa.eu/solution/electronic-signatures-and-infrastructures-esi-associated-signature-containers-asic-part-3-baseline/about https://www.etsi.org/deliver/etsi_ts/103100_103199/103174/02.02.01_60/ts_103174v020201p.pdf
The SMP has been used as the basis for the development of the eDelivery SMP specification, which in turn is the basis for the implementation of the CEF eDelivery Building Block. The CEF eDelivery Building Block helps public administrations to exchange information with stakeholders (e.g. other administrations, businesses or citizens). eDelivery SMP specification: https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery+SMP CEF eDelivery Building Block: https://ec.europa.eu/inea/sites/inea/files/building_block_dsi-introdocument_edelivery_v1_00.pdf
'Registered Organization Vocabulary helps to scope comprehensibly administrative procedures, rules data, and services by providing a structured vocabulary for describing organisations that have gained legal entity status through a formal registration process. Furthermore, the Registered Organization Vocabulary, despite not being maintained anymore, is still used by the Open Standards for Linking Organizations (OSLO), more concrete in the application profile of "Slimme Stadsdistributie". The "Slimme Stadsdistributie" application profile reuses terms from the Registered Organization Vocabulary to represent the fundamental concept of a Geregistreerde Organisatie and its key properties, such as its registration identifier and its legal name. This ensures a common semantic understanding of what constitutes a registered organisation in the context of smart urban distribution. Registered Organization Vocabulary reference: https://www.w3.org/TR/vocab-regorg/ OSLO Smart City Distribution - Application profile Reference: https://data.vlaanderen.be/doc/applicatieprofiel/slimme-stadsdistributie/'
'CSV makes sure content is available on the web, structures data and makes it usable in a non-proprietary open format. So it can be said that CSV is independent from any technology or platform. CSV reference: https://datatracker.ietf.org/doc/html/rfc4180'
'The purpose of XML is not related to e-accessibility. Therefore, this criterion is not applicable to the specification.'
'The purpose of this Core Vocabulary is not related to the protection against unauthorised changes. Therefore, this criterion is not applicable to this specification. CPSV-AP reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-service-vocabulary-application-profile'
'The purpose of SFIA is not related to the visibility of administrative procedures, rules data and services. Therefore, this criterion is not applicable to this specification. SFIA reference: https://sfia-online.org/en/sfia-8'
'The Advanced Encryption Standard can be implemented in any software, firmware, hardware or any combination of them. Therefore, the standard is technology agnostic. AES Standard Reference: https://csrc.nist.gov/pubs/fips/197/final'
The purpose of SMTP is not related to the delivery of multilingual public services. Therefore, this criterion is not applicable to the specification. SMTP IETF reference: https://tools.ietf.org/html/rfc5321
'Administrative metadata within the CSIP can include information about access rights, permissions, and security measures associated with the information package. This metadata can be used to specify and enforce restrictions on who can access the information and under what conditions, therefore, addressing and enabling the implementation of confidentiality features. E-ARK CSIP specification: https://earkcsip.dilcis.eu/#introduction'
HTTP is used for any solution using internet, including innovative solutions.
'ISO/IEC 27001 is presented as an exhaustive set of requirements to be applied in any given Information Security Management system (ISMS), therefore, it does not allow extension. ISO 27001 reference: https://www.iso.org/obp/ui/#iso:std:iso-iec:27001:ed-2:v1:en'
Regarding eSignatures, CAdES includes features to the long-term preservation of data included in electronic signatures. The LTA-Level of requirements is covering the preservation, integrity of attributes and validation materials for the eSignatures ensuring the long-term accessibility. However, the specification is not strictly related to the functions of eArchiving.
'ETSI TS 119 614-1 has the support of various communities listed in the following link as "Supporting Organizations", including Universities, private and public companies. The ESI technical committee provides public support to members and non-members alike, with different conditions depending on ETSI membership status. Portal ETSI reference: https://portal.etsi.org/webapp/workprogram/Report_WorkItem.asp?WKI_ID=39422 ESI technical committe reference: https://www.etsi.org/committee/1399-esi'
'iCalendar does not define any mechanism to protect data against unauthorized changes. iCalendar could allow third-party standards to enhance data integrity. iCalendar Classification: https://www.rfc-editor.org/rfc/rfc5545#section-3.8.1.3'
SEMIC developed a service that checks the integrity and consistency against the DCAT-AP specification of one or more software description metadata files. It is available for free at the on Joinup, the European Commission collaborative platform for the reuse of IT Solutions. See: http://dcat-ap.semic.eu/dcat-ap_validator.html https://joinup.ec.europa.eu/solution/dcat-application-profile-data-portals-europe/about
After searching in the different official European websites, there is no evidence of any cross-border project that uses the Standard for Public Codes nor explicit agreements involving the usage of the specification.
The W3C Royalty-Free IPR licenses granted under the W3C Patent Policy apply to all W3C specifications, including DCAT. See: https://www.w3.org/TR/patent-practice#ref-AC
The specification is mainly focused on the definition of a common vocabulary for the description and the exchange of access rights and digital materials consumptions. This common framowork and method help to ensure the trustworthy data exchange between administrations and stakeholders. W3C specification reference: https://www.w3.org/TR/odrl-vocab/#vocab-core
'An extension is possible for the specification as EuroVoc has an active maintenance team that examines proposals made by EuroVoc users and forwards them to the Group Interinstitutional Lex (GIL) EuroVoc Committee, which evaluates and votes the proposals and decides on the amendments to be made. EuroVoc Handbook: https://publications.europa.eu/resource/cellar/a2723a83-574f-11eb-b59f-01aa75ed71a1.0001.01/DOC_1 EuroVoc: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource /dataset/eurovoc'
RegOrg can be found for free along within the European Collaborative Platform, Joinup. RegOrg Joinup reference: https://joinup.ec.europa.eu/solution/registered-organization-vocabulary
'ShEx is being used in the Hercules ASIO project, which has developed a lite version of ShEx. The lite version helps to facilitate such organisational interoperability agreements, insofar the project outcome enhances interoperabiltiy bteween university knowledge technologies. ShEx primer document: https://shexspec.github.io/primer/ ShEx Community Group: https://www.w3.org/community/shex/ ShEx Github: https://github.com/shexSpec/spec/issues'
'Joinup offers several services that aim to help e-Government professionals share their experience with each other. Joinup supports them to find, choose, re-use, develop and implement interoperability solutions. UDDI appears in many Joinup entries as a discussion topic, and the specification is distributed and can also be found in the platform. UDDI distribution in Joinup: https://joinup.ec.europa.eu/collection/dutch-standardisation-forum-comply-or-explain-standards/solution/universal-description-discovery-integration'
Ogg is publicly available for its use and implementation. Moreover, it is available for everyone to study with no cost on XIPH webpage. Ogg XIPH reference: https://xiph.org/ogg/doc/rfc3533.txt
'The EIRA was used to analyse and design a solution for the VAT in the Digital Age (ViDA). The work was done together with TAXUD. ViDA Success Story: https://interoperable-europe.ec.europa.eu/collection/european-interoperability-reference-architecture-eira/news/egoverac-success-vida-e-invoicing-requirements-dg-taxud EIRA reference: https://interoperable-europe.ec.europa.eu/collection/european-interoperability-reference-architecture-eira /solution/eira/release/610 EIRA Github Repository: https://github.com/CarTool-EC/EIRA'
'The REM RI (Relay Interface) should be identified by a transport protocol, a hostname and a port number. REM is a particular instance of Electronic Registered Delivery Service (ERDS) and makes interoperability smooth and increases usability, at the same time, the application of additional security mechanisms ensures integrity, confidentiality, and non-repudiation and protects against the risk of loss, theft, damage or any other illegitimate modifications, which enhances the trustworthy exposure of interfaces. Other techniques may be used either according to clause 6.1 of ETSI EN 319 522-3, peer-to-peer agreements between REMSPs or based on the best practices recommended in Annex A of ETSI EN 319 532-4. ETSI EN 319 532-3, Routing Information, page 25 reference: https://www.etsi.org/deliver/etsi_en/319500_319599/31953203/01.02.01_60/en_31953203v010201p.pdf '
The purpose of W3C Best Practices is not related to organisational interoperability. Therefore, this criterion is not applicable to the specification. W3C reference: https://www.w3.org/TR/dwbp/
'EuroVoc has not been found included in any initiative neither at European nor on national level covering privacy aspects. EuroVoc: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource /dataset/eurovoc'
'The main function of UDDI is to organize and catalog web services in a register, which can be applied to multiple domains such as the public sector. For example, UDDI can be used for the listing and description of government web services, thereby improving their discoverability and thus, enhancing the visibility of administrative services. UDDI techtarget reference: https://www.techtarget.com/whatis/definition/UDDI-Universal-Description-Discovery-and-Integration'
'In order to meet the standard protocol requirements, LDAP can not be customised. Extension Mechanisms for DNS: https://datatracker.ietf.org/doc/html/rfc6891'
'Domibus supports extension through its plugin mechanism and allows you to add custom features, integrations, and enhancements to meet specific requirements and extend its functionality. Domibus specification: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/Domibus'
'While IPv4 doesn’t inherently provide visibility into these business elements, it enables access to data and services that can make them visible, such as through supporting access to web applications or the interconnection of distributed systems. IPv4 IETF: https://www.rfc-editor.org/rfc/rfc791'
'ISO/IEC 19944-1, focusing on cloud service management, has the potential to simplify the delivery of public services. By implementing the specification, public administrations can leverage cloud computing to achieve scalability, cost efficiency, accessibility, collaboration, and rapid deployment of digital services. ISO/IEC 19944-1 provides guidelines for effective cloud service management, allowing public administrations offer a more streamlined and efficient delivery of public services. ISO/IEC 19944-1 specification: https://www.iso.org/standard/60545.html'
"There is no evidence of any study directly assessing the effectiveness of the EN 303 645 specification. However, there are some organisations from the private sector, offering solutions based on the specification's performance with respect to the market, that indirectly assess the specification's effectiveness. It is the case of TÜV SÜD, which offers testing against the EN 303 645 specification. TÜV SÜD-EN 303 645 reference: https://www.tuvsud.com/en-us/industries/consumer-products-and-retail/iot-cybersecurity/"
'As a business domain agnostic specification, FTP can be used for the exchange of documents addressing any business domain. FTP Specification Reference: https://datatracker.ietf.org/doc/html/rfc959'
'The purpose of XSLT is not related to e-accessibility. Therefore this criterion is considered not applicable specification. XSLT Reference: https://www.w3.org/TR/xslt-30'
'CPSV-AP is designed to facilitate the access to public service information among other main goals of the specification. CPSV-AP reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-service-vocabulary-application-profile'
'Conformance to HTTP implementation means it is correctly mapped and aligned with the vocabularies it defines. HTTP can define conformance requirements relying on manual methods and general guidelines for assessing conformance by the usage of the keywords: "MUST," "SHOULD," and "MAY". Httplint is an online tool that performs various checks on HTTP/1.1 headers returned by a server. It checks the syntax and content of almost all HTTP/1.1 response headers, and also warns about missing headers and suggests improvements. HTTP Lint: http://zamez.org/httplint HTTP /1.1 RFC 2616 Reference: https://www.rfc-editor.org/rfc/rfc2616.html HTTP/1.1 Semantics, RFC 9110 Reference: https://www.rfc-editor.org/rfc/rfc9110'
'The purpose of IPv6 is not related to e-accessibility. Therefore this criterion is considered not applicable to the specification. IPv6 IETF: https://www.rfc-editor.org/rfc/rfc2460'
According to the 5 star Open Data model suggested by Tim Berners-Lee about how to publish linked data, the second star corresponds to make data available as structured data, an area of application of SOAP 1.2. In addition, SOAP 1.2 serialisation provides several advantages, especially if the Semantic Web is not just about providing metadata for existing web pages, but also about exchange of content that is machine-readable. See: https://5stardata.info/en/ https://pdfs.semanticscholar.org/dbf2/6496e5b3087b708d4c00883c6470b53ff8d8.pdf
'While the purpose of Dataspace Protocol is not related to enabling the long-term preservation of data/information/knowledge (electronic records included) explicitly, the protocol does promote data management practices that can address this issue. For instance, establishing technical and semantic interoperability can improve long-term preservation of data greatly. IDSA IDS Specification: https://github.com/International-Data-Spaces-Association/ids-specification/'
The purpose of CAdES is not related to organisational interoperability. Therefore, this criterion is not applicable to the specification. CAdES ISO reference: https://www.iso.org/standard/64756.html CAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/101700_101799/101733/02.01.01_60/ts_101733v020101p.pdf
'Although the main purpose of the specifications is not the preservation of information it can be used in the context of eArchiving. An example of this aim is DCAT and DCAT-AP, data catalogues vocabularies built around RDF and which are used with the purpose of describing datasets included in data catalogues. The enrichment by means of metadata according to RDF schema could help to the long term preservation of digital documents. DCAT specification: https://www.w3.org/TR/vocab-dcat-2/ DCAT-AP Specification: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/dcat-application-profile-data-portals-europe/release/200 RDF primer document: https://www.w3.org/TR/rdf11-primer/'
DNS does not hamper the scalability of the systems implementing it. In fact, by allowing the association of a name to a domain, the maintenance and identification of domains is facilitated.
SMTP is publicly available for implementation and use, and therefore for everyone to study, for free on IETF webpage. SMTP IETF reference: https://tools.ietf.org/html/rfc5321
'UDDI.org, which is now associated with OASIS, is comprised of more than 200 major software developers and e-business leaders. Since 2000, UDDI has released three versions for different main purposes. Moreover, the specification is in constant development by its community, and there is documentation available in uddi.org. Therefore, it is demonstrated that UDDI has enough maturity for its use in the development of digital solutions and services. UDDI OASIS reference: http://www.uddi.org/pubs/uddi_v3.htm#_Toc85907974 UDDI evolution reference: http://www.uddi.org/pubs/the_evolution_of_uddi_20020719.pdf'
The purpose of XAdES is not related to the comprehensibility of administrative information, data or services. Therefore, this criterion is not applicable to this specification. XAdES ISO reference: https://www.iso.org/standard/56025.html XAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/101900_101999/101903/01.04.02_60/ts_101903v010402p.pdf
There are no Member States recommending Standard for Public Code in their ICT National Catalogues. The Standard for Public Code webpage: https://standard.publiccode.net/ CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'LDAP provides communication between clients and AD, which means it is responsible for transporting highly sensitive information. For that matter LDAP can be developed to meet high performance security standards, including those related to data processing. An example for that could be the layer/transport layer security (SSL/TLS) encryption can add vital protection to information shared through LDAP and enhance the security of organizations’ communication channels. LDAP Authentication methods and security mechanisms: https://www.rfc-editor.org/rfc/rfc4513.txt'
After checking the assessments performed by CAMSS and the list of specifications identified by the MSP Multi-stakeholder-platform, no assessment verifying the compliance of the specification with the European standardisation regulation has been found. ICT technical specifications: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en CAMSS Assessments Library: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-assessments-library
The SOAP 1.2 is included in the European Interoperability Architecture (EIA) study explores the need for a European interoperability architecture facilitating the establishment of European public services (cross border eGovernment services). WS-Security is a SOAP 1.2 extension so it can be mapped in EIRA too. See: https://ec.europa.eu/isa2/sites/isa/files/isa_2.1_eia-finalreport-commonvisionforaneia.pdf
The DCAT-AP vocabulary supports the attribution of data and metadata to various participants such as resource creators, publishers and other parties. In addition, it also supports the association of rights and licenses with catalogued Resources and Distributions. Such metadata improves the reliability of data exchanged between citizens, businesses and public administrations.
XSD is included in 2 national catalogues of recommended specifications. They belong to the Netherlands and Spain. The National Interoperability Framework (NIF) of these Member States is fully aligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards https://joinup.ec.europa.eu/collection/national-interoperability-framework-observatory-nifo/nifo-factsheets
'There are pieces of evidence that state OData is wide-spread and used (see OData ecosystem reference). Although there are some market alternatives to OData, such as GData (Google) or OpenAPI, it is worth to note that there is some evidence of OData as an innovative solutions creator. Moreover, the specification has a dedicated Github tailored by the Microsoft community. Stackshare-OData reference: https://stackshare.io/odata/alternatives OData ecosystem reference: https://www.odata.org/ecosystem/ OData-Microsoft Github reference: https://github.com/OData GData reference: https://developers.google.com/gdata?hl=es-419 OpenApi reference: https://spec.openapis.org/oas/latest.html'
Any cross-border project using internet, uses HTTPS. An interesting example is the TESTA network service – which stands for Trans European Services for Telematics between Administrations – provides a European backbone network for data exchange between a wide variety of public administrations. It is an ISA2 solution which has been designed to support the needs for a whole range of application architectures relying on protocols such as HTTPS. See: https://ec.europa.eu/isa2/solutions/testa_en
'The purpose of SAML 2.0 is not related to the publication of data as Linked Open Data. Therefore, this criterion is not applicable to this specification. SAML 2.0 Reference: http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-tech-overview-2.0.html'
'XACML can be used independently from any other technical specifications. However, it is worth noting that since it is based on XML, it can be dependent on conventions and rules for the correct XML usage. XACML OASIS reference: https://docs.oasis-open.org/xacml/3.0/xacml-3.0-core-spec-os-en.html'
There are no Member States recommending SAMM in their ICT National Catalogues. The SAMM webpage: https://standard.publiccode.net/ SAMM documentation: https://github.com/OWASP/samm/blob/master/Supporting%20Resources/v2.0/OWASP-SAMM-v2.0.pdf CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'5 Member States are recommending the specification in their ICT National Catalogues. CAMSS List of standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards National Catalogue of France: https://www.numerique.gouv.fr/uploads/Referentiel_General_Interoperabilite_V2.pdf'
'The purpose of TGF is not related to the long-term preservation of information, therefore, this criterion is not applicable to the specification. TGF specification: http://docs.oasis-open.org/tgf/TGF/v2.0/cs01/TGF-v2.0-cs01.html'
FTPS is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, FTPS can define the interoperability aspects of the "Network", "Networking Service", "Public Network" and "Private Network" ABBs of the EIRA Technical View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/solution/elis/release/v100
'The ETSI and any of its committees, in charge of the development of EN 303 645, operates under the ETSI Intellectual Property Rigths (IPRs) and IPR Policy. The specification is licensed on a (F)RAND basis. Intellectual Property Rights Policy, ETSI ownership of IPRs section: https://www.etsi.org/intellectual-property-rights'
Representing the graphical information from several sources as XML, it can help the comprehensibility of administrative data. In this sense, it can also help the decision-making process by displaying graphics and data that is relevant for the administration. SVG W3C reference: https://www.w3.org/TR/SVG11/
The purpose of UTF-8 is not related to long term preservation of electronic records. Therefore this criterion is considered not applicable to this specification.
The main purpose of RegOrg is to capture the typical details recorded by business registers and thereby facilitate information exchange between them. So it facilitates the comprehensibility of public administrations data. RegOrg about Joinup reference: https://joinup.ec.europa.eu/solution/registered-organization-vocabulary/about
'E-ARK CSIP places a strong emphasis on enabling the long-term preservation of information. The CSIP provides guidelines and recommendations for packaging, managing, and preserving digital information to ensure its accessibility, integrity, and usability over extended periods of time. E-ARK CSIP specification: https://earkcsip.dilcis.eu/#introduction'
'As Internet Protocol Stack, IPv6 is being selected gradually by different member states. The specification is the most used data exchange protocol over the internet. The European Union is willing to implement the IPV6 as it is stated in the following report: "The adoption of IPv6 in Europe, in particular within European public administrations, is still low, but the availability of IPv6 communication is vital for the economic development and the digitisation of European public administrations. The goals of the Digital Agenda for Europe and the Digital Single Market Strategy are based on stable and reliable data networks". Therefore IPv6 fosters the visibility of data across borders. "IPv6 framework for European Governments" reference: https://ec.europa.eu/isa2/sites/isa/files/ipv6_framework_for_european_governments_0.pdf IPv6 IETF: https://www.rfc-editor.org/rfc/rfc2460'
'Several implementations are assessing the usefulness and exploring how the usage of this specification can enhance the accessibility to digital platforms. Some of them are React Aria and Mozilla. However, this does not extend to the European Public Service. Mozilla reference, Accessibility with WAI-ARIA section: https://developer.mozilla.org/en-US/docs/Learn/Accessibility/WAI-ARIA_basics React Aria reference, home page: https://react-spectrum.adobe.com/react-aria/'
The specification includes accessibility as one of the aspects to take into account for the development of new solutions and products. Since it is a key aspect for the equal treatment of citizens. Moreover, it provides guidelines on how the code has to be documented using WCAG standard to ensure the maximum user/usage scope possible. The Standard for Public Code webpage: https://standard.publiccode.net/
'No member state has been found including TGF in its natioal catalogue of recommended specifications. CAMSS list of standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
'The purpose of EuroVoc is not related to enabling digital service delivery channels. Therefore, this criterion is considered not applicable to this specification. EuroVoc: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource /dataset/eurovoc'
'There is no Member State recommending SFIA in its ICT National Catalogue. SFIA reference: https://sfia-online.org/en/sfia-8'
EuroVoc was developed for the first time in 1982. It has been constantly evolving to adapt user's needs. Moreover, there are several releases since it was developed that justify its maturity and its use in the developement products and services. EuroVoc Releases: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/eurovoc
ELI is a business-specific specification that is focused on the identification and definition of metadata for legal documents at the European Level. Even though it could be extended or modified to fit other business requirements, there are no implementations that evidence this fact. ELI reference: https://eur-lex.europa.eu/eli-register/about.html ELI Technical Documentation: https://eur-lex.europa.eu/eli-register/technical_information.html
There are many free online tools that perform numerous checking in order to verify the conformity of the ETSI Advanced Electronic Signatures which includes XAdES. XAdES conformance testing: https://signatures-conformance-checker.etsi.org/pub/index.shtml
"Schema.org may enable digital service delivery channels. European Legislation Identifier (ELI) is using schema.org in some of its use cases, increasing the access to legislative documents. ELI is adopting the schema.org Legislation vocabulary. Schema.org homepage reference, 'About Schema.org' section: https://schema.org/docs/about.html ELI-Joinup reference: https://joinup.ec.europa.eu/collection/eli-european-legislation-identifier/solution/eli-legislation-extension-schemaorg/about Schema.org reference, Legislation vocabulary: https://schema.org/Legislation"
"The specification is made by W3C, which is a non-European international SDO. Therefore, it can't be considered as an European Standard. World Wide Web Consortium (W3C) reference: https://www.w3.org/"
"ETSI TS 119 432 foresees enabling access control mechanisms. Digital signatures can work as access control mechanisms to private data. The authorised signer's use of its key for signing requires users to provide multiple proofs of their claimed identity before being granted access to the needed set of resources. Nevertheless, the way in which the user identity verification process is carried out by the service provider or any suggestion concerning the usage of multi-factor authentication mechanisms is out of the scope of the present document. ETSI TS 119 432: https://www.etsi.org/deliver/etsi_ts/119400_119499/119432/01.02.01_60/ts_119432v010201p.pdf"
'UTF-8 was launched at the beginning of 2000s, and it currently is one of the three encoding methods recognised by Unicode or web languages. This fact demonstrates the maturity and the market acceptance for development of products and services. Usage statistics for character encodings for websites: https://w3techs.com/technologies/overview/character_encoding/all '
At the moment of performing the assessment, Ipsec is widely used, including for the development of innovative solutions and especially when Virtual Private Networks are required.
'Some evaluations indirectly evaluate the efficiency of the specification. For example, this document offers a survey of current literature and examines open-source dataspace connector implementations that adhere to the International Data Spaces (IDS) standard. The selection of the IDS standard in this context serves as an indirect demonstration of its relevance and efficiency compared to other alternatives. A Survey of Dataspace Connector Implementations: https://arxiv.org/pdf/2309.11282.pdf'
'ETSI TS 119 512 protocols are designed in a way that can be implemented separately depending on the preservation goals (see section 4.2) or the storage models (see section 4.3). Partial implementations therefore are allowed in this specification. ETSI TS 119 512 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.02_60/ts_119512v010102p.pdf'
"Schema.org is a (structured data) mark-up schema that helps search engines understand the information on web pages and potentially provides richer search results. Therefore, the specification addresses data portability. At European level, the DCAT Application Profile for Data Portals in Europe (DCAT-AP) will be mapped to schema.org, resulting in DCAT-AP-SDO (Schema.org profile of DCAT Application Profile for Data Portals in Europe); apart from aiming at improving data portability within European Data Portals, the DCAT-AP-SDO schema will support the evolution of European public services by enhancing data discovery networks on the web as its precursor DCAT-AP did (see ISA Programme reference, DCAT-AP and public sector databases). Schema.org homepage reference, 'About Schema.org' section: https://schema.org/docs/about.html DCAT-AP reference: https://op.europa.eu/en/web/eu-vocabularies/dcat-ap DCAT-AP-SDO reference: https://ec-jrc.github.io/dcat-ap-to-schema-org/ ISA Programme reference, DCAT-AP and public sector databases: https://ec.europa.eu/isa2/solutions/dcat-application-profile-data-portals-europe_en"
UTF-8 is included in within the Belgian Interoperability Framework's website in order ease its implementation and use. See: https://www.belgif.be/en/specifications
3 Member States are recommending WS-BPEL in their ICT National Catalogues. They belong to Cyprus, France and Germany. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'The main purpose of CPOV is to provide a reusable data model for describing public organisations in the European Union. It manages a public portfolio that facilitates the discovery of which public authorities and departments are responsible for given areas of the public task. Therefore, CPOV provides a standarized frame which facilitates interoperability, and the visibility of government data. CPOV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-organisation-vocabulary'
ADMS supports the evolution of European Public Services by enhancing the discoverability and reuse of interoperability solutions. ADMS on Joinup: https://joinup.ec.europa.eu/solution/asset-description-metadata-schema-adms/about ADMS Specification W3C: https://www.w3.org/TR/vocab-adms/
XAdES is included in several national catalogues from Member States. A total of 7 countries listed the XAdES within their national catalogues. See CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
"The purpose of the specification is not directly related to the visibility of public administrations' procedures, rules, data or services. Publiccode.yml focuses on the reuse of software developed by public bodies, ensuring the efficiency and effectiveness of the budget dedicated to address specific needs. So, administrations can benefit from other administrations services with the implementation of the specification, however, it is not directly impacting comprehensibility of their procedures, rules, data or services. Publiccode.yaml documentation: https://docs.italia.it/italia/developers-italia/publiccodeyml-en/en/master/index.html"
The adoption of TIFF/IT as high quality image format for exchanging data does not hamper the scalability of systems. It is widely adopted for this purpose because it is independent of any platform or software. TIFF/IT ISO reference: https://www.iso.org/standard/34342.html
JPEG is already associated to an EIRA ABB in the EIRA Library Of Interoperability Specifications (ELIS). Specifically, JPEG can define the interoperability aspects of the "Representation" ABB from the EIRA Semantic view. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/solution/elis/release/v100
'The purpose of IPSec is to secure communications over a Network which does not simplify the delivery of European public services. IPSec reference, What IPSec Does: https://datatracker.ietf.org/doc/html/rfc4301#section-3.1'
'The specification addresses semantic aspects thus data security and data privacy issues are addresses by other means. The specification does not prevent the use of any security means. As noted previously, the chief architect of XBRL GL designed the Specification was deeply engaged in the W3C’s security specifications development. While XBRL GL itself does not inherently enable secure exchange, it has been designed with secure exchange in mind.'
'While the purpose of this specification is not related to ensuring the protection of personal data managed by Public Administrations, IDSA does define their privacy policy regarding personal data. Furthermore, data sovereignty is one of the pillars of IDS, which aims enables you to self-determine how, when and at what price others may use it across the value chain. IDSA Privacy Policy: https://internationaldataspaces.org/privacypolicy/ IDSA Data Sovereignty: https://internationaldataspaces.org/why/data-sovereignty/'
'5 Member States are recommending IPsec in their ICT National Catalogues. This Member States are France, Greece, Malta, Netherlands and Spain. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
'There has not been found any Member State recommending the DPV specification. DPV specification: https://w3c.github.io/dpv/dpv/ DPV primer document: https://w3c.github.io/dpv/primer/#introduction'
'The OAIS reference model provides a common framework for digital preservation that is designed to be interoperable between different systems and organizations. It defines a set of concepts and principles that can be used to guide the development of digital preservation systems, and it provides a framework for understanding the interactions between different components of a digital preservation system. OAIS specification: https://public.ccsds.org/Pubs/650x0m2.pdf'
'OpenTelemetry is currently in its 33rd version. Changes to the specification are versioned according to Semantic Versioning 2.0 and described in CHANGELOG.md. Layout changes are not versioned. Specific implementations of the specification should specify which version they implement. Changes to the change process itself are not currently versioned but may be independently versioned in the future. Furthermore, the specification has a section dedicated to past and futures milestones. OpenTelemetry Versioning: https://github.com/open-telemetry/opentelemetry-specification/#versioning-the-specification OpenTelemetry Milestones: https://github.com/open-telemetry/opentelemetry-specification/milestones'
'According to the 5 star Open Data model suggested by Tim Berners-Lee about how to publish linked data, the second star corresponds to the availability of data as structured data. ebXML is a standard that proposes an XML-based infrastructure enabling the user to store data in a structured manner. Then, this specification supports the publication of data as open data. ebXML reference, section 1: http://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html#__RefHeading__8798_474791649 Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/en/'
'There are many documents that provide an overview of the usage and functionalities of MIME. Such is the case of a scholar paper which describes the effectiveness of the mechanisms provided by MIME for Internet multimedia mail. MIME: a portable and robust multimedia format for Internet mail: https://link.springer.com/article/10.1007/BF01210505'
There is no Member State that includes CPSV-AP in their national catalogue with the National Interoperability Framework (NIF) aligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'ebXML is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, ebXML can define the interoperability aspects of the Service Registration Service ABB of the EIRA Technical View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/v110'
'DNS is recommended by 9 Member States, including France, Germany, Spain, Sweden, Malta, Cyprus, Greece, Croatia and the Netherlands. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards '
'The purpose of DCAT-AP is not related to the protection of personal data, therefore this critierion is not applicable to the specification. DCAT-AP Specification: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/dcat-application-profile-data-portals-europe/release/200'
As a vocabulary, the implementation of CLV can be tested using methods like SHACL shapes and using semantic reasoners to ensure that the implementation is well-formed. These validation mechanisms can be used with open source tools or lite versions of tools like GrapghDB or Protégé. SHACL validation: https://graphdb.ontotext.com/documentation/free/shacl-validation.html#what-is-shacl-validation Semantic Reasoners List: http://owl.cs.manchester.ac.uk/tools/list-of-reasoners/
'After researching there has been no success finding any recommendation from any European Member State. ETSI EN 319 422 reference: https://www.etsi.org/deliver/etsi_en/319400_319499/319422/01.01.01_60/en_319422v010101p.pdf'
Although the main purpose of the specifications is not the preservation of information it can be used in the context of eArchiving. An example of this aim is DCAT and DCAT-AP, data catalogues vocabularies built around RDF and which are used with the purpose of describing datasets included in data catalogues. The enrichment by means of metadata according to RDF schema could help to the long term preservation of digital documents.
The purpose of the specifications is not related to the availability of interfaces with internal information systems. Therefore, this criterion is not applicable to this specification. TSP IETF reference: https://tools.ietf.org/html/rfc3161
'In order to meet the standard protocol needs, LDAP can not be customised. However, OpenLDAP can be customised. LDAP IETF reference: https://tools.ietf.org/html/rfc4511 Jumpcloud reference: https://jumpcloud.com/blog/difference-between-ldap-openldap-active-directory'
'According to this specification, data portability raises a series of security concerns that need security controls mechanisms. The CSCs need to classify the data according to how sensitive is its content; more sensitive data need a higher level of security controls applied. There are also the security controls relating to the operation of the application (firewalls, authentication, encryption and so on). ISO 19941: https://www.iso.org/obp/ui/en/#iso:std:iso-iec:19941:ed-1:v1:en'
'AMPQ can be found in the EIRA Library of Interoperability Specifications (ELIS) under the "Data Exchange" ABB in the Technical Application View. EIRA Library of Interoperability Specifications (ELIS): https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/version-610'
'ETSI’s standards-making process has been clearly defined after years of experience. The organisation has adopted the open approach which means direct participation and consensus as a basis to develop standards. All the stakeholders have the opportunity to participate directly in the process of standardisation through the technical committees created to develop ETSI’s technical specifications and standards. The decision-making process includes a public review, where stakeholders involved can provide technical feedback in order to enhance and maximize the quality and accuracy of the standards. ETSI standard making: https://www.etsi.org/standards/standards-making'
'The purpose of YAML is not related to provide means for restriction of access to information/data. Therefore, this criterion is considered not applicable to this specification. YAML specification: https://yaml.org/spec/1.2.2/'
The specification fosters innovative solutions as the current web-enabled context, where innovative eGovernment and eCommerce applications are increasingly deployed, it has become essential to provide machine-readable forms (generally in XML) of the contents of the text. LegalRuleML reference: http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/legalruleml-core-spec-v1.0.html
The purpose of HTML is not related to organisational interoperability. Therefore, this criterion is not applicable to the specification. HTML W3C reference: https://www.w3.org/TR/html401/
The purpose of IPv4 is not related to e-accessibility. Therefore this criterion is considered not applicable specification.
"The PROV family of documents has been developed and maintained by the PROV working group. Nonetheless, the working group has been already dissolved, given that the specification's development is considered to be finalized and closed. PROV WG Charter: https://www.w3.org/2011/01/prov-wg-charter PROV Primer document: https://www.w3.org/TR/prov-primer/"
'As it happens with all Core Vocabularies, the ADMS specification can be extended for specific purposes on determined use cases, as it is a profile of DCAT. ADMS Specification W3C: https://www.w3.org/TR/vocab-adms/'
'The publiccode.yml specification does not specifically address the protection of personal data managed by public administrations. Its primary focus is on standardising the metadata related to public sector software to enable efficient reuse and sharing across administrations. While it supports interoperability and transparency, it does not include provisions for safeguarding personal data, nor does it offer guidelines related to privacy or data protection standards in public administration systems. Publiccode.yaml documentation: https://docs.italia.it/italia/developers-italia/publiccodeyml-en/en/master/index.html'
'The ELI system does not inherently provide means for restricting access to information or data. Therefore, this criterion is considered not applicable to this specification. ELI reference: https://eur-lex.europa.eu/eli-register/about.html'
After searching in the different official European websites, there is no evidence of any cross-border project that use HTML4 nor explicit agreements involving the usage of the specification.
'IPv6 offers a larger address space compared to IPv4, allowing public services to have unique, globally routable IP addresses for every device. This can simplify direct access to various administrative services without the need for complex NAT (Network Address Translation) configurations. IPv6 IETF: https://www.rfc-editor.org/rfc/rfc2460'
'iCalendar provides sets of data values that are valid for each property and parametre. The conformance of such a property or parametre is defined as plain text and can be autmatically assessed by using the iCalendar Validator. iCalendar specification: https://www.rfc-editor.org/rfc/rfc5545 iCalendar Validator: https://icalendar.org/validator.html'
'XBRL International has a public reviewing period for all of its specifications. XBRL GL consultations can be conducted by XBRL International members and " volunteers" using the "public working drafts". These public working drafts are available in https://specifications.xbrl.org/spec-group-index-xbrl-gl.html https://www.xbrl.org/the-consortium/get-involved/navigating-your-journey-as-a-volunteer/the-standards-development-process-overview/ Please see also further instructions on how to contribute or take part in the specification development: https://specifications.xbrl.org/faq.htm'
PNG is an ISO standard and as all ISO standards, they have to be paid to access its content. However, it can be checked out in W3C website where the content is aligned with the ISO standard. PNG ISO reference: https://www.iso.org/standard/29581.html PNG W3C reference: https://www.w3.org/TR/PNG/
'The specification introduces certain aspects that can contribute to enabling the secure exchange of data by providing identity and access management in International Data Spaces, which means that there is a strong concern regarding this. It guarantees secure communication channels and authentication mechanisms, thus improving data protection during the data exchange between different systems and services. DAPS: https://github.com/International-Data-Spaces-Association/IDS-G/tree/main/Components/IdentityProvider/DAPS'
'UBL fosters data processing as it is a specification used to exchange information between systems and parties with a specific format. Therefore, by applying structure to documents and providing the data types expected, the usage of UBL can be useful for trustworthy data processing. In the case of security, there are no provisions. UBL v2.3 reference: http://docs.oasis-open.org/ubl/os-UBL-2.3/UBL-2.3.html'
"The specification is included within the EIRA Interoperability Specification Library (ELIS) listed as a possible specification to be used for implementing two of EIRA's ABBs. Moreover, IETF 3161 Time Stamp Protocol (TSP) is considered as the basis of the European Standard Electronic Signatures and Infrastructures (ESI); Time-stamping protocol and time-stamp token profiles from ETSI. Within the document, it is recognised as the basis to which ETSI standard applied constraints. ETSI Catalogue: https://www.etsi.org/standards-search#Pre-defined%20Collections ETSI EN 319 422: Electronic Signatures and Infrastructures (ESI); Time-stamping protocol and time-stamp token profiles "
The W3C Royalty-Free IPR licences granted under the W3C Patent Policy apply to all W3C specifications, including W3C data on the web best practices. W3C Patent practice: https://www.w3.org/TR/patent-practice#ref-AC
'There have been found some studies assessing UTF-8 in terms of effectiveness. For example, ""A case study in SIMD text processing with parallel bit streams: UTF-8 to UTF-16 transcoding"" or a study on the influence of UTF coded data in HDB-3 operation efficiency. A case study in SIMD text processing with parallel bit streams: UTF-8 to UTF-16 transcoding: https://dl.acm.org/doi/abs/10.1145/1345206.1345222 Compatibility of UTF-8 Encoding System to HDB-3 Scrambling Method: https://koreascience.kr/article/JAKO201322045164159.page '
The purpose of LegalDocML is not related to the publication of public data as open data. Therefore, this criterion is not applicable to this specification. Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/en/ LegalDocML reference: https://www.oasis-open.org/committees/legaldocml/charter.php
ETSI’s Intellectual Property Rights Policy is based on Standard Essential Patents (SEP). The policy implemented by the standardisation organisation seeks to reduce risks and ensure that the standards are available under (F) RAND basis and Royalty-free, it means with no cost or fee to be paid when possible. See: https://www.etsi.org/intellectual-property-rights
'LDAP is used by European Insitutions. Moreover, it is possible to search European Laws that mention LDAP as part of common European information system. It can be found through EurLex, the European Gateway for regulation. In "Amended proposal for a REGULATION OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL establishing an action programme for customs in the European Union for the period 2014-2020 (Customs 2020) and repealing Decision N°624/2007/EC", LDAP is mentioned as one of the Common European Information Systems, in the Multi-Annual Financial Framework for the period 2014-2020. Eurlex reference: https://eur-lex.europa.eu/search.html scope=EURLEX&text=ldap&lang=en&type=quick&qid=1711091678660&page=2 Amended proposal reference: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A52012PC0464&qid=1711091678660 '
The purpose of the Core Location Vocabulary is not related to e-accessibility. Therefore, this criterion is considered not applicable to this specification. CLV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-location-vocabulary
There are existing documentation and studies assessing the effectiveness and efficiency of SMTP. The document referenced below is a practical study assessing the e-mail communication thought SMTP. This document studies how SMTP makes e-mail communication more efficient. Practical study SMTP: https://www.researchgate.net/publication/227859099_A_Practical_Study_of_E-mail_Communication_through_SMTP
'The E-ARK has been a project funded by the European Commission, and has now become a standard used for the development of e-archiving solutions, therefore E-ARK CSIP is a European Standard. E-ARK CSIP specification: https://earkcsip.dilcis.eu/#introduction e-archiving projects using CSIP: https://www.eark-project.com/stories.html'
PDF/A has the ISO community that supports the development of: International standards, Technical Specifications, Technical Report and Publicly Available Specification. The ISO standardization process: http://www.isotc292online.org/projects/iso-process/
'The DCAT specification reuses the ODRL specification, which was included in the SPECIAL initiative under the 2020 Horizon program. Scalable Policy-aware linked data architecture for privacy, transparency and compliance reference: https://cordis.europa.eu/project/id/731601/results DCAT (v2.0.0) reference: https://www.w3.org/TR/vocab-dcat/ '
'The purpose of ebXML is not related to te-accessiblity. Therefore, this criterion is not applicable to this specification. ebXML reference: http://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html'
'The message-level security standards employed by ebXML rely on XML Security operations such as XML Signature and XML Encryption. As described in the Oracle document about security features, the XML Encryption mechanism allows for the encryption of digital content, making data more secure and trustworthy. ebXML security: https://www.oracle.com/technical-resources/articles/enterprise-architecture/ebxml-security1.html XML Encryption: https://www.w3.org/Encryption/2001/ ebXML RegRep OASIS reference: https://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html'
'The purpose of GITB TDL is not related to the comprehensibly of administrative procedures, rules data, and services. Therefore this criterion is not applicable to this specification. GITB TDL reference: https://www.itb.ec.europa.eu/docs/tdl/latest/introduction/index.html#what-is-the-gitb-tdl'
The specification is included in 2 Member States' catalogues of recommended specifications. Examples of Member States including SAML 2.0 on their catalogues are Portugal and Slovakia. See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'The IPsec specification is included in the GRID4EU project. The GRID4EU project focuses on how distribution system operators can dynamically manage electricity supply and demand, which is crucial for integration of large amounts of renewable energy, and empowers consumers to become active participants in their energy choices. GRID4EU project: https://cordis.europa.eu/project/id/268206'
'ETSI TS 119 512 specification is distributed from the ETSI platform. ETSI supports European regulations and legislation through the creation of Harmonised European Standards. ETSI’s mission is to provide platforms where interested parties come together and collaborate on the development and promotion of standards for Information and Communication Technology (ICT) systems and services. ETSI TS 119 512 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.02_60/ts_119512v010102p.pdf'
The purpose of PAdES is not related to the visibility of administrative information, data or services. Therefore, this criterion is not applicable to this specification. PAdES ISO reference: https://www.iso.org/standard/67937.html PAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/102700_102799/10277801/01.01.01_60/ts_10277801v010101p.pdf
The purpose of HTTPS is not related to the long-term preservation of electronic records and other kinds of information. Therefore, this criterion is not applicable to this specification.
'SAREF releases do not foresee a public review. Releases and extensions are just published while reviewing is done internally by the ETSI Technical Committee SmartM2M. SAREF Technical Specification: https://www.etsi.org/deliver/etsi_ts/103200_103299/103264/03.01.01_60/ts_103264v030101p.pdf ETSI Technical Committee SmartM2M: https://www.etsi.org/committee/smartm2m'
JSON is defining a set of rules to format data in order to ensure the proper data exchange between applications and platforms. Even defining rules, it can not be considered as a data model in itself, therefore, JSON is not defining a cross-sector data model.
CPOV is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, CPOV can define the interoperability aspects of the "Core Data Model" and "Data" ABBs of the EIRA Semantic View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/solution/elis/release/v100
'There are existing documentation and studies assessing the effectiveness of ETSI TS 119 612 together with other specifications. The "eIDAS Regulation and Its Impact on National Legislation: The Case of the Slovak Republic" study, focuses on the critical analysis of the adopted eIDAS Regulation, its impact on the existing e-signature legislation and the amendments adopted, which are necessary to unify the legal framework for electronic signature of the Member States of the European Union. Moreover, the legal aspects of the e-signature are analised. "eIDAS Regulation and Its Impact on National Legislation: The Case of the Slovak Republic" study: https://www.mdpi.com/2076-3387/12/4/187'
"There is no evidence of available studies directly assessing the efficiency of this specification. However, there are some use case evaluations submitted by (non-)European administrations where effectiveness is analysed. It is the case of Scotland, which publicly depicted the implementation process of NUTS and explicitly shows the way in which the specification can be adapted to disparate territories. EUROSTAT reference, NUTS Principles and Characteristics section: https://ec.europa.eu/eurostat/web/nuts/principles-and-characteristics Scotland government reference, Scotland's NUTS implementation document: https://www.gov.scot/publications/review-nomenclature-units-territorial-statistics-nuts-boundaries/"
'The efficiency of WAI-ARIA involves various methods, such as usability studies, user testing, and evaluation against established accessibility standards. As the specification undergoes evaluation, numerous cases and studies investigate its utilization in web content for e-accessibility purposes. ACM Digital Library reference: https://dl.acm.org/doi/10.1145/3412841.3442066 WAI-ARIA Practices reference: https://wai-aria-practices.netlify.app/aria-practices/ WAI-ARIA reference: https://www.w3.org/TR/wai-aria/ '
CSV is publicly available for implementation and use, and therefore for everyone to study, for free on IETF webpage. See: https://tools.ietf.org/html/rfc4180
The application of the once-only principle in all EU Member States public administrations aims at reducing the administrative burden. To achieve this, interoperability between public administrations is a sine qua non condition. SOAP addresses and facilitates the exchanging of information within cross border services and impacts positively the development of eGovernment.
Although there are no specific studies or documentation about the "Standard for Public Code", there are several studies concerning the importance to include open source solutions and software to public administrations and their benefit to administrations, businesses and citizens. Adopting open source software in public administration: The importance of boundary spanners and political commitment https://www.sciencedirect.com/science/article/abs/pii/S0740624X15000258 A study on the introduction of Open Source Software in the Public Administration: https://link.springer.com/chapter/10.1007/0-387-34226-5_16 Open source software for the public administration: https://www.researchgate.net/publication/228770161_Open_source_software_for_the_public_administration
Not enough information has been found to answer positively or negatively to this criterion. No information related to the governance process of the Better regulation has been found to support the answer to the criterion. European Comission webpage: https://ec.europa.eu/info/strategy/decision-making-process_en
'There exist some assessments indirectly addressing the effectiveness of OData in industry (e.g., Microsoft Azure), or documentation focusing on the improvement of the OData specification (e.g., the future release, OData.Neo). OData assessments reference: https://www.odata.org/blog/ Microsoft Open Technologies (China) reference: https://www.odata.org/blog/ms-open-tech-china-introduces-azure-based-open-data-solution-using-ckan-and-odata-technologies/ OData.Neo reference: https://github.com/OData/OData.Neo'
UTF-8 is maintained by IETF which is an international community developing open standards. See: https://www.ietf.org/about/
The Web Services Security (WS-Security) main function is to reinforce integrity and confidentiality of the messages used by SOAP specification. The purpose of SOAP 1.2 is to store, transport and exchange data through interoperable systems. Moreover WS-Security helps, SOAP 1.2 that uses XML which defines a set of rules for encoding documents in a human-readable format and machine-readable format enhancing the reusability of data and stimulating the interoperability of systems and services.
The ISO 14533-1:2014 which refers to CAdES is not available for free for everyone to study. Payment is needed to reach access to the standard. CAdES ISO reference: https://www.iso.org/standard/64756.html
There is no adoption of competing, new European Standards foreseen covering the same area with the same level of security as TLS 1.3.
'There is no Member State that includes WAI-ARIA in their national catalogue with The National Interoperability Framework (NIF) in alignment with the three categories 1. Conceptual model for integrated public services provision, 2. interoperability layers, and 3. interoperability principles. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
Each of the specification approval phases (TAB, Council, Public RfCs / Consultation) allow for objections and appeals. See: https://www.rd-alliance.org/groups/creating-and-managing-rda-groups/working-group-outputs.html
'YAML can enable the exposure of interfaces, particularly in the context of APIs and other service configurations. By using YAML to define and document interfaces, developers and administrators can clearly communicate the structure, endpoints, methods, and parameters of their services. Some API specifications use YAML to define the structure of API requests and responses. YAML specification: https://yaml.org/spec/1.2.2/ OpenAPI definitions in YAML https://swagger.io/docs/specification/basic-structure/'
The purpose of TLS 1.2 is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification.
'File transfer is an essential component of many information exchange processes in public services. FTP can be used as a means to transfer files between different systems and entities involved in public service delivery. It provides a standardized protocol for file transfer, enabling interoperability and efficient exchange of information. In this sense, it can be said that the specification simplifies the delivery of European public services. FTP Specification Reference: https://datatracker.ietf.org/doc/html/rfc959 '
ELI is used for the EUR-Lex, the site where EU Institutions publish their datasets for their reuse. In there, it is used to improve the shareability, researchability and interoperability when processing legal data developed by the different Member States. EU Open Data Portal Data sets: https://data.europa.eu/euodp/en/data/group/eli?groups=eli ELI reference: https://eur-lex.europa.eu/eli-register/about.html 5-star linked open data: https://www.w3.org/DesignIssues/LinkedData.html
'The purpose of NFVI is not related to the implementation of the once-only principle. Therefore, this criterion does not apply to this specification. NFVI Deliver, Infrastructure Overview section 4: https://www.etsi.org/deliver/etsi_gs/NFV-INF/001_099/001/01.01.01_60/'
SMTP can be found for free along within the European Collaborative Platform, Joinup. SMTP solution in Joinup platform: https://joinup.ec.europa.eu/solution/simple-mail-transfer-protocol/distribution/simple-mail-transfer-protocol
'Any cross-border project using internet, uses HTTP Cookies. An interesting example is Europeana, a project that aims to provide digital access to European cultural heritage material. Europeana uses HTTP Cookies to imporve the experience on the website, keeping the user signed in, and remembering navigation preferences. Europeana Cookies policy: https://www.europeana.eu/en/rights/cookies-policy'
'HTTP Cookies is based on a set of syntax rules that define all the requirements met to provide the functionality. There are no extensions that can be added on top of the main functionalities HTTP Cookies is designed for. IEFT Request for comments: https://datatracker.ietf.org/doc/html/rfc6265#section-4 HTTP Cookies reference: https://developer.mozilla.org/en-US/docs/Web/HTTP/Cookies#creating_cookies'
'Assuming data is retained, the AMQP specification promotes information reuse through filter sets to efficiently reuse relevant information. (Refer to section 3.5.8 Filter Set) OASIS AMQP Reference: http://docs.oasis-open.org/amqp/core/v1.0/amqp-core-complete-v1.0.pdf'
The main purpose of PAdES baseline profile is not related to the preservation of digital information or items. Although, the different profiles defined by the specification are related to the long-term preservation of eSignatures and the materials related to the validation. This capability ensures the availability of signatures and related materials within a long period according to the needs of each implementer.
All specifications are publicly and openly referenced on the RDA web platform at https://www.rd-alliance.org/recommendations-outputs/adoption-recommendations All specifications are deposited in official repositories and have DOIs
"The Better Regulation Toolbox is an internal European Commission resource designed as a complement to the Commission's Better regulation guideline. It provides more specific and operational guidance to those involved with different elements regarding EU legislation The construction of European Laws and policies aims to be proportionate to users needs, rights and duties, in this sense the specifications allows the use of extensions as long as the core elements of the toolbox are maintained. Better Regulation Guidelines and Toolbox reference: https://commission.europa.eu/law/law-making-process/better-regulation/better-regulation-guidelines-and-toolbox_en Better Regulation Toolbox reference: https://commission.europa.eu/document/download/9c8d2189-8abd-4f29-84e9-abc843cc68e0_en?filename=BR%20toolbox%20-%20Jul%202023%20-%20FINAL.pdf"
The purpose of RegOrg is not related to the delivery of multilingual public services. Therefore, this criterion is not applicable to this specification. RegOrg Joinup reference: https://joinup.ec.europa.eu/solution/registered-organization-vocabulary
XAdES (ISO 14533-2:2012) is an ISO standard and as all ISO standards, they have to be paid to access its content. However, it can be checked out in ETSI website where the content is aligned with the ISO standard. XAdES ISO reference: https://www.iso.org/standard/56025.html XAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/101900_101999/101903/01.04.02_60/ts_101903v010402p.pdf
"Section 5 of the specification about confidentiality, security and integrity expresses that the SCASC shall guarantee the integrity and confidentiality of the received information. For instance, in remote signing services with SCAL1 (Section 5.3), the signing key's confidentiality and integrity are ensured by the SCDev that can be activated by the SSASC. Such activation can remain for a given period and/or for a given number of signatures. ETSI TS 119 432: https://www.etsi.org/deliver/etsi_ts/119400_119499/119432/01.02.01_60/ts_119432v010201p.pdf"
'There are extensions avilable for RFC3161. One of the extensions is ANSI X9.95, which specifies the minimum security requirements for the effective use of time stamps in a financial services environment. ANSI X9.95 reference: https://webstore.ansi.org/standards/ascx9/ansix9952022'
"The IT Professionalism Europe (ITPE) publishes some analysis on the EN 16234-1 e-CF component in different sectors of the European economy. The e-Competence Framework is positively evaluated as an effective enabler of SME communications. IT Professionalism Europe (ITPE) reference, Reports & Publications section, 'e-CF for SME’s – competence need analysis' document: https://itprofessionalism.org/app/uploads/2019/08/Competence-need-Analysis.pdf"
'UTF-8 is included in the catalogue of recommended specifications of 10 Member States. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standard'
'There are many online guidelines to assess the conformance of the HTTP Cookies implementation. Furthermore, there are also companies that offer services related to the assessment of HTTP Cookies in order to find vulnerabilities associated with personal data processing and assess the compliance against EU legislation. Nonetheless, no tools or platforms have been found that allow testing of implementations. HTTP Cookies IETF guide: https://datatracker.ietf.org/doc/html/rfc6265#section-4 HTTP Cookies testing tutorial: https://www.guru99.com/cookie-testing-tutorial-with-sample-test-cases.html '
'The OASIS Technical Committee, in charge of the development of OData, operates under RF (royalty-free) on RAND Mode of the OASIS IPR Policy. Therefore, the specification is licensed on a Royalty-free. OASIS Intellectual Property guidelines, section 5.2: https://www.oasis-open.org/policies-guidelines/ipr/'
WS-Security is included in 5 national catalogue of recommended specifications. The The specification is fully aligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'ODRL is intended to be applicable across various platforms, including different operating systems, web platforms, and other technology environments.Whether an application is running on Windows, macOS, Linux, a web-based platform, or any other environment, developers can integrate ODRL support to manage digital rights in a consistent and standardized manner. W3C specification: https://www.w3.org/TR/odrl-vocab/#vocab-core'
The purpose of IPv4 is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification.
'According to the 5 star Open Data model suggested by Tim Berners-Lee about how to publish linked data, the second star corresponds to the availability of data as structured data. WAI-ARIA is intended to be used to increase semantics in programming languages like HTML5 and vector image formats like SVG2, or to be used as an accessibility enhancement technology in other markup-based languages not including support for Accessible Rich Internet Applications (ARIA). Therefore, it eases the publication of open data. WAI-ARIA reference, section 1.1: https://www.w3.org/TR/wai-aria/ Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/en/ '
PDF is a business agnostic document format that can be reused in a cross-domain way.
'SOAP is included in 10 national catalogues of recommended specifications. Among those we can find Spain. The National Interoperability Framework (NIF) of these Member States is fully aligned with at least 2 out of 3 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets NIFO Factsheets Spain: https://administracionelectronica.gob.es/pae_Home/pae_Estrategias/pae_Interoperabilidad_Inicio /pae_Normas_tecnicas_de_interoperabilidad.html#CATALOGOESTANDARES NIFO factsheets: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public-administration-factsheets-2022 CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards '
After checking the different standard catalogues at supra-national level, there is no evidence of the inclusion of CAdES (ISO 14533-1:2014) within any European catalogue of standards. ICT technical specifications: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en CEN search tool catalogue: https://standards.cen.eu/dyn/www/f?p=CENWEB:105::RESET:::: CENELEC search tool catalogue: https://www.cenelec.eu/dyn/www/f?p=104:107:0::::FSP_LANG_ID:25
'The purpose of ETSI TS 119 612 is not related to the publication of public data as open data. Therefore this criterion is not applicable to the specification. ETSI TS 119 612: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf'
'After some research, nothing related to Fair, Reasonable and Non-Discriminatory was found. DCMI About: https://www.dublincore.org/about/ '
XACML is a de-fact standard markup language that is used in a wide variety of solutions, although it does not foster any innovative solutions.
'While genericode is primarily focused on providing a standardized format for representing code lists and controlled values, organizations can take steps to ensure the long-term preservation of data represented in genericode format by implementing appropriate data management and archiving practices. For instance, the specification allows for the inclusion of metadata alongside code values, providing additional context and information. Organizations should ensure that metadata associated with genericode files is also preserved and archived to maintain the integrity and usability of the data over time. Code List Representation (genericode): https://docs.oasis-open.org/codelist/genericode/v1.0/os/genericode-v1.0-os.html'
'While the Dataspace Protocol is not involved in enabling the secure processing of data, important concepts for IDS like "Connectors" and providing a standard on how Datasets are deployed as DCAT Catalogs help improving secure processing of data. IDSA Dataspace Protocol: https://docs.internationaldataspaces.org/ids-knowledgebase/v/dataspace-protocol/overview/readme'
'HTTP specification does offer flexibility in how developers can implement the protocol. The use of terms like "MAY," "SHOULD," and "OPTIONAL" signals that not all features or behaviors are mandatory. HTTP /1.1 RFC 2616 Reference: https://www.rfc-editor.org/rfc/rfc2616.html HTTP/1.1 Semantics, RFC 9110 Reference: https://www.rfc-editor.org/rfc/rfc9110'
'ETSI TS 119 432 was created as a support for electronic signatures and electronic seals according to the trust services for electronic transactions in the internal market and repealing Directive 1999/93/EC (the eIDAS Regulation). The eIDAS Regulation provides for the interoperability of national eID schemes among EU member states. This requires the development of a technology-neutral framework that does not favour any particular technical solution for eID implementation. ETSI TS 119 432: https://www.etsi.org/deliver/etsi_ts/119400_119499/119432/01.02.01_60/ts_119432v010201p.pdf eIDAS Regulation: https://digital-strategy.ec.europa.eu/en/policies/eidas-regulation'
'ETSI TS 119 511 is part of the Electronic Signatures and Infrastructure (ESI) family of specifications and is dependent on some of the protocols and semantics they convey, therefore, this specification is not technology agnostic. ETSI TS 119 511 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119511/01.01.01_60/ts_119511v010101p.pdf'
LDAP is an application protocol for accessing and maintaining distributed directory information services over an Internet Protocol network, which defines the authentication user schema which allows and fosters its reuse in a cross-sector manner. However, it is not defining a data model. LDAP IETF reference: https://tools.ietf.org/html/rfc4511
"CPOV contriubutes to enabling exposure of interfaces in many ways. We can highlight link data from public organizations to other data sets, enable the creation of interoperable catalogues of public organisation in Europe and beyond, browse public organizations by its function, and keep track of the evolution of public organizations. Therefore, it improves the interoperability and reusability of data, allowing organisations to develop API's and web sevices that provide access to this information effectively. CPOV Joinup reference: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/core-public-organisation-vocabulary/distribution/core-public-organisation-vocabulary-version-100-pdf"
EuroVoc is publicly available for implementation and use for free on EuroVoc's webpage. Therefore, it can be reused by the organisations, administrations, open communities, etc. that developed it. EuroVoc webpage: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/eurovoc
The PAdEs Baseline profile is a business domain agnostic specification, meaningch means that it can be reused in a context where eSignatures are needed to develop an activity or solution.
'The Asset Administration Shell (AAS) has a brief definition of conformance assessments, based on the validation of one of the data formats (XML) in section 7.3. Details of the Asset Administration Shell (AAS) https://industrialdigitaltwin.org/en/wp-content/uploads/sites/2/2024/06/IDTA-01001-3-0-1_SpecificationAssetAdministrationShell_Part1_Metamodel.pdf'
'The purpose of SFIA is not related to the simplification of European public services. Therefore, this criterion does not apply to this specification. SFIA reference: https://sfia-online.org/en/sfia-8'
'The specification does indeed allow customisation in the implementation guidelines, making use of the XML customisation options. DCMI Point 3, General Implementation Guidelines: https://www.dublincore.org/specifications/dublin-core/dc-xml-guidelines/ DCMI About: https://www.dublincore.org/about/ '
"As a specification with the aim of helping to represent information which can be documents, persons, physical object or abstract objects, it helps administrations to provide information to stakeholders. Therefore, RDF fosters the visibility of the administration's data and services. As a way to make data reusable, it eases the decision-making process. RDF primer document: https://www.w3.org/TR/rdf11-primer/"
'There is no Member State recommending NFVI in its ICT National Catalogue. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
'The iCalendar document defines the data format and media type of text/calendar, which is independent of any calendar service or protocol, and barely gives provisions on the use of other specifications to mitigate possible privacy threads, and thus, protect personal data. iCalendar specification: https://www.rfc-editor.org/rfc/rfc5545'
'The Asset Administration Shell (AAS) has been included in an initiative covering privacy aspects, the Platform Industrie 4.0 initiative in Germany in the context of the Digital Twins initiative (IDTA). This initiative aims to create an environment where all partners can share manufacturing assets and define in a collaborative manner their specifications in order to make the overall process more integrated. Industrie 4.0 initiative: https://www.plattform-i40.de/IP/Navigation/EN/Home/home.html Details of the Asset Administration Shell (AAS) https://industrialdigitaltwin.org/en/wp-content/uploads/sites/2/2024/06/IDTA-01001-3-0-1_SpecificationAssetAdministrationShell_Part1_Metamodel.pdf'
'The specification has 14 previous releases, which is indicative of sufficient mature for its use in the development of digital solutions/services. There is a link down below which provides documentation for all the releases the specifications has had. DCMI Version History: https://www.dublincore.org/specifications/dublin-core/dcmi-terms/release_history/'
'ECLI implements DCMI, as ECLI is a uniform identifier that has the same recognizable format for all Member States and EU courts. It can contribute to the evolution of European public services as it can describe any web resource, helping and/or enhancing the European services further. DCMI About: https://www.dublincore.org/about/ ECLI Information: https://e-justice.europa.eu/175/EN/european_case_law_identifier_ecli?init=true '
'At the time of elaborating this assessment, this specification is included in the Controlled Vocabulary ABB in the current EIRA Library Of Interoperability Specifications (ELIS). EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /solution/elis/release/600'
'The specification Asset Administration Shell (AAS) is under the Creative Commons Attribution 4.0 International License. So the specification is free to be distributed and only proper attribution to the creators is required. CC-BY-4.0 reference: https://creativecommons.org/licenses/by/4.0/ Details of the Asset Administration Shell (AAS) https://industrialdigitaltwin.org/en/wp-content/uploads/sites/2/2024/06/IDTA-01001-3-0-1_SpecificationAssetAdministrationShell_Part1_Metamodel.pdf'
'There is existing documentation and studies assessing the efficiency of Extensible Forms Description Language. The "Enterprise-level Web Forum Applications with XForms and XFDL" study, presents the first integration of the standardised XML markup for expressing the core processing of a web-based form applications (XForms) with a host language (XFDL) that offers security, precision presentation, a document-centric capability, and other features that contribute to a more rich user experience. However, in the 'Sustainability of Digital Formats: Planning for Library of Congress Collections' report, it is mentioned that there are simpler technologies preferred nowadays. "Enterprise-level Web Forum Applications with XForms and XFDL" study: http://www.pdfpower.com/XML2005Proceedings/ship/74/XFormsAndXFDL_Boyer.PDF "Sustainability of Digital Formats: Planning for Library of Congress Collections" report about XFDL: https://www.loc.gov/preservation/digital/formats/fdd/fdd000580.shtml Extensible Forms Description Language reference: https://www.w3.org/TR/NOTE-XFDL'
'BFO allows the specification to be implemented partially. BFO reference: https://www.iso.org/standard/74572.html'
'After searching in the different official European websites and repositories, there is no evidence that HTTP Cookies is included in an open repository/catalogue of standards at a national level. HTTP Cookies reference: https://developer.mozilla.org/en-US/docs/Web/HTTP/Cookies#creating_cookies'
'There are some optional parts in the REM Structure which can make the structure effectively larger by adding an extension. In the REM-MD Evidence MIME section 0..N, the body is optional, and in the Original Message, the body is optional too. ETSI EN 319 532-3 reference, section 6: https://www.etsi.org/deliver/etsi_en/319500_319599/31953203/01.02.01_60/en_31953203v010201p.pdf'
TLS 1.2 is publicly available for study and use at no cost on the IETF webpage. See: https://tools.ietf.org/html/rfc5246
"The specification has a compliance test in GitHub where any user can access it and execute it to assure the specification's correct implementation. SCIM 2.0 Compliance Test Utility: https://github.com/suvera/scim2-compliance-test-utility"
The purpose of Xfoms 2.0 is not related to data portability. Therefore, this criterion is not applicable to this specification. Xforms 2.0 W3C reference: https://www.w3.org/community/xformsusers/wiki/XForms_2.0
"HTTP doesn't encourage community building, its features as an open standard can support the creation and sharing of data across various platforms, allowing collaboration and innovation among entities or platforms. HTTP /1.1 RFC 2616 Reference: https://www.rfc-editor.org/rfc/rfc2616.html"
'By providing a standardized format for representing calendar data, iCalendar ensures interoperability, making it easier to exchange scheduling and event information across different software and platforms. This facilitates seamless data sharing between European public services, supporting efficient collaboration and coordination among various entities. iCalendar specification: https://www.rfc-editor.org/rfc/rfc5545'
'Following the completion of the research into conformity tests and certifications, a tool has been identified that enables the testing of implementations. The "IPsec Test Suite" can be used to test IPsec implementations for security flaws and robustness problems. Moreover, it also has been found the "MyIKEv2" tool, which is a testing tool for IKEv2/IPsec in Linux. BlackDuck IPsec Test Suite: https://www.blackduck.com/fuzz-testing/defensics/protocols/ipsec.html "MyIKEv2" testing tool: https://www.myikev2.net/ '
'Partial implementations of MIME are common, and they are designed to allow developers to tailor their applications to their specific requirements while still benefiting from the flexibility and compatibility that MIME provides for internet communication. For example, an email client may choose to support only basic text and HTML content types, omitting support for more specialized types like audio or video. MIME specification: https://tools.ietf.org/html/rfc2045'
'The AKN4EU specification does address long-term preservation of data, information, or knowledge. It is designed to facilitate the exchange of legal and legislative information, it does include features that could potentially support long-term preservation efforts. AKN4EU reference: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/akn4eu '
'The specification allows the exchange of authentication and authorization data between parties. It is mainly used to ensure single sign-on (SSO) and by doing so, it secures the exchange of data. It extends SSO across security domains independently from any platform which prevents non-interoperable proprietary technologies. For instance, a relevant implementation of SAML 2.0 is SAML Web Browser SSO profile. SAML 2.0 Reference: http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-tech-overview-2.0.html SAML 2.0 Web Browser SSO Profile Reference: https://www.ibm.com/docs/en/was-liberty/core?topic=authentication-saml-20-web-browser-single-sign'
SAML 2.0 is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). Specifically, SAML 2.0 can define the interoperability aspects of the "Identity management Component", “Identity Management Service”, “Access Management Component”, and “Access Management Service” ABBs of the EIRA Technical View. See: https://joinup.ec.europa.eu/solution/elis/distribution/eliscataloguev100betaxlsx
'The Core Location Vocabulary specification foresees some requirements that can be implemented incrementally, such as its properties. In this sense, the specification consists of properties and classes, which can be implemented incrementally, depending on the use case. Core Location Vocabulary: https://interoperable-europe.ec.europa.eu/collection/semic-support-centre/solution/core-location-vocabulary/release/100'
'MIME has been found to be distributed through the European-led collaborative platform Joinup. MIME in Joinup: https://joinup.ec.europa.eu/collection/ict-standards-procurement/solution/rfc-2045-multipurpose-internet-mail-extensions-mime'
'The HTTPS specification itself does not have a validator or conformance-checking tool associated with it. However, there are several tools and practices available to assess the implementation and conformance of HTTPS in a web application or server configuration such as the SSL/TLS Certificate Validation. Validation methods for TLS/SSL certificates: https://www.digicert.com/faq/public-trust-and-certificates/what-are-the-validation-methods-for-tls-ssl-certificates'
'There is no conformity test from the OASIS, but there are free online documents that will help you validate the UDDI specification when it is implemented. It is also possible to test UDDI with IBM UDDI Test Registry, to experience the registration process, but without putting the web service in an official register. IBM Test UDDI reference: https://www.ibm.com/docs/es/rsas/7.5.0?topic=standards-universal-description-discovery-integration-uddi UDDI v3 reference: https://www.ibm.com/docs/en/was-zos/9.0.5?topic=services-overview-version-3-uddi-registry'
'XSD 1.1 is maintained by W3C which is an international community developing open standards. W3C Consortium Reference: https://www.w3.org/Consortium/ XSD Reference: https://www.w3.org/TR/2012/REC-xmlschema11-1-20120405/'
'The purpose of YAML is not related to data integrity. Therefore, this criterion is considered not applicable to this specification. YAML specification: https://yaml.org/spec/1.2.2/'
'The ISO 3166-1 specification is integrated in some Authority tables (e.g., Country) of the Publications Office (OP) of the European Union, but the specification as such is not included in any open repository of standards at European level. OP reference, Authority tables: https://op.europa.eu/en/web/eu-vocabularies/authority-tables?msclkid=72f85375b00d11ec9c13d3f9f6befab0'
'The purpose of OAS is not related to multilingualism, therefore, this criterion is not applicable to the specification. OAS specification: https://spec.openapis.org/oas/latest.html#openapi-specification OAS in Github: https://github.com/OAI/OpenAPI-Specification/#participation'
After carrying out information retrieval, no document or study has been found assessing the PAdES in terms of efficiency or effectiveness.
'OAIS provides a reference model framework from which to set responisbilities for organisations involved in the long-term preservation of Information archives. The OAIS specification comprises different strategies in which it can be done, depending on the type of archives or the needs of the designated community, meaning that implementations of the reference model can vary, and therefore can be met partially. OAIS specification: https://public.ccsds.org/Pubs/650x0m2.pdf'
'While the Dataspace Protocol is not involved in protection against unauthorised changes, some aspects of the entire group of IDS specifications, such as the IDS "Connector" concept and metadata provisioning, which improves data traceability and data integrity. IDSA Dataspace Protocol: https://docs.internationaldataspaces.org/ids-knowledgebase/v/dataspace-protocol/overview/readme'
'SAML 2.0 is a format that allows seamless cross-border interoperability between systems, independently of existing implementations. To demonstrate this fact is worth to take into account that in the context of Connecting Europe Facility (CEF), the CEF eID Building Block has been developed to support the (eiDAS) regulation. This building block includes technical specifications composing the “eiDAS eiD profile”. Among these specifications, the eiDAS SAML Attribute Profile defines the SAML 2.0 attributes to be used for the assertion of natural and legal person identity between eIDAS nodes. Regulation (EU) No 2021/1153 Reference: https://eur-lex.europa.eu/legal-content/en/TXT/?uri=CELEX%3A32021R1153 eID Building Block Reference: https://hadea.ec.europa.eu/news/eid-discover-one-cef-building-blocks-2022-06-27_en'
"The Better Regulation Toolbox is an internal European Commission resource designed as a complement to the Commission's Better regulation guideline. It provides more specific and operational guidance to those involved with different elements regarding EU legislation. The construction of European Laws and policies aims to be proportionate to users needs, rights and duties, therefore the specification defines the development of public policies and laws with adaptability and applicability in multiple contexts at it's core. In this sense being able to implement the guidelines incrementally and separately is key. Better Regulation Guidelines and Toolbox reference: https://commission.europa.eu/law/law-making-process/better-regulation/better-regulation-guidelines-and-toolbox_en Better Regulation Toolbox reference: https://commission.europa.eu/document/download/9c8d2189-8abd-4f29-84e9-abc843cc68e0_en?filename=BR%20toolbox%20-%20Jul%202023%20-%20FINAL.pdf"
"GraphQL is mature enough to consider its use, or suitability, in the development of digital solutions and services. Although its ideonality will depend on the user's preferences, GraphQL is demonstrating its potential in data requests across multiple servers and systems. GraphQL is not a de facto specification intended to replace any other specification for data extraction and manipulation (such as OData or REST), as its implementation will depend on the type of service that incorporates it. GraphQL specification: https://spec.graphql.org/October2021/#sec-Overview OData specification: http://docs.oasis-open.org/odata/odata/v4.0/errata03/os/complete/part1-protocol/odata-v4.0-errata03-os- part1-protocol-complete.html#_Toc453752197 REST API specification: https://restfulapi.net"
'While TSP itself does not encrypt or secure data, it provides an essential layer of trust and verification to data transactions, enhancing security when integrated with other security measures. The examples below demonstrate how adding reliable timestamps to data operations supports the secure exchange of information by ensuring transparency, accountability, and the integrity of data records. TSP IETF reference: https://tools.ietf.org/html/rfc3161'
'The specification supports data driven service interoperability like opening of data and reporting. Danish business registry sharing all annual financial statements in XBRL as open data: https://datacvr.virk.dk/data'
'DCAT-AP does not directly address secure processing of data, but it can promote best practices for metadata description and publication that indirectly contribute to the security of data processing. By providing metadata elements to describe the technical details of data services, it can help data publishers provide information about security measures. Additionally, using standard vocabularies and identifiers can facilitate interoperability of data services that require secure access to data. Finally, it is often used with other standards and guidelines, such as FAIR principles and DMP guidelines, that provide additional guidance on how to ensure secure processing of data. DCAT-AP Specification: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/dcat-application-profile-data-portals-europe/release/200'
SAML 2.0 is publicly available for free on OASIS Webpage. See: http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-tech-overview-2.0.html
LDAP is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, LDAP can define the interoperability aspects of the “Service Registration Service” and “Service Registry Component” ABBs of the EIRA Technical Infrastructure View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/solution/elis/release/v100
The TLS 1.2 is published as a reusable solution in Joinup, the collaborative platform for Reusable IT Solutions funded by the European Commission. See: https://joinup.ec.europa.eu/solution/tls-rfc-5246-transport-layer-security-protocol
'Being XML-based, UBL can uniformily reuse data, however, there are no specific provisions addressing this topic. UBL v2.3 reference: http://docs.oasis-open.org/ubl/os-UBL-2.3/UBL-2.3.html'
'CIM NGSI-LD API is not included in any national catalogue of recommended specifications whose Member State NIF has a high performance on interoperability according to NIFO factsheets. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
'The publiccode.yml specification does allow for customisation. It provides a flexible framework for documenting public sector software, with core fields to ensure consistency, while allowing optional fields to be adapted based on specific needs. This flexibility enables public administrations to tailor the metadata to reflect unique project or organisational requirements, without being overly prescriptive. As such, it supports EIF Recommendation 8 by providing a standard that can be adapted to different contexts rather than enforcing a rigid, technology-specific structure. Publiccode.yaml documentation: https://docs.italia.it/italia/developers-italia/publiccodeyml-en/en/master/index.html'
'The ETSI TS 119 512 specifiction system architecture for preservation, includes a preservation interface that is provided by the preservation service and used by the client. ETSI TS 119 512 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.02_60/ts_119512v010102p.pdf'
The purpose of PDF/A is not related to e-accessibility. Therefore, this criterion is considered not applicable to this specification. PDF/A reference: https://www.iso.org/standard/38920.html https://www.iso.org/standard/50655.html
There is no Member State that includes SAMM in their national catalogue with The National Interoperability Framework (NIF) aligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'The ESPD cannot be customised given that it is based on the Universal Business Language (UBL) which is immutable. ESPD Business handbook: https://docs.ted.europa.eu/ESPD-EDM/latest/xml_business_handbook.html UBL specification: https://docs.oasis-open.org/ubl/UBL-2.3.html'
'The specification does not indicate that relevant information is allowed to be reused, meaning that all information needs to be provided whenever it is needed. ETSI TS 119 612 specification: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf '
The main purpose of this Core Vocabulary is to support the exchange of information between organisations that define criteria and organisations that respond to these criteria by means of evidences. This Core Vocabulary helps to comprehend the administrative rules and data of public administration. CCCEV reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-criterion-and-core-evidence-vocabulary
'Genericode encourages collaboration as it was created by OASIS, a non-profit and open consortium dedicated to standardisation. Both members and non-members of the Code List Representation TC are welcome to participate in the unmoderated Code List Representation Developer Mail List by subscribing at the OASIS mail list manager if any discussion about genericode arises. Furthermore, there is a public GitHub with the development and maintenance of the documentation and artefacts associated with OASIS genericode. OASIS Code list Representation TC: https://groups.oasis-open.org/communities/tc-community-home2?CommunityKey=7558fd85-f7ac-4dd7-b57b-018dc7d3f6f7 Code List genericode GitHub: https://github.com/oasis-tcs/codelist-genericode'
'XHTML is a superseded specification that evolved from HTML4 using XML and became a W3C recommendation on 26 January 2000. It has seen several updates, including XHTML 2, which was recommended on 31 May 2001. However, HTML5 has largely replaced XHTML, retaining many of its strengths, such as stricter syntax, while offering improved features, better browser compatibility, and a more modern approach to web development. XHTML W3C reference: https://www.w3.org/TR/xhtml1/ XHTML 2 Reference: https://html.spec.whatwg.org/multipage/introduction.html#history-2 HTML5 W3C Reference: https://html.spec.whatwg.org/multipage/'
'In UDDI, each register must establish its information protection policy, establishing nodes, which protect the data. Each register can have one or more nodes, and contribute to accessibility of web service metadata. Moreover, nodes can use authInfo elements, which are optional elements in API calls for publication, research and subscription API sets, with the objective of control the access. Access control UDDI reference: http://www.uddi.org/pubs/uddi_v3.htm#_Toc85908215 AuthInfo elements UDDI: http://www.uddi.org/pubs/uddi_v3.htm#_Toc85908057'
'Such means as restriction of access to information/data can be provided as SOAP extensions using the SOAP extensibility mode. The SOAP Messaging Framework does not directly provide any mechanism for dealing with it directly. SOAP Reference, section 7 Security Considerations: https://www.w3.org/TR/soap12/#secconsiderations'
'The specification uses the TestBed service to validate GraphQL queries against GraphQL schemas and contributes to enabling the delivery of European public services. Test Bed offers support for projects using GraphQL by launching a new GraphQL validator to validate queries against their target schemas. The validator is based on the GraphQL reference implementation and expects as input the query to validate as well as the target schema. TestBed & GraphQL reference: https://joinup.ec.europa.eu/collection/interoperability-test-bed-repository/solution/interoperability-test-bed/news/new-graphql-validation-service'
'HTTPS is being used by the TESTA (Trans European Services for Telematics between Administrations) network service, a cross border project that provides a European backbone network for data exchange between a wide variety of public administrations. HTTPS specification: https://tools.ietf.org/html/rfc2818 TESTA project: https://ec.europa.eu/isa2/solutions/testa_en'
"The specification is included in two Member States' catalogues of recommended specifications. These Member States are Malta and the Netherlands. National catalogue Malta: https://mccaa.org.mt/Section/Content?contentId=1243 National catalogue The Netherlands: https://www.forumstandaardisatie.nl/open-standaarden/lijst"
HTML can be found for free along within the European Collaborative Platform, Joinup. HTML in Joinup platform: https://joinup.ec.europa.eu/solution/html-401-specification
"In the specification's documentation there is a specific part where is mentions the extension of SMP and the use of it as optional. SMP OASIS reference: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505009"
'The Asset Administration Shell (AAS) has specific provisions regarding encryption of data shared among partners that allow the confidentiality of data. Specifically the specification encrypts the data once it is packed. Furthermore, the specification also allows third party extensions to conform to more strict encryption. Security aspects of the Asset Administration Shell: https://admin-shell-io.github.io/aas-specs-antora/IDTA-01004/v3.0/introduction.html Details of the Asset Administration Shell (AAS) https://industrialdigitaltwin.org/en/wp-content/uploads/sites/2/2024/06/IDTA-01001-3-0-1_SpecificationAssetAdministrationShell_Part1_Metamodel.pdf'
XML defines an abstract data model called "the XML Tree" that is used to structure XML documents. It is therefore reused when using XML for exchanging data across sectors. See: https://www.w3schools.com/xml/xml_tree.asp
'The purpose of DPV is not related to data access, therefore, this criterion is not applicable to the specification. DPV specification: https://w3c.github.io/dpv/primer/'
'The purpose of WAI-ARIA is not related to the secure of data exchange. Therefore, this criterion is not applicable to this specification. WAI-ARIA reference: https://www.w3.org/TR/wai-aria/'
The purpose of TSP is not related to the delivery of multilingual public services. Therefore, this criterion is not applicable to the specification. TSP IETF reference: https://tools.ietf.org/html/rfc3161
'The E-ARK CSIP Specification is not related to multilingualism. Therefore, this criterion is not applicable to the specification. E-ARK CSIP specification: https://earkcsip.dilcis.eu/#introduction'
'ELI is a business-specific specification that is focused on the identification and definition of metadata for legal documents at the European Level. While it has the potential to be adapted or expanded to accommodate other business needs, there is currently no evidence of implementations reflecting such modifications. ELI reference: https://eur-lex.europa.eu/eli-register/about.html ELI Technical Documentation: https://eur-lex.europa.eu/eli-register/technical_information.html'
Core Vocabularies can be used as the foundation of common export formats for data in base registries like cadastral, business registers or public service portals. The Registered Organisation Vocabulary as well as the Core Business Vocabulary can be used to describe and ease the publication of information as open data. There is an example of the publication of data as Linked Open Data: "Greek Tax Authorities business registry published as linked open data using core business and core location". Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/en/ RegOrg Joinup reference: https://joinup.ec.europa.eu/solution/registered-organization-vocabulary/about Core Business Vocabulary reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-business-vocabulary
'The Core Public Organisation Vocabulary facilitates the process for institutions publishing data about public organisations. This Core Vocabulary fosters interoperability and impacts positively on the development of eGovernment. Moreover, CPOV facilitates the reusability of public information, and contributes to the only-once principle, by allowing data to be shared and integrated into different systems and platforms. CPOV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-organisation-vocabulary'
'The specification has been developed to support some requirements that are not mandatory but recommended. For example, some security layers such as the SASL can be implemented, but is not required to run the specification. LDAP SASL reference: https://datatracker.ietf.org/doc/html/rfc2444 '
'The protocol for remote digital signature creation aims to scope comprehensibly administrative procedures, rules data, and services as it can help define the services required for remote digital signature creation, such as signature generation, key management, and timestamping. In addition, it may define the administrative procedures involved in remote digital signature creation, such as user authentication, authorization, and key management. ETSI TS 119 432: https://www.etsi.org/deliver/etsi_ts/119400_119499/119432/01.02.01_60/ts_119432v010201p.pdf'
12 Member States are recommending ODF in their ICT National Catalogues. These Member States are Croatia, Denmark, Estonia, France, Greece, Ireland, Malta, Netherlands, Norway, Slovenia, Sweden and UK. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'The purpose of CPSV-AP is related to the delivery of multilingual public services. All datatype properties with datatype “text” where the value for that property may exist in multiple languages, the property has multiple instances which are tagged with a language identifier for each language in which the value for that property exists. CPSV-AP Joinup webpage: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/core-public-service-vocabulary-application-profile/release/22'
'The purpose of PROV is not related to the delivery of digital services. Therefore, this criterion is not applicable to the specification. PROV Primer document: https://www.w3.org/TR/prov-primer/ PROV Ontology: https://www.w3.org/TR/2013/REC-prov-o-20130430/ PROV Data Model: https://www.w3.org/TR/2013/REC-prov-dm-20130430/'
'12 Member States are recommending CSV in their ICT National Catalogues. Amog those Member States recommending the specification, there is Spain as an example. Spain National Catalogue: https://administracionelectronica.gob.es/pae_Home/dam/jcr:9e2c2877-5103-4934-8440-c60ba2e10c48 /Catalogue_of_Standards_NIF_Spain.pdf CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards '
'SFIA is a framework for defining skills and competences in digital communities. In this sense, the specification is domain-agnostic and can be used in any domain where the ICT sector can operate. SFIA reference: https://sfia-online.org/en/sfia-8'
The OASIS Security Services Technical Committee, in charge of the development of SAML 2.0, operates under RF on RAND Mode of the OASIS IPR Policy. The specification is licensed on a Royalty-free and (F)RAND basis. See: https://www.oasis-open.org/committees/security/ipr.php https://www.oasis-open.org/policies-guidelines/ipr
The purpose of this Core Vocabulary is not related to e-accessibility. Therefore, this criterion is considered not applicable to this specification. CPSV-AP reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-service-vocabulary-application-profile
CAMSS Assessment of ODRL EIF Scenario v1.0.0
CAdES Baseline Profile is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). Specifically, CAdES Baseline Profile can define the interoperability aspects of “e-Seal Creation Service”, “e-Seal Verification and Validation Service”, “e-Signature Creation Service”, and “e-signature Verification and Validation Service” ABBs of the EIRA Technical View. See: https://joinup.ec.europa.eu/solution/elis/distribution/eliscataloguev100betaxlsx
"HTTP is included within at least 12 Member States' ICT Calogues. This Member States are Bulgaria, Croatia, Cyprus, Finland, France, Germany, Greece, Netherlands, Norway, Portugal, Spain and Sweden. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards"
'The specification does not talk about any kind of customisation. ETSI TS 119 614-1 reference: https://www.etsi.org/deliver/etsi_ts/119600_119699/11961401/01.01.01_60/ts_11961401v010101p.pdf'
The specification is included in 8 Member States' catalogues of recommended specifications. This Member States are Estonia, France, Germany, Greece, Norway, Poland, Slovenia and Spain. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'IPsec is included in 5 national catalogues of recommended specifications. They belong to France, Greece, Malta, Netherlands and Spain. The National Interoperability Framework (NIF) of Greece and Spain are aligned with at least 3 out of 4 scoreboards of the EIF Monitoring according to the National Interoperability Framework Observatory (NIFO) factsheets. CAMSS list of standards: https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards National Catalogue of France: http://references.modernisation.gouv.fr/sites/default/files/Referentiel_General_Interoperabilite_V2.pdf National Catalogue of Greece: http://www.e-gif.gov.gr/portal/pls/portal/docs/1/211041.PDF National Catalogue of Spain: https://administracionelectronica.gob.es/pae_Home/pae_Estrategias/pae_Interoperabilidad_Inicio/pae_Normas_tecnicas_de_interoperabilidad.html#CATALOGOESTANDARES NIFO factsheets: https://joinup.ec.europa.eu/collection/national-interoperability-framework-observatory-nifo/nifo-factsheets'
The purpose of Ogg is not related with data portability. Therefore, this criterion is not applicable to this specification. Ogg XIPH reference: https://xiph.org/ogg/doc/rfc3533.txt
'The purpose of IPv6 is not related to long term preservation of electronic records. Therefore, this criterion is considered not applicable to this specification. IPv6 IETF: https://www.rfc-editor.org/rfc/rfc2460'
'The long-term preservation of data needs to be addresses by other standard means. The use of XBRL GL in Turkey for example, leverages digital signatures and certificates so long-term data does not need to be maintained centrally; authentication of data maintained at the enterprise is accomplished through the certificates that prove the integrity of information provided at a later time.'
'GraphQL has many communities that support its maintenance and developments. The most important of them is the GraphQL technical steering committee (TSC) and the GraphQL community in Github, both of which are in constant communication and alltogether develop the specification. GraphQL TSC: https://graphql.org/community/developers/#technical-governance GraphQL Github community: https://github.com/graphql'
'There has not been found any community sharing their data and results on national platforms. However, ETSI TS 119 511 indirectly encourages the creation of communities on national platforms through ETSI membership and directives. ETSI TS 119 511 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119511/01.01.01_60/ts_119511v010101p.pdf'
'XSLT specification enables a variety of implementations, from those supporting only basic functionality to those implementing the full range of the specification’s features. (See Section 27.1-2 Example) XSLT Reference: https://www.w3.org/TR/xslt-30/#basic-conformance'
'CIRCABC (Communication and Information Resource Centre for Administrations, Businesses and Citizens) is a collaborative platform that enables administrations, businesses and citizens to manage and share resources in private workplaces. This platform includes the WAI-ARIA specification, which is meant to facilitate the organisational aspects of this platform. CIRCABC reference: https://joinup.ec.europa.eu/collection/communication-and-information-resource-centre-administrations-businesses-and-citizens-circabc/solution/circabc/about'
'By using ISO/IEC 27001, administrations can ensure that, when needed, data portability can be done ensuring the integrity of data and preserving the confidentiality of the information being exchanged. ISO 27001 reference: https://www.iso.org/obp/ui/#iso:std:iso-iec:27001:ed-2:v1:en'
'The purpose of XHTML is to publish administrative data on the web. By allowing to publish custom data in an understandable format, it fosters the comprehensibility of administrative data. Moreover, it also eases the decision-making process by ensuring the data exchange and data reuse among stakeholders. XHTML W3C reference: https://www.w3.org/TR/xhtml1/'
'LDES is not included in any national catalogue of recommended specifications whose Member State NIF has a high performance on interoperability according to NIFO factsheets. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards'
'After searching in different European platforms, OAS has not been found to take part in the creation of communities along with the sharing of their data and results on European Platforms. OAS specification: https://spec.openapis.org/oas/latest.html#openapi-specification OAS in Github: https://github.com/OAI/OpenAPI-Specification/#participation'
'IEEE Std 802.3-2022 allows for partial implementations, giving organisations flexibility in adopting specific elements based on their needs. For example, a manufacturer can implement only 10BASE-T or 1000BASE-T without needing to support all the possible Ethernet speeds and media types. 10BASE-T Reference: https://www.techtarget.com/searchnetworking/definition/10BASE-T 1000BASE-T Reference: https://www.techtarget.com/searchnetworking/definition/1000BASE-T IEEE Std 802.3-2022 Reference: https://ieeexplore.ieee.org/document/9844436'
'LDAP is developed by IETF which is based in the USA. Therefore, the specification cannot be regarded as a European Standard. IETF reference: https://www.ietf.org/'
There are no disclosures of ISO IPR Database to identify the licensing under the specification. ISO 14533-1:2014 (CAdES) is not listed in ISO/IEC/ITU Common Patent policy, so it cannot be confirmed that the specification is licensed on a (F)RAND basis. ISO patents: https://www.iso.org/iso-standards-and-patents.html ISO standards and patents IPR database: http://isotc.iso.org/livelink/livelink/13622347/Patents_database.xls?func=doc.Fetch&nodeId=13622347
'LDAP is still excellent with authenticating Linux-based applications including many open source solutions, for example: OpenVPN, Jenkins, Kubernetes. It is often used to complement Active Directory (AD) as a directory services protocol. Therefore, it is demonstrated that LDAP has enough market acceptance for its use in the development of digital solutions and services. LDAP used with OpenVPN: https://openvpn.net/vpn-server-resources/openvpn-access-server-on-active-directory-via-ldap/'
'BFO provides in the documentation the requirements for automatically establishing conformance measurements (section 4.6.5 Validating conformance to BFO). BFO reference: https://www.iso.org/standard/74572.html'
'Section 6.6 of the specification explains that in the context of the CIA paradigm the role of integrity is to give assurance to user B that on receipt of data from user A that what he receives is exactly as sent by user A and that the data has not been manipulated by user E. In addition, there is a close relationship between integrity and availability with the defining characteristic that the system delivering data is complete and has itself not been corrupted nor manipulated by user E. Integrity is therefore a key characteristic of non-repudiation services. ETSI Context Information Management (CIM); Security and Privacy: https://www.etsi.org/deliver/etsi_gr/CIM/001_099/007/01.01.02_60/gr_cim007v010102p.pdf'
'This specification is supported by ISO. In order to participate in creating standards, the user must be part of their national standards body (assuming their country is part of ISO). Other groups working on ontologies based on the BFO include it as a de facto element. BFO reference: https://www.iso.org/standard/74572.html '
'There is no evidence found of the creation of any community along with the sharing of their data and resultson European platforms. Therefore this criterion is not applicable to this specification. IPSec reference, What IPSec Does: https://datatracker.ietf.org/doc/html/rfc4301#page-7 IPSec reference: https://datatracker.ietf.org/doc/html/rfc4301'
The specification is independent of any software or platform. The Core Public Organisation Vocabulary can be used by any organisation. CPOV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-organisation-vocabulary
'The purpose of SHACL is not related to e-accessibility. Therefore this criterion is considered not applicable to the specification. SHACL W3C reference: https://www.w3.org/TR/shacl/'
'The SHACL specification is included in SHAPEness project. And in this context, the SHAPENESS is utilised by the European Plate Observing System (EPOS). The SHAPEness features have proven to be a valuable solution to easily create and maintain valid graphs according to the EPOS data model. In addition, the Test Bed project can be highlighted, as it offers a reusable SHACL validation service, allowing RDF content validation through SHACL shapes. SHAPEness project in European Plate Observing System (EPOS): https://link.springer.com/chapter/10.1007/978-3-031-39141-5_23 SHACL Test Bed: https://interoperable-europe.ec.europa.eu/collection/interoperability-test-bed-repository/solution/interoperability-test-bed/news/shacl-validator-updates SHACL W3C reference: https://www.w3.org/TR/shacl/'
'The specification is independent from any particular software, hardware, or operating system. So, it can be said that ISO 19941:2017 is independent of any specific platform. ISO 19941: https://www.iso.org/obp/ui/en/#iso:std:iso-iec:19941:ed-1:v1:en'
'The EN 16234-1 e-CF framework is intended to serve as a device to represent the European e-Competence Framework, which focuses on skills and competences of the ICT professional workforce. EN 16234-1 e-CF has a self-contained structure and behaves as a single-purpose device; therefore, the specification does not allow customisation. CEN reference, CEN/TC 428 - ICT Professionalism and Digital Competences (Published standards), EN 16234-1 e-CF: https://standards.cencenelec.eu/dyn/www/f?p=205:110:0::::FSP_PROJECT:67073&cs=15E62ED24D608A5F10D6BEE8E6D50FA10'
'The specification is free to use. There are no royalties or fees required to use the specification, as it is licensed under the CC0 1.0 Universal license. This licensing framework places the specification in the public domain, permitting unrestricted use, including reproduction, modification, and distribution, without any royalties, fees, or conditions. Publiccode.yaml Licensing: https://github.com/publiccodeyml/publiccode.yml/blob/main/LICENSE'
'YAML is an open file format published with an open license to use as the user sees fit. With that said, most of the subsets, tools and libraries for YAML have assorted licenses that are slightly more specific. For example, the YAML CSS Framework is published under the CC-BY 2.0 Creative Commons Attibution license, which simply requires an attribution link to the originating site. YAML specification: https://yaml.org/spec/1.2.2/'
As a document exchange format, PDF/A is a valuable tool for sharing information through the internet. Allowing sharing data and information the standard foster the visibility of administration data and services. Additionally, it eases the decision-making process within administrations. PDF/A reference: https://www.iso.org/standard/38920.html https://www.iso.org/standard/50655.html
The purpose of ADMS is not related to e-accessibility. Therefore, this criterion is considered not applicable to this specification. ADMS Specification W3C: https://www.w3.org/TR/vocab-adms/
'The purpose of SAREF is not related to providing means for restriction of access to information/data. Therefore, this criterion is not applicable to this specification. SAREF: https://saref.etsi.org/core/v3.1.1/ '
'OData allows for including custom transformations (that is, query options) that the user explicitly requests, which are not necessary defined in the OData specification. However, these extensions are restrictive or limited to a specific functionality. OData reference, 2 Overview and 6 Extensibility: http://docs.oasis-open.org/odata/odata/v4.0/errata03/os/complete/part1-protocol/odata-v4.0-errata03-os-part1-protocol-complete.html#_Toc453752211'
'XHTML specification is not platform-agnostic, is dependent on certain environments and platforms, such as compatible web browsers for proper rendering. Browser Compatibility Reference: https://www.lambdatest.com/web-technologies/xhtml XHTML W3C reference: https://www.w3.org/TR/xhtml1/'
'JSON itself does not provide direct customization options. It has a predefined structure and syntax that follows a specific set of rules. The basic building blocks of JSON are objects, arrays, strings, numbers, booleans, and null values, and it does not support custom data types. Nonetheless, indirect customisations can be applied, as their basic building blocks can be flexibly used. JSON specification: https://www.ecma-international.org/wp-content/uploads/ECMA-404_2nd_edition_december_2017.pdf'
'BFO is independent of any platform and can be implemented without dependencies with technologies. Further more, BFO is designed to support information system interoperability per se. BFO reference: https://www.iso.org/standard/74572.html'
'Domibus is currently being used and implemented by a large number of projects involving large-scale message exchange in the context of public services delivery. An example of projects using Domibus to deliver public services is the MAPA project, or the e-CODEX platform, which provides easy access to cross-border justice for citizens, business and legal professionals all over Europe. Domibus implementation in MAPA project: https://mapa-project.eu/2022/01/F DomibusConnector Suite for e-CODEX: https://www.e-codex.eu/node/47'
'The EIRA is a completely free of charge specification provided by the European Commission, and there is no fee or IPR limitation to use it. Moreover, the tools used for modelling and working with the EIRA, are open source and can be used without paying. Moreover, apart from using the specification with no limitations, the action provides support for implementing it free of charge. EIRA reference: https://interoperable-europe.ec.europa.eu/collection/european-interoperability-reference-architecture-eira /solution/eira/release/610 EIRA Github Repository: https://github.com/CarTool-EC/EIRA '
'DCAT is included in five national catalogues, with the Netherlands and Spain as examples. The Netherlands have the highest performance of all Member States, complying with all 3 sections of the EIF according to the NIFO factsheets. NIFO factsheets: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public-administration-factsheets-2022 CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards '
'IPv6 is already associated to EIRA ABBs in the EIRA Library of Interoperability Specifications (ELIS). More specifically, IPv6 can define the interoperability aspects of the "Data Exchange" and "Firewall" ABBs of the EIRA Technical View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/v610'
At the time of elaborating this assessment, FTPS does not foster the creation of innovative solutions. Since its publication in 2005 as an extension of FTP, it has been used to secure the ordinary protocol FTP. However, another FTP extension with the same purpose as this specification, is raising its usage and FTPS is getting obsolete. FTPS - Obsolescent Secure FTP: https://www.ssh.com/ssh/ftp/ftps FTPS IETF reference: https://tools.ietf.org/html/rfc4217
'One of the main purposes of OAIS is to provide a framework from which apply long-term preservation of information techniques in archival information systems. OAIS specification: https://public.ccsds.org/Pubs/650x0m2.pdf"'
'iCalendar is based on a Multipurpose Internet Mail Extensions (MIME) content and relies on other specifications that enable formats and interoperability features for conveying calendaring and scheduling information between different systems. MIME: https://datatracker.ietf.org/doc/html/rfc2048 iCalendar Basic Grammar and Conventions: https://www.rfc-editor.org/rfc/rfc5545#section-2'
'As defined on the OASIS Technical Committee (TC), only TC members are involved in the development of the OData specification. External contribution to this committee is possible through open channels. OData OASIS Technical Committee reference: https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=odata OData OASIS Technical Committee, Overview reference: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=odata#overview OData.org working groups: https://www.odata.org/contribution/'
"DNS facilitates the visibility of public administrations. As an example of ensuring their visibility, DNS might enhance the transparency of public administrations' networks. The European Commission proposes its own DNS service, the DNS4EU, which will allow the access to global Internet and will comply with EU regulations. DNS IETF reference: https://datatracker.ietf.org/doc/html/rfc8499 Domain Names - Implementation and Specification: https://tools.ietf.org/html/1035 DNS4EU initiative https://www.joindns4.eu/"
'The Core Criterion and Core Evidence Vocabulary (CCCEV) supports the exchange of information and the changes between organisations that define criteria and organisations that respond to these criteria by means of evidences. Core Criterion and Core Evidence Vocabulary reference (v1.0.0): https://joinup.ec.europa.eu/release/core-criterion-and-core-evidence-vocabulary-v100 '
'As ECLI implements DCMI, it can be considered its use in European Cross-border projects or initiatives, using just one search interface with one identifier to find all occurrences of the ruling in all participating national and cross-border databases. ECLI Webpage: https://e-justice.europa.eu/175/EN/european_case_law_identifier_ecli?init=true'
'By itself, does not inherently provide mechanisms to protect information against unauthorized changes. Integrating ODRL into systems that implement these security measures can contribute to a more comprehensive approach to protecting information against unauthorized changes. W3C specification reference: https://www.w3.org/TR/odrl-vocab/#vocab-core'
The Publications Office of the European Union who is in charge of the development of the EuroVoc, has defined a mechanism for the improvement and maintenance of the specification. EuroVoc about: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/eurovoc
"HTTP mentions the importance of protecting personal information in server logs and the potential risks associated with transferring sensitive data. (See section 11.1 at HTTP/1.1 RFC 7). HTTP clients are often privy to large amounts of personal information (e.g. the user's name, location, mail address, passwords, encryption keys, etc.), and SHOULD be very careful to prevent unintentional leakage of this information via the HTTP protocol to other sources. HTTP /1.1 RFC 2616 Reference: https://www.rfc-editor.org/rfc/rfc2616 HTTP/1.1 Authentication, RFC 9110 Reference: https://www.rfc-editor.org/rfc/rfc9110"
The Core Location Vocabulary is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, CLV can define the interoperability aspects of the "Core Data Model" and "Data" ABBs of the EIRA Semantic View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/solution/elis/release/v100
'The UDDI specification establishes a structured registry for web services, acting as a comprehensive repository that houses descriptions of web services, data on service providers, and details on accessing these services. This registry facilitates easy information sharing among administrators and stakeholders, enabling them to connect with minimal effort. Specifically, UDDI helps bridge the gap between requesters and providers, streamlining processes and fostering efficient service ecosystems. Evidence of its implication on the OOP is that SELIS project is included within one of the main Building Blocks for the accomplishment of the once-only principle, eInvoicing. UDDI OASIS reference: https://www.oasis-open.org/standard/uddi/ SELIS Joinup reference: https://joinup.ec.europa.eu/collection/eprocurement/document/secure-electronic-invoicing-service-selis'
'The Dataspace Protocol is not included in any national catalogue of recommended specifications whose Member State NIF has a high performance on interoperability according to the NIFO factsheets. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards 2023 NIFO factsheets: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public-administration-factsheets-2023'
The purpose of the specification is not related to the availability of interfaces with internal information systems. Therefore, this criterion is not applicable to this specification. EuroVoc webpage: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/eurovoc
The purpose of PAdES is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification. PAdES ISO reference: https://www.iso.org/standard/67937.html PAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/102700_102799/10277801/01.01.01_60/ts_10277801v010101p.pdf
'One of the main features of the TSP is that it allows for the maintenance of accurate and consistent timestamps, thus helping in creating a reliable record of data changes and states over time. Users, therefore, can access historical data effectively and ensures that any reused information reflects its proper sequence and integrity. Allowing the reuse of existing data that has been certified, the specification can avoid administrations asking for same certified references in procurement, for instance. TSP IETF reference: https://tools.ietf.org/html/rfc3161'
Version 1.1 of the specification is referenced within Joinup as one of the assets for the licensing of datasets. However, the link provided allows users to access the whole text of the latest version, therefore it is accessible for free from the European Platform Joinup. Rights and licences for Datasets: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/dcat-application-profile-implementation-guidelines/discussion/mi6-rights-and-licences-datasets
XHTML is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, XHTML can define the interoperability aspects of the "Representation" ABB of the EIRA Semantic View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/solution/elis/release/v100
'The purpose of IPv6 is not related to the delivery of multilingual services. Therefore this criterion is not applicable to this specification. IPv6 IETF: https://www.rfc-editor.org/rfc/rfc2460'
'The IPsec specification has been included in many European projects focused on privacy aspects. One such project is Demo 4 from the GRID4EU European project. In this project, the IPsec protocol is mentioned as a mechanism to transport information from primary substations to secondary substations. Moreover, the IPsec specification is also used for transporting electrical network data and control messages. IPSec reference: https://www.rfc-editor.org/rfc/rfc6071.html IPsec in GRID4EU project reference: http://www.cired.net/publications/workshop2014/papers/CIRED2014WS_0107_final.pdf GRID4EU project reference: https://ses.jrc.ec.europa.eu/eirie/en/data-collection/grid4eu-demo-4-increase-medium-voltage-mv-networks-hosting-capacity-der-introducing'
'EN 319 422 defines requirements for a common electronic delivery service in the framework of the eIDAS Regulation. It also provides a profile scheme that is of interest for the eIDAS Regulation. ETSI EN 319 422 reference: https://www.etsi.org/deliver/etsi_en/319400_319499/319422/01.01.01_60/en_319422v010101p.pdf'
There are no evidences of existing studies or documentation assessing the standard or specification in terms of effectiveness and efficiency to justify the criterion.
'By allowing the exchange of datasets metadata, DCAT-AP increases the searchability, visibility, discoverability and reuse of existing data, including information on processes and administrative rules. DEU data provider manual: https://dataeuropa.gitlab.io/data-provider-manual/ DCAT-AP Specification: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/dcat-application-profile-data-portals-europe/release/200'
'Syslog, as a logging protocol, is not inherently designed for the purpose of exposing interfaces to access public administration services. Syslog is primarily used for the collection and transmission of log messages between network devices, systems, and applications. However, syslog can indirectly contribute to the management and monitoring of public administration services by providing a standard in logging security events, providing an audit trail for security-related activities. This is essential for public administration services to identify and respond to potential security threats. Syslog Protocol: https://datatracker.ietf.org/doc/html/rfc5424'
'YAML is already associated with EIRA ABBs in the EIRA Library of Interoperability Specifications (ELIS). More specifically, YAML can define the interoperability aspects of the “Container”, "Container Registry", and "Containers Manager" ABBs of the EIRA Technical Infrastructure View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/600'
The purpose of MIME is not related to the publication of public data as open data. Therefore, this criterion is not applicable to this specification. MIME reference: https://tools.ietf.org/html/rfc2045 Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/en/
After searching for a certification or conformity test to validate Ogg, no tool has been found that assess the conformity of the specification.
Zaragoza's City Council is using HTML5 in part to improve results in higher efficiency and cost savings. Moreover, in the Touch5Mobile uses HTML5 to be more cost effective.
'The Dataspace Protocol aims to be versatile across various technologies by establishing rules and guidelines for data spaces. It provides frameworks that work with different technical setups, enabling smooth communication and management among diverse systems. Furthermore, the fact that the protocol uses widely spread standards such as HTTPS or ODRL confirms its technology agnostic status. IDSA Dataspace Protocol Specification: https://docs.internationaldataspaces.org/ids-knowledgebase/v/dataspace-protocol/overview/readme'
The purpose of PNG is not related to the delivery of multilingual public services. Therefore, this criterion is not applicable to this specification. PNG W3C reference: https://www.w3.org/TR/PNG/ PNG ISO reference: https://www.iso.org/standard/29581.html
'IETF is a vendor neutral SDO. However, FTP relies on the default data connection ports provided by TCP to ensure that all data exchanged is sent correctly to the proper destination. FTP Specification Reference: https://tools.ietf.org/html/rfc959 Transmission Control Protocol (TCP) Reference: https://tools.ietf.org/html/rfc793'
"EN 16234-1 e-CF provides a common European description of the knowledge, skills and competences of the ICT professional workforce in any sector of activity. According to Joinup's Rolling Plan for ICT Standardisation, the use of the specification will increase the development and promotion of ICT professionalism, digital skills and e-learning in all sectors of society and industry. Joinup-2021 Rolling Plan for ICT Standardisation reference, Education, Digital skills and Digital learning section: https://joinup.ec.europa.eu/collection/rolling-plan-ict-standardisation/education-digital-skills-and-digital-learning"
The purpose of RDF is not related to the delivery of multilingual services. Therefore this criterion is not applicable to this specification.
"PROV can indirectly support the visibility of administrative procedures, rules, data, and services by providing contextual information and traceability. By incorporating PROV into an organization's data management or governance framework, it becomes possible to capture and represent the lineage and history of administrative processes, data, and services. Provenance information can be used to document the steps and activities involved in administrative procedures, such as data collection, processing, and transformation. PROV Primer document: https://www.w3.org/TR/prov-primer/ PROV Ontology: https://www.w3.org/TR/2013/REC-prov-o-20130430/ PROV Data Model: https://www.w3.org/TR/2013/REC-prov-dm-20130430/"
'CPOV is designed to be extensible and customizable. Like the OSLO extension, Core Vocabularies allow you to create customized propertites or classes that are aligned with the unique requirements of organizations. Therefore, it is possible define custom properties or classes to capture the data we want. OSLO extension for Core Vocabularies: https://www.w3.org/2013/share-psi/workshop/berlin/EuropeanInteroperabilityTheISACoreVocabularies CPOV custom: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/core-public-organisation-vocabulary/distribution/core-public-organisation-vocabulary-version-100-pdf'
'iCalendar is not a European Standard. iCalendar specification: https://www.rfc-editor.org/rfc/rfc5545'
WS-BPEL is publicly available for free on OASIS Webpage. WS-BPEL OASIS reference: http://docs.oasis-open.org/wsbpel/2.0/OS/wsbpel-v2.0-OS.html
UTF-8 is recommended by 10 Member States. See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
The adoption of SVG as a document format for exchanging photographs helps citizens, businesses, and administrations to share information. Moreover, as it is stated in the specification document, as a graphics technology for the web it allows the scalability in terms of amounts of data, users, and different applications without hampering the interoperability nor scalability of systems. SVG W3C reference: https://www.w3.org/TR/SVG11/
The purpose of the specification is not related to defining organisational interoperability aspects. Therefore, the criterion is not applicable to this specification.
'ISO 19941 mentions the importance of organisational policies in any scenario involving cloud computing interoperability and portability. It is detailed what possible organisational policies should be considered and incorporated thus, this could facilitate organisational interoperability agreements. ISO 19941: https://www.iso.org/obp/ui/en/#iso:std:iso-iec:19941:ed-1:v1:en'
'The specification has published all the documentation and assets for the usage of the specification but it is worth mentioning that the details are to be found on the GitHub Wiki. BFO reference: https://www.iso.org/standard/74572.html BFO GitHub Wiki: https://github.com/bfo-ontology/BFO/wiki'
At the moment of performing the assessment, the specification is not associated with any ABB from the latest version published of the ELIS v1.0.0. However, ELI is associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS) on-going version 1.1.0 that will be published in 2021. More specifically, ELI can define the interoperability aspects of the "Legislation Catalogue" ABBs of the EIRA Legal View, and "Ontology" ABB from the Semantic View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/v100
Even though the PM2 alliance gathers the inputs from different stakeholders, there are no disclosures of a public-review being part of the decision-making process. The OpenPM in the end is produced and published by the Center of Excellence for Project Management Methodology, which congregates individuals and organisations coming from several and diverse area of knowledge. The Center of Excellence also coordinates the PM Support Network (PSN), which in turn contributes to the development of communities and professionals executing projects using the methodology. OpenPM2 specification reference: https://op.europa.eu/en/publication-detail/-/publication/ac3e118a-cb6e-11e8-9424-01aa75ed71a1/language-en/format-PDF/source-83307127 PM2 alliance and advisory commettees: https://www.pm2alliance.eu/advisory-committees/
Core Vocabularies can be used as the foundation of common export formats for data in base registries like cadastral, business registers or public service portals. The Registered Organisation Vocabulary as well as the Core Business Vocabulary (it is the same vocabulary but it was renamed) can be used to describe and ease the publication of information as open data. There is an example of the publication of data as Linked Open Data: "Greek Tax Authorities business registry published as linked open data using core business and core location". Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/en/ RegOrg Joinup reference: https://joinup.ec.europa.eu/solution/registered-organization-vocabulary/about Core Business Vocabulary reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-business-vocabulary Greek Tax Authorities business registry published as linked open data using core business and core location: https://joinup.ec.europa.eu/collection/registered-organization-vocabulary/news/core-business-and-core-locati
'The ebXML specification was originally designed to be associated with business processes. In this sense, the ebXML working groups included a section dedicated to "business processes." Additionally, the "XML and Global Business Exchanges - an invitation" document states that the specification aims to be a global initiative to develop an open technical framework, enabling XML to be utilised in a consistent and uniform manner for the exchange of all electronic business data. However, it does not state that the specification cannot be used in other domains. Therefore, although it is designed to be implemented in a business context, it can be considered domain-agnostic. ebXML business domain: https://xml.coverpages.org/ebXML.html "XML and Global Business Exchanges - an invitation" document: https://xml.coverpages.org/ebXMLInvit.pdf ebXML RegRep OASIS reference: https://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html'
'ISO 3166-1 is intended to identify a country, dependencies and special areas of geographical interest. There is no possibility of partial implementation of the specification, as the specification has a single purpose. ISO 3166-1 reference: https://www.iso.org/standard/72482.html '
'There are already studies and documentation assessing the specification in terms of effectiveness and efficiency. The topics are different, for instance, there is a study assessing the capabilities of XML Schema for the defense against Signature Wrapped Attacks. Another field of documentation is the XML Schema clustering, and its effectiveness for the improvement of user results. ResearchGate XML Schema Validation Reference: https://www.researchgate.net/publication/252053794_On_the_effectiveness_of_XML_Schema_validation_for_countering_XML_Signature_Wrapping_attacks ResearchGate Effectiveness & Efficiency Assessment Reference: https://www.researchgate.net/publication/254858700_XML_schema_matching_balancing_efficiency_and_effectiveness_by_means_of_clustering'
'The fact that the specification describes the model for being serialised and represented in a machine\x02readable format fosters the exchange and reuse of information and its translation to other languages different from the original in which was developed the initial resource. Therefore, ODRL can be useful to ensure the availability of access datasets licensing and the related services in different languages, easing the multilingualism of digital public services. W3C specification reference: https://www.w3.org/TR/odrl-vocab/#vocab-core'
After carrying out information retrieval, no document or study has been found assessing the OpenPM2 in terms of efficiency or effectiveness.
'Registered Organization Vocabulary does not ensure and enable data processing accuracy. The main purpose of the specification is to define a standardised way of describing organisations that have gained legal entity status through a formal registration process. Therefore, this criterion is considered not applicable to this specification. Registered Organization Vocabulary reference: https://www.w3.org/TR/vocab-regorg/'
XAdES is included in 7 national catalogues. They belong to Member States which comply with at least 4 out of 5 sections of the EIF according to the NIFO factsheets. See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
"FTP is used as the main protocol for file exchange by many public organisations. By allowing public administration to share information with others, it fosters the comprehensibly of data (e.g. Administrative rules, processes etc.) and facilitates public administrations decision-making. An example of implementation supporting this fact would be CIRCABC, a project with the purpose of enhancing the collaboration, communication and document exchange between different European Union's stakeholders. CIRCABC Reference: https://circabc.europa.eu/ui/welcome FTP Specification Reference: https://datatracker.ietf.org/doc/html/rfc959"
'The specification does dwell in data portability between systems/applications or supporting the implementation/evolution of standards since it is designed to support the interchange of information among different information systems. But its main focus is the model, it contributes to data portability but it is up to the users to develop it. OSI reference https://www.iso.org/standard/20269.html'
'Syslog provides with security features for the exchange of data. According to section 5.1 of the specification's protocol "all implementations of this specification MUST support a TLS-based transport". The syslog protocol operates at the application layer, and its focus is on the transmission and reception of log messages. The content of syslog messages is typically sent in clear text by default. Syslog Protocol Section 5.1: hhttps://datatracker.ietf.org/doc/html/rfc5424#section-5.1'
'ShEx can be very useful for data portability as it is a tool that allows for the communication of data structures associated with some process or interface. Moreover, ShEx also allows for the serialization in different human and machine-readable formats, use cases that ease the transfer of data between systems, at the same time it eases comprehensibility for humans. An example of the ShEx implementation would be the Hercules ASIO project, whose objective is to create a Research Management System (RMS) based on semantic open data that offers a global view of the research data of the Spanish University System (SUE), to improve management, analysis and possible synergies between universities and the general public. Therefore, supporting the implementation of European public services. ShEx primer document: https://shexspec.github.io/primer/ ShEx Community Group: https://www.w3.org/community/shex/ ShEx Github: https://github.com/shexSpec/spec/issues Hercules ASIO project: https://github.com/HerculesCRUE/ib-shex-lite'
All the IETF standards are free and open technical specification, built on IETF standards and licenses from the Open Web Foundation. The specification is therefore licensed on a royalty-free basis. See: https://tools.ietf.org/html/rfc3668
Belgium is recommending CPSV-AP in their ICT National Catalogues. Belgium national catalogue: https://www.belgif.be/nl/specifications
'OCSP is included in 1 national catalogue of recommended specifications. It belongs to Spain. The National Interoperability Framework (NIF) of this Member States is almost fully aligned with the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. National catalogue Spain: https://administracionelectronica.gob.es/pae_Home/pae_Estrategias/pae_Interoperabilidad_Inicio /pae_Normas_tecnicas_de_interoperabilidad.html#CATALOGOESTANDARES NIFO factsheets: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public-administration-factsheets-2021'
HTML is a business domain agnostic specification that can be reused in a cross-domain way. HTML W3C reference: https://www.w3.org/TR/html401/
'IPsec allows data portability between systems and is compatible with both IPv4 and IPv6. Moreover, IPsec works with AH and ESP headers, which facilitate data transfer between systems. Therefore, IPsec can use these headers to enhance data portability between applications. IPSec reference: https://www.rfc-editor.org/rfc/rfc6071.html IPsec in IPv4 and IPv6: https://networkengineering.stackexchange.com/questions/37025/ipsec-in-ipv4-and-ipv6'
'The Data Privacy Vocabularies and Controls Community Group (DPVCG) is in charge of mantaining and developing the DPV, it is a fairly open group that welcomes participation regarding extensions and refinement of terms. DPV specification: https://w3c.github.io/dpv/primer/ '
Although Ogg’s purpose is not the long-term preservation of data, it can be used to store multimedia content. Ogg XIPH reference: https://xiph.org/ogg/doc/rfc3533.txt
'XHTML, developed by the W3C, is not classified as a European Standard. However, it significantly contributes to the foundation of web technologies widely used throughout Europe. By providing a consistent way to structure web documents, XHTML has helped improve digital communication and made it easier to exchange information. XHTML W3C reference https://www.w3.org/TR/xhtml1/'
The purpose of CSS v2.1 is to give format to web designs, thus, the use of the specifications does not hamper the scalability of systems. By using CSS v2.1, administrations, citizens or businesses can visualize data over the Internet. If the environment grows or changes, CSS can be adapted without creating harm over the solution. CSS v2.1 W3C reference: https://www.w3.org/TR/2011/REC-CSS2-20110607/
The HTML5 Royalty-Free IPR licenses granted under the W3C Patent Policy apply to all W3C specifications, including HTML5. See: https://www.w3.org/2012/12/html5-cr.html.en
The application of the once-only principle in all EU Member States public administrations aims at reducing the administrative burden. To achieve this, interoperability between public administrations is a sine qua non condition. In this sense, SHACL addresses and facilitates interoperability between public administrations, cross border services and impacts positively the development of eGovernment. This is due to the fact that it has been designed to enhance the semantic and technical interoperability layers of ontologies expressed as RDF graphs, and RDF is a European Standard used by public administrations in projects for sharing Linked Data.
'UBL is an Extensible Mark up Language (XML) based specification. XML is a markup language and file format for storing, transmitting and reconstructing arbitrary data, and it emphasizes simplicity generality and usability across the internet. For that matter, XML supports at least one of the five stars of Tim Berners-Lee scale. UBL v2.3 reference: http://docs.oasis-open.org/ubl/os-UBL-2.3/UBL-2.3.html Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/en/'
Time-Stamp Protocol (TSP) is widely used and implemented in the context of application, transport, internet and link layers as FTP or IP. Moreover, there are several implementations of the specification that support the market acceptance of TSP. TSP IETF reference: https://tools.ietf.org/html/rfc3161
'Syslog focuses on the transmission and reception of log messages in a standardized format. However, syslog can indirectly contribute to organizational interoperability by providing a standardised communication format, thus improving cross-platform compatibility and secure information exchange. Syslog Protocol: https://datatracker.ietf.org/doc/html/rfc5424'
The purpose of XHTML is not related to the availability of interfaces with internal information systems. Therefore, this criterion does not apply to this specification. XHTML W3C reference: https://www.w3.org/TR/xhtml1/
'HTTP is included in European Union Agency for Network and Information Security (ENISA). This organisation is a centre of network and information security expertise for the EU, its member states, the private sector and Europe’s citizens. ENISA works with these groups to develop advice and recommendations on good practice in information security. It assists EU member states in implementing relevant EU legislation and works to improve the resilience of Europe’s critical information infrastructure and networks. ENISA Privacy and Data Protection by design Reference: https://www.enisa.europa.eu/publications/privacy-and-data-protection-by-design HTTP /1.1 Access Authentication, RFC 2616 Reference: https://www.rfc-editor.org/rfc/rfc2616.html#section-11'
'ETSI TS 119 512 is designed to support possible customisations depending on the business-specific needs and requiremets. ETSI TS 119 512 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.02_60/ts_119512v010102p.pdf '
XACML is publicly available for free on OASIS Webpage. XACML OASIS reference: http://docs.oasis-open.org/xacml/3.0/errata01/xacml-3.0-core-spec-errata01.html
'W3C has a defined and publicly available Process for the Development and approval process of the specification as a recommended standard. Also, a clear Release Notes tracking the changes of the different versions is archived. W3C Process Document reference: https://www.w3.org/2021/Process-20211102/'
CAMSS Assessment of XSLT EIF Scenario v1.0.0
'The purpose of IPSec is to secure communications over a Network; therefore, the specification does not focus on the facilitation of digital service delivery channels. IPSec reference, How IPSec Works: https://datatracker.ietf.org/doc/html/rfc4301#page-9'
'As a protocol for mantaining and accessing Directory Services, LDAP is a useful tool to display of user information in a readable manner. comprehensibility of data therefore is supported by the fact that it permits to access user information in the network in a structured, human-readable manner. LDAP Directory Information Models: https://datatracker.ietf.org/doc/html/rfc4512 LDAP IETF reference: https://tools.ietf.org/html/rfc4511 '
As WS-BPEL is a language used for the composition of web services, WS-BPEL helps and fosters the visibility of administration data, and services. Moreover, it eases the decision-making process by ensuring the data exchange and reuse. The specification: http://docs.oasis-open.org/wsbpel/2.0/OS/wsbpel-v2.0-OS.html
'While genericode itself does not directly enable the exposure of interfaces to access public administration services, it can indirectly contribute to the interoperability and integration of systems that provide access to public administration services by promoting consistency, compatibility, and semantic clarity in data exchange. By utilising genericode-compliant code lists, agencies can ensure how data is represented and exchanged between services and external systems. Code List Representation (genericode): https://docs.oasis-open.org/codelist/genericode/v1.0/os/genericode-v1.0-os.html'
CAMSS Assessment of CPOV EIF Scenario v1.0.0
The specification is independent of any software, hardware, or operating system. So it can be said that ELI is independent of any specific technology or platform. However, it is worth to note that is has been defined taking into account other international standards or specifications for example for its serialisation as ontology. (e.g. RDFa in XHTML: Syntax and Processing) ELI reference: https://eur-lex.europa.eu/eli-register/about.html
'OData Services requiring authentication should consider supporting basic authentication as defined in RFC7617 over HTTPS for the highest level of interoperability with generic clients. OData reference on authentication: https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#sec_Authentication The 'Basic' HTTP Authentication Scheme", RFC 7617: https://tools.ietf.org/html/rfc7617'
'Syslog has been selected for its use in the European Data Protection Supervisor (EDPS). It is the European Union’s (EU) independent data protection authority and they aim to monitor, advise, intervene, and cooperate in personal data and privacy matters regarding EU institutions. It is mentioned that SYSLOG is the administrative management tool for training at the European Commission in three fields: informatics, language and general. EDPS: https://edps.europa.eu/_en Training SYSLOG: https://edps.europa.eu/data-protection/our-work/publications/opinions-prior-check/training-syslog-commission_en'
'In 1992 there was the SAS (Statement on Auditing Standards) 70 and then there was a transition to the ISAE 3402 / SSAE16 which is based on the SSAE 16 and is an analysis and evaluation standard (assurance). Finally, the standard was published by The International Auditing and Assurance Standards Board (IAASB) in December 2009. Therefore we can state that ISAE 3402 has a widespread market acceptance. ISAE 3402 history: https://www.isae3402.com/ISAE3402_history'
'The purpose of DPV is not related to the authenticity and authenticathion of the agents involved in data transactions, therefore, this criterion is not applicable to the specification. DPV specification: https://w3c.github.io/dpv/primer/'
The adoption of RegOrg as a data model does not hamper the scalability of systems. The use of existing data models for the development of common information systems facilitates the development of those systems and improves their interoperability. Moreover, RegOrg facilitates information exchange between business registers. RegOrg Joinup reference: https://joinup.ec.europa.eu/solution/registered-organization-vocabulary
'There are several existing documents and studies assessing SAML 2.0 features and capabilities and effectiveness. Broadly speaking, the studies are focused on the capability to enable Single Sign-on and its benefits. Researchgate analysis on SAML2.0 Reference: https://www.researchgate.net/publication/221609828_Formal_analysis_of_SAML_20_web_browser_single_sign-on Researchgate on Single Sign-on Auth Reference: https://www.researchgate.net/publication/45872317_Web_single_sign-on_authentication_using_SAML'
The specification is a key enabler for digital transactions across borders ensuring the trustworthiness of data being exchanged. This fact helps to avoid the non-digital data exchange allowing the reduction of administrative burden.
'TS 119 614-1 is a testing conformance suite that can be applied in any domain and context where the exchange of documents is required. Therefore, the specification is usable beyond any business-specific domain and can be used in any kind of organisation. ETSI TS 119 614-1 reference: https://www.etsi.org/deliver/etsi_ts/119600_119699/11961401/01.01.01_60/ts_11961401v010101p.pdf'
'FTP allows public administration to exchange information and therefore to avoid requesting standard information to citizens or businesses several times. FTP is used by MAGA, an initiative from the Flemish Region of Belgium consisting in a common platform for data reuse between administrations. Magda Solution Reference: https://joinup.ec.europa.eu/solution/magda-platform/about FTP Specification Reference: https://datatracker.ietf.org/doc/html/rfc959 '
'The SHACL specification documentation states that the only mandatory implementation is SHACL Core, while other components can be implemented separately. In this context, SHACL Core includes essential features for representing shapes, constraints, and targets. SHACL W3C reference: https://www.w3.org/TR/shacl/'
'The purpose of SFIA is not related to data portability. Therefore, this criterion is not applicable to this specification. SFIA reference: https://sfia-online.org/en/sfia-8'
The specification is included in 9 Member States' catalogues of recommended specifications. Some examples of Member States including IPv6 on their catalogues are Spain, Sweden, France or Germany. See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'Although MIME itself does not provide means for data confidentiality, its security extension mechanism (S/MIME) is a powerful tool for implementing data confidentiality features in email communication. It leverages cryptographic techniques to protect the content of emails and attachments, ensuring that sensitive information remains confidential and secure during transmission and storage. MIME specification: https://tools.ietf.org/html/rfc2045 S/MIME specification: https://www.rfc-editor.org/rfc/rfc5751.html'
By using LDAP, the system administrator is prevented from providing several authentication accounts for accessing distributed directories, the user does not have to deal with several credentials. This fact helps to adapt the specification to user’s needs without hampering the scalability of systems._x000D_ _x000D_ LDAP IETF reference: https://tools.ietf.org/html/rfc4511
RDF is built around specifications as XML or URL (URI). Even though, both web standards are well known and widely extended avoiding interoperability hampering.
'DPV is independent of any specification and can be implemented without relying on other technologies. DPV specification: https://w3c.github.io/dpv/primer/ '
As one of the official European Organisation for standardisation, ETSI standards are compliant with the European Standardisation Regulation 1025/2012. See: https://www.etsi.org/about/etsi-in-europe
'The OASIS Universal Business Language (UBL) Standard, version 2.1, has been designated by the European Commission as one of the first consortium standards officially eligible for referencing in tenders from public administrations. Still UBL is not considered a European standard although it is recoginzed as such. COMMISSION IMPLEMENTING DECISION of 31 October 2014 on the identification of Universal Business Language version 2.1 for referencing in public procurement: https://eur-lex.europa.eu/legal-content/ES/TXT/?qid=1657095448506&uri=CELEX:32014D0771'
The purpose of CPOV is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification. CPOV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-organisation-vocabulary
'The specification cannot be implemented partially. Therefore, this criterion does not apply to this specification. Core Criterion and Core Evidence Vocabulary reference (v1.0.0): https://joinup.ec.europa.eu/release/core-criterion-and-core-evidence-vocabulary-v100 '
'ISO/IEC 19944-1 allows for extension to accommodate additional requirements or specific use cases beyond its scope. Extension enables organizations to address unique data management needs, industry-specific considerations, and emerging technologies, while maintaining compatibility with the core principles of the standard. ISO/IEC 19944-1 specification: https://www.iso.org/standard/60545.html'
The Executive Committee has to review and co-ordinate the progress of the TCs and, from time to time, review the terms of reference given to Technical Committees. In addition, the Technical Committee shall review and approve the minutes of the preceding meeting. The minutes, after approval, shall constitute the official record of the meeting of a TC See: http://www.ecma-international.org/memento/policies.htm
'DIDs are persistent and can be updated and reusable in many situations. In this way, if the controller of a web page or any other web resource wants to assign it a persistent, cryptographically verifiable identifier, the controller can give it a DID. Furthermore, in the DID document, the author can include the "alsoKnownAs" property pointing to the current URL of the blog, and make DID upgradable. DIDs W3C: https://www.w3.org/TR/did-core/#assigning-dids-to-existing-web-resources'
Examples of public institutions or organisations are provided in in the criteria 1. (e.g EMBL European Bioinformatics Institute, and Australian Center for Plant Functional Genomics)
PDF/A is included in 3 national catalogues of recommended specifications. They belong to Estonia, Spain and Sweden. The National Interoperability Framework (NIF) of these Member States is fully aligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. National catalogue Estonia: https://www.mkm.ee/sites/default/files/interoperability-framework_2011.doc National catalogue Spain: https://administracionelectronica.gob.es/pae_Home/pae_Estrategias/pae_Interoperabilidad_Inicio/pae_Normas_tecnicas_de_interoperabilidad.html#CATALOGOESTANDARES National catalogue Sweden: https://www.avropa.se/globalassets/dokument/open-it-standards.pdf?_t_id=1B2M2Y8AsgTpgAmY7PhCfg%3d%3d&_t_q=standards&_t_tags=language%3asv%2csiteid%3a95d515a5-23ca-47bf-87a9-07b10d8ac360&_t_ip=178.139.72.144&_t_hit.id=Avropa_Core_Models_Media_GenericMedia/_ff07d720-f793-44b0-994d-27e79b28f6bd&_t_hit.pos=7 NIFO factsheets: https://joinup.ec.europa.eu/collection/national-interoperability-framework-observatory-nifo/nifo-factsheets
"TSP is not included in any Member States' catalogues of recommended specifications. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards"
XHTML appears from the reformulation of HTML4 using XML. XHTML 1.0 became a World Wide Web Consortium (W3C) recommendation on 26 January 2000. There have been multiple updates with new versions of XHTML, for example in XHTML 1.1 became a W3C recommendation on 31 May 2001. There is a development of XHTML5 which is an XML adaptation of the HTML5 specification. This fact proves that the specification is mature enough for its use in the development of products and services. XHTML W3C reference: https://www.w3.org/TR/xhtml1/
'The purpose of this Core Vocabulary is not related to enabling long-term preservation of data/information. Therefore, this criterion is not applicable to this specification. CPSV-AP Joinup webpage: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/core-public-service-vocabulary-application-profile/release/22'
'The specification allows for customisation. The specification is designed to be modular and flexible, which enables implementers to develop their own extensions or customisations to meet specific requirements. Implementers can customise the specification by adding the elements they developed or extensions that have been modified, attributes, or namespaces to the existing XML schema. They can also develop their own modules or components that extend or modify the behavior of the specification. AKN4EU reference: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/akn4eu'
'OCSP is meant to serve in the Internet of Things domain. Moreover, the specification is also available for its use within a public administration service, for example in PDF signatures. OCSP reference: https://datatracker.ietf.org/doc/html/rfc2560 Adobe OCSP reference: https://www.adobe.com/devnet-docs/acrobatetk/tools/QuickKeys/Acrobat_SigRevCheck_KeyAll.pdf'
'The Extensible Forms Description Language (XFDL) is a useful specification for creating, processing, and rendering electronic forms and documents. Moreover, it can also be useful for addressing some issues related to conducting electronic commerce on the Web. However, other newer and easier-to-implement specifications have been developed to perform these functions. Therefore, although XFDL is still in use for addressing functions related to e-commerce, it is not the preferred specification. XFDL for e-commerce: https://drdobbs.com/web-development/xfdl-the-extensible-forms-description-la/184411136 "Sustainability of Digital Formats: Planning for Library of Congress Collections" repport: https://www.loc.gov/preservation/digital/formats/fdd/fdd000580.shtml Extensible Forms Description Language reference: https://www.w3.org/TR/NOTE-XFDL'
'There is the Accessible Rich Internet Applications Working Group (ARIA WG) which aims to develop technologies that improve the accessibility of web content for people with disabilities, which includes the continued development of WAI-ARIA. Participating in the WG requires a W3C account. W3C has a defined and publicly available Process for the Development and approval process of the specification as a recommended standard. Also, a clear Release Notes tracking the changes of the different versions is archived. ARIA Working Group reference: https://www.w3.org/WAI/ARIA/ W3C Process document: https://www.w3.org/2021/Process-20211102/#groups'
'ELI is an initiative aimed at improving the interoperability of legal information within the European Union. It provides a common framework for identifying and referencing legal documents across different jurisdictions. ELI is often used as a best practice and guideline rather than a formal standard. ELI reference: https://eur-lex.europa.eu/eli-register/about.html'
'The Advanced Encryption Standard includes mechanisms that help guarantee data accuracy, such as data encryption. By encrypting information, it can help ensure that data has not been altered by an unauthorised user since it was sent. Geeksforgeeks AES reference: https://www.geeksforgeeks.org/advanced-encryption-standard-aes/ AES Standard Reference: https://csrc.nist.gov/pubs/fips/197/final'
'Registered Organization Vocabulary states that a publisher may use any of the terms defined in this document encoded in any technology although RDF and XML are preferred. This indicates that while RDF and XML are preferred, the specification does not mandate their use, making it usable across different technologies. Registered Organization Vocabulary reference: https://www.w3.org/TR/vocab-regorg/'
The purpose of TIFF/IT is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification. TIFF/IT ISO reference: https://www.iso.org/standard/34342.html
'The purpose of EuroVoc is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification. EuroVoc: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource /dataset/eurovoc'
'SFIA is intended to serve as a device to represent the skills and competences of any ICT professional workforce. Although the specification does not foresee specific support for multilingualism, SFIA could be used in any multilingual context since it represents concepts and their scope. SFIA reference: https://sfia-online.org/en/sfia-8 '
The W3C Royalty-Free IPR licenses granted under the W3C Patent Policy apply to all W3C specifications, including SHACL See: https://www.w3.org/TR/patent-practice#ref-AC
UDDI is included in 2 national catalogues. They belong to Member States which comply with at least 4 out of 5 sections of the EIF according to the NIFO factsheets. The Member States are the Netherlands, and Spain. See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards https://joinup.ec.europa.eu/collection/national-interoperability-framework-observatory-nifo/nifo-factsheets
'ISO 639-2 is intended to identify a language name. This specification relates to metadata, and can be used in any system that ingests metadata. Therefore, it can be considered platform-agnostic. ISO 369-2 FAQs: https://www.loc.gov/standards/iso639-2/faq.html#5 https://www.loc.gov/standards/iso639-2/faq.html#7'
Better Regulation Toolbox was developed between 2015 and 2017 aiming to help those involved in the creation of public policies and laws across the European Union. Its market acceptance lies in the European Public sector which has set Better regulation and the toolbox as the tools for the development, implementation and assessment of the impact of public policies and laws. Better Regulation Toolbox reference: https://ec.europa.eu/info/sites/info/files/better-regulation-toolbox_2.pdf .
TLS 1.2 is included in two national catalogues, which belong to Member States complying with at least 4 out of 5 sections of the EIF according to the NIFO factsheets. See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
The purpose of CSV is not related to the once-only principle. Therefore, this criterion is not applicable to the specification.
WSDL is not included in any supra-national catalogue of standards.
' HTTPS cookies is maintained and developed by IETF which is an international community developing open standards. HTTPS cookies reference: https://datatracker.ietf.org/doc/html/rfc6265'
The purpose of SOAP 1.2 is not related to e-accessibility. Therefore, this criterion is not applicable to the specification.
"The specification is included in 12 Member States' catalogues of recommended specifications. Some examples of Member States including CSV on their catalogues are the Netherlands, Slovenia or Sweden. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards "
The Joint Photographic Experts Group (JPEG) committee has a long tradition in the creation of still image coding standards. JPEG is a joint working group of the International Standardization Organization (ISO) and the International Electrotechnical Commission (IEC). It can be found in the particular website created to communicate and gather information about the JPEG standard. This website is known as jpeg.org. The specification in ISO: https://www.iso.org/standard/18902.html JPEG.org: https://jpeg.org/jpeg/index.html
'exbXML is included in 1 national catalogues of recommended specifications. It belongs to Norway. The National Interoperability Framework (NIF) of Norway is aligned with at least 3 out of 4 scoreboards of the EIF Monitoring according to the National Interoperability Framework Observatory (NIFO) factsheets. CAMSS list of standards: https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards NIFO Factsheets: https://interoperable-europe.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public-administration-factsheets-2024 National Catalogue of Norway: https://www.difi.no/fagomrader-og-tjenester/digitalisering-og-samordning/standarder ebXBL RegRep reference: https://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html'
'WAI-ARIA deals with roles, states, and properties of user interface components to improve accessibility, particularly for assistive technologies. It does not specifically address data integrity or provide mechanisms to protect information against unauthorized changes. Therefore, this criterion is not applicable to this specification. WAI-ARIA reference: https://www.w3.org/TR/wai-aria-1.2/'
ODRL does not directly help with the provision of application programming interfaces (APIs) or Web services. However, ODRL aims to ensure consistency when describing the rules and access conditions to datasets or services. By providing this machine-readable format information, the specification makes data more accessible and comprehensive allowing its proper reuse. W3C specification reference: https://www.w3.org/TR/odrl-vocab/#vocab-core
The specification has been developed by European Institutions for its implementation across borders to enhance the law-making and the processes. It is involved in an organisational agreement between European Institutions "INTERINSTITUTIONAL AGREEMENT BETWEEN THE EUROPEAN PARLIAMENT, THE COUNCIL OF THE EUROPEAN UNION AND THE EUROPEAN COMMISSION ON BETTER LAW-MAKING - INTERINSTITUTIONAL AGREEMENT" that aims to enhance the law-making for efficiency and effectiveness of European processes. European Comission Webpage: https://ec.europa.eu/info/index_en INTERINSTITUTIONAL AGREEMENT: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv:OJ.L_.2016.123.01.0001.01.ENG&toc=OJ:L:2016:123:TOC
'ISO 3166-1 is a key component in the development of some European cross-border projects and initiatives. However, ISO 3166-1 does not encourage the creation of communities nor promotes the sharing of data and results in any European platform. ISO 3166-1 reference: https://www.iso.org/standard/72482.html '
The purpose of SVG is not related to organisational interoperability. Therefore, this criterion is not applicable to the specification. SVG W3C reference: https://www.w3.org/TR/SVG11/
'The purpose of GITB TDL is not related to the visibility of administrative procedures, rules data, and services. Therefore this criterion is not applicable to this specification. GITB TDL reference: https://www.itb.ec.europa.eu/docs/tdl/latest/introduction/index.html#what-is-the-gitb-tdl'
'There are studies assessing the specification in terms of effectiveness and can be checked in the following links: https://link.springer.com/article/10.1007/s10791-006-9008-2 https://link.springer.com/chapter/10.1007/978-3-642-04205-8_6'
'8 Member States are recommending MIME in their ICT National Catalogues. The Member states are Croatia, France, Germany, Greece, Malta, the Netherlands, Spain and Sweden. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
'SAREF is primarily designed for representing the semantics of smart appliances in the context of the Internet of Things (IoT). While its initial focus is on the domain of smart appliances, the ontological principles it employs, combined with its extensibility features, allow for potential usage beyond the business-specific domain of smart appliances. SAREF: https://saref.etsi.org/core/v3.1.1/ '
'OData was approved as an OASIS Standard in 2014 and as an ISO standard in 2017. Currently, there is OData version 4.1. Microsoft, as other corporations (see OData ecosystem reference) and organisations such as the World Health Organization (WHO), are using this specification in some of their systems. Besides, the OData Technical committee is very active in terms of new releases. OData Blog: https://www.odata.org/blog/OData-Published-as-an-ISO-Standard/ OData Technical Committee: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=odata#technical OData ecosystem reference: https://www.odata.org/ecosystem/ Microsoft-OData reference: https://docs.microsoft.com/es-es/odata/ WHO reference: https://www.who.int/data/gho/info/gho-odata-api'
'The Core Public Organisation Vocabulary was released in December 2016. Since 2016, CPOV has released two major versions. Its first aspiration was to become a common data model for describing public organisations in the European Union. CPOV can therefore be considered mature enough for its use in the development of products and services. CPOV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-organisation-vocabulary CPOV github releases: https://github.com/SEMICeu/CPOV/tree/master/releases'
'Registered Organization Vocabulary can be implemented using other technologies as well. This makes the specification usable across different platforms and systems. Registered Organization Vocabulary reference: https://www.w3.org/TR/vocab-regorg/'
'ETSI TS 119 512 protocols can be used in any business domains of the european public administrations. In this sense the use of different preservation schemes in the specification that build the so called preservation profiles. This capabilities make the specification truly domain agnostic. ETSI TS 119 512 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.02_60/ts_119512v010102p.pdf'
SMP is already associated to an EIRA ABB in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, SMP can define the interoperability aspects of the "Service Delivery Model" ABBs of the EIRA Organisational View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/solution/elis/release/v100
'IPv6 is in constant development and some articles discuss improvements to IPv6. Moreover, the IPv6 is being applied in many countries. In 2024, Germany follows France with a steady increase in IPv6 deployment and is currently at 73.3%. A considerable change compared to 2019, when IPv6 capability was 43.82%. Also, the percentage of users who access Google over IPv6 is about 45% compared to 2019, when it was 20%. Although there are differences between countries, their adoption is increasing. IPv6 adoption reference: https://www.ipxo.com/blog/ipv6-adoption/ Per-country IPv6 adoption reference: https://www.google.com/intl/en/ipv6/statistics.html#tab=per-country-ipv6-adoption'
The once-only principle is an e-government concept that aims to ensure that citizens, institutions, and companies only have to provide certain standard information to the authorities and administrations once. The Internet Protocol is a necessary specification for the implementation of the once-only-principle as it allows cross-border communications over the internet.
'OAIS is recommended by the France Natioanl Catalogue of IT standards. France national catalogue of IT standards: https://www.numerique.gouv.fr/uploads/Referentiel_General_Interoperabilite_V2.pdf OAIS specification: https://public.ccsds.org/Pubs/650x0m2.pdf'
'ETSI TS 119 432 provides a variety of processing models for the correct implementation of the protocol. For instance, the purpose of the signature creation process is to take the Data To Be Signed Representation (DTBSR) and create a digital signature value under the control of the signer. The creation of the digital signature value is managed by an Server Signing Application Service Component (SSASC) that uses a signing key, held within a cryptographic security module (SCDev), that the signers can activate by means of a secure authorisation and activation process. ETSI TS 119 432: https://www.etsi.org/deliver/etsi_ts/119400_119499/119432/01.02.01_60/ts_119432v010201p.pdf'
'HTTP is maintained by IETF which is an international community developing open standards. IETF Community reference: https://www.ietf.org/about/'
'iCalendar facilitates the capture and exchange of information that would normally be stored in a calendar and scheduling application. Although the focus of the specification is not data preservation, iCalendar provides a common format that allows a personal information manager (PIM) or group scheduling product to preserve its data. iCalendar specification: https://www.rfc-editor.org/rfc/rfc5545'
'XSLT specification is designed to be technology-agnostic, focusing on data transformation and manipulation without being tied to any specific technology. (See Section 2.9) XSLT Reference: https://www.w3.org/TR/xslt-30/#extensibility'
CAMSS Assessment of LDAP EIF Scenario v2.0.0
Even though at the moment of elaborating the assessment the specification is used in the context of the cross-border reusability of interoperability solutions, the specification in itself is used to describe these solutions in a repository. Therefore, ADMS does not foster the creation of innovative solutions.
'AMQP specification does not directly ensure or guarantee data processing accuracy. Therefore, this criterion is not applicable to this specification. OASIS AMQP Reference: http://docs.oasis-open.org/amqp/core/v1.0/amqp-core-complete-v1.0.pdf'
The specification is independent from any software, hardware, or operating system. It can be used and applied independently from other standards, or software requierements. Betterr Regulation Toolbox reference: https://ec.europa.eu/info/sites/info/files/better-regulation-toolbox_2.pdf
'The specification was initially developed in 2017 with its initial version 1.0. It was used as the basis for the development of European Specifications and building blocks enhancing the development of public services. It is being used in the SMP software for eDelivery. SMP OASIS reference: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505009 eDelivery software Reference: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/SMP+software'
The SOAP 1.2 is included in the European Interoperability Architecture (EIA) study explores the need for a European interoperability architecture facilitating the establishment of European public services (cross border eGovernment services). The document includes references to the Reference Interoperability agreement(RIA), where SOAP can be mapped with the technical agreement for “ Agreement on the technical connection aspects for electronic data Exchange” in the context of epSOS Project. See: https://ec.europa.eu/isa2/sites/isa/files/isa_2.1_eia-finalreport-commonvisionforaneia.pdf
"As is described in section 1 of the specification's document, the specification specifies a format and a mechanism for establishing, locating, accessing and authenticating a trusted list which makes available trust service status information so that interested parties may determine the status of listed trust services at a given time. ETSI TS 119 612: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf"
The Internet Protocol is a necessary specification for the implementation of the once-only-principle as it allows cross-border communications over the internet.
'The specification enables data portability to a certain extent, which can support the implementation or evolution of European public services. FTP provides a standardized protocol for transferring files between systems and applications, allowing data to be exchanged and shared. By adhering to the FTP specification, systems and applications supporting European public services can utilize FTP to transfer data in a consistent and interoperable manner. FTP can facilitate the exchange of various types of data, including documents, records, and datasets, which are integral to public service operations. FTP Specification Reference: https://tools.ietf.org/html/rfc959'
The specification is included in 12 Member States' catalogues of recommended specifications. These Member States including ODF on their catalogues are Croatia, Denmark, Estonia, France, Greece, Ireland, Malta, Netherlands, Norway, Slovenia, Sweden and UK. Joinup Assessment Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'The specification builds on standards that are integrated within the ISO OSI model (ISO/IEC 7498-1:1994) layers, such as HTTPS. The primary aim of the OSI model standard is to delineate interactions between systems, regardless of these protocols, by providing clear and adaptable guidelines for implementation. IDSA Dataspace Protocol Specification: https://docs.internationaldataspaces.org/ids-knowledgebase/v/dataspace-protocol/overview/readme ISO/IEC 7498-1:1994: https://www.iso.org/standard/20269.html?browse=tc'
The purpose of WS-BPEL is not related to the long-term preservation of electronic records and other kinds of information. Therefore, this criterion is not applicable to the specification.
'The first drafts of XBRL GL were developed in 1999 by the chief architect who contributed the work to XBRL. Development and implementation of pre-recommendation status versions followed shortly after (See http://www.xbrl.org/business/companies/breathing-new-life-into-old-systems.pdf from 2004, for example). The standards process within XBRL led to the first official version in 2005. The Specification was not developed in a background. Its chief architect and other participants also contributed to virtually all other Specifications in overlapping space, including UN/CEFACT Accounting and Audit artefacts, OECD Standard Audit File for Taxation (SAF-T), ISO/TC 295’s Audit Data Collection specification ISO 21378:2019, AICPA Audit Data Standards, and others, each focusing on some specific area or compliance. This collaboration was to encourage harmonization and help in proving the capabilities of XBRL GL. https://www.xbrl.org/int/gl/2007-04-17/GLFramework-REC-2007-04-17.htm All versions: https://specifications.xbrl.org/spec-group-index-xbrl-gl.html '
ADMS, as a vocabulary for the description of assets included within a Repository (Catalogue), it can be used to define Interoperability Solutions catalogues, beyond the eGovernement scope. ADMS on Joinup: https://joinup.ec.europa.eu/solution/asset-description-metadata-schema-adms/about ADMS Specification W3C: https://www.w3.org/TR/vocab-adms/
'The Advanced Encryption Standard itself does not define a formal access control system with explicit roles and permissions. However, the encryption it provides acts as an effective access control by restricting data access to those who possess the decryption key. Geeksforgeeks AES reference: https://www.geeksforgeeks.org/advanced-encryption-standard-aes/ AES Standard Reference: https://csrc.nist.gov/pubs/fips/197/final'
'W3C has a defined and publicly available Process for the Development and approval process of the specification as a recommended standard, including a public review. W3C Process Document reference: https://www.w3.org/2021/Process-20211102/'
'The effectiveness of DNS over HTTPS (DoH) is often evaluated through various means, including practical implementations and pilot projects. A 2019-paper related to the 17th International Conference on Emerging eLearning Technologies and Applications (ICETA) discusses DNS security in V2X networks and highlights DoH as a way to secure name services in V2X networks, which demonstrates the effectiveness of the specification. An overview of DNS security in V2X networks: https://ieeexplore.ieee.org/abstract/document/9040111'
'ETSI TS 119 612 can facilitate the modelling of business processes when it comes to anything related to trusted lists, as it can establish, locate, access and authenticate with security and makes available the trust service status information. ETSI TS 119 612 specification: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf'
'Syslog is not included in any national catalogue of recommended specifications whose Member State NIF has a high performance on interoperability according to NIFO factsheets. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards'
' Given that a verifiable credential often contains personally identifiable information (PII), implementers are strongly advised to use mechanisms while storing and transporting verifiable credentials that protect the data from those who should not access it. Mechanisms that could be considered include Transport Layer Security (TLS) or other means of encrypting the data while in transit, as well as encryption or data access control mechanisms to protect the data in a verifiable credential while at rest. Verifiable Credentials Privacy Considerations: https://www.w3.org/TR/vc-data-model/#privacy-considerations'
'SOAP 1.2 is a messaging protocol for exchanging information in a structured way, it uses XML for its message format. As the protocol is a messaging system for exchanging information in a structured way, it helps to promote the visibility and comprehensibility of the administrative rules. In addition, it is a key enabler for web services reuse across borders along with UDDI and WSDL. SOAP Reference: https://www.w3.org/TR/soap12/ Differences in SOAP Versions: https://www.ibm.com/support/knowledgecenter/en/SSAW57_8.5.5/com.ibm.websphere.nd.multiplatform.doc/ae/cwbs_soapverdiffs.html'
WS-BPEL does not directly conform with the main conditions to publish data as open data. However, this specification can be used for the consumption of open data by the definition of web services business process. WS-BPEL OASIS reference: http://docs.oasis-open.org/wsbpel/2.0/OS/wsbpel-v2.0-OS.html Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/en/
'Various EU Member States have are considering adoption the specification as their standard for the creation and publication of legal documents in a machine-readable format. AKN4EU reference: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/akn4eu'
'The specification does not foresee any support for multilingualism. Nevertheless, it does mention that cloud computing services may have operational policies such as requirements for support of minority user languages. Some territories also have strict laws and regulations around correct use of character sets in user interfaces (notably Asian characters and their usage), legal requirements to support mandatory “official” languages (some of which might have few real speakers). ISO 19941: https://www.iso.org/obp/ui/en/#iso:std:iso-iec:19941:ed-1:v1:en'
XAdES does not provide a cross sector reusable data model per se. The specification provides a set of conformance level for the basic features in the context of the European Internal Market.
'OAIS can indirectly help ensure data processing accuracy by promoting metadata quality controls, data integrity checks or preservation planning. Nonetheless, OAIS specification does not give specific provisions to perform them. OAIS specification: https://public.ccsds.org/Pubs/650x0m2.pdf'
12 Member States are recommending HTML in their ICT National Catalogues. This Member States are Croatia, Cyprus, Estonia, Germany, Greece, Malta, Norway, Poland, Slovenia, Spain, Sweden and UK. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
"Schema.org may contribute and promote the visibility of administrative procedures, rules data and services on the web. The specification promotes schemas for structured data (e.g. services, data) enabling potential users to find and use such data as services or relevant information. Up to date, there is no evidence of schema.org as a promising enabler of visibility, but there are ongoing projects such as the Schema.org profile of DCAT Application Profile for Data Portals in Europe (Schema.org profile of DCAT-AP, or DCAT-AP-SDO) that are working in this direction. Schema.org homepage reference, 'Documentation' section: https://schema.org/docs/documents.html DCAT-AP reference: https://op.europa.eu/en/web/eu-vocabularies/dcat-ap DCAT-AP-SDO reference: https://ec-jrc.github.io/dcat-ap-to-schema-org/"
After checking the different standard catalogues at supra-national level, there is no evidence of the inclusion of PDF/A within any European catalogue of standards. ICT technical specifications: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en CEN search tool catalogue: https://standards.cen.eu/dyn/www/f?p=CENWEB:105::RESET:::: CENELEC search tool catalogue: https://www.cenelec.eu/dyn/www/f?p=104:107:0::::FSP_LANG_ID:25
W3C Best Practices is not included in any Member States' catalogues of recommended specifications. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
"The EN 303 645 specification does not simplify the delivery of European public services, but can indirectly facilitate their delivery. The specification has been included in several initiatives supported by the EU cybersecurity certification framework for ICT products (see J. Pandza's presentation on the ENISA Cybersecurity Standardisation Event, and see EU cybersecurity certification framework reference). For example, there is the Eurosmart IoT Certification Scheme, which relies on the EN 303 645 specification, setting the first common certification scheme for IoT devices in Europe and facilitating the delivery of European public services. ENISA Cybersecurity Standardisation Event 2021, Jasper Pandza presentation: https://www.enisa.europa.eu/events/cybersecurity_standardisation_2021/std-2021-presentations EU cybersecurity framework reference: https://digital-strategy.ec.europa.eu/en/policies/cybersecurity-certification-framework Eurosmart IoT Certification Scheme reference: https://www.eurosmart.com/eurosmart-iot-certification-scheme/"
'Registered Organization Vocabulary helps to the enabling of visibility of administrative procedures, rules data, and services by providing a structured vocabulary for describing organisations that have gained legal entity status through a formal registration process. Furthermore, the Registered Organization Vocabulary, despite not being maintained anymore, is still used by the Open Standards for Linking Organizations (OSLO), more concrete in the application profile of "Slimme Stadsdistributie". The "Slimme Stadsdistributie" application profile reuses terms from the Registered Organization Vocabulary to represent the fundamental concept of a Geregistreerde Organisatie and its key properties, such as its registration identifier and its legal name. This ensures a common semantic understanding of what constitutes a registered organisation in the context of smart urban distribution. Registered Organization Vocabulary reference: https://www.w3.org/TR/vocab-regorg/ OSLO Smart City Distribution - Application profile Reference: https://data.vlaanderen.be/doc/applicatieprofiel/slimme-stadsdistributie/'
The purpose of TLS 1.2 is not related to long term preservation of electronic records. Therefore this criterion is considered not applicable to this specification
'CSV makes sure content is available on the web, structures data and makes it usable in a non-proprietary open format. So it can be said that CSV is independent from any technology or platform. Therefore reside in different places. CSV reference: https://datatracker.ietf.org/doc/html/rfc4180'
The specification is included in 7 Member States' catalogues of recommended specifications. Some examples of Member States including UDDI on their catalogues are the Netherlands, Spain or Belgium. See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'The purpose of RDF is not related to the provision of access control mechanisms. Therefore this criterion is not applicable to the specification. RDF primer document: https://www.w3.org/TR/rdf11-primer/'
'The Asset Administration Shell (AAS) makes no provision for a partial implementation since the specification is tailored for industrial manufacturing interoperability. Details of the Asset Administration Shell (AAS) https://industrialdigitaltwin.org/en/wp-content/uploads/sites/2/2024/06/IDTA-01001-3-0-1_SpecificationAssetAdministrationShell_Part1_Metamodel.pdf'
Core Criterion and Core Evidence Vocabulary is publicly available for implementation and use for free in Joinup's webpage. Therefore, it can be reused by the organisations, administrations, open communities, etc. that developed it. CCCEV reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-criterion-and-core-evidence-vocabulary
RDA specification and recommendation processes are open from inception. Individual membership to RDA is free and open to all, as long as individuals subscribe to the RDA Guiding Principles (https://rd-alliance.org/about/get-involved.html): • Openness – Membership is open to all interested individuals who subscribe to the RDA’s Guiding Principles. RDA community meetings and processes are open, and the deliverables of RDA Working Groups will be publicly disseminated. • Consensus – The RDA moves forward by achieving consensus among its membership. RDA processes and procedures include appropriate mechanisms to resolve conflicts. • Balance – The RDA seeks to promote balanced representation of its membership and stakeholder communities. • Harmonization – The RDA works to achieve harmonization across data standards, policies, technologies, infrastructure, and communities. • Community-driven – The RDA is a public, community-driven body constituted of volunteer members and organizations, supported by the RDA Secretariat. • Non-profit - RDA does not promote, endorse, or sell commercial products, technologies, or services. Organisations may join RDA as members for an annual fee. Full details are provided at https://rd-alliance.org/organisation/rda-organisation-affiliate-members/rda-organisational-membership.html RDA Specifications, upon delivery, are assessed by the RDA Technical Advisory Board (TAB) and feedback / comments are given. All outputs go through an open and transparent Request for Comments process of 1 month on the RDA web platform. Details on the process are available at - https://www.rd-alliance.org/groups/creating-and-managing-rda-groups/working-group-outputs.html
'There are some forums discussing the implementation of XFDL. In addition, papers assessing the specification and offering new functionalities can be found on the internet. Stackoverflow XFDL forum: https://stackoverflow.com/questions/tagged/xfdl Extensible Forms Description Language reference: https://www.w3.org/TR/NOTE-XFDL'
'The REST API is the most widely used API for client-server interface interaction, being implemented by large organisations such as Facebook or Amazon, thus demonstrating its maturity for the development of digital solutions/services. REST reference: https://restfulapi.net/ Amazon Web Services reference: https://docs.aws.amazon.com/apigateway/api-reference/ Facebook reference: https://zappysys.com/blog/get-data-from-facebook-in-ssis-using-rest-api/#:~:text=Facebook%20provides%20rich%20set%20of%20REST%20API%20to,popular%20programming%20languages%20%28e.g.%20C%23%2C%20Java%2C%20Ruby%2C%20Python%29.'
'UTF-8 does not provide access mechanisms on its own, but additional security measures such as user authentichation or authorisation can be implemented on top of the specification to guarantee access control mechanisms. UTF-8 specification: https://datatracker.ietf.org/doc/html/rfc3629'
'E-ARK CSIP has not been found recommended by any Member State. E-ARK CSIP specification: https://earkcsip.dilcis.eu/#introduction'
'UTF-8 is independent of any specification and can be implemented without dependencies with technologies or platforms. UTF-8 specification: https://datatracker.ietf.org/doc/html/rfc3629 '
PNG can be found along within the European Collaborative Platform, Joinup. However, it points to the W3C specification document not to the ISO. PNG in Joinup platform: https://joinup.ec.europa.eu/solution/portable-network-graphics-png-specification-second-edition/distribution/portable-network-graphics-png-specification-second-edition
'Domibus adheres to messaging standards such as the AS4 profile of the ebMS (ebXML Messaging Service) standard. This standardization promotes consistent data structures and formats during message exchange, which can aid in data portability by ensuring that data is correctly interpreted and processed by different systems. AS4 Profile of ebMS 3.0: http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/profiles/AS4-profile/v1.0/AS4-profile-v1.0.html Domibus specification: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/Domibus'
UDDI is available for free for its use and study at OASIS' webpage. See: http://www.uddi.org/pubs/uddi_v3.htm
'XACML is designed to be extensible, allowing organisations to adapt the specification to their specific needs. This flexibility helps in creating custom solutions that can still adhere to the visibility and management principles of XACML. XACML OASIS reference: https://docs.oasis-open.org/xacml/3.0/xacml-3.0-core-spec-os-en.html'
'ETSI EN 319 422 has the support of various communities listed in the following link as "Supporting Organizations", including Universities, private and public companies. The ESI technical committee provides public support to members and non-members alike, with different conditions depending on ETSI membership status. This support helps to increase the use of the specification and the specification itself by detecting weaknesses in implementation or any other relevant aspect of the specification's funtionalities Portal ETSI reference: https://portal.etsi.org/webapp/workprogram/Report_WorkItem.asp?WKI_ID=39422 ESI technical committe reference: https://www.etsi.org/committee/1399-es'
'The OASIS Security Services Technical Committee, in charge of the development of SAML 2.0, operates under RF on RAND Mode of the OASIS IPR Policy. The specification is licensed on a Royalty-free and (F)RAND basis. OASIS Commitee Referenece: https://www.oasis-open.org/committees/security/ipr.php OASIS Policies Guidelines: https://www.oasis-open.org/policies-guidelines/ipr'
PAdES (ISO 14533-3:2017) is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, it can define the interoperability aspects of the "e-Seal Preservation Service" and "e-Signature Preservation Service" ABBs of the EIRA Technical Infrastructure View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/solution/elis/release/v100
WS-BPEL is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, WS-BPEL can define the interoperability aspects of the "Orchestration Service", and "Orchestration component" ABBs of the EIRA Technical View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/solution/elis/release/v100
'The specification is mature enough to consider its use in the development of digital solutions/services as its documented use in an Italian government website mentioning the use of ETSI EN 319 532-3 in their Certified Email (PEC), providing technical rules that envisage eIDAS Regulation. ESI/REM service does not foresee to replace any other specification for exchanging transactions securily, as it is the default framework in this domain. ESI Wiki Link not Public, Log required: https://esiprivatewiki.etsi.org/ ETSI EN 319 532-3 reference: https://www.etsi.org/deliver/etsi_en/319500_319599/31953203/01.02.01_60/en_31953203v010201p.pdf REM SERVICES - Criteri di adozione degli standard ETSI - Italy Policy IT: https://www.agid.gov.it/sites/default/files/repository_files/rem_services_-_criteri_di_adozione_degli_standard_etsi_-_policy_it_1.0_28_maggio_2021.pdf'
ODF specification is not included in European Platforms as it needs to be paid, and the European Institutions using the EIF and other actions supports the usage of Open Standards.
There are some free online validators for MIME to check the compliance of MIME messages with the IETF standards. MIME online validator: https://www.mimevalidator.net/
FTPS is publicly available for implementation and use, and therefore for everyone to study, for free on IETF webpage. FTPS IETF reference: https://tools.ietf.org/html/rfc4217
'Domibus can somehow contribute to facilitating organisational interoperability agreements given that it provides a common and standardised tool for the communication and data exchange between different entities. Domibus specification: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/Domibus '
XAdES is part of the electronic signature stack of specifications, this group of specifications are aimed to ensure the availability and validation of signed data. Therefore, the implementation of eSignatures involving XAdES fosters secure and trustworthy data exchange.
'The SCIM protocol document explicitly addresses data protection and its aligment to relevant regulations. Some considerations include what to do in case of disclosure of sensitive information in URIs or secure storage and handling of sensitive data. However, the responsibility for ensuring compliance with data protection regulations rests on the organizations implementing SCIM and the broader ecosystem in which it is used. SCIM Protocol: https://datatracker.ietf.org/doc/html/rfc7644'
'ETSI TS 119 612 is a component derived from the actions implemented based on the Regulation (EU) No 910/2014 of the European Parliament and of the Council of 23 July 2014 on electronic identification and trust services for electronic transactions in the internal market. This regulation aims to enhance interoperability when it comes to the trust services of e-signatures in the European context. Regulation (EU) No 910/2014 of the European Parliament and of the Council of 23 July 2014 on electronic identification and trust services for electronic transactions in the internal market: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv:OJ.L_.2014.257.01.0073.01.ENG'
'ODRL is not a European Standard itself. Instead, it is a standardized language for expressing permissions, obligations, and constraints for digital content and services. Instead, ODRL is an open standard that has been developed by a community of stakeholders with a focus on providing a common framework for expressing digital rights. ODRL Community Group Home page: https://www.w3.org/community/odrl/'
The specification is independent from any specific tecnology. However, its serialisation is carried out using three different formats such as RDF, JASON-LD, and XML. W3C specification reference: https://www.w3.org/TR/odrl-vocab/#vocab-core
'While PROV can provide valuable insights into the lineage and relationships of administrative procedures and services, the comprehensibility of these elements requires consideration of other factors beyond the scope of the PROV family of documents. PROV Primer document: https://www.w3.org/TR/prov-primer/ PROV Ontology: https://www.w3.org/TR/2013/REC-prov-o-20130430/ PROV Data Model: https://www.w3.org/TR/2013/REC-prov-dm-20130430/'
The specification aims to provide a format for long-term storage and access to parliamentary, legislative and judicial documents that allows search, interpretation and visualization of documents. Therefore, LegalDocML can support and foster the long-term preservation of electronic records, especially legal texts. LegalDocML reference: https://www.oasis-open.org/committees/legaldocml/charter.php
'The effectiveness of CIM NGSI-LD API is often evaluated through various means, including practical implementations and pilot projects. For instance, a 2021-paper by ETSI is intended to complement the NGSI-LD information model normative specification, it is also intended to be complementary to the NGSI-LD Primer, which mainly explains how to use the NGSI-LD API in a more “hands-on” practical way, especially for the initial use cases considered location, which demonstrates the effectiveness of CIM NGSI-LD API. Guidelines for Modelling with NGSI-LD: https://www.researchgate.net/profile/Gilles-Privat/publication/349928709_Guidelines_for_Modelling_with_NGSI-LD_ETSI_White_Paper/links/6047dca2299bf1e07869576b/Guidelines-for-Modelling-with-NGSI-LD-ETSI-White-Paper.pdf'
'The purpose of Domibus is not related to the publication of data on the web. Therefore this criterion is not applicable to the specification. Domibus specification: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/Domibus'
By allowing the publication and discovery of web services, UDDI helps to reduce administrative burden avoiding administration and stakeholders to expend time searching for web services and improving the results while integrating services and exchanging data.
'ETSI TS 119 511 specification is distributed from the ETSI platform. ETSI’s mission is to provide platforms where interested parties come together and collaborate on the development and promotion of standards for Information and Communication Technology (ICT) systems and services. ETSI TS 119 511 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119511/01.01.01_60/ts_119511v010101p.pdf '
"The iCalendar specification allows for customization through the use of custom properties and parameters, enabling developers to add additional data and metadata specific to their application's requirements. This flexibility allows for tailoring the standard to suit various use cases and customizing the representation of calendar data as needed. iCalendar specification: https://www.rfc-editor.org/rfc/rfc5545"
'Clear and well-structured YAML can enhance e-accessibility by making it easier for screen readers and other assistive technologies to interpret the content. Moreover, including comments describing the purpose of specific settings or options can benefit developers, testers, and maintainers, improving overall accessibility. YAML specification: https://yaml.org/spec/1.2.2/'
SHACL is a web standard whose only purpose is RDF data graphs validation. Therefore, it is not a commonly accepted business process modelling standard or specification.
"While ISO/IEC 19944-1 does not delve into the technical details of implementing these mechanisms, it provides a foundation for organisations to establish appropriate confidentiality measures within their cloud environments. By adopting the classification scheme outlined in ISO/IEC 19944-1, organisations can identify and categorize data based on its sensitivity, including confidential information. This classification enables organisations to apply appropriate confidentiality mechanisms based on the data's classification. ISO/IEC 19944-1 specification: https://www.iso.org/standard/60545.html"
'In the context of e-archiving, OAIS can be an efficient tool to simplify processes given it provides a reference model addressing data management, ingestion, access and dissemination of information as well as the migration of information to new media and forms, thus, enabling digital service delivery channels. OAIS specification: https://public.ccsds.org/Pubs/650x0m2.pdf '
'While SCIM defines mechanisms for authentication and authorization, the guarantee of authenticity and authentication of the roles involved in data transactions ultimately depends on the implementation of SCIM and the security practices adopted by the participating entities. SCIM relies on standard HTTP authentication mechanisms. The choice of authentication method is not explicitly defined in the SCIM specification and is left to the implementer. SCIM: https://scim.cloud/'
'The main purpose of this Core Vocabulary is to support the exchange of information between organisations that define criteria and organisations that respond to these criteria by means of evidences. This Core Vocabulary helps to comprehend the administrative rules and data of public administration. Core Criterion and Core Evidence Vocabulary reference (v1.0.0): https://joinup.ec.europa.eu/release/core-criterion-and-core-evidence-vocabulary-v100 '
The Standard for Public Code provides public organizations with a model for building their open source solutions to enable successful future reuse by similar public organizations in other places. Besides, the standard also aims to make sure that the generated code is published to allow reuse for other parts and documented accordingly enabling other implementations. In this sense, the specification in itself fosters the publication of solutions as open data but also can contribute to creating solutions focused on the publication of open data. The Standard for Public Code webpage: https://standard.publiccode.net/
By associating a name to an IP, DNS facilitates the identification of the content of domains and therefore, reduces administrative burden.
The specification is included in 8 Member States' catalogues of recommended specifications. This Member States are Croatia, France, Malta, the Netherlands, Norway, Poland Spain and Sweden. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'Joinup offers several services that aim to help e-Government professionals share their experience with each other. Joinup supports them to find, choose, re-use, develop and implement interoperability solutions. DQV is mentioned in some Joinup entries as a discussion topic, although is not distributed in the platform. DQV Joinup reference: https://joinup.ec.europa.eu/collection/access-base-registries/solution/abr-bregdcat-ap/discussion/issue-06-quality-datasets'
The purpose of the specification is not related to the publication of data as Linked Open Data. Therefore, e-Delivery SMP 1.10 is not fostering the publication of Linked Open Data.
'The Advanced Encryption Standard provides a standardised method for protecting data by encrypting it in a common format. This standard facilitates collaboration by ensuring data is encrypted and decrypted uniformly. An example can be found looking at VeraCrypt project. The aim of this initiative is to encrypt partitions or storafe devices, in an automatic and fast manner. VeraCrypt AES project: https://veracrypt.eu/en/Home.html AES Standard Reference: https://csrc.nist.gov/pubs/fips/197/final'
"Besides CELAR and Indigo projects, the European Union is committed to the development of open source utilities that can be used in industry as well as in research. It is the case of the RADON project, where TOSCA is used as the project's Infrastructure as code (IaC) format centerstage. RADON project reference: https://radon-h2020.eu/"
The Registered Organization Vocabulary is a simplified, reusable and extensible data model that captures the fundamental characteristics of a legal entity. It facilitates the information exchange between business sectors and organisations, fostering the digitization of the administrations' transaction. Therefore, it reduces the administrative burden by avoiding the exchange of non-digital documents. RegOrg Joinup reference: https://joinup.ec.europa.eu/solution/registered-organization-vocabulary
'Domibus can contribute to the comprehensibility of data and services by promoting standardized messaging, and including metadata withing messages, thus providing additional context about the data being exchanged. This metadata enhances comprehensibility by offering insights into the purpose, source, and content of the messages. Domibus specification: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/Domibus'
The XACML specification includes data structures and models that can be considered as reusable models for establishing data policies, the data involved and the processes involved. XACML OASIS reference: http://docs.oasis-open.org/xacml/3.0/errata01/xacml-3.0-core-spec-errata01.html
There are no existing European standards with market uptake covering the same area as RPKI.
'HTTP can facilitate digital communication and online services in several ways. It helps reduce network usage and latency when accessing online public service portals, ensuring faster and more efficient service delivery. The caching mechanism allows for the storage and reuse of data, which decreases the number of requests sent to servers. This not only improves performance but also reduces the load on the server side, enhancing reliable access to public services. HTTP /1.1 RFC 2616 Reference: https://www.rfc-editor.org/rfc/rfc2616.html HTTP/1.1 Caching, RFC 9111 Reference: https://www.rfc-editor.org/rfc/rfc9111'
There are already existing tools for testing the implementation of XACML polocies. The Security Pool Policy allow to check for enhancements in a XACML implementation. Also, a tool known as WS2 Identity Server is available under its own licence to allow the testing of XACML implementations. WS2 Identity Server https://docs.wso2.com/display/IS541/Using+the+XACML+TryIt+Tool
'The ebXML specification offers a standardised format for exchanging messages between users. In this context, the ebXML specification also facilitates business collaborations through the exchange of XML documents in a standardised format. ebXML interoperability: https://www.tutorialspoint.com/ebxml/ebxml_quick_guide.htm ebXML RegRep OASIS reference: https://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html'
'Extensible Forms Description Language is already associated to EIRA ABBs in the EIRA Library of Interoperability Specifications (ELIS). More specifically, Extensible Forms Description Language can define the interoperability aspects of the "Forms Management" ABB of the EIRA Technical View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/v610 Extensible Forms Description Language reference: https://www.w3.org/TR/NOTE-XFDL'
'The purpose of DPV is not related to data processing accuracy, therefore, this criterion is not applicable to the specification. DPV specification: https://w3c.github.io/dpv/primer/'
'The ELI specification is supported by the ELI Task Force, which includes representatives from multiple European countries. The ELI TF, which consists of European countries that have implemented ELI, is responsible for defining ELI-related specifications and ensuring their future evolution. This community is public and its work, including the ELI specifications and best practice guides, is freely accessible. ELI Task Force reference: https://eur-lex.europa.eu/eli-register/about.html ELI Best Practices reference: https://joinup.ec.europa.eu/collection/digital-skills-public-sector/solution/interoperable-europe-academy /european-legislation-identifier'
'ODRL is maintained by W3C which is an international community developing open standards. The ODRL community provides forums for discussion, collaboration, and sharing of best practices related to the implementation and use of ODRL. W3C Consortium home page: https://www.w3.org/Consortium/ ODRL Community: https://www.w3.org/community/odrl/ W3C Working Group Github space: https://github.com/w3c/odrl'
'The purpose of XML is to store, transport and exchange data through interoperable systems. Moreover, XML defines a set of rules for encoding documents in a human-readable format and machine-readable format enhancing the reusability of data and stimulating the interoperability of systems and services. Additionally, W3C develops its specification independently from any vendor. Thus, the adoption of XML does not hamper the data portability of data expressed with it. In fact, the adoption of XML fosters data portability, especially between REST APIs. See: https://www.w3.org/TR/2006/REC-xml11-20060816/'
"IPv6 can work with VPN's to guarantee restrictions who can access to information. One example is the OpenVPN, which supports IPv6 natively, and is highly configurable with extensive control options. Moreover, the ACL functionality in IPv6 helps to establish an access control. Access Control Lists for IPv6 reference: https://www.cisco.com/c/en/us/td/docs/routers/ios/config/17-x/sec-vpn/b-security-vpn/m_ip6-acls-xe.html#GUID-C7F3B9EF-CD1E-45E4-8A48-F301C746FAC1 OpenVPN reference: https://support.openvpn.com/hc/en-us/articles/17891771293083-Access-Server-Enable-and-configure-IPv6-to-transport-IPv6-packets-through-the-VPN-tunnel"
"The purpose of ISO 639-2 is not related to the exposure of interfaces to access public administrations' services. Therefore, this criterion is not applicable to this specification. ISO 639-2 reference: https://www.iso.org/standard/4767.html"
'As the sum of all hardware and software components that make up the environment in which the NFV is deployed, the NFVI addresses security aspects through different standardised modules. NFVI Deliver, Infrastructure Overview section 6.7: https://www.etsi.org/deliver/etsi_gs/NFV-INF/001_099/001/01.01.01_60/'
'As SMP is maintained by OASIS which is an international community developing open standards, it encourages people to join and contribute to the development and maintenance of old and new specifications and share their data once a specification its finished on European platforms and the eDelivery User Community. OASIS Community Reference: https://www.oasis-open.org/join-2/ eDelivery User Community: https://ec.europa.eu/digital-building-blocks/wikis/display/EDELCOMMUNITY/eDelivery+User+Community'
'OGC TrainingDML-AI is not included in any national catalogue of recommended specifications whose Member State National Interoperability Framework has a high performance on interoperability according to NIFO factsheets. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss'
'Currently the Asset Administration Shell (AAS) is maintained by the Platform Industrie 4.0 and has a dedicated working group which is open to contribution on github. Asset Administration Shell (AAS) Github https://github.com/admin-shell-io/aas-specs/blob/master/CONTRIBUTING.md Details of the Asset Administration Shell (AAS) https://industrialdigitaltwin.org/en/wp-content/uploads/sites/2/2024/06/IDTA-01001-3-0-1_SpecificationAssetAdministrationShell_Part1_Metamodel.pdf'
'The XML specification itself does not directly address the protection of personal data managed by Public Administrations or any specific data privacy concerns. XML is a markup language designed for the structuring and representation of data, allowing for the exchange and storage of information in a standardized format. Therefore this criterion is not applicable to the specification.'
'TLS 1.3 is recognised by the Multi-Stakeholder Platform on ICT Standardisation of the European Commission. This recognition also underscores the role of TLS 1.3 in advancing trusted communication within European cross-border services, aligning with the EU’s commitment to robust cybersecurity frameworks. European Multi-Stakeholder Platform on ICT Standardisation: https://digital-strategy.ec.europa.eu/en/policies/multi-stakeholder-platform-ict-standardisation Commission Implementing Decision (EU) 2017/2288 of 11 December 2017 on the identification of ICT Technical Specifications for referencing in public procurement Reference: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32017D2288'
'DIDs is included in the EUOS, the EU Observatory for ICT Standardisation. Moreover it is also included in the Data Space Support Center (DSSC) Standards catalogue, where it covers the trust layer. EUOS repository: https://www.standict.eu/standards-repository/decentralized-identifiers-dids-v10-core-architecture-data-model-and DSSC standards catalogue: https://dssc.eu/space/SE1/185794711/Data+Sovereignty+and+Trust+standards+and+technologies+landscape'
"There is no direct assessment on the efficiency of the ebXML specification. However, according to the OASIS Technology Reports, several studies on different digital solutions from the public and private domain indirectly assess the specification's efficiency. OASIS Technology Reports reference: http://xml.coverpages.org/ebXML.html"
The specification eases the identification of parties capabilities and information to make proper and reliable data exchange between parties. Therefore, by implementing the specification administrative information is clearer and available to every party interested. The specification: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505000
'Mime is already mapped in the EIRA Libary of Interoperability Specifications (ELIS). More specifically, MIME covers the "Data exchange" ABB of the EIRA technical view. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/v501'
'The French "General framework for improving accessibility" (RGAA) includes the WAI-ARIA specification in their e-accessibility policies. This implies a willingness to use this technology. RGAA reference: https://www.numerique.gouv.fr/publications/rgaa-accessibilite/methode-rgaa/criteres/'
CAMSS Assessment of TSP EIF Scenario v1.0.0
"IEEE Std 802.3-2022 efficiency is evaluated through industry feedback, testing, research, adoption, and ongoing updates. It's being tested in IEEE projects to ensure it meets requirements. The standard's adaptability allows the working group to address evolving needs. As a result, numerous new projects are currently being developed to leverage its capabilities. IEEE Working Group Projects: https://www.ieee802.org/3/ IEEE Working Group Details: https://standards.ieee.org/ieee/802.3/10422/ IEEE Std 802.3-2022 Reference: https://ieeexplore.ieee.org/document/9844436"
'REST is an architecture style that defines how different systems should interact. REST APIs generate a way of accessing web services in a simple and flexible way without having any processing, thus explicitly addressing and enabling e-accessibility REST reference: https://restfulapi.net/'
'The Advanced Encryption Standard is assessed and discussed in various forums and across the Internet. For example, in the Autoit Web can be found some forums that discuss the Advanced Encryption Standard, and its implementation in different contexts. Autoit Advanced Encryption Standard: https://www.autoitscript.com/forum/topic/78745-advanced-encryption-standard-aesrijndael-udf/ AES Standard Reference: https://csrc.nist.gov/pubs/fips/197/final'
'XML is a business domain agnostic specification. See:https://www.w3.org/TR/2006/REC-xml11-20060816/'
'The main purpose of the specification is the exchange of information among systems that are “open” to one another, for this purpose the specification defines multiple layers where the primarily machines can interact in a consistent manner. OSI reference https://www.iso.org/standard/20269.html'
'The IAASB is dedicated to operating as transparently as possible. IAASB meetings are open to the public and meeting agendas, agenda papers, and meeting highlights are posted on the website. In addition, the website includes project histories, audio recordings of the IAASB meetings, IAASB Exposure Drafts and all comments made on those drafts by stakeholders. IAASB reference: https://www.iaasb.org/about-iaasb'
"Schema.org was founded by major technology companies and its use extends to the world's leading search engines, such as Google and Yahoo! (see Schema.org homepage reference, 'About Schema.org' section). Besides, the schema.org project has supported the development of another specification in order to better represent web content and display it in a useful and relevant way, the HTML Microdata tags (see Schema.org reference, Getting started section). In this sense, schema.org will not only help search engines to better perform, but also would increase its market applicability in the wide web community, proving its market acceptance: the more web services implement these HTML tags, the more widespread use the specification will achieve in the market. Schema.org homepage reference, 'About Schema.org' section: https://schema.org/docs/about.html Schema.org reference, Getting started section: https://schema.org/docs/gs.html HTML Microdata reference: https://dev.w3.org/html5/md-LC/"
HTTPS is the main protocol underlying the world wide web. The protocol supports the exchange of high amounts of data.
'DAPS can typically be customised to align with specific organizational requirements and use cases. Customisation allows organizations to tailor the provisioning process, attribute mappings, workflows, and other aspects of the system to meet their unique needs. For example, a user could customise the mapping of attributes between identity sources and target systems. DAPS: https://github.com/International-Data-Spaces-Association/IDS-G/tree/main/Components/IdentityProvider/DAPS'
CAMSS Assessment of Better Regulation Toolbox EIF Scenario v1.0.0
'Registered Organization Vocabulary is a vocabulary built on established standards to facilitate interoperability. However, the inherent characteristics of RDF and the development of Core Business Vocabulary (CBV) suggest that there were areas where the approach could be further optimised for broader and more efficient data modeling of legal entities. Registered Organization Vocabulary reference: https://www.w3.org/TR/vocab-regorg/ Publication of the Core Business Vocabulary as RegOrg on the W3C standards track Reference: https://interoperable-europe.ec.europa.eu/collection/registered-organization-vocabulary/news/publication-core-busin Core Business Vocabulary Reference: https://semiceu.github.io/Core-Business-Vocabulary/releases/2.1.0/'
'As a specification created to provide a standard-way to express credentials on the Web, there are several features that ensure the alignment with this definition. One example is the credential metadata, which contains crucial information about the credential itself, such as the credential type, issue date, and expiration date. Another example would be proofs like a digital signature, ensuring that the credential genuinely originates from the claimed issuer and has remained untampered. These facts increase the reliability of the exchanged data. Verifiable Credentials: https://www.w3.org/TR/vc-data-model/ '
'As a protocol for mantaining and accessing Directory Services, LDAP is a useful tool to display of user information in a readable manner. Comprehensibility of data therefore is supported by the fact that it permits to access user information in the network in a structured, human-readable manner. LDAP Directory Information Models: https://datatracker.ietf.org/doc/html/rfc4512 LDAP IETF reference: https://tools.ietf.org/html/rfc4511'
The purpose of XSLT is not related to organisational interoperability. Therefore, this criterion is not applicable to the specification.
SAMM provides an effective and measurable way for all types of organizations to analyze and improve their software security posture. Applying the model, the organisation can develop and improve software applications in terms of security. Therefore, the specification can be used within the creation and maintenance of innovative solutions since security is a key aspect. SAMM webpage: https://owaspsamm.org/ SAMM documentation: https://github.com/OWASP/samm/blob/master/Supporting%20Resources/v2.0/OWASP-SAMM-v2.0.pdf
SAMM is a set of criteria that supports all types of organizations in developing and improving software solutions. It supports the complete software lifecycle and is technology and process agnostic, allowing its maximum reuse. SAMM webpage: https://owaspsamm.org/ SAMM documentation: https://github.com/OWASP/samm/blob/master/Supporting%20Resources/v2.0/OWASP-SAMM-v2.0.pdf
'The specification is intended solely for documenting metadata related to public code projects and does not aim to support or regulate secure data exchange. It lacks provisions for security or privacy frameworks and does not establish protocols for handling sensitive data or ensuring secure communications. Therefore, its scope does not align with the data exchange security and privacy requirements outlined in EIF Recommendation 15. Publiccode.yaml documentation: https://docs.italia.it/italia/developers-italia/publiccodeyml-en/en/master/index.html'
'UTF-8 is maintained by IETF which is an international community developing open standards. About IETF: https://www.ietf.org/about/ '
'XSD 1.1 is an open specification that can be used independently from other technologies or platforms. However, XSD 1.1 is defining datatypes which depend on definitions in XML and Namespaces in XML. This fact is not hampering the adoption of XSD as XML is worldwide adopted. XSD Reference: https://www.w3.org/TR/2012/REC-xmlschema11-1-20120405/'
The purpose of the Core Location Vocabulary is to capture the fundamental characteristics of a location, represented as an address, a geographic name or geometry. It was developed from November 2011 until February 2012. It had some updates, and it was finally published in May 2012. This fact shows that CLV is mature enough for its use in the development of products and services. CLV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-location-vocabulary
No overlap has been detected with European standardisation organisations activities at EU level. This conclusion is based on the work programme of CEN and ETSI as published on their respective websites, and on the ENISA Programming Document 2018-2020
ASiC is included in the Dutch national catalogue of recommended specifications. The National Interoperability Framework (NIF) of the Netherlands is fully aligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. See: https://joinup.ec.europa.eu/collection/national-interoperability-framework-observatory-nifo/nifo-factsheets
The specification allows cross-domain single sign-on, which reduces the administrative burden of the system administrators and the users. By using SAML 2.0, the system administrator is prevented from providing several authentication tokens and, the user does not have to deal with several credentials. In addition, the use of the specifications helps to enhance and foster digital communication between administrations and users avoiding the non-digital data exchange.
The purpose of CSS is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification. CSS v2.1 W3C reference: https://www.w3.org/TR/2011/REC-CSS2-20110607/
CPOV defines a data model for describing public organisations in the European Union. The Core Public Organisation Vocabulary addresses specific needs of businesses, public administrations and citizens across the European Union. CPOV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-organisation-vocabulary
8 Member States are recommending LDAP in their ICT National Catalogues. This Member States are Croatia, France, Germany, Greece, Malta, Netherlands, Spain and Sweden. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'CPOV is useful for modeling of business processes in public administrations. It CPSV and CPOV addresses the need for public administrations to describe their services and events in a common way. Moreover, the CPOV provides the ability to link public services to public organizations, hence defining which organization has the authority over specific public services. CPOV Joinup reference: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/core-public-organisation-vocabulary/distribution/core-public-organisation-vocabulary-version-100-pdf'
XSD 1.1 is defining the schema and datatypes in order to define and constraint the structures and content included in XML files. Moreover, XSD 1.1 is describing an abstract data model which provides details on the schema definition. Therefore, XSD is defining a cross-sector reusable data model. See: https://www.w3.org/TR/xmlschema11-1/
Data on the Web Best Practices was produced in 2004 by W3C, and it has the full support from the W3C group which is an international community where Member organizations, a full-time staff, and the public work together to develop Web standards. W3C Reference: https://www.w3.org/TR/dwbp/
The purpose of HTTP is not related to the long-term preservation of electronic records and other kinds of information. Therefore, this criterion is not applicable to this specification
'OpenTelemetry is associated with EIRA ABB's in the EIRA Library of Interoperability Specifications (ELIS). More specifically, it is associated with the "Artificial Intelligence" and "Audit" ABBs from the "Technical-Application" View and the "Analytics" and "Telemetry" ABBs from the "Technical-Infrastructure" View of the current EIRA Library Of Interoperability Specifications (ELIS). EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /solution/elis'
SAMM is not included in any Member States' catalogues of recommended specifications. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'Verifiable Credentials can play a role in facilitating organizational interoperability agreements, particularly in the context of identity management and secure exchange of private personal data. Verifiable Credentials: https://www.w3.org/TR/vc-data-model/'
'At the moment of performing the assessment, no initiative at national or European level has been found to use ISO 19941 to cover privacy aspects. ISO 19941: https://www.iso.org/obp/ui/en/#iso:std:iso-iec:19941:ed-1:v1:en '
'The classification scheme outlined in ISO/IEC 19944-1 can be adapted and tailored to suit the specific needs and circumstances of an organization. This means that organizations can choose to implement certain elements or categories of the classification scheme that align with their data management objectives and priorities. ISO/IEC 19944-1 specification: https://www.iso.org/standard/60545.html '
'Core Vocabularies allow you to choose properties according to the needs of an organization. In this way, if an Organization only needs to capture data on the organizational structure, it is not necessary to include other properties which captures data far from our interests. CPOV partial implementations: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/core-public-organisation-vocabulary/distribution/core-public-organisation-vocabulary-version-100-pdf'
'DCAT supports the evolution and implementation of European Public Services by enhancing the searchability and discoverability of datasets across borders. DCAT is an interoperability enabler. DCAT (v2.0.0) reference: https://www.w3.org/TR/vocab-dcat-2/ '
The purpose of CAdES is not related to the publication of public data as open data. Therefore, this criterion is not applicable to this specification. CAdES ISO reference: https://www.iso.org/standard/64756.html CAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/101700_101799/101733/02.01.01_60/ts_101733v020101p.pdf
At least 7 Member States are recommending HTTPS in their ICT National Catalogues. See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'The specification is not related to the publication of public data as open data. Therefore this criterion is not applicable to this specification. UDDI reference: https://www.oasis-open.org/standard/uddi/'
'E-ARK CSIP has been found to be included in the catalogue/repository of archival solutions of the Center for Technology Transfer (CTT) from the government of Spain E-ARK CSIP specification: https://earkcsip.dilcis.eu/#introduction CTT electronic archive: https://administracionelectronica.gob.es/ctt/verPestanaDescargas.htm?idIniciativa=archive'
DCAT-AP is part of the Belgian catalogue of recommended specifications. See: https://www.belgif.be/nl/specifications
"ETSI TS 119 612 enables the exposure of interfaces by allowing Trusted List Scheme Operators (TLSO) to make TL's available through HTTP. TLSOs may also in addition support publication through LDAP or FTP. ETSI TS 119 612 specification: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf"
'Long-term preservation of data, information, and electronic records involves considerations that extend beyond the scope of the OSI model. Therefore, this criterion is considered not applicable to this specification. ISO/IEC 7498:1: https://www.iso.org/standard/20269.html'
CPOV can be found for free along within the European Collaborative Platform, Joinup. CPOV in Joinup platform: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-organisation-vocabulary
'The specification mentions mutliple other specifications across the reference document, such as ETSI EN 319 412-2, ETSI EN 319 412-3, etc... ETSI EN 319 422 reference: https://www.etsi.org/deliver/etsi_en/319400_319499/319422/01.01.01_60/en_319422v010101p.pdf ENISA pdf reference: https://www.enisa.europa.eu/publications/towards-a-harmonised-conformity-assessment-scheme-for-qtsp-qts/view/++widget++form.widgets.fullReport/@@download/ENISA+Report+-+Recommendations+for+technical+implementation+of+the+eIDAS+Regulation.pdf'
The specification is independent of any software, hardware, or operating system. So it can be said that OpenPM2 is independent of any specific technology or platform. Additionally, OpenPM2 provides a set of tools that can be used for the development of projects implementing this methodology. OpenPM2 specification reference: https://op.europa.eu/en/publication-detail/-/publication/ac3e118a-cb6e-11e8-9424-01aa75ed71a1/language-en/format-PDF/source-83307127
'WSDL provides a standardized way to define the inputs, outputs, and operations of a web service, it is not inherently a tool for modeling business processes. W3C WSDL specification: https://www.w3.org/TR/wsdl20/'
The purpose of UTF-8 is not related to organisational interoperability. Therefore, this criterion is not applicable to the specification.
'The purpose of ISO 3166-1 is not related to secure exchange of data. Therefore, this criterion does not apply to this specification. ISO 3166-1 reference: https://www.iso.org/standard/72482.html'
'There is no Member State that includes Core Criterion and Core Evidence Vocabulary in their national catalogue with the National Interoperability Framework (NIF) aligned with at least 2 out of 3 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. NIFO factsheets: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public-administration-factsheets-2022 CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards '
'EN 303 645 is associated to the consumer IoT devices domain and is not intended to be used in other domains. Therefore, the specification does not allow customisation. EN 303 645 reference: https://www.etsi.org/deliver/etsi_en/303600_303699/303645/02.01.01_60/en_303645v020101p.pdf'
XHTML fosters e-accessibility helping people with disabilities to understand and navigate through web and mobile web applications with friendly tools and proper information formats. Moreover, the Regional Government of Bizkaia developed his website to promote the integration of groups with disabilities into the Public Administration of Bizkaia. They used XHTML 1.0 recommendations and CSS2. XHTML 1.0 implemented in e-accessability project: https://joinup.ec.europa.eu/collection/einclusion/document/eaccesibility-public-administration-bizkaia-bizkaianet
'There is no Member State that includes EN\xa0319\xa0422 in their national catalogue with its National Interoperability Framework (NIF) in alignment with the three categories: 1. Conceptual model for integrated public services provision, 2. interoperability layers, and 3. interoperability principles. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards NIFO Factsheets: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public-administration-factsheets-2022'
PNG is an image extension which allows visualizing and storing images. However, as they cannot be protected with a password or something, everyone who has access to a PNG file can visualize it. PNG W3C reference: https://www.w3.org/TR/PNG/ PNG ISO reference: https://www.iso.org/standard/29581.html
'OSI contributes to improve the delivery of public services since it is designed for being used by all the interconnected systems, therefore if Governments and public sector organisations implement it, they will enhance the delivery of services, improving interoperability and portability of data. OSI reference https://www.iso.org/standard/20269.html'
'The purpose of Core Location Vocabulary is not related to the secure processing of data. Therefore this criterion is considered not applicable to the specification. Core Location Vocabulary: https://interoperable-europe.ec.europa.eu/collection/semic-support-centre/solution/core-location-vocabulary/release/100'
'IPv6 can be found through EurLex in a regulation. The "Regulation (EU) 2019/881 of the European Parliament and of the Council of 17 April 2019 on ENISA (the European Union Agency for Cybersecurity) and on information and communications technology cybersecurity certification and repealing Regulation (EU) No 526/2013 (Cybersecurity Act)" mentions the IPv6 specification as a key protocol for the security of the public core of the open internet and the stability of its functioning. Moreover, IPv6 can also be found in "Action Plan for the deployment of Internet Protocol version 6 (IPv6) in Europe". In this document it is explained that the European Commission will disseminate best practices and will work with vendors to provide full IPv6 functionality in terms of privacy. EurLex "Regulation (EU) 2019/881 of the European Parliament and of the Council of 17 April 2019 on ENISA (the European Union Agency for Cybersecurity) and on information and communications technology cybersecurity certification and repealing Regulation (EU) No 526/2013 (Cybersecurity Act)" reference: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32019R0881&qid=1729248000483 EurLex "Action Plan for the deployment of Internet Protocol version 6 (IPv6) in Europe" reference: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:52008DC0313&qid=1729248000483'
The specification is included within the European Single Procurement Document (ESPD) initiative, which is a cross border initiative that aims to simplify the steps when procuring public contracts. The initiative has been running since years ago, and although is not mandatory to use, Member States acting as contracting authorities are able to publish tenders. These tenders can be applied across borders. Therefore, it can be considered as an interoperability agreement between public administrations at supra-national level.
The specification provides a common method for the interoperability of systems when referring to access rights and licensing. This is a key aspect when developing any solution, including innovative solutions. Besides, as a core vocabulary it can be extended to adapt the needs of users allowing to get the maximum benefit of the implementation. The working group in charge of ODRL development provides a set of implementers and the results of the implementations, which, as can be read in the table from the following resource, it is positive. Meaning that ODRL is a good asset and fosters the creation of solutions, including innovative ones. W3C working group implementators report: https://w3c.github.io/poe/test/implementors
'There is no evidence that the specification has been explicitly endorsed by any European Union member state. OGC TrainingDML-AI: https://www.ogc.org/standard/trainingdml-ai/'
MIME is available for its use and implementation on IETF's webpage defined in several RFCs. MIME reference 1: https://tools.ietf.org/html/rfc2045 MIME reference 2: https://tools.ietf.org/html/rfc2046 MIME reference 3: https://tools.ietf.org/html/rfc2047
'13 Member States are recommending RDF in their ICT National Catalogues. CAMSS list of standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
'ETSI TS 119 512 is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, ETSI TS 119 512 can define the "e-Signature Creation Service" and the "e-Signature Verification and Validation Service" ABB of the EIRA Technical view. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/v110 '
After having researched the effectiveness and efficiency of the ADMS, no study or documentation assessing the specification in terms of effectiveness and efficiency has been found to justify this criterion.
'The purpose of IPsec is not related to the reuse of information when needed. Therefore this criterion is considered not applicable to the specification. IPSec reference: https://www.rfc-editor.org/rfc/rfc6071.html'
W3C has provided a validator which allows to test and validate HTML documents including HTML5. Additionally, HTML5 test provides a Markup Validation Service for free to validate HTML5 implementations. See: https://validator.w3.org/ https://html5test.com/
'The specification supports diverse technological environments given that ensuring broad applicability and adaptability to multiple contexts, from configuration management to data serialization between other fuctionalities. YAML specification: https://yaml.org/spec/1.2.2/'
'Genericode is part of eSubmission, a public European initiative created to facilitate the submission of regulatory information concerning marketing authorisations application for medicinal products to National Competent Authorities and EMA (European Medicines Agency) as well as to streamline the business process, standards for electronic submissions have been developed. The electronic Common Technical Document (eCTD) 4.0 Implementation package contains the updated eCTD v4.0 EU M1 Implementation Guide and updated controlled vocabulary lists in machine-readable genericode format. eSubmission: https://esubmission.ema.europa.eu/ ICH eCTD v4.0: https://www.ich.org/page/ich-electronic-common-technical-document-ectd-v40'
'The TrainingDML-AI Standard is designed to be technology agnostic. It defines a UML model and encodings for machine learning training data, which can be implemented in various technologies. OGC TrainingDML-AI Standard: https://docs.ogc.org/is/23-008r3/23-008r3.html'
'IPsec can establish secure Virtual Private Network (VPN) connections, allowing authorised users to access services and data securely over the internet. For example, government employees or public service agents can securely access centralised systems from remote locations, enabling efficient delivery of services without compromising security. IPSec reference: https://www.rfc-editor.org/rfc/rfc6071.html'
'The Publiccode.yaml is an Italian initiative. Italy has reached a good performance when it comes to the EIF monitoring mechanisms, and specifically the last NIFO Factsheets. According to the specification documentation, there is also Germany which is starting to use the standard for describing software. In this case, Germany achieves good levels for the elements that there is data available, but exist a significant quanity of principles that Germany does not have information to analyse it, therefore, it is difficult to consider the results positive. Publiccode.yaml documentation: https://docs.italia.it/italia/developers-italia/publiccodeyml-en/en/master/index.html NIFO Factsheets Italy: https://joinup.ec.europa.eu/sites/default/files/inline-files/DPA_Factsheets_2021_Italy_vFINAL.pdf NIFO Factsheets Germany: https://joinup.ec.europa.eu/sites/default/files/inline-files/DPA_Factsheets_2021_Germany_vFinal.pdf'
'As for all eGovernment-related Vocabularies, the SEMIC action from the ISA2 is the responsible for the maintenance and growth of the ADMS development, as well as the community around it. Semic in Joinup: https://joinup.ec.europa.eu/collection/semic-support-centre'
'By employing a common data model, adhering to platform-neutral principles, YAML can be effectively implemented across a wide range of platforms. YAML specification: https://yaml.org/spec/1.2.2/'
By adopting this standard every organisation contributes to securing their own routing and ensures that problems caused by others are not spread further. The specification contributes to a safe and secure internet.
'As for all eGovernment-related Vocabularies, the SEMIC action from the ISA2 is the responsible for the maintenance and growth of the CPSV-AP development, as well as the community around it. Semic in Joinup: https://joinup.ec.europa.eu/collection/semic-support-centre'
'The purpose of Extensible Forms Description Language is not related to the publication of public data as open data. Therefore this criterion is not applicable to the specification. Extensible Forms Description Language reference: https://www.w3.org/TR/NOTE-XFDL'
'EuroVoc indirectly aids in long-term preservation by providing a standardized system for organizing information, facilitating its accessibility and understanding over time. EuroVoc: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource /dataset/eurovoc'
"ebXML provides a set of components enabling users to store and work with any type of electronic content. The specification's ebRIM and ebRS components provides an ebXML infrastructure model, as well as a service interface contributing to this end. Therefore, ebXML facilitates the modelling of business processes. ebXML RegRep OASIS reference: https://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html"
'The ELI specification simplifies the delivery of European public services. By making legislation available online in a standardized format, it facilitates the exchange and reuse of legal information across borders. This not only promotes the development of new services but also makes information flows more effective, potentially shortening the time taken to publish legislation. Therefore, the ELI specification plays a significant role in administrative simplification. ELI reference: https://eur-lex.europa.eu/eli-register/about.html'
"The Test Bed can be extended where needed to support domain-specific capabilities. For example, you can add processing handler extensions to the test bed's capabilities to undertake actions that it does not natively support. GITB TDL reference: https://www.itb.ec.europa.eu/docs/tdl/latest/introduction/index.html#processing-handlers"
DCAT-AP is an EU cross-border project consisting in an application profile of DCAT for European data portals. See: https://joinup.ec.europa.eu/solution/dcat-application-profile-data-portals-europe/about
The specification was developed in 2001, by OASIS. It has been evolved over the years demonstrating that it overcame the possible issues raised on the developement and implementation. Moreover, the version of the issue being assessed is the 3.0, which enforces the maturity of the spec for its use in the developement of products and services. XACML OASIS reference: http://docs.oasis-open.org/xacml/3.0/errata01/xacml-3.0-core-spec-errata01.html
The purpose of the specifications is not related with the publication of Open Data. Therefore, this criterion is not applicable for this specification.
ADMS is publicly available for implementation and use for free on W3C's webpage. Therefore, it can be reused by the organisations, administrations, open communities, etc. that developed it. ADMS on Joinup: https://joinup.ec.europa.eu/solution/asset-description-metadata-schema-adms/about ADMS Specification W3C: https://www.w3.org/TR/vocab-adms/
All the IETF specifications are made available free of charge to the general public via the website. IETF drafts are published publicly discussions take place online in archived mailing lists. Moreover, the IETF Datatracker is the day-to-day front-end to the IETF database for people who work on IETF standards. It contains data about the documents, working groups, meetings, agendas, minutes, presentations, and more, of the IETF._x000D_ During the development of a specification, draft versions of the document are made available for informal review and comment by placing them in the IETF's Internet-Drafts directory. This makes an evolving working document readily available to a wide audience, facilitating the process of review and revision._x000D_ See:_x000D_ https://datatracker.ietf.org/_x000D_ http://www.ietf.org/id-info/
'Better Regulation Guidelines and Toolbox market acceptance lies in the European Public sector which has set it as the framework for the development, implementation and assessment of the impact derived from public policies and laws. Currently there some market acceptance as described on the European Parliamentary Research Service briefing regarding the Better Regulation Guidelines and Toolbox. The report does not describe a formal, public change management process for these documents -such as public consultations on modifications to the guidelines, public version control, or detailed release notes for external consumption. Instead, they are characterised as internal documents, with references to internal procedures that are not publicly available. Better Regulation Guidelines and Toolbox reference: https://commission.europa.eu/law/law-making-process/better-regulation/better-regulation-guidelines-and-toolbox_en European Parliamentary Research Service briefing https://www.europarl.europa.eu/RegData/etudes/BRIE/2022/699463/EPRS_BRI(2022)699463_EN.pdf'
'The specification explicitly addresses and enables data integrity with the implementation of digital signatures. A digital signature is data appended to, or a cryptographic transformation of a data unit that allows a recipient of the data unit to prove the source and integrity of the data unit and protect against forgery e.g. by the recipient. As a result, the value of a digital signature is the result of the cryptographic transformation of a data unit that allows a recipient of the data unit to prove the source and integrity of the data unit and protect against forgery. ETSI TS 119 432: https://www.etsi.org/deliver/etsi_ts/119400_119499/119432/01.02.01_60/ts_119432v010201p.pdf'
"The purpose of the specification is not directly related to the visibility of public administrations' procedures, rules, data or services. Publiccode.yml focuses on the reuse of software developed by public bodies, ensuring the efficiency and effectiveness of the budget dedicated to address specific needs. So, administrations can benefit from other administrations services with the implementation of the specification, however, it is not directly impacting visibility. Publiccode.yaml documentation: https://docs.italia.it/italia/developers-italia/publiccodeyml-en/en/master/index.html"
'OAS has a long history of developments and improvements. Starting in 2010 as the Swagger API, OAS quickly increased in popularity, and in 2015 acquired its actual name under the sponsorship of the Linux Foundation, and other funding members such as IBM, resulting in the most widely used tool for the creation and documentation of APIs. OAS specification: https://spec.openapis.org/oas/latest.html#openapi-specification OAS in Github: https://github.com/OAI/OpenAPI-Specification/#participation'
'ShEx has not been found to be included in any open repository or catalogue of standards at European level. ShEx primer document: https://shexspec.github.io/primer/ ShEx Community Group: https://www.w3.org/community/shex/ ShEx Github: https://github.com/shexSpec/spec/issues'
'NFVI releases do not foresee public reviews. However, the Testing, Experimentation and Open Source (TST) Working Group provides feature requests to open source projects and results of implementation experience to open source communities (see NFV participation requirements reference). Moreover, there is a wiki that openly provides release notes and draftings. TST NFV reference: https://portal.etsi.org/TB-SiteMap/NFV/NFV-WGs-amp-EGs-ToR NFV participation requirements: https://www.etsi.org/network-functions-virtualisation/get-involved-in-nfv ETSI NFVI wiki reference: https://nfvwiki.etsi.org/index.php?title=Main_Page'
"The ESPD also aligns with the European Interoperability Framework (EIF), which sets out principles and guidelines for promoting interoperability among European public administrations. The EIF includes a focus on ensuring the protection of personal data, as well as promoting transparency, accountability, and the respect for individuals' rights. ESPD data protection: https://op.europa.eu/en/web/espd-seminar-2020/privacy-statement ESPD business handbook: https://docs.ted.europa.eu/ESPD-EDM/latest/xml_business_handbook.html"
'The MIME-Based Secure Peer-to-Peer Business Data Interchange Using HTTP, Applicability Statement 2, RFC 4130 (AS2) has been found eligible as one of the most popular methods for transporting structured business data securely and reliably over the Internet by the Commission Implementing Decision (EU) 2017/1358. MIME specification: https://tools.ietf.org/html/rfc2045 MIME-Based Secure Peer-to-Peer Business Data Interchange Using HTTP, Applicability Statement 2, RFC 4130 (AS2): https://www.rfc-editor.org/rfc/rfc4130.html ICT Specifications for e-procurement: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32017D1358'
"HTTP Cookies enable web servers to store stateful information on the user's device or to track the user's browsing activity. They can also be used to save for subsequent use information that the user previously entered into form fields, such as names, addresses, passwords, and payment card numbers. Therefore, HTTP Cookies can facilitate data portability having a positive impact in interoperability. HTTP Cookies reference: https://datatracker.ietf.org/doc/html/rfc6265#section-5"
'The specification is developed by the European Commission, specifically by the DIGIT B.2. The development process is open, there is a team working on the action, but there are spaces and communities where users can participate providing feedback for the update and creation of new features. The evolution of the EIRA follows the semantic versioning approach x.y.z. EIRA reference: https://interoperable-europe.ec.europa.eu/collection/european-interoperability-reference-architecture-eira /solution/eira/release/610 EIRA Github Repository: https://github.com/CarTool-EC/EIRA'
'The specification itself does not encourage the creation of communities, but as a part of IETF, its community does encourage people to join and contribute develop specification sharing the data on European platforms. FTP Specification Reference: https://datatracker.ietf.org/doc/html/rfc959'
CAdES (ISO 14533-1:2014) is not included in any Member States' catalogues of recommended specifications. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'ETSI TS 119 511 maps its requirements according to relevant data protection regulations such as the Article 24.2 of Regulation (EU) No 910/2014, which state the requirements for qualified trust service providers, and outlines the specific security procedures such services need to apply. ETSI TS 119 511 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119511/01.01.01_60/ts_119511v010101p.pdf Regulation (EU) No 910/2014 of the European Parliament and of the Council of 23 July 2014 on electronic identification and trust services for electronic transactions in the internal market and repealing Directive 1999/93/EC https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv:OJ.L_.2014.257.01.0073.01.ENG'
EuroVoc is used for data processing acrosss Europe by the European Insitutions and also the National ones. Moreover, there is the possibility to search European Laws amongst other documents using its classification. It can be done through a EurLex, the European Gateway for regulation. Additionally, it is used in the EU Open Data Portal as a method for knowledge classification. In the EU Open Data Portal, datasets are related and linked to EuroVoc domains that improve the searchability and reuse of information. EU Open Data Portal example: https://data.europa.eu/euodp/es/data/dataset/building-stock-observatory Search by EuroVoc: https://eur-lex.europa.eu/browse/eurovoc.html?params=12,1216#arrow_1216 Publication Office of the European Union: https://op.europa.eu/en/home
'The TrainingDML-AI Standard primarily centers on crafting a UML model and encodings for geospatial machine learning training data. Its adoption can indirectly enhance the efficiency, effectiveness, and inclusivity of public service delivery. By offering a framework for the standardized utilization of geospatial training data, it supports the creation of AI/ML applications capable of revolutionizing the design and delivery of public services. OGC TrainingDML-AI Standard: https://docs.ogc.org/is/23-008r3/23-008r3.html'
The purpose of LegalRuleML is not related to long-term preservation of electronic records and other kinds of information. Therefore, this criterion is not applicable to this specification. LegalRuleML reference: http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/legalruleml-core-spec-v1.0.html
'Conforming to the UBL standard means that all business document types remain machine-readable and therefore enhances interoperability between systems, as the document transfer is done in a standardized way. UBL v2.3 reference: http://docs.oasis-open.org/ubl/os-UBL-2.3/UBL-2.3.html'
'We can state that OAS is related to the publication of open data given that it constitutes a tool that facilitates the development of RESTful conformant APIs. Since RESTful APIS can generate plugins that allow for the retrieval of resources in any given format, we can state that OAS facilitates the publication of open data. OAS specification: https://spec.openapis.org/oas/latest.html#openapi-specification Tim Berners-Lee in the 5-Stars approach: https://5stardata.info/en/'
'European Blockchain Services Infrastructure (EBSI) is the first pan-European, public-driven blockchain initiative of its kind and verifiable credentials and verifiable presentations play a major role within the EBSI ecosystem. EBSI VC/VP data models build upon the W3C Verifiable Credentials, which defines the standard way to present credentials/certificates on the internet in a common digital way. EBSI W3C Verifiable Credentials (VCs) and W3C Verifiable Presentations (VPs): https://ec.europa.eu/digital-building-blocks/wikis/pages/viewpage.action?pageId=555222155'
'Such means as ensuring the protection of personal data managed by Public Administrations can be provided as SOAP extensions using the SOAP extensibility mode. The SOAP Messaging Framework does not directly provide any mechanism for dealing with it directly. SOAP Reference, section 7 Security Considerations: https://www.w3.org/TR/soap12/#secconsiderations'
"The main purpose of HTTP Cookies is to track and store user's data on the webpage. Nonetheless, in some way, it contributes to the comprehensibility of administrative services by remembering client's information and therefore, providing a better operational website that can be adapted to the user's preferences. HTTP Cookies reference: https://developer.mozilla.org/en-US/docs/Web/HTTP/Cookies#creating_cookies"
'After checking the assessments performed by CAMSS, no assessment verifying the compliance of the specification with the European standardisation regulation (Regulation 1025/2012 on European Standardisation) has been found. Therefore HTTP Cookies is not a European Standard. ICT technical specifications: https://ec.europa.eu/growth/single-market/european-standards/ict-standardisation/ict-technical-specifications_en CENELEC and CEN search tool catalogue: https://standards.cencenelec.eu/dyn/www/f?p=CEN:105::RESET::::'
'The purpose of ISO 3166-1 is not related to secure process of data. Therefore, this criterion does not apply to this specification. ISO 3166-1 reference: https://www.iso.org/standard/72482.html'
TLS 1.2 is already associated to EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, TLS 1.2 can define the interoperability aspects of the "Network", "Networking Service", "Private Network" and "Public Network" ABBs of the EIRA Technical View. See: https://joinup.ec.europa.eu/solution/elis/distribution/eliscataloguev100betaxlsx
'SCIM is not a European Standard as it is not developed nor maintained by any European organisation nor initiative.'
'Contributions and improvements on the open-sorce community can be requested through the bitbucket and Github repository, where reviews of Domibus are held. Nonetheless, developers feedback is only visible with the prior registration on the eDelivery user community. eDelivery Developers community: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/eDelivery+Developers+Community+management Domibus specification: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/Domibus Domibus in Bitbucket: https://ec.europa.eu/digital-building-blocks/code/projects/EDELIVERY/repos/domibus/browse?at=9d8ec59fcdf'
The specification is included in eDelivery Service provided by CEF, which has the aim of providing a secure infrastructure and services for data exchanging. Additionally, eDelivery SMP 1.10 is based on the OASIS’s SMP 1.0 standard, which provides security features involving X509 encryption. Therefore, eDelivery SMP 1.10 eases the secure and trustworthy data exchange between different parties involved.
LegalDocML is available at OASIS's web page for everyone to study. LegalDocML reference: https://www.oasis-open.org/committees/legaldocml/charter.php
'ISO/IEC 7498:1 is designed to be language-agnostic and can be used in a multilingual context. The OSI model is well-suited for use in a multilingual context, as its conceptual framework is independent of language, and it has been employed internationally in the development of network communication standards. ISO/IEC 7498:1: https://www.iso.org/standard/20269.html'
'IEEE Std 802.3-2022 is platform-agnostic, meaning it can be implemented across various hardware and software platforms, ensuring broad compatibility and interoperability. It provides a common framework for a wide range of technologies and applications, independent of any specific vendor or proprietary solution. IEEE Std 802.3-2022 Reference: https://ieeexplore.ieee.org/document/9844436'
'There is no Member State that includes schema.org in their national catalogue with The National Interoperability Framework (NIF) in alignment with the three categories: 1. Conceptual model for integrated public services provision, 2. interoperability layers, and 3. interoperability principles. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
The application of the once-only principle in all EU Member States' public administrations aims at reducing the administrative burden. This Core Vocabulary fosters interoperability between public administrations, cross border services and impacts positively the development of eGovernment. CCCEV reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-criterion-and-core-evidence-vocabulary Joinup news page "CCCEV - a key enabler of the Once-Only Principle": https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/news/cccev-and-once-only-principle
'There are many documents that provide an overview of the usage and functionalities of MIME. Such is the case of a scholar paper whcih describes the efficiency of the mechanisms provided by MIME for Internet multimedia mail. MIME: a portable and robust multimedia format for Internet mail: https://link.springer.com/article/10.1007/BF01210505'
OpenPM2 is not included in any national catalogue of recommended specifications whose Member State NIF is fully aligned with at least 4 out of 5 sections of the EIF according to NIFO factsheets. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
5 Member States are recommending CAdES in their ICT National Catalogues. See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
Ogg can help comprehend the multimedia data of public administration by adding text as subtitles. In this sense, the specification can play an active role on the representation of the information in an easier visual way. This fact can consider Ogg to foster the comprehensibility of administrative rules and data. Ogg XIPH reference: https://xiph.org/ogg/doc/rfc3533.txt
'OpenTelemetry, while primarily designed for observability, can be comprehensively scoped to provide significant insights into administrative procedures. For instance, by instrumenting each step of an administrative procedure, OpenTelemetry captures detailed information about the execution flow, including the time taken at each step and any errors encountered. Furthermore, this helps in understanding how often rules are accessed, modified, and by whom. OpenTelemetry: https://opentelemetry.netlify.app/docs/specs/otel/'
'The purpose of REST is not related to the development of business processes. Therefore this criterion is not applicable. REST reference: https://restfulapi.net/'
'TLS 1.3 is specification-independent and can be implemented without dependencies on specific technologies or platforms. Moreover, the IETF, a vendor-neutral Standards Development Organisation, developed the technical specification independently of any vendor products. TLS 1.3 2018 Reference: https://www.rfc-editor.org/rfc/rfc8446.html'
The specification has been successfully implemented in multiple ways and with different approaches by several early adopters from the research services community: • The Helmholtz Centre Potsdam (GFZ) has prototyped it for use in GEOFON to manage large numbers of overlapping seismological datasets https://github.com/javiquinte/datacoll • The Perseids Project at Tufts University has used it to improve data sharing and annotation management http://collections.perseids.org/; https://github.com/RDACollectionsWG/perseids-manifold • The Max Planck Computing and Data Facility (MPCDF) has included it in a generic data repository software https://github.com/TomZastrow/reptor • The German Climate Computing Center (DKRZ) has used the recommendation to deploy an operative service that enables data users to create custom research data collections ("data carts") as part of the global Earth System Grid Federation (ESGF): https://esgf-data.dkrz.de/projects/esgf-dkrz/datacart_pid While these are service providers for specific scientific research communities, the early adoption prototypes demonstrate that, in principle, service provisioning based on the specification is feasible and not bound to particular usage domains.
CAMSS Assessment of CLV EIF Scenario v1.0.0
'In the DTD for Schemas Section there is a part for "Customisation entities" that can lead to think this specification allows customisation. XSD Reference: https://www.w3.org/TR/2012/REC-xmlschema11-1-20120405/'
The specification allows saving and exchanging content as images. However, the typology of PNG files are not the most used to exchange and reuse information across borders. At least not in the domain of eProcurement or the development of CEF Building Blocks in which the once-only principle is based. PNG W3C reference: https://www.w3.org/TR/PNG/ PNG ISO reference: https://www.iso.org/standard/29581.html
HTML5 can be used independently from other technical specifications, depite that it can be enhanced by mixing HTML5 along other specifications. For instance, CSS is a commonly used together with HTML5. See: https://www.w3.org/TR/2014/REC-html5-20141028/
After checking the different standard catalogues at the supra-national level, the Publications Office has listed it with all the specifications and resources produced and used for open data production, reuse and shareability. EUR-Lex: https://eur-lex.europa.eu/homepage.html ELI reference: https://eur-lex.europa.eu/eli-register/about.html EU Vocabularies Business Collection: https://op.europa.eu/en/web/eu-vocabularies/business-collections
'The TESTA network service – which stands for Trans European Services for Telematics between Administrations – provides a European backbone network for data exchange between a wide variety of public administrations. It is an ISA2 solution and which has been designed to support the needs for a whole range of application architectures relying on protocols such as HTTP or the secured version HTTPS. Trans European Services for Telematics between Administrations reference: https://ec.europa.eu/isa2/solutions/testa_en'
XHTML has some features to prevent possible security vulnerabilities. Moreover, by allowing to exchange data via online websites, XHTML fosters the secure and trustworthy data exchange between administrations and stakeholders. XHTML W3C reference: https://www.w3.org/TR/xhtml1/
CSV is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). Specifically, CSV can define the interoperability aspects of the "Representation" ABB of the EIRA Semantic View. See: https://joinup.ec.europa.eu/solution/elis/distribution/eliscataloguev100betaxlsx
'The purpose of ebXML is not related to e-accessibility. Therefore this criterion is considered not applicable to the specification. ebXML RegRep OASIS reference: https://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html'
As a format for the exchange of documents and files over the internet, it allows its implementation without hampering the scalability and the interoperability between systems. Also, it is a manner or means to allow the communication between administrations, business, and citizens. MIME reference: https://tools.ietf.org/html/rfc2045
'The E-ARK CSIP focuses on the organization and structure of digital information packages, the use of standard file formats, and the inclusion of descriptive metadata. These aspects are applicable to various domains and sectors that deal with digital records and archives, therefore it can be considered domain-agnostic. E-ARK CSIP specification: https://earkcsip.dilcis.eu/#introduction'
By allowing the data exchange between applications and systems talking different languages JSON fosters the data portability of European public services.
'The purpose of this specification is not related to provide means for restriction of access to information/data. Therefore, this criterion is not applicable to this specification. LDES specification: https://joinup.ec.europa.eu/collection/semic-support-centre/linked-data-event-streams-ldes'
By allowing public administration to consume and share information with others, it fosters the visibility of data (e.g. Administrative rules, processes etc.) and facilitates public administrations decision-making. The specification: http://docs.oasis-open.org/wsbpel/2.0/OS/wsbpel-v2.0-OS.html
'The purpose of Core Location Vocabulary is not related to e-accessibility. Therefore this criterion is considered not applicable to the specification. Core Location Vocabulary: https://interoperable-europe.ec.europa.eu/collection/semic-support-centre/solution/core-location-vocabulary/release/100'
UDDI includes features and capabilities to manage and maintain data integrity and access to UDDI repositories or nodes. This fact, helps to the secure and trustworthy data exchange between administration and stakeholders. See: http://www.uddi.org/pubs/uddi_v3.htm#_Toc85907992
'The specification is development for the evolution of interoperability. The development of XBRL GL comes with close relationships with European public services participants through collaboration in the development of OECD’s SAF-T and UN/CEFACT’s accounting and audit artefacts, as well as international collaboration through the ISO. https://docs.google.com/spreadsheets/d/1a1HJJJfwsLUbLvJzQ9hQ-ZGtiz2peyGt/edit?usp=sharing&ouid=117964998322026798794&rtpof=true&sd=true'
Several implementations and studies are assessing the usefulness and exploring how the usage of the specification can enhance the legal domain. This fact contributes to the market extension of the specification. A key point is also the incorporation to trans-European projects as LEOS or MIREL. Moreover, it has been included within the EU Observatory for ICT Standardisation and their catalogue of standards. EU Observatory for ICT Standardisation: https://www.standict.eu/standards-repository/working-group/oasis-legalruleml-tc
'ISO 3166-1 is included in 2 national catalogues of recommended specifications. They belong to Malta and the Netherlands. The National Interoperability Framework (NIF) of these Member States varies when aligned with the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. Whereas the Netherlands perfoms higher, Malta has a middle-lower performance compared to the European average. Some of the Maltese weaknesses relate to the three EIF categories, the need to improve the EIF Principles and the Conceptual Model scoreboards. In addition, there is data missing on the Inclusion and Accessibility and Preservation of Information on the EIF Principles. National catalogue Malta: https://mccaa.org.mt/Section/Content?contentId=1243 National catalogue The Netherlands: https://www.forumstandaardisatie.nl/open-standaarden/lijst NIFO factsheets: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public-administration-factsheets-2021'
EuroVoc is publicly available for its use and implementation. Moreover, it is available for everyone to study with no cost. EuroVoc reference: https://eur-lex.europa.eu/browse/eurovoc.html?locale=en
'IPv4 is the previous version of the Internet Protocol, but it is widely adopted and still prevailing. The newest has specific features and improves security aspects. Thus, it is not dependent of any specific platform and the adoption of IPv4 does not hamper the interoperability. IPv4 IETF: https://www.rfc-editor.org/rfc/rfc791'
Data on the web best practices is publicly available for implementation and use for free on W3C's webpage. Therefore, it can be reused by the organisations, administrations, open communities, etc. that developed it. W3C reference: https://www.w3.org/TR/dwbp/
After checking the assessments performed by CAMSS and the list of specifications identified by the MSP Multi-stakeholder-platform, no assessment verifying the compliance of the specification with the European standardisation regulation has been found._x000D_ _x000D_ ICT technical specifications:_x000D_ https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en
'The Advanced Encryption Standard, which defines the Advanced Encryption Standard (AES), significantly enables the secure exchange of data by providing a robust and widely trusted encryption algorithm. By converting data into an unreadable format without the appropriate key, AES ensures that transmitted information remains incomprehensible to any unauthorised person who might intercept it. Geeksforgeeks AES reference: https://www.geeksforgeeks.org/advanced-encryption-standard-aes/ AES Standard Reference: https://csrc.nist.gov/pubs/fips/197/final'
8 Member States are recommending CSV in their ICT National Catalogues. See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'NFVI fosters and simplifies ditigal services, but does not consistently offer any delivery channel. This specification contains some counterparts in terms of systems connectivity, basically brought by its discrete connectivity (i.e., services are separate from each other and not interconnectable with each other). NFVI Deliver, Infrastructure Overview section 7.3: https://www.etsi.org/deliver/etsi_gs/NFV-INF/001_099/001/01.01.01_60/ '
'The REST specification appears in the EIRA Library of Interoperable Specifications (ELIS) as a technical application associated to the machine to machine interface ABB, therefore it can be mapped to the EIRA. ELIS referenece: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/v110'
'The ebXML specification can be found in the e-CODEX system. In this system, the gateway is responsible for the basic exchange of communications. In this context, the ebXML and ebMS 3.0 specifications allow for the structuring of message headers, securing message exchange, and enabling global communication. Eur-lex ebXML reference: https://eur-lex.europa.eu/legal-content/ES/TXT/?uri=CELEX%3A32022D2519&qid=1743495780482 ebXML RegRep OASIS reference: https://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html'
'ETSI TS 119 432 can facilitate interoperability between organisations by providing a common framework for signature creation and verification. Standards such as XAdES (XML Advanced Electronic Signatures) and PAdES (PDF Advanced Electronic Signatures) define interoperable formats and procedures that enable signatures to be exchanged and verified across different systems and platforms. Furthermore, an open and accessible protocol encourages widespread adoption and interoperability by minimising barriers to entry for organizations wishing to implement digital signature capabilities. ETSI TS 119 432: https://www.etsi.org/deliver/etsi_ts/119400_119499/119432/01.02.01_60/ts_119432v010201p.pdf'
'The European Interoperability Reference Architecture (EIRA) is an architecture content metamodel defining the most salient architectural building blocks (ABBs) needed to build interoperable e-Government systems. Currently the specification is not included in any catalogue of a member state. CAMSS list of standards: https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and\x02specifications-camss/camss-list-standards'
'OpenTelemetry is an open source project that anyone in the community can use and improve. The community uses GitHub discussions for most communications. For those who are brand new to OpenTelemetry and want to chat or get redirected to the appropriate place for a specific question, they can join the CNCF OTel Slack channel. OpenTelemetry Community: https://opentelemetry.io/community/ OTel GitHub Discussions: https://github.com/open-telemetry/community/discussions CNCF OpenTelemetry Slack channel: https://opentelemetry.io/community/end-user/slack-channel/'
The purpose of RegOrg is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification. RegOrg Joinup reference: https://joinup.ec.europa.eu/solution/registered-organization-vocabulary
The rules on European standardisation allow the European Commission to identify information and communication technology (ICT) technical specifications - that are not national, European or international standards - to be eligible for referencing in public procurement. This allows public authorities to make use of the full range of specifications when buying IT hardware, software and services, allowing for more competition in the field and reducing the risk of lock-in to proprietary systems. After being evaluated compliant with the regulation on standardisation 1025/2012, TLS 1.2 has been identified by Commission Implementing Decision and included in the European list of ICT Standards for e-procurement. See: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en
"TLS-Anvil is a test suite for the evaluation of RFC compliance of Transport Layer Security (TLS) libraries using combinatorial testing (CT). It currently includes around 400 test cases that are based on requirements derived from various TLS-related RFCs listed on the TLS-Anvil Introduction page, as well as attacks from the past. The tests are implemented in Java using JUnit, coffee4j and TLS-Attacker and aim to detect violations of the TLS specification by servers or clients. Internet.nl is an initiative of the Dutch Internet Standards Platform that helps you to check whether your website, email and internet connection use modern and reliable Internet Standards. With the test tool Internet.nl users can easily check whether their internet is 'up to date' i.e. if their website, email and internet connection use modern internet standards. The tool provides detailed background information on the test results with how-to's and manuals. The test tool Internet.nl is an initiative of the Dutch Internet Standards Platform which is a collaboration of partners from the internet community and the Dutch government. The platform's mission is to jointly promote the use of modern internet standards keeping the internet reliable and accessible for everybody. Internet.nl web Reference: www.internet.nl Internet.nl Open source code Reference: https://github.com/internetstandards/Internet.nl TLS-Anvil Test Cases Introduction Reference: https://tls-anvil.com/docs/Introduction TLS-Anvil Github Reference: https://github.com/tls-attacker/TLS-Anvil?tab=readme-ov-file "
'The purpose of this Core Vocabulary is not related to ensuring the protection of personal data managed by Public Administrations. Therefore, this criterion is considered not applicable to this specification. Core Criterion and Core Evidence Vocabulary reference (v1.0.0): https://joinup.ec.europa.eu/release/core-criterion-and-core-evidence-vocabulary-v100 '
'All solutions developed in ISA² Programme are under ISA Open Metadata Licence which is perpetual, royalty-free and non-exclusive license to Use and re-Use the Works. ISA open metadata license: https://joinup.ec.europa.eu/licence/isa-open-metadata-licence-v11'
TIFF/IT does not define a cross-sector reusable data model, but defines a computer file format for storing raster graphics images. TIFF/IT ISO reference: https://www.iso.org/standard/34342.html
'As long as there exists a time-stamping client and a time-stamping server that meets the requirements defined in IETF RFC 3161, the specification will be platform agnostic. ETSI EN 319 422 reference: https://www.etsi.org/deliver/etsi_en/319400_319499/319422/01.01.01_60/en_319422v010101p.pdf'
'WSDL can support interoperability, achieving comprehensive data portability involves considerations beyond the technical aspects covered by WSDL. Additional factors, such as data standards, semantic interoperability, governance frameworks, and compliance with regulations, contribute to effective data portability in the context of European public services. Moreover, the adoption of standardized WSDL descriptions can contribute to data portability to some extent by promoting interoperability between systems and applications. W3C WSDL specification: https://www.w3.org/TR/wsdl20'
SOAP is defining a data model, which represents application-defined data structures and values as a directed edge-labelled graph of nodes. Therefore, as a sector agnostic specification, SOAP defines a cross-sector reusable data model. See: https://www.w3.org/TR/2007/REC-soap12-part2-20070427/#datamodel
'ODRL specification is not included in a formal open repository or catalog of standards at the European level, such as those maintained by organizations like CEN (European Committee for Standardization) or ETSI(European Telecommunications Standards Institute). ODRL is typically managed by the ODRL Initiative, which is a community-driven effort that supports the development and promotion of the ODRL standard. ODRL Community Group Home page: https://www.w3.org/community/odrl/'
"This specification is supported by ISO's Information technology commitee. In order to participate in creating standards, the user must be part of their national standards body (assuming their country is part of ISO). ISO Technical committees: https://www.iso.org/get-involved.html ISO Information technology commitee: https://www.iso.org/committee/45020.html"
'Secure processing of data generally involves additional security measures and technologies, such as encryption, access control and authentication. These security measures are implemented at the application level and are not part of the core MIME standard. MIME specification: https://tools.ietf.org/html/rfc2045 S/MIME specification: https://www.rfc-editor.org/rfc/rfc5751.html'
CSS v2.1 has been used to develop innovative solutions in the past, but with the new version CSS3, all web solutions that want to be developed with CSS use the latest version because it is more efficient and has more features. CSS v2.1 W3C reference: https://www.w3.org/TR/2011/REC-CSS2-20110607/ CSS Color Module Level 3 W3C reference: https://www.w3.org/TR/2018/REC-css-color-3-20180619/
"The specification is associated with EIRA ABB's in the EIRA Library of Interoperability Specifications (ELIS). More specifically, RDF is associated with the Legal Act Representation, the Open Data and the Representation ABB from the semantic view, and the Triplestore ABB from the techical view. ELIS link: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/v500"
'The Github platform hosts the OpenAPI guidelines and specifications, as well as a space for contributions and proposals of improvements in which any individual interested is encouraged to participate and raise issues regarding OAS implementation. OAS has also been found to be featured in the Central Digital and Data Office platform from the United Kingdom. In this platform, information about the use and implementation of OAS is shared and reviewed, OAS discussion forum in Github: https://github.com/OAI/OpenAPI-Specification/discussions Describing RESTful APIs with OpenAPI 3: https://www.gov.uk/government/publications/recommended-open-standards-for-government/describing-restful-apis-with-openapi-3 '
'The registration process to join and participate in the W3C Verifiable Credentials Working Group depends on whether the stakeholder works for a W3C Member organization or not. If their employer is not able to join W3C and the stakeholder considers they have the expertise and availability to participate, they may request to participate as an Invited Expert. W3C Verifiable Credentials Working Group: https://www.w3.org/groups/wg/vc/'
'TGF includes several principles and guidelines related to the secure exchange of data. It enphasises the importance of security, privacy and confidentiality in the development of digital solutions and services, promoting securty controls, use of cryptographic techniques, and the implementation of the service oriented architecture (SOA) security principles. TGF specification: http://docs.oasis-open.org/tgf/TGF/v2.0/cs01/TGF-v2.0-cs01.html SOA Specification: http://docs.oasis-open.org/soa-rm/soa-ra/v1.0/cs01/soa-ra-v1.0-cs01.pdf'
The Standard for Public Code is a set of criteria that supports public organizations in developing and maintaining software and policy together, so it can be said that Standard for Public code fosters the visibility of administrative rules, data, services and decision-making of a public administration. The Standard for Public Code webpage: https://standard.publiccode.net/
DCAT-AP is available for its implementation and use on Github and Joinup, the European Commission collaborative platform for the reuse of IT Solutions. See: https://joinup.ec.europa.eu/solution/dcat-application-profile-data-portals-europe/about https://github.com/SEMICeu/DCAT-AP
UDDI is not defining a data model per se, instead of providing a data model the specification provides an Information model with the features and constraints for using it. Each initiative or specific type of repository can map information from the informational model to build their own data model. See: uddi.org/pubs/uddi_v3.htm#_Toc85908471
After checking the different standard catalogues at supra-national level, there is no evidence of the inclusion of W3C Best Practices within any European catalogue of standards. ICT technical specifications: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en CEN search tool catalogue: https://standards.cen.eu/dyn/www/f?p=CENWEB:105::RESET:::: CENELEC search tool catalogue: https://www.cenelec.eu/dyn/www/f?p=104:107:0::::FSP_LANG_ID:25
'The purpose of TOSCA is not related to the secure processing of data. Therefore, this criterion is considered not applicable to this specification. TOSCA reference: https://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.3/os/TOSCA-Simple-Profile-YAML-v1.3-os.html'
'The Extensible Forms Description Language specification permits extensibility including custom items, options and external code functions. Extensible Forms Description Language reference: https://www.w3.org/TR/NOTE-XFDL'
'This specification is being directly used to create innovative solutions. For instance, it is included in AgroPortal, the homepage of ontologies and semantic artefacts in agri-food and related domains. In 2019, ETSI released a new SAREF ontology extension smart agriculture, thus why its involvement in AgroPortal. AgroPortal SAREF: https://agroportal.lirmm.fr/ontologies/SAREF'
The purpose of PAdES is not related to the publication of public data as open data. Therefore, this criterion is not applicable to this specification. PAdES ISO reference: https://www.iso.org/standard/67937.html PAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/102700_102799/10277801/01.01.01_60/ts_10277801v010101p.pdf
'The ETSI and any of its committees, in charge of the development of ETSI EN 319 422, operates under the ETSI Intellectual Property Rights (IPRs) and IPR Policy. The specification is licensed on a royalty-free basis. Intellectual Property Rights Policy, ETSI ownership of IPRs section: https://www.etsi.org/intellectual-property-rights'
'The purpose of SHACL is not related to the long-term preservation of data. Therefore this criterion is not applicable to this specification. SHACL W3C reference: https://www.w3.org/TR/shacl/'
'Since ShEx is a language for describing RDF graph structures, consequently, and according to the main principles of open data, it is a good enabler for the publishing of linked data, given that ShEx schemas are intended for use in validating instance data, communicating interface parameters and data structures, generating user interfaces, and transforming RDF graphs into other data formats and structures, therefore, it makes sure data is well structured to be published as open data. ShEx primer document: https://shexspec.github.io/primer/ ShEx Community Group: https://www.w3.org/community/shex/ ShEx Github: https://github.com/shexSpec/spec/issues Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/en/'
'EN 16234-1 e-CF does facilitate the modelling of business processes. The Digital Organisational Frameworks and IT Professionalism (DigiFrame) seeks to reach a mutual agreement on new coordinated procedures for reliable, effective and efficient measurement and forecasting of the demand and supply of high-tech skills at European and national level. IT Professionalism Europe (ITPE) reference, Reports & Publications section, Workshops on the Digiframe (2018) – Presentations subsection: https://itprofessionalism.org/app/uploads/2021/01/DIGIFRAME_workshop-4-morningafternoon_report_201811205_final.pdf '
'8 Member States are recommending MIME in their ICT National Catalogues. The Member states are Croatia, France, Germany, Greece, Malta, the Netherlands, Spain and Sweden. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards '
Not enough pieces of evidence have been found to answer positively or negatively to this criterion. It seems that OpenPM2 goal is not related to enabling e-accessibility for European Public Services. OpenPM2 specification reference: https://op.europa.eu/en/publication-detail/-/publication/ac3e118a-cb6e-11e8-9424-01aa75ed71a1/language-en/format-PDF/source-83307127
'TOSCA provides a metamodel facilitating the modelling of business processes. Apart from the Service Template, the specification describes the orchestration processes defining the process models that are used to manage a service throughout its lifetime. TOSCA reference, Glossary section: https://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.3/os/TOSCA-Simple-Profile-YAML-v1.3-os.html#_Toc26969419'
PAdES is a business domain agnostic specification that can be reused in a cross-domain way. It can apply to any type of transaction, between an individual and a company, between two companies, between an individual and a governmental body, etc. PAdES ISO reference: https://www.iso.org/standard/67937.html PAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/102700_102799/10277801/01.01.01_60/ts_10277801v010101p.pdf
After being evaluated compliant with the regulation on standardisation 1025/2012, CSV has been identified by Commission Implementing Decision and included in the European list of ICT Standards for e-procurement. See: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en
No formal agreement has been found established between organisations or administrations involved in European public service provision including the usage of SVG.
"ebXML facilitates organisational interoperability agreements, as one of the specification's objectives is to boost interoperability within organisations. In this sense, it is noteworthy that it allows for the creation of a standardised framework to share XML documents. Moreover, it also enables the creation of a Collaboration Protocol Agreement (CPA). ebXML RegRep OASIS reference: https://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html"
'SEMIC, the Semantic Interoperability Community, who is in charge of developing DCAT-AP, has a specific Change and Release Management Policy for DCAT-AP where they encourage any stakeholder to contribute to the development of the specification. DCAT-AP change and release management policy: https://joinup.ec.europa.eu/solution/dcat-application-profile-data-portals-europe/document/change-and-release-management-policy-dcat-ap DCAT-AP in Joinup: https://joinup.ec.europa.eu/solution/dcat-application-profile-data-portals-europe/about SEMIC DCAT-AP: https://github.com/SEMICeu/DCAT-AP '
At the time of elaborating this assessment, OWL current version (OWL2) is not included in any EIRA ABB in the current EIRA Library Of Interoperability Specifications (ELIS). However, the previous version of the specification can define the interoperability aspects of the "Core Data Model" ABB of the EIRA Semantic View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/solution/elis/release/v100
'DNS over HTTPS (DoH) is not inherently designed to facilitate organisational interoperability agreements. While DoH may not directly address organisational interoperability agreements, it can play a role in ensuring secure and private DNS communication between systems or entities that want to make an organisational interoperability agreements. RFC 8484: https://datatracker.ietf.org/doc/html/rfc8484'
"While this specification's scope is not explicitly directed towards visibility of administrative procedures, rules data, and services, the new specification can improve it by defining a simple way to send or request data, using a serialization format (JSON-LD) which is very familiar to many developers so that rapid adoption is facilitated. NGSI-LD supports a wide range of administrative and operational tasks through its API, covering the creation, querying, subscription and management of entities and their data. This includes advanced geo-temporal queries and subscription mechanisms that notify users of changes, enabling dynamic and responsive administrative processes. GS CIM 009: https://www.etsi.org/deliver/etsi_gs/CIM/001_099/009/01.07.01_60/gs_CIM009v010701p.pdf GS CIM 008: https://www.etsi.org/deliver/etsi_gr/CIM/001_099/008/01.02.01_60/gr_CIM008v010201p.pdf"
'The PROV family of documents can provide valuable context and provenance information that aids in understanding how interfaces are utilized and their interactions with data and services. Organizations can utilize PROV in conjunction with other techniques and standards to enhance the exposure and documentation of interfaces. For example, PROV-AQ describes data access mechanisms and query services for working with provenance records associated with web pages, resources or other deployments, Such as the Prov-Store, a public provenance repository that enables a URI provenance that can be queried. PROV Primer document: https://www.w3.org/TR/prov-primer/ PROV-AQ https://www.w3.org/TR/prov-aq/ ProvStore: https://eprints.soton.ac.uk/365509/2/poster-abstract.pdf '
The specification is included in the European collaborative platform for the development of ICT solution Joinup. See: https://joinup.ec.europa.eu/solution/universal-description-discovery-and-integration/distribution/uddi-specification
'The purpose of OAS is to help with the development and documentation of APIs, with any kind of restrictions related to the domain it is to be applied; therefore, OAS is domain-agnostic and can be used in any domain. OAS specification: https://spec.openapis.org/oas/latest.html#openapi-specification OAS in Github: https://github.com/OAI/OpenAPI-Specification/#participation'
PAdES (ISO 14533-3:2017) has the ISO community that supports the development of: International standards, Technical Specifications, Technical Report and Publicly Available Specification. The ISO standardization process: https://www.iso.org/stages-and-resources-for-standards-development.html
'According to this specification cloud computing is defined as a paradigm for enabling network access to a scalable and elastic pool of shareable physical or virtual resources with self-service provisioning and administration on-demand. Therefore, information is only provided once-only and reused as needed. ISO 19941: https://www.iso.org/obp/ui/en/#iso:std:iso-iec:19941:ed-1:v1:en'
'DQV provides customisation options that enable users to tailor the specification to their particular needs. Users can define their own quality dimensions, metrics, and indicators, or extend existing ones to accommodate domain-specific requirements. This flexibility allows for partial implementations where only the necessary components are implemented or customised according to the specific context. Data Quality Vocabulary: https://www.w3.org/TR/vocab-dqv/'
There are several existing mechanisms to assess JSON conformity. Different types of validators depending on users’ needs. See: https://github.com/nst/JSONTestSuite https://jsoncompare.com/#!/simple/ https://jsonformatter.curiousconcept.com/
Kendo UI survey of more than 4000 developers showed the following resulting that justify the fostering of HTML5 toward innovative solution: 63% indicate that they are actively developing with HTML5. See: https://www.w3.org/2012/12/html5-cr.html.en
'There are existing validation tools for UTF-8. UTF-8 validator in Github: https://github.com/digital-preservation/utf8-validator'
A public review is part of the decision-making process defined by the change and release management policy. See: Europe/document/change-and-release-management-policy-dcat-ap https://joinup.ec.europa.eu/solution/dcat-application-profile-data-portals-europe/about
'HTTPS enables authenticity features through server authentication using digital certificates issued by trusted certificate authorities. This ensures that the client is communicating with the legitimate server and not an imposter, providing confidence in the authenticity of the connection. HTTPS specification: https://tools.ietf.org/html/rfc2818'
The purpose of JSON is not related to organisational interoperability. Therefore, this criterion is not applicable to the specification.
'The DPV working group was created as an outcome of the W3C Workshop on Data Privacy Controls and Vocabularies in Vienna in 2017, and started on 25th May 2018 – the date of the enforcement of GDPR. Since then, the DPVCG has worked to fulfil its aims and objectives, and produced the Data Privacy Vocabulary (DPV) as a deliverable. '
'The specification addresses data integrity by providing identity and access management in International Data Spaces, ensuring that the right users (that are part of the ecosystem connected to or within an enterprise) have the appropriate access to technology resources. DAPS: https://github.com/International-Data-Spaces-Association/IDS-G/tree/main/Components/IdentityProvider/DAPS'
ADMS is included in the national catalogue of Slovakia. The National Interoperability Framework (NIF) of this Member State is fully aligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. Slovakia’s Catalogue: http://www.informatizacia.sk/standardy-is-vs/596s NIFO factsheets: https://joinup.ec.europa.eu/collection/national-interoperability-framework-observatory-nifo/nifo-factsheets
'TS 119 614-1 is a testing conformance suite that can be applied in any domain and context where the exchange of documents is required. Therefore, the specification is usable beyond any business-specific domain and ensures its implementation across business domains. ETSI TS 119 614-1 reference: https://www.etsi.org/deliver/etsi_ts/119600_119699/11961401/01.01.01_60/ts_11961401v010101p.pdf'
Better Regulation Toolbox fosters the secure and trustworthy data exchange between citizens, businesses and public administrations by proposing methods to ensure that ICT systems and solutions developed under the scope of public services include security regarding data exchanged between parties interested. Providing this checklist method helps the development of public policies that guarantee secure and trustworthy data exchange. Betterr Regulation Toolbox reference: https://ec.europa.eu/info/sites/info/files/better-regulation-toolbox_2.pdf
'The purpose of OSI is not related to the reuse of information. Therefore, this criterion is not applicable to the specification. OSI reference https://www.iso.org/standard/20269.html'
'The purpose of IPsec is not related to the exposure of interfaces. Therefore this criterion is not applicable to this specification. IPSec reference: https://www.rfc-editor.org/rfc/rfc6071.html'
'The purpose of BFO is not related to access control. Therefore, this criterion is not applicable to the specification. BFO reference: https://www.iso.org/standard/74572.html'
OASIS has defined a clear process where all the stakeholders involved have the opportunity to participate in the development of the specification development process. Moreover, there is a public review in the TC process. OASIS guideline: https://www.oasis-open.org/policies-guidelines/tc-process-2017-05-26
'The Extensible Forms Description Language (XFDL) specification has its origins in the Universal Forms Description Language (UFDL) specification. This initial specification was developed from 1993 to 1998 by the UWI.com organisation. In this context, the XFDL specification is the result of creating an XML syntax for the UFDL, thereby enabling the expression of powerful, complex forms in a syntax that promotes application interoperability and adherence to global Internet standards. In addition, there is a discontinued GitHub repository for the XFDL specification, where some information about the specification, such as its main page, can be found. However, there are still some niche software applications that continue using this specification for creating digital signatures or complex, legally binding forms with high precision. Discontinued Github page for XFDL: https://w3c.github.io/Unitas/?s=XFDL&v=19980902 Extensible Forms Description Language reference: https://www.w3.org/TR/NOTE-XFDL'
'The purpose of ISO 639-2 is not related to reduce administrative burden. The specification is intended to serve as a code to identify a language name. Therefore, this criterion is considered not applicable to this specification. ISO 369-2 FAQs: https://www.loc.gov/standards/iso639-2/faq.html#7'
'There are 3 Member States recommending ISO 639-2 in their ICT National Catalogues. These Member States are Ireland, Norway and Spain. National catalogue Ireland: https://data.gov.ie/pages/opendatatechnicalframework#recommended-standards-for-open-data National catalogue Norway, forth drop-down tap: https://www.digdir.no/digitale-felleslosninger/nettlesarbaserte-tenester/1491 National catalogue Spain: https://administracionelectronica.gob.es/pae_Home/pae_Estrategias/pae_Interoperabilidad_Inicio/pae_Normas_tecnicas_de_interoperabilidad.html#CATALOGOESTANDARES'
The fact that the specification has been widely adopted and the strong interest by different organisations and initiatives demonstrates that the specification has sufficient completeness and consistency for the use and development of products and services required to gather or exchange wheat-related data.
FTP has been widely used for the exchange of data in the past years and has been supported for long time by most of the web browsers. However FTP is beginning to be considered obsolete by major browser. For instance Google Chrome, a browser having market dominance over the market deprecated the support for FTP and states that ¨Usage of FTP in the browser is sufficiently low that it is no longer viable to invest in improving the existing FTP client¨. See: https://www.chromestatus.com/feature/6246151319715840
CAdES has been included within the European Public Service “Digital Signature Service” (hereby DDS). The initiative includes three main features: the digital signature, the extension a digital signature, and the validation. Moreover, it is worth to note that DSS initiative included in the Connecting Europe Facility Programme context which aims to fund projects and initiatives for enhancing European public services. See: https://ec.europa.eu/cefdigital/DSS/webapp-demo/doc/dss-documentation.html https://ec.europa.eu/inea/connecting-europe-facility/cef-telecom
The purpose of LDAP is not related to the availability of interfaces with internal information systems. Therefore, this criterion is not applicable to this specification. LDAP IETF reference: https://tools.ietf.org/html/rfc4511
'The TGF provides guidance on access control and recommends the use of security mechanisms such as authentication, authorization, and encryption to ensure access control. The specification also includes guidelines for managing access to information and services based on roles and permissions, as well as best practices for securing communication channels and data storage. TGF specification: http://docs.oasis-open.org/tgf/TGF/v2.0/cs01/TGF-v2.0-cs01.html'
'At the time of elaborating this assessment, this specification is included in the current EIRA Library Of Interoperability Specifications (ELIS). It is also included in the "Data Space" and "Data Space Connector" ABB, specifically the Technical Application layer. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /solution/elis/release/600 '
'SCIM allows for customization through the use of extensions. While the core SCIM specification defines a set of standard features for identity management, it also provides a framework for extending these capabilities to meet specific customization requirements. SCIM: https://scim.cloud/'
'When serializing JavaScript objects into JSON, properties with a value of undefined are omitted from the resulting JSON string. This flexibility enables working with JSON data that may not contain all the expected fields or may vary in structure, thus allowing for partial implementations. JSON specification: https://www.ecma-international.org/wp-content/uploads/ECMA-404_2nd_edition_december_2017.pdf'
'The purpose of RDF is not related to confidentiality, therefore, this criterion is not applicable to the specification. RDF primer document: https://www.w3.org/TR/rdf11-primer/'
'NFVI works on a hierarchical-interface basis. According to the NFVI documentation, hierarchical interfaces relates to peer level interfaces (e.g., transport interfaces, signalling interfaces, and routing protocol interfaces). However, this specification does not apply to client-server interfaces because it works on a peer-to-peer basis (that is, from server to server). As a consequence, the client interfaces may be re-built to conform to the NFVI container interface specification. NFVI Deliver, Infrastructure Overview section 6.5.1: https://www.etsi.org/deliver/etsi_gs/NFV-INF/001_099/001/01.01.01_60/'
'The OASIS Technical Committee, in charge of the development of OData, operates under RF (royalty-free) on RAND Mode of the OASIS IPR Policy. Therefore, the specification is licensed on a Royalty-free basis. OASIS Intellectual Property guidelines, section 5.2: https://www.oasis-open.org/policies-guidelines/ipr/ UBL Intellectual Property Rights policy: https://docs.oasis-open.org/ubl/os-UBL-2.3/UBL-2.3.html#S-IPR-POLICY'
'By adopting the E-ARK CSIP, organizations can choose the technology and systems that best suit their specific requirements, as long as they adhere to the specified standards and guidelines outlined by the specification. E-ARK CSIP specification: https://earkcsip.dilcis.eu/#introduction'
'At the time of elaborating this assessment, this specification is included in the "Technical Agreement" and "Technical Interoperability Agreement" ABBs in the current EIRA Library Of Interoperability Specifications (ELIS), specifically the "Technical-Infrastructure View" layer. It is also included in the "Data Space", "Data Space Connector", "Data Space Connector Consumer" and "Data Space Connector Provider" ABBs, which are in the "Technical-Application View" layer. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /solution/elis/release/600'
"There are assessment evaluating the specification's effectiveness, such as the LEOS tool, which uses AKN4EU proving that the specification can be effective. LEOS Tool Reference: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/solution/eif-toolbox/solution-leos-software-components-under-eupl"
'The purpose of GITB TDL is not related to the delivery of multilingual public services. Therefore, this criterion is not applicable to this specification. GITB TDL reference: https://www.itb.ec.europa.eu/docs/tdl/latest/introduction/index.html#what-is-the-gitb-tdl'
'Applications implemented based on OpenAPI interface files can automatically generate documentation of methods, parameters and models. This helps keep the documentation, client libraries, and source code in sync, thus, enabling data portability between systems. OAS specification: https://spec.openapis.org/oas/latest.html#openapi-specification OAS in Github: https://github.com/OAI/OpenAPI-Specification/#participation'
'WAI-ARIA is mentioned and referenced in the CNECT Rolling Plan as a Accessibility of ICT products and services. Rolling Plan 2023 , section Accessibility of ICT products and services: https://joinup.ec.europa.eu/collection/rolling-plan-ict-standardisation/accessibility-ict-products-and-services-rp2023'
The adoption of ODF as a document format for exchanging information does not hamper the scalability of systems. ODF ISO reference: https://www.iso.org/standard/66363.html ODF OASIS reference: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office
"W3C Data Quality Vocabulary's first public working draft was published in 2015. Since then, three major releases have been published and several minor changes have been recommended. In addition, different documentation on its supporting processes has been published to ensure the correct change and release of its content. For instance, section B of the specification explains changes made since the last published version. Therefore, this specification has been evolved enough and mechanisms for its development have been put in place. Change History DQV: https://www.w3.org/TR/vocab-dqv/#change-history W3C Recommendation Track: https://www.w3.org/2021/Process-20211102/#rec-track General Requirements for Technical Reports: https://www.w3.org/2021/Process-20211102/#recs-and-notes"
'The Advanced Encryption Standard does not allow the customisation of its core components when is implemented. AES Standard Reference: https://csrc.nist.gov/pubs/fips/197/final'
'The specification counts with a specific section (5.1.4) that is about Language Support, so it can be determined that is designed to fully support multilingualism. ETSI TS 119 612: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf'
'The purpose of WAI-ARIA is not related to the secure of data exchange. Therefore, this criterion is not applicable to this specification. WAI-ARIA reference: https://www.w3.org/TR/wai-aria-1.2/'
The purpose of CSS is to give format to web documents, including layout, colours and fonts. A well-formatted web document helps the public administration to make the information more comprehensible. Without a CSS, the information could be confusing and it could take longer to see the meaning of the information. An example of this is EUR-Lex, the cross border gateway to EU Law. It is using CSS to present the different documentation contained in EUR-Lex. Presentation style sheets EU Vocabulary: https://op.europa.eu/en/web/eu-vocabularies/presentation-style-sheets EUR-Lex: https://eur-lex.europa.eu/homepage.html?locale=en
The specification is widely adopted amongst others like SMTP for the exchange of data over the internet. It allows sharing several file formats, which makes the specification highly reusable. The specification has been implemented and it is supported by numerous mail software as Mailchimp amongst others, demonstrating the market acceptance of MIME. MIME reference: https://tools.ietf.org/html/rfc2045
'The purpose of ISO 3166-1 is not related to the protection of personal data. Therefore, this criterion is not applicable to this specification. ISO 3166-1 reference: https://www.iso.org/standard/72482.html '
'The purpose of CSV is not related to security and privacy of the data exchange. Therefore, this criterion is not applicable to the specification. CSV reference: https://datatracker.ietf.org/doc/html/rfc4180'
SHACL is built around RDF and is highly dependent from it since its purpose is to validate RDF graphs. However, note that RDF is a European standard since 2014 and the common data format for Semantic web.
Internet Protocol Security (IPsec), a protocol providing a network layer security (authentication and encryption), is an optional feature that allows the Internet Protocol to secure the data exchange. However, in the latest version of the protocol (IPv6), the feature has been included as mandatory enhancing security settings. See: https://tools.ietf.org/html/rfc791 https://tools.ietf.org/html/rfc1349 https://tools.ietf.org/html/rfc2474 https://tools.ietf.org/html/rfc6864 https://tools.ietf.org/html/rfc2460
'IPv4 is widely adopted as a key protocol for making data, information, and resources available on the internet. However, it is worth noting that the newer version, IPv6, is being gradually adopted and incorporates several innovative solutions. Despite this, IPv4 is still in use and continues to be adopted in many countries, such as the Netherlands, where it plays a crucial role in terms of security and privacy. National catalogue of Netherlands: https://www.forumstandaardisatie.nl/open-standaarden/lijst IPv6 specification: https://www.rfc-editor.org/rfc/rfc2460 IPv4 to IPv6 transition: https://www.geeksforgeeks.org/transition-from-ipv4-to-ipv6-address/'
'By allowing the authentication for using services SAML 2.0 can contribute and promote the comprehensibly of administrations by simplifying access to administrations’ services. Moreover, it can be used internally by public officers which enhances the decision-making process, but it is not its main purpose. SAML 2.0 Reference: http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-tech-overview-2.0.html'
'Each test performed by the specification has a tag EUMS (European Union Member State) that varies depending on the Member State or not Member State using the specification, so although not explicitly recommended, there are Member States that use it. This is supporting eIDAS implementations especifically for validating the requirements from ETSI TS 119 614-1 V1.1.1. ETSI TS 119 614-1 reference: https://www.etsi.org/deliver/etsi_ts/119600_119699/11961401/01.01.01_60/ts_11961401v010101p.pdf'
'PROV-XML has been found included in the Joinup repository, which is a European platform for sharing IT solutions and specifications. PROV Primer document: https://www.w3.org/TR/prov-primer/ PROV-XML in Joinup: https://joinup.ec.europa.eu/collection/w3c-standards-and-technical-reports/solution/prov-xml-prov-xml-schema/about'
TIFF/IT is used to send data for print-ready pages. This fact allows administrations to share digital content among others and with the stakeholders. Although it is an image format excellent for printing, it is also used to store images and to avoid paper images, which reduces the administrative burden. TIFF/IT ISO reference: https://www.iso.org/standard/34342.html
'The purpose of ISAE 3402 is not related to the enabling of data portability between systems or applications. Therefore this criterion is not applicable to this specification. ISAE 3402 handbook reference: https://www.ifac.org/system/files/downloads/b014-2010-iaasb-handbook-isae-3402.pdf'
'The IPsec specification is a set of rules used to establish secure network connections. In this context, the specification offers various mechanisms to ensure data protection, including those related to tunneling and confidentiality. Therefore, public administrations can use some of these mechanisms to safeguard personal data. IPSec reference: https://www.rfc-editor.org/rfc/rfc6071.html IPsec security reference: https://www.geeksforgeeks.org/ip-security-ipsec/'
'The Registered Organization Vocabulary is no longer maintained by W3C; however, all its releases and related information can still be found on the W3C Working Group page. Development and community have since shifted towards the Core Business Vocabulary. Registered Organization Vocabulary reference: https://www.w3.org/TR/vocab-regorg/ Core Business Vocabulary Github reference: https://github.com/SEMICeu/Core-Business-Vocabulary/tree/master Core Business Vocabulary Github Issue 51 - RegOrg maintenance reference: https://github.com/SEMICeu/Core-Business-Vocabulary/issues/51 '
'There are different documentation and information that takes into account EuroVoc as part of the narrative and includes it as valuable. An article shows the efficiency of EuroVoc since it is included as the core of an application for the categorisation of documents: JRC EuroVoc Indexer JEX - A freely available multi-label categorisation tool: https://www.researchgate.net/publication/256846257_JRC_EuroVoc_Indexer_JEX_- _A_freely_available_multi-label_categorisation_tool'
The purpose of CLV is not related to the availability of interfaces with internal information systems. Therefore, this criterion is not applicable to this specification. CLV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-location-vocabulary
'The purpose of XML is not related to organisational interoperability. Therefore, this criterion is not applicable to the specification.'
"The specification is included in 13 Member States' catalogues of recommended specifications. Some examples of Member States including RDF on their catalogues are the Netherlands, Slovenia, Spain or Sweden. CAMSS list of standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards"
"According to the CEN-CENELEX Guide 8, all patents, including EN 16234-1 e-CF, are licensed on a royalty-free basis. However, the specification should be purchased from each of the national standardisation organisations' sales points. CEN-CENELEC Guide 8 reference, section 4.1: https://www.cencenelec.eu/media/Guides/CEN-CLC/cenclcguide8.pdf National standardisation organisations reference: https://standards.cencenelec.eu/dyn/www/f?p=205:35:0::::FSP_SURR_WI:67073&cs=1D6A0AE3F4B33063EC3BB54B719082165"
'As it is stated in the "implementation and specification document" the The goal of domain names is to provide a mechanism for naming resources in such a way that the names are usable in different hosts, networks, protocol families, internets, and administrative organizations. Therefore, by allowing the association of information with domain names, DNS facilitates their comprehension of data and services in a network. DNS IETF reference: https://tools.ietf.org/html/1034 Domain Names - Implementation and Specification: https://tools.ietf.org/html/1035 '
'SAREF is designed to facilitate the publication of data on the web, particularly in the context of the Internet of Things (IoT). SAREF provides a standardised way to represent the semantics of information related to smart appliances and devices. This standardisation promotes interoperability and facilitates the sharing and publication of data on the web in a consistent and understandable manner. SAREF Technical Specification: https://www.etsi.org/deliver/etsi_ts/103200_103299/103264/03.01.01_60/ts_103264v030101p.pdf'
"During the public review, the draft is shared with the public, allowing stakeholders and any interested party to provide feedback and suggest improvements. This process helps identify issues and gather diverse perspectives, ensuring the standard meets user and industry needs. The feedback can lead to revisions, enhancing the final standard's quality and relevance. Participating in IEEE SA Public Review (Commenters): https://standards-support.ieee.org/hc/en-us/sections/5747263044116-Participating-in-IEEE-SA-Public-Review-Commenters"
'The purpose of this Core Vocabulary is not related to security and privacy of the data exchange. Therefore, this criterion is not applicable to this specification. CPSV-AP Joinup webpage: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/core-public-service-vocabulary-application-profile/release/22'
'The specification admits multiple extension elements in the TSL Testing such as Scheme Extension elements, Information Extension elements, Service Information Extension elements, Extension Type instances, etc. ETSI TS 119 614-1 page 5 reference: https://www.etsi.org/deliver/etsi_ts/119600_119699/11961401/01.01.01_60/ts_11961401v010101p.pdf'
'ETSI TS 119 614-1 can be found on the specifications and standards repository of its own standards development organization, the European Telecommunication Standards Institute (ETSI). ETSI Standards Repository Search: https://www.etsi.org/standards#page=1&search=ETSI%20TS%20119%20614- 1&title=1&etsiNumber=1&content=1&version=0&onApproval=1&published=1&historical=1&startDate=1988- 01-15&endDate=2022-07- 25&harmonized=0&keyword=&TB=&stdType=&frequency=&mandate=&collection=&sort=1'
'The specification is not included in any initiative at European or National level covering privacy aspects. Therefore, this criterion is not applicable to the specification.'
'XACML is included in 2 national catalogues of recommended specifications. They belong to Cyprus and Germany. The National Interoperability Framework (NIF) of Cyprus and Germany is fully aligned with at least 3 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards National Interoperability Framework Observatory: https://joinup.ec.europa.eu/collection/national-interoperability-framework-observatory-nifo/nifo-factsheets National Catalogue of Cyprus: https://dits.dmrid.gov.cy/dmrid/dits/dits.nsf/all/B83AA8E4EB4EFD19C225855800288B10/$file/Cyprus% 20eGovernment%20Interoperability%20Framework_new%20EIF_v2.0-To%20Publish.pdf National Catalogue of Germany: https://www.cio.bund.de/Webs/CIO/DE/digitaler-wandel/architekturen-und-standards/architekturen-und\x02standards-node.html'
'The main purpose of this Core Vocabulary is to support the exchange of information between organisations that define criteria and organisations that respond to these criteria using evidences. So, it facilitates the visibility of administrative rules. Core Criterion and Core Evidence Vocabulary reference (v1.0.0): https://joinup.ec.europa.eu/release/core-criterion-and-core-evidence-vocabulary-v100 '
'The specification encourages the creation of communities by providing a common framework for the development of interoperable public services and the sharing of data and results across communities and platforms. AKN4EU reference: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/akn4eu'
'WAI-ARIA specification itself does not explicitly address multilingual considerations. However, the accessibility principles promoted by WAI-ARIA can be applied in a multilingual context to enhance the user experience for individuals who use assistive technologies and may interact with content in different languages. Therefore, this criterion is not applicable to this specification. WAI-ARIA reference: https://www.w3.org/TR/wai-aria-1.2/ WAI-ARIA roles guide: https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Roles'
'The specification does dwell in data portability between systems/applications or supporting the implementation/evolution of European public services since it is designed to support the interchange of information among heterogeneous information systems. BFO reference: https://www.iso.org/standard/74572.html'
'The OpenTelemetry GitHub is where all major and minor releases foresee a public review during which collected feedback is publicly visible. The repository has two public sections dedicated to issues and pull requests, which means that any user can see the whole release lifecycle of the specification and participate in it. OpenTelemetry GitHub: https://github.com/open-telemetry/opentelemetry-collector'
The specification is not included per se in any supra-national catalogue. Despite this, SOAP 1.2 is part of the Electronic Signatures and Infrastructures (ESI); Rationalized framework of Standards for Electronic Registered Delivery Services Applying Electronic Signatures, which is an ETSI Special Report. See: https://www.etsi.org/deliver/etsi_sr/019000_019099/019050/01.01.01_60/sr_019050v010101p.pdf
'OAS is recommended by The Netherlands and Malta. National Catalogue of The Netherlands: https://www.forumstandaardisatie.nl/open-standaarden National Catalogue of Malta: https://mccaa.org.mt/Section/Content?contentId=1243'
'The purpose of the specification is not related to supporting the evolution of European public services, therefore it does not promote or hinder it. ETSI TS 119 614-1 reference: https://www.etsi.org/deliver/etsi_ts/119600_119699/11961401/01.01.01_60/ts_11961401v010101p.pdf'
'In the specification documentation, there is no reference to the possibility of customisation, so it is asumed that it is not possible. CSV reference: https://datatracker.ietf.org/doc/html/rfc4180'
"RDF is compliant with one of the maximum levels of maturity provided by Tim Berners Lee’s 5 stars schema for open data. Moreover, RDF is highly aligned with the principles for Linked Data promoted by W3C and Tim Berners Lee. In fact, RDF is one of the proposed standards for the publication of Linked Open Data. The specification is compliant with Tim Berners Lee's principles for the Linked Data and, as well, is highly aligned with the different levels of maturity of Tim Berners Lee's 5 stars schema for open data. In fact, RDF is one of the proposed standards for the publication of Linked Data. W3C Linked data design issues: https://www.w3.org/DesignIssues/LinkedData.html Tim berners-Lee 5 star linked open data: https://5stardata.info/en/ https://www.w3.org/TR/ld-bp/ Best Practices for Publishing Linked Data"
The specification is independent of any software, hardware, or operating system. So it can be said that WS-BPEL is independent of any specific technology or platform. The specification: http://docs.oasis-open.org/wsbpel/2.0/OS/wsbpel-v2.0-OS.html
'BFO is not yet used in European institutions but BFO contributes to improve interoperability and portability of data. BFO reference: https://www.iso.org/standard/74572.html'
'OData allows for including custom transformations (query options) that the user explicitly requests, which are not necessary defined in the OData specification. However, these extensions are restrictive or limited to a specific functionality. OData reference on extensibility: https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#_Toc31358848'
'The specification can facilitate the modelling of business processes by helping standardize and agree to the form which the information is described. Standardising the evidence modelling may help in the cross-border participation by eliminating language barriers between European countries. Core Criterion and Core Evidence Vocabulary reference (v1.0.0): https://joinup.ec.europa.eu/release/core-criterion-and-core-evidence-vocabulary-v100 '
The rules on European standardisation allow the European Commission to identify information and communication technology (ICT) technical specifications - that are not national, European or international standards - to be eligible for referencing in public procurement. This allows public authorities to make use of the full range of specifications when buying IT hardware, software and services, allowing for more competition in the field and reducing the risk of lock-in to proprietary systems. After being evaluated compliant with the regulation on standardisation 1025/2012, FTP has been identified by Commission Implementing Decision and included in the European list of ICT Standards for e-procurement. See: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en
UDDI registries or nodes depend on WSDL to complete the data exchange transaction and provide the requester with information. Additionally, UDDI relies on SOAP to enable the service invoke by the requester.
IETF has a defined set of processes for the modification and revocation of standards. _x000D_ _x000D_ See:_x000D_ https://www.ietf.org/standards/process/ _x000D_ https://tools.ietf.org/html/rfc2026
The purpose of XSD 1.1 is not related to business processes modelling. Therefore this criterion is considered not applicable to this specification.
'UBL appears in Joinup as one of the identiefied ICT specifications for e-procurement. Joinup distribution of UBL: https://joinup.ec.europa.eu/collection/ict-standards-procurement/identified-ict-specifications-procurement'
CSS is a simple mechanism for adding style (fonts, colours, spacing...) to web documents, but by itself, it does not publish data on the web. Also, it does not comply with the other levels of maturity presented by Tim Berners-Lee's 5 stars for open data. CSS v2.1 W3C reference: https://www.w3.org/TR/2011/REC-CSS2-20110607/ Five star open data: https://5stardata.info/en/
As a key enabler for the data exchange and interchange between administrations and stakeholders, JSON enhances the communication and information exchange across borders between public administrations. Therefore, the adoption of the specification avoids citizens and businesses to provide information in several times.
DNS is available on JoinUp as a reusable solution. See: https://joinup.ec.europa.eu/solution/dns-rfc-1034-rfc-1035-domain-name-system/about
'The specification has been implemented several times and in different environments, such as in public administrations. An example of XACML implementation is Semiramis, which aims to provide e-services with the required underlying secure authentication and management approach. XACML OASIS reference: https://docs.oasis-open.org/xacml/3.0/xacml-3.0-core-spec-os-en.html'
'UTF-8 is included in 10 national catalogues of recommended specifications, among which we can find the Netherlands and Sweden, whose National Interoperability Framework (NIF) is fully aligned with at least 2 out of 3 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. CAMSS List of standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards NIFO Factsheets https://joinup.ec.europa.eu/collection/national-interoperability-framework-observatory-nifo/nifo-factsheets '
SMTP allows the connection between email servers providing the digitization of public administration communications and reduces the non-digital communication flows. So it reduces the administrative burden. SMTP IETF reference: https://tools.ietf.org/html/rfc5321
'The XFDL specification does not directly address personal data protection. However, it provides a mechanism to secure personal data through the signature item. This feature includes a digital signature that verifies the authenticity of the form and encrypts the signed data using a hash algorithm specified in the form’s signformat option. By ensuring the integrity and authenticity of the data, XFDL helps protect personal data in public administration processes, particularly in ensuring that signed information remains tamper-proof. XFDL privacy reference: https://www.w3.org/TR/NOTE-XFDL#button'
By securing data exchange through computer networks, TLS 1.2 allows the information exchange between administrations and its stakeholders. Thus, the adoption of TLS 1.2 avoids the analogical data exchange reducing the administrative burden.
XAdES Baseline Profile is built over XML and its constraints. Even though, as XML is an open standard widely used the implementation of the specification does not hamper the interoperability of systems. See: https://www.etsi.org/deliver/etsi_ts/103100_103199/103171/02.01.01_60/ts_103171v020101p.pdf
'DQV is a vocabulary for expressing data quality and according to the W3C Data on the Web Best Practices Working Group, it t is foreseen as an extension to the DCAT vocabulary [vocab-dcat] to cover the quality of the data, how frequently is it updated, whether it accepts user corrections, persistence commitments etc. Therefore, this specification incorportes open standards as it reuses an already existing RDF vocabulary. Data Quality Vocabulary: https://www.w3.org/TR/vocab-dqv/'
'eTwinning is a community for schools, an online space for teachers and school staff to collaborate and develop national and international projects. In this project, data in transit, management access and data transfers on platforms is secured and encrypted via TLS. eTwinning. European School Education Platform Reference: https://school-education.ec.europa.eu/en/etwinning eTwinning Privacy Aspects TLS Reference: https://school-education.ec.europa.eu/en/etwinning_privacy_policy?prefLang=es TLS 1.3 Reference: https://www.rfc-editor.org/rfc/rfc8446.html'
'According to the EIRA Library of Interoperability Specifications (ELIS), Verifiable Credentials is included in the "Distributed Blockchain Network" ABB from the Technical Infrastructure view and the "Privacy" ABB from the technical Application view. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /solution/elis/release/600'
XSLT is included in 7 national catalogues. They belong to Member States which comply with at least 4 out of 5 sections of the EIF according to the NIFO factsheets. See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
There are no disclosures of ISO IPR Database to identify the licensing under the specification. ISO 14533-2:2012 is not listed in ISO/IEC/ITU Common Patent policy, so it cannot be confirmed that the specification is licensed on a (F)RAND basis. ISO patents: https://www.iso.org/iso-standards-and-patents.html ISO standards and patents IPR database: http://isotc.iso.org/livelink/livelink/13622347/Patents_database.xls?func=doc.Fetch&nodeId=13622347
'The purpose of DCAT-AP it to support the implementation of European Public Services by enhancing the searchability and discoverability of datasets across borders. DCAT-AP is an interoperability enabler. DCAT-AP - a key for European data publishers to reach the data consumers and create a European open data ecosystem: https://ec.europa.eu/isa2/dcat-ap-key-european-data-publishers-reach-data-consumers-and-create-european-open-data-ecosystem_en DCAT-AP Specification: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/dcat-application-profile-data-portals-europe/release/200'
'Syslog plays a specific role in IT and network management. While syslog itself is not directly designed for the delivery of public services, it can contribute to the overall efficiency, security, and reliability of IT systems, which may, in turn, impact European public services delivery. Syslog Protocol: https://datatracker.ietf.org/doc/html/rfc5424'
'ODRL is designed with flexibility and extensibility in mind, allowing users to create, share, and reuse digital rights expressions efficiently. The specification provides mechanisms to support a modular and interoperable approach to expressing digital rights, which facilitates the reuse of relevant information in diverse contexts. W3C ODRL Community: https://github.com/w3c/odrl W3C specification reference: https://www.w3.org/TR/odrl-vocab/#vocab-core'
OWL2 as an extension of RDF, defines a common language to express information that can be exchanged between applications without losing meaning. OWL 2 is designed to facilitate ontology development and sharing via the Web. So it fosters trustworthy data exchange between administrations and stakeholders. OWL2 W3C reference: https://www.w3.org/TR/owl2-overview/
'The implementation of ISAE 3402 could, for example, allow administrations to properly track how the different organisations providing digital public services are distributing funds. Or also to ensure that the procedures and transactions with stakeholders are properly mapped. ISAE 3402 auditing tool, therefore, is designed to be imlemented in any domain. ISAE 3402 handbook reference: https://www.ifac.org/system/files/downloads/b014-2010-iaasb-handbook-isae-3402.pdf'
'The purpose of the ESPD is not related to the secure exchange of data. Therefore, this criterion is not applicable to the specification. ESPD business handbook: https://docs.ted.europa.eu/ESPD-EDM/latest/xml_business_handbook.html'
'This specification refers to the W3C Verifiable Credentials Data Model so, it is inherently abstract and can be implemented and/or used in any domain as long as it fulfills the requirements. Therefore, its use goes beyond a specific business domain. Verifiable Credentials: https://www.w3.org/TR/vc-data-model/'
W3C Best Practices fosters the secure and trustworthy data exchange between citizens, businesses and public administrations by using standards that are specific to the publishing of datasets related to particular domains & applications, involving communities of users interested in that data. W3C Reference: https://www.w3.org/TR/dwbp/
'ELI is a public asset developed by a European Institution with the participation of interested parties like the Member States. To foster the implementation across public administrations it can be accessed for free without any payment restrictions. Therefore, it can be considered that the specification is licensed under royalty-free basis and (F)RAND basis. ELI reference: https://eur-lex.europa.eu/eli-register/about.html'
There is no Member State that includes XAdES (ISO 14533-2:2012) in their national catalogue with The National Interoperability Framework (NIF) aligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
The CPSV-AP allows describing public services in a standardised human and machine-readable format. This fact fosters the discoverability of the datasets containing information about public services. Therefore, it enhances its reuse and visibility. CPSV-AP Joinup webpage: https://joinup.ec.europa.eu/solution/core-public-service-vocabulary-application-profile/release/22 Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/en/ On using the core public sector vocabulary (CPSV) to publish a "citizen's guide" as linked data: https://www.researchgate.net/publication/325495548_On_using_the_core_public_sector_vocabulary_CPSV_to_publish_a_citizen's_guide_as_linked_data
'The ISO 639-2 code suite was developed to be used by libraries, information services and publishers to indicate language in the exchange of information, especially in computerised systems. The specification may contribute to the promotion of administration services by easing the automatic translation of the website content from one official European language to another (by using a the EU Official Language codelist) when using a European public service interface or solution, such as eForms. ISO 369-2 FAQs: https://www.loc.gov/standards/iso639-2/faq.html#5 eForms reference: https://docs.ted.europa.eu/eforms/0.5.0/translations/index.html eForms Language reference: https://docs.ted.europa.eu/eforms/0.5.0/codelists/index.html#_tailored_codelists'
HTTP is a sector agnostic specification.
'LDES is a European Standard as it was developed and recognized by the European standards organisations; it is also maintained by the EU community. LDES specification: https://joinup.ec.europa.eu/collection/semic-support-centre/linked-data-event-streams-ldes'
'The OSI specification specifically mentions that there is conformance definitions and provisions. The conformance test is done via the ISO/IEC 9646, which is a multi-part International Standard that specifies a general methodology for testing the conformance of products to OSI specifications. OSI conformance https://www.iso.org/standard/17473.html?browse=ics OSI reference https://www.iso.org/standard/20269.html'
CAMSS Assessment of CCCEV EIF Scenario v1.0.0
'On September 9th, 2024, eIDAS adopted TLS 1.3 as a required protocol within its framework. The eIDAS Regulation, is a key European Union regulation aimed at ensuring secure and seamless digital interactions across member states. It establishes standards for electronic identification and trust services, enabling businesses, citizens, and public authorities to carry out secure cross-border transactions. By adopting TLS 1.3, eIDAS reinforces its commitment to the protection of digital communications. eIDAS Regulation Reference: https://digital-strategy.ec.europa.eu/en/policies/eidas-regulation eIDAS eID Profile Reference: https://ec.europa.eu/digital-building-blocks/sites/display/DIGITAL/eIDAS+eID+Profile eIDAS eID Profile Cryptographic Reference: https://ec.europa.eu/digital-building-blocks/sites/download/attachments/467109280/eIDAS%20Cryptographic%20Requirement%20v.1.4.1_final.pdf?version=2&modificationDate=1729176493701&api=v2'
The purpose of ADMS is not related to organisational interoperability. Therefore, this criterion is not applicable to the specification. ADMS Specification W3C: https://www.w3.org/TR/vocab-adms/
'As can be seen on the Oracle documentation about ebXML MCD implementation, the ebXML specification can work with some components that can be customised. For example, Message Control Documents (MCD), which serve as an interface between a back-end system and WebLogic Integration - Business Connect for processing business messages. In this sense, when using MCD, some elements are optional to implement. However, the core elements of the specification cannot be customised. ebXML MCD implementation: https://docs.oracle.com/cd/E13215_01/wlibc/docs81/admin/xml_protocols.html#1032357 ebXML RegRep OASIS reference: https://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html'
'Although MIME itself does not foresee secure exchange of data mechanisms, its security extension (S/MIME) can enable it through a combination of encryption, digital signatures, authentication and data integrity checks. MIME specification: https://tools.ietf.org/html/rfc2045 S/MIME specification: https://www.rfc-editor.org/rfc/rfc5751.html '
'TGF is an OASIS standard, therefore it is not considered to be European. TGF Specification: http://docs.oasis-open.org/tgf/TGF/v2.0/cs01/TGF-v2.0-cs01.html'
'UDDI does not help the availability of interfaces with internal information. In fact, the purpose of the specification is not related to this action. Despite this, UDDI supports the availability of technical interfaces that may be used to access web services, given that it specifies the methods and protocols through which the services can be accessed and used, making it easier for developers and other systems to integrate with public administration services. UDDI techtarget reference: https://www.techtarget.com/whatis/definition/UDDI-Universal-Description-Discovery-and-Integration UDDI OASIS reference: https://www.oasis-open.org/committees/uddi-spec/doc/spec/v3/uddi-v3.0.2-20041019.htm#_Toc85907967'
'The OAIS reference model does provide a framework for organizing and managing digital information in a way that can support a wide range of administrative procedures, rules, and services. By defining a set of functions and interfaces that are necessary for the long-term preservation and access of digital objects, the OAIS reference model provides a foundation for the development of systems and services that can be used to manage and provide access to digital information in a wide range of contexts. OAIS specification: https://public.ccsds.org/Pubs/650x0m2.pdf'
The purpose of OpenPM2 seems not to be related to long term preservation of electronic records. Moreover, no information has been found to answer positively or negatively to this criterion. OpenPM2 specification reference: https://op.europa.eu/en/publication-detail/-/publication/ac3e118a-cb6e-11e8-9424-01aa75ed71a1/language-en/format-PDF/source-83307127
UDDI is developed and maintained by OASIS, which is an International Organisation developing Standards. After finishing UDDI's last version (v3, which is being assessed) the Technical Committee was closed. See: https://www.oasis-open.org/committees/uddi-spec/doc/spec/v3/uddi-v3.0.2-20041019.htm#_Toc85907967
'OData follows REST principles and there exists some kind of privacy mechanisms. However, the purpose of OData is not related to the security and privacy of the data exchange. For this OData relies on the conformity of the user to implement RFC 7231 (HTTP secure transfer). RFC 7231 reference: https://datatracker.ietf.org/doc/html/rfc7231 Odata reference: https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#_Toc3135883'
'ISAE 3402 is focused on ensuring risk management regarding the security of information, therefore, this criterion does not apply due to the scope of the specification. ISAE 3402 handbook reference: https://www.ifac.org/system/files/downloads/b014-2010-iaasb-handbook-isae-3402.pdf'
TLS 1.3 provides secure internet connections, with the aim of secure data exchange between internet systems (such as websites or mail servers). The Enterprise Transport Security (ETS) technical specification from ETSI also works in that area, but does not cover the same level of security, it does not have the exact same application area.
'OAS development is guided by the Techincal Steering Commitee (TSC) a group of committers in charge of implementing new versions of the specification. Moreover, the OAS has support from the community in Github, where anyone interested is encouraged to pull requests and give feedback on its implementation. OAS Github: participation https://github.com/OAI/OpenAPI-Specification/'
'The purpose of BFO is not related to privacy and as such is not included in any initiative both National and European level. Therefore, this criterion is not applicable to the specification. BFO reference: https://www.iso.org/standard/74572.html'
'6 Member States are recommending IPv4 in their ICT National Catalogues. This Member States are Croatia, France, Germany, Netherlands, Norway and Sweden. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards'
'ETSI TS 119 511 along with the whole Electronics Signature Infrastructure (ESI) family of specifications, has been proven effective for the Preservation of Evidence of Cryptographically Signed Documents (TR-ESOR), a document from the German Federal Office of Information Security that specifies security-related requirements for the long-term preservation of evidence of cryptographically signed electronic documents and data along with associated electronic administrative data (metadata). TR-ESOR Preservation of Evidence of Cryptographically Signed Document: https://www.bsi.bund.de/SharedDocs/Downloads/EN/BSI/Publications/TechGuidelines/TR03125/TR-03125_B_v1_2_2.pdf?__blob=publicationFile&v=1 ETSI TS 119 511 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119511/01.01.01_60/ts_119511v010101p.pdf '
'The DPV is based on the legislative requirements of the European Union, such as the GDPR, which aims to harmonise data privacy laws across Europe. Therefore, the DPV promotes the comprehensibility of administrative procedures by providing a clear vocabulary that defines all levels at which personal data will be processed. DPV specification: https://w3c.github.io/dpv/primer/ GDPR reference: https://gdpr.eu/'
'This Core Vocabulary is included in the Center for transfer of technology (CTT), in the Spanish ICT National Catalogue. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards Spanish National Catalogue: https://administracionelectronica.gob.es/ctt/CTTprincipalEs.htm?idioma=en&urlMagnolia=/pae_Home/en/pae_SolucionesCTT.html#.ZC1eDXvP02w'
The purpose of CSS v2.1 is not related with data portability. Therefore, this criterion is not applicable for this specification. CSS v2.1 W3C reference: https://www.w3.org/TR/2011/REC-CSS2-20110607/
'TGF promotes the use of secure and resilient infrastructures to ensure that data processing is performed in a secure and reliable manner, as well as the implementation of appropiate security controls to ensure authentication and access-control methods. TGF specification: http://docs.oasis-open.org/tgf/TGF/v2.0/cs01/TGF-v2.0-cs01.html'
'The ETSI TS 119 512 specification outlines protocols for trust service providers that offer long-term data preservation services for digital signatures and other types of data. Using digital signatures and time-stamps tokens, is guaranteed that data has not been changed since it was signed. Moreover, it is possible to establish access control mechanisms to access data. Therefore, data is secure and protected against unwanted changes. ETSI TS 119 512: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.01_60/ts_119512v010101p.pdf'
'After checking the different standard catalogues at supra-national level, there is no evidence of ISO 639-2 as a European standard. ICT technical specifications: https://ec.europa.eu/growth/single-market/european-standards/ict-standardisation/ict-technical-specifications_en CENELEC and CEN search tool catalogue: https://standards.cencenelec.eu/dyn/www/f?p=CEN:105::RESET::::'
"The Extensible Forms Description Language (XFDL) specification is based on XML, which allows for efficient storage and reuse of information. While the XFDL specification itself is not specifically designed for the long-term preservation of data, it can contribute to this goal through XML's inherent capabilities, such as data reuse. XML reuse of information reference: https://www.geeksforgeeks.org/dtd-entities/ Extensible Forms Description Language reference: https://www.w3.org/TR/NOTE-XFDL"
'The ESPD has support from several communities and stakeholders involved in public procurement processes, which suggests that it is a widely accepted and trusted document for use in public procurement. Moreover, Github hosts the most active community of contributors to the improvement and development of the specification. ESPD Business handbook: https://docs.ted.europa.eu/ESPD-EDM/latest/xml_business_handbook.html ESPD in Github: https://github.com/OP-TED/ESPD-EDM'
CAdES is business agnostic and in consequence, its Baseline Profile can be considered business agnostic as well. CAdEs Baseline profile is an extension to provide interoperability when AdES signatures need to be interchanged across borders in the context of the EU internal market. Thus, it can be used in any business domain requiring interoperability features along with eSignature.
'LDAP is not related to the publication of open data, therefore this criterion is not applicable to the specification. LDAP v3.0 https://datatracker.ietf.org/doc/html/rfc4511 '
'Internet Protocol Security (IPsec), a protocol providing network layer security (authentication and encryption), is an optional feature that allows the Internet Protocol to secure data exchange. However, in the latest version of the protocol (IPv6), this feature has been made mandatory, enhancing security settings. IPsec protocol: https://www.cloudflare.com/learning/network-layer/what-is-ipsec/ IPv4 IETF: https://www.rfc-editor.org/rfc/rfc791 IPv6 specification: https://www.rfc-https://www.rfc-editor.org/rfc/rfc2460'
The purpose of MIME is to allow the exchange of documents between systems and applications. MIME reference: https://tools.ietf.org/html/rfc2045
'CSV makes sure content is available on the web, structures data and makes it usable in a non-proprietary open format. Consequently, CSV fosters data portability as the specification makes files available for any system. CSV reference: https://datatracker.ietf.org/doc/html/rfc4180'
'The purpose of XACML is not related to data portability. Therefore, this criterion is not applicable to this specification. XACML OASIS reference: https://docs.oasis-open.org/xacml/3.0/xacml-3.0-core-spec-os-en.html'
'The purpose of NUTS is not related to data portability. Therefore, this criterion is not applicable to this specification. EUROSTAT reference, History of NUTS section: https://ec.europa.eu/eurostat/web/nuts/history'
'The European Legislation Identifier (ELI) is a system designed to make legislation available online in a standardized format, so that it can be accessed, exchanged, and reused across borders. ELI is based on a voluntary agreement between the EU countries and includes technical specifications on web identifiers (URIs) for legal information, metadata specifying how to describe legal information, and a specific language for exchanging legislation in machine-readable formats. Moreover, the ELI is used by the EU Open Data Portal to describe datasets from Member States that have already implemented the specification. This facilitates the publication of public data as open data, promoting transparency and interoperability among information systems. ELI reference: https://eur-lex.europa.eu/eli-register/about.html EU Open Data portal Examples: https://data.europa.eu/euodp/en/data/group/eli?groups=eli'
'ETSI TS 119 512 provides a framework for access control primarily in the context of electronic signatures and trust services. It defines mechanisms to ensure that only authorised entities can access certain resources or perform specific actions. ETSI TS 119 512: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.01_60/ts_119512v010101p.pdf'
'After searching in different catalogues and repositories, there is no evidence found of ETSI TS 119 614-1 being included in the catalogue of any Member State or the List of Standards. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards'
'IEEE Std 802.3-2022 provides the infrastructure for data transmission, media access control, and network performance optimization, supporting digital service delivery channels. IEEE Std 802.3-2022 Reference: https://ieeexplore.ieee.org/document/9844436'
'ISO 3166-1 can enable the exposure of interfaces if combined with other specifications, notably those specifications inherent to the interface of a given public service. For example, the specification prompts the display of data associated to the country or territory where a user is submitting an ESPD (European Single Procurement Document) form. ISO 3166-1 reference: https://www.iso.org/standard/72482.html ESPD reference, Legal framework and context section: https://docs.ted.europa.eu/ESPD-EDM/3.0.1/xml_business_handbook.html#_i_1_1_legal_framework_and_context'
'For the ISO 639-2 maintenance, there is the Library of Congress Registration Authority (ISO 639-2/RA). This community supports the development of this specification and attends language code change requests. ISO 639-2/RA reference: https://www.loc.gov/standards/iso639-2/'
eDelivery SMP has diverse implications in terms of Intellectual Property Rights. On one hand, the SMP 1.0 specification which is under non-assertion IPR policy, from OASIS IPR Policy. On the other hand, the ministry of Justice and the European Commission are in charge of part of the specification content. The specification is licensed under (F) RAND basis and Royalty-free basis. See: https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery+SMP+-+1.10#eDeliverySMP-1.10-Ownership https://www.oasis-open.org/policies-guidelines/ipr
"SHACL enables the definition of custom functions that can be utilised within constraints. This capability is particularly useful for performing complex calculations or validations that are not achievable with the built-in SHACL functions. For instance, to ensure that a person's age is greater than 18, a custom function can be defined to create a constraint that checks the person's birthdate and calculates their age. SHACL Custom reference: https://shacl.dev/article/advanced_SHACL_features_you_need_to_know.html SHACL W3C reference: https://www.w3.org/TR/shacl/"
CSS does not define a cross-sector reusable data model. Instead, it defines a set of conventions and rules to provide style to web documents. CSS v2.1 W3C reference: https://www.w3.org/TR/2011/REC-CSS2-20110607/
The Core Public Organisation Vocabulary facilitates information sharing between governments, businesses, and citizens. The CPOV allows managing a cross-border repository of public services and organisations. So, it fosters data portability between systems and applications supporting the implementation and evolution of European public services. CPOV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-organisation-vocabulary
'Core Criterion and Core Evidence Vocabulary has been used to develop some European projects, for example, ESPD-EDM (European Single Procurement Document - Exchange Data Model) which is the technical representation of the legal European Single Procurement Document. It is used to support interoperability between ESPD services provided all over Europe. ESPD documentation: https://docs.peppol.eu/pracc/espd/edm/ Core Criterion and Core Evidence Vocabulary reference (v1.0.0): https://joinup.ec.europa.eu/release/core-criterion-and-core-evidence-vocabulary-v100 '
'The purpose of SAREF is not related to guaranteeing the authenticity and authentication of roles agents involved in the data transactions. Therefore, this criterion is not applicable to this specification. SAREF: https://saref.etsi.org/core/v3.1.1/ '
'SMP is maintained by OASIS which is an international community developing open standards. SMP OASIS reference: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505009'
"NFVI is not included in any Member States' catalogues of recommended specifications. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards"
'The purpose of Domibus is not related to the long-erm preservation of information. Therefore, this criterion is not applicable to the specification. Domibus specification: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/Domibus'
'There are no Member States recommending SAREF in their ICT National Catalogues. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards '
'The purpose of OData is not related to the delivery of multilingual public services. Therefore, this criterion is not applicable to this specification. OData reference: http://docs.oasis-open.org/odata/odata/v4.0/odata-v4.0-part1-protocol.htm'
'While iCalendar can include some limited administrative information in event descriptions and custom properties, it is not a comprehensive solution for managing administrative procedures, rules data, and services. Its primary purpose remains as a format for representing and exchanging calendar-related data, and organizations may need to integrate iCalendar with other dedicated systems to address their administrative needs comprehensively. iCalendar specification: https://www.rfc-editor.org/rfc/rfc5545'
FTP is publicly available for study and use at no cost on the IETF webpage. See: https://tools.ietf.org/html/rfc959
'HTTPS itself is not technology-agnostic. It is a specific implementation of the HTTP protocol that adds security features through the use of SSL/TLS encryption. HTTPS relies on the SSL/TLS protocols to establish secure connections and encrypt data transmission. TLS specification: https://www.rfc-editor.org/rfc/rfc8446 HTTPS specification: https://datatracker.ietf.org/doc/html/rfc2818'
The Registered Organization Vocabulary is a simplified, reusable and extensible data model that captures the fundamental characteristics of a legal entity. RegOrg Joinup reference: https://joinup.ec.europa.eu/solution/registered-organization-vocabulary
'The main purpose of the ISO/IEC 27001 is to preserve the confidentiality, integrity and availability of information by applying a risk management process and to give confidence to interested parties that risks are adequately managed. Following the requirements set by ISO/IEC 27001 secures data portability between systems, and its scalable approach supports the evolution of european public services. ISO 27001 reference: https://www.iso.org/obp/ui/#iso:std:iso-iec:27001:ed-2:v1:en'
DCAT is a cross-sector and cross-border reusable vocabulary. In contexts where there are sector-specific or national requirements, the specification is extended (e.g. DCAT-AP-BE, DCAT-AP, StatDCAT-AP) See: https://www.w3.org/TR/vocab-dcat-2/#introduction
'The purpose of DNS is not related to the publication of open data. Therefore this criterion is not applicable to this specification. DNS IETF reference: https://datatracker.ietf.org/doc/html/rfc8499'
'DCMI does not include a definition of conformance. Nevertheless, the Dublin Core Application Profiles may include documentation on constrains meaning that implementors can elaborate their own conformance test. DCMI About: https://www.dublincore.org/about/ DCMI Application Profile Review: https://www.dublincore.org/specifications/dublin-core/application-profile-review/'
'ISO/IEC 7498:1 was initially released in 1984 and its second and current version was released in 1996. The specification goes under review every 5 years. Therefore, this version remains current. While all stages of the life cycle of the specification are public, its details are not. ISO/IEC 7498:1: https://www.iso.org/standard/20269.html'
'Based on the information available on the CEN website, the scope of the specification does not explicitly mention the modeling of business processes. CEN reference: https://www.cen.eu/Pages/default.aspx AKN4EU reference: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/akn4eu'
'Effective data management practices, as encouraged by ISO/IEC 19944-1, can contribute to an improved visibility of administrative procedures, rules, data, and services within cloud computing environments. By categorizing and organizing data according to the provided classification scheme, organisations can enhance the visibility and accessibility of their data assets, including administrative procedures and rules. Additionally, ISO/IEC 19944-1 promotes effective governance and management of cloud services, which can indirectly contribute to the visibility of services within cloud computing environments. By adopting the recommended practices outlined in the specification, organisations can establish clearer governance structures, define service management processes, and ensure the appropriate visibility of services. ISO/IEC 19944-1 specification: https://www.iso.org/standard/60545.html'
Data on the Web Best Practices gives some advice on how to publish data on the web. However, it does not make data available on the Web, or it does not make data available as structured data. So, this specification does not support any level of maturity of Tim Berners-Lee 5-star schema for Open Data. Data on the Web Best Practices W3C: https://www.w3.org/TR/dwbp/ Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/en/
'The specification does not allow any customisation to be made. See: https://www.w3.org/TR/2006/REC-xml11-20060816/ '
'As ETSI EN 319 422 was released in 2015, it has more than 2 years of maturity and can be proof that demonstrates it has overcome possible difficulties. ETSI EN 319 422 reference: https://www.etsi.org/deliver/etsi_en/319400_319499/319422/01.01.01_60/en_319422v010101p.pdf eIDAS Regulation reference: https://digital-strategy.ec.europa.eu/en/policies/eidas-regulation Reference of Implementation of trusted services: https://www.sede.fnmt.gob.es/documents/10445900/10536309/dpc_unidades_sellado_tiempo_english.pdf'
The purpose of CSS v2.1 is not related to long term preservation of electronic records. Therefore, this criterion is considered not applicable to this specification. CSS v2.1 W3C reference: https://www.w3.org/TR/2011/REC-CSS2-20110607/
The rules on European standardisation allow the European Commission to identify information and communication technology (ICT) technical specifications - that are not national, European or international standards - to be eligible for referencing in public procurement. This allows public authorities to make use of the full range of specifications when buying IT hardware, software and services, allowing for more competition in the field and reducing the risk of lock-in to proprietary systems. After being evaluated compliant with the regulation on standardisation 1025/2012, MIME has been identified by Commission Implementing Decision. ICT Standards for Procurement: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en
'XBRL is used in many MS in external reporting to government, but XBRL GL taxonomy not yet included. However there has been developments to use the specification in Estonia and among the Nordic Countries. These are under development. It is also worth mentioning the specification is used in Turkey. Estonia: https://itl.ee/en/news/data-driven-reporting-is-the-next-step-in-real-time-economy-sector/ Turkey (https://www.edefter.gov.tr/edeftermevzuat.html) '
The SMP specification defines a set of data structures (a data model) that can be followed for proper implementation of the specification that can be used across-sector. SMP OASIS reference: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505009
The OASIS Technical Committee, in charge of the development of XACML, operates under RF on RAND Mode of the OASIS IPR Policy. The specification is licensed on a Royalty-free and (F)RAND basis. OASIS IPR: https://www.oasis-open.org/committees/security/ipr.php https://www.oasis-open.org/policies-guidelines/ipr
The DCAT vocabulary supports the attribution of data and metadata to various participants such as resource creators, publishers and other parties. In addition, it also supports the association of rights and licenses with catalogued Resources and Distributions. Such metadata improves the reliability of data exchanged between citizens, businesses and public administrations.
'There are various implementations where AMQP is utilised. For example, AMQP 1.0 is used with Azure Service Bus, which includes creating connections, sessions, and links, and transferring messages to and from Service Bus entities such as queues, topics, and subscriptions. Another application of AMQP is in Red Hat AMQ, which is based on open-source communities like Apache ActiveMQ and Apache Kafka. This flexible messaging platform reliably delivers information, enabling real-time integration and connecting the Internet of Things (IoT). Red Hat Enterprise MRG: https://docs.redhat.com/es/documentation/Red_Hat_Enterprise_MRG/3/html/messaging_programming_reference/index#idm140626033708592 Microsoft Azure Messaging services : https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-amqp-protocol-guide OASIS AMQP Reference: http://docs.oasis-open.org/amqp/core/v1.0/amqp-core-complete-v1.0.pdf'
'The Open Data Protocol (OData) supports the creation of data services based on REST, which allow resources to be published and edited by web clients via HTTP messages. OData could allow a third-party information system to act on behalf of citizens who cannot, permanently or temporarily, make direct use of public services. In this sense, it can contribute to e-accessiblity. OData reference, 1 Introduction: https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html'
'The specification OSI can be implemented in many fields and business domains. It is a fully domain agnostic specification since its a reference model to facilitate the interconnection between open systems and being vendor neutral. OSI reference https://www.iso.org/standard/20269.html'
'While the ESPD itself does not enable the visibility of administrative procedures, rules, data, and services, its use in conjunction with digital solutions can help to increase transparency and visibility in public procurement processes, such as the e-certis tool, which helps contracting authorities to verify the certificates and documentation submitted by suppliers in response to tender opportunities. e-certis and ESPD: https://single-market-economy.ec.europa.eu/single-market/public-procurement/digital-procurement/europeansingle- procurement-document-and-ecertis_en ESPD Business handbook: https://docs.ted.europa.eu/ESPD-EDM/latest/xml_business_handbook.html'
'ebXML is part of several initiatives and projects at European level. The specification is included in The Once-Only Principle project (TOOP) and in different publi procurement initiatives (see Decision 2016/1765 reference). TOOP project reference: https://toop.eu/info Decision (EU) 2016/1765 reference: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32016D1765'
The purpose of WS-BPEL is not related to e-accessibility. Therefore, this criterion is not applicable to the specification. The specification: http://docs.oasis-open.org/wsbpel/2.0/OS/wsbpel-v2.0-OS.html
The purpose of PDF 1.7 is not related to the delivery of multilingual public services. Therefore, this criterion is not applicable to the specification.
'As long as there exists a time-stamping client and a time-stamping server that meets the requirements defined in IETF RFC 3161, the technology will be agnostic. ETSI EN 319 422 reference: https://www.etsi.org/deliver/etsi_en/319400_319499/319422/01.01.01_60/en_319422v010101p.pdf'
Even though JPEG is supporting the first level of maturity from the Tim Berners-Lee 5-star schema for the Open data, which allows the availability of the information over the internet, the specification cannot be considered as an asset to foster data as open data. JEPG ISO reference: https://www.iso.org/standard/18902.html JPEG public reference: https://jpeg.org/jpeg/ Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/en/
'The purpose of SMP is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification. SMP OASIS reference: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505009'
IETF is a consensus-based group, and authority to act on behalf of the community requires a high degree of consensus and the continued consent of the community. The process of creating an Internet Standard is straightforward: a specification undergoes a period of development and several iterations of review by the Internet community and revision based upon experience is adopted as a Standard by the appropriate body and is published. In practice, the process is more complicated, due to (1) the difficulty of creating specifications of high technical quality; (2) the need to consider the interests of all of the affected parties; (3) the importance of establishing widespread community consensus; and (4) the difficulty of evaluating the utility of a particular specification for the Internet community. The goals of the Internet Standards Process are: - Technical excellence; - prior implementation and testing; - clear, concise, and easily understood documentation; - openness and fairness; and - timeliness. The goal of technical competence, the requirement for prior implementation and testing, and the need to allow all interested parties to comment all require significant time and effort. The Internet Standards Process is intended to balance these conflicting goals. The process is believed to be as short and simple as possible without sacrificing technical excellence, through testing before adoption of a standard, or openness and fairness. IETF Reference: https://www.ietf.org/standards/process/
'UBL is an internationally-standardized specification for a suite of common business documents (invoices, purchase orders, waybills, etc.) and a concrete XML syntax (using XSD or RNC) for expressing those documents in a machine-readable format. It is flexible enough to include its own business objects and XML syntax as extensions. It is structured in such a way that it can make business documents utilizing a common library of business objects. UBL v2.3 reference: http://docs.oasis-open.org/ubl/os-UBL-2.3/UBL-2.3.html UBL guidelines for customization: https://docs.oasis-open.org/ubl/guidelines/UBL2-Customization1.0cs01.pdf'
'Some European projects using UBL have been found to conduct effciency assessments. Such is the case of PEPPOL BIS Billing or ESPD. In addition, there has been found some academic papers and assess the efficiency of UBL conformity to specific data models. Peppol BIS Billing 3.0 https://docs.peppol.eu/poacc/billing/3.0/ UBL data model architecture discussion paper: https://www.academia.edu/3213815/UBL_v2_Data_Model_Architecture_Discussion_Paper'
'XACML is included in the DSSC catalogue, where XACML is classified as a Data Sovereignty and Trust standard. DSSC catalogue: https://dssc.eu/space/SE1/185794711 /Data+Sovereignty+and+Trust+standards+and+technologies+landscape'
"When it comes to logging into website, HTTP Cookies can reuse the client information by means of granting him access to the website's services. The stateful nature of HTTP Cookies, therefore, makes it a tool to store and reuse information. HTTP Cookies reference: https://datatracker.ietf.org/doc/html/rfc6265#section-5 "
'The Extensible Forms Description Language specification is based on XML. In this sense, XFDL implementations can be assessed by checking if they follow the correct XML structure. To test this, there are many tools available to test and validate an XML document, such as xmlvalidation. Xmlvalidation platform: https://www.xmlvalidation.com/ Extensible Forms Description Language reference: https://www.w3.org/TR/NOTE-XFDL'
The purpose of OWL2 is not related to the implementation of the once-only principle. Therefore, this criterion does not apply to this specification. OWL2 W3C reference: https://www.w3.org/TR/owl2-overview/
'ETSI TS 119 612 can be applied in any domain and context where the use of the time-stamping protocol is realised. Therefore, the specification is usable beyond any business-specific domain and can be used in any kind of organisation (See section 6 in the following document). ETSI TS 119 612: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf'
'The Advanced Encryption Standard (AES) is used in the VeraCrypt project as an encryption algorithm to protect data from unauthorised access. VeraCrypt AES project: https://veracrypt.eu/en/AES.html AES Standard Reference: https://csrc.nist.gov/pubs/fips/197/final'
'Domibus is part of the CEF eDelivery solutions, which offer conformance testing services in order to verify conformance to the relevant eDelivery specifications upon which Domibus is built. CEF eDelivery conformance testing services: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/eDelivery+Conformance+testing'
'JSON is also distributed through the European platform and repository Joinup, a collaborative platform facilitating the sharing and reuse of IT solutions developed for public administrations. JSON in Joinup: https://joinup.ec.europa.eu/collection/ict-standards-procurement/solution/json-rfc7159-javascript-object-notation-json'
'DNS is independent of any specification and can be implemented without dependencies of any platform. DNS IETF reference: https://datatracker.ietf.org/doc/html/rfc8499 Domain Names - Implementation and Specification: https://tools.ietf.org/html/1035'
'DAPS aims to be versatile across various technologies by establishing rules and guidelines for managing attributes. It provides frameworks that work with different tech setups, enabling smooth communication and attribute management among diverse systems. DAPS: https://github.com/International-Data-Spaces-Association/IDS-G/tree/main/Components/IdentityProvider/DAPS'
'According to section 4.4 of the documentation, ETSI TS 119 512 provides an interface between users and preservation services, however, specific provision are fully achieved if it is combined with its companion documents ETS TS 119 511 therefore, enabling the visibility of administrative procedures, rules and services if combined with other specifications. ETSI TS 119 512 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.02_60/ts_119512v010102p.pdf TR-ESOR Preservation of Evidence of Cryptographically Signed Document: https://www.bsi.bund.de/EN/Service-Navi/Publications/TechnicalGuidelines/TR03125/TechnicalGuidelines_03125_node.html'
The purpose of UDDI is not related to e-accessibility. Therefore this criterion is considered not applicable to this specification.
'The DCAT-AP has been developed and maintaied by the ISA SEMIC action. SEMIC is a group developing european standards centered around semantic technologies. Therefore, DCAT-AP is a European standard. DCAT-AP Specification: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/dcat-application-profile-data-portals-europe/release/200'
'XHTML can be mapped to the EIRA Library of Interoperability Specifications (ELIS) in the "Knowledge" and "Data Representation" under the Semantic view. EIRA Library of Interoperability Specifications (ELIS): https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-andspecifications-camss/solution/elis/release/v610'
'The Better Regulation Guidelines and Toolbox only refers to the access control mechanisms in Tool 28 but is only recommended as best practice. In this sense the specification sets the legal framework for the provision of such features but does not set a definitive guide. Better Regulation Guidelines and Toolbox reference: https://commission.europa.eu/law/law-making-process/better-regulation/better-regulation-guidelines-and-toolbox_en Better Regulation Toolbox reference: https://commission.europa.eu/document/download/9c8d2189-8abd-4f29-84e9-abc843cc68e0_en?filename=BR%20toolbox%20-%20Jul%202023%20-%20FINAL.pdf'
'UTF-8 is recommended by 10 Member States. CAMSS List of standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards '
'The Technical Committee (TC) CYBER (Cybersecurity) collaborates with stakeholders (primarily, National Standards Organizations -NSOs, academics and governmental bodies) to develop standards that improve the privacy and security of organizations and citizens in Europe and all over the world (see ETSI Directives, Rules of Procedure section, and EN 303 645 homepage reference). As the EN 303 645 is a European Standard (EN), the specification has gone through (national) public enquiry and voting (see NSOs ETSI-partnerships, EN 303 645 Public enquiry, and ETSI TC CYBER Contribution references). However, public consultations on major and minor releases are not publicly visible. ETSI Directives, Rules of Procedure section: https://portal.etsi.org/Resources/ETSI-Directives EN 303 645 homepage reference: https://www.etsi.org/technologies/consumer-iot-security EN 303 645 Public Enquiry reference: https://www.etsi.org/newsroom/press-releases/1789-2020-06-etsi-releases-world-leading-consumer-iot-security-standard NSOs ETSI-partnerships reference: https://www.etsi.org/about/our-partnerships ETSI TC CYBER, Contribution reference: https://portal.etsi.org/tb.aspx?tbid=824#/50610-contributions'
'ISO 639-2 is intended to identify a language name. This specification relates to metadata, and can be used in any system that ingests metadata. Therefore, it can be considered technology-agnostic. ISO 369-2 FAQs: https://www.loc.gov/standards/iso639-2/faq.html#5 https://www.loc.gov/standards/iso639-2/faq.html#7'
The specification was developed in 1992 and it has been broadly used. JPEG is supported as one of the main image file formats. Independent JPEG Group: https://www.ijg.org/ JPEG.org: https://jpeg.org/jpeg/index.html
The version 1.0 of the specification, which is the previous version of the SMP, was identified within the List ICT technical specifications as reusable, meaning that the Service Metadata Publisher is considered. Even though the version being assessed is not the one identified, it can be considered that the SMP is listed within this repository at European Level. ICT technical specifications: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en
After searching for a certification or conformity test to validate this document, no tool has been found that assesses the conformity of the specification.
"The OGC TrainingDML-AI working group values all feedback received but maintains confidentiality of feedback and contributors' identities to foster an inclusive and open process and protect intellectual property rights. However, the final standard will be publicly accessible, reflecting changes based on feedback received. Subscribers to the Distribution List may access open feedback. OGC Policies reference: https://www.ogc.org/about-ogc/policies/ OGC Distribution list substription: https://www.ogc.org/requests/ogc-seeks-public-comment-on-new-standard-for-training-data-for-ai-mlapplications/"
'While IndexedDB itself does not define a specific mechanism for it, storage of structured content also allows developers to store internationalised content, using different records or structure within records to hold language alternatives. Indexed Database API: https://www.w3.org/TR/IndexedDB/'
'HTTP contributes to data integrity through features like secure transport (TLS), caching and invalidation procedures, conditional requests, and message framing that help to ensure the complete and unaltered transmission of information. HTTP/1.1, RFC 2616 Reference: https://www.rfc-editor.org/rfc/rfc2616 HTTP/1.1 Caching, RFC 9111 Reference: https://www.rfc-editor.org/rfc/rfc9111#name-updating-stored-header-fiel HTTP/1.1 Authentication, RFC 9110 Reference: https://www.rfc-editor.org/rfc/rfc9110#name-http-authentication'
'ETSI TS 119 512 can facilitate the modelling of business processes when it comes to defining the relationships among the preservation schemes, preservation profiles and their related policies on a given business-specific trust service (see section 4.4). ETSI TS 119 512 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.02_60/ts_119512v010102p.pdf'
'The purpose of TrainingDML-AI is not related the secure processing of data. However, secure processing of data is typically ensured by implementing appropriate security measures at the application level. OGC TrainingDML-AI Standard: https://docs.ogc.org/is/23-008r3/23-008r3.html'
This specification fosters the data exchange between citizens and businesses, and public administrations. Moreover, it is capable to transport mail across multiple networks. But the main problem of this protocol is his inherent insecurity. SMTP does not include any security feature, therefore, it could be feasible for even fairly casual users to negotiate directly with receiving and relaying SMTP servers and create messages that will trick a naive recipient into believing that they came from somewhere else. However, there are secured solutions that use SMTP as his core to make an email protocol secure, for example, SMTPS (Simple Mail Transfer Protocol Secure) or STARTLS-SMTP. But they could be analysed as different specifications. SMTP IETF reference: https://tools.ietf.org/html/rfc5321 Secure SMTP over Transport Layer Security: https://tools.ietf.org/html/rfc3207
"OSI is associated to the ABB's Data Space Connector, Data Space Connector consumer and Data Space Provider in the EIRA Library Of Interoperability Specifications (ELIS). EIRA Library Of Interoperability Specifications (ELIS) https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/version-610"
'ISAE 3402 was published for the first time in 2009, which means that it has evolved from a stable version and it is mature enough to consider it for the creation and development of solutions and services. ISAE 3402 supersedes SAS 70 and puts more emphasis on procedures for the ongoing monitoring and evaluation of controls. ISAE 3402 history https://www.isae3402.com/ISAE3402_history/ '
'The purpose of OCSP is not related to the availability of interfaces with internal information systems. Therefore, this criterion is not applicable to this specification. OCSP reference: https://datatracker.ietf.org/doc/html/rfc2560'
'The purpose of DAPS is not related to e-accessibility. Therefore, this criterion is considered not applicable to this specification. DAPS: https://github.com/International-Data-Spaces-Association/IDS-G/tree/main/Components/IdentityProvider/DAPS'
'The SAML 2.0 specification itself is focused on authentication, authorization, and federated identity, not directly on modelling business processes. However, federated identity, which SAML supports, can significantly streamline business processes: Federated identity allows users to use a single set of credentials to access multiple systems or applications across different organizations. SAML2.0 Reference: http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-tech-overview-2.0.html'
'GraphQL has a large history of implementations, and its improvements are widely documented in github. The specification has published documentation of its supporting processes in the Github platform, where anyone can access to the history of changes and the authors involved. The link below shows all the changes implemented for the last release of 2021 and the developers involved in those changes. GraphQL changelog in Github: https://github.com/graphql/graphql-spec/blob/main/changelogs/October2021.md'
'The purpose of Extensible Forms Description Language is not related to facilitate the modelling of business processes. Therefore this criterion is not applicable to the specification. Extensible Forms Description Language reference: https://www.w3.org/TR/NOTE-XFDL'
'The purpose of Extensible Forms Description Language is not related to the delivery of multilingual services. Therefore this criterion is not applicable to this specification. Extensible Forms Description Language reference: https://www.w3.org/TR/NOTE-XFDL'
'The specification does not make any provision that would facilitate the organisational interoperability agreements. FTP Specification Reference: https://datatracker.ietf.org/doc/html/rfc959'
'iCalendar has not been found included in any initiative covering privacy aspects. iCalendar specification: https://www.rfc-editor.org/rfc/rfc5545'
'IEEE Std 802.3-2022 does not directly enable the exposure of interfaces for public administration services. Therefore, this criterion is not applicable to this specification. IEEE Std 802.3-2022 Reference: https://ieeexplore.ieee.org/document/9844436'
'Odata is included in 2 national catalogues of recommended specifications. They belong to France and The Netherlands. The National Interoperability Framework (NIF) of these Member States are aligned with at least 3 out of 4 scoreboards of the EIF Monitoring framework according to the National Interoperability Framework Observatory (NIFO) factsheets. National catalogue France: https://www.numerique.gouv.fr/publications/interoperabilite/ National catalogue Netherlands: https://www.forumstandaardisatie.nl/open-standaarden/aanbevolen NIFO factsheets: https://interoperable-europe.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public-administration-factsheets-2024'
HTTPS does not defines a cross-sector reusable data model. HTTPS is a transfer protocol used for secure communication over a computer network.
'DCAT-AP can be used with any software platform or system that supports the standard. This is because DCAT-AP is based on web standards such as RDF (Resource Description Framework), which is widely used on the web and can be implemented by any software platform or system. DCAT-AP Specification: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/dcat-application-profile-data-portals-europe/release/200'
'DNS is the hierarchical and decentralized naming system used to identify computers reachable through the Internet or other Internet Protocol (IP) networks. For that matter it can be used in any domain. DNS IETF reference: https://tools.ietf.org/html/1034 Domain Names - Implementation and Specification: https://tools.ietf.org/html/1035 '
'The PROV family of documents does not provide direct means for the restriction of access to information. Access control and restriction of information are typically implemented at the system or application level through security mechanisms, authentication protocols, and authorization frameworks. These mechanisms determine who has access to specific information and under what conditions. PROV Primer document: https://www.w3.org/TR/prov-primer/ PROV Ontology: https://www.w3.org/TR/2013/REC-prov-o-20130430/ PROV Data Model: https://www.w3.org/TR/2013/REC-prov-dm-20130430/ PROV-AQ Security cosiderations: https://www.w3.org/TR/2013/NOTE-prov-aq-20130430/#security-considerations'
"Currently the specification is widely used in various implementations. Currently the International Classification for Standards (ICS) lists the specification's updates showing its widespread use and implementation. Furthermore, given that the specification is a basic element of specification development its usage is mainly on communication engineering companies such as Microsoft. ICS on OSI https://www.iso.org/ics/35.100/x/ Microsoft and OSI: https://learn.microsoft.com/en-us/windows-hardware/drivers/network/windows-network-architecture-and-the-osi-model OSI reference https://www.iso.org/standard/20269.html "
'The purpose of DCAT is not related to e-accessibility. Therefore this criterion is not applicable to this specification. DCAT (v2.0.0) reference: https://www.w3.org/TR/vocab-dcat-2/ '
'ETSI TS 119 511 is part of the Electronic Signatures Infrastructure (ESI) family of specifications. The ESI dates back to 2012, when the General Policy Requirements for Trust Service Providers supporting Electronic Signatures (ETSI EN 319 401) specification was first issued. Since its first publication, there have been many extensions one of which is ETSI TS 119 511, whose version 1.1.1 was released in 2020 when the eIDAS regulation identified the need to create protocols to develop preservation services for trust service providers, as mentioned in ETSI SR 019 510, giving birth to both TS 119 511 and TS 199 512 specifications. ESI specification history: https://standards.globalspec.com/std/14387016/EN%20319%20401 ETSI TS 119 511 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119511/01.01.01_60/ts_119511v010101p.pdf ETSI EN 319 401 specification: https://www.etsi.org/deliver/etsi_en/319400_319499/319401/02.03.01_60/en_319401v020301p.pdf eIDAS blog, New APIs for the eIDAS-Ecosystem: https://blog.eid.as/tag/etsi-ts-119-512-en/'
"As a common data exchange format, CSV fosters the visibility of administration's data. It eases the publication of structured data for the consumption by the different stakeholders. Therefore, CSV fosters the visibility of administrations data. Additionally, it can be used internally easing as well as the decision-making process. CSV reference: https://datatracker.ietf.org/doc/html/rfc4180"
The purpose of RegOrg is not related to organisational interoperability. Therefore, this criterion is not applicable to the specification. RegOrg Joinup reference: https://joinup.ec.europa.eu/solution/registered-organization-vocabulary
'IPv4 can be enhanced with IPsec, which ensures the authenticity and integrity of transmitted data. IPsec guarantees that the content remains unchanged from its original form when it is sent, and that data will reliably reach the receiver. IPsec protocol: https://www.cloudflare.com/learning/network-layer/what-is-ipsec/'
'DPV provides mechanisms for extending concepts in order to align existing concepts or vocabularies with the DPV taxonomies, such as by declaring them as subclasses of a particular concept. This allows for the creation of domain or jurisdiction specific extensions, such as DPV-GDPR for expressing the legal bases provided by GDPR. DPV Extending concepts for use cases: https://w3c.github.io/dpv/primer/#using-dpv-in-use-cases'
'OAIS appears in the National Catalogue of France. France gets a high performance on interoperability according to the National Interoperability Framework Observatory (NIFO) Factsheets. National Catalogue of France: https://www.numerique.gouv.fr/uploads/Referentiel_General_Interoperabilite_V2.pdf NIFO Factsheets: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public-administration-factsheets-2022'
'The centralised databases that GraphQL is able to generate actively promote visibility and the ruling of data insofar it facilitates the retrieval and publication of data in a system, thus having the potential to leverage administrative procedures. GraphQL specification: https://spec.graphql.org/October2021/#sec-Overview'
The first version of ODF was released in 2005, but it was not published as an ISO standard until 2006. It is implemented by LibreOffice, a worldwide Open document format that has the support of The Document Foundation, an open community focused on the improvement of LibreOffice. ODF ISO reference: https://www.iso.org/standard/66363.html ODF OASIS reference: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office The Document Foundation https://wiki.documentfoundation.org/ODF
'The ebXML specification is an independent technology that takes a top-down approach to providing business process standardisation. In this context, the specification requirements also address interoperability, ubiquity, extensibility, security, transactions, and so on. Moreover, several initiatives in Europe have adopted the Universal Business Language (UBL), which is designed to be agnostic with respect to any EDI infrastructure and mapped to the ebXML core components. Interoperable Europe Portal OASIS UBL reference: https://interoperable-europe.ec.europa.eu/collection/eprocurement/solution/oasis-universal-business-language-ubl "ebXML and Web services" study: https://ieeexplore.ieee.org/abstract/document/1200304 ebXML RegRep OASIS reference: https://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html'
'According to the 5 star Open Data model suggested by Tim Berners-Lee about how to publish linked data, the forth star corresponds to represent data with URIs. According to the Odata home page, OData enables the publication of open data. This specification supports REST-based data services, allowing any resource, as well as open data, to be published and edited via simple HTTP messages. Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/en/ Odata reference: https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html'
"Schema.org grants data exchange permissions through the schema.org type DigitalDocumentPermission. Such metadata improves the reliability of data exchanged between citizens, businesses and public administrations. Schema.org homepage reference, 'About Schema.org' section: https://schema.org/docs/about.html Schema.org reference, DigitalDocumentPermission type: https://schema.org/DigitalDocumentPermission?msclkid=fe03a55bab5411eca9752ad0bc8beac1"
RegOrg is a business domain agnostic data model that can be reused in a cross-domain way. RegOrg about Joinup reference: https://joinup.ec.europa.eu/solution/registered-organization-vocabulary/about
'The UDDI specification includes a flexible data structure that can be extended to accommodate additional types of data beyond the standard set. This extensibility is facilitated through the use of tModels (type models), which are abstract descriptions of concepts or business services within UDDI. tModels UDDI reference: http://www.uddi.org/pubs/uddi_v3.htm#_Toc85908315'
'The ELI system does not inherently provide protection against unauthorized changes.Therefore, this criterion is considered not applicable to this specification. ELI reference: https://eur-lex.europa.eu/eli-register/about.html'
Due to the fact that the purpose of IPSec is to secure communications over the Internet Protocol (IP), IPSec is dependant from IPv4 and IPv6. However, IPSeC is designed for this area of application and IPv4 and IPv6 are widely used standards. Therefore, this dependency with specification for which IPSec has been developed, does not hamper interoperability.
'The ELI specification significantly enhances the facilitation of organizational interoperability agreements by providing a standardized framework for the identification and referencing of legal documents across different entities. Its design promotes consistency and compatibility, fostering a more seamless exchange of information and collaboration among organizations. ELI reference: https://eur-lex.europa.eu/eli-register/about.html'
"GraphQL does not provide any feature that contribute to covering authenticity aspects. Only the GraphQL JavaScript extension may process the user's authenticated viewer object via the rootValue argument when resolving a response. GraphQL specification, Authorization section: https://graphql.org/learn/authorization/#gatsby-focus-wrapper GraphQL-JS extension: https://graphql.org/graphql-js/"
'TOSCA offers the possibility to manage and orchestrate resources for the provisioning of cloud applications and services. In this sense, when combined with other specifications, the specification can scope comprehensibility of data and services. TOSCA reference, section 1.2: https://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.3/os/TOSCA-Simple-Profile-YAML-v1.3-os.html#_Toc26969412'
'The EN 16234-1 e-CF framework is intended to serve as a device to represent the European e-Competence Framework, which focuses on skills and competences of the ICT professional workforce. There is no possibility to extend the specification, as EN 16234-1 e-CF has a single purpose. CEN reference, CEN/TC 428 - ICT Professionalism and Digital Competences (Published standards), EN 16234-1 e-CF: https://standards.cencenelec.eu/dyn/www/f?p=205:110:0::::FSP_PROJECT:67073&cs=15E62ED24D608A5F10D6BEE8E6D50FA10'
'In accordance with ISO/IEC JTC 1 and the ISO and IEC Councils, ISO/IEC 19944-1 is classified as a Publicly Available Standard (PAS) and therefore is publicly available for Standardization purposes. ISO/IEC JTC 1: https://jtc1info.org/ Publicly available ISO/IEC standards: https://standards.iso.org/ittf/PubliclyAvailableStandards/index.html'
'Syslog allows for customisation to a significant extent. The syslog protocol is designed to be flexible, and various elements within syslog messages can be customized based on specific needs and requirements. Some aspects of syslog that can be customised are: Message content, facility codes, severity levels, structured data, timestamp format, transport protocol, etc. Syslog Protocol: https://datatracker.ietf.org/doc/html/rfc5424'
'DNS over HTTPS (DoH) allows for partial implementations. Implementing DoH can be done selectively for specific clients, applications, or DNS queries, rather than applying it universally across an entire network. This flexibility enables organizations to adopt DoH gradually or in a targeted manner. For instance, organisations can adopt DoH gradually by implementing it on a subset of devices or services. DoH specification: https://datatracker.ietf.org/doc/html/rfc8484'
'XHTML utilizes XML namespaces. This allows you to incorporate custom elements and attributes from other XML vocabularies within your XHTML documents.As an example XHTML could be used in conjunction with the MathML. MathML Reference: https://www.w3.org/TR/xhtml1/#ref-xhtml-mathml XHTML W3C reference: https://www.w3.org/TR/xhtml1/'
'OpenTelemetry significantly enhances the exposure and management of interfaces as it enables detailed tracking of API performance, improves reliability and user experience, offers deep tracing and diagnostic capabilities and helps ensure compliance and security. By leveraging OpenTelemetry, public administrations can ensure their services are robust, efficient, and user-friendly, leading to better service delivery. OpenTelemetry: https://opentelemetry.netlify.app/docs/specs/otel/'
'After checking the different standard catalogues at supra-national level, there is no evidence of NFVI as a European standard. ICT technical specifications: https://ec.europa.eu/growth/single-market/european-standards/ict-standardisation/ict-technical-specifications_en CENELEC and CEN search tool catalogue: https://standards.cencenelec.eu/dyn/www/f?p=CEN:105::RESET::::'
'There is no evidence of any assessment regarding the efficiency of this specification, nor any evaluation submitted by a European administration. Publications Office reference: https://op.europa.eu/en/home Language codelist reference: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/language'
'The ISO 639-2 code suite was developed to be used by libraries, information services and publishers to indicate language in the exchange of information, especially in computerised systems. Therefore, the specification prompts visibility of administrations by allowing, for instance, the publication of data or the display of web content in the language of the user. For example, the European Commission website (http://ec.europa.eu) can be switched into one of the official languages of the EU. ISO 369-2 FAQs: https://www.loc.gov/standards/iso639-2/faq.html#5 Language codelist reference: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/language European Commission reference: https://ec.europa.eu/'
'The specification has published the major releases but no public documentation or supporting processes are available. The specification current version replaces the previous version from 1984 which was developed as an industry effort, attempting to get industry participants to agree on common network standards to provide multi-vendor interoperability. It was common for large networks to support multiple network protocol suites, with many devices unable to interoperate with other devices because of a lack of common protocols. When TCP/IP came into widespread use on multi-vendor networks for internetworking OSI was relegated. Nonetheless the OSI reference model is still in place in certain aspects like cloud computing OSI reference https://www.iso.org/standard/20269.html OSI and cloud computing https://blogs.cisco.com/cloud/an-osi-model-for-cloud'
The main objective of the Portable Document Format (PDF) is to allow text format and images to be independent and work for any software, hardware or operating system. So it can be said that PDF is independent from any specific technology of platform.
'The conformance of schema.org implementations can be assessed in several ways since it is defined as a set of requirements (see Schema.org reference, Vocabulary Definition Files section). Additionally, the schema.org project offers a conformance testing platform to allow testing implementations (see Schema.org reference, Validator section). Schema.org reference, Data model-Conformance section: https://schema.org/docs/datamodel.html Schema.org reference, Vocabulary Definition Files section: https://schema.org/docs/developers.html#defs Schema.org reference, Validator section: https://validator.schema.org/'
DNS is independent of any specification and can be implemented without dependencies with technologies or platforms.
'XSLT has an open community where stakeholders can participate in discussions and contribute to the evolution of the standard. Community engagement can foster the sharing of best practices, use cases, and insights related to the implementation of XSLT. XQuery and XSLT Extensions Community Group: https://www.w3.org/groups/cg/xslt-40/'
The specification is included in 8 Member States' catalogues of recommended specifications. This Member States are Croatia, France, Germany, Greece, Malta, Netherlands, Spain and Sweden. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
There are no competitors for TLS 1.3 since no standards with overlapping functional scope have been found. No interoperability issues with the implementation of existing European or international standards exist.
SOAP 1.2 is publicly available for implementation and use for free on W3C's webpage. Therefore it can be reused by the organisations, administrations, open communities, etc. that developed it. See: https://www.w3.org/TR/soap12/
'iCalendar defines an access classification as the only component of the overall security system within a calendar application. However, this access classification mechanism must be complemented by other security components of a calendar system in line with the platform or system where the specification is being used. iCalendar Classification: https://www.rfc-editor.org/rfc/rfc5545#section-3.8.1.3'
There are no tools that assess the conformity of FTPS implementations. However, there are online tools developed by the FTP community, which assess FTP and FTPS servers performance. FileZilla tests FTPS implementation: https://filezilla-project.org/
'ETSI EN 319 532-3 is to ensure a consistent form of service across Europe, especially with regard to the form of evidence provided, in order to maximize interoperability even between e-mail domains governed by different policy rules. ETSI EN 319 532-3 reference: https://www.etsi.org/deliver/etsi_en/319500_319599/31953203/01.02.01_60/en_31953203v010201p.pdf'
'GITB TDL is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, GITB TDL can define the interoperability aspects of the Human Interface ABB of the EIRA Technical View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/v110'
'No communities have been found created to share data and results of the implementation of ISO 27001 on European platforms. ISO/IEC 27001 reference website: https://www.iso.org/standard/54534.html'
'France has been found recommending YAML in their ICT National Catalogue. Moreover, it has been used in European projects. OpenModel project: https://cordis.europa.eu/project/id/953167/reporting CAMSS list of standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards France National catalogue: http://references.modernisation.gouv.fr/sites/default/files/Referentiel_General_Interoperabilite_V2.pdf'
'Having reviewed various standard catalogues at the supra-national level, the Publications Office has compiled a comprehensive list containing specifications and resources integral to the creation, utilization, and accessibility of open data. EUR-Lex: https://eur-lex.europa.eu/homepage.html ELI reference: https://eur-lex.europa.eu/eli-register/about.html EU Vocabularies Business Collection: https://op.europa.eu/en/web/eu-vocabularies/business-collections'
'All solutions developed in ISA² Programme are under ISA Open Metadata Licence which is perpetual, royalty-free and non-exclusive license to Use and re-Use the Works. ISA open metadata license: https://interoperable-europe.ec.europa.eu/licence/isa-open-metadata-licence-v11 Core Location Vocabulary: https://interoperable-europe.ec.europa.eu/collection/semic-support-centre/solution/core-location-vocabulary/release/100'
'With GraphQL, the business domain can be modelled as a graph by defining a schema; within the schema, it defines different types of nodes and how they connect/relate to one another. GraphQL specification: https://spec.graphql.org/October2021/#sec-Overview GraphQL capability: https://graphql.org/learn/thinking-in-graphs/'
At the moment of performing the assessment, PDF/A is widely used in across sector manner. One of the main document format used for the document exchange between different parties, and to ensure the availability of documents' content over the time. A clear example of this are public administrations and the high usage of PDF as a document format to exchange information. However, it cannot be considered as an asset to build innovative solutions. PDF/A reference: https://www.iso.org/standard/38920.html https://www.iso.org/standard/50655.html
The OpenPM2 is a specification that aims to increase the effective and efficient management of process helping them to the development of better solutions, products or services. However, its implementation is not strictly related to reach or foster the secure data exchange of the developed products and services. Nonetheless, the use of this specification can help to determine the certain KPI helping the proper evolution of projects, and therefore a better quality in the developed solution. In this sense, the application could help to enhance how data is exchanged. OpenPM2 specification reference: https://op.europa.eu/en/publication-detail/-/publication/ac3e118a-cb6e-11e8-9424-01aa75ed71a1/language-en/format-PDF/source-83307127
'TrainingDML-AI Standard’s effectiveness has undergone a internal rigorous review and approval process. The effectiveness of the standard would likely depend on factors such as its adoption rate, the performance of AI/ML models trained using data prepared according to the standard, and feedback from the user community. OGC TrainingDML-AI Standard: https://docs.ogc.org/is/23-008r3/23-008r3.html OGC TrainingDML-AI approach for making EO training datasets ready in deep learning frameworks paper: https://ieeexplore.ieee.org/document/10233498'
'After checking the different standard catalogues at supra-national level, there is no evidence of REST as a European standard. ICT technical specifications: https://ec.europa.eu/growth/single-market/european-standards/ict-standardisation/ict-technical-specifications_en CENELEC and CEN search tool catalogue: https://standards.cencenelec.eu/dyn/www/f?p=CEN:105::RESET::::'
'A Linked Data Event Stream (LDES) helps to establish a harmonised approach for digital coordination through APIs. By allowing the publication of data as "event streams", public administrations can share real-time updates about different processes. Therefore, visibility of administrative procedures, rules data, and services can improve greatly. LDES specification: https://joinup.ec.europa.eu/collection/semic-support-centre/linked-data-event-streams-ldes'
"JSON is available for its use an implementation at ECMA International and EITF's webpages. In addition, ECMA's technical Committee for JSON is in charge of maintaining, improving the specification and other management tasks. JSON specification in ECMA webpage: https://www.ecma-international.org/publications/standards/Ecma-404.htm JSON specification in IETF: https://tools.ietf.org/html/rfc8259 JSON Technical Committee: https://www.ecma-international.org/technical-committees/tc39/ "
'The XML specification itself does not providean access control mechanism.Therefore this criterion is not applicable to the specification.'
"REST is a sofware architectural style which defines a set of costraints for how the architecture of an internet-scale distributed hypermedia system should behave. REST architectural constraints are designed to provide efficient and scalable client-server applications allowing for extensions and new adaptations when needed. In this regard, REST allows for a greater interoperability, explicitly addressing and enabling data portability between systems/applications. REST reference: https://restfulapi.net/ REST Introduction from Roy Fielding's dissertation: https://www.ics.uci.edu/~fielding/pubs/dissertation/introduction.htm"
The objective of the LegalRuleML TC is to extend RuleML with formal features specific to legal norms, guidelines, policies and reasoning; that is, the TC defines a standard (expressed with XML-schema and Relax NG) that is able to represent the particularities of the legal normative rules with a rich, articulated, and meaningful markup language. It can be concluded that the specification fosters defining organisational interoperability aspects. LegalRuleML reference: http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/legalruleml-core-spec-v1.0.html
One of the main goals of the Better Regulation Toolbox is to enhance the transparency of the public policy and law-making, increasing the visibility of public administrations decision-making process. Better Regulation Toolbox reference: https://ec.europa.eu/info/sites/info/files/better-regulation-toolbox_2.pdf Objective of Better Regulation Toolbox: https://ec.europa.eu/info/law/law-making-process/planning-and-proposing-law/better-regulation-why-and-how_en#objectives-of-the-better-regulation-agenda
'The DNS specification includes the data structures of data communication used by the system, therefore, DNS may, at some point, facilitate the modelling of business processes. DNS Domain Names: https://datatracker.ietf.org/doc/html/rfc8499 DNS - implementation and specification: https://tools.ietf.org/html/1035'
The purpose of this RegOrg is not related to the availability of interfaces with internal information systems. Therefore, this criterion is not applicable to this specification. RegOrg Joinup reference: https://joinup.ec.europa.eu/solution/registered-organization-vocabulary
By establishing constraints on the creation and exchange of XML documents XSD fosters the trustworthy data exchange between administrations and stakeholders. However, XSD does not include security features in itself. Despite this, XML includes several recommendations in order to ensure the security of data and users.
'SMP specification leads, in combination with other specifications, dicussions in the eDelivery User Community, which deals with privacy aspects. SMP OASIS reference: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505009 Reference of SMP working in combination with other specifications: https://ec.europa.eu/digital-building-blocks/wikis/display/EDELCOMMUNITY/eDelivery+User+Community'
The purpose of XML is to store, transport and exchange data through interoperable systems. Additionally, the specification provides the means to validate XML documents using XML schemas.
'Through the identifiers, a decentralised and verifiable way of monitoring and managing administrative processes is provided. If each step in the administrative process can be associated with a did, the processes can be verified and made more visible and reliable, thus contributing to the visibility of administrative procedures. DIDs W3C: https://www.w3.org/TR/did-core/'
'Slovenia is recommending ODRL2. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards '
'The specification is independent from any particular software, hardware, or operating system. So, it can be said that the Dataspace Protocol is independent of any specific platform. IDSA Dataspace Protocol Specification: https://docs.internationaldataspaces.org/ids-knowledgebase/v/dataspace-protocol/overview/readme'
' ISO/IEC 7498:1 does not prescribe specific hardware, operating systems, or platforms.The platform-agnostic nature of the OSI model allows for the development of network protocols and communication systems that can work across diverse platforms, operating systems, and hardware architectures. ISO/IEC 7498:1: https://www.iso.org/standard/20269.html'
'While ODRL does not address these specific aspects of data accuracy, it can be integrated into broader systems that implement these practices. For example, ODRL might be used to express rights and permissions related to accessing or modifying data, and the accuracy of the data itself would be managed through other data governance and quality assurance measures. W3C specification reference: https://www.w3.org/TR/odrl-vocab/#vocab-core'
'There are several existing documents and studies assessing SAML 2.0 features and capabilities and efficiency. Broadly speaking, the studies are focused on the capability to enable Single Sign-on and its benefits. Researchgate analysis on SAML2.0 Reference: https://www.researchgate.net/publication/221609828_Formal_analysis_of_SAML_20_web_browser_single_sign-on Researchgate on Single Sign-on Auth Reference: https://www.researchgate.net/publication/45872317_Web_single_sign-on_authentication_using_SAML'
The purpose of SMTP is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification. SMTP IETF reference: https://tools.ietf.org/html/rfc5321
"REST is a sofware architectural style which defines a set of costraints for how the architecture of an internet-scale distributed hypermedia system should behave. REST architectural constraints are designed to provide efficient and scalable client-server applications through a URI resource approach. In this regard, REST allows for a greater interoperability, explicitly addressing and enabling data portability between systems/applications. REST reference: https://restfulapi.net/ REST Introduction from Roy Fielding's dissertation: https://www.ics.uci.edu/~fielding/pubs/dissertation/introduction.htm"
'There are assessments that evaluate the effectiveness by evaluating digital solutions that involve the specification, as it shows in the following link: ADMS in Joinup: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/adms '
After checking the different standard catalogues at the supra-national level, the European Commission has listed it within Better Regulation Toolbox with all the specifications and resources produced and used by European Institutions. Even though the specification is not listed in the ICT standards catalogue, it can be considered that is included within a European Catalogue because it is included within the European Commission solutions stack for the development of better digital administrations. Better Regulation Toolbox on European Comission webpage: https://ec.europa.eu/info/law/law-making-process/planning-and-proposing-law/better-regulation-why-and-how/better-regulation-guidelines-and-toolbox/better-regulation-toolbox_en
eDelivery SMP 1.0 is available for free at CEF’s website, which is an open resource for the European development. See: https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery+SMP+-+1.10
'LDAP gives access to distributed directory services according to the data and services models provides by the X.500 family of standards. Therefore, the specification facilitates the modeling of business processes. LDAP IETF reference: https://datatracker.ietf.org/doc/html/rfc4511 X.500 reference: https://www.itu.int/rec/dologin_pub.asp?lang=e&id=T-REC-X.500-201910-I!!PDF-E&type=items'
HTML is publicly available for implementation and use for free on W3C's webpage. Therefore, it can be reused by the organisations, administrations, open communities, etc. that developed it. HTML W3C reference: https://www.w3.org/TR/html401/
'The RFC 3161 Time-Stamp Protocol (TSP) is widely used and involved in e-Signature services. This electronic signatures are part of digital public services, and also private in order to focus the development of digital environments avoiding the non-digital transactions. Moreover, the TSP has been adopted by many countries and the European Union for initiatives and projects. TSP IETF reference: https://tools.ietf.org/html/rfc3161 DigiStamp: https://www.digistamp.com/ FreeTSA: https://www.freetsa.org/index_en.php'
'The specification enables developers to create custom widgets and other web application components. WAI-ARIA reference, section 1: https://www.w3.org/TR/wai-aria/'
This Core Vocabulary offers several services that aim to help e-Government professionals share their experience with each other, so it fosters the creation of innovative solutions. CCCEV reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-criterion-and-core-evidence-vocabulary
'IPsec foresees extensibility but only in very specific cases. Normally this extensibility is limited to IP fragmentation. IPSec reference: https://www.rfc-editor.org/rfc/rfc6071.html'
By allowing public administration to share information with others in a specific format, it fosters the comprehensibility of data (e.g. Administrative rules, processes etc.) and facilitates public administrations decision-making. MIME reference: https://tools.ietf.org/html/rfc2045
'While the specification itself does not directly simplify the delivery of European public services, it can play a role in supporting the development of digital solutions and services that can help to streamline and improve the delivery of these services in the legal domain. AKN4EU reference: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/akn4eu'
The rules on European standardisation allow the European Commission to identify information and communication technology (ICT) technical specifications - that are not national, European or international standards - to be eligible for referencing in public procurement. This allows public authorities to make use of the full range of specifications when buying IT hardware, software and services, allowing for more competition in the field and reducing the risk of lock-in to proprietary systems. After being evaluated compliant with the regulation on standardisation 1025/2012, FTP has been identified by Commission Implementing Decision. During the evaluation process, all the Member States are invited to share their doubts. The positive evaluation of FTP and its identification is considered an interoperability agreement. See: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en
"This specification's releases do not foresee public reviews. While the life cycle of ISO 19941 is completely public, its content is not published on the web. ISO 19941: https://www.iso.org/standard/66639.html"
'There are several studies assessing the adoption, strengths, weaknesses, effectiveness and efficiency of FTP. Downsides of using an FTP Solution: https://dzone.com/articles/potential-downsides-of-using-an-ftp-solution Evaluate your FTP Assessment: https://themanifest.com/development/how-evaluate-your-file-transfer-protocol-system Risks of using FTP: https://sapinsider.wispubs.com/Assets/Articles/2012/January/Using-FTP-Know-The-Risks '
'There has not been found any European cross-border project directly using ISO/IEC 19944-1. Nonetheless, the EUCS Cloud Service Scheme, is using the components from ISO/IEC 17788 and ISO/IEC 17789, standards from which ISO19944-1 is derived and extended. ISO/IEC 19944-1 specification: https://www.iso.org/standard/60545.html EUCS project: https://www.enisa.europa.eu/publications/eucs-cloud-service-scheme'
'As a specification used to encode a wide range of resources, UTF-8 eases the codification of interfaces ensuring its availability. Therefore, UTF-8 helps to ensure the availability of internal information systems from public administrations. UTF-8 specification: https://datatracker.ietf.org/doc/html/rfc3629 '
'The purpose of UDDI is not related to the delivery of multilingual services. Therefore this criterion is not applicable to this specification. UDDI OASIS reference: https://www.oasis-open.org/standard/uddi/'
'UBL conceptual model is based on modeling systems such as entity/relationship modeling and the unified modeling language. The use of UBL has many benefits for the modelling of business processes, among which we can highlight that it provides detailed textual descriptions, explanations, and examples of each of its specified functions and messages, as well as clear rules for extension and a number of subsets and tool resources. The Meaning of UBL: The Value of a Semantic Data Model: http://ubl.xml.org/forum/the-meaning-of-ubl-the-value-of-a-semantic-data-model'
5 Member States are recommending PAdES in their ICT National Catalogues. See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
LegalRuleML extends RuleML with formal features specific to legal norms, guidelines, policies and reasoning. The specification is also able to represent the particularities of the legal normative rules with a rich, articulated, and meaningful markup language. An example of this is the LEOS software, a tool for drafting legal documents at European Level. Moreover, its structured format and capabilities can help administrations at European Level to transpose legal documents into national law and vice versa easily. This fact is a key aspect to reduce the administrative burden. LegalRuleML reference: http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/legalruleml-core-spec-v1.0.html LEOS: https://joinup.ec.europa.eu/collection/justice-law-and-security/solution/leos-open-source-software-editing-legislation
The purpose of the specification is not related with the publication of data. Therefore, this criterion is not applicable to this specification. XACML OASIS reference: http://docs.oasis-open.org/xacml/3.0/errata01/xacml-3.0-core-spec-errata01.html
'The purpose of Advanced Encryption Standard is not related to facilitate the modelling of business processes. Therefore this criterion is not applicable to this specification. AES Standard Reference: https://csrc.nist.gov/pubs/fips/197/final'
'The puropes of ETSI TS 119 511 is not related to the exposure of interfaces. Therefore this criterion does not apply to this specification. ETSI TS 119 511 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119511/01.01.01_60/ts_119511v010101p.pdf'
After checking the assessments performed by CAMSS and the list of specifications identified by the MSP Multi-stakeholder-platform, no assessment verifying the compliance of the specification with the European standardisation regulation has been found. ICT technical specifications: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en CEN search tool catalogue: https://standards.cen.eu/dyn/www/f?p=CENWEB:105::RESET:::: CENELEC search tool catalogue: https://www.cenelec.eu/dyn/www/f?p=104:107:0::::FSP_LANG_ID:25
W3C provides a Markup Validation Service for free to validate Web documents including XHTML implementations. W3C Markup Validation Service: https://validator.w3.org/
'Syslog is technology-agnostic at the application layer, meaning it is not tied to a specific operating system, programming language, or underlying technology. Syslog operates at the network layer and focuses on the transport of log messages between devices and systems. This characteristic makes syslog a versatile and widely adopted logging protocol. Syslog Protocol: https://datatracker.ietf.org/doc/html/rfc5424'
'WSDL encourages the creation of modular and reusable service descriptions. Developers can design services in a way that promotes consistency and reduces redundancy, leading to more maintainable and efficient systems. WSDL has adopted the "+xml" convention that is described in the IETF RFC 3023 defining XML data types and its security considerations. As an XML document, every implementation can have different security requirements. As an example of implementation is the SELIS project, which aims to make available a web services regarding the eInvoicing. This topic is included within the Once-only Principle and Digital Single Market frameworks. SELIS Documentation: https://joinup.ec.europa.eu/collection/eprocurement/document/secure-electronic-invoicing-service-selis W3C WSDL specification: https://www.w3.org/TR/wsdl20/ WSDL IETF 3023: https://www.w3.org/TR/wsdl20/#RFC3023 '
'Linked Data Event Streams (LDES) itself is a conceptual framework and a set of principles for representing and publishing real-time event data using Linked Data on the web. While LDES is designed to be conceptually technology-agnostic, the practical implementation details may involve specific technologies to realise the principles and standards it advocates. LDES specification: https://joinup.ec.europa.eu/collection/semic-support-centre/linked-data-event-streams-ldes'
XSD 1.1 is maintained by W3C which is an international community developing open standards. See: https://www.w3.org/Consortium/ https://www.w3.org/TR/xmlschema11-1/ https://www.w3.org/TR/xmlschema11-2/
After checking the different standard catalogues at supra-national level, there is no evidence of the inclusion of CPOV within any European catalogue of standards. ICT technical specifications: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en
The purpose of the specification is not related to the availability of interfaces with internal information systems. Therefore, this criterion does not apply to this specification. XACML OASIS reference: http://docs.oasis-open.org/xacml/3.0/errata01/xacml-3.0-core-spec-errata01.html
'DQV promotes transparency in data publishing by providing standardised metadata about data quality. When applied to public administration services, DQV can enhance transparency and accountability by making the quality of data used in service interfaces more visible to stakeholders, including service users, regulators, and auditors. This transparency fosters trust in public administration services and encourages responsible data management practices. Data Quality Vocabulary: https://www.w3.org/TR/vocab-dqv/'
Even PDF is supporting the first level of maturity from the Tim Berners Lee 5-stars schema for the Open data, it is not supporting the main principles for the publication of data as Linked Open Data. See: https://www.w3.org/wiki/LinkedData https://5stardata.info/es/
'The purpose of FTP is not related to long term preservation of electronic records. Therefore this criterion is considered not applicable to this specification. FTP Specification Reference: https://datatracker.ietf.org/doc/html/rfc959'
'UDDI allows implementations that can work with different programs like python or Java. Some of these are UDDI::Lite and UDDI4r. Tutorialspoint UDDI reference: https://www.tutorialspoint.com/uddi/uddi_implementations.htm'
'REST specification conformance can be manually assessed by following its architectural constraints to help in obtaining a uniform interface and guiding the behaviour of components. No conformance testing platform has been found, however, there are accessible assessment online guides. REST reference: https://restfulapi.net/rest-architectural-constraints/ '
'Verifiable Credentials explicitly adresses and enables data portability between systems/applications supporting the implementation or evolution of European public services by providing them with the means to issue, manage and verify fraud-proof credentials efficiently and securely and for users to maintain greater privacy and control over their personal data. Verifiable Credentials: https://www.w3.org/TR/vc-data-model/'
W3C has a defined and publicly available Process for the Development and approval process of the specification as a recommended standard. Also, a clear Release Notes tracking the changes of the different versions is archived. W3C Process document https://www.w3.org/2018/Process-20180201/#Policies
Better Regulation Toolbox includes references to the relevance Open Data for the development of public policies. It is one of the principles or basis for the evidence-based development that the specification defines, however, the purpose of the specification is not related to the development and publication of Linked Open Data. Betterr Regulation Toolbox reference: https://ec.europa.eu/info/sites/info/files/better-regulation-toolbox_2.pdf 5-star linked open data: https://www.w3.org/DesignIssues/LinkedData.html
'ShEx allows for partial implementations in the sense that its functionalities can be invoked separately. For instance, it can be only used for serializing RDF data into JSON format, or into a concise human-readable compact syntax (ShExC), or it can only be used to validate RDF graphs. ShEx primer document: https://shexspec.github.io/primer/ ShEx Community Group: https://www.w3.org/community/shex/ ShEx Github: https://github.com/shexSpec/spec/issues'
FTPS was first published as a draft RFC in 1996, but the RFC was not finished until 2005. Since then, many implementations using FTPS have been done to secure FTP, which it proves that it is mature enough for the development of products and services. FTPS IETF reference: https://tools.ietf.org/html/rfc4217
XAdES (ISO 14533-2:2012) is not included in any Member States' catalogues of recommended specifications. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
"The specification's community is an active and growing community of individuals and organizations who are interested in the use and development of the Akoma Ntoso standard. It also has the support of the XML community as the AKN4EU specification is based on the XML. AKN4EU reference: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/akn4eu"
The specification has the support of European Member States developing e-Law solutions at national and European Solutions. ELI is within the focus of ISA2, which aims to fund and improve interoperability solutions across Europe. The Publications Office is also supporting implementations of ELI and the shareability of dedicated data sets. ELI reference: https://eur-lex.europa.eu/eli-register/about.html EU Open Data portal: https://data.europa.eu/euodp/en/data/group/eli?groups=eli ISA2 and ELI: https://ec.europa.eu/isa2/news/eli-and-eli-dl-greater-interoperability-legislation_en
"TGF provides guidance and best practices for designing and implementing digital service delivery channels that are aligned with citizens' needs and preferences, and that promote efficiency, transparency, and accessibility in government service delivery. TGF specification: http://docs.oasis-open.org/tgf/TGF/v2.0/cs01/TGF-v2.0-cs01.html"
Since the specification has been developed by European Institutions for its implementation across borders to increase interoperability, it can be considered that it is legally compliant. Moreover, the ELI is a key aspect to ensure the development and transposition of European legislation into National Laws and vice versa, helping to standardise regulation creation and development across the European territory. ELI reference: https://eur-lex.europa.eu/eli-register/about.html ELI Testimonials: https://eur-lex.europa.eu/eli-register/testimonials.html ELI highlights: https://eur-lex.europa.eu/eli-register/index.html
'TSP is developed and maintained by IETF, a widely recognised open international community developing standards to enhance the internet. IETF Reference: https://www.ietf.org/ TSP IETF reference: https://tools.ietf.org/html/rfc3161'
'ETSI TS 119 612 defines how digital certificates and public-key infrastructures (PKIs) are used in the authentication process, which inherently includes mechanisms for ensuring that access is only granted to entities possessing valid credentials. ETSI TS 119 612: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf'
'The Extensible Forms Description Language specification has been published and is maintained by the World Wide Web Consortium (W3C). Moreover, there is a discontinued GitHub page for XFDL. Discontinued Github page for XFDL: https://w3c.github.io/Unitas/?s=XFDL&v=19980902 Extensible Forms Description Language reference: https://www.w3.org/TR/NOTE-XFDL'
'DNS queries over HTTPS (DoH) is developed by IETF, a standard development organisation based in the US. Moreover, the DNS queries over HTTPS (DoH) specification does not appear in any of the main European standard development bodies, therefore, the specification is not a European standard. DoH specification: https://datatracker.ietf.org/doc/html/rfc8484'
'The FTP is used in the context of the CIRCABC, a cross-border initiative that provides a web application enabling collaboration, communication and document exchange between European Union stakeholders. CIRCABC isa2 Reference: https://ec.europa.eu/isa2/sites/isa/files/circabc.pdf CIRCABC Reference: https://circabc.europa.eu/faces/jsp/extension/wai/navigation/container.jsp'
'The purpose of CSV is not related to the delivery of multilingual public services. Therefore, this criterion is not applicable to the specification. CSV reference: https://datatracker.ietf.org/doc/html/rfc4180'
'The specification is not related to the publication of public data as open data. Therefore this criterion is not applicable to this specification. ETSI EN 319 422 reference: https://www.etsi.org/deliver/etsi_en/319400_319499/319422/01.01.01_60/en_319422v010101p.pdf'
'DNS over HTTPS (DoH) is a protocol that encrypts DNS queries and their responses to enhance privacy and security, therefore it is not directly related to the publication of data on the web. DoH specification: https://datatracker.ietf.org/doc/html/rfc8484'
"The specification is included in 1 Member State' catalogue of recommended specifications. This Member State is Spain. National catalogue Spain: https://administracionelectronica.gob.es/pae_Home/dam/jcr:9e2c2877-5103-4934-8440-c60ba2e10c48 /Catalogue_of_Standards_NIF_Spain.pdf CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards"
"The Credentials Community Group's mission is to explore the creation, storage, presentation, verification, and user control of credentials. They focus on a verifiable credential (a set of claims) created by an issuer about a subject—a person, group, or thing—and seek solutions inclusive of approaches such as: self-sovereign identity; presentation of proofs by the bearer; data minimization; and centralized, federated, and decentralized registry and identity systems. Their tasks include drafting and incubating Internet specifications for further standardization and prototyping and testing reference implementations. Credentials Community Group: https://www.w3.org/community/credentials/"
"W3C Verifiable Credentials' first public working draft was published in 2017. Since then, one major release has been published and several minor changes have been recommended. In addition, different documentation on its supporting processes has been published to ensure the correct change and release of its content. Therefore, this specification has been evolved enough and mechanisms for its development have been put in place. W3C Recommendation Track: https://www.w3.org/2021/Process-20211102/#rec-track General Requirements for Technical Reports: https://www.w3.org/2021/Process-20211102/#recs-and-notes"
'Several developer platforms discuss YAML extensively, one prominent example being Stack Overflow. Stack Overflow operates as a community-driven forum where developers can ask questions, share insights, and provide solutions related to YAML. Stackoverflow YAML: https://stackoverflow.com/questions/tagged/yaml'
'Although designed for use in business supply chains it can be (and has been) adapted for other contexts of use. This is because all the business document constructs in a UBL are drawn from a single library of reusable components. Therefore, UBL can be implemented across business domains. UBL v2.3 reference: http://docs.oasis-open.org/ubl/os-UBL-2.3/UBL-2.3.html Developer community OASIS. UBL functionalities: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ubl#functionality'
HTML5 is not included in any catalogue of standards at supra-national level. However, it can be found within the European Colaborative platform, Joinup along with other extensions and versions of the specification. See: https://joinup.ec.europa.eu/search?keys=HTML5&f%5B0%5D=type%3Asolution&page=0
'RDF provides the means to describe data in a highly expressive way. By enablig data integration from multiple sources, RDF allows multiple schemas to be applied, interlinked and queried as one, and modified withut changing the data instances, thus enabling digital service delivery channels. RDF Description services: https://www.w3.org/1999/11/02-RDFServices/'
'The DCAT vocabulary has a strong support from the interest groups and is extensively used by public administrations’ for the exchange of data across borders and sectors. The specification also counts with a major release (v3.0.0) to further support the argument. Additionally, the specification is widely used by public administrations profiling or extending it to fit domain-specific or national requirements - DCAT-AP: Application Profile for Public Sector Datasets. - DCAT-AP-BE: Extension of DCAT-AP for Belgium specific requirements. - StatDCAT-AP: Extension of DCAT-AP for the publication of statistical data. DCAT (v2.0.0) reference: https://www.w3.org/TR/vocab-dcat-2/'
'FTP is included in 8 national catalogues of recommended specifications. Among those we can find the Netherlands. The National Interoperability Framework (NIF) of these Member States is fully aligned with at least 2 out of 3 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. NIFO factsheets: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public-administration-factsheets-2022 CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards Netherlands NIFO Factsheets: https://joinup.ec.europa.eu/sites/default/files/inline-files/DPA_Factsheets_2022_Netherlands_vFinal_0.pdf'
SAMM aims to help organizations analyse their current software security practices. By following and implementing SAMM European Institutions can improve and develop software that allows data portability ensuring maximum security on these information transactions. SAMM webpage: https://owaspsamm.org/ SAMM Documentation: https://github.com/OWASP/samm/blob/master/Supporting%20Resources/v2.0/OWASP-SAMM-v2.0.pdf
'The message returned by a Service Metadata Publisher service is signed using one or more XML-Signatures. Moreover, the purpose of the specification is to ease and ensure the discoverability of different parties to exchange the desired information. The specification defines a set of requirements regarding the authentication of parties that ensures secure and trustworthy data exchange. SMP OASIS reference: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505009'
'AMQP specification enables a secure processing of data through security layers like TLS and SASL are employed to ensure authenticated and encrypted transport, which can be combined for enhanced security. OASIS AMQP Reference: http://docs.oasis-open.org/amqp/core/v1.0/amqp-core-complete-v1.0.pdf'
'When it comes to the preservation mechanisms, ETSI TS 119 512 specifies a data structure "EvidenceExchange", which contains preservation objects and preservation evidences to support seamless export and import from one preservation service to another one using evidence records, therefore enhancing interoperability between systems and ensuring data portability. ETSI TS 119 512 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.02_60/ts_119512v010102p.pdf '
'HTTPS is not related to data accuracy. Therefore this criterion is not applicable to the specification. HTTPS specification: https://tools.ietf.org/html/rfc2818'
"ISAE 3402 is part of the International Federation of Accountants (IFAC) standard providing companies in the financial sector with an independent assessment tool on user entities' controls over financial reporting. The ISAE 3402 auditing tool, therefore, it does not allow customisation. ISAE 3402 handbook reference: https://www.ifac.org/system/files/downloads/b014-2010-iaasb-handbook-isae-3402.pdf"
'In the REST architectural style, data and functionality are considered resources and are accessed using Uniform Resource Identifiers (URIs). With a REST protocol you can do the following operations with data POST (creation), GET, PUT, DELETE. Thus, in some way, it facilitates the publication of public data as open data. REST reference: https://restfulapi.net/ See this link for the justification: https://www.bbvaapimarket.com/es/mundo-api/api-rest-que-es-y-cuales-son-sus-ventajas-en-el-desarrollo-de-proyectos/ The 5-star of Tim Berners-Lee can be found in the following link: https://5stardata.info/en/ '
Consensus is a foundation upon which the Alliance is built and all processes and procedures, particularly in connection to the focus, work plans, deliverables, milestones and tangible specifications / recommendations are consensus based.
'The XACML specification significantly enhances the secure processing of data through its comprehensive access control framework. By enabling context-aware policies, XACML ensures that data processing operations are conducted securely. XACML OASIS reference: https://docs.oasis-open.org/xacml/3.0/xacml-3.0-core-spec-os-en.html'
'The ETSI and any of its committees, in charge of the development of ETSI TS 119 614-1, operate under the ETSI Intellectual Property Rights (IPRs) and IPR Policy. The specification is licensed on a (F)RAND basis. Intellectual Property Rights Policy, ETSI ownership of IPRs section: https://www.etsi.org/intellectual-property-rights'
'The specification can be found, for instance, in one site at national level in Poland. It is present at different levels, the site includes information related to the new releases, access to them, new courses, etc. In general terms, EIRA is present at national level in Poland. Portal Gov: https://www.gov.pl/web/ia/czym-jest-eira-nowy-kurs-online-w-akademii-interoperacyjnosci EIRA reference: https://interoperable-europe.ec.europa.eu/collection/european-interoperability-reference-architecture-eira /solution/eira/release/610 EIRA Github Repository: https://github.com/CarTool-EC/EIRA'
"The purpose of LDAP is not related to the exposure of interfaces to access the public administration's services. Therefore, this criterion is not applicable to this specification. LDAP IETF reference: https://tools.ietf.org/html/rfc4511 "
The Semantic Interoperability Community (SEMIC) has established Working Groups. These Working Groups are open to the participation of everyone interested in semantic solution working for public administrations in the Member States or in EU institutions. SEMIC working groups: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/about
The application of the once-only principle in all EU Member States public administrations aims at reducing the administrative burden. EuroVoc fosters interoperability between public administrations, cross border services and impacts positively the development of eGovernment. EuroVoc webpage: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/eurovoc
The main purpose of SVG is to exchange and represent graphical information over the internet. Its compatibility with XML, CSS and other transformation elements like XSLT, allows the data portability of the information contained in SVG files. Also, it can represent graphical content from simple XML inputs. SVG W3C reference: https://www.w3.org/TR/SVG11/ SVG and XSL: https://www.w3.org/People/maxf/papers/2002-07-SVGOpen/svgopen.html#id2590005
"No evidence has been found that ISAE 3402 is recommended by any European Member State's Catalogue. CAMSS list of standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specificationscamss /camss-list-standards"
The self-assessment model allows users to manage the development and deployment of software and adapt the actions to each specific purpose targeting depending on the organisation's needs. This fact helps public administrations to create and implement secure digital public services without wasting time and means. Moreover, the creation of secure digital public services fosters the eGovernment and the digitalisation reducing administrative burden. SAMM webpage: https://owaspsamm.org SAMM documentation: https://github.com/OWASP/samm/blob/master/Supporting%20Resources/v2.0/OWASP-SAMM-v2.0.pdf
The first version of the specification was released back in 2009 and has been maintained and evolved on a community-driven basis until achieving version 2.0 released in 2020. The evolution of the specification involves a wide range of technical profiles and experience in the field of this specification. Through continuous improvement and discussion the specification has been released late in 2020 but with a cured development ensuring the maturity of the specification. SAMM webpage: https://owaspsamm.org/ SAMM documentation: https://github.com/OWASP/samm/blob/master/Supporting%20Resources/v2.0/OWASP-SAMM-v2.0.pdf
'The SEMIC Support Center is responsible for the development of the specification. They are in charge of its maintenance, implementation pilots, knowledge sharing and, strategy and roadmap. SEMIC in Joinup: https://joinup.ec.europa.eu/collection/semic-support-centre'
'Time-Stamp Protocol (TSP) was defined in 2001 and is a cryptographic protocol for certifying timestamps using X.509 certificates and public key infrastructure. Moreover the IETF has published all documentation about TSP in the web. Therefore, it is demonstrated that TSP has enough maturity for its use in the development of products and services. TSP IETF reference: https://tools.ietf.org/html/rfc3161'
'The specification has an holistic perspective that goes from Legal to Technical aspects following the LOST approach from the European Interoperability Framework (EIF). This implies that EIRA can help Public Administrations to analyse and design digital public services that considers interoperability across views as requirements and also specifically the reuse of relevant information. The EIRA can help also with the use-centric approach from design, as it can help to establish the precise requirements that could later on extended by eGovERA and solutions focused on guaranteeing that users do not need to provide additional information. EIRA reference: https://interoperable-europe.ec.europa.eu/collection/european-interoperability-reference-architecture-eira /solution/eira/release/610 EIRA Github Repository: https://github.com/CarTool-EC/EIRA'
'ETSI TS 119 512 is not related to multilingualism. Therefore this criterion is not applicable to this specification. ETSI TS 119 512 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.02_60/ts_119512v010102p.pdf'
'HTTP Cookies provides a way of addressing the secure and trustworthy processing of data by adding the "httpOnly" attribute to prevent access to Cookies via JavaScript, or by setting the "SameSite" attribute to "strict" when it is necessary to authenticate sensitive information from the user. In browsers that support SameSite, this ensures that the authentication cookie isn't sent with cross-site requests. HTTP Cookies security reference: https://datatracker.ietf.org/doc/html/rfc6265#section-8'
'The purpose of DPV is not related to data integrity, therefore, this criterion is not applicable to the specification. DPV specification: https://w3c.github.io/dpv/primer/'
The Better regulation toolbox is an internal European Commission resource designed as a complement to the Commission's Better regulation guideline. It provides more specific and operational guidance to those involved with the various better regulation instruments. By allowing to make the data available to other persons or organisations, the Betterr Regulation Toolbox Contributes to the development of eGovernment reducing the administrative burden. Betterr Regulation Toolbox reference: https://ec.europa.eu/info/sites/info/files/better-regulation-toolbox_2.pdf
'There has not been found any European cross-border project using the TGF. TGF specification: http://docs.oasis-open.org/tgf/TGF/v2.0/cs01/TGF-v2.0-cs01.html'
'The specification defines a profile for the time-stamping protocol and the time-stamp token defined in IETF RFC 3161. It defines what a time-stamping client supports and what a time-stamping server supports. Time-stamp validation is out of scope and is defined in ETSI EN 319 102. ETSI EN 319 422 reference: https://www.etsi.org/deliver/etsi_en/319400_319499/319422/01.01.01_60/en_319422v010101p.pdf'
'The specification itself does not inherently provide any built-in mechanisms for ensuring the protection of personal data managed by Public Administrations. CSV is a simple, plain text format primarily designed for storing and exchanging tabular data. CSV reference: https://datatracker.ietf.org/doc/html/rfc4180'
HTML is maintained by W3C which is an international community developing open standards. Developer community W3C: https://www.w3.org/Consortium/
Douglas Crockford was the creator of JSON. The system was sold to Sun Microsystems, Amazon.com and EDS. The website of the specification was launched in 2002. JSON reuses conventions from other programming languages, in consequence, many libraries of programming use it. Therefore, it is demonstrated that JSON has enough maturity and market acceptance for its use in the development of products and services. See: https://www.json.org/json-en.html
XAdES Baseline Profile is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). Specifically, ASiC Baseline Profile can define the interoperability aspects of “e-Seal Creation Service”, “e- Verification Seal and Validation Service”, “e-Signature Creation Service”, and “e-signature Verification and Validation Service” ABBs of the EIRA Technical View. See: https://joinup.ec.europa.eu/solution/elis/distribution/eliscataloguev100betaxlsx
SOAP 1.2 is maintained by W3C which is an international community developing open standards. See: https://www.w3.org/Consortium/
'ETSI TS 119 612 specifies a format and mechanisms for establishing, locating, accessing and authenticating a trusted list which makes available trust service status information so that interested parties may determine the status of a listed trust service at a given time as well as enabling data portability between systems/applications. It defines the format and semantics of a TL as well as the mechanisms for accessing TLs. It also provides guidance for locating and authenticating TLs. ETSI TS 119 612 specification: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf '
When HTML 4 became a W3C recommendation it had a good acceptance, it was the best markup language in the market, but when XHTML and HTML5 appeared, its use decreased considerably. It can be seen in the following link, a comparison of usage of the different HTML languages and it is obvious that HTML 4 is near 0% of usage. XHTML trend: https://try.powermapper.com/Stats/HtmlVersions
'LDAP can be used independently of any other technical specifications. As a network protocol, it can be implemented in any type of domain. For instance, it is widely used to complement Active Directory (AD) as a directory services protocol. LDAP IETF reference: https://tools.ietf.org/html/rfc4511 LDAP with Active Directory: https://www.solarwindsmsp.com/blog/difference-between-ldap-ad'
'The AKN4EU specification itself does not provide inherent mechanisms to protect information against unauthorized changes. However, several measures can be implemented to protect information integrity and guard against unauthorized modifications when utilizing the specification. AKN4EU reference: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/akn4eu'
"While SCIM's primary focus is on the exchange of identity-related data, it can indirectly contribute to organisational interoperability agreements.For instance, SCIM provides a standardised protocol that helps ensure that different systems, even from different organizations, can understand and process identity data in a consistent manner. Furthermore, by adhering to SCIM, organizations can establish interoperable identity management practices and ensure consistency across systems. SCIM: https://scim.cloud/"
SAML 2.0 can be used independently from any other technical specifications or operating system. The specification has been developed by OASIS Security Services Technical Committee independently from any specific platforms or technologies. Even though SAML 2.0 is XML based specifications, as XML is a well-known specification it does not cause technological dependency. See: https://developers.onelogin.com/saml http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-tech-overview-2.0.html
The purpose of the specification is not related to fostering multilingualism. Therefore, e-Delivery SMP 1.10 is not related to multilingualism.
CAdES is a business domain agnostic specification that can be reused in a cross-domain way. It can apply to any type of transaction, between an individual and a company, between two companies, between an individual and a governmental body, etc. CAdES ISO reference: https://www.iso.org/standard/64756.html CAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/101700_101799/101733/02.01.01_60/ts_101733v020101p.pdf
'UTF-8 supports many languages and can accommodate pages and forms in different cases including a mixture of these languages. The fact of allowing encoding with several languages allows the data consumption by the different linguistic groups that form the EU. Therefore, UTF-8 fosters the delivery of European multilingual services. Choosing and applying character encoding: https://www.w3.org/International/questions/qa-choosing-encodings.en UTF-8 specification: https://datatracker.ietf.org/doc/html/rfc3629'
'The XSLT specification is designed to transform data from XML into other formats, making it useful for handling administrative data. For example, XSLT is used to convert into RDF Tenders European Daily XML dumps documents. TED extractor Project: https://github.com/opendatacz/TED_extractor/tree/master XSLT Reference: https://www.w3.org/TR/xslt-30/#json-in-xml'
'DAPS is being directly used to create various innovative solutions. For instance, the specification plays a crucial role in Catena X, an initiative that aims to create a uniform standard for the data exchange across the entire automotive value chain. The Catena-X role of a company requesting some specific data is a foundation for the decision whether the requesting company is allowed to consume this specific data. DAPS is the component which is responsible for the distribution of the described company attributes by issuing certificates including the attributes as well as the company identity to the EDCs, which are representing the companies. Catena-X: https://catena-x.net/en/about-us'
'Section 1.4 of the OAIS specification states that, although the archive has to support OAIS information model (section 2.2), the same does not define or require any particular method of implementation of the concepts. Moreover, to be conformant with OAIS, all the responsibilities defined by the section 3.1 have to be fulfilled, Nonetheless, there can be found some tools that help to assess archiving systems conformity to OAIS, but this is a ""proposed measurement"" not an official one. OAIS functional model conformance test: a proposed measurement: https://www.emerald.com/insight/content/doi/10.1108/00330331211244850/full/html OAIS specification: https://public.ccsds.org/Pubs/650x0m2.pdf'
"LDAP has various authentication methods to prevent from hostile agents. SASL is an example which supports a variety of authentication mechanisms. However, with the bing system that LDAP have, it insn't necessary to implement any implementation to guarantee the authentication. LDAP Authentication methods and security mechanisms: https://www.rfc-editor.org/rfc/rfc4513.txt"
UTF-8 is a sector agnostic specification which means that can be used in any business domain requiring data encoding.
'WSDL is included IN 10 national catalogues of recommended specifications. They belong to Bulgaria, Cyprus, France, Germany, Greece, Malta, Netherlands, Portugal, Spain and Sweden. The National Interoperability Framework (NIF) of these Member States is fully aligned with at least 2 out of 3 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. NIFO Factsheets: https://joinup.ec.europa.eu/collection/national-interoperability-framework-observatory-nifo/nifo-factsheets CAMSS List of standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
'UBL is the product of an open and accountable OASIS Technical Committee with participation from a variety of international and industry data standards organizations. It was originally approved as an OASIS standard in 2004 and is among the most mature and widely implemented OASIS Standards. In 2014 the European Commission declared UBL 2.1 officially eligible for referencing in tenders from public administrations and in 2015 UBL 2.1 was also approved as ISO/IEC 19845:2015, establishing UBL as a true international standard for use by governmental bodies globally. With this endorsement, UBL has reached the maximum level of sanction possible for an international standard. The current version, UBL 2.3, was approved in 2021. Developer community OASIS. UBL functionalities: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ubl#sanction'
'The specification explicitly addresses data protection and its alignment to relevant regulations. There are details available about the general privacy considerations and specific privacy implications of deploying the Verifiable Credentials Data Model into production environments. Verifiable Credentials Privacy Considerations: https://www.w3.org/TR/vc-data-model/#privacy-considerations'
'The purpose of the specification is to facilitate the exchange of structured data. By allowing to make the data available to other persons or organisations, this Core Vocabulary reduces the administrative burden and enables digital service delivery channels. CPSV-AP Joinup webpage: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/core-public-service-vocabulary-application-profile/release/22'
'OData offers a way to both break down data silos and increase the shared value of data (see Joinup reference). The specification contributes creating an ecosystem where data consumers and producers can interoperate more than ever, allowing more applications to make sense of a broader set of data. In this sense, the specification promotes visibility, for example through the OData data model. However, no evidence was found in terms of promoting and supporting the internal nor the external visibility of European public services. Joinup OASIS Open Data Protocol reference: https://joinup.ec.europa.eu/collection/ict-standards-procurement/solution/odp-oasis-open-data-protocol-odata-tc/about'
'As of now, the Asset Administration Shell (AAS) is not an european standard. Details of the Asset Administration Shell (AAS) https://industrialdigitaltwin.org/en/wp-content/uploads/sites/2/2024/06/IDTA-01001-3-0-1_SpecificationAssetAdministrationShell_Part1_Metamodel.pdf'
'There are no Member States recommending EuroVoc in their ICT National Catalogues. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards'
'The effectiveness of WAI-ARIA involves various methods, such as usability studies, user testing, and evaluation against established accessibility standards. As the specification undergoes evaluation, numerous cases and studies investigate its utilization in web content for e-accessibility purposes. NSU article about WAI-ARIA solutions: https://www.nosolousabilidad.com/articulos/wai_aria.htm ACM Digital Library WAI-ARIA reference: https://dl.acm.org/doi/abs/10.1145/2461121.2461141 WAI-ARIA reference: https://www.w3.org/TR/wai-aria/'
'Registered Organization Vocabulary can facilitate the modeling of business procesess by describing the characteristics and registration details of legal entities to ease data exchange between business registers. Registered Organization Vocabulary specification reference: https://www.w3.org/TR/vocab-regorg/'
WS-Security is an extension of SOAP specification to improve the security web services, so it is dependant on it.
'The specification has been selected as one of the key elements for the data interchange between administrations and stakeholders. Europeana is using JSON within the Search API, the method created to diving into the european cross-border project data. These features allow retrieving information from EUROPEANA. Moreover, the Single Electronic Data Interchange Area (SEDIA) is using JSON as the basis to make data available for stakeholders. Examples SEDIA activity is the Call for Tenders, a key point on European eProcurement. Additionally, the EU Open Data Portal is another cross-border initiative that relies on JSON as a message format for API’s communication. EUROPEANA website: https://pro.europeana.eu/resources/apis/search SEDIA website: https://ec.europa.eu/info/funding-tenders/opportunities/portal/screen/support/apis EU Open data portal: http://data.europa.eu/euodp/en/data/dataset/eu-open-data-portal-api" '
'According to the 5 star Open Data model suggested by Tim Berners-Lee about how to publish linked data, the first star corresponds to the publication of data under an open license. OCSP generally uses open source protocol syntax when determining the status of a digital certificate, such as HTTP and SMTP. OCSP reference, section 2: https://datatracker.ietf.org/doc/html/rfc2560 Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/en/'
Although at the moment of elaborating the assessment the specification is widely used, the specification in itself does not give any innovative solution that can be part of an innovative cutting edge solution. MIME reference: https://tools.ietf.org/html/rfc2045
'As specification to structure data in order to allow the maximum interoperability between systems, RDF fosters the data portability between administrations at the same time that helps to enhance data discoverability and enabling the cross-data set queries using SPARQL. Specifically, RDF helps data portability and exchange between databases. The serialisation of RFD has several forms that ensure the availability of data, thus, supporting the implementation and evolution of European Public Services. RDF primer document: https://www.w3.org/TR/rdf11-primer/'
'Yes, the specification can enable digital service delivery channels. By providing a common, interoperable data format, it can help facilitate the exchange of information between different systems and applications supporting the implementation of European public services, including those delivered through digital channels in the legal domain. AKN4EU reference: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/akn4eu'
Ogg has a good market acceptance. The online news portal Tagesschau was awarded for making all its video entries available in the open format Ogg. A few countries recommend Ogg as an open source multimedia container. Tagesschau awarded for Ogg: https://joinup.ec.europa.eu/collection/open-source-observatory-osor/news/former-german-justice-ministe Ogg XIPH reference: https://xiph.org/ogg/doc/rfc3533.txt
'Althought eh specification is not used a t EU level, the specification is used in the European Materials Modeling Ontology (EMMO) created by the European Materials Modelling Council (EMMC). EMMO reference: https://emmc.eu/'
'The application of the once-only principle in all EU Member States public administrations aims at reducing the administrative burden. To achieve this, interoperability between public administrations is a sine qua non condition. In this sense, ShEx addresses and facilitates interoperability between public administrations, and cross border services and impacts positively the development of eGovernment. This is because of the fact that it has been designed to enhance the semantic and technical interoperability layers of ontologies expressed as RDF graphs, and RDF is a European Standard used by public administrations in projects for sharing Linked Data. ShEx primer document: https://shexspec.github.io/primer/ ShEx Community Group: https://www.w3.org/community/shex/ ShEx Github: https://github.com/shexSpec/spec/issues '
'OpenTelemetry’s design allows for flexible, partial implementations, making it highly adaptable to varying organizational needs and constraints. Its modular architecture, pluggable exporters, incremental instrumentation capabilities, configurable sampling strategies, and interoperability with existing systems all support the ability to adopt OpenTelemetry gradually. OpenTelemetry: https://opentelemetry.netlify.app/docs/specs/otel/'
'The PROV family of documents allows for customization, enabling organizations or systems to tailor the PROV specifications to their specific requirements and domain-specific needs. For example, organizations can create domain-specific extensions to the PROV Data Model or define custom attributes to capture additional metadata or domain-specific information in their provenance representation. PROV Primer document: https://www.w3.org/TR/prov-primer/'
'ISAE 3402 is focused on the preservation of confidential data and its availability. Therefore this criterion is not applicable to this specification. ISAE 3402 handbook reference: https://www.ifac.org/system/files/downloads/b014-2010-iaasb-handbook-isae-3402.pdf'
'While DQV itself does not directly enable the visibility of administrative procedures, rules data, and services, it plays a crucial role in promoting transparency, interoperability, and quality assessment by providing an standardised metadata about data quality, which can indirectly contribute to their visibility and usability in the context of data publishing and sharing. Data Quality Vocabulary: https://www.w3.org/TR/vocab-dqv/'
'Syslog focuses on the transmission and reception of log messages and does not inherently provide built-in mechanisms for secure processing of data. Syslog Protocol: https://datatracker.ietf.org/doc/html/rfc5424'
'There are studies assessing the specification in terms of efficiency and can be checked in the following links: https://link.springer.com/article/10.1007/s10791-006-9008-2 https://link.springer.com/chapter/10.1007/978-3-642-04205-8_6'
There are many documents that provide an overview of the usage and functionalities of MIME. In some cases it is compared with the STMP, showing the strengths and weaknesses. Documentation about MIME: https://www.geeksforgeeks.org/multipurpose-internet-mail-extension-mime-protocol/
'ETSI TS 119 512 can be found on the specifications and standards repository of its own standards development organization, the European Telecommunication Standards Institute (ETSI). ETSI standards repository: https://www.etsi.org/committee/1399-esi'
'The XACML specification provides a thorough and detailed framework that supports comprehensive and transparent management of access control policies, ensuring that administrative procedures, rules data, and services are all robustly covered. XACML OASIS reference: https://docs.oasis-open.org/xacml/3.0/xacml-3.0-core-spec-os-en.html'
'SCIM is included in the Rolling Plan for ICT standardisation of 2023 by the European Commission. Specifically, it mentioned in the Cloud and Edge Computing Rolling Plan, which aims to establish a coherent framework and conditions for cloud computing in Europe. Cloud and Edge Computing Rolling Plan 2023: https://joinup.ec.europa.eu/collection/rolling-plan-ict-standardisation/cloud-and-edge-computing-rp-2023'
The standard or specification is included in 2 national catalogues that belong to Member States which comply with at least 4 out of 5 sections of the EIF according to the NIFO factsheets. (e.g. the Netherlands, Sweden) See: https://www.forumstandaardisatie.nl/open-standaarden/lijst http://www.avropa.se/dynamiska-sidor/sok/?query=standards&searchtype=web
'There is no Member State that includes the EN 303 645 specification in their national catalogue with The National Interoperability Framework (NIF) in alignment with the three categories: 1. Conceptual model for integrated public services provision, 2. interoperability layers, and 3. interoperability principles. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
"There are different kind of assessments evaluating the schema.org specification. However, these evaluations indirectly address the specification's effectiveness or may focus on the phases prior to the development of digital solutions, what makes them hard to find. Check bibliographical platforms or research centres, such as ResearchGate (see Europeana Foundation and INESC-ID joint research reference) or the Joint Research Centre of the European Commission (JRC) (see JRC publications repository reference, 'Application Programming Interfaces in Governments' document). Europeana Foundation and INESC-ID joint research reference: https://www.researchgate.net/profile/Nuno-Freire-2/publication/325529501_Evaluation_of_Schemaorg_for_Aggregation_of_Cultural_Heritage_Metadata/links/5b22540da6fdcc69745ee712/Evaluation-of-Schemaorg-for-Aggregation-of-Cultural-Heritage-Metadata.pdf JRC publications repository reference, 'Application Programming Interfaces in Governments' document: https://publications.jrc.ec.europa.eu/repository/handle/JRC120429"
'DNS is a hierarchical and decentralized naming system used to identify computers reachable through the Internet or other Internet Protocol (IP) networks. For that matter it can be implemented in any domain. DNS IETF reference: https://tools.ietf.org/html/1034 Domain Names - Implementation and Specification: https://tools.ietf.org/html/1035 '
'ESPD is a modular document that consists of several sections, each of which covers a specific area of information related to the procurement process. Contracting authorities can choose which sections of the ESPD are relevant to their procurement process and request that suppliers provide the corresponding information, therefore allowing for partial implementations. ESPD Business handbook: https://docs.ted.europa.eu/ESPD-EDM/latest/xml_business_handbook.html'
'According to the Principle 3.5 of the E-ARK CSIP specification, the structure information packages must explicitly define the possibilities for adding additional components into the information package, therefore, allowing for extensions. E-ARK CSIP specification: https://earkcsip.dilcis.eu/#introduction'
'TSP can be implemented in any platform and it is independent of any technology. TSP IETF reference: https://tools.ietf.org/html/rfc3161'
'XSLT does not inherently provide secure exchange of data, secure data exchange can be achieved by integrating XSLT with other technologies and best practices, such as XML Signature, allowing to digitally sign XML data, ensuring the integrity and authenticity of the information. XML Signature Reference: https://www.w3.org/TR/xmldsig-core1/ XSLT Reference: https://www.w3.org/TR/xslt-30 '
'IEEE Std 802.3-2022 is a detailed specification for Ethernet networking. It supports various applications, from local area networks (LANs) to high-speed data centres, making it versatile for digital solutions. The standard includes detailed documentation about change management processes, including erratum and a list of versions, providing a robust foundation for current and future networking needs. IEEE Std 802.3-2022 Reference: https://ieeexplore.ieee.org/document/9844436'
8 Member States are recommending TIFF in their ICT National Catalogues. This Member States are Estonia, France, Germany, Greece, Norway, Poland, Slovenia and Spain. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'The purpose of Indexed Database API is not related to secure processing of data. Therefore, this criterion is not applicable to the specification. Indexed Database API: https://www.w3.org/TR/IndexedDB/'
"This Technical Specification (TS) has been produced by ETSI Technical Committee Electronic Signatures and Trust Infrastructures (ESI). There are two paths to get involved in ETSI's Industry Specification Groups (ISG): as an ETSI member, or as a direct participant. The participation in the technical group is reserved to ETSI members, who require registration, fees, and membership approval. Organisations who are not members of ETSI may still participate in the ISG, attend meetings, subscribe to the e-mail lists and help build the specifications by making technical contributions. They do not have voting rights and must pay a participation fee per person per meeting day to attend ISG meetings. ETSI Technical Committee ESI: https://www.etsi.org/committee/esi"
'Although the specification does not directly specify the sharing of results and data on European platforms, it is free and open for everyone to check their information and results, and join the community through GraphQL Foundation. There is also an open Discord platform community to join and a GraphQL Slack channel for historical discussions at European level. GraphQL Foundation Website: https://graphql.org/foundation/ Discord - GraphQL Community Resources: https://graphql.org/community/ GraphQL Europe Slack (historical discussions) channel at EU level: https://www.graphql-europe.org/'
The implementation of the specification fosters the data portability according to its purpose. CAdES Baseline profile has been developed to provide basic features necessary for electronic procedures including eSignature across borders. The implementation of CAdES Baseline Profile enhances the interoperability in the context of the European Single Digital Market.
'REST apis have 8 main security design principles that aim to provide a secure and trustwrthy exchange and processing of data. REST API security essentials reference: https://restfulapi.net/security-essentials/'
The purpose of DCAT-AP is not related to the medullisation of business processes. Therefore this criterion is not applicable to this specification.
XSLT Baseline Profile is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). Specifically, ASiC Baseline Profile can define the interoperability aspects. See: https://joinup.ec.europa.eu/search?keys=xslt&page=0
The purpose of WSDL is not related to organisational interoperability. Therefore, this criterion is not applicable to the specification.
'As the specification is using the SOAP Processing Model, it can adopt the HTTP binding to benefit from a consistent specification for an authentication credential, enabling authenticity in the process. SOAP Reference, Section 4.2 Binding Framework: https://www.w3.org/TR/soap12/#secconsiderations'
The rules on European standardisation allow the European Commission to identify information and communication technology (ICT) technical specifications - that are not national, European or international standards - to be eligible for referencing in public procurement. This allows public authorities to make use of the full range of specifications when buying IT hardware, software and services, allowing for more competition in the field and reducing the risk of lock-in to proprietary systems. After being evaluated compliant with the regulation on standardisation 1025/2012, XML has been identified by Commission Implementing Decision and included in the European list of ICT Standards for e-procurement. See: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en
After checking the different standard catalogues at supra-national level, there is no evidence of the inclusion of Xforms within any European catalogue of standards. ICT technical specifications: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en CEN search tool catalogue: https://standards.cen.eu/dyn/www/f?p=CENWEB:105::RESET:::: CENELEC search tool catalogue: https://www.cenelec.eu/dyn/www/f?p=104:107:0::::FSP_LANG_ID:25
'TGF promotes the use of inclusive design and accessibility best practices in the development of digital solutions and services. In particular, the TGF emphasises the importance of user-centred design, which involves designing products and services that meet the needs of all users, including those with disabilities. The TGF also promotes the use of open standards and open data, which can help ensure that digital solutions and services are accessible to all users, regardless of the technologies they use. TGF specification: http://docs.oasis-open.org/tgf/TGF/v2.0/cs01/TGF-v2.0-cs01.html'
The purpose of EuroVoc is not related to e-accessibility. Therefore, this criterion is considered not applicable to this specification. EuroVoc webpage: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/eurovoc
There are already existing studies and documents assessing and documenting UDDI features and providing possible improvements of its performance among other aspects. See: https://www.researchgate.net/publication/303921682_INDEXING_TRADITIONAL_UDDI_FOR_EFFICIENT_DISCOVERY_OF_WEB_SERVICES https://www.academia.edu/14435163/Binding_now_or_binding_later_The_performance_of_UDDI_registries
Like all the IETF standards, HTTPS is a free and open technical specification, built on IETF standards and licenses from the Open Web Foundation. FTP is licensed on a F(RAND) basis. See: https://tools.ietf.org/html/rfc3668
'9 member states are recommending the use of JSON in their ICT National Catalogues, these Member States are: Cyprus, Denmark, Finland, France, Iceland, Malta, The Netherlands, Slovakia and Slovenia. CAMSS List of standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
'The PROV family of documents indirectly addresses data integrity by capturing and representing provenance information. The captured lineage and transformation details can be used to verify the integrity of data throughout its lifecycle. However, additional security measures and best practices are required to ensure comprehensive data integrity. PROV Primer document: https://www.w3.org/TR/prov-primer/ PROV Ontology: https://www.w3.org/TR/2013/REC-prov-o-20130430/ PROV Data Model: https://www.w3.org/TR/2013/REC-prov-dm-20130430/'
'XSLT specification does not directly address the protection of personal data. Therefore this criterion is considered not applicable specification. XSLT Reference: https://www.w3.org/TR/xslt-30'
'UBL addresses some provisions on digital signature (see section 5.2.4 of specification), enabling the archiving and long-term preservation of information. UBL v2.3 reference: http://docs.oasis-open.org/ubl/os-UBL-2.3/UBL-2.3.html'
The DNS specification includes the data structures of data communication used by the system.
'The conformance of OpenTelemetry implementations can be assessed through various means to ensure compliance with the specification and interoperability with other components in the OpenTelemetry ecosystem. For instance, some supported languages such as Erlang/Elixir have a testing section where it is specified how to validate spans and attributes. OTel Erlang/Elixir Testing: https://opentelemetry.io/docs/languages/erlang/testing/'
There is no Member State that includes RegOrg in their national catalogue with The National Interoperability Framework (NIF) aligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'The IEEE Std 802.3-2022 does not specifically ensure long-term data preservation, but it creates the structure that helps with reliable data management, which is important for effective preservation strategies. IEEE Std 802.3-2022 Reference: https://ieeexplore.ieee.org/document/9844436'
The purpose of MIME is not related to the availability of interfaces with internal information systems. Therefore, this criterion is not applicable to this specification. MIME reference: https://tools.ietf.org/html/rfc2045
The purpose of LDAP is not related to the publication of public data as linked open data. Therefore, this criterion is not applicable to this specification. LDAP IETF reference: https://tools.ietf.org/html/rfc4511 Five star linked open data: https://www.w3.org/DesignIssues/LinkedData.html
'The Testing, Experimentation and Open Source (TST) Working Group provides feature requests to open source projects and results of implementation experience to open source communities; however, not in national platforms. TST NFV reference: https://portal.etsi.org/TB-SiteMap/NFV/NFV-WGs-amp-EGs-ToR'
TIFF/IT is a business domain agnostic specification that can be reused in a cross-domain way. TIFF/IT ISO reference: https://www.iso.org/standard/34342.html
'The purpose of this Core Vocabulary is not related to the authenticity and authentication of the role agents involved in data transactions. Therefore, this criterion is not applicable to this specification. CPSV-AP reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-service-vocabulary-application-profile'
'The specification introduces certain aspects that can contribute to provide means for restriction of access to information or data, as in the implementation of CESOP Legislative Package , which monitor the payees of cross-border payments and transmit information. XSD Reference: https://www.w3.org/TR/2012/REC-xmlschema11-1-20120405/ Legislative Package CESOP Reference: https://taxation-customs.ec.europa.eu/taxation-1/central-electronic-system-payment-information-cesop_en'
'One of the main keys of LDAP is that it is useful for organisations to protect and manage information. In addtion, there are measures that can help to the protection of personal data. While SASL improves security, implementing a single sign-on system using LDAP is another method that can enhance security aspects. LDAP IETF reference: https://tools.ietf.org/html/rfc4511 LDAP Wirex reference: https://wirexsystems.com/resource/protocols/ldap'
After searching in the different official European websites, there is no evidence of any cross-border project that use LDAP nor explicit agreements involving the usage of the specification.
The Time-Stamp Protocol, or TSP is a cryptographic protocol for certifying timestamps using X.509 certificates and public key infrastructure. The timestamp is the signer's assertion that a piece of electronic data existed at or before a particular time. TSP IETF reference: https://tools.ietf.org/html/rfc3161
The IETF is a consensus-based group, and authority to act on behalf of the community requires a high degree of consensus and the continued consent of the community. The process of creating and Internet Standard is straightforward: a specification undergoes a period of development and several iterations of review by the Internet community and revision based upon experience, is adopted as a Standard by the appropriate body... and is published. In practice, the process is more complicated, due to (1) the difficulty of creating specifications of high technical quality; (2) the need to consider the interests of all the affected parties; (3) the importance of establishing widespread community consensus; and (4) the difficulty of evaluating the utility of a particular specification for the Internet community. The goals of the Internet Standards Process are: - Technical excellence; - prior implementation and testing; - clear, concise, and easily understood documentation; - openness and fairness; and - timeliness. The goal of technical competence, the requirement for prior implementation and testing, and the need to allow all interested parties to comment all require significant time and effort. The Internet Standards Process is intended to balance these conflicting goals. The process is believed to be as short and simple as possible without sacrificing technical excellence, thorough testing before adoption of a standard, or openness and fairness. Standard process IETF: https://www.ietf.org/standards/process/
Like all the IETF standards, LDAP is a free and open technical specification, built on IETF standards and licenses from the Open Web Foundation. LDAP is therefore licensed on a royalty-free basis. Intellectual Property Rights in IETF: https://tools.ietf.org/html/rfc3668
The specification is focused on the discoverability of parties, involving the use of parties metadata and the identification of access points. This field is being developed by public administrations in order to create innovative solutions that work for the enhancement and digitalisation of administrations services. An element that can be related to the creation of innovative solutions is the CEF eDelivery Building Block, which can be considered an innovative solution in terms of eGovernment and the relation of Public Administrations with their stakeholders. The specification: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505000 eDelivery: https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery
'HTTPS can enable digital service delivery channels by providing a secure and encrypted communication channel between clients and servers. It forms the foundation for secure and reliable online interactions, allowing organizations to deliver their services through digital channels such as websites, web applications, and APIs. HTTPS specification: https://tools.ietf.org/html/rfc2818'
The ISO 15948:2004 which refers to PNG is not available for free for everyone to study. Payment is needed to reach access to the standard. PNG ISO reference: https://www.iso.org/standard/29581.html
"The purpose of Core Location Vocabulary is not related to enabling the exposure of interfaces to access the public administration's services. Therefore this criterion is not applicable to the specification. Core Location Vocabulary: https://interoperable-europe.ec.europa.eu/collection/semic-support-centre/solution/core-location-vocabulary/release/100"
'The specification is available for free at the European Collaborative platform Joinup. Joinup Europa: https://joinup.ec.europa.eu/solution/web-services-description-language-wsdl-version-20-part-0-primer'
OASIS has defined WS-Security-dev and the standard feedback from OASIS which is the process where all the stakeholders involved have the opportunity to participate in the development of the specification development process. See: https://www.oasis-open.org/policies-guidelines/tc-process-2017-05-26
'HTTP can provide a common language and set of rules for web communication between different systems or users and services. This standardisation is important for the interoperability as it ensures that different implementations can exchange information effectively. HTTP /1.1 RFC 2616 Reference: https://www.rfc-editor.org/rfc/rfc2616.html HTTP/1.1 Semantics RFC 9110 Reference: https://www.rfc-editor.org/rfc/rfc9110#name-routing-http-message HTTP/1.1 Caching, RFC 9111 Reference: https://www.rfc-editor.org/rfc/rfc9111'
As one of the main markup languages for encode web resources, WS-BPEL is involved in the data exchange. WS-BPEL files are largely used to exchange information through the web. The specification: http://docs.oasis-open.org/wsbpel/2.0/OS/wsbpel-v2.0-OS.html
XML is included in several national catalogues from Member States. A total of 14 countries listed the XML within their national catalogues (e.g. Belgium, France, Germany, etc.). See CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
HTML is the standard markup language for web documents. It can be assisted by technologies such as Cascading Style Sheets (CSS) and scripting languages such as JavaScript. It proportionates to the users an environment for cross-platform applications with access to device capabilities and accept all type of files to be published. So, it is proportionate to the needs of its users. HTML W3C reference: https://www.w3.org/TR/html401/
'The specification is independent of any software, hardware, or operating system. Therefore, OCSP is independent of any specific platform. OCSP reference: https://datatracker.ietf.org/doc/html/rfc2560'
OWL2 has a positive impact on system interoperability. While developing ontologies with OWL2 a syntax is needed in order to store ontologies and to exchange them among tools and applications. RDF/XML syntax provides positive interoperability among OWL2 tools because it can be written and read by all conformant OWL2 software. OWL2 W3C reference: https://www.w3.org/TR/owl2-overview/ RDF 1.1 XML Syntax https://www.w3.org/TR/rdf-syntax-grammar/
The specification aims to be the basis for the development of public solutions that could be reusable across borders. It provides codebases that can be adapted to reach specific business requirements of certain implementations. Security is a key aspect when exchanging information and in this way, the specification states that when developing or implementing public source it should be enabled communication points to communicate regarding security aspects. Moreover, the flexibility that codebases grant allows administrations to integrate specific security capabilities to ensure a secure and trustworthy data exchange. The Standard for Public Code webpage: https://standard.publiccode.net/
'Section 7.1.6 of the specification explicitly addresses and enables the secure and trustworthy processing of data as it highlights considerations regarding policy interoperability. For instance, there can be specific security requirements based on the nature of the data and the processing involved, for example, where credit card information is concerned, the cloud service can be required to meet the requirements of the Payment Card Industry Data Security Standard (PCI-DSS). PCI Data Security Standard (PCI DSS): https://www.pcisecuritystandards.org/documents/Virtualization_InfoSupp_v2.pdf ISO 19941: https://www.iso.org/obp/ui/en/#iso:std:iso-iec:19941:ed-1:v1:en'
'After checking the different standard catalogues at supra-national level, there is no evidence of WAI-ARIA as a European standard. WAI-ARIA is a technical specification developed by the World Wide Web Consortium (W3C) to improve the accessibility of web content. W3C Specification: https://www.w3.org/TR/?filter-tr-name=WAI ICT technical specifications: https://ec.europa.eu/growth/single-market/european-standards/ict-standardisation/ict-technical-specifications_en CENELEC and CEN search tool catalogue: https://standards.cencenelec.eu/dyn/www/f?p=CEN:105::RESET:::: '
The purpose of SOAP 1.2 is not related to the long-term preservation of electronic records and other kinds of information. Therefore, this criterion is not applicable to the specification.
HTML5 has been assessed by the CAMSS Team under the MSP scenario, which is fully compliant with the European Standardisation Regulation 1025/2012. See: https://joinup.ec.europa.eu/solution/camss-assessment-html5-msp-scenario
'The OASIS Technical Committee, in charge of the development of OData, operates under RF (royalty-free) on RAND Mode of the OASIS IPR Policy. Therefore, the specification is licensed on a Royalty-free and mostly aligned with F/RAND principles. OASIS Intellectual Property guidelines, section 5.2: https://www.oasis-open.org/policies-guidelines/ipr/#contributions'
Core Vocabularies can be used as the foundation of common export formats for data in base registries like cadastral, business registers or public service portals. The Core Location Vocabulary is a simplified, reusable and extensible data model that captures the fundamental characteristics of a location, represented as an address, a geographic name, or a geometry. By describing locations (addresses, geographical names, etc) in a common way using both human and machine-readable format, it allows the publication of information as linked open data for its consultation and reuse. 5-star linked open data: https://www.w3.org/DesignIssues/LinkedData.html CLV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-location-vocabulary Use cases and benefits of ISA² specifications: https://ec.europa.eu/isa2/sites/isa/files/docs/publications/isa2_study_use_cases_and_benefits_of_isa2_specifications_january_2019.pdf
CPSV-AP is a reusable and extensible data model for harmonising the way public services are described in a machine-readable format. So it describes the public administrations and eases their visualization and comprehensibility. CPSV-AP reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-service-vocabulary-application-profile
'ETSI EN 319 422 has the support of various communities listed in the following link as "Supporting Organizations", including Universities, private and public companies. The ESI technical committee provides public support to members and non-members alike, with different conditions depending on ETSI membership status. This support helps to increase the use of the specification and the specification itself by detecting weaknesses in implementation or any other relevant aspect of the specification's functionalities. About ETSI: https://www.etsi.org/about Portal ETSI reference: https://portal.etsi.org/webapp/workprogram/Report_WorkItem.asp?WKI_ID=39422 ETSI Technical committee reference: https://www.etsi.org/committee/1399-es.'
'Taking the initial purpose of the specification, which is to enrich connector identities by issuing up-to-date information in form of signed claims, it can be considered that the specification is involved in fostering the comprehensibility of Public Administrations data as well as relevant data produced for the decision-making process. DAPS: https://github.com/International-Data-Spaces-Association/IDS-G/tree/main/Components/IdentityProvider/DAPS'
'The purpose of TOSCA is not related to the secure exchange of data. Therefore, this criterion is considered not applicable to this specification. TOSCA reference: https://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.3/os/TOSCA-Simple-Profile-YAML-v1.3-os.html'
The specification has been developed under a voluntary agreement between the Member States aiming to enhance the legal framework and the cooperation between administrations for building an interoperability environment across borders. Council communications and conclusions "Council Conclusions published on 26 October 2012 (2012/C 325/02)", and the "Council conclusions of 6 November 2017 on the European Legislation Identifier" are the official legal document where ELI is defined. Council Conclusions published on 26 October 2012 (2012/C 325/02): https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:52012XG1026(01) Council conclusions of 6 November 2017 on the European Legislation Identifier: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:52017XG1222(02) ELI reference: https://eur-lex.europa.eu/eli-register/about.html
'Although TOSCA is widely known in the field of cloud computing, the specification offers versatility, as it runs in a container (or software unit) and specifies orchestration process models that enable the management of services, as well as their use in various domains, independently of the application context. TOSCA reference: https://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.3/os/TOSCA-Simple-Profile-YAML-v1.3-os.html'
'By associating a name to an IP, DNS facilitates the identification of the content of domains and therefore, it can be said to reduce the administrative burden. Currently the EU is working on creating secure DNS services for the european organisations and citizens. DNS IETF reference: https://datatracker.ietf.org/doc/html/rfc8499 Backbone networks for pan-European cloud federation (CEF-DIG-2021-CLOUD) https://ec.europa.eu/info/funding-tenders/opportunities/portal/screen/opportunities/topic-details/cef-dig-2021-cloud-dns-works'
'The efficiency of HTTP has been shown through its evolution into HTTP/3. HTTP/3 improves speed and reliability by using modern transport protocols, addressing the limitations of earlier versions. These advancements show that HTTP continuously adapts to meet new technological and security demands, proving its lasting efficiency. HTTP /1.1 RFC 2616 Reference: https://www.rfc-editor.org/rfc/rfc2616.html Measuring HTTP/3: Adoption and Performance: https://arxiv.org/pdf/2102.12358'
eDelivery SMP 1.10 is part of the eDelivery Building Block (BB), which is provided by CEF and aims to help public administrations to share electronic data across borders in a reliable way. The BB eases the integration between implementers fostering the creation of interoperable infrastructures used for the digital data exchange. See: https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/How+does+eDelivery+work
'The Executive Committee has to review and coordinate the progress of the TCs and, from time to time, review the terms of reference given to Technical Committees. In addition, the Technical Committee shall review and approve the minutes of the preceding meeting. Although Ecma is the SDO that first developed the specification, it is currently being maintained by the IETF, thus, adhering to the development process defined by the organisation, which comprehends public reviews. ECMA Directives: http://www.ecma-international.org/memento/policies.htm Standard process IETF: https://www.ietf.org/standards/process/'
'The purpose of SAML 2.0 is not related to ensuring and enabling data processing accuracy. Therefore, this criterion is not applicable to the specification. SAML 2.0 Reference: http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-tech-overview-2.0.html'
The purpose of XAdES is not related to the visibility of administrative information, data or services. Therefore, this criterion is not applicable to this specification. XAdES ISO reference: https://www.iso.org/standard/56025.html XAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/101900_101999/101903/01.04.02_60/ts_101903v010402p.pdf
"XSLT's main function is transforming XML data, which is essential for interoperability between different systems. In European public services, which often involve diverse systems and data formats, XSLT can convert data between these formats, ensuring seamless information exchange. An example of usage is at the European Single Procurement Document (ESPD). XSLT is used to transform ESPD documents into different formats, such as PDF or HTML, making them accessible and readable across various platforms and devices. European Single Procurement Document (ESPD) Github Reference: https://github.com/OP-TED/ESPD-EDM XSLT Reference: https://www.w3.org/TR/xslt-30 "
'This specification is included in the solutions catalogue of ICT Standards for Procurement created by the European Commision. The European Catalogue will contribute to these objectives by offering a one-stop shop for procurers on guidelines for procurement, including on vendor lock-in, on the use of standards, and a lifecycle costing scheme that accounts for the often neglected interoperability costs. It will streamline the numerous guidelines and provide for a platform of exchange and dissemination. ICT Standards for Procurement: https://joinup.ec.europa.eu/collection/ict-standards-procurement'
'XHTML is one of the main markup languages to develop web resources. XHTML files are used to exchange information through the web. This fact proves that XHTML fosters data portability between systems and applications. XHTML W3C reference: https://www.w3.org/TR/xhtml1/'
'Conformance requirements of DNS queries over HTTPS (DoH) are expressed with a combination of descriptive assertions. The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in the normative parts of this document are to be interpreted as described in BP14. BCP 14: https://www.rfc-editor.org/info/bcp14'
'There is no Member State recommending EN 16234-1 e-CF in its ICT National Catalogue. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
'The purpopse of Indexed Database API is not related to comprehensibly administrative procedures, rules data, and services. Therefore this criterion is not applicable to the specification. Indexed Database API: https://www.w3.org/TR/IndexedDB/'
'DAPS is an attribute server that issues OAuth2 access tokens to International Data Spaces connectors. The connectors need these to access the services and data of other connectors. the decision about permitted access is not made by DAPS but always by the requested connector itself. Therefore, DAPS merely administers the International Data Spaces attributes of the registered connectors. DAPS: https://github.com/International-Data-Spaces-Association/IDS-G/tree/main/Components/IdentityProvider/DAPS'
'Currently the Asset Administration Shell (AAS) is not directly used in any European Cross-border initiative, but IDTA it is including the GAIA-X services. In this sense AAS has been included in some GAIA-X initiatives that are cross-border such as the Digital Product Passport. Digital Product Passport reference: https://www.sciencedirect.com/science/article/pii/S2212827124003482 IDTA and GAIA-X: https://industrialdigitaltwin.org/en/use-cases/demonstrator-collaborative-condition-monitoring-data-sharing-as-win-win Details of the Asset Administration Shell (AAS) https://industrialdigitaltwin.org/en/wp-content/uploads/sites/2/2024/06/IDTA-01001-3-0-1_SpecificationAssetAdministrationShell_Part1_Metamodel.pdf'
IPv4 has been selected within the cross-border project of The Compendium from the National Research and Education Networks in Europe (NREN). The Compendium structures its services in an IP-based network using mainly IPv4. The protocol acts as the backbone of the Pan-European network provided by GEANT. See: https://www.geant.org/Resources/Documents/Compendium2016.pdf https://www.geant.org/Networks/Pan-European_network/Pages/Home.aspx
At the moment of performing the assessment, UDDI is one of the foundations of web services together with SOAP and WSDL. Even there is a new implementation mode as is REST, SOAP is still active and highly used in the creation of new solutions including innovative solutions.
'ADMS provides a standardised method for describing assets and their distributions. Therefore, while providing a common way and components for the metadata provision, it helps the comprehensibility of data and services of Public administrations across borders. ADMS on Joinup: https://joinup.ec.europa.eu/solution/asset-description-metadata-schema-adms/about ADMS Specification W3C: https://www.w3.org/TR/vocab-adms/'
'Syslog, as a protocol for message logging, is not specifically designed for the long-term preservation of data, information, or electronic records. Its primary function is to transmit and store log messages related to system events, errors, and activities. Syslog Protocol: https://datatracker.ietf.org/doc/html/rfc5424'
"WSDL itself doesn't enforce or dictate language-specific aspects, it provides a foundation for describing the technical aspects of web services. The broader considerations for multilingual support involve design choices, documentation practices, and the implementation of the web service itself. W3C WSDL specification: https://www.w3.org/TR/wsdl20/"
The specification is not included in any Member State national catalogue for ICT. Despite this, eDelivery SMP 1.10 is a European profile recommended by the European public bodies in order to establish a common interoperability framework.
'ebXML is already associated to EIRA ABBs in the EIRA Library of Interoperability Specifications (ELIS). More specifically, ebXML can define the interoperability aspects of the "Registration" ABB of the EIRA Technical View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /solution/elis/release/v610 ebXML RegRep OASIS reference: https://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html'
No tools assessing the conformity of implementations with the specification have been found coming from the IETF. However, there are existing tools available on open source to check the conformity and performance of TLS including version being assessed TLS 1.2. See: https://github.com/drwetter/testssl.sh
'The specification is used in the European Materials Modeling Ontology (EMMO) created by the European Materials Modelling Council (EMMC). BFO reference: https://www.iso.org/standard/74572.html'
'ETSI EN 319 422 can be applied in any domain and context where the use of time-stamping protocol is realized. Therefore, the specification is usable beyond any business-specific domain and can be used in any kind of organisation. ETSI EN 319 422 reference: https://www.etsi.org/deliver/etsi_en/319400_319499/319422/01.01.01_60/en_319422v010101p.pdf '
'The purpose of NUTS is not related to enabling the long-term preservation of data, information nor knowledge. Therefore, this criterion does not apply to this specification. EUROSTAT reference, NUTS Principles and Characteristics section: https://ec.europa.eu/eurostat/web/nuts/principles-and-characteristics'
'The purpose of LDAP is not related to long term preservation of electronic records. Therefore, this criterion is considered not applicable to this specification. LDAP IETF reference: https://tools.ietf.org/html/rfc4511'
XACML is a markup language that is used to declare access conditions stated on Security Policies. It can be adapted to ensure that web services are compliant with security policies, and therefore, ensure the data trustworthy exchange. XACML OASIS reference: http://docs.oasis-open.org/xacml/3.0/errata01/xacml-3.0-core-spec-errata01.html
The specification is aimed to participate in the evaluation of access policies, participating in authentication processes that can ease the secure and trustworthy exchange of data. For security reasons, the XForms Processor must not dereference the URI bound to this form control without explicit user permission. Xforms 2.0 W3C reference: https://www.w3.org/community/xformsusers/wiki/XForms_2.0
'DPV provides a taxonomy of technical and organisational measures for representing information about how the processing of personal data is technically and organisationally protected, safeguarded, secured, or otherwise managed. By referring to what measures are in place (such as GDPR) DPV directly addresses issues about the secure processing of data pointing to the compliance of legal obligations to ensure data protection. DPV specification: https://w3c.github.io/dpv/dpv/ DPV primer document: https://w3c.github.io/dpv/primer/#introduction '
"The ebXML specification provides guidelines to validate ebXML services. ebXML RegRep Part 2 proposes a validator plugin that evaluates any client's sever's ebXML conformance requirements. ebXML reference: http://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html http://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-rs-v4.0-os.html#__RefHeading__32527_422331532"
"EuroVoc was developed for the first time in 1982. It has been constantly evolving to adapt user's needs. Moreover, there are several releases since it was developed that justify its maturity and its use in the developement products and services. EU Vocabularies Releases: https://op.europa.eu/en/web/eu-vocabularies/releases EuroVoc: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource /dataset/eurovoc"
'Every five years, ISO standards go through a systematic review process during which the members assess and propose updatings. ISO public review guide: https://www.iso.org/files/live/sites/isoorg/files/store/en/PUB100413.pdf'
DCAT is a domain-agnostic specification that can be reused for the description of any catalogue of dataset independently from the business domain addressed. For DCAT users having business-specific requirements, the specification is generally extended (e.g. StatDCAT-AP for statistical data)
'The ebXML specification, as an enabler of electronic data interchange (EDI) functionalities over the Internet, has a wide-spread use in both private and public sectors. For instance, several initiatives in Europe have adopted the Universal Business Language (UBL), which is designed to be agnostic with respect to any EDI infrastructure and mapped to the ebXML core components, which proves the degree of usefulness of the specification and its suitability to be used in the development of digital solutions/services (see Joinup OASIS UBL reference). Joinup OASIS UBL reference: https://joinup.ec.europa.eu/collection/eprocurement/solution/oasis-universal-business-language-ubl/about ubl.xml.org reference: http://ubl.xml.org/ebXML'
SOAP 1.2 is associated to an EIRA ABB in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, SOAP 1.2 can define the interoperability aspects of the "Machine to Machine Interface", "Data Exchange Component" and, “Data Exchange Service” ABBs from the EIRA Technical Infrastructure view. See: https://joinup.ec.europa.eu/release/eira-library-interoperability-specifications-elis/v100-beta
HTML is included in 4 national catalogues of recommended specifications. They belong to Estonia, the Netherlands, Spain and Sweden. The National Interoperability Framework (NIF) of these Member States is fully aligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards NIFO factsheets: https://joinup.ec.europa.eu/collection/national-interoperability-framework-observatory-nifo/nifo-factsheets
'EN 16234-1 e-CF provides a common European description of the knowledge, skills and competences of the ICT professional workforce in all sectors. It contributes to moving towards a comprehensive framework for ICT practitioners integrating different building blocks relying not only on the EN 16234-1 e-CF but also on the e-CF User Guide (EN 16234-2) and the e-CF Methodologies (EN 16234-3). CEN reference, CEN/TC 428 - ICT Professionalism and Digital Competences (Published standards), EN 16234-1 e-CF: https://standards.cencenelec.eu/dyn/www/f?p=205:32:0::::FSP_ORG_ID,FSP_LANG_ID:1218399,25&cs=1C0456547BD827F5A977AD2936836C8DA CEN reference, CEN/TC 428 - ICT Professionalism and Digital Competences (Published standards), EN 16234-2 User Guide: https://standards.cencenelec.eu/dyn/www/f?p=CEN:110:0::::FSP_PROJECT,FSP_ORG_ID:70377,1218399&cs=13178F0C970F6172F57335317C3456DD8 CEN reference, CEN/TC 428 - ICT Professionalism and Digital Competences (Published standards), EN 16234-3 Methodology: https://standards.cencenelec.eu/dyn/www/f?p=CEN:110:0::::FSP_PROJECT,FSP_ORG_ID:70378,1218399&cs=192D0AD053B765C617E43CC16AD1D4019'
'OASIS has defined a clear Technical Committee (hereby TC) process where all the stakeholders involved have the opportunity to participate in the development of the specification development process. All the information related to a TC activity is hosted and can be consulted. OASIS Policies Guidelines: https://www.oasis-open.org/policies-guidelines/tc-process-2017-05-26'
'Although DCAT-AP itself does not provide means for the enabling of data integrity, the SEMIC Support Center has developed the DCAT-AP validator, a software tool to check metadata description of datsets for integrity and consistency. DCAT-AP validator: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/dcat-ap-validator'
'XSLT specification includes several mechanisms for assessing its efficiency, primarily through testing and implementation reports. There are document of the European Commission assessing the suitability of XSLT specification. Digital Signature Service: https://ec.europa.eu/cefdigital/DSS/webapp-demo/doc/dss-documentation.html#_xades_profiles XSLT Reference: https://www.w3.org/TR/xslt-30'
The adoption of the spefication to specify certified time stamps can be done independently from the amount of data. Several implementations can be used by administrations, citizens and businesses for the certification of documents. For instance, TSP is the basis of ETSI EN 319 422 Electronic Signatures and Infrastructures (ESI); Time-stamping protocol and time-stamp token profiles, which use a European specification to ensure the time-stamp of documents and the requirements, including the Time Stamp RFC3161. TSP IETF reference: https://tools.ietf.org/html/rfc3161 DigiStamp: https://www.digistamp.com/ FreeTSA: https://www.freetsa.org/index_en.php ETSI EN 319 422 Electronic Signatures and Infrastructures (ESI); Time-stamping protocol and time-stamp token profiles: https://www.etsi.org/deliver/etsi_en/319400_319499/319422/01.01.01_60/en_319422v010101p.pdf
'There are three Member States recommending UBL in their ICT National Catalogues. These Member States are The Netherlands Malta and Greece. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
6 Member States are recommending FTP in their ICT Catalogues. See CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
OWL2 has been used to develop innovative solutions in numerous cases. Some examples are integrating OWL2 with text editors such as Protégé 4, SWOOP. It has also been integrated with TopBraid Composer which is an enterprise-class modelling environment for developing Semantic Web ontologies. More innovative solutions can be seen at the following link in the 'Editors / Development Environments / APIs' section._x000D_ _x000D_ Also, it is worth to note that OWL is the basis for the creation of Ontologies, and therefore one of the basis for the development of the Semantic Web. _x000D_ _x000D_ OWL2 solutions:_x000D_ https://www.w3.org/2001/sw/wiki/OWL/Implementations
'XSLT specification is a language designed for transforming XML data. This functionality is applicable to any domain that uses XML as a data representation, generating different output formats for different use cases. XSLT Reference: https://www.w3.org/TR/xslt-30'
Even though the purpose of OWL2 is not related directly to long term preservation of electronic records, there are examples of ontologies developed for the preservation and maintenance of metadata in archives systems. An example of this is the Library of Congress initiative PREMIS OWL Ontology. OWL2 W3C reference: https://www.w3.org/TR/owl2-overview/ PREMIS OWL Ontology https://www.loc.gov/standards/premis/ontology/index.html
'The OASIS Technical Committee, in charge of the development of ebXML, operates under RF (royalty-free) on RAND (reasonable and non-discriminatory) Mode of the OASIS IPR Policy. Therefore, the specification is licensed on a Royalty-free. OASIS Intellectual Property guidelines, section 5.2: https://www.oasis-open.org/policies-guidelines/ipr/'
'Currently the Asset Administration Shell (AAS) is not included in any national catalogue. However, IDTA is extensibly recommended by the German authorities which includes the AAS. IDTA repository: https://industrialdigitaltwin.org/en/content-hub/aasspecifications Details of the Asset Administration Shell (AAS) https://industrialdigitaltwin.org/en/wp-content/uploads/sites/2/2024/06/IDTA-01001-3-0-1_SpecificationAssetAdministrationShell_Part1_Metamodel.pdf'
"Domibus allow to deploy and use specific components or features of the platform based on a given organisation's requirements. Domibus modularity, therefore, makes it a flexible solutions that allow for partial implementations. Domibus specification: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/Domibus"
IETF is a non-profit making organisation. It is large open community of network designers, operators, vendors, and researchers. It is open to any interested individual with the evolution of the Internet architecture and the smooth operation of the Internet. See: https://www.ietf.org/rfc/rfc3935.txt
'The ebXML specification is recommended in several European Commission Decisions for public procurement. Public procurement reference: https://joinup.ec.europa.eu/collection/ict-standards-procurement/identified-ict-specifications-procurement'
'The purpose of EuroVoc is not related to providing means for restriction of access to information/data. Therefore, this criterion is not applicable to this specification. EuroVoc: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource /dataset/eurovoc'
3 Member States are recommending ASiC in their ICT National Catalogues. See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
All XIPH standards are under BSD-style license which is a specific license for open source specifications. More specifically it is a free-software license with only minimal restrictions on how the software can be used, modified, and redistributed, usually including a warranty disclaimer. XIPH documentaiton: https://wiki.xiph.org/index.php/Main_Page
'The specification is technology-agnostic, meaning it does not depend on any software or platform. RDF primer document: https://www.w3.org/TR/rdf11-primer/'
'The Dataspace Protocol is a set of specifications designed to negotiate Agreements, among other functions. The Contract Negotiation Protocol and Contract Negotiation HTTPS Binding documents section of the specification definese how Contract Negotiations are conducted and requested via HTTPS endpoints. Furthermore, IDSA Rulebook aims is to describe clearly which rules are mandatory and which are optional guidelines. This governance framework includes functional, technical, operational, and legal dimensions. Contract Negotiation Protocol: https://docs.internationaldataspaces.org/ids-knowledgebase/v/dataspace-protocol/contract-negotiation/contract.negotiation.protocol IDSA Rulebook: https://docs.internationaldataspaces.org/ids-knowledgebase/v/idsa-rulebook/idsa-rulebook/1_introduction'
'The WAI-ARIA specification itself does not provide means for the restriction of access to information or data.Therefore, this criterion is not applicable to this specification. WAI-ARIA reference: https://www.w3.org/TR/wai-aria/'
The purpose of XACML is not related to e-accessibility. Therefore, this criterion is not applicable to the specification. XACML OASIS reference: http://docs.oasis-open.org/xacml/3.0/errata01/xacml-3.0-core-spec-errata01.html
Core Public Service Vocabulary Application Profile 2.2 is already associated to an EIRA ABB in the EIRA Library Of Interoperability Specifications (ELIS). Specifically, this Core Vocabulary can define the interoperability aspects of the "Core Data Model" and "Data" ABBs from the EIRA Semantic view. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/solution/elis/release/v100
The purpose of this specification is not related to reduce administrative burden. The main purpose of Ogg is to proportionate a multimedia open source format/container. Therefore, this criterion is considered not applicable to this specification. Ogg XIPH reference: https://xiph.org/ogg/doc/rfc3533.txt
'IDSA was formed in 2017 to develop the IDS (formerly known as Industrial Data Spaces) reference architecture model and certification procedures based on industry requirements thus, DAPS is related to facilitating organisational interoperability agreements. DAPS: https://github.com/International-Data-Spaces-Association/IDS-G/tree/main/Components/IdentityProvider/DAPS'
'While the primary focus of OpenTelemetry is on observability and monitoring of digital systems, it indirectly supports the long-term preservation of electronic records by ensuring the integrity, reliability, accessibility, and security of the underlying infrastructure. OpenTelemetry can improve long-term preservation of electronics resources through the integration with storage backends. OpenTelemetry: https://opentelemetry.netlify.app/docs/specs/otel/'
'OData queries and shares data across different systems via RESTful interfaces. RESTful APIs may be platform-agnostic, without any dependency on the environment or programming language being used, and in this case OData primarily exists to expose data in a platform agnostic manner so that .NET, Java, Php, Python, REST, etc clients can all access the data. So, the specification is platform-agnostic. OData reference: https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#_Toc31358832'
'REST is an architecture style that defines how different systems should interact. REST APIs generate a way of accessing web services in a simple and flexible way without having any processing,Therefore allowing for a comprehensible display of administrative procedures, and services. The french government website data.gouv.fr which hosts the french governments datasets is built under the REST architectural style. REST reference: https://restfulapi.net/ Data.gouv.fr reference: https://doc.data.gouv.fr/api/intro/'
The rules on European standardisation allow the European Commission to identify information and communication technology (ICT) technical specifications - that are not national, European or international standards - to be eligible for referencing in public procurement. This allows public authorities to make use of the full range of specifications when buying IT hardware, software and services, allowing for more competition in the field and reducing the risk of lock-in to proprietary systems. After being evaluated compliant with the regulation on standardisation 1025/2012, HTTPS has been identified by Commission Implementing Decision. See: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en
'Section 7.9 of the specification focuses on the component for language selection. This component shall be used to request a preferred language of the response and shall be specified according to IETF RFC 5646. The service should provide language-specific responses using the requested language. In the case the requested language is not supported then no error shall be raised and the responses shall be produced in the SCS default language. ETSI TS 119 432: https://www.etsi.org/deliver/etsi_ts/119400_119499/119432/01.02.01_60/ts_119432v010201p.pdf IETF RFC 5646: https://datatracker.ietf.org/doc/rfc5646/'
'IPsec allows the exchange of data between systems, supporting the evolution of European public services. An example of its implementation is the TESTA project, which provides a secure cross-border data communication network service for public administrations. IPSec reference, What IPSec Does: https://datatracker.ietf.org/doc/html/rfc4301#page-7 Interoperable Delivery of European Egovernment Services to Public Administrations, Businesses and Citizens (IDABC) Reference Link: https://ec.europa.eu/idabc/en/document/2097.html TESTA Service: https://ec.europa.eu/isa2/solutions/testa_en'
The IETF is completely open to newcomers. There is no formal membership, no membership fee, and nothing to sign. The IETF's standards development work is organized into 8 Areas Each Area has 1 or more Area Directors (ADs), which together comprise the Internet Engineering Steering Group (IESG). The IESG is responsible for technical management of IETF activities, the Internet standards process, and for the actions associated with entry into and movement along the Internet ''standards track'', including final approval of specifications as Internet Standards and publication as an RFC. Within each Area there are multiple Working Groups (WG). Each WG has one or more chairs who manage the work, and a written charter defining what the work is and when it is due. There are more than 100 WGs. The WGs produce Internet Drafts (I-Ds) which often lead to the publication of an Internet standard as an RFC. See: http://www.ietf.org/newcomers.html
'GITB TDL is maintained and supported by the interoperability test bed team. Further developments have been carried out by the developer community regarding GITB TDL that can be viewed at its webpage. GITB TDL change history reference: https://github.com/ISAITB/gitb/tree/master/gitb-validator-tdl/src/main/java/com/gitb/vs/tdl JOINUP reference: https://joinup.ec.europa.eu/collection/interoperability-test-bed-repository/solution/interoperability-test-bed/detailed-information#releases'
"This specification is currently included in the EIRA Library of Interoperability Specifications (ELIS). Currently the specification is listed in the following ABB's: DataManagementApplicationService, DataAnalyticsApplicationComponent, DataAnalyticsApplicationService, DataManagementApplicationComponent EIRA Library of Interoperability Specifications (ELIS): https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/version-610"
The purpose of DCAT-AP is not related to organisational interoperability. Therefore this criterion is not applicable to this specification.
The specification was developed in 2012 and has been implemented at European level, and it has been evolved together with the application profile used in the European Platform for the reusability of interoperability Solutions, Joinup. ADMS in Joinup: https://joinup.ec.europa.eu/solution/asset-description-metadata-schema-adms/about
As a specification that enhances the discoverability and access to different web services, it can help to ensure access by providing SOAP endpoints where the services and internal information are located.
"Criteria used to define NUTS codes do exist, but there is not a reference document to this end: 'NUTS 1981- NUTS 1999' and 'REGULATION (EC) No 1059/2003'. EUROSTAT reference, History of NUTS section, 'NUTS 1981 - NUTS 1999' document, 'Structure of this document' section: https://ec.europa.eu/eurostat/web/nuts/history EUR-LEX reference, REGULATION (EC) No 1059/2003' document: https://eur-lex.europa.eu/legal-content/EN/ALL/?uri=CELEX:02003R1059-20180118&qid=1519136753473"
'ISO/IEC 27001 includes requirements for the assessment and treatment of information security risks tailored to the needs of the organization. The requirements set out in this International Standard are generic and are intended to be applicable to all organizations, regardless of type, size or nature. ISO 27001 reference: https://www.iso.org/obp/ui/#iso:std:iso-iec:27001:ed-2:v1:en'
"DNS Queries over HTTPS (DoH) is included in the EU-funded SAPPAN project, which seeks to introduce a privacy-preserving sharing and automation platform to facilitate efficient response to and recovery from cyberattacks. DoH has been created to improve users' privacy on the internet and it will develop a cyberthreat intelligence system to assist security and IT personnel within and across organisations in timely responding to threats. SAPPAN Project: https://sappan-project.eu/ DoH Insight: https://dl.acm.org/doi/10.1145/3407023.3409192"
'UBL foresees support for multilingual context as it provides clear rules for extension and a number of subsets and tool resources such as localization dictionaries in Chinese, Danish, German, Italian, Japanese, Korean, Spanish and Turkish. This enables communities to create explicit extensions that are locally profiled for their context of use. UBL v2.3 reference: http://docs.oasis-open.org/ubl/os-UBL-2.3/UBL-2.3.html The Meaning of UBL: The Value of a Semantic Data Model: http://ubl.xml.org/forum/the-meaning-of-ubl-the-value-of-a-semantic-data-model'
'The majority of real-world ebXML messages have unique XML-based, message-level security requirements, including digital signatures, non-repudiation, data privacy, and content-borne threat protection. As described in the Oracle document about security features, these message-level mechanisms provide protection over and above transient application layer security such as SSL/TLS. Therefore, the specification can help to ensure a secure exchange of data between users. ebXML security: https://www.oracle.com/technical-resources/articles/enterprise-architecture/ebxml-security1.html ebXML RegRep OASIS reference: https://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html'
'IPv6 incorporates some security and privacy-adressed extensions. In addition, there are extension headers, each identified with a different Next Header value, which allow additional features and better flexibility. In addition, an IPv6 packet may carry zero, one, or more extension headers. IPv6 extension: https://www.rfc-editor.org/rfc/rfc2460#section-4'
'The specification allows certain functions to be executed, enabling an XFDL form to perform procedural operations. These operations are optional, not mandatory, which allows XFDL to adapt more effectively to various contexts. Extensible Forms Description Language reference: https://www.w3.org/TR/NOTE-XFDL'
The purpose of SAML 2.0 is not related to the delivery of multilingual public services. Therefore, this criterion is not applicable to the specification.
'ETSI TS 119 511 can be mapped in the EIRA Library of Interoperability Specifications (ELIS), more specifically in the Technical application view, as part of the "Trust Service Provisioning Component" ABB. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/v500'
'WAI-ARIA has the Web Accessibility Initiative - Communities of Practice (WAI-COOP) platform for sharing results and best practices. Therefore, the specification encourages the creation of open information about the specification and encourages relevant communities to share their results at the European level. WAI-COOP reference: https://www.w3.org/WAI/about/projects/wai-coop/'
There are several existing documents and studies assessing SAML 2.0 features and capabilities and efficiency. Broadly speaking, the studies are focused on the capability to enable Single Sign-on and its benefits. See: https://www.researchgate.net/publication/221609828_Formal_analysis_of_SAML_20_web_browser_single_sign-on https://www.researchgate.net/publication/45872317_Web_single_sign-on_authentication_using_SAML
'There is no Member State that includes HTTP Cookies in their national catalogue with The National Interoperability Framework (NIF) in alignment with the three categories 1. Conceptual model for integrated public services provision, 2. interoperability layers, and 3. interoperability principles. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
'SAREF indirectly aids in long-term preservation by providing a standardised way to describe the functionalities and interactions of smart appliances in the context of the IoT, facilitating its accessibility and understanding over time. SAREF: https://saref.etsi.org/core/v3.1.1/ '
'After being evaluated compliant with the regulation on standardisation 1025/2012, CSV has been identified by Commission Implementing Decision and included in the European list of ICT Standards for e-procurement. CSV being compliant with 1025/2012 regulation Reference: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=celex%3A32012R1025'
'The classification scheme outlined in ISO/IEC 19944-1 is intended to be flexible and adaptable, allowing it to be applied across different cloud platforms and architectures. ISO/IEC 19944-1 specification: https://www.iso.org/standard/60545.html'
'An OAIS should take into account the intellectual property rights concepts, such as copyrights, patents and any other applicable laws (e.g., data protection) prior to accepting restricted materials into the OAIS. It can establish guidelines for ingestion of information and rules for dissemination and duplication of the information when necessary. Nonetheless it does not explicitly address GDPR compliance. OAIS specification: https://public.ccsds.org/Pubs/650x0m2.pdf'
The specification has been selected within the scope of LEOS project to develop the LEOS software, which aims to ease the drafting and edition of legal documents. LEOS: https://joinup.ec.europa.eu/collection/justice-law-and-security/solution/leos-open-source-software-editing-legislation
'IPsec is a business domain agnostic specification and therefore can be used in any domain. List of IPSec Implementations: http://www.mit.edu/~tytso/ipsec/surv9607.html'
'As a solution developed by the SEMIC action of the ISA2 Programme funded by the European Commission, DCAT-AP is part of their supra-national catalogue of reusable solutions. SEMIC repository of specifications - DCAT-AP: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/our-solutions ISA2 Solutions: https://ec.europa.eu/isa2/solutions_en'
The purpose of HTML5 is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification.
'Open & Agile Smart Cities & Communities (OASC) are an international network of cities and communities that partners with local administrations of all sizes and all over the world to assist them in their journey towards digital transformation. They facilitate seamless sharing and re-use of digital, data-driven solutions to avoid vendor lock-in, to reduce innovation costs and improve efficiency, thanks to open standards and APIs (application programming interfaces). One of the standards mentioned in their blog is CIM NGSI-LD API, particularly how it targets Smart City applications and government services, which is an indicative evidence of its positive market uptake. ETSI Releases Full-Feature Specification to Support Smart Cities & Communities: https://oascities.org/etsi-release-full-feature-specification-to-support-smart-cities-communities/'
"There are not specific assessments nor any deployment use case evaluating the specification's effectivenes. TOSCA reference: https://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.3/os/TOSCA-Simple-Profile-YAML-v1.3-os.html"
No regulation has been found directly mentioning CAdES as a subject of the agreement. Despite this, eiDAS regulation is focused on electronic identification and trust services for electronic transactions. CAdES Baseline profile is specifying the profile of CMS signed-data on the context of the European Internal Market. Moreover, it is compliant with eiDAS regulation, a key enabler on the trustworthy data exchange across borders. See: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv%3AOJ.L_.2014.257.01.0073.01.ENG https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=celex%3A32006L0123
'CPSV-AP is a European Standard as it was developed and recognized by the European standards organisations; it is also maintained by the EU community. CPSV-AP Joinup webpage: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/core-public-service-vocabulary-application-profile/release/22'
'The XML specification itself does not provide built-in mechanisms for guaranteeing the authenticity and authentication of the roles or agents involved in data transactions. Therefore this criterion is not applicable to the specification.'
Even WS-BPEL is fostering the first level of maturity provided by Tim Berners-Lee's 5 stars schema for publication of Open data, it is not supports the principles to be considered as fostering actor on publishing Linked Open Data.
The purpose of the specification addresses and facilitates the exchanging of information. By allowing to make web services available and the data exchange between systems from administrations and stakeholders, SOAP fosters the reduction of administrative burden.
'The purpose of this specification is not related to e-accessibility. Therefore, this criterion is considered not applicable to this specification. LDES specification: https://joinup.ec.europa.eu/collection/semic-support-centre/linked-data-event-streams-ldes'
'OData services return URLs to identify resources requested by clients. Where possible, interoperability increases by exploiting the information found in the route part of the URL. However, attention must be paid to those URLs including custom transformations (that is, query options) and clients must be aware of it in future requests to the identified resource. OData reference, 6 Extensibility: http://docs.oasis-open.org/odata/odata/v4.0/errata03/os/complete/part1-protocol/odata-v4.0-errata03-os-part1-protocol-complete.html#_Toc453752211'
HTML is a markup languages to develop web documents and make them online to share and publish information. The specification supports the first level of maturity which corresponds to make data available on the Internet. So, the specification is aligned with the different levels of maturity of Tim Berners-Lee's 5-star schema for Open Data. HTML W3C reference: https://www.w3.org/TR/html401/ Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/en/
'GITB TDL allows the review and provision of feedback but there is no pre-release public review process defined. There is no direct evidence that a public review is conducted according to the GITB TDL documentation. GITB TDL reference: https://www.itb.ec.europa.eu/docs/tdl/latest/introduction/index.html#what-is-the-gitb-tdl'
'The TGF emphasizes the importance of clear and unambiguous definitions for data elements and process steps, which can help prevent errors and ensure consistent processing of data. In addition, the TGF supports the use of standards and protocols for data exchange and communication, which can help ensure the accuracy of data as it is transferred between systems and organiSations. TGF specification: http://docs.oasis-open.org/tgf/TGF/v2.0/cs01/TGF-v2.0-cs01.html'
"There are multiple mentions to the extension of XSD throughout the specification's documentation. XSD Reference: https://www.w3.org/TR/2012/REC-xmlschema11-1-20120405/"
"The specification is included in 1 Member State' catalogue of recommended specifications. This Member State is Spain. National catalogue Spain: https://administracionelectronica.gob.es/pae_Home/dam/jcr:9e2c2877-5103-4934-8440-c60ba2e10c48/Catalogue_of_Standards_NIF_Spain.pdf CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards"
'After searching in different catalogues and repositories, there is no evidence found of ETSI EN 319 532-3 being included in the catalogue of any Member State or the List of Standards. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards '
'The purpose of IPv4 is not related to e-accessibility. Therefore this criterion is considered not applicable to the specification. IPv4 IETF: https://www.rfc-editor.org/rfc/rfc791'
The Web Services Security (WS-Security) main function is to reinforce integrity and confidentiality of the messages used by SOAP specification. Therefore, this criterion is not applicable to the specification.
'Linked Data Event Streams offers a service to help e-Government professionals share their experience with each other, so it fosters the creation of innovative solutions. By making data accessible via one URI endpoint, LDES makes it easy to retrieve data which is published as a uniform linked data standard. LDES specification: https://joinup.ec.europa.eu/collection/semic-support-centre/linked-data-event-streams-ldes'
'To ensure information is protected against unauthorised changes, UTF-8 needs to use additional security measures that may include digital signatures or encryption mechanisms. UTF-8 specification: https://datatracker.ietf.org/doc/html/rfc3629 Integrity constraints to UTF-8: https://documentation.sas.com/doc/en/pgmsascdc/9.4_3.5/viyadatamig/p03xdtcn8yshoan1f26is9okzn4p.htm '
Betterr Regulation Toolbox can be found for free on the European Comission webpage. Better Regulation Toolbox reference: https://ec.europa.eu/info/sites/info/files/better-regulation-toolbox_2.pdf
The purpose of ODF is not related to e-accessibility. Therefore, this criterion is not applicable to the specification. ODF ISO reference: https://www.iso.org/standard/66363.html ODF OASIS reference: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office
'The specification has been found included in two Member States National catalogue: Slovenia and Ireland. It is also added in Cyprus even though the NIFO factsheet of Cyprus is not fully compliant with the EIF. All three countries that the specification has been found in, comply with middle-upper performance than stated in the Digital Public Administration Factsheets. CAMSS List of Standards 2022 https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
'By testing the requirements established in ETSI TS 119 612, which aims to enable trusted list for validating the stutus of services, the specification helps to enhance and upgrade the delivery of digital service delivery channels. ETSI TS 119 614-1 reference: https://www.etsi.org/deliver/etsi_ts/119600_119699/11961401/01.01.01_60/ts_11961401v010101p.pdf'
The purpose of TLS 1.2 is not related to the delivery of multilingual European public services. Therefore this criterion is considered not applicable specification.
XACML is the basis of the Polocy Management impelemented by the cross-border project SEMINARIS. This projects aims to provide e-services with the required underlying secure authentication and management approach Semiramis home page: https://joinup.ec.europa.eu/solution/semiramis/about
'As most of the vocabularies, DCAT reuses several existing ones (e.g. "adms", "foaf") and the Resource Description Framework (RDF). This results in a dependency that can hamper interoperability, especially in the case where new releases of the reused vocabularies are not backward compatible. DCAT (v2.0.0) reference: https://www.w3.org/TR/vocab-dcat-2/ ADMS reference: https://www.w3.org/TR/vocab-adms/ FOAF reference: http://xmlns.com/foaf/0.1/'
XAdES Baseline Profile function is to facilitate the electronic signature in compliance with eIDAS, so it can be concluded that through it processes, data and services are fostered.
DCAT-AP has a strong support from different communities. In fact, it is a joint initiative of: • The DCAT-AP Working Group; the Directorate-General for Informatics: DG • DIGIT - in particular the SEMIC action of the ISA² programme; the Directorate-General for Communications Networks, Content & • Technology: DG CONNECT; and • The Publications Office of the EU. See: https://joinup.ec.europa.eu/solution/dcat-application-profile-data-portals-europe/about https://ec.europa.eu/isa2/sites/isa/files/leaflet_dcat-ap_lr_v13.pdf
W3C has a defined and publicly available Process for the Development and approval process of the specification as a recommended standard, including a public review. W3C Process document: https://www.w3.org/TR/xslt-30/
Taking the initial purpose of the specification, it can be considered that the specification is involved in fostering the comprehensibility of Public Administrations data as well as relevant data produced for the decision-making process. EuroVoc webpage: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/eurovoc
FTP is already associated to EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, FTP can define the interoperability aspects of the "Network", "Network Service", "Private Network" and "Public Network" ABBs of the EIRA Technical View. See: https://joinup.ec.europa.eu/solution/elis/distribution/eliscataloguev100betaxlsx
' Assessments of the efficiency of W3C Verifiable Credentials primarily involve evaluating the performance, scalability, and practicality of implementations. Real-world Implementations provide valuable insights into how Verifiable Credentials perform in diverse use cases and environments and the W3C Working Group has published a collection of those: Verifiable Credentials Use Cases: https://www.w3.org/TR/vc-use-cases/'
'The iCalendar specification allows for extension through the use of custom properties, parameters, and non-standard components. This extensibility enables developers to add new features or attributes beyond the core standard to meet specific needs or to support additional functionalities. iCalendar specification: https://www.rfc-editor.org/rfc/rfc5545'
SMTP is maintained and developed by IETF which is an international community developing open standards. Developer community IETF: https://www.ietf.org/about/
'ETSI TS 119 612 supports digital signatures and other trust services, which rely on strong authentication methods to verify the identity of the individuals or entities involved in a transaction. These mechanisms help ensure that only authorised individuals can perform actions like signing or accessing data. ETSI TS 119 612: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf'
'The PROV family of documents is designed to promote data portability through interoperability, support data exchange through various serialization formats, allow for semantic alignment with other ontologies, and enables customization and extensions to meet specific service requirements, it can be stated that it can support the implementation or evolution of European public services. PROV Primer document: https://www.w3.org/TR/prov-primer/'
'The specification has an application profile that addresses e-accesibility, supported by DCMI Accessibility Community, which main focus is to ensure that DC metadata users can describe resources and services in a way that will increase the accessibility of information for everyone. This supports the "AccessForAll" approach to accessibility that differs from previous reliance solely on good resource design and construction. DCMI About: https://www.dublincore.org/about/ DCMI Accessibility Community: https://www.dublincore.org/groups/access/'
HTTPS is a sector agnostic specification.
Understanding data exchange as the publication by the administration of data for its later consumption by citizens, the specification facilitates the trustworthy data exhange in RDF format by providing the means to validate RDF data graphs.
OpenPM2 is a Project Management Methodology developed by the European Commission. Its purpose is to enable Project Managers (PMs) to deliver solutions and benefits to their organisations by effectively managing the entire lifecycle of their project. PM2 has been created with the needs of European Union Institutions and projects in mind but is transferable to projects in any organisation. OpenPM2 specification reference: https://op.europa.eu/en/publication-detail/-/publication/ac3e118a-cb6e-11e8-9424-01aa75ed71a1/language-en/format-PDF/source-83307127
'After checking the different standard catalogues at supra-national level, there is no evidence of GITB TDL as a European standard. ICT technical specifications: https://ec.europa.eu/growth/single-market/european-standards/ict-standardisation/ict-technical-specifications_en CENELEC and CEN search tool catalogue: https://standards.cencenelec.eu/dyn/www/f?p=CEN:105::RESET::::'
There is no national or European platform with the specification XAdES (ISO 14533-2:2012) available for free. However, there are some free documents in Joinup that covers XAdES digital signatures - Testing Conformance and Interoperability. XAdES Joinup reference: https://joinup.ec.europa.eu/solution/etsi-tr-119-134-series-electronic-signatures-and-infrastructures-esi-xades-digital-signatures
'ISO/IEC 7498:1 has a specific section called "Transport Layer" whose purpose is to provide transparent transfer of data between session-entities and relieves them from any concern with the detailed way in which reliable and cost effective transfer of data is achieved. ISO/IEC 7498:1: https://www.iso.org/standard/20269.html'
'SFIA has been adopted by governments, companies and individuals since its inception in 2000. For example, at European level SFIA has been mapped to the e-Competence Framework (see SFIA reference, Standard skills profiles section, EU ICT Role Profiles subsection). In addition, SFIA has created a worldwide community of users for the collaborative development of the specification. SFIA has not only been kept relevant through open consultation, but also has been updated every few years to address the changing needs of industry and business. In addition, the maintenance of SFIA is carried out with the support of relevant stakeholders in governmental organisations world-wide (see SFIA reference, Standard skills profiles section, USA National Initiative for Cybersecurity Education (NICE) subsection). SFIA reference, Standard skills profiles section, EU ICT Role Profiles subsection: https://sfia-online.org/en/tools-and-resources/standard-industry-skills-profiles/european-union/eu-ict-role-profiles SFIA reference, About SFIA section: https://sfia-online.org/en/about-sfia SFIA reference, Standard skills profiles section, USA National Initiative for Cybersecurity Education (NICE) subsection: https://sfia-online.org/en/tools-and-resources/standard-industry-skills-profiles/usa-national-initiative-for-cybersecurity-education-nice-work-roles'
By providing style, the CSS is an asset that when used properly could help to enhance and ease the accessibility of disabled people. It could help to provide context and support the functionalities of the web design. Moreover, the Regional Government of Bizkaia developed his website to promote the integration of groups with disabilities into the Public Administration of Bizkaia. They used XHTML 1.0 recommendations and CSS2. CSS and JavaScript accessibility best practices: https://developer.mozilla.org/en-US/docs/Learn/Accessibility/CSS_and_JavaScript CSS2 implemented in e-accessability project: https://joinup.ec.europa.eu/collection/einclusion/document/eaccesibility-public-administration-bizkaia-bizkaianet
'The purpose of NUTS is not related to e-accessibility. Therefore, this criterion does not apply to this specification. EUROSTAT reference, NUTS Principles and Characteristics section: https://ec.europa.eu/eurostat/web/nuts/principles-and-characteristics'
The specification is a widely used de-facto standard. Thus, it is sufficiently mature for the development of products and services. Since it's recommendation by W3c in 1996, XML has been used by many products and services. See: https://www.w3.org/TR/2006/REC-xml11-20060816/
By easing the creation of secured web services, XACML contributes to the increment of digital public services between administrations and stakeholders and among administrations. This public services can include Secure Data Transfer amongst other services. XACML OASIS reference: http://docs.oasis-open.org/xacml/3.0/errata01/xacml-3.0-core-spec-errata01.html SEMIRAMIS project: https://joinup.ec.europa.eu/solution/semiramis/about
'There are already existing tools for testing the implementation of XACML policies. The Security Pool Policy allow to check for enhancements in a XACML implementation. Also, a tool known as WS2 Identity Server is available under its own licence to allow the testing of XACML implementations. Furthermore, XACML defines conformance provisions in section 10. XACML OASIS reference: https://docs.oasis-open.org/xacml/3.0/xacml-3.0-core-spec-os-en.html WS2 Identity Server https://docs.wso2.com/display/IS541/Using+the+XACML+TryIt+Tool '
"In the specification's documentation section 5.6.2 it is explained how the SMP 2.0 can restrict access to information and data. SMP OASIS reference, section 5.6.2 about how to restrict access to information: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505052"
'ISO 19944-1 is not related to e-accesibility. Therefore, this criterion is not applicable to the specification. ISO/IEC 19944-1 specification: https://www.iso.org/standard/60545.html'
'There is no Member State that includes ETSI EN 319 532-3 in their national catalogue with its National Interoperability Framework (NIF) in alignment with the three categories: 1. Conceptual model for integrated public services provision, 2. interoperability layers, and 3. interoperability principles. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
SAMM is licensed under CC, which essentially means that the commercial use of the work and possible derivative works is allowed, the distribution of which must be done with a license equal to the one that regulates the original work. SAMM webpage: https://owaspsamm.org/ SAMM documentation: https://github.com/OWASP/samm/blob/master/Supporting%20Resources/v2.0/OWASP-SAMM-v2.0.pdf
The purpose of IPsec is not related to the delivery of multilingual European public services. Therefore this criterion is considered not applicable specification.
CSS v2.1 is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, CSS can define the interoperability aspects of the "Human Interface" ABB of the EIRA Technical Application View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/solution/elis/release/v100
' SCIM is designed to facilitate the exchange of identity information between identity providers and service providers, which can be valuable for data portability scenarios between systems and applications, including those supporting the implementation or evolution of European public services. While SCIM is primarily designed for managing identity information, its features can contribute to data portability in the context of user identities within the European public services framework. SCIM: https://scim.cloud/'
'By allowing communications over the internet, IPv6 contributes to the exchange of information between public administrations. Therefore, it reduces administrative burden. IPv6 IETF: https://www.rfc-editor.org/rfc/rfc2460'
WS-BPEL is maintained and developed by OASIS which is an international community developing open standards. Developer community OASIS: https://www.oasis-open.org/org/
"JSON is available for its use, study and implementation at Ecma International and IETF's webpages. Moreover, Ecma International's purpose is to make available the developed standards and specifications in a non-discriminatory and free of charges. Therefore, JSON is licensed under (F)RAND and Royalty-free basis. Terms and conditions for IPR disclosures can be found in Ecma's webpage. ECMA IPR: http://www.ecma-international.org/memento/Ecma%20IPR%20policies.htm JSON specification in ECMA webpage: https://www.ecma-international.org/publications/standards/Ecma-404.htm JSON specification in IETF: https://tools.ietf.org/html/rfc8259 "
The adoption of PDF/A as a document format for exchanging information does not hamper the scalability of systems. It is a widely adopted and used for this purpose and, moreover, it is independent of any platform or software. Therefore, PDF/A is proportionate to the users' needs and at the same time, it does not hamper the interoperability and scalability of systems.
PNG is a file format that allows to save images digitally. This fact allows administrations to share digital content among others and with the stakeholders. Allowing the exchange of visual information can help administrations to spread information all over the Internet avoiding having paper images, which reduces the administrative burden. PNG W3C reference: https://www.w3.org/TR/PNG/ PNG ISO reference: https://www.iso.org/standard/29581.html
'The Data Spaces Business Alliance (DSBA) aims to converge the best skills, assets, and experience in Europe into a one-stop-shop for data spaces, from inception to deployment. The Data Spaces Business Alliance are Gaia-X European Association for Data and Cloud AISBL, the Big Data Value Association (BDVA), FIWARE Foundation, and the International Data Spaces Association (IDSA), who created and currently maintains the Dataspace Protocol. With this cross-industry expertise, resources and know-how, the Alliance drives awareness, evangelizes technology, shapes standards, and enables integration across industries. Data Spaces Business Alliance (DSBA): https://data-spaces-business-alliance.eu/'
'The purpose of ISO 639-2 is not related to security and privacy of the data exchange. Therefore, this criterion is not applicable to this specification. ISO 639-2 reference: https://www.iso.org/standard/4767.html'
"All schema.org releases provide for public review. Changes to the schema.org specification are proposed, discussed, prepared and reviewed by the schema.org Community Group and ultimately reviewed and published by the Steering Group, which holds the final decision. Collected feedback is also available through the schema.org Github (see Schema.org-W3 Github reference, Issues section). Schema.org homepage reference, 'About Schema.org' section: https://schema.org/docs/about.html Schema.org-W3 Github reference, Issues section: https://github.com/schemaorg/schemaorg/issues"
'XML can enable digital service delivery channels. By using XML to structure and share data, organizations can make it easier for customers to access their services through digital channels like websites, mobile apps, and APIs. As a use-case example a government agency could use XML to make their services available online. By structuring their service data using XML and providing APIs for accessing that data, they could enable citizens to access and interact with government services through digital channels. See: https://www.w3.org/TR/2006/REC-xml11-20060816/'
The specification in itself does not include security features, but the security considerations aim to put together the benefits of the WS-BPEL and the WS-Security specifications, that can be used to secure the Web services transactions. Therefore, it can be said that the orchestration of web services combining both specifications can ensure the trustworthy data exchange between administrations and stakeholders. The specification: http://docs.oasis-open.org/wsbpel/2.0/OS/wsbpel-v2.0-OS.html
'The purpose of En 303 645 specification is not related to the implementation of the once-only principle. Therefore, this criterion does not apply to this specification. EN 303 645 reference: https://www.etsi.org/deliver/etsi_en/303600_303699/303645/02.01.01_60/en_303645v020101p.pdf'
The European Public Sector Information platform assessed the impact of the use of DCAT for the European Open Data Catalogues. See: https://www.europeandataportal.eu/sites/default/files/2013_impact_of_standards_in_european_data_catalogues.pdf
'IDS have a method of certificating conformance to the IDS standards. IDS certification has two parts: First, the interested part needs to prove that the IDS component is built correctly. Second, they need to make sure their IDS component’s operational environment is supporting data sharing according to the requirements and rules. While the certification of operational environment focuses on security and trust, the component certification also ensures interoperability. IDS Certification: https://internationaldataspaces.org/offers/certification/'
'The PROV family of documents use in systems or applications can indirectly support security efforts through traceability, accountability, integrity, non-repudiation, auditing, and forensic analysis. However, implementing comprehensive security measures is essential for ensuring the secure exchange of data. PROV Primer document: https://www.w3.org/TR/prov-primer/ PROV Ontology: https://www.w3.org/TR/2013/REC-prov-o-20130430/ PROV Data Model: https://www.w3.org/TR/2013/REC-prov-dm-20130430/'
'The specification was developed in 1991 by the IETF group, and it has become a widely used format for the transaction of different types of files over the internet. It is focused on the transfer via email, and it is supported by numerous mail software. This fact demonstrates the maturity of MIME for its use for the development of services and products. MIME specification: https://tools.ietf.org/html/rfc2045'
'The ISO 639-2 code suite was developed for its use by libraries, information services and publishers to indicate language in the exchange of information, especially in computerised systems. Indicating language in the exchange of information is becoming more necessary in the European cross-border context. ISO 369-2 FAQs: https://www.loc.gov/standards/iso639-2/faq.html#5'
'OData services are used by a large community of users. The OData protocol differs from other REST-based web services in that it provides a uniform way of describing both the data and the data model. OData should be implemented as a very basic and compliant service; in this sense, th specification is domain-agnostic, designed to be implemented in any domain. For example, there are the Cambridge Weather-Pyslet demo service and the City of Medicine Hat Open Data Portal, in the field of academics and medicine, respectively. OData ecosystem, Live services reference: https://www.odata.org/ecosystem/ OData reference, 2 Overview: http://docs.oasis-open.org/odata/odata/v4.0/errata03/os/complete/part1-protocol/odata-v4.0-errata03-os-part1-protocol-complete.html#_Toc453752201'
'Open reviews are an essential part of the verification process for eArchiving Building Block specification documentation. A review is a systematic examination of a document by experts and other stakeholders to find and remove errors early on in the specification life cycle. For example, the github issues channel from the CSIP is a tool used by anyone who wants to contribute to the development of the specification. Open review guidelines for eArchiving Building Block specifications and documentation: https://dilcis.eu/images/procedures/LC-001390244_CEF-TC_2019-3_M23c.pdf E-ARK CSIP Github isues: https://github.com/DILCISBoard/E-ARK-CSIP/issues '
'Schema.org provides a data model that allows modeling business processes within and beyond an organisation. Schema.org reference, Data model section: https://schema.org/docs/datamodel.html'
'The specification supports data exchange and business processes among partners. The specification is easy to implement into standard business processes. https://www.xbrl.org/int/gl/2016-12-01/gl-framework-2017-PWD-2016-12-01.html https://www.dropbox.com/sh/b5i8ehpnzzymowl/AACpTH-mWRwOFGIQkUYDbWoWa/29.10.2021%20Presentations?dl=0&preview=005_TietoEVRY_Symposium_29.10.2021.pdf&subfolder_nav_tracking=1 '
SOAP 1.2 is available for free at the European Collaborative platform for the development of ICT solutions. See: https://joinup.ec.europa.eu/solution/soap-version-12-part-0-primer
'To be able to make access control related decisions that are based on reliable identities and properties of Participants, a concept for Identity and Access Management (IAM) is mandatory. DAPS provides the International Data Spaces with identity management across companies according to modern standards with low organizational effort. DAPS: https://github.com/International-Data-Spaces-Association/IDS-G/tree/main/Components/IdentityProvider/DAPS'
'The specification can enable digital service delivery channels. SOAP is a protocol designed for exchanging structured information between systems over a network, and it can be utilized to facilitate communication between different components and systems involved in digital service delivery. SOAP Reference: https://www.w3.org/TR/soap12/'
'The syntax defined by GraphQL can indeed be implemented separately, depending on the specific needs and requirements of the cases for which the specification is being used. GraphQL specification: https://spec.graphql.org/October2021/#sec-Overview'
"The specification's schema is in rdf, which is one of the conditions to be linked open data. Dublin Core Ontology metadata using rdf: https://www.dublincore.org/specifications/dublin-core/dc-rdf/ Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/en/"
'The specification proposes optional extensions. Therefore, it can be considered that OCSP allows for partial implementation. OCSP reference, section 4: https://datatracker.ietf.org/doc/html/rfc2560'
'W3C has a page that collects implementations of the Data Quality Vocabulary, an RDF vocabulary which has been developed in the W3C Data on the Web Best Practices Group. For instance, a research group from the University of Leizpig has developed RDFUnit, which provides an API to generate DQV reports. DQV Implementations: https://www.w3.org/2013/dwbp/wiki/List_of_DQV_implementations RDFUnit: https://github.com/AKSW/RDFUnit/tree/master/rdfunit-w3c-dqv'
The scalability and broad character of the specification can make possible the creation and the availability of solutions fostering the reuse and availability of information between administrations and citizens. This fact demonstrates that the specification can foster the implementation of the once-only principle. The Standard for Public Code webpage: https://standard.publiccode.net/
'ISAE 3402 is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, ISAE 3402 can define the interoperability aspects of the Privacy Framework ABB of the EIRA Organisational View. ELIS reference: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /solution/elis/release/v110'
'The specification is domain-agnostic, its main purpose has to do with document exchange and therefore can be implemented in either public administrations or any other kind of organization. ETSI EN 319 532-3 reference: https://www.etsi.org/deliver/etsi_en/319500_319599/31953203/01.02.01_60/en_31953203v010201p.pdf'
No evidence has been found of the specification being included in a formal interoperability agreement between organisations involved in the European public services provision. However, LegalDocML has been included within the European Commission's Rolling Plan for ICT Standarisation and in the related standardisation activities of the same report. The European Commission includes in its Rolling Plan for ICT Standarisation: https://ec.europa.eu/digital-single-market/en/rolling-plan-ict-standardisation
'The IPv4 specification can utilise Access Control Lists (ACLs) to establish an access control mechanism and ensure that data is protected against unauthorised access. Packet filtering is a technique used to control network traffic and restrict access for specific users or devices. ACLs perform this filtering by evaluating traffic as it moves through a router or switch, allowing or blocking packets based on defined rules for specific interfaces or VLANs. IPv4 ACL: https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst2960l/software/15-2_6_e/configuration_guide/b_1526e_consolidated_2960l_cg/m_sec_acls_cg_danube_2960l_cdb.html'
'Open telemetry is an open source project where anyone interested can participate and get involved in its development. There is a mailing list communicating updates, and community meetings are held regularly. Moreover, there are special interest groups (SIGs) for specific contributions to the project. OpenTelemetry Community Content: https://github.com/open-telemetry/community'
'TSP is mentioned at "Commision decision of 25 February 2011 establishing minimum requirements for the cross-border processing of documents signed electronically by competent authorities under Directive 2006/123/EC of the European Parliament and of the Council on services in the internal market". In this document it is metioned that States should implement technical means which support signed documents in BES or EPES format. One of the technical means mentioned is TSP. Commision decision referene: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32011D0130&qid=1714025936203#ntc6-L_2011053ES.01006801-E0006 '
'Domibus is primarily an open-source software solution for secure electronic message exchange, and it adheres to messaging standards such as the AS4 (Applicability Statement 4) profile of the ebMS (ebXML Messaging Service) standard. While it may not be listed in an official national catalogue or standards repository, it is widely recognized and used within the context of eGovernment initiatives and secure data exchange in Europe. Domibus specification: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/Domibus AS4 Profile of ebMS 3.0: http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/profiles/AS4-profile/v1.0/AS4-profile-v1.0.html'
'There are many communities that share their data and results of their implementations of REST. Some examples of such communities can be found in the following links. 3CX community: https://www.3cx.com/community/threads/rest-api.74033/ DocuWare community forum: https://support.docuware.com/es-ES/forums/help-with-technical-problems/07aabc66-fcd2-ea11-bf22-00155d3d4054'
'GiITB TDL simplifies the delivery of European Public Services by contributing to the adoption of a multi-channel delivery approach. GITB TDL reference: https://www.itb.ec.europa.eu/docs/tdl/latest/introduction/index.html'
The purpose of this document is not related with data portability. Therefore, this criterion is not applicable to this specification. W3C reference: https://www.w3.org/TR/dwbp/
'The specification provides a standard format for representing legal documents that can facilitate the reuse of relevant information when needed. By using a standardized format, legal documents can be exchanged and processed by different systems and applications, which can help to ensure interoperability and avoid compatibility issues. AKN4EU reference: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/akn4eu'
'UTF-8 can play an important role in facilitating accurate representation and exchange of multilingual data and information, promoting inclusivity, and improving communication and interoperability in administrative contexts, thus, fostering comprehensibility of administrative procedures. UTF-8 specification: https://tools.ietf.org/html/rfc3629 '
'The purpose of PROV is not related to multilingualism. Therefore, this criterion is not applicable to the specfication. PROV Primer document: https://www.w3.org/TR/prov-primer/ PROV Ontology: https://www.w3.org/TR/2013/REC-prov-o-20130430/ PROV Data Model: https://www.w3.org/TR/2013/REC-prov-dm-20130430/'
'The specification defines how different parties and transactions have to be done in order to allow proper discoverability and data exchanges. Therefore, it is defining organisational requirements for the data transaction between two or more parties. SMP OASIS reference: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505009'
XML is a markup language that was designed to store and transport data, and defines a set of rules for encoding documents in a human-readable format and machine-readable format. XML is appropriate to areas of applications like IoT requiring lightweight payloads of data and is applicable to any business domain. However, it is worth noting that XML has some limitations with heavier amounts of data due to the time consuming process for parsing and validating of data expressed in XML.
The purpose of WS-Security is not related to the long-term preservation of electronic records and other kinds of information. Therefore, this criterion is not applicable to the specification.
'HTTPS itself does not facilitate organizational interoperability agreements directly. However, its secure and standardized communication channel can support interoperability efforts by ensuring secure data transmission, standardization, authentication, and compliance with regulations. Interoperability agreements require additional efforts and coordination beyond HTTPS implementation. HTTPS specification: https://tools.ietf.org/html/rfc2818'
'The XFDL specification does not directly handle the authentication of role agents involved in data transactions. However, it supports digital signatures, which ensure the authenticity of the data and verify the identity of the signer. By using a digital signature, public administrations can confirm that the form data has not been tampered with and that it was signed by an authorised agent. This aligns with the XML Signature Syntax and Processing specification, which provides a standardised method for generating and verifying digital signatures in XML documents, ensuring the integrity and authenticity of the data, as well as the identity of the signer within a secure, interoperable framework. XML Signature Syntax and Processing reference: https://www.w3.org/TR/xmldsig-core1/ XFDL security reference: https://www.w3.org/TR/NOTE-XFDL#button'
By providing interoperable vocabulary, model and encoding mechanisms, the specification contributes to the standardisation of the statements and conditions of use for public services and improves the comprehensibility of administrative services. It is a valuable tool for the cross-border decision-making process. W3C specification reference: https://www.w3.org/TR/odrl-vocab/#vocab-core
'TLS 1.3 offers several improvements over TLS 1.2. Major differences include a notably faster connection between client and server, the TLS handshake, and simpler, more secure cipher suites, sets of algorithms such as AEAD algorithms that secure a network connection during the handshake. It also introduces 0-RTT (Zero Round-Trip Time), enabling faster connection establishment for some data. These changes, amongst others, provide improved performance and stronger security between client and server. At the time of doing this assessment, there is currently a draft from February 2025 pending to review. This draft aims to refine and improve the existing TLS 1.3 standard, ensuring it remains secure, efficient, and interoperable in the long term. TLS 1.3 2025 Draft Reference: https://www.ietf.org/archive/id/draft-ietf-tls-rfc8446bis-12.html TLS 1.3 2018 Reference: https://www.rfc-editor.org/rfc/rfc8446.html'
The specification is aimed to represent public ontologies in order to be readable in both formats, machine-readable, and human-readable format. However, OWL2 does not help the availability of interfaces with internal information. OWL2 W3C reference: https://www.w3.org/TR/owl2-overview/
CAMSS Assessment of MIME EIF Scenario v1.0.0
According to the 5 star Open Data model suggested by Tim Berners-Lee about how to publish linked data, the second star corresponds to make data available as structured data, an area of application of XML. Additionally, RDF is a W3C specification that defines XML syntax for RDF, the de facto standard for publishing Linked Open Data. See: https://5stardata.info/en/ https://www.w3.org/TR/rdf-syntax-grammar/
The European Commission includes in its Rolling Plan for ICT Standardisation and in the related standardisation activities of the same rolling plan. The specification has sufficient market acceptance for its use in the development of products and services. The inclusion as basis for LEOS supports the fact that the specification has sufficient market acceptance according to the target audince. In addition, The LegalDocML TC works to advance worldwide best practices for the use of XML within a Parliaments', Assembly's or Congress' document management processes, within courts' and tribunals' judgment management systems, and generally in legal documents including contracts. The European Commission includes in its Rolling Plan for ICT Standarisation: https://ec.europa.eu/digital-single-market/en/rolling-plan-ict-standardisation LegalDocML reference: https://www.oasis-open.org/committees/legaldocml/charter.php
IPv6 is included in 4 national catalogues, which belong to Member States which comply with at least 4 out of 5 sections of the EIF according to the NIFO factsheets. See: https://www.forumstandaardisatie.nl/open-standaarden/lijst https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'Given that the aim of the DPV is to become a standard data model and vocabulary to be used across Europe, it is designed to support most of the languages used in the European Union. DPV specification: https://w3c.github.io/dpv/primer/'
"The iCalendar specification allows for partial implementations, giving developers the flexibility to support specific subsets of the standard according to their application's needs. iCalendar specification: https://www.rfc-editor.org/rfc/rfc5545"
By defining common vocabulary that can be expressed in a machine-readable format, the specification can foster the exchange of data between administrations and systems supporting its implementation. W3C specification reference: https://www.w3.org/TR/odrl-vocab/#vocab-core
'The specification aggregate data from multiple UI components in order to not repeat code or queries to get the desired data. GraphQL Multiple UI Site: https://graphql.org/learn/queries/#fragments'
'The SHACL specification can be found assessed and discussed in different forums. In example, we can mention the Netherlands Standardisation Forum, where the specification is assessed. In addition, there are many papers discussing SHACL and how it can be implemented. Netherlands Standardisation Forum SHACL: https://www.forumstandaardisatie.nl/open-standaarden/shacl SHACL W3C reference: https://www.w3.org/TR/shacl/'
'Domibus is not a European standard in the sense of being an official standardization document or specification issued by a recognized European standardization organization. However, it is treated as such given that it is an important component from the eDelivery building block. regarded as an eIDAS regulation enabler. Digital Europe eDelivery: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/eDelivery Domibus specification: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/Domibus'
'While the CSIP does not explicitly focus on the secure processing of data, its adherence to open standards, inclusion of administrative metadata, and alignment with best practices can indirectly support the secure processing of data. Organizations implementing the CSIP should complement it with appropriate security measures, encryption, access controls, and compliance with data protection regulations to ensure secure data processing. E-ARK CSIP specification: https://earkcsip.dilcis.eu/#introduction'
'The puropse of ETSI TS 119 512 is not related to the publication of open data, therefore this criterion is not applicable to the specification. ETSI TS 119 512 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.02_60/ts_119512v010102p.pdf Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/en/'
'XHTML has some features to prevent possible security vulnerabilities. Moreover, by allowing to exchange data via online websites, XHTML fosters the secure and trustworthy data exchange between administrations and stakeholders. XHTML W3C reference: https://www.w3.org/TR/xhtml1/'
'EN 319 532 is a European standard, delivered by a European Standardisation organisation (ETSI), according to the specification documentation. ETSI EN 319 532-3 reference: https://www.etsi.org/deliver/etsi_en/319500_319599/31953203/01.02.01_60/en_31953203v010201p.pdf '
'After being evaluated compliant with the regulation on standardisation 1025/2012, UTF-8 has been identified by Commission Implementing Decision and included in the European list of ICT Standards for e-procurement. Identified Standards for Procurement: https://joinup.ec.europa.eu/collection/ict-standards-procurement/identified-ict-specifications-procurement '
The purpose of EuroVoc is related to the delivery of multilingual public services. By establishing language equivalences between identical concepts expressed in different languages, it allows documents to be indexed in the language of the documentalist and searches to be made in the user’s language; EuroVoc webpage: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/eurovoc
"The SMP eases and fosters the discoverability of administrations data or services to others that can be administrations or other stakeholders. Easing this communication the specification allows different parties to discover others' capabilities and information to exchange documents amongst them. This fact increases the visibility of administrations' data and also improves and helps the decision-making processes. SMP OASIS reference: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505009"
WSDL was developed by IBM, Microsoft, and Ariba initially in 2000. The following version was at their charge as well, introducing minor changes. The last version became a W3C recommendation in 2007. Nowadays, the international organisation is maintaining and developing WSDL. Moreover, it continues having support from companies with a wide market share. Therefore, it is demonstrated that WSDL has enough market acceptance and maturity for its use in the development of products and services.
'After checking the different standard catalogues at supra-national level, there is no evidence of OCSP as a European standard. ICT technical specifications: https://ec.europa.eu/growth/single-market/european-standards/ict-standardisation/ict-technicalspecifications_ en CENELEC and CEN search tool catalogue: https://standards.cencenelec.eu/dyn/www/f?p=CEN:105::RESET::::'
"Participation in ISO technical committee work is possible, depending on the membership category of the participant. Public reviews are not foreseen, provided that the Public Administration was a subscriber member. ISO membership manual, 'ISO member rights, good practice and obligations' section: https://www.iso.org/publication/PUB100399.html"
'The specification was originally created by Facebook. In 2015 it became open and it is now supported by its own community in GraphQL Foundation. GraphQL FAQ Website: https://graphql.org/faq/#who-founded-the-organization'
'The purpose of EN 16234-1 e-CF is not related to the visibility of administrative procedures, rules data and services. Therefore, this criterion is not applicable to this specification. CEN reference, CEN/TC 428 - ICT Professionalism and Digital Competences (Published standards), EN 16234-1 e-CF: https://standards.cencenelec.eu/dyn/www/f?p=205:110:0::::FSP_PROJECT:67073&cs=15E62ED24D608A5F10D6BEE8E6D50FA10'
At the time of elaborating this assessment, DCAT is extensively used to create innovative linked open data solutions. Especially by public administration looking forward to foster cross-border interoperability and transparency.
'SAML 2.0 primarily facilitates authentication through Single Sign-On (SSO). However, its assertions can include user attributes and roles, which Service Providers can leverage for access control decisions. Thus, while SSO simplifies the login process, SAML 2.0 also indirectly aids in implementing access control mechanisms. SAML 2.0 Reference: http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-tech-overview-2.0.html'
"The uniform interface constraint is fundamental to the design of any RESTful system. It simplifies and decouples the architecture, which enables each part to evolve indepently. For that reason, REST architectural style ensures standarized transfer of information between softwares, thus enabling the exposure of interfaces. REST reference: https://restfulapi.net/rest-architectural-constraints/#uniform-interface REST Chapter 5 from Roy Fielding's dissertation: https://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm"
'No Member States have been found recommending Syslog in their ICT National Catalogues. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards'
'XML is included in 5 national catalogues. They belong to Member States which comply with at least 4 out of 5 sections of the EIF according to the NIFO factsheets. See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
The specification is included in 3 Member States' catalogues of recommended specifications. This Member States are France, the Netherlands and Spain. National catalogue France: http://references.modernisation.gouv.fr/sites/default/files/Referentiel_General_Interoperabilite_V2.pdf National catalogue the Netherlands: https://www.forumstandaardisatie.nl/open-standaarden National catalogue Spain: https://administracionelectronica.gob.es/pae_Home/pae_Estrategias/pae_Interoperabilidad_Inicio/pae_Normas_tecnicas_de_interoperabilidad.html#CATALOGOESTANDARES
PAdES is relying on PDF to verify and validate signed PDF format documents. Despite this fact, PDF is a widely adopted format for data exchange and this dependancy, thus it does not hamper its adoption.
'In ETSI TS 119 512, there are different profiles of preservation schemes, but without mentioning whether they can be implemented independently. Moreover a preservation service may support different preservation schemes, which define the general approach for preservation. ETSI TS 119 512 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.02_60/ts_119512v010102p.pdf'
'The AMQP specification documentation suggests it is sufficiently mature for use in the development of digital solutions and services. The standard continues to be maintained and advanced by the OASIS AMQP TC. While companies like Microsoft, Red Hat, and Software AG support AMQP in their products and see it being used in various scenarios. Furthermore, AMQP has been approved for release as an ISO and IEC International Standard with the designation ISO/IEC 19464. AMQP blog reference: https://www.oasis-open.org/2014/05/01/iso-and-iec-approve-oasis-amqp-advanced-message-queuing-protocol/ AMQP TC reference: https://groups.oasis-open.org/communities/tc-community-home2?CommunityKey=969c2da1-55c4-4bba-92d2-018dc7d3efe9 ISO/IEC 19464 reference: https://www.iso.org/standard/64955.html OASIS AMQP Reference: http://docs.oasis-open.org/amqp/core/v1.0/amqp-core-complete-v1.0.pdf'
ADMS helps to search, identify, retrieve, compare semantic assets to be reused by public administrations, it can help to reduce the administrative burden related to the development and design of solutions. ADMS on Joinup: https://joinup.ec.europa.eu/solution/asset-description-metadata-schema-adms/about ADMS Specification W3C: https://www.w3.org/TR/vocab-adms/
'Currently no member state has included the specification on its national catalogue. CAMSS list of standads: https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
"In the context of the implementation of the persistent URI policy for EU institutions, NUTS contributes to the simplification of delivery of European public services as the NUTS classification allows to link data files (datasets) to a specific region, enchancing data discovery within the EU via HTTP scheme. EUROSTAT reference, NUTS Principles and Characteristics section: https://ec.europa.eu/eurostat/web/nuts/principles-and-characteristics ISA Programme-Joinup reference, 'Revise the NUTS RDF model' document: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/document/supporting-implementation-persistent-uri-policy-eu-institutions"
'Given that it has been developed by the International Organization for Standardization (ISO), ISO/IEC19944-1 is not considered to be a European standard. ISO/IEC 19944-1 specification: https://www.iso.org/standard/60545.html'
'TOSCA offers the possibility to manage and orchestrate resources for the provisioning of cloud applications and services. In this sense, when combined with other specifications, the specification enables visibility of data and services. TOSCA reference, section 1.2: https://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.3/os/TOSCA-Simple-Profile-YAML-v1.3-os.html#_Toc26969412'
There are several studies assessing the adoption, strengths, weaknesses, effectiveness and efficiency of FTP. See: https://dzone.com/articles/potential-downsides-of-using-an-ftp-solution https://themanifest.com/development/how-evaluate-your-file-transfer-protocol-system https://sapinsider.wispubs.com/Assets/Articles/2012/January/Using-FTP-Know-The-Risks
'In order to maintain the confidentiality, integrity and availability of information, ISO/IEC 27001 defines the standards on which the long-term preservation of data must be carried out so that it is stored in a secure manner in accordance with information security management systems. ISO/IEC 27001 reference website: https://www.iso.org/standard/54534.html'
After checking the different standard catalogues at supra-national level, there is no evidence of the inclusion of this Core Vocabulary within any European catalogue of standards. ICT technical specifications: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en CEN search tool catalogue: https://standards.cen.eu/dyn/www/f?p=CENWEB:105::RESET:::: CENELEC search tool catalogue: https://www.cenelec.eu/dyn/www/f?p=104:107:0::::FSP_LANG_ID:25
'The purpose of TLS 1.3 is not related to the delivery of multilingual services. Therefore this criterion is not applicable to this specification. TLS 1.3 Presentation Language: https://www.rfc-editor.org/rfc/rfc8446.html#section-3'
'Being a widely adopted framework for long-term preservation of digital information, it has been assessed by various organisations and academia groups. Find below an analysis of the feasibility of the OAIS model applied in small organisations, and a study assessing OAIS compliance for disaggregated preservation services. Preserving the cultural heritage: An investigation into the feasibility of the OAIS model for application in small organisations: https://www.emerald.com/insight/content/doi/10.1108/00012530610713597/full/html Modelling OAIS Compliance for Disaggregated Preservation Services: http://www.ijdc.net/index.php/ijdc/article/view/25'
The specification is used for the certification of time-stamps, which provides information about the creation or modifications of certain documentation or data, it can be used when archiving electronic records as a manner to preserve the integrity of such data. Therefore, the IETF 3161 Time Stamp Protocol (TSP) fosters the preservation of electronic documents by providing a mechanism for clearly identify time stamps for these electronic documents. TSP IETF reference: https://tools.ietf.org/html/rfc3161
By allowing public administrations to have online forms to interact with the population, Xforms fosters the visibility and comprehensibility of public administrations and services. Xforms 2.0 W3C reference: https://www.w3.org/community/xformsusers/wiki/XForms_2.0
The LegalRuleML is part of OASIS developer community. The main objective of the community is to promote individuals, organizations, and governments come together to solve some of the world’s biggest technical challenges through the development of open code and open standards LegalRuleML reference: http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/legalruleml-core-spec-v1.0.html OASIS home page: https://www.oasis-open.org/
​The Semantic Interoperability Community (SEMIC) develops solutions to help European public administrations perform seamless and meaningful cross-border and cross-domain data exchanges. They develop semantic specifications and interoperability solutions under the ISA² Programme. When a new solution release is finished, it is submitted for a public review with a minimum period of four weeks. Specification development process by the ISA Programme: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/document/description-change-management-release-and-publication-process-structural-metadata-specifications Detailed document ISA Programme: https://joinup.ec.europa.eu/sites/default/files/document/2016-10/description_of_a_change_management_release_and_publication_process_for_structural_metadata_specifications_developed_by_the_isa_progr.pdf
PDF 1.7 is not included at any European platform and has to be paid for its usage. However, Adobe has also made the specification available free of charge on the website, but notes that, although it has identical content, the document in question is not an official ISO document.
FTPS is maintained and developed by IETF which is an international community developing open standards. Developer community IETF: https://www.ietf.org/about/
'ETSI TS 119 432 specifies the protocols semantics for requesting the digital signatures creation to a remote server and for receiving the related response. For the semantics mentioned, the specification has two bindings, each one in a different format (XML and JSON). Both XML and JSON can be easily parsed and manipulated by programming languages and tools, making them machine-readable and ideal for exchanging data between different systems and platforms. ETSI TS 119 432: https://www.etsi.org/deliver/etsi_ts/119400_119499/119432/01.02.01_60/ts_119432v010201p.pdf'
'OData services are used by a large community of users. These services use a common data model, which allows any client to interact with the service in a well-defined way (see OData reference). In this sense, the specification is domain-agnostic. For example, there are the Cambridge Weather-Pyslet demo service and the City of Medicine Hat Open Data Portal, in the field of academics and medicine, respectively. OData ecosystem, Live services reference: https://www.odata.org/ecosystem/ OData reference, 4 Service model: http://docs.oasis-open.org/odata/odata/v4.0/errata03/os/complete/part1-protocol/odata-v4.0-errata03-os-part1-protocol-complete.html#_Toc453752204'
'ODRL has an open community where stakeholders can participate in discussions, share experiences, and contribute to the evolution of the standard. Community engagement can foster the sharing of best practices, use cases, and insights related to the implementation of ODRL. ODRL github community: https://github.com/w3c/odrl W3 ODRL community: https://www.w3.org/community/odrl/ '
'The purpose of CPOV is not related to the protection of personal data. Therefore, this criterion is considered not applicable to this specification. CPOV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-organisation-vocabulary'
'The Asset Administration Shell (AAS) is not related to the secure processing of data. Therefore the criterion is not applicable. Details of the Asset Administration Shell (AAS) https://industrialdigitaltwin.org/en/wp-content/uploads/sites/2/2024/06/IDTA-01001-3-0-1_SpecificationAssetAdministrationShell_Part1_Metamodel.pdf'
"EUROSTAT (European Commission) ensures the maintenance of the NUTS classification. However, NUTS does not encourage the creation of communities nor does not promote the sharing of data and results in any national platform, except for some (non-)European states that have individually shared their data and results on their respective national platforms (see EconStor Publications reference, Croatia's NUTS implementation document, and Scotland government reference, Scotland's NUTS implementation document). EUROSTAT reference, NUTS Principles and Characteristics section: https://ec.europa.eu/eurostat/web/nuts/principles-and-characteristics EconStor Publications reference, Croatia's NUTS implementation document: https://www.econstor.eu/bitstream/10419/115958/1/ERSA2003_096.pdf Scotland government reference, Scotland's NUTS implementation document: https://www.gov.scot/publications/review-nomenclature-units-territorial-statistics-nuts-boundaries/"
By using ADMS to describe assets/solutions, the administrations ensure and enhance the visibility of these solutions and assets that are involved in the development of EU administrations’ activity. ADMS on Joinup: https://joinup.ec.europa.eu/solution/asset-description-metadata-schema-adms/about ADMS Specification W3C: https://www.w3.org/TR/vocab-adms/
As a document exchange format, PDF/A is a valuable tool for sharing information through the internet. Allowing sharing data and information the standard foster the comprehensibility of administration data and services. Additionally, it eases the decision-making process within administrations. PDF/A reference: https://www.iso.org/standard/38920.html https://www.iso.org/standard/50655.html
'The purpose of DCAT is not related to the implementation of authentication mechanisms. Therefore, this criterion is not applicable tot the specification. DCAT-AP Specification: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/dcat-application-profile-data-portals-europe/release/200'
There are no disclosures of ISO IPR Database to identify the licensing under the specification. ISO 10918-1:1994 (JPEG) is not listed in ISO/IEC/ITU Common Patent policy, so it cannot be confirmed that the specification is licensed on a (F)RAND basis. ISO patents: https://www.iso.org/iso-standards-and-patents.html ISO standards and patents IPR database: http://isotc.iso.org/livelink/livelink/13622347/Patents_database.xls?func=doc.Fetch&nodeId=13622347
'ELI is designed to be technology-agnostic. This means that it is intended to work independently of specific technological platforms or systems. The goal is to allow flexibility in its implementation across various technology environments, making it adaptable to different systems and ensuring interoperability. This approach facilitates the integration of ELI into diverse information systems and applications without being tied to a particular technology stack. ELI reference: https://eur-lex.europa.eu/eli-register/about.html'
'DCAT is a domain-agnostic specification that can be reused for the description of any catalogue of dataset independently from the business domain addressed. For DCAT users having business-specific requirements, the specification is generally extended (e.g. StatDCAT-AP for statistical data). Therefore, the specification can be implemented across business domains. DCAT-AP Specification: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/dcat-application-profile-data-portals-europe/release/200 StatDCAT-AP: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/statdcat-application-profile-data-portals-europe/release/101'
IPSec is already associated to an EIRA ABB in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, IPSec can define the interoperability aspects of the "Network Service" and "Network Components" ABBs of the EIRA Technical View. See: https://joinup.ec.europa.eu/solution/elis/distribution/eliscataloguev100betaxlsx
'ETSI TS 119 612 does simplify the delivery of European public services as TLSOs shall define, maintain and implement appropriate measures, practices and policies, including change management and security procedures, for establishing, publishing and maintaining the trusted list to ensure that the information provided in the trusted list is timely, accurate, complete and authentic. ETSI TS 119 612 specification: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf'
ADMS is a vocabulary based on DCAT for the description of Assets, specifically interoperability solutions). In this sense, the ADMS helps the publication and reusability of solutions and their data. ADMS on Joinup: https://joinup.ec.europa.eu/solution/asset-description-metadata-schema-adms/about ADMS Specification W3C: https://www.w3.org/TR/vocab-adms/
"While OpenTelemetry is not directly related to enabling the secure exchange of data, the OpenTelemetry Collector defaults to operating in a secure manner, even though it is configuration driven. A section of the specification is dedicated to reported Common Vulnerabilities and Exposures (CVEs) across all repositories in the OpenTelemetry organization on GitHub and how to report and respond to any security incident that impacts OTel's Community. OpenTelemetry Security: https://opentelemetry.io/docs/security/ "
'ETSI TS 119 612 can be found on the specifications and standards repository of its standards development organization, the European Telecommunication Standards Institute (ETSI). ETSI standards repository: https://www.etsi.org/committee/1399-esi'
'As it happens with all the e-Government Vocabularies, it has the SEMIC action from the ISA2 as responsible for the maintenance of the development. SEMIC in Joinup: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic'
'There are existing studies assessing HTTPS in terms of effectiveness. Among some of the studies found there can be mentioned a survey of the implementation of HTTPS in Android Apps or an assessment of the legal and technical solutions to secure HTTPS. Security Collapse in the HTTPS Market: Assessing legal and technical solutions to secure HTTPS: https://dl.acm.org/doi/abs/10.1145/2668152.2673311 A Survey on HTTPS Implementation by Android Apps: Issues and Countermeasures: https://www.sciencedirect.com/science/article/pii/S2210832716300722 An Empirical Study of the Cost of DNS-over-HTTPS: https://dl.acm.org/doi/abs/10.1145/3355369.3355575'
'The purpose of this specification is not related to providing an access control mechanism. Therefore, this criterion is not applicable to this specification. LDES specification: https://joinup.ec.europa.eu/collection/semic-support-centre/linked-data-event-streams-ldes'
HTML5 foster e-accessibility through improving accessibility of web and mobile web applications, digital signs, ebooks and devices not yet known for people with disabilities.
'SCIM includes mechanisms for access control, allowing organizations to define and enforce policies regarding who can perform specific operations on user identities and groups. These access control mechanisms are crucial for ensuring the security and integrity of identity-related data managed through SCIM. SCIM: https://scim.cloud/'
As a mail format specification, MIME is a valuable tool for sharing information through the internet between administrations and stakeholders. It allows sharing data and information in a specific format, it fosters the visibility of administration data and services. MIME fosters the collaboration between public administrations and it eases the decision-making process of institutions. MIME reference: https://tools.ietf.org/html/rfc2045
'OCSP defines a protocol useful in determining the current status of a digital certificate without requiring CRLs (certificate revocation list). Therefore, it can simplify the delivery of any European public service. OCSP reference: https://datatracker.ietf.org/doc/html/rfc2560'
'TGF provides guidelines for designing and implementing cross-organisational processes and services, as well as for developing interoperability agreements between public and private organisations. The TGF aims to promote the alignment of business objectives, processes, and IT systems, enabling organisations to work together in a coordinated and effective way. TGF specification: http://docs.oasis-open.org/tgf/TGF/v2.0/cs01/TGF-v2.0-cs01.html"'
'XACML indirectly contributes to data processing accuracy by providing robust and detailed access control, ensuring that only authorized and qualified individuals can access and modify data. XACML OASIS reference: https://docs.oasis-open.org/xacml/3.0/xacml-3.0-core-spec-os-en.html'
"The specification is included in two Member States' catalogues of recommended specifications. These Member States are The Netherlands and France. National catalogue France: http://references.modernisation.gouv.fr/sites/default/files/Referentiel_General_Interoperabilite_V2.pdf National catalogue Netherlands: https://www.forumstandaardisatie.nl/open-standaarden/lijst CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards "
'First of all ISAE 3402 provides a guarantee in the context of the security and confidentiality of information for users and companies. Therefore, when a public administration contracts a service from a private company, it can request the ISAE 3402 to ensure that their data complies with adequate confidentiality and security, ISAE 3402 handbook reference: https://www.ifac.org/system/files/downloads/b014-2010-iaasb-handbook-isae-3402.pdf'
'According to the 5 star Open Data model suggested by Tim Berners-Lee about how to publish linked data, the second star corresponds to the availability of data as structured data. Schema.org is a structured data mark-up schema enabling search engines and other information systems to query data in a structured manner. Then, this specification supports the publication of data as open data. Schema.org reference, Getting started section: https://schema.org/docs/gs.html Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/en/'
"The Technical Committee (TC) CYBER (Cybersecurity) is encharged of the development and maintenance of the EN 303 645 specification. As other ETSI technical committes, the TC CYBER contributes to the report writing. Participation is open prior a registration process and a financial contribution (see ETSI Directives' Rules of Procedure). ETSI Directives, Rules of Procedure: https://portal.etsi.org/Resources/ETSI-Directives ETSI TC CYBER press release reference: https://www.etsi.org/committee/1393-cyber"
'As defined on the OASIS ebXML Registry Technical Committee (TC), only this TC is involved in the release lifecycle of the specification. External contribution to this committee is possible through the Comment List, where potential contributors may provide their feedback to members of the OASIS ebXML Registry TC. All contribution from TC members and others regarding the release lifecylce of the specification is publicly available in the TC archive. OASIS ebXML Registry TC, Mail Lists and Comments section: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=regrep#feedback Comment List reference: https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=regrep OASIS ebXML Registry TC archive reference: https://lists.oasis-open.org/archives/regrep/'
'The specification was officially established in 2012, and the ELI ontology version 1.3 was published in July 2020, incorporating the experience and expertise of Member States collaborating closely to refine the specification. On the ELI homepage, various materials are available to aid in visualizing and comprehending the evolution of the specification. These resources assist Member States in implementing ELI seamlessly, enhancing interoperability, and ensuring cost-efficiency. The ongoing contributions from Member States play a crucial role in the continuous evolution of the specification, allowing it to adapt to the changing needs of users. ELI reference: https://eur-lex.europa.eu/eli-register/about.html ELI highlights: https://eur-lex.europa.eu/eli-register/index.html'
'The ETSI and any of its committees, in charge of the development of ETSI EN 319 532-3, operate under the ETSI Intellectual Property Rights (IPRs) and IPR Policy. The specification is licensed on a (F)RAND basis. Intellectual Property Rights Policy, ETSI ownership of IPRs section: https://www.etsi.org/intellectual-property-rights'
'The ITPE conducts conferences and webinars within various communities using the specification to give a voice to anyone who wants to give their opinion on the EN 16234-1 e-CF specification, including European participation. IT Professionalism Europe (ITPE) reference, Events: https://itprofessionalism.org/events/'
IETF has a defined set of processes for the modification and revocation of standards. See: https://www.ietf.org/standards/process/ https://tools.ietf.org/html/rfc2026
'WSDL enables communication and integration between components developed using different technologies. The goal is to facilitate interoperability among diverse systems, applications, and programming languages. By providing a standardized way to describe the contract between a service provider and a service consumer. W3C WSDL specification: https://www.w3.org/TR/wsdl20/ '
'The purpose of DQV is not related to the access control mechanisms. Therefore, this criterion is considered not applicable to the specification. DQV IETF reference: https://www.w3.org/TR/vocab-dqv/'
'The OData protocol provides support for both user and version-driven extensibility by means of different extension methods, through a combination of versioning, conventions and explicit extension points. OData reference, 6 Extensibility: http://docs.oasis-open.org/odata/odata/v4.0/errata03/os/complete/part1-protocol/odata-v4.0-errata03-os-part1-protocol-complete.html#_Toc453752211'
'The Core Public Organisation Vocabulary fosters the delivery of multilingual services in European public institutions. CPOV is designed to be extensible and adaptable in different languages. CPOV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-organisation-vocabulary'
'After checking the different standard catalogues at supra-national level, there is no evidence of WAI-ARIA as a European standard. ICT technical specifications: https://ec.europa.eu/growth/single-market/european-standards/ict-standardisation/ict-technical-specifications_en CENELEC and CEN search tool catalogue: https://standards.cencenelec.eu/dyn/www/f?p=CEN:105::RESET::::'
'Syslog can provide some mechanisms for authentication and can support the authenticity of the roles involved in data transactions to a certain extent. Implementing secure authentication mechanisms, such as TLS (Transport Layer Security) or other secure transport options, enhances sender identification and helps ensure that the syslog messages are genuinely coming from the claimed source. Syslog Protocol: https://datatracker.ietf.org/doc/html/rfc5424'
'HTTP Cookies can only be implemented within an HTTP communication protocol. Therefore, this specification is not technology-agnostic. IETF HTTP Cookies: https://datatracker.ietf.org/doc/html/rfc6265'
FTP is an internet protocol for the exchange of data over an Internet network. It supports the first level of maturity defined in the Tim Berners-Lee´s 5 stars Open Data deployment scheme, "Make your data accessible on the web". See: https://5stardata.info/en/ https://tools.ietf.org/html/rfc959
The purpose of Ogg is not related to e-accessibility. Therefore, this criterion is considered not applicable to this specification. Ogg XIPH reference: https://xiph.org/ogg/doc/rfc3533.txt
'The specification does provide the means for the administrations using it to comprehensively organise the procedures and bureaucracy related to their operations. This is done providing a general framework through the ontology to identify and classify the different organisational elements, whether they are data, services or procedural resources. BFO reference: https://www.iso.org/standard/74572.html'
"There are many papers evaluating the specification's effectiveness. An example of a paper evaluating GraphQL effectiveness: https://ieeexplore.ieee.org/abstract/document/9163501"
"OpenTelemetry is included in the Spanish National Institute of Cybersecurity (INCIBE). OpenTelemetry-Go Contrib is a collection of third-party packages for OpenTelemetry-Go. Prior to version 0.46.0, the grpc Unary Server Interceptor out of the box adds labels `net.peer.sock.addr` and `net.peer.sock.port` that have unbound cardinality. It leads to the server's potential memory exhaustion when many malicious requests are sent. An attacker can easily flood the peer address and port for requests. Version 0.46.0 contains a fix for this issue. INCIBE-CERT Vulnerabilities: https://www.incibe.es/en/incibe-cert/early-warning/vulnerabilities/cve-2023-47108"
'The XACML specification provides significant mechanisms for protecting personal data managed by Public Administrations through fine-grained, attribute-based access control, policy enforcement, and audit capabilities. Moreover, XACML should be integrated with other security measures. XACML OASIS reference: https://docs.oasis-open.org/xacml/3.0/xacml-3.0-core-spec-os-en.html'
Better Regulation Toolbox is a public asset developed by a European Institution and can be accessed and reused without any payment conditions. Therefore, it can be considered that the specifications is licensed under royalty-free basis and (F)RAND basis. Better Regulation Toolbox reference: https://ec.europa.eu/info/sites/info/files/better-regulation-toolbox_2.pdf
'The purpose of OAIS is not related to multilingualism, therefore this criterion is not applicable to the specification. OAIS specification: https://public.ccsds.org/Pubs/650x0m2.pdf'
'ebXML is originally associated to the electronic business domain. However, the specification could be indistinctly implemented in other domains as the automobile domain (see ebXML application reference). OASIS ebXML Registry TC reference, Announcements section: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=regrep#announcements ebxml.xml.org reference: http://ebxml.xml.org/milestones ebXML application reference: http://ebxml.xml.org/resources'
'After searching in the different official European websites, there is no evidence of any cross-border project that use CPOV nor explicit agreements involving the usage of the specification. Despite this, there are countries that extend Core Vocabularies to use them with specific attributes they want. Core Vocabularies reference: https://www.w3.org/2013/share-psi/workshop/berlin/EuropeanInteroperabilityTheISACoreVocabularies'
The rules on European standardisation allow the European Commission to identify information and communication technology (ICT) technical specifications - that are not national, European or international standards - to be eligible for referencing in public procurement. This allows public authorities to make use of the full range of specifications when buying IT hardware, software and services, allowing for more competition in the field and reducing the risk of lock-in to proprietary systems. After being evaluated compliant with the regulation on standardisation 1025/2012, MIME has been identified by Commission Implementing Decision. During the evaluation process, all the Member States are invited to share their doubts. The positive evaluation of MIME and its identification is considered an interoperability agreement. ICT Standards for Procurement: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en
'XBRL international supports the above by national and international communities to further develop and support the implementation of the specification. https://www.xbrl.org/tag/xbrl-europe/ https://www.xbrl.org/the-consortium/ '
'The version which is being assessed was released in 2012, fact that demonstrates the maturity of the specification for its use in the development of products and services. Moreover, XSD is an open specification supported by products and services and it is involved in the development of web services as XML schemas are needed for validating XML files. XSD Reference: https://www.w3.org/TR/2012/REC-xmlschema11-1-20120405/'
'Like other vocabularies, ADMS reuses components from other vocabularies. (e.g. foaf, dcat), and also the resource Description Framework (RDF). This causes a dependency that can hamper the interoperability in those cases where new releases of the reused vocabularies are not backward compatible. ADMS Specification W3C: https://www.w3.org/TR/vocab-adms/'
The Core Location Vocabulary facilitates the process for institutions to classify and to describe data about location aspects of public organisations, citizens, and businesses. By ensuring the reuse of information among administrations and systems, it fosters interoperability and impacts positively on the development of eGovernment. CLV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-location-vocabulary
"The purpose of CSV is not related to enabling the exposure of interfaces to access the public administration's service. Therefore, this criterion is not applicable to the specification. CSV reference: https://datatracker.ietf.org/doc/html/rfc4180"
'The specification had reached a mature state, with version 1.0 of the specification having been released in October 2019. The specification was developed through a multi-year process involving stakeholders from across the European Union, and is designed to provide a common framework for the creation and exchange of legal documents in a machine-readable format. AKN4EU reference: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/akn4eu'
CSS can be found for free along within the European Collaborative Platform, Joinup. CSS in Joinup platform: https://joinup.ec.europa.eu/solution/cascading-style-sheets/distribution/cascading-style-sheets
XACML can be used independently from any other technical specifications or operating system. However, it is worth noting that since it is based on XML, it can be dependent on conventions and rules for the correct XML usage. XACML OASIS reference: http://docs.oasis-open.org/xacml/3.0/errata01/xacml-3.0-core-spec-errata01.html
'UDDI has been selected several times for European administrations in order to make their web services available and discoverable for each other, and their stakeholders. An example of this kind UDDI use case is SELIS project, which aims to ease the eInvoicing processes. It is included within the Digital Single Market framework. SELIS reference: https://joinup.ec.europa.eu/collection/eprocurement/document/secure-electronic-invoicing-service-selis'
'The purpose of HTTP Cookies is not related to the modelling of business processes. Therefore this criterion is not applicable to this specification. HTTP Cookies reference: https://developer.mozilla.org/en-US/docs/Web/HTTP/Cookies#creating_cookie'
'Conformance to DPV implementation means it is correctly mapped and aligned with the vocabularies it defines. For that matter, the "Development Guide" section found in Github indicates how the conformity process has to be carried out. DPV specification: https://w3c.github.io/dpv/primer/ DPV in Github: https://github.com/w3c/dpv'
'HTTPS has become the standard protocol for transmitting sensitive data over the internet, and it is widely supported by web browsers, web servers, and other software applications. The majority of websites that handle user data, especially those involving e-commerce, online banking, and user accounts, use HTTPS to ensure the security and privacy of their users. The maturity of HTTPS is evident in the widespread adoption of SSL/TLS certificates, which are essential for enabling HTTPS connections. Certificate authorities issue these certificates, and a robust ecosystem exists for their issuance, management, and verification. SSL Certificate explanation: https://www.kaspersky.com/resource-center/definitions/what-is-a-ssl-certificate'
'ELI specification does enable digital service delivery channels. According to the ELI ‘Pillar IV’ protocol, an ELI provider must provide two channels: the ELI Sitemap and the ELI Atom feed. These channels facilitate the dissemination of ELI metadata in a structured format embedded in the web pages of Official Journal websites. This allows legislation publishers to share their data in an interoperable way, thereby enabling digital service delivery channels. However, to be compatible with the ELI ‘Pillar IV’ protocol, it is necessary to have ELI Pillar III implemented, which involves the inclusion of structured metadata in web pages. ELI IV specification refrerence: https://eur-lex.europa.eu/content/eli-register/ELI-Pillar-IV-protocol-specification-v1.0_en.pdf ELI reference: https://eur-lex.europa.eu/eli-register/about.html'
The specification is a widely used de-facto standard. Thus, it is sufficiently mature for the development of products and services. Since it's release 1995, IPSec overcame most of its initial problems and has been used by many products and services. See: https://www.ibm.com/it-infrastructure/z/zos https://www.ibm.com/it-infrastructure/power/os/aix https://www.oracle.com/solaris/solaris11/ http://www.mit.edu/~tytso/ipsec/surv9607.html
'The purpose of OAS is not related to the reuse of information, therefore this criterion is not applicable to the specification. OAS specification: https://spec.openapis.org/oas/latest.html#openapi-specification OAS in Github: https://github.com/OAI/OpenAPI-Specification/#participation'
"Domibus, as a messaging platform, focuses on ensuring the secure transmission of messages and documents. While it supports digital signatures that contribute to data authenticity and integrity, it doesn't inherently guarantee data accuracy beyond the scope of secure message exchange. Domibus specification: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/Domibus "
CAdES and CAdES Baseline profile are included in the ETSI’s catalogue of standards. As ETSI is considered an official standardisation organisation, it can be considered that the specifications are included in a supra-national catalogue. See: https://www.etsi.org/standards#page=1&search=ETSI%20TS%20103%20173&title=1&etsiNumber=1&content=1&version=0&onApproval=1&published=1&historical=1&startDate=1988-01-15&endDate=2020-01-08&harmonized=0&keyword=&TB=&stdType=&frequency=&mandate=&collection=&sort=1
'ISO has defined a clear procedure to develop its standards. It consists in a 6-steps process where everyone who is interested can participate. However, if you want to participate, you have to contact your national standards body and you have to be approved for joining the Technical committee (TC) who will develop the standard. ISO has defined the roadmap of standards, it is composed of 6 steps as before said. For the approval of a standard the two-thirds majority of P-members of TC is needed. If the result is negative, the document is returned to TC/SC to be further studied. The ISO standardization process: https://www.iso.org/stages-and-resources-for-standards-development.html'
'After researching there has been no success finding any indication of conformance on the specification. ETSI EN 319 422 reference: https://www.etsi.org/deliver/etsi_en/319400_319499/319422/01.01.01_60/en_319422v010101p.pdf'
The OASIS Technical Committee, in charge of the development of WS-BPEL, operates under RF on RAND Mode of the OASIS IPR Policy. The specification is licensed on a Royalty-free and (F)RAND basis. OASIS IPR: https://www.oasis-open.org/committees/security/ipr.php https://www.oasis-open.org/policies-guidelines/ipr
'The Data Spaces Business Alliance (DSBA) aims to converge the best skills, assets, and experience in Europe into a one-stop-shop for data spaces, from inception to deployment. The Data Spaces Business Alliance are Gaia-X European Association for Data and Cloud AISBL, the Big Data Value Association (BDVA), FIWARE Foundation, and the International Data Spaces Association (IDSA), who created and currently maintains DAPS. With this cross-industry expertise, resources and know-how, the Alliance drives awareness, evangelizes technology, shapes standards, and enables integration across industries. Data Spaces Business Alliance (DSBA): https://data-spaces-business-alliance.eu/'
By allowing the authentication for using services SAML 2.0 fosters visibility by simplifying access to administrations’ services. Moreover, it can be used internally by public officers which enhances the decision-making process.
'The "xsl:evaluate" feature in XSLT adds flexibility by allowing dynamic evaluation of XPath expressions. To ensure secure processing of data, it's crucial to use this feature with caution. By validating and sanitizing input expressions, only enabling dynamic evaluation for trusted sources, and configuring the processor to disable unsafe operations, you can mitigate security risks like code injection attacks. XSLT Reference: https://www.w3.org/TR/xslt-30'
'The ebXML specification extends XML standard. In this context, XML is technology agnostic, therefore ebXML can also be considered as a technology agnostic specification. ebXML RegRep OASIS reference: https://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html'
'The purpose of this Core Vocabulary is not related to ensuring and enabling data processing accuracy. Therefore, this criterion is not applicable to this specification. CPSV-AP reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-service-vocabulary-application-profile'
'ESPD is designed to be technology-agnostic, meaning that it can be used with a variety of different digital solutions and services. The ESPD is available in a range of formats, including electronic forms, and structured data formats such as XML, which allows it to be integrated into a wide range of digital systems and platforms. Such is the case of the Spanish service-based "registro de licitadores". ESPD Business handbook https://docs.ted.europa.eu/ESPD-EDM/latest/xml_business_handbook.html Spanish service DEUC: https://visor.registrodelicitadores.gob.es/espd-web/filter?lang=es'
'The purpose of OSI is not related to privacy and as such is not included in any initiative both National and European level. Therefore, this criterion is not applicable to the specification. OSI reference https://www.iso.org/standard/20269.html'
'Domibus enables secure data exchange through encryption, digital signatures, transport security, access control, authentication, authorization, message validation, and audit trails. It ensures data confidentiality, integrity, and controlled access during electronic message exchange. Domibus specification: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/Domibus AS4 specification: http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/profiles/AS4-profile/v1.0/AS4-profile-v1.0.html '
The purpose of the specification is not related to the publication of data as Open Data. Therefore, this criterion is not applicale to this specification.
'A few assessments have been carried on the specification effectiveness, in particular regarding the administrative burden and simplification. Given the nature of the Better Regulation Guidelines and Toolbox only a few assesments can be carried out since the specification is rather stable. In this sense, all are conducted by think tanks that focus on administration simplification and integration. It is worth mentioning that the Cambridge one is the most recent one and focuses on what can be adapted from the Better Regulation Guidelines and Toolbox in the UK context post brexit. Better Regulation Guidelines and Toolbox reference: https://commission.europa.eu/law/law-making-process/better-regulation/better-regulation-guidelines-and-toolbox_en "Can We Better the European Union Better Regulation Agenda?" Cambidge's article: https://www.cambridge.org/core/journals/european-journal-of-risk-regulation/article/abs/can-we-better-the-european-union-better-regulation-agenda/46A0BA96D46266FF5C8320A2DA3B937F "To the Commissioner responsible for better regulation" Bruegel's study: https://www.bruegel.org/wp-content/uploads/2019/09/MEMO-Better-Regulation.pdf'
'This specification has a section dedicated compliance and consistence with the OSI reference model. Section 9.2 details the application of consistency and compliance requirements regarding ISO/IEC 7498:1. ISO/IEC 7498:1: https://www.iso.org/standard/20269.html'
'This specification contains a number of cloud interoperability and portability facet models that state the aim of the facet and its requirement. For instance, the syntactic facet of cloud interoperability aims to receive data in an understood format therefore, data exhange formarts should be standardized in JSON, XML, ASN.1 etc. ISO 19941: https://www.iso.org/obp/ui/en/#iso:std:iso-iec:19941:ed-1:v1:en'
'Registered Organization Vocabulary facilitates the information exchange between business registers, improving the interoperability of systems used by European public services that rely on information about registered organisations. It also promotes the reuse of European vocabularies such as ADMS, enhancing metadata management, ensuring semantic consistency, and supporting the discoverability and interoperability of organisational data across different systems. Registered Organization Vocabulary reference: https://www.w3.org/TR/vocab-regorg/ Asset Description Metadata Schema (ADMS) reference: https://www.w3.org/TR/vocab-adms/'
'The authentication verification relationship is used to specify how the DID subject is expected to be authenticated for purposes such as logging into a website or engaging in any sort of challenge-response protocol. A particular DID method could decide that authenticating as a DID controller is sufficient to, for example, update or delete the DID document. Another DID method could require different keys or a different verification method entirely to be presented, in order to update or delete the DID document than that used to authenticate. DIDs authentication W3C: https://www.w3.org/TR/did-core/#authentication'
All the IETF standards are free and open technical specification, built on IETF standards and licenses from the Open Web Foundation. The specification is therefore licensed on a royalty-free basis._x000D_ _x000D_ See:_x000D_ https://tools.ietf.org/html/rfc3668
'HTTP specification facilitates the publication of data on the web. It provides the necessary mechanisms to create, access, manage, and efficiently distribute data in various formats, giving a diverse user base and ensuring data integrity and security. HTTP/1.1 Semantics, RFC 9110 Reference: https://www.rfc-editor.org/rfc/rfc9110 HTTP/1.1: Semantics and Content, RFC 7231 Reference: https://www.rfc-editor.org/rfc/rfc7231'
The ISO 12639:2004 which refers to TIFF/IT is not available for free for everyone to study. Payment is needed to reach access to the standard. TIFF/IT ISO reference: https://www.iso.org/standard/34342.html
'OCSP specifies the data that needs to be exchanged between an application checking the status of one or more certificates and the server providing the corresponding status. The purpose of OCSP is not related to the comprehensibility of administrative procedures, rules data, and services. OCSP reference, section 2: https://datatracker.ietf.org/doc/html/rfc2560'
'AMQP specification facilitates the restriction of access to information and data through security layers such as filters and hostname verification, for example SASL Init,which ensures that the client is properly authenticated before any further communication occurs. It is the implementer of the specification who determines the level of access to the information and data. Oasis AMQP Reference: http://docs.oasis-open.org/amqp/core/v1.0/amqp-core-complete-v1.0.pdf'
'OASIS has defined a clear Technical Committee (hereby TC) process where all the stakeholders involved have the opportunity to participate in the development of the specification development process. OASIS guideline: https://www.oasis-open.org/policies-guidelines/casestudies'
'The DPV taxonomy and data model can be adapted to the business-specific needs, allowing for partial implementations depending on the requirements of any particular context where it is to be applied. DPV specification: https://w3c.github.io/dpv/dpv/ DPV primer document: https://w3c.github.io/dpv/primer/#introduction'
'The specification can enable digital service delivery channels to some extent. FTP is a protocol that facilitates the transfer of files between systems, which can be utilized within digital service delivery channels. FTP Specification Reference: https://datatracker.ietf.org/doc/html/rfc959 '
'The purpose of DIDs is not related to long term preservation of electronic records. Therefore this criterion is considered not applicable to this specification. DIDs W3C: https://www.w3.org/TR/did-core/'
'DNS over HTTPS (DoH) is not designed to address the long-term preservation of data, information, or knowledge, including electronic records. DoH is a protocol that focuses on securing the DNS (Domain Name System) communication by encrypting DNS queries and responses. DoH specification: https://datatracker.ietf.org/doc/html/rfc8484'
'DIDs allow for extension. The data model supports two types of extensibility. For maximum interoperability, it is recommended that extensions use the W3C DID Specification Registries mechanism. Representations may define other extensibility mechanisms, including ones that do not require the use of the DID Specification Registries. DIDs W3C: https://www.w3.org/TR/did-core/#extensibility'
PDF/A has been assessed previously by the Netherlands using the Technical scenario which is fully aligned with the European Standardisation Regulation 1025/2012. As the result of the assessment is positive, PDF/A can be considered compliant with the European regulation. PDF/A in JoinUp: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/camss-assessment-pdf-a2-scenario-2
'Information can be exchanged in a secure and trustworthy manner. With peer-to-peer basis and using verification methods, data and information can be exchanged in a secure manner, which also guarantees the secure processing of data. DIDs security requirements: https://www.w3.org/TR/did-core/#security-requirements'
'HTTP Cookies is a business domain agnostic specification that can be implemented in a cross-domain way. HTTP Cookies: https://datatracker.ietf.org/doc/html/rfc6265'
Open PM2 is an initiative supported by ISA2 to bring the PM2 Methodology and its benefits closer to its broader stakeholders and user community. The European Commission ISA2 Programme supports the development of solutions in the area of interoperability. ISA2 programme: https://ec.europa.eu/isa2/home_en OpenPM2 specification reference: https://op.europa.eu/en/publication-detail/-/publication/ac3e118a-cb6e-11e8-9424-01aa75ed71a1/language-en/format-PDF/source-83307127
There are many documents that evaluate the effectiveness and efficiency of this specification. For example, in the following link there is a study of Xforms called "Efficient evaluation of shared predicates for XForms page access control". Xforms evaluation: https://ieeexplore.ieee.org/document/4766728
The purpose of JSON is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification.
'There has not been found any article or study assessing the effectivenss of the ISO/IEC 19944-1. ISO/IEC 19944-1 specification: https://www.iso.org/standard/60545.html'
JSON is available for its use an implementation at ECMA International and EITF's webpages. See: https://www.ecma-international.org/publications/standards/Ecma-404.htm https://tools.ietf.org/html/rfc8259
'The OAS is an open-source, royalty-free specification. It is available for free for its use and implementation both on its website and on the Github repository. OAS specification: https://spec.openapis.org/oas/latest.html#openapi-specification OAS in Github: https://github.com/OAI/OpenAPI-Specification/#participation OAS governace rules: https://www.openapis.org/participate/how-to-contribute/governance'
'Section 7.7 of ETSI TS 119 432 is dedicated to the component for the client application authentication. This component shall contain information to authenticate the client application to access to the SCASC or the SSASC. However, the way a client application authenticates to the SCASC or SSASC is out of scope of the protocol. ETSI TS 119 432: https://www.etsi.org/deliver/etsi_ts/119400_119499/119432/01.02.01_60/ts_119432v010201p.pdf'
'TLS 1.3 is specification-independent and can be implemented without dependencies on platforms. Moreover, the IETF, a vendor-neutral Standards Development Organisation, developed the technical specification independently of any vendor products. TLS 1.3 2018 Reference: https://www.rfc-editor.org/rfc/rfc8446.html'
'The purpose of EN 16234-1 e-CF is not related to data portability. Therefore, this criterion is not applicable to this specification. CEN reference, CEN/TC 428 - ICT Professionalism and Digital Competences (Published standards), EN 16234-1 e-CF: https://standards.cencenelec.eu/dyn/www/f?p=205:110:0::::FSP_PROJECT:67073&cs=15E62ED24D608A5F10D6BEE8E6D50FA10'
The adoption of this Core Vocabulary as a data model does not hamper the scalability of systems. CPSV-AP reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-service-vocabulary-application-profile
Even though at the moment of elaborating the assessment the specification is used, the specification in itself does not give any innovative solution since it is a language used for the composition of web services.
'There exist two independent communities, one providing public support and the other one in charge of the EN 16234-1 e-CF specification maintenance (see CEN/TC 428 "ICT Professionalism and Digital Competences" Business Plan 2022). On one side, there is the IT Professionalism Europe (ITPE), which was created in 2018 and performs all activities related to counselling and advice under this specification; and on the other side, there is the CEN/TC 428 - ICT Professionalism and Digital Competences which is in charge of the maintenance of the specification, although it is also responsible to provide public support. The CEN/TC 428 comprises participants from national and CEN-recognised working groups (see CEN/TC 428 "ICT Professionalism and Digital Competences" Business Plan 2022 reference, section 5 and CEN reference, CEN/TC 428 - ICT Professionalism and Digital Competences section, CEN/TC 428 Subcommittees and Working Groups). Interestingly, only ITPE provides an e-CF preview through the Access e-CF Explorer service. IT Professionalism Europe (ITPE) reference: https://itprofessionalism.org/about-us/ CEN/TC 428 "ICT Professionalism and Digital Competences" Business Plan 2022 reference: https://standards.cencenelec.eu/BPCEN/1218399.pdf CEN reference, CEN/TC 428 - ICT Professionalism and Digital Competences section, CEN/TC 428 Subcommittees and Working Groups: https://standards.cencenelec.eu/dyn/www/f?p=205:29:0::::FSP_ORG_ID,FSP_LANG_ID:1218399,25&cs=1C0456547BD827F5A977AD2936836C8DA#1 IT Professionalism Europe (ITPE) reference, Access e-CF Explorer: https://itprofessionalism.org/about-it-professionalism/competences/the-e-competence-framework/'
The adoption of CAdES as electronic signature for signing online documents does not hamper the scalability of systems. CAdES ISO reference: https://www.iso.org/standard/64756.html CAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/101700_101799/101733/02.01.01_60/ts_101733v020101p.pdf
'TLS 1.3 does not facilitate organisational interoperability agreements, instead it provides a secure, reliable and interoperable channel that enables organisations to securely comunicate and exchange data, which is essential for the implementation of interoperability agreements and the operation of European public services. TLS 1.3 Reference: https://www.rfc-editor.org/rfc/rfc8446.html'
'ISO/IEC 19944-1 can indirectly contribute to data portability efforts by providing a classification scheme, promoting consistent data management practices, and encouraging interoperability considerations within cloud computing environments. ISO/IEC 19944-1 specification: https://www.iso.org/standard/60545.html'
XSLT is a language for transforming XML documents in a variety of formats including HTML, plain texts of XSL, PDF among others. It is a specification that adapts to the needs of the users. See: https://www.w3.org/TR/XAdES/
'AMQP specification is platform-agnostic because it is designed to function independently of specific platforms, which ensures reliable information exchange between parties across diverse systems. OASIS AMQP Reference: http://docs.oasis-open.org/amqp/core/v1.0/amqp-core-complete-v1.0.pdf'
The purpose of CPOV is not related to the availability of interfaces with internal information systems. Therefore, this criterion is not applicable to this specification. CPOV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-organisation-vocabulary
The specification assessed is focused on signed data transactions across borders, which means data portability. Moreover, as before mentioned, the scalability and adaptability of specification allow successful data exchange and reuse enhancing the interoperability of systems.
The purpose of SAML 2.0 is not related to organisational interoperability. Therefore, this criterion is not applicable to the specification.
PAdES Baseline Profile is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). Specifically, PAdES Baseline Profile can define the interoperability aspects of “e-Seal Creation Service”, “e-Seal Verification and Validation Service”, “e-Signature Creation Service”, and “e-signature Verification and Validation Service” ABBs of the EIRA Technical View. See: https://joinup.ec.europa.eu/solution/elis/distribution/eliscataloguev100betaxlsx
'As a Reference Architecture, EIRA is meant to be used in early stages such the analysis, where the requirements for solutions developments are sets. In this sense, the EIRA provides a set of architecture building blocks, and also flexibility to extend it, ensuring that an e-Accessibiilty from design can be followed, ensuring that Digital Public Services that start from EIRA to its implementation can be accessible. EIRA reference: https://interoperable-europe.ec.europa.eu/collection/european-interoperability-reference-architecture-eira /solution/eira/release/610 EIRA Github Repository: https://github.com/CarTool-EC/EIRA'
'The Dublin Core Ontology may enable digital service delivery channels. European Legislation Identifier (ELI) is using DCMI in some of its use cases, increasing the access to legislative documents. ELI is adopting the DCMI Legislation vocabulary. DCMI About: https://www.dublincore.org/about/ ELI-Joinup reference: https://joinup.ec.europa.eu/collection/eli-european-legislation-identifier/solution/eli-legislation-extension-schemaorg/about '
The purpose of XML is not related to organisational interoperability. Therefore, this criterion is not applicable to the specification.
This document sets out Best Practices tailored primarily for those who publish data on the Web. The Best Practices are designed to meet the needs of information management staff, developers, and wider groups such as scientists interested in sharing and reusing research data on the Web. W3C reference: https://www.w3.org/TR/dwbp/
"The specification is associated with two EIRA's ABB in the EIRA Library of Interoperabiliy Specifications (ELIS). The specification is associated with the European Legal Act and Legal Act ABBs in the Legal View, and the Legal Act Representation in the Semantic View. ELIS reference: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/v501"
'The purpose of JSON is not related to the authentication of the roles involved in data transactions. Therefore, this criterion is not applicable to the specification. JSON specification: https://www.ecma-international.org/wp-content/uploads/ECMA-404_2nd_edition_december_2017.pdf'
UDDI is not included within any catalogue of standards at European level.
'By allowing the publication and discovery of web services, UDDI helps to reduce administrative burden avoiding administration and stakeholders to spend time searching for web services and improving the results while integrating services and exchanging data. UDDI OASIS reference: https://www.oasis-open.org/standard/uddi/'
'The specification allows for extension. The specification is designed to be modular and extensible, which enables implementers to add new elements, attributes, or namespaces to the existing XML schema to meet specific requirements. Implementers can extend the Akoma Ntoso specification by defining their own modules or components that incorporate new functionality or modify the behavior of the specification. These extensions can be developed in accordance with the guidelines and best practices provided by the specification, which help to ensure interoperability between different implementations. AKN4EU reference: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/akn4eu'
DCAT is hosted at W3C's website and it is available to everyone for free for its use, implementation or study. See: https://www.w3.org/TR/vocab-dcat-2/
'HTTPS achieves information confidentiality through the use of SSL/TLS (Secure Sockets Layer/Transport Layer Security) protocols, which encrypt the data exchanged between the client and server. The encryption process scrambles the information in such a way that it can only be deciphered by the intended recipient, ensuring that it remains confidential even if intercepted during transit. HTTPS specification: https://tools.ietf.org/html/rfc2818'
'ISO/IEC 27001 does not depend on other standards such as ISO/IEC 27002. Moreover, it can be implemented without relying on specific technologies, as ISO/IEC 27001 comprises a set of requirements that ensure the compliance with ISMS. ISO 27001 reference: https://www.iso.org/obp/ui/#iso:std:iso-iec:27001:ed-2:v1:en '
There are no disclosures within the ISO IPR Database to identify the licensing under the specification can be used. ISO patents: https://www.iso.org/iso-standards-and-patents.html ISO standards and patents IPR database: http://isotc.iso.org/livelink/livelink/13622347/Patents_database.xls?func=doc.Fetch&nodeId=13622347
RDF N-Triples is a lined-based plain text format that performs encoding RDF graphs, this encoding is carried out by using UTF-8. As RDF is the main technology used to publish Linked Open Data (LOD), therefore, the specification could help to the publication of data as LOD. However, N-Triples presents a tedious process if the purpose is encode big amounts of data. See: https://www.w3.org/TR/n-triples/
At the time of elaborating this assessment, this specification is not included in any EIRA ABB in the current EIRA Library Of Interoperability Specifications (ELIS). EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/solution/elis/release/v100
'The PROV family of documents has not been found recommended by any Member State. PROV Primer document: https://www.w3.org/TR/prov-primer/ PROV Ontology: https://www.w3.org/TR/2013/REC-prov-o-20130430/ PROV Data Model: https://www.w3.org/TR/2013/REC-prov-dm-20130430/'
RDF is included in 4 national catalogues of recommended specifications. They belong to the Netherlands, Slovakia, Spain, and Sweden. The National Interoperability Framework (NIF) of these Member States is fully aligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards https://joinup.ec.europa.eu/collection/national-interoperability-framework-observatory-nifo/nifo-factsheets
'ODRL is a policy expression language that provides a flexible and interoperable information model, vocabulary, and encoding mechanisms for representing statements about the usage of content and services. This fact is a key aspect for the interaction and the collaboration between parties and how they need to consume content or services. W3C specification reference: https://www.w3.org/TR/odrl-vocab/#vocab-core'
'The specification was developed in 2001, by OASIS. It has been evolved over the years demonstrating that it overcame the possible issues raised on the developement and implementation. Moreover, the version of the issue being assessed is the 3.0, which enforces the maturity of the spec for its use in the developement of products and services. Furthermore, the XACML specification has matured enough to be supported in a growing number of commercial identity management products. XACML OASIS reference: https://docs.oasis-open.org/xacml/3.0/xacml-3.0-core-spec-os-en.html#_Toc325047066 XACML coverpages reference: https://xml.coverpages.org/xacml.html'
'FTP is a protocol exclusively designed for the transfer of files which does not secure the traffic. However, there are existing extensions of FTP that secure the information delivery. For instance, FTP over TLS, known as FTPS, uses the Transport Layer Security (TLS) to secure FTP communications over a network. FTP Specification Reference: https://datatracker.ietf.org/doc/html/rfc959 Securing FTP with TLS Reference: https://tools.ietf.org/html/rfc4217'
'UTF-8 itself does not allow customization, but it can be used as a basis for custom encodings or variations that include additional characters or provide optimizations for specific use cases. However, using custom encodings may create interoperability issues with other systems that use standard UTF-8 encoding. UTF-8 specification: https://datatracker.ietf.org/doc/html/rfc3629 '
The IETF is a consensus-based group, and authority to act on behalf of the community requires a high degree of consensus and the continued consent of the community. The process of creating an Internet Standard is straightforward: a specification undergoes a period of development and several iterations of review by the Internet community and revision based upon experience, is adopted as a Standard by the appropriate body... and is published. In practice, the process is more complicated, due to (1) the difficulty of creating specifications of high technical quality; (2) the need to consider the interests of all of the affected parties; (3) the importance of establishing widespread community consensus; and (4) the difficulty of evaluating the utility of a particular specification for the Internet community. The goals of the Internet Standards Process are:_x000D_ - technical excellence_x000D_ - prior implementation and testing;_x000D_ - clear, concise, and easily understood documentation;_x000D_ - openness and fairness; and _x000D_ - timeliness_x000D_ The goal of technical competence, the requirement for prior implementation and testing, and the need to allow all interested parties to comment all require significant time and effort. The Internet Standards Process is intended to balance these conflicting goals. The process is believed to be as short and simple as possible without sacrificing technical excellence, thorough testing before adoption of a standard, or openness and fairness._x000D_ See:https://www.ietf.org/standards/process/
'NUTS is included in the Taxonomies EU Vocabularies repository of standards. Publications Office, EU Vocabularies repository: https://op.europa.eu/en/web/eu-vocabularies/taxonomies'
At the moment of performing the assessment, UTF-8 is widely adopted in environments developing and implementing ICT solutions including innovative solutions.
Xforms 2.0 is an XML format used for collecting inputs from web forms. Although it is used in a wide variety of solutions, it does not foster the creation of innovative solutions. Xforms 2.0 W3C reference: https://www.w3.org/community/xformsusers/wiki/XForms_2.0
'The European Interoperability Reference Architecture is based on ArchiMate, an open standard. Also, it is modelled using Archi, an open-source tool that is also based on ArchiMate and TOGAF. It provides Open Exchange Formats (xml based) that allow users to use it in out of Archi tool. EIRA reference: https://interoperable-europe.ec.europa.eu/collection/european-interoperability-reference-architecture-eira /solution/eira/release/610 EIRA Github Repository: https://github.com/CarTool-EC/EIRA Archi - Archimate Modelling Tool: https://www.archimatetool.com/ Archimate: https://www.opengroup.org/archimate-forum/archimate-overview'
ADMS, as a vocabulary, can be implemented and reused independently of the amounts of data without hampering the scalability or the interoperability of systems. The reuse of the specification for the description of Interoperability Solutions or assets would ease and enhance the interoperability. ADMS Specification W3C: https://www.w3.org/TR/vocab-adms/
"Schema.org was founded by big tech companies and its use is widespread in the major search engines like Google or Yahoo! (see Schema.org homepage reference, 'About Schema.org' section). Schema.org started in 2011 and went through 14 major releases in the last nine years, the last one in 2022. Besides, the schema.org project publishes documentation on all the specification's supporting processes on its Releases section. Schema.org homepage reference, 'About Schema.org' section: https://schema.org/docs/about.html Schema.org reference, Releases section: https://schema.org/docs/releases.html"
'The Basic Formal Ontology (BFO) is a small, upper level ontology that is designed for use in supporting information retrieval, analysis and integration in scientific and other domains. Thus the specification is conceived as a tool to facilitate organisational interoperability agreements. BFO reference: https://www.iso.org/standard/74572.html'
'Publiccode.yml does not include a real conformance testing suit, however, within the documentation there are explicitly stated which elements are mandatory or not, allowing the users to check and correct their publiccode.yml files accordingly. Moreover, there are different YAML syntax validator that can help to ensure files are properly built. Publiccode.yaml documentation: https://docs.italia.it/italia/developers-italia/publiccodeyml-en/en/master/index.html Section "The Standard": https://docs.italia.it/italia/developers-italia/publiccodeyml-en/en/master/schema.core.html# YAML Validator Checker: https://yamlchecker.com/ YAMLint: https://www.yamllint.com/'
'The purpose of SOAP 1.2 is not related to e-accessibility. Therefore, this criterion is not applicable to the specification. SOAP Reference: https://www.w3.org/TR/soap12/'
The purpose of FTP is not related to organisational interoperability. Therefore, this criterion is not applicable to the specification.
SEMIC, the Semantic Interoperability Community, who is in charge of developing DCAT-AP has a specific Change and Release Management Policy for DCAT-AP where they encourages any stakeholder to contribute to the development of the specification. See: https://joinup.ec.europa.eu/solution/dcat-application-profile-data-portals-europe/document/change-and-release-management-policy-dcat-ap https://joinup.ec.europa.eu/solution/dcat-application-profile-data-portals-europe/about https://github.com/SEMICeu/DCAT-AP
The purpose of LDAP is not related to the delivery of multilingual public services. Therefore, this criterion is not applicable to the specification. LDAP IETF reference: https://tools.ietf.org/html/rfc4511
The purpose of LegalDocML is to provide a format for long-term storage and access to parliamentary, legislative and judicial documents that allows search, interpretation and visualization of documents. Concequently, it can be said that the specification fosters data portability between systems and applications. LegalDocML reference: https://www.oasis-open.org/committees/legaldocml/charter.php
There is no Member State that includes PAdES (ISO 14533-3:2017) in their national catalogue with The National Interoperability Framework (NIF) aligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'E-ARK CSIP is in itself a tool that provides detailded guidelines for the development of e-archiving systems, establishing common understanding of the requirements which need to be met in order to achieve interoperability of information packages, therefore, it is a tool to assess the correct implementation of the aforementioned systems. E-ARK CSIP specification: https://earkcsip.dilcis.eu/#introduction'
'The purpose of MIME is not related to organisational interoperability. Therefore, this criterion is not applicable to the specification. MIME reference: https://tools.ietf.org/html/rfc2045'
'The Asset Administration Shell (AAS) has specific provisions regarding data integrity since the main purpose of the specification is the sharing of the manufacturing assets. In this sense the specification provides reference to the IEC 63278-4 as a means to protect the data from unauthorised changes. Data integrity in the AAS: https://admin-shell-io.github.io/aas-specs-antora/IDTA-01004/v3.0/introduction.html#_integrity_protection Details of the Asset Administration Shell (AAS) https://industrialdigitaltwin.org/en/wp-content/uploads/sites/2/2024/06/IDTA-01001-3-0-1_SpecificationAssetAdministrationShell_Part1_Metamodel.pdf'
IPSec is a business domain agnostic specification.
'After being evaluated compliant with the regulation on standardisation 1025/2012, LDAPv3 has been identified by Commission Implementing Decision and included in the European list of ICT Standards for eprocurement. The specification can also be found in the Joinup repository. ICT technical specifications: https://single-market-economy.ec.europa.eu/single-market/european-standards/ict-standardisation/ict-technical-specifications_en?prefLang=es'
'The purpose of Extensible Forms Description Language is not related to secure exchange of data since the specification not provide any reference to security considerations. Extensible Forms Description Language reference: https://www.w3.org/TR/NOTE-XFDL'
'DQV has been used in the ALIGNED project. ALIGNED is developing tools and methods for parallel software and data engineering of web-scale information systems. Moreover, the concrete objective of ALIGNED is to demonstrate that the tools and methods that are developed can be integrated into the work-flows of all of these four use cases in such a way that they produce measurable improvements in terms of productivity, quality and agility. Furthermore, the results of the ALIGNED project have been incorporated to DQV evolution and development. ALIGNED project reference: https://cordis.europa.eu/project/id/644055/reporting'
'While Domibus may not be the central solution for e-accessibility, it plays a role within the broader context of ensuring that digital services and systems are inclusive and usable for all individuals, including those with disabilities. Domibus specification: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/Domibus'
'ETSI TS 119 512 has been developed to enable the long-term preservation of electronic signatures, in which case it also includes the retrieval of these electronic signatures through a storage system. The features provided by this specification are considered very valuable in reducing the administrative burden, as it facilitates the storage and preservation of data, ensuring that document signatures remain valid over time. ETSI TS 119 512 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.02_60/ts_119512v010102p.pdf'
'The specification is a reference model that provides a common basis for the coordination of standards development for the purpose of systems interconnection. Through a conceptual and structured approach, the specification can provide valuable insights and principles that can be applied to the modelling, analysis, and improvement of business processes, especially in environments where information systems and networked operations play a critical role. OSI reference https://www.iso.org/standard/20269.html'
Slovenia is recommending ODRL2 in its ICT National Catalogue. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
"There are many papers evaluating the specification's efficiency. An example of a paper evaluating GraphQL effectiveness: https://ieeexplore.ieee.org/abstract/document/9163501"
The purpose of this Core Vocabulary is not related to the modelling of organisational interoperability aspects. Therefore, this criterion is not applicable to the specification. CCCEV reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-criterion-and-core-evidence-vocabulary
The specification was carried out in 2004 and has been developed and maintained by OASIS. It has had one update version 1.1 in 2006. The last version contained significant changes.
'XHTML does not ensure and enable data processing accuracy. Therefore, this criterion is not applicable to the specification. XHTML W3C reference: https://www.w3.org/TR/xhtml1/'
'Syslog is primarily focused on the transmission and reception of log messages and does not inherently guarantee data processing accuracy. However, following the standard format proposed by the protocol can guarantee data accuracy to an extent. Syslog Protocol: https://datatracker.ietf.org/doc/html/rfc5424'
'The purpose of EuroVoc is to facilitate the processing of data of administations mainly European but also National. By allowing to make the data available to other persons or organisations, the EuroVoc Contributes to the development of eGovernment reducing the administrative burden. EuroVoc: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource /dataset/eurovoc'
'The ebXML specification includes detailed guidelines for business process modeling, which helps in defining and automating administrative procedures. Additionally, the registry and repository components manage metadata about services, facilitating efficient discovery and access. Finally, the messaging services ensure reliable and secure delivery of business information, which is crucial for handling administrative data. ebXML RegRep OASIS reference: https://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html'
'DNS is independent of any specification and can be implemented without dependencies with technologies. DNS IETF reference: https://datatracker.ietf.org/doc/html/rfc8499 Domain Names - Implementation and Specification: https://tools.ietf.org/html/1035'
'OAS takes into account essential safety aspects when it comes to the design of APIs. Security in OAS is tackled with the "Security Requirement Object" where security mechanisms are settled to authorise requests. OAS Security Requirements Object: https://spec.openapis.org/oas/latest.html#security-requirement-object OAS specification: https://spec.openapis.org/oas/latest.html#openapi-specification OAS in Github: https://github.com/OAI/OpenAPI-Specification/#participation'
'The Internet Engineering Task Force (IETF), a global, open standards organization not specific to any particular region or governmental body, developed HTTP. While not a European Standard, HTTP is used extensively across all Member States. HTTP and IETF reference: https://developer.mozilla.org/en-US/docs/Web/HTTP/Evolution_of_HTTP#http1.1_%E2%80%93_the_standardized_protocol '
'Neither PROV, nor any of its specifications have been found included in the National Catalogue of recommended specifications of any Member State. CAMSS List of standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
'LDAP has some mechanisms to guarantee the integrity and confidentiality of the data. Some of them are Transport Security Layer (TLS), and Simple Authentication and Security Layer (SASL) mechanisms, such as DIGEST-MD5 and GSSAPI. Linuxtopia Data Integrity and Confidentiality Protection: https://www.linuxtopia.org/online_books/network_administration_guides/ldap_administration/security_Data_Integrity_and_Confidentiality_Protection.html? LDAP Authentication methods and security mechanisms: https://www.rfc-editor.org/rfc/rfc4513.txt'
CAMSS Assessment of OData EIF Scenario v1.0.0
'DNS can be extended with several transport protocols to provide a safer data exchange. the Domain Name System Security Extensions (DNSSEC) modify DNS to add support for cryptographically signed responses, while other extensions such as Transaction Signature (TSIG), add support for cryptographic authentication between trusted peers and are commonly used to authorize zone transfer or dynamic update operations. Resource Records for the DNS Security Extensions: https://datatracker.ietf.org/doc/html/rfc4034 Extension Mechanisms for DNS: https://datatracker.ietf.org/doc/html/rfc6891 DNS IETF reference: https://www.ietf.org/rfc/rfc1034.txt '
'According to section 4.4 of the ETSI TS 119 512 specification document, the Profile element outlines the technical details of a preservation profile, allowing a client to use the preservation interface to communicate with the preservation service. Full implementation of specific provisions is achieved when combined with its companion documents, ETSI TS 119 511. This combination ensures a more comprehensive understanding of administrative procedures, rules, and services. ETSI TS 119 512 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.02.01_60/ts_119512v010201p.pdf ETSI TS 119 511 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119511/01.01.01_60/ts_119511v010101p.pdf'
'OData offers a way to both break down data silos and increase the shared value of data. The specification contributes to creating an ecosystem where data consumers and producers can interoperate more than ever, allowing more applications to make sense of a broader set of data. In this sense, the specification promotes comprehensibility, for example through the OData data model. However, no evidence was found in terms of promoting and supporting the comprehensibility of European public services. About ODP - OASIS Open Data Protocol (OData) TC (Joinup): https://joinup.ec.europa.eu/collection/ict-standards-procurement/solution/odp-oasis-open-data-protocol-odata-tc/about'
'Although ISAE 3402 is not developed by European Organisations that are following the European Standardisation Regulation, it is being recommended by ENISA according to the report for Security certification practice in the EU. ENISA webpage: https://www.enisa.europa.eu/publications/security-certification-practice-in-the-euinformation-security\x02management-systems-a-case-study/at_download/fullReport '
The purpose of DNS is not related to the publication of public data as open data. Therefore this criterion is not applicable to this specification.
The purpose of XML is not related to e-accessibility. Therefore, this criterion is not applicable to the specification.
'The purpose of OData is not related to the organisational interoperability agreements per se, but given that it is recommended by Microsoft it can be argued that OData can serve as a baseline to facilitate interoperability agreements since the main strength of the specification is the semantic interoperability. OData reference: https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#_Toc31358832 '
'Effective data management practices, as encouraged by ISO/IEC 19944-1, can contribute to an improved comprehensibility of administrative procedures, rules, data, and services within cloud computing environments. By categorizing and organizing data according to the provided classification scheme, organisations can enhance the visibility and accessibility of their data assets, including administrative procedures and rules. Additionally, ISO/IEC 19944-1 promotes effective governance and management of cloud services, which can indirectly contribute to the comprehensibility of services within cloud computing environments. By adopting the recommended practices outlined in the specification, organisations can establish clearer governance structures, define service management processes, and ensure the appropriate comprehensibility of services. ISO/IEC 19944-1 specification: https://www.iso.org/standard/60545.html'
'DPV provides a taxonomy of technical and organisational measures for representing information about how the processing of personal data is technically and organisationally protected, safeguarded, secured, or otherwise managed. By referring to what measures are in place (such as GDPR) DPV directly addresses issues about the secure processing of data pointing to the compliance of legal obligations to ensure data protection. DPV specification: https://w3c.github.io/dpv/primer/'
W3C provides a test suite for free to assess SHACL implementations. See: https://w3c.github.io/data-shapes/data-shapes-test-suite/
'OAIS provides a comprehensive framework for protecting information against unauthorized changes, helping to ensure that digital objects and metadata remain authentic, reliable, and trustworthy over time. OAIS specification: https://public.ccsds.org/Pubs/650x0m2.pdf '
CAMSS Assessment of DNS EIF Scenario v2.0.0
"Better Regulation Toolbox (as a part of the Better Regulation framework) is a European Commission resource designed as a complement to the Commission's Better regulation guideline. Even though it could be extended or modified to fit other business requirements at the National level, for instance, there are no implementations that evidence the possibility of extension to other business domains other than the development of public policies and laws. Better Regulation Guidelines and Toolbox reference: https://commission.europa.eu/law/law-making-process/better-regulation/better-regulation-guidelines-and-toolbox_en Better Regulation Toolbox reference: https://commission.europa.eu/document/download/9c8d2189-8abd-4f29-84e9-abc843cc68e0_en?filename=BR%20toolbox%20-%20Jul%202023%20-%20FINAL.pdf."
'UTF-8 can be used as part of a larger strategy for secure processing of data. UTF-8 can be used to encode data that is being transmitted over a secure channel or stored securely in a database, but additional security measures such as encryption, access controls, and authentication are necessary to ensure the secure processing of data. UTF-8 specification: https://datatracker.ietf.org/doc/html/rfc3629'
As RDF defines a common framework to express information that can be exchanged between applications without losing meaning, it fosters the trustworthy data exchange between administrations and stakeholders.
RegOrg is publicly available for its use and implementation. It is available for everyone to study with no cost on Joinup webpage. Moreover, it is also available on W3C webpage. RegOrg Joinup reference: https://joinup.ec.europa.eu/solution/registered-organization-vocabulary RegOrg W3C reference: https://www.w3.org/TR/vocab-regorg/
'UTF-8 allows for extensions to add support for additional characters or optimize the encoding for specific use cases, but any extensions must be defined and documented to ensure compatibility with other systems that use UTF-8. UTF-8 specification: https://datatracker.ietf.org/doc/html/rfc3629 '
IPsec is available at the ICT Standards for Procurement Joinup for its use and implementation. See: https://joinup.ec.europa.eu/solution/ietf-rfc-4301-2005-security-architecture-internet-protocol/distribution/ietf-rfc-4301-2005-security-architecture-internet-protocol
'There are existing tools that allow for the testing and implementation of DIDs. The DID Test Suite performs interoperability tests on the W3C Decentralized Identifier specification and is maintained by the W3C DID Working Group. There are three types of implementations that this test suite tests: DID Methods, DID Resolvers, and DID URL Dereferencers. DID Test Suite: https://github.com/w3c/did-test-suite '
The purpose of HTML5 is not related to organisational interoperability. Therefore, this criterion is not applicable to the specification.
'The Advanced Encryption Standard facilitates organisational interoperability agreements by offering a widely adopted, open, and technically detailed encryption standard. This allows organisations to have a common basis for data security in their interactions, and to facilitate the exchange of data. AES Standard Reference: https://csrc.nist.gov/pubs/fips/197/final'
The European Union Agency For Network And Information Security includes within a set of guidelines for implementing qualified electronic time stamps. That means that the specification, as part of this set of guidelines, is recommended when handling Timestamps. ENISA Security guidelines on the appropriate use of qualified electronic time stamps: https://security.stackexchange.com/questions/173652/how-to-timestamp-a-document-without-electronic-signature-under-eidas
'Several implementations are assessing the usefulness and exploring how the usage of this specification can enhance the accessibility to digital platforms. Some of them are React Aria and Mozilla. However, this does not extend to the European Public Service. Mozilla reference, Accessibility section: https://developer.mozilla.org/en-US/docs/Web/Accessibility React Aria reference, home page: https://react-spectrum.adobe.com/react-aria/'
There are document of the European Commission assessing the suitability of XSLT specification. See: https://ec.europa.eu/cefdigital/DSS/webapp-demo/doc/dss-documentation.html#_xades_profiles
"EN 303 645 is associated to the consumer IoT device and the data security domain. EN 303 645 is a comprehensive, single-purpose specification that manufacturers and IoT stakeholders need in order to meet basic security requirements (see EN 303 645 homepage, 'International alignment and adoption' section). European directives are currently making an effort to verticalise the consumer IoT industry (see EN 303 645 homepage reference, about the vertical standard concept), opening up new possibilities to other domains (see Europe Plans on IoT reference). However, there is no evidence of the use of the specification in other domains, nor in the public sector. EN 303 645 homepage, 'International alignment and adoption' section: https://www.etsi.org/technologies/consumer-iot-security EN 303 645 homepage, 'Vertical Standard' section: https://www.etsi.org/technologies/consumer-iot-security Europe Plans on IoT reference: https://joinup.ec.europa.eu/collection/rolling-plan-ict-standardisation/internet-things"
The purpose of SMTP is not related to organisational interoperability. Therefore, this criterion is not applicable to the specification. SMTP IETF reference: https://tools.ietf.org/html/rfc5321
'IEEE Std 802.3-2022 primarily focuses on the physical and data link layers for Ethernet networks, and it does not directly address multilingualism. Therefore, this criterion is not applicable to this specification. IEEE Std 802.3-2022 Reference: https://ieeexplore.ieee.org/document/9844436'
PNG is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, PNG can define the interoperability aspects of the "Representation" ABBs of the EIRA Semantic View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/solution/elis/release/v100
'The implementation of e-signature is a mean that allows administrations and stakeholders to exchange digital data reducing the amount of non-digital documents exchanged. Additionally, it fosters the reuse of data across borders, which as well takes part in the administrative burden reduction. ETSI TS 119 512 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.02_60/ts_119512v010102p.pdf ETSI EN 319 401 specification: https://www.etsi.org/deliver/etsi_en/319400_319499/319401/02.03.01_60/en_319401v020301p.pdf'
'The XACML specification can be found in the DSSC catalogue, classified as a Data Sovereignty and Trust standard. DSSC catalogue: https://dssc.eu/space/SE1/185794711 /Data+Sovereignty+and+Trust+standards+and+technologies+landscape'
LegalDocML is XML based, however, it is not dependent on any other technology or platform, so it can be implemented independently from specific technologies or platforms. LegalDocML reference: https://www.oasis-open.org/committees/legaldocml/charter.php
'Genericode is designed to be technology agnostic. It is defined using XML, which is a widely adopted and platform-independent markup language. XML can be processed and interpreted by a variety of programming languages, frameworks, and tools, making genericode usable across different technology stacks and platforms. Code List Representation (genericode): https://docs.oasis-open.org/codelist/genericode/v1.0/os/genericode-v1.0-os.html'
'The only way the information can be long-term preserved is if it gets a PDF file copy of the REM Message containing it. ETSI EN 319 532-3 reference: https://www.etsi.org/deliver/etsi_en/319500_319599/31953203/01.02.01_60/en_31953203v010201p.pdf'
'The Asset Administration Shell (AAS) has specific provisions regarding encryption of data shared among partners that allow the confidentiality of data. Furthermore the specification also allows third party extensions to conform to more strict encryption. Details of the Asset Administration Shell (AAS) https://industrialdigitaltwin.org/en/wp-content/uploads/sites/2/2024/06/IDTA-01001-3-0-1_SpecificationAssetAdministrationShell_Part1_Metamodel.pdf'
'The specification is included in an initiative at European level covering privacy aspect. As an example, the implementation of CESOP Legislative Package , which monitor the payees of cross-border payments and transmit information. XSD Reference: https://www.w3.org/TR/2012/REC-xmlschema11-1-20120405/ Legislative Package CESOP Reference: https://taxation-customs.ec.europa.eu/taxation-1/central-electronic-system-payment-information-cesop_en Electronic system of payment information to combat fraud regulation Reference: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32022R1504'
'To maintain the confidentiality, integrity, and availability of financial information, ISAE 3402 implements controls that trace the movements of that data as well as preserve it. ISAE 3402 UK website reference: https://isae3402.co.uk/isae-3402'
After searching in the different official European websites, there is no evidence of any cross-border project that use CLV nor explicit agreements involving the usage of the specification.
PDF/A does not define a cross-sector reusable data model, but defines a file format for representing electronic documents. PDF/A reference: https://www.iso.org/standard/38920.html https://www.iso.org/standard/50655.html
'DCAT-AP has been selected for the description of datasets by three European Initiatives: The European Data Portal, The European Open Data Portal and the JRC Data Catalogue. DCAT-AP for data portals: https://joinup.ec.europa.eu/solution/dcat-application-profile-data-portals-europe/about '
The rules on European standardisation allow the European Commission to identify information and communication technology (ICT) technical specifications - that are not national, European or international standards - to be eligible for referencing in public procurement. This allows public authorities to make use of the full range of specifications when buying IT hardware, software and services, allowing for more competition in the field and reducing the risk of lock-in to proprietary systems. After being evaluated compliant with the regulation on standardisation 1025/2022, IPSec has been identified by Commission Implementing Decision and included in the European list of ICT Standards for e-procurement. See: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en
The purpose of TSP is not related to e-accessibility. Therefore, this criterion is considered not applicable specification. TSP IETF reference: https://tools.ietf.org/html/rfc3161
LegalRuleML aims to close the gap between natural language text description and semantic norm modelling. Providing a common solution for treating legal resources the specification can then foster Semantic Web technologies such as: NLP, Information Retrieval (IR), graph representation, as well as Web ontologies and rules. Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/en/ LegalDocML reference: http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/legalruleml-core-spec-v1.0.html
'The specification is sufficiently mature, and there is documentation available on the following link: IPSec Working Group Documents: https://tools.ietf.org/wg/ipsec'
DCAT-AP is available on Joinup, the collaborative platform created by the European Commission to share and reuse IT solutions and good practices. See: https://joinup.ec.europa.eu/solution/dcat-application-profile-data-portals-europe/releases
'DQV allows for the documentation of metadata concerning the provenance and sources of data. By providing details about where data originates and the process through which it was collected and processed, DQV helps to establish the authenticity of the data. Knowing the provenance can assure users that the data has not been altered inappropriately and remains true to its original source. DQV reference: https://www.w3.org/TR/vocab-dqv/#DimensionsOfISOIEC25012'
"TLS 1.3 provides mechanisms for reusing relevant information, notably through Pre-Shared Keys and session tickets. With this method, systems save and reuse details from earlier secure exchanges, speeding up future connections. As an example, after a client authenticates, the server can give it a 'ticket' to remember that authentication, avoiding the need to re-authenticate next time. TLS 1.3 Resumption and Pre-Shared Key Reference: https://www.rfc-editor.org/rfc/rfc8446.html#section-2.2 TLS 1.3 Session tickets Reference: https://www.rfc-editor.org/rfc/rfc8446.html#section-4.6.1"
'The purpose of genericode is not related to providing an access control mechanism. Therefore, this criterion is considered not applicable to this specification. Code List Representation (genericode): https://docs.oasis-open.org/codelist/genericode/v1.0/os/genericode-v1.0-os.html'
'ETSI TS 119 612 is part of the Electronic Signatures Infrastructure (ESI) family of specifications. The ESI dates back to 2012, when the General Policy Requirements for Trust Service Providers supporting Electronic Signatures (ETSI EN 319 401) specification was first issued. Since its first publication, there have been many extensions one of which is ETSI TS 119 612, whose version 2.2.1 was released in 2016 when the eIDAS regulation identified the need to create protocols to develop preservation services for trust service providers, as mentioned in ETSI SR 019 510. Finally, in 2024 was published the latest version of the specification (version 2.3.1). ESI specification history: https://standards.globalspec.com/std/14387016/EN%20319%20401 ETSI TS 119 612 specification: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf ETSI EN 319 401 specification: https://www.etsi.org/deliver/etsi_en/319400_319499/319401/02.03.01_60/en_319401v020301p.pdf ETSI SR 019 510 specification: https://www.etsi.org/deliver/etsi_sr/019500_019599/019510/01.01.01_60/sr_019510v010101p.pdf eIDAS blog, New APIs for the eIDAS-Ecosystem: https://blog.eid.as/tag/etsi-ts-119-512-en/'
The information on (new) standardisation activities is widely announced via the IETF websites and working group activities. There also is a mailing list one can subscribe to for announcements. This so-called IETF Announce list receives announcements about IETF meetings, the activities and actions of the IESG, the RFC Editor, the NomCom, and other announcements of interest to the IETF community. See: https://www.ietf.org/how/lists/announcement/
'ISO/IEC 7498:1 is primarily a conceptual framework for network communication and does not explicitly address the reuse of information in terms of data or content. However, the principles of modularity and layering within the OSI model indirectly support the reuse of relevant information. ISO/IEC 7498:1: https://www.iso.org/standard/20269.html'
Xforms 2.0 is publicly available for implementation and use for free on W3C's webpage. Therefore, it can be reused by the organisations, administrations, open communities, etc. that developed it. Xforms 2.0 W3C reference: https://www.w3.org/community/xformsusers/wiki/XForms_2.0
As Internet Protocol Stack, IPv6 it is being selected gradually by different Member States. The specification is the most used for the data exchange over the internet therefore IPv6 fosters the visibility of data across borders. The European Union is willing to implement the IPV6 as state on the following report: "The adoption of IPv6 in Europe, in particular within European public administrations, is still low, but the availability of IPv6 communication is vital for the economic development and the digitisation of European public administrations. The goals of the Digital Agenda for Europe and the Digital Single Market Strategy are based on stable and reliable data networks." See: https://ec.europa.eu/isa2/sites/isa/files/ipv6_framework_for_european_governments_0.pdf
'Slovenia is recommending ODRL2 in its ICT National Catalogue. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards '
'Digital service delivery channels involve the use of digital technologies to provide services to users or customers. These channels can include websites, mobile applications, APIs, and other digital platforms. The OSI model, as a conceptual framework, contributes to the development and interoperability of protocols that may be used in creating these digital service delivery channels. OSI reference https://www.iso.org/standard/20269.html'
SHACL is a web standard whose only purpose is RDF data graphs validation. Moreover, there are no implementations of SHACL in domains different from the one it was originally developed for.
'While SCIM provides a foundation for managing user identities, the secure processing of data goes beyond the scope of the SCIM specification. Instead, the secure processing of data relies on the implementation of SCIM in conjunction with various security practices and mechanisms. SCIM: https://scim.cloud/'
'CSV makes sure content is available on the web, structures data and makes it usable in a non-proprietary open format. Consequently the CSV enables the digital service delivery channels as it makes files available for any system. CSV reference: https://datatracker.ietf.org/doc/html/rfc4180'
'The CPSV-AP allows describing public services in a standardised human and machine-readable format. This fact fosters the discoverability of the datasets containing information about public services. Therefore, it enhances its reuse and visibility. CPSV-AP Joinup webpage: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/core-public-service-vocabulary-application-profile/release/22 Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/en/'
'Due to its machine-readable nature, iCalendar has become a widely adopted standard for exchanging calendar data across various platforms and applications, making it an essential tool for automating calendar-related tasks and enabling seamless integration between different software systems. Moreover, the iCalendar format is designed to be easily shareable and disseminated across the internet, making it a good choice for publishing calendar information on websites or web-based applications. iCalendar specification: https://www.rfc-editor.org/rfc/rfc5545'
'The GraphQL specification preserves the information as long as you mantain the API where the information is maintained. If it gets deleted so will the data in it. GraphQL clients can use HTTP caching to easily avoid refetching resources, and for identifying when two resources are the same. GraphQL FAQ Website: https://graphql.org/faq/#why-should-i-use-graphql GraphQL Caching: https://graphql.org/learn/caching/'
'The specification allows the secure processing of data between parties. It is mainly used to ensure single sign-on (SSO) and by doing so, it secures the processing of data. It extends SSO across security domains independently from any platform which prevents non-interoperable proprietary technologies. For instance, a relevant implementation of SAML 2.0 is SAML Web Browser SSO profile. This profile was specified to promote interoperability by allowing the authentication to service providers through external identity providers. SAML 2.0 Reference: http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-tech-overview-2.0.html'
"There are many tools assessing the conformance of DNS's implementations. For instance, the DNS Compliance Testing provides tools to allow Registries and Registrars (amongst others) to check the DNS protocol compliance of the servers they are delegating zones to. GITHUB DNS Compliance Testing: https://gitlab.isc.org/isc-projects/DNS-Compliance-Testing"
XSD 1.1 is supporting the second level of maturity of Tim Berners-Lee's 5-stars schema for open data. It eases the availability of the data and structures XML files. Additionally, XSD 1.1 is implied within the RDF 1.1 XML Syntax, used for the serialisation of RDF documents as XML. Therefore, XSD fosters the publication of data as Open Data. See: https://5stardata.info/en/ https://www.w3.org/TR/rdf-syntax-grammar/
'PROV primarily focuses on capturing and representing provenance information rather than providing specific mechanisms for secure data processing. However, the use of PROV in systems or applications can indirectly contribute to the secure processing of data by providing traceability, accountability, integrity, and auditing capabilities. PROV Primer document: https://www.w3.org/TR/prov-primer/ PROV Ontology: https://www.w3.org/TR/2013/REC-prov-o-20130430/ PROV Data Model: https://www.w3.org/TR/2013/REC-prov-dm-20130430/'
The Better regulation toolbox is an internal European Commission resource designed as a complement to the Commission's Better regulation guideline. It provides specific and operational guidance to those involved with the various better regulation instruments. These instruments aim to give support for the implementation, monitoring, and impact assessment of public policies and laws on which new and innovative solutions should be based. Therefore, it can be considered that the Better Regulation Toolbox fosters the creation of innovative solutions and services across Europe. Better Regulation Toolbox reference: https://ec.europa.eu/info/sites/info/files/better-regulation-toolbox_2.pdf .
'9 Member States are recommending XHTML in their ICT National Catalogues. This Member States are Cyprus, Estonia, France, Germany, Greece, Norway, Poland, Slovenia and Spain. National Catalogue of Cyprus: https://dits.dmrid.gov.cy/dmrid/dits/dits.nsf/all/B83AA8E4EB4EFD19C225855800288B10/$file/Cyprus% 20eGovernment%20Interoperability%20Framework_new%20EIF_v2.0-To%20Publish.pdf National Catalogue of Spain: https://administracionelectronica.gob.es/pae_Home/pae_Estrategias/pae_Interoperabilidad_Inicio /pae_Normas_tecnicas_de_interoperabilidad.html#CATALOGOESTANDARES CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards'
After searching for a certification or conformity test to validate possible implementations or contributions to the specification the Foundation for Public Code has established a common method for validating and certificating those new codebase elements. However, there is no automated tool for users to test conformity or reach certifications. The Standard for Public Code webpage: https://standard.publiccode.net/
The purpose of CSV is not related to e-accessibility. Therefore, this criterion is not applicable to the specification.
CSV is available for free at IETF's webpage. It can be studied, implemented for free according to users' needs. See: https://tools.ietf.org/html/rfc4180
'After checking the different standard catalogues at supra-national level, there is no evidence of the inclusion of HTTP Cookies within any European catalogue of standards. ICT technical specifications: https://ec.europa.eu/growth/single-market/european-standards/ict-standardisation/ict-technical-specifications_en CENELEC and CEN search tool catalogue: https://standards.cencenelec.eu/dyn/www/f?p=CEN:105::RESET:::: CENELEC and CEN website: https://www.cencenelec.eu/'
'No project covering privacy and using UDDI, has been found. Therefore this criterion is considered not applicable to this specification. UDDI OASIS reference: https://www.oasis-open.org/committees/uddi-spec/doc/spec/v3/uddi-v3.0.2-20041019.htm#_Toc85907967'
'The Core Location Vocabulary is a business domain agnostic specification that can be reused in a cross-domain way. Core Location Vocabulary: https://interoperable-europe.ec.europa.eu/collection/semic-support-centre/solution/core-location-vocabulary/release/100'
The purpose of DCAT is not related to e-accessibility. Therefore this criterion is not applicable to this specification.
'The purpose of ISO 3166-1 is not related to facilitating the publication of open data. Therefore, this criterion is not applicable to this specification. ISO 3166-1 reference: https://www.iso.org/standard/72482.html'
'ETSI TS 119 511 is being used in the eIDAS project, which focuses on the creation of e-signature services aiming to enable secure cross-border transactions. eIDAS is based on the Regulation (EU) No 910/2014 of the European Parliament and of the Council of 23 July 2014 on electronic identification and trust services for electronic transactions in the internal market. Regulation (EU) No 910/2014 of the European Parliament and of the Council of 23 July 2014 on electronic identification and trust services for electronic transactions in the internal market: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv:OJ.L_.2014.257.01.0073.01.ENG ETSI TS 119 511 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119511/01.01.01_60/ts_119511v010101p.pdf'
'IPsec can be customised in the sense that the user might opt for one configuration or the other depending on the host implementation requirements needed to deploy the specification. For example it is possible to modify the IPsec tunnels created by the IPsec wizard or convert them into custom tunnels to access more options. IPsec tunnels customisation: https://docs.fortinet.com/document/fortigate/7.6.0/ssl-vpn-to-ipsec-vpn-migration/137787/part-2-configuring-ipsec-tunnels-using-the-vpn-wizard IPSec reference: https://www.rfc-editor.org/rfc/rfc6071.html'
'The TrainingDML-AI Standard enables data portability by defining a model and encodings for exchanging and retrieving training data via the Web. This could potentially support the implementation or evolution of European public services that use AI/ML, by enabling the standardized exchange of training data between different systems and applications. OGC TrainingDML-AI Standard: https://docs.ogc.org/is/23-008r3/23-008r3.html'
'DNS over HTTPS (DoH) is designed to be technology agnostic meaning that it operates at the application layer of the networking stack and can be implemented across different platforms and technologies. DoH focuses on securing the communication between clients (such as web browsers or applications) and DNS resolvers by encrypting DNS queries using the HTTPS protocol. DoH specification: https://datatracker.ietf.org/doc/html/rfc8484'
The rules on European standardisation allow the European Commission to identify information and communication technology (ICT) technical specifications - that are not national, European or international standards - to be eligible for referencing in public procurement. This allows public authorities to make use of the full range of specifications when buying IT hardware, software and services, allowing for more competition in the field and reducing the risk of lock-in to proprietary systems. After being evaluated compliant with the regulation on standardisation 1025/2012, HTTP has been identified by Commission Implementing Decision and included in the European list of ICT Standards for e-procurement. See: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en
'The use of the shared standard of CIM NGSI-LD API can significantly reduce complexities and barriers in establishing interoperable systems across organisational boundaries. The specification can be used to maintain a single consistent API for Context Information Management, particularly for Smart City applications and government services, which can help when drafting agreements related to that. GS CIM 009: https://www.etsi.org/deliver/etsi_gs/CIM/001_099/009/01.07.01_60/gs_CIM009v010701p.pdf'
'The objective of the Open Systems Interconnection (OSI) is the creation of a common basis for the coordination of standards development for the purpose of systems interconnection and its expansion. OSI reference https://www.iso.org/standard/20269.html'
'The purpose of Advanced Encryption Standard is not related to e-accessibility. Therefore this criterion is considered not applicable to the specification. AES Standard Reference: https://csrc.nist.gov/pubs/fips/197/final'
'The only part of the implementation that can be optional is a prerequisite in the test assertion, which is a logical expression (similar to a Predicate) which further qualifies the Target for undergoing the core test that addresses the Normative Statement. ETSI TS 119 614-1 reference: https://www.etsi.org/deliver/etsi_ts/119600_119699/11961401/01.01.01_60/ts_11961401v010101p.pdf'
'MIME provides a framework for structuring and encoding digital content, which can simplify the delivery of public services by enabling efficient, secure, and standardized communication and document exchange between government agencies and the public. MIME specification: https://tools.ietf.org/html/rfc2045'
' The HTTP Cookies can be found in the EIRA Library of Interoperability Specifications (ELIS), more specifically mapped to the Human Interface ABB in the Technical Application view. ELIS referenece: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/v110'
'There are application profiles based in SMP are part of the eDelivery building block in OASIS, which leads to the specification being an European Standard. SMP OASIS reference: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505009 Digital Building Blocks Reference: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/SMP+software'
ASiC and ASiC Baseline Profile are open standards developed and maintained by ETSI, and it is available for free at ETSI’s webpage for everyone to study or implement. See: https://www.etsi.org/standards
Like all the IETF standards, CSV is a free and open technical specification, built on IETF standards and licenses from the Open Web Foundation. CSV is therefore licensed on a royalty-free basis. No IPR disclosures have been submitted directly on the IPv6 specification (RFC 2818). See: https://tools.ietf.org/html/rfc3668
'The purpose of OSI is not related to long-term preservation of data/information/knowledge. Therefore, this criterion is not applicable to the specification. OSI reference https://www.iso.org/standard/20269.html'
The recommendatios is iming to achieve seamless interoperability, trust, and ultimately to provide growth and employment opportunities by facilitating data exchange across organisations, disciplines and geographical borders.
'SAREF is currently in its 3.1.1 version thus, major releases have been published. In addition, public documentation has been published about its supporting process, specifically related to change history and issues regarding every version. SAREF: https://saref.etsi.org/core/v3.1.1/ SAREF Change Management: https://labs.etsi.org/rep/saref/saref4auto/-/commits/prerelease-v1.1.1/'
'The specification is recomended by the Data Office of Spain. DIDs is mentioned in the Action plan for the deployment of data spaces. In this report, DIDs is mentioned as an specification for the implementation of sovereignty and trust funcionalities. Action plan for the deployment of data spaces: https://portal.mineco.gob.es/RecursosNoticia/mineco/prensa/noticias/2024/OdD-Plan_actuaciones_despliegue_espacios_datos_v1-0.pdf'
After searching in the different official European websites, a cross-border project, called SML software, has been found that uses SMTP as his email server configuration. The specification is included as the implementation of the eDelivery BDXL, which as the CEF eDelivery, aims to help the European public administrations to exchange digital data across borders fostering a common digital environment. The reference to the usage of SMTP can be found in the Quick Start Guide v2.2. Main page project: https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/SML CEF eDelivery BDXL: https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery+BDXL+1.6 Quick Start Guide v2.2: https://ec.europa.eu/cefdigital/wiki/download/attachments/82773331/BDMSL%20Quick%20Start%20Guide%20v2.2.pdf?version=1&modificationDate=1582037177388&api=v2
'The ebXML specification describes a set of security features of ebXML RegRep and incorporates different specifications to enable the secure processing of data. According to the specification documentation, ebXML supports the management of authorized users of the ebXML service. ebXML reference: http://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html ebXML RegRep Part 2: http://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-rs-v4.0-os.html#__RefHeading__32703_422331532'
'DNS Queries over HTTPS (DoH) is included in the second report of the observatory function on encryption by the Europol and Eurojust Public Information. Europol is the law enforcement agency of the European Union (EU) that aims to support its Member States in preventing and combating all forms of serious international and organised crime, cybercrime and terrorism. On the other hand, Eurojust is the European Union Agency for Criminal Justice Cooperation where national judicial authorities work closely together to fight serious organised cross-border crime. Second report of the observatory function on encryption: https://www.eurojust.europa.eu/sites/default/files/Publications/Reports/2020-01_Joint-EP-EJ-Report_Observatory-Function-on-Encryption_EN.pdf Europol: https://www.europol.europa.eu/ Eurojust Public Register: https://www.eurojust.europa.eu/public-register'
"There are no requirements on the extent of the implementation of the specification and the extent of the data contents being used should vary between use cases. It's recommended to publish sets of requirements per implementation. https://www.xbrl.org/int/gl/2016-12-01/gl-framework-2017-PWD-2016-12-01.html"
Many implementations are using OWL2 in the market. In the following link, there is a summary with some important examples. Moreover, there are a lot of software supporting the implementation and usage of the specification. _x000D_ OWL2 implementation:_x000D_ https://www.w3.org/2001/sw/wiki/OWL/Implementations
'SEMIC developed a service that checks the integrity and consistency against the DCAT-AP specification of one or more software description metadata files. It is available for free in Joinup, the European Commission collaborative platform for the reuse of IT Solutions. DCAT-AP validator: http://dcat-ap.semic.eu/dcat-ap_validator.html DCAT-AP in data portals: https://joinup.ec.europa.eu/solution/dcat-application-profile-data-portals-europe/about '
'As the specification comes from the IETF community, different initiatives surrounding CSV encourages the creation of communities that work on the specification and digital solutions. IETF Community about: https://www.ietf.org/how/'
ODRL is a specification that provides a core vocabulary that allows the description and representation of information in a standardised and machine-readable format fostering the data exchange and the interoperability of organisations and resources using it. An example of its potential use on the publication and exchange of open data is the inclusion within SPECIAL, an H2020 European Project that stands for "Scalable Policy-awarE Linked Data arChitecture for prIvacy, trAnsparency and compLiance". This project aims to provide solutions for data protection and its reuse using standards to allow maximum applicability and interoperability across borders. Moreover, the specification offers serialisation in common formats for open data publication and shareability such as RDF or JASON-LD. W3C specification reference: https://www.w3.org/TR/odrl-vocab/#vocab-core SPECIAL Deliverable: https://www.specialprivacy.eu/images/documents/SPECIAL_D17_M17_V10.pdf
'ODRL is designed to express and manage digital rights, permissions, and restrictions related to digital content. It includes mechanisms for specifying access controls, limitations, and conditions on how digital assets can be used. W3C specification reference: https://www.w3.org/TR/odrl-vocab/#vocab-core'
There are some projects that include XSLT "A Prototype Cross-Border GML Data Service" that has opened new opportunities for creating integrated cross-border spatial data services with Geography Mark-up Language. In addition, the INSPIRE Directive and related regulations can also be considered a cross-border EU initiative, included in the ISA programme. See: https://agile-online.org/conference_paper/cds/agile_2004/papers/4-2-3_lehto.pdf https://ies-svn.jrc.ec.europa.eu/projects/registry-development/wiki/Re3gistry_1_0_documentation#_cp3
'UBL helps to ensure interoperability when it comes to define processes for setting standards-based infrastructure for electronic Extensible Markup Language (XML) business documents exchange. This is why, among other reasons, it appears as one of the setting standards for the "Commission Implementing Decision of 3 April 2014 on the identification of ICT technical specifications eligible for referencing in public procurement" COMMISSION IMPLEMENTING DECISION of 31 October 2014 on the identification of Universal Business Language version 2.1 for referencing in public procurement: https://eur-lex.europa.eu/legal-content/ES/TXT/?qid=1657095448506&uri=CELEX:32014D0771'
Since the specification is directly related with the certification of existing data, it can help administrations with the implementation of the once-only principle. Allowing the reuse of existing data that has been certified, the specification can avoid administrations asking for same certified references in procurement, for instance. TSP IETF reference: https://tools.ietf.org/html/rfc3161
At the time of elaborating this assessment, FTP does not foster the creation of innovative solutions. Since its development in 1971, it has been used in combination with other specifications in order to enhance security (e.g. TLS & SSL). However, even these extensions of FTP are not considered innovative solutions.
'GraphQL does not mandate a particular programming language or storage system for application services that implement it. Instead, application services take their capabilities and map them to a uniform language, type system, and philosophy that GraphQL encodes. Therefore, GraphQL can be said to be independent of any technologies. GraphQL specification overview: https://spec.graphql.org/October2021/#sec-Overview'
'The degree to which the ELI specification accommodates partial implementations is contingent upon the particular requirements and characteristics under consideration. Typically, specifications such as ELI are crafted with a focus on modularity, thereby enabling those implementing it to select and rank specific elements in accordance with their individual needs and available resources. ELI reference: https://eur-lex.europa.eu/eli-register/about.html'
'There exist different initiatives across Europe adopting the EN 16234-1 e-CF specification. It is the case of the Digital Competence Framework for Citizens (DigComp) initiative, which provides a common understanding of what digital competences, knowledge, skills and attitudes are, and helps citizens to engage with digital, new and emerging technologies. Digital Competence Framework for Citizens (DigComp) reference: https://joint-research-centre.ec.europa.eu/digcomp_en?msclkid=27a7a8f2b64611eca3ebf019d32a2764'
'No document or study has been found assessing the CPOV in terms of efficiency or effectiveness. CPOV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-organisation-vocabulary'
'There exist some assessments indirectly addressing the effectiveness of OData in industry (e.g., Microsoft Open Technologies), or documentation focusing on the improvement of the OData specification (e.g., the future release, OData.Neo). OData assessments reference: https://www.odata.org/blog/ Microsoft Open Technologies (China) reference: https://www.odata.org/blog/microsoft-open-technologies-releases-odata-producer-for-sugarcrm-to-boost-the-efficiency-of-corporate-data-exchange/ OData.Neo reference: https://github.com/OData/OData.Neo'
'AMQP is involved in the European solution for data spaces and digital transformation, enabling data sharing, interoperability, and efficient data transport within the context of European initiatives. Emerging approaches for data-driven innovation in Europe Reference: https://interoperable-europe.ec.europa.eu/sites/default/files/custom-page/attachment/2022-02/jrc-tr_ddi_2021_v9_online.pdf'
By easing the digital communication SMP is an asset for the simplification and the reduction of administrative burden. The specification fosters the digital exchange of information by enhancing the discoverability of Access points easing the digitalisation of data transactions between administrations and also with other stakeholders like business or citizens. SMP OASIS reference: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505009
JPEG is a specification that supports data portability, and therefore, supporting the development of European Public Services. JEPG ISO reference: https://www.iso.org/standard/18902.html JPEG public reference: https://jpeg.org/jpeg/
'XACML is used in Privacy Preserving Perimeter Protection Project. In this project, XACML is used to implement a privacy-aware access control module. Privacy Preserving Perimeter Protection Project: https://cordis.europa.eu/project/id/312784/reporting '
'Acoording to this specification, regardless of the domain special attention has to be given to personal information. For instance, section 5.2.2.5 of the ISO mentions the regulation (EU) 2016/679 about General Data Protection Regulation. ISO 19941: https://www.iso.org/obp/ui/en/#iso:std:iso-iec:19941:ed-1:v1:en EU 2016/679: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=celex%3A32016R0679'
This standard is licensed CC-0, which essentially means that the project, along with the contributions, is in the public domain in whatever jurisdiction possible, and everyone can do whatever they want with it. The Standard for Public Code webpage: https://standard.publiccode.net/
'There are several studies assessing ShEx efficiency when it comes to modelling and validating RDF graphs. For example, there has been found an interesting study assessing the efficiency of ShEx when it comes to create subsets of knowledge graphs. Creating Knowledge Graphs Subsets using Shape Expressions: https://arxiv.org/abs/2110.11709 Using Shape Expressions (ShEx) to Share RDF Data Models and to Guide Curation with Rigorous Validation: https://link.springer.com/chapter/10.1007/978-3-030-21348-0_39'
'EuroVoc is used for the EU Open Data Portal, the site where EU Institutions publish their datasets for their reuse. In there, it is also used the classification of EuroVoc in order to improve the shareability, researchability and interoperability when processing the data. It helps to link data under knowledge domains. EuroVoc: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource /dataset/eurovoc 5-star linked open data: https://www.w3.org/DesignIssues/LinkedData.htm'
'Syslog is a powerful tool for providing visibility into administrative procedures, rules data, and services within a networked environment. For example, syslog can be configured to log various administrative actions and commands executed on network devices, servers, or other systems. Also, syslog is commonly used for logging security events and incidents and allows administrators to define rules for logging specific events or conditions. Syslog Protocol: https://datatracker.ietf.org/doc/html/rfc5424'
FTPS is an extension of FTP which allows public administration to exchange information securely, so it avoids multiple requests of standard information to citizens or businesses. FTPS IETF reference: https://tools.ietf.org/html/rfc4217
LDAP is included in 3 national catalogues of recommended specifications. They belong to the Netherlands, Spain and Sweden. The National Interoperability Framework (NIF) of these Member States is fully aligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. National catalogue the Netherlands: https://www.forumstandaardisatie.nl/open-standaarden National catalogue Spain: https://administracionelectronica.gob.es/pae_Home/pae_Estrategias/pae_Interoperabilidad_Inicio/pae_Normas_tecnicas_de_interoperabilidad.html#CATALOGOESTANDARES National catalogue Sweden: https://www.avropa.se/globalassets/dokument/open-it-standards.pdf?_t_id=1B2M2Y8AsgTpgAmY7PhCfg%3d%3d&_t_q=standards&_t_tags=language%3asv%2csiteid%3a95d515a5-23ca-47bf-87a9-07b10d8ac360&_t_ip=178.139.72.144&_t_hit.id=Avropa_Core_Models_Media_GenericMedia/_ff07d720-f793-44b0-994d-27e79b28f6bd&_t_hit.pos=7 NIFO factsheets: https://joinup.ec.europa.eu/collection/national-interoperability-framework-observatory-nifo/nifo-factsheets
The purpose of SMP is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification. SMP OASIS reference: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505009
The purpose of DCAT-AP is not related to e-accessibility. Therefore this criterion is not applicable to this specification.
'ODRL specification is designed to support extension. The extensibility feature of ODRL allows users to introduce custom elements, semantics, and vocabulary to meet specific requirements beyond the core features defined in the standard. This extension mechanism is valuable for accommodating diverse use cases and industry-specific needs. W3C specification: https://www.w3.org/TR/odrl-vocab/#vocab-core'
'The effectiveness of ISO 19941 is often evaluated through various means, including practical implementations and pilot projects. For instance, a 2017-paper mentions this specification as a reference for an FBM model of ISO Cloud Computing Architecture, which demonstrates the effectiveness of ISO 19941 as it taken into account. An FBM Model of ISO Cloud Computing Architecture: https://link.springer.com/chapter/10.1007/978-3-319-73805-5_16 ISO 19941: https://www.iso.org/obp/ui/en/#iso:std:iso-iec:19941:ed-1:v1:en'
'There are already existing studies and documents assessing and documenting YAML features and providing possible improvements of its performance among other aspects. There are two papers that can be useful to discover how YAML can be effective. In "Comparision between JSON and YAML for data serialization" it is determined and discussed the primary differences between two different serialization formats, namely YAML and JSON. In "YAML: A tool for hardware design visualization and capture", is described an approach that helps to capture the structural aspects of a design at a high level of abstraction and enables the system designer to enter designs "schematically" using predefined structural and functional entities conforming to UML notation. Therefore, the specification can achieve different objectives alone or together with other specifications. "Comparision between JSON and YAML for data serialization" https://citeseerx.ist.psu.edu/document?repid=rep1&type=pdf&doi=636a2b04d98c0af8e9d6f59148352dd63af4f0c1 "YAML: A tool for hardware design visualization and capture": https://ieeexplore.ieee.org/abstract/document/874023'
Even though the specification can be associated with solutions or projects aiming to ensure the availability of interfaces with internal information, the specification in itself does not foster its availability. OpenPM2 specification reference: https://op.europa.eu/en/publication-detail/-/publication/ac3e118a-cb6e-11e8-9424-01aa75ed71a1/language-en/format-PDF/source-83307127
As a lightweight protocol for securing data packets, IPsec allows the scalability of systems. Its use for large amounts of data does not hamper performance. For instance, the TESTA project, which provides a secure cross-border data communication network service for public administrations, uses IPSec for national and European connections. See: https://ec.europa.eu/isa2/solutions/testa_en
"CIM NGSI-LD API is maintained by the European Telecommunications Standards Institute (ETSI), a European Standards Organization (ESO) that is recognised as the regional standards body dealing with telecommunications, broadcasting and other electronic communications networks and services. Furthermore, the specification is mentioned in the Artificial intelligence section from Joinup's 2024 ICT Rolling Plan, fact that proves that it is of current relevance and has significant implications for interoperability. This naturally attracts the attention of developer communities, generating debates and discussions to explore its effective implementation, impact and possible improvements. ETSI: https://www.etsi.org/about GS CIM in ICT Rolling plan: https://joinup.ec.europa.eu/collection/rolling-plan-ict-standardisation/artificial-intelligence-rp2024"
'The purpose of WAI-ARIA is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification. WAI-ARIA reference: https://www.w3.org/TR/wai-aria/'
TLS 1.2 is developed and maintained by IETF, a widely recognised open international community developing standards to enhance the internet. See: https://www.ietf.org/ https://tools.ietf.org/html/rfc5246
'The specification was developed in 2002. Up-to-date, the X.509 Internet Public Key Infrastructure Online Certificate Status Protocol (OCSP) updates the previous X.509 Internet Public Key Infrastructure (RFC 5912), reaching version 8. OCSP reference, Abstract section: https://datatracker.ietf.org/doc/html/rfc2560 OCSP version reference: https://datatracker.ietf.org/doc/rfc6960/'
The purpose of ADMS is not related to the delivery of multilingual public services. Therefore, this criterion is not applicable to this specification. ADMS Specification W3C: https://www.w3.org/TR/vocab-adms/
XAdES is a business domain agnostic specification that can be reused in a cross-domain way. XAdES ISO reference: https://www.iso.org/standard/56025.html XAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/101900_101999/101903/01.04.02_60/ts_101903v010402p.pdf
'As for all eGovernment-related Vocabularies under the previous ISA2 Program, the SEMIC Support Center is responsible for the maintenance of the development of the specification. SEMIC in Joinup: https://joinup.ec.europa.eu/collection/semic-support-centre'
'ETSI TS 119 612 is being used in the eIDAS project, which focuses on the creation of e-signature services aiming to enable secure cross-border transactions. eIDAS is based on Regulation (EU) No 910/2014 of the European Parliament and of the Council of 23 July 2014 on electronic identification and trust services for electronic transactions in the internal market. Regulation (EU) No 910/2014 of the European Parliament and of the Council of 23 July 2014 on electronic identification and trust services for electronic transactions in the internal market: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv:OJ.L_.2014.257.01.0073.01.ENG ETSI TS 119 612 specification: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf'
'Genericode can be used in virtually any business domain. Genericode provides a standardised format for representing code lists and controlled values, making it applicable to a wide range of industries and applications. Genericode can be used to represent currency codes, country codes, medical diagnostic codes, procedure codes, area codes, government agency codes, regulatory classifications, etc. Code List Representation (genericode): https://docs.oasis-open.org/codelist/genericode/v1.0/os/genericode-v1.0-os.html'
The rules on European standardisation allow the European Commission to identify information and communication technology (ICT) technical specifications - that are not national, European or international standards - to be eligible for referencing in public procurement. This allows public authorities to make use of the full range of specifications when buying IT hardware, software and services, allowing for more competition in the field and reducing the risk of lock-in to proprietary systems. After being evaluated compliant with the regulation on standardisation 1025/2012, RDF has been identified by Commission Implementing Decision and included in the European list of ICT Standards for e-procurement. See: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en
'There has not been found any Member State recommending TGF. TGF specification: http://docs.oasis-open.org/tgf/TGF/v2.0/cs01/TGF-v2.0-cs01.html'
'While OpenTelemetry is not directly related to protecting information against unauthorised changes, data integrity is addressed as permissions are mentioned. Some components may require privileged access and care should be taken before enabling these components. In fact, the Collector components may require external permissions including network access or RBAC. Finally, component developers should minimise privileged access requirements and must document what requires privileged access and why. OTel Security Best Practices: https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/security-best-practices.md'
'ETSI TS 119 432 is developed and maintained by the European Telecommunications Standards Institute (ETSI). Its development involves contributions from industry experts and collaboration within ETSI working groups, particularly ETSI Technical Committee ESI. This standardisation body covers the format of digital signatures, as well as procedures and policies for creation and validation. ETSI takes into account the impact of users as they improve their standards and their relevancy. ETSI Technical Committee ESI: https://www.etsi.org/committee/esi'
'The specification counts with a specific section (5.1.4) that is about Language Support, so it can be determined that is designed to fully support multilingualism. ETSI TS 119 612 specification: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf '
'The purpose of Verifiable Credentials enable digital service delivery channels as a good asset for digitalisation and administrative simplification. For instance, government-issued identity documents, such as national ID cards, can be verifiable credentials, which can be easily managed and verified while the individual maintains control over their personal data. Verifiable Credentials: https://www.w3.org/TR/vc-data-model/'
'The specification is maintained by International Data Spaces Global (IDS-G) and any user can contribute by proposing discussions on the IDS-G GitHub Discussion channel. IDS-G Discussions: https://github.com/International-Data-Spaces-Association/IDS-G/discussions'
'While not a direct feature of OpenTelemetry, applications instrumented with OpenTelemetry can incorporate internationalisation (i18n) support to handle multilingual content and user interfaces effectively. OpenTelemetry can capture telemetry data related to user interactions with multilingual content, providing insights into how different language versions of an application are used. OpenTelemetry Languages: https://opentelemetry.io/docs/languages/other/'
The Core Location Vocabulary defines a core data model that allows the description of locations, geographical elements in a common way. This fact ensures a trustworthy reuse and data exchange among administrations and stakeholders. CLV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-location-vocabulary
'TGF has not been found included in any initiative covering privacy aspects. TGF specification: http://docs.oasis-open.org/tgf/TGF/v2.0/cs01/TGF-v2.0-cs01.html'
'HTTP Cookies provides a way of addressing the secure exchange of data by adding the "httpOnly" attribute to prevent access to Cookies via JavaScript, or by setting the "SameSite" attribute to "strict" when it is necessary to authenticate sensitive information from the user. In browsers that support SameSite, this ensures that the authentication cookie isn't sent with cross-site requests. HTTP Cookies security reference: https://datatracker.ietf.org/doc/html/rfc6265#section-8'
'The specification is not related to the publication of public data as open data. Therefore this criterion is not applicable to this specification. IPv4 IETF: https://www.rfc-editor.org/rfc/rfc791'
"The purpose of the specification is not directly related to the visibility of public administrations' procedures, rules, data or services. Publiccode.yml focuses on the reuse of software developed by public bodies, ensuring the efficiency and effectiveness of the budget dedicated to address specific needs. So, administrations can benefit from other administrations services with the implementation of the specification, including the use of the same web services or other related reusable software. However, it is not directly impacting the visibility of internal interfaces. Publiccode.yaml documentation: https://docs.italia.it/italia/developers-italia/publiccodeyml-en/en/master/index.html"
'Contracting authorities can add additional questions or modify existing ones in the ESPD model to ensure that they collect the information they need to make informed decisions and evaluate supplier responses effectively, as well as aggregate business requirements if needed, thus allowing for extensions. ESPD Business handbook: https://docs.ted.europa.eu/ESPD-EDM/latest/xml_business_handbook.html'
'OCSP specifies the data to be exchanged between an application that checks the status of one or more certificates and the server that provides the corresponding status. However, no evidence was found supporting the evolution of European public services. OCSP reference, section 2: https://datatracker.ietf.org/doc/html/rfc2560'
There are no Member States recommending Core Criterion and Core Evidence Vocabulary in their ICT National Catalogues. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'XML can enable digital service delivery channels. By using XML to structure and share data, organizations can make it easier for customers to access their services through digital channels like websites, mobile apps, and APIs. See: https://www.w3.org/TR/2006/REC-xml11-20060816/'
"ISO/IEC 7498:1 is part of Joinup's catalogue of ICT Standards for Procurement. Joinup is the European Commission's one-stop shop for interoperable, open and free digital government ICT solutions, and an online space for e-Government professionals and enthusiasts to share and learn about digital public services and initiatives. Its market acceptance can further be evidenced by its integration in healthcare standards such as HL7 and FHIR. Joinup ISO/IEC 7498:1: https://joinup.ec.europa.eu/collection/ict-standards-procurement/solution/isoiec-7498-11994-information-technology-open-systems-interconnection-basic-reference-model-basic ISO/IEC 7498 in HL7 standard: https://www.disrupciontecnologica.com/hl7/"
'OCSP is a protocol useful in determining the current status of a digital certificate without requiring Certificate Revocation Lists (CRLs). The purpose of OCSP is not related to the visibility of administrative procedures, rules data, and services. OCSP reference, Abstract section and Appendix A: https://datatracker.ietf.org/doc/html/rfc2560'
"In accordance with Common Patent Policy for ITU-T/ITU-R/ISO/IEC the ISO 639-2 is licensed under (F)RAND basis. Although there are terms included that allow patent holder to apply specific costs. It is defined in IPR disclosures that can be found at ISO's webpage. ISO patents: https://www.iso.org/iso-standards-and-patents.html ISO standards and patents IPR database: http://isotc.iso.org/livelink/livelink/13622347/Patents_database.xls?func=doc.Fetch&nodeId=13622347"
'Registered Organization Vocabulary does not guarantee the authenticity and authentication of the roles agents involved in the data transactions. The main purpose of the specification is to define a standardised way of describing organisations that have gained legal entity status through a formal registration process. Therefore, this criterion is considered not applicable to this specification. Registered Organization Vocabulary reference: https://www.w3.org/TR/vocab-regorg/'
'The Asset Administration Shell (AAS) has specific provisions regarding authentication of the stakeholders, in this sense the usage of other specifications to meet this parameter is recommended, on the section 7.3 the usage of XACML is mentioned as an integral part of the specification. XACML recomedation in AAS specification: https://admin-shell-io.github.io/aas-specs-antora/IDTA-01004/v3.0/introduction.html#_attribute_based_access_control_abac Details of the Asset Administration Shell (AAS) https://industrialdigitaltwin.org/en/wp-content/uploads/sites/2/2024/06/IDTA-01001-3-0-1_SpecificationAssetAdministrationShell_Part1_Metamodel.pdf'
'The purpose of EuroVoc is not related to security and privacy of the data exchange. Therefore, this criterion is not applicable to this specification. EuroVoc: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource /dataset/eurovoc'
'Genericode can be used effectively in a multilingual context due to its flexibility in representing code lists and controlled values. The "Language" tag support allows for the inclusion of metadata alongside code values, which can include language tags to specify the language of the metadata. This means that descriptions, labels, or other textual information associated with code values can be provided in multiple languages within the same genericode file. Code List Representation (genericode): https://docs.oasis-open.org/codelist/genericode/v1.0/os/genericode-v1.0-os.html'
'Being a standard protocol for mantaining and accessing directory services, LDAP can be used across business domains as long as they require the storage and management of user information. LDAP IETF reference: https://tools.ietf.org/html/rfc4511'
The information shared by an IPV6 packet, the smallest message entity exchanged via the Internet Protocol, contains information structured in cross-border reusable data model.
Not enough information has been found to consider this criterion positive or negative.
'OCSP allows applications to determine the revocation status of identified certificates. In this sense, the specification addresses data protection but does not make any reference to relevant regulations at a European level. OCSP reference, section 2: https://datatracker.ietf.org/doc/html/rfc2560'
'TS 119 614-1 is a set of conformance testing practices for electronic signatures and preservation and is intended to support the development and manufacture of different solutions at EU level. The specification is intentionally not linked to any software development technology and is also intentionally agnostic on implementation strategies. This is one of the reasons why the test assertions set includes tests on the correctness of the structure of all elements specified by the XML Schemas associated with ETSI TS 119 612. ETSI TS 119 614-1 reference: https://www.etsi.org/deliver/etsi_ts/119600_119699/11961401/01.01.01_60/ts_11961401v010101p.pdf'
Not enough information has been found to answer negatively or positively to this criterion. Moreover, it seems that the specification is not aimed to foster e-accessibility to legislation. Therefore, this criterion is considered not applicable to this specification. ELI reference: https://eur-lex.europa.eu/eli-register/about.html
"ETSI TS 119 612 does not allow any kind of customisation as it has to be implemented how it is described in the specification's document. ETSI TS 119 612 specification: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf"
'The EUROSTAT (European Commission) is in charge of maintaining and publishing each of the three NUTS levels. The specification is upgraded by national, regional and local administrations and representatives of the Member States in collaboration with the European Commission. However, contributions are not always available (see EUROSTAT-NUTS lattest amendments reference, History of NUTS section, NUTS 2021 XLS document). European Parliament reference: https://www.europarl.europa.eu/factsheets/en/sheet/99/la-nomenclatura-comun-de-unidades-territoriales-estadisticas-nuts- EUROSTAT-NUTS lattest amendments reference, History of NUTS section, NUTS 2021 XLS document: https://ec.europa.eu/eurostat/web/nuts/history'
'The IPsec specification promotes a common framework for security in communication between organisations. This can help facilitate agreements between organisations to define a unique method for securing communications. Thus, IPsec can help to protect data using a common framework. IPSec reference: https://www.rfc-editor.org/rfc/rfc6071.html'
"CPOV standardizes information on public organizations facilitates interoperability between systems, and allows government entities to share and reuse data efficiently by reducing duplicates and improving information accuracy. By facilitating access to consistent data, CPOV improves citizens and businesses' ability to interact with public services, and therefore, simplifies the delivery of them. CPOV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-organisation-vocabulary"
There are many free online tools that uses OWLAPI code to validate whether an ontology is conformant with the different OWL profiles. One working example:_x000D_ _x000D_ OWL Validator:_x000D_ http://www.cosasbuenas.es/blog/owl-validator OWL 2 Validator: http://visualdataweb.de/validator/
'The XACML specification provides robust capabilities for customization, allowing organisations to define, implement, and manage custom access control policies tailored to their specific requirements. Moreover, there are XACML customisations available on the market. XACML OASIS reference: https://docs.oasis-open.org/xacml/3.0/xacml-3.0-core-spec-os-en.html XACML OASIS Hierarchical Resource reference: https://www.oasis-open.org/standard/xacml3-0-hier/'
The specification was developed by 2011 and has been broadly implemented and used for the representation of graphical information containing vectors and mixed vector/raster. Also, it is interesting to mention that it has been evolving along with other specifications to ensure the interoperability between some of them. SVG W3C reference: https://www.w3.org/TR/SVG11/
'Even though the specification is related to the use and publication of metadata, it is not directly related to the publication of open data. The relation with metadata and its publication is focused on the availability and discoverability of access points and different parties for the exchange of data. SMP OASIS reference: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505009 Five star linked open data: https://www.w3.org/DesignIssues/LinkedData.html'
FTPS is a business domain agnostic specification that can be reused in a cross-domain way. FTPS IETF reference: https://tools.ietf.org/html/rfc4217
'The Better Regulation Guidelines and Toolbox encompasses a set of requirements, recommendations and principles that need to be taken into account when planning, developing and also when implementing public policies. Within the different tools described in the Better Regulation Toolbox some aspects that take into account interface issues (regarding end-user interfaces but also institutions access to interfaces) are present. Better Regulation Guidelines and Toolbox reference: https://commission.europa.eu/law/law-making-process/better-regulation/better-regulation-guidelines-and-toolbox_en Better Regulation Guidelines reference: https://commission.europa.eu/document/download/d0bbd77f-bee5-4ee5-b5c4-6110c7605476_en?filename=swd2021_305_en.pdf Better Regulation Toolbox reference: https://commission.europa.eu/document/download/9c8d2189-8abd-4f29-84e9-abc843cc68e0_en?filename=BR%20toolbox%20-%20Jul%202023%20-%20FINAL.pdff'
'The XSLT specification is mature for developing digital solutions and services, with comprehensive features and detailed documentation. W3C has a clear and structured methodology to publicly share documentation, and specifically the change management and release management. Test suite for XSLT: https://dvcs.w3.org/hg/xslt30-test/ XSLT Reference: https://www.w3.org/TR/xslt-30'
RDF is publicly available for implementation and study for free on W3C's webpage. See: https://www.w3.org/TR/rdf11-primer
'OCSP specifies the data to be exchanged between an application that checks the status of one or more certificates and the server that provides the corresponding status. However, no evidence was found supporting its implementation in any European public services. OCSP reference, section 2: https://datatracker.ietf.org/doc/html/rfc2560'
'The IPsec specification can use XAuth (Extended Authentication) to guarantee user access. XAuth increases security by requiring remote dial-up clients to authenticate. In addition, XAuth utilises established authentication mechanisms, such as LDAP, to authenticate dial-up clients. Therefore, the specification can enhance access control mechanisms to improve security aspects. IPSec reference: https://www.rfc-editor.org/rfc/rfc6071.html XAuth authentication mechanism: https://docs.fortinet.com/document/fortigate/7.4.0/administration-guide/277729/using-xauth-authentication'
'DCAT-AP primarily focuses on enabling the discovery and access of datasets and data catalogs, rather than exposing interfaces to access public administration services directly. However, DCAT-AP can indirectly facilitates the exposure of interfaces by providing a standardized way to describe the datasets and data services that are available on a data portal. DCAT-AP includes metadata elements for describing data services, such as web services, APIs, and SPARQL endpoints, that can provide information on the technical characteristics of the service, and by using standard vocabularies and identifiers, it can provide additional information about the datasets and services that can help users to select and filter the most relevant services for their needs. DCAT-AP Specification: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/dcat-application-profile-data-portals-europe/release/200'
There is no assessment regarding the compliance of the specification with European Standardisation Regulation 1025/2012. Despite CEF is a European Commission action, there is no evidence to answer positively to this criterion.
'The IPsec specification does not fully address all use cases of the IPsec architecture. The user may refer to other documentation that addresses additional details of the architecture in specific environments where **** 15comprehensibility considerations may be an asset. IPSec reference: https://tools.ietf.org/html/rfc4301 '
'The ebXML specification is included in 1 Member State catalogue of recommended specifications. It Member State is Norway. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards ebXML RegRep OASIS reference: https://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html'
The Core Public Organisation Vocabulary facilitates the information sharing between governments, business and citizens. So, it reduces the administrative burden by facilitating the use of digital data. CPOV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-organisation-vocabulary
'DNS is recommended by 9 Member States, including France, Germany, Spain, Sweden, Malta, Cyprus, Greece, Croatia and the Netherlands. CAMSS list of standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specificationscamss /camss-list-standards'
'NFVI is intended to be used in virtualised ecosystems. Because the NFVI is a distribution set of NFVI-nodes in multiple locations that supports the locality and latency requirements of NFV use cases, the specification can be used in any domain and is domain-agnostic. NFVI Deliver, Infrastructure Overview: https://www.etsi.org/deliver/etsi_gs/NFV-INF/001_099/001/01.01.01_60/'
The purpose of the specifications is not related to the availability of interfaces with internal information systems. Therefore, this criterion is not applicable to this specification. In the case that there would be an interface with HTML, this specification could help to ensure the availability of interfaces giving the correct format. CSS v2.1 W3C reference: https://www.w3.org/TR/2011/REC-CSS2-20110607/
Taking the initial purpose of the specification, it can be considered that the specification is involved in fostering the comprehensibility of Public Administrations data as well as relevant data produced for the decision-making process. ELI provides a common schema for the definition of legislation metadata, easing the understanding and the shareability of legislation documents and their access. ELI reference: https://eur-lex.europa.eu/eli-register/about.html
'The EN 16234-1 e-CF framework is not dependent on any other specification, operating system or web platform; therefore, the specification is platform-agnostic. CEN reference, CEN/TC 428 - ICT Professionalism and Digital Competences (Published standards), EN 16234-1 e-CF: https://standards.cencenelec.eu/dyn/www/f?p=205:110:0::::FSP_PROJECT:67073&cs=15E62ED24D608A5F10D6BEE8E6D50FA10'
'OAS gives itself a criterion and guidelines and structure to develop APIs and also constitutes an environment for testing the conformity of the application to the OAS parameters. To this end, OAS conformance testing functionalities range from data and description validation (to check for the correct syntax and data flow) to mock servers (to provide example responses before writing code). Advatages of using OpenAPI: https://oai.github.io/Documentation/start-here.html#advantages-of-using-openapi OAS specification: https://spec.openapis.org/oas/latest.html#openapi-specification OAS in Github: https://github.com/OAI/OpenAPI-Specification/#participation'
The specification is independent of any software or platform. The Registered Organization Vocabulary can be used by any organisation. RegOrg Joinup reference: https://joinup.ec.europa.eu/solution/registered-organization-vocabulary
After being evaluated compliant with the regulation on standardisation 1025/2012, UTF-8 has been identified by Commission Implementing Decision and included in the European list of ICT Standards for e-procurement. See: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en
Using Xforms 2.0 contributes to the increase in digital public services. By allowing public administrations to develop online forms, it reduces the administrative burden. Xforms 2.0 W3C reference: https://www.w3.org/community/xformsusers/wiki/XForms_2.0
'ETSI TS 119 432 is not related to enabling e-accessibility. Therefore, this criterion is considered not applicable to this specification. ETSI TS 119 432: https://www.etsi.org/deliver/etsi_ts/119400_119499/119432/01.02.01_60/ts_119432v010201p.pdf'
'The SAML 2.0 specification is recognized and integrated in several initiatives at both European and national levels, especially those concerning identity management, privacy, and electronic transactions such as eIDAS. eIDAS Reference: https://digital-strategy.ec.europa.eu/es/policies/eidas-regulation SAML 2.0 Reference: http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-tech-overview-2.0.html'
'EuroVoc is not included in any national catalogue of recommended specifications whose Member State NIF has a high performance on interoperability according to NIFO factsheets. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards'
'LDAP appears in the Commission Implementing Decision "on the identification of ICT technical specifications eligible for referencing inpublic procurement". In this document, LDAP is said to be a stable technology that has the potential to increase interoperability and constitutes a de-facto standard for authentication, For that matter, the LDAP standard can facilitate organisational interoperability agreements. Commission Implementing Decision of 3 April 2014 on the identification of ICT technical specifications eligible for referencing in public procurement: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32014D0188'
'Core Public Organisation Vocabulary facilitates the information sharing. It enables G2G (Government-to-Government), G2B (Government-to-Business) and G2C (Government-to-Citizen) information sharing. Moreover, CPOV can be complemented with other security specifications which guarantee the secure interactions between users. CPOV Joinup reference: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/core-public-organisation-vocabulary/distribution/core-public-organisation-vocabulary-version-100-pdf'
JSON strongly supports Tim Berners Lee's 5-star schema for open data. The adoption of JSON fosters the publication of data as open data by means of providing structured data and the usage of non-proprietary formats. Moreover, it helps to link data by means of embedding metadata. See: https://www.europeandataportal.eu/sites/default/files/european_data_portal_-_open_data_goldbook.pdf https://5stardata.info/en/
The Standard for Public Code is a set of criteria that supports public organizations in developing and maintaining software and policy together. Therefore, the specification fosters the reduction of the administrative burden by enabling digital public services, reducing the extra cost of non-digital communications. Moreover, the specification aims to increase the efficiency and effectiveness of development processes for the creation of reusable solutions, which also contribute to the reduction of administrative burden. The Standard for Public Code webpage: https://standard.publiccode.net/
The specification is an element with high relevance in the data and information exchange. UTF-8 as a specification to encoding data ensures that files, web applications and systems can be read by both parts implied in the communication ensuring the reliability of transferred data. Therefore, UTF-8 eases the trustworthy data exchange between administration and stakeholders.
'Through the caching architectural principle, REST has the ability to store copies of frequently accessed data in several places along the requeest-response path. The Cache Control Headers can indicate when a representation never expires, meaning that the data of the representation is well preserved. REST Caching resference: https://restfulapi.net/caching/'
PDF/A is a business agnostic document format that can be reused in a cross-domain way.
'OData is tied up to RESTful APIs communication. Although the OData service declares its own data model in a machine-readable form, which allows customers to interact with the service on a generic basis, OData relies on RESTful APIs in order to be implemented. OData reference, 4 Service Model: http://docs.oasis-open.org/odata/odata/v4.0/errata03/os/complete/part1-protocol/odata-v4.0-errata03-os-part1-protocol-complete.html#_Toc453752204'
'While the JSON specification itself does not directly address data processing accuracy, developers can implement best practices, rigorous testing, and quality assurance measures to ensure accurate data processing when working with JSON. JSON specification: https://www.ecma-international.org/wp-content/uploads/ECMA-404_2nd_edition_december_2017.pdf'
'The purpose of OData is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification. OData reference: https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html'
'DCAT-AP is part of the Danish catalogue of recommended specifications. Danish catalogue of specifications: https://arkitektur.digst.dk/specifikationer/datasaet'
"No evidence has been found that HTTP Cookies is recommended by any European Member State's Catalogue. HTTP Cookies reference: https://datatracker.ietf.org/doc/html/rfc6265#section-1"
The purpose of WS-BPEL is not related to the once-only principle. Therefore, this criterion is not applicable to the specification. The specification: http://docs.oasis-open.org/wsbpel/2.0/OS/wsbpel-v2.0-OS.html
8 Member States are recommending MIME in their ICT National Catalogues. The Member states are Croatia, France, Germany, Greece, Malta, the Netherlands, Spain and Sweden. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
IPv6 allows data exchange between systems and it is compatible with the previous version IPv4. Furthermore, he European Union fosters del IPv6 to ensure "The goals of the Digital Agenda for Europe and the Digital Single Market Strategy are based on stable and reliable data networks." See: https://ec.europa.eu/isa2/sites/isa/files/ipv6_framework_for_european_governments_0.pdf
XAdES is maintained by ETSI, one of the European Agencies for Standardisation. See: https://www.etsi.org/about
'After checking the different standard catalogues at supra-national level, there is no evidence of the inclusion of ISO 639-2 within any European catalogue of standards. ICT technical specifications: https://ec.europa.eu/growth/single-market/european-standards/ict-standardisation/ict-technical-specifications_en CENELEC and CEN search tool catalogue: https://standards.cencenelec.eu/dyn/www/f?p=CEN:105::RESET::::'
'The purpose of the specification is not related to the facilitation of organisational interoperability agreements, therefore this criterion is not applicable to this specification. ETSI EN 319 422 reference: https://www.etsi.org/deliver/etsi_en/319400_319499/319422/01.01.01_60/en_319422v010101p.pdf'
After checking the different standard catalogues at supra-national level, there is no evidence of the inclusion of SVG within any European catalogue of standards. ICT technical specifications: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en CEN search tool catalogue: https://standards.cen.eu/dyn/www/f?p=CENWEB:105::RESET:::: CENELEC search tool catalogue: https://www.cenelec.eu/dyn/www/f?p=104:107:0::::FSP_LANG_ID:25
The purpose of TLS 1.2 is not related to organisational interoperability. Therefore, this criterion is not applicable to the specification.
'While the PROV family of documents does not specifically facilitate organizational interoperability agreements, its adoption and use can indirectly support such agreements by providing a common data model, semantic interoperability, standardized formats, and a framework for defining relationships and dependencies. PROV Primer document: https://www.w3.org/TR/prov-primer/ PROV Ontology: https://www.w3.org/TR/2013/REC-prov-o-20130430/ PROV Data Model: https://www.w3.org/TR/2013/REC-prov-dm-20130430/'
The purpose of SHACL is not related in any way to the long-term preservation of electronic records and other kinds of information. Therefore, this criterion is not applicable.
'The purpose of the specification is not related to enabling the visibility of administrative procedures, rules data and services, therefore it does not promote or hinder it. ETSI EN 319 422 reference: https://www.etsi.org/deliver/etsi_en/319400_319499/319422/01.01.01_60/en_319422v010101p.pdf'
'The primary purpose of HTTPS (HTTP Secure) is to establish a secure and encrypted connection between a client (such as a web browser) and a server. This secure connection ensures that data exchanged between the client and server remains protected and cannot be intercepted or tampered with by unauthorized parties. HTTPS specification: https://tools.ietf.org/html/rfc2818'
The specification eases the access to information via webpages. Therefore, it reduces administrative burden for citizens, businesses and public administrations.
'The European Commission is the main organiser of communities focused on data sharing and results. In this sense the maintainer is the one encouraging via the specification to create these communities. Better Regulation Guidelines and Toolbox reference: https://commission.europa.eu/law/law-making-process/better-regulation/better-regulation-guidelines-and-toolbox_en Better Regulation Toolbox reference: https://commission.europa.eu/document/download/9c8d2189-8abd-4f29-84e9-abc843cc68e0_en?filename=BR%20toolbox%20-%20Jul%202023%20-%20FINAL.pdf'
'The purpose of OSI is not related to data protection as such, but the specification addresses the protection of data against unauthorised changes during the transfer of data between systems, in particular on the Application Layer, where on the Connection-mode facilities data integrity can be protected via agreements on security aspects. OSI reference https://www.iso.org/standard/20269.html'
'Currently OData is used in the context of Datalab (formerly known as Open Government Data Initiative), a cloud-based Open Data Catalogue for organisations that provide access to government data, including browse, visualise, analyse & download in multiple formats. It is also used in the context of agricultural data by the agricultural ministry of Rumania, the Date Deschise AFIR project. Date Deschise AFIR project reference https://opendata.afir.info/Home/About Datalab reference: https://github.com/openlab/OGDI-DataLab OData Ecosystem: https://www.odata.org/ecosystem/ '
The purpose of PNG is not related to e-accessibility. Therefore, this criterion is considered not applicable to this specification. PNG W3C reference: https://www.w3.org/TR/PNG/ PNG ISO reference: https://www.iso.org/standard/29581.html
'DNS over HTTPS (DoH) can contribute to data portability between systems and applications as it secures DNS (Domain Name System) queries by encrypting the communication between the client and the DNS resolver, which is crucial in security and privacy matters. It allows secure access to data, avoids censorship filters, and improves overall privacy allowing for a secure environment for data portability. DoH specification: https://datatracker.ietf.org/doc/html/rfc8484'
The CPOV eases the description and publication of datasets including information of different public organisations, their services and responsibilities. These descriptions are done using human and redeable formats which ease the reusability and the information exchange across-borders. CPOV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-organisation-vocabulary
HTTP is a transfer protocol which has been developed to exchange the information through computer networks. It is supporting the first level of maturity defined by Tim Berners Lee-s 5 star schema for Open data, "Make your data available" See https://5stardata.info/en
'The Technical Committee (TC) CYBER (Cybersecurity) provides feature requests to open source projects and results of implementation experience to open source communities. ETSI, as an acknowledged European standardisation, offers different channels for the creation of communities and the sharing of data and results in European platforms. TC CYBER reference: https://www.etsi.org/cyber-security/tc-cyber-roadmap'
The specification can be used on any operating system and hardware platform.
The SHACL has been assessed through the CAMSS Method which is in full compliance with Annex II criteria set out in the Regulation 1025/2012, hereafter 'the standardisation regulation'.
'The specification provides a set of viewpoints that are related to different aspects such as security, privacy or governance. Also, it provides a few more that can be considered in a nutshell, the core components that digital public services need, and also the key building blocks to achieve interoperability. These views are High-level viewpoint and the Key Interoperability Enablers. These viewpoints and its components are elements considered when validating using the Interoperability Architecture Solutions Validator. If some of these basic elements are not including, the validator would report some errors and warnings. Nonetheless, this is what confirms the partial implementation of EIRA when defining solutions. EIRA reference: https://interoperable-europe.ec.europa.eu/collection/european-interoperability-reference-architecture-eira /solution/eira/release/610 EIRA Github Repository: https://github.com/CarTool-EC/EIRA '
'Genericode is included in the electronic Common Technical Document (eCTD) 4.0 Implementation package. eCTD is the standard norm for industry submissions maintained by the International Council for Harmonisation of Technical Requirements for Pharmaceuticals for Human Use (ICH). The package contains the updated eCTD v4.0 EU M1 Implementation Guide and the as well updated controlled vocabulary lists in machine-readable genericode format. ICH eCTD v4.0: https://www.ich.org/page/ich-electronic-common-technical-document-ectd-v40'
'There are no Member States recommending OpenTelemetry in their ICT National Catalogues. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards '
'While the main purpose of IPsec is not to simplify the delivery of public services, it can play a significant role. Public administrations often share sensitive data, and IPsec can protect this information. In this sense, IPsec can make communication between public administrations more efficient by establishing a unified security architecture. Thus, it is not necessary to establish a specific security layer for each individual communication. IPSec reference: https://www.rfc-editor.org/rfc/rfc6071.html'
The implementation of ELI helps to make legislation available for different stakeholders from governments. On one hand it supports the interoperability between European Public Administrations fostering data exchange and enhancing the visibility of administrations data. On the other hand, it also helps to make legislations available, fostering that citizens and business follow the work done by public administrations. ELI reference: https://eur-lex.europa.eu/eli-register/about.html
'First of all ISAE 3402 provides a guarantee in the context of the security and confidentiality of information for users and companies. Therefore, when a public administration contracts a service from a private company, it can request the ISAE 3402 to ensure that their data complies with adequate confidentiality and security. ISAE 3402 handbook reference: https://www.ifac.org/system/files/downloads/b014-2010-iaasb-handbook-isae-3402.pdf'
'To support unauthorised access and modification of information, LDAP foresees a set of additional layers of security that require authentication mechanisms such as SASL and TLS. It is vital that these security functions be interoperable among all LDAP clients and servers on the Internet; therefore there has to be minimum subset of security functions that is common to all implementations that claim LDAP conformance. LDAP Authentication methods and security mechanisms: https://www.rfc-editor.org/rfc/rfc4513.txt'
PAdES (ISO 14533-3:2017) is an ISO standard and as all ISO standards, they have to be paid to access its content. However, it can be checked out in ETSI website where the content is aligned with the ISO standard. PAdES ISO reference: https://www.iso.org/standard/67937.html
'The objective of ETSI TS 119 612 is not to enable the long-term preservation of data/information, moreover it is described in the documentation that the hyperlinks described cannot be guaranteed to have long term validity. ETSI TS 119 612 specification: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf'
After carrying out information retrieval, no document or study has been found assessing the CLV in terms of efficiency or effectiveness. However, there is an ISA2 documentation where there are defined use cases and benefits of using its solutions, including the different Core Vocabularies. Use cases and benefits of ISA² specifications: https://ec.europa.eu/isa2/sites/isa/files/docs/publications/isa2_study_use_cases_and_benefits_of_isa2_specifications_january_2019.pdf
"In accordance with Common Patent Policy for ITU-T/ITU-R/ISO/IEC the ISO 3166-1 is licensed under (F)RAND basis. Although there are terms included that allow patent holder to apply specific costs. It is defined in IPR disclosures that can be found at ISO's webpage. ISO patents: https://www.iso.org/iso-standards-and-patents.html ISO standards and patents IPR database: http://isotc.iso.org/livelink/livelink/13622347/Patents_database.xls?func=doc.Fetch&nodeId=13622347 "
'Registered Organization Vocabulary does not provide an access control mechanism. The main purpose of the specification is to define a standardised way of describing organisations that have gained legal entity status through a formal registration process. Therefore, this criterion is considered not applicable to this specification. Registered Organization Vocabulary reference: https://www.w3.org/TR/vocab-regorg/'
'There is no evidence that the specification has been included in an open repository/catalogue of standards at national level. OGC TrainingDML-AI: https://www.ogc.org/standard/trainingdml-ai/'
'The purpose of EN 16234-1 e-CF is not related to the protection of personal data in Public Administrations. Therefore, this criterion is not applicable to this specification. CEN reference, CEN/TC 428 - ICT Professionalism and Digital Competences (Published standards), EN 16234-1 e-CF: https://standards.cencenelec.eu/dyn/www/f?p=205:110:0::::FSP_PROJECT:67073&cs=15E62ED24D608A5F10D6BEE8E6D50FA10'
'The efficiency of SCIM is often assessed based on several factors that relate to its performance, scalability, and practical implementation. For instance, a 2023 paper by the Institute of Electrical and Electronics Engineering (IEEE) talks about how efficiency is heavily reliant on shared resources in a modern cloud computing culture and how SCIM can be a solution for the challenges presented in access management in centralized and decentralized identity governance. A Survey on IdAM for Cross-Domain Dynamic Users: https://ieeexplore.ieee.org/abstract/document/10132479'
After being evaluated compliant with the regulation on standardisation 1025/2012, DNS has been identified by Commission Implementing Decision. During the evaluation process, all the Member States are invited to share their doubts. The positive evaluation of DNS and its identification is considered an interoperability agreement. See: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en See: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en
'DAPS has not been found included in any initiative neither at European nor on national level covering privacy aspects. DAPS: https://github.com/International-Data-Spaces-Association/IDS-G/tree/main/Components/IdentityProvider/DAPS'
The purpose of PAdES is not related to the publication of public data as linked open data. Therefore, this criterion is not applicable to this specification. PAdES ISO reference: https://www.iso.org/standard/67937.html PAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/102700_102799/10277801/01.01.01_60/ts_10277801v010101p.pdf
ELI is not included in any national catalogue of recommended specifications whose Member State NIF is fully aligned with at least 4 out of 5 sections of the EIF according to NIFO factsheets. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
The specification has been implemented several times and in different environments, open source and commercial. Some examples of XACML implementations are Balana, AuthForce, or Security Policy Pool. Balana Github: https://github.com/wso2/balana AuthForce: https://authzforce.ow2.org/ Security Pool: https://securitypolicytool.com/ XACML OASIS reference: http://docs.oasis-open.org/xacml/3.0/errata01/xacml-3.0-core-spec-errata01.html
'The purpose of the specification is not related to supporting the implementation of European public services, therefore it does not promote or hinder it. ETSI TS 119 614-1 reference: https://www.etsi.org/deliver/etsi_ts/119600_119699/11961401/01.01.01_60/ts_11961401v010101p.pdf'
'As it was previously recorded in the Fog and Edge Computing from ENISA report, the XML specification addresses data security and trustworthy data processing. ‘Fog and Edge Computing in 5G’ ENISA report: https://www.enisa.europa.eu/publications/fog-and-edge-computing-in-5g XML Reference: https://www.w3.org/TR/xml/ '
After checking the different standard catalogues at supra-national level, the Publication Office of the European Union has listed it within EurVocabularies with all the specifications and resources produced and used by European Institutions. EU Vocabularies: https://op.europa.eu/en/web/eu-vocabularies Joinup post linked to the EuroVoc reosurces: https://joinup.ec.europa.eu/collection/eu-semantic-interoperability-catalogue/news/eurovoc-freely-available
DNS is maintained by IETF which is an international community developing open standards. See: https://www.ietf.org/about/
'The Extensible Forms Description Language (XFDL) specification allows for customisation. In this context, XFDL enables the definition of the characteristics of an item, which is a single object on a page of a form. For example, one such item is the "button", which can perform a variety of tasks when pressed by the user, such as saving, printing, canceling, and more. Extensible Forms Description Language reference: https://www.w3.org/TR/NOTE-XFDL'
The purpose of CSV is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification.
'The purpose of RDF is not related to data authentication. Therefore, this criterion is not applicable to the specification. RDF primer document: https://www.w3.org/TR/rdf11-primer/'
'The effectiveness of the syslog protocol is typically assessed based on its adoption, implementation, and how well it meets message logging needs of organizations. For instance, a 2013-paper published for the International Journal of Advanced Research in Computer Science talks about syslog as a promising solution to Log Management. The solution proposed here greatly simplifies the process of log storage and analysis by centralizing the logging process from all the devices present in the network and also provide a secured storage for the log data. Syslog a Promising Solution to Log Management: https://www.researchgate.net/profile/Prasanta-Sahoo-3 /publication/332780312_Syslog_a_Promising_Solution_to_Log_Management/links /5cc9415c4585156cd7bdf3c0/Syslog-a-Promising-Solution-to-Log-Management.pdf'
3 Member States are recommending OWL2 in their ICT National Catalogues. This Member States are France, the Netherlands and Spain. National catalogue France: http://references.modernisation.gouv.fr/sites/default/files/Referentiel_General_Interoperabilite_V2.pdf National catalogue the Netherlands: https://www.forumstandaardisatie.nl/open-standaarden National catalogue Spain: https://administracionelectronica.gob.es/pae_Home/pae_Estrategias/pae_Interoperabilidad_Inicio/pae_Normas_tecnicas_de_interoperabilidad.html#CATALOGOESTANDARES
'AMQP specification offers various ways to customise messages and connections. These mechanisms enable implementers and users to customise AMQP to suit their specific needs and environments, promoting flexibility and interoperability. For example, custom data types, filtering messages, and negotiation features are the most common customisable options. (Refer to sections 1.1.2 Described Types, 2.2 Version Negotiation and 3.5.1 Filtering Messages) OASIS AMQP Reference: http://docs.oasis-open.org/amqp/core/v1.0/amqp-core-complete-v1.0.pdf'
The Better Regulation Toolbox in itself is a common method for planning, developing, assessing and monitoring the implementation of policies and laws. It is used by de different EU institutions involved in these tasks, moreover, it can be transposed to national level to ensure that national laws and policies are developed with the maximum accuracy. Better Regulation Toolbox on European Comission webpage: https://ec.europa.eu/info/law/law-making-process/planning-and-proposing-law/better-regulation-why-and-how/better-regulation-guidelines-and-toolbox/better-regulation-toolbox_en Law-making process: https://ec.europa.eu/info/law/law-making-process_en
UTF-8 is publicly available for implementation and use for free on IETF's webpage. See: https://tools.ietf.org/html/rfc3629
There is no Member State that includes Data on the Web Best Practices W3C in their national catalogue with The National Interoperability Framework (NIF) aligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'The purpose of this Core Vocabulary is to support the exchange of information between organisations that define criteria and organisations that respond to these criteria by means of evidences. Core Criterion and Core Evidence Vocabulary reference (v1.0.0): https://joinup.ec.europa.eu/release/core-criterion-and-core-evidence-vocabulary-v100 '
SMTP is widely used and implemented in the context of email services, therefore, this fact demonstrates the market acceptance of the specification. Moreover, there are several implementations of the specifications that support the market acceptance of SMTP. SMTP Transactional Email Solutions 2020: https://formedbythemosthigh.com/2020/01/27/email-verification-25/
The purpose of the Core Location Vocabulary is to create a reusable and extensible data model that captures the fundamental characteristics related to people, locations and businesses. By providing a set of information to describe data in the sectors mentioned before, it helps public administrations to save and comprehend in an orderly and standardized way, information related to people, locations or business. CLV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-location-vocabulary
'There has not been found any platform to test conformance to ETSI TS 119 512, nonetheless, the specification lists a set of requirements needed to comply with in order to be conformant can be checked manually wether or not applied. ETSI TS 119 512 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.02_60/ts_119512v010102p.pdf'
Like all the IETF standards, TLS 1.2 is a free and open technical specification, built on IETF standards and licenses from the Open Web Foundation. TLS 1.2 is therefore licensed on a royalty-free basis. See: https://tools.ietf.org/html/rfc3668
"OData follows REST principles and there exists some kind of data access. It is up to the stakeholders to define if the diferent API's are secure via the suggested tools (RFC 7617). OData on authenticathion: https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#sec_Authentication RFC 7617 reference: https://datatracker.ietf.org/doc/html/rfc7617 OData reference: https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#_Toc31358832"
'SAML 2.0 is a format that allows seamless cross-border interoperability between systems, regardless of its implementation. The specification allows cross-domain single sign-on, which reduces the administrative burden of the system administrators and the users. As well, providing authentication across sectors and platforms allows administrations and stakeholders to exchange and reuse data fostering the data portability across borders. SAML 2.0 Reference: http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-tech-overview-2.0.html'
'Domibus facilitates the exchange of electronic messages and documents between different entities, such as government agencies, organizations, and partners. Its primary purpose is to ensure the secure, reliable, and standardized transmission of data while adhering to relevant standards like the AS4 profile of the ebMS standard. Domibus specification: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/Domibus'
'MIME itself is not directly related to the enabling of exposure of interfaces, nonetheless, it can indirectly contribute to such purposes by promoting content negotiation and define data exchange formats. MIME specification: https://tools.ietf.org/html/rfc2045'
"LDES has been recommended by the Spanish government through their open data initiative webpage. The government's blog explains how LDES can help overcoming data publishing challenges. Overcoming Data Publishing Challenges with Linked Data Event Streams (LDES): https://datos.gob.es/en/blog/overcoming-data-publishing-challenges-linked-data-event-streams-ldes"
The purpose of the specification is not related to the long-term preservation of electronic records. Therefore, e-Delivery SMP 1.10 is not fostering the long-term preservation of electronic resources.
There are already existing documents and studies assessing the JSON's features and performance. In some cases, the study has been carried out in a comprehensive comparison between XML and JSON. See: https://www.researchgate.net/profile/Hanif_Ullah/publication/321361853_Behavior_based_Comparative_analysis_of_XML_and_JSON_web_technologies/links/5a1eb56f0f7e9b9d5e000bfd/Behavior-based-Comparative-analysis-of-XML-and-JSON-web-technologies.pdf https://www.researchgate.net/profile/Kamir_Yusof/publication/320045078_Efficiency_of_JSON_for_data_retrieval_in_big_data/links/5a3f14ea458515f6b0456f54/Efficiency-of-JSON-for-data-retrieval-in-big-data.pdf
'There are already existing assessments assessing the efficiency and effectiveness of the ISO/IEC 27001. An example of such assessment can be viewed on the following link. ISO/IEC 27001 assessment: https://www.researchgate.net/publication/286651142_Evaluating_the_Effectiveness_of_ISO_27001_2013_Based_on_Annex_A'
'Although the ETSI TS 119 612 specification does not provide information about if it can be partial implemented, it specifies some mechanisms which can be implemented incrementally or separately. There are some attributes that must be implemented, but other are optional. ETSI TS 119 612: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf'
The use of SAML 2.0 has been agreed for the eiDAS technical subgroup to use the specification on the eiD Building Block to support eiDAS regulation. The regulation 910/2014 is a document that implies all the Member States and their responsibilities as public services providers. Therefore, the agreement for using SAML 2.0 as part of the eiD Building to support eiDAS regulation can be understood as an agreement involving public services providers. See: https://ec.europa.eu/futurium/en/content/eidas-regulation-regulation-eu-ndeg9102014
'The purpose of OSI is not related to e-accessibility. Therefore, this criterion is not applicable to the specification. OSI reference https://www.iso.org/standard/20269.html'
'One of the main advantages of this technique of dynamic attribute provisioning is that attribute revocation does not enforce certificate revocation and re-issuance. This means that information is provided once-only and reused as needed. DAPS: https://github.com/International-Data-Spaces-Association/IDS-G/tree/main/Components/IdentityProvider/DAPS'
'SHACL is included in 3 national catalogues of recommended specifications. They belong to Belgium, Malta and the Netherlands. The National Interoperability Framework (NIF) of Belgium and the Netherlands are aligned with at least 3 out of 4 scoreboards of the EIF Monitoring according to the National Interoperability Framework Observatory (NIFO) factsheets. CAMSS list of standards: https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standard NIFO Factsheets: https://interoperable-europe.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public-administration-factsheets-2024 National Catalogue of Belgium: https://www.belgif.be/page/specifications.en.html National Catalogue of the Netherlands: https://www.forumstandaardisatie.nl/open-standaarden/lijst National Catalogue of Malta: https://mccaa.org.mt/Section/Content?contentId=1243 SHACL W3C reference: https://www.w3.org/TR/shacl/'
PDF/A is designed for this purpose. It is an Electronic document file format for long-term preservation of data. PDF/A reference: https://www.iso.org/standard/38920.html https://www.iso.org/standard/50655.html
'While genericode itself does not enforce the principle of providing information once-only and reusing it as needed, genericode can facilitate this principle by providing a standardised format for representing code lists. Furthermore, appendix E (non-normative) mentions considerations of life cycle metadata. Data life cycle management relies on having useful life cycle metadata with which to record properties of data and histories of changes in that data. Appendix E genericode: https://docs.oasis-open.org/codelist/genericode/v1.0/os/genericode-v1.0-os.html#A-CONSIDERATIONS-OF-LIFE-CYCLE-METADATA'
As one of the official European Standardisation Organisation, ETSI develops standards that are compliant with the European Standardisation Regulation 1025/2012. See: https://www.etsi.org/about/etsi-in-europe
'In ETSI EN 319 401, which is a complementary specification of ETSI ES 119 512, some trusted services are defined to improve the processing of trusted data. Some of these mechanisms are the creation, verification and validation of digital signatures and related certificates and the creation, verification and validation of time stamps and related certificates. Through these verification systems, data can be treated reliably, guaranteeing that data has not been altered since the digital signature was validated. ETSI TS 119 512: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.01_60/ts_119512v010101p.pdf ETSI EN 319 401: https://www.etsi.org/deliver/etsi_en/319400_319499/319401/02.03.01_60/en_319401v020301p.pdf'
'Valid PROV documents have to satisfy certain definitions, inferences, and constraints, and are specified in PROV-CONSTRAINTS document. Moreover, there can be found automated ways of testing PROV conformance, such as the PROV validator, a tool that validates PROV representations or translate them into other representations. PROV-CONSTRAINTS: https://www.w3.org/TR/2013/REC-prov-constraints-20130430/ ProvValidator: https://openprovenance.org/services/view/validator'
'YAML can be used with kubernetes. Kubernetes objects are intention registries that can be found inside Kubernetes system. These objects are useful to represent the state of a cluster. More specifically, kubernetes objects can describe which applications work in containers, the resources available for these applications, and how these aplications behave, in relation to reboot and update policies. Kubernetes reference: https://kubernetes.io/es/docs/concepts/overview/working-with-objects/kubernetes-objects/'
There are no Member States recommending SMP in their ICT National Catalogues. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'The purpose of SAML 2.0 is not related to the long-term preservation of electronic records and other kinds of information. Therefore, this criterion is not applicable to the specification. SAML 2.0 Reference: http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-tech-overview-2.0.html'
'There are existing documentation and studies assessing the effectiveness and efficiency of LDAP. It is a comparison between LDAP 2 and LDAP 3. As well, the study shows the improvement of the different versions over time as resulting in more efficient protocol. Difference between LDAP2 and LDAP3: https://docs.microsoft.com/en-us/previous-versions/windows/desktop/ldap/differences-between-ldap-2-and\x02ldap-3 Assessment of LDAP services in high availability environment: https://www.infona.pl/resource/bwmeta1.element.baztech-32ec800f-6db2-4a4a-be0a-bcb3fae16d23/tab /summary'
'The security section of OpenTelemetry asserts that receivers/exporters should use encrypton and authentication of their identity. They should also limit exposure of servers to authorised users and may pose a security risk if configuration parameters are modified improperly. In addition, any incoming or outgoing communication should leverage TLS and authentication. OTel Security Best Practices: https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/security-best-practices.md'
The purpose of CSS v2.1 is not related to the delivery of multilingual public services. Therefore, this criterion is not applicable to the specification. CSS v2.1 W3C reference: https://www.w3.org/TR/2011/REC-CSS2-20110607/
"Section 5.3.3 of the specification explicitly addresses and enables the implementation of features to guarantee data integrity thanks to its Identity and Access Management (IdAM). Depending on the user's role and identity, data may be restricted. ISO 19941: https://www.iso.org/obp/ui/en/#iso:std:iso-iec:19941:ed-1:v1:en"
'SCIM could contribute to simplifying the delivery of European public services by providing a standardized and interoperable way to exchange identity information. This can be valuable in scenarios where multiple systems and services need to collaborate, ensuring a consistent and efficient exchange of identity-related data. SCIM: https://scim.cloud/'
The ISO specifications are published to be able to respond to a market need which represent a consensus of an expert group. It was launched in 2012 as a proprietary solution. These facts demonstrate the maturity and market acceptance for its use in the development of products and services. XAdES ISO reference: https://www.iso.org/standard/56025.html XAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/101900_101999/101903/01.04.02_60/ts_101903v010402p.pdf
'The purpose of ShEx is not related to e-accessibility; therefore this criterion does not apply to the specification. ShEx primer document: https://shexspec.github.io/primer/ ShEx Community Group: https://www.w3.org/community/shex/ ShEx Github: https://github.com/shexSpec/spec/issues'
'The main purpose of ETSI TS 119 511 is to provide all the policy requirements needed for trust service providers providing long-term data preservation services of e-signatures and of general data. ETSI TS 119 511 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119511/01.01.01_60/ts_119511v010101p.pdf '
DCAT is maintained by W3C which is an international community developing open standards. See: https://www.w3.org/Consortium/ https://github.com/w3c/dxwg/
The specification is available for its use and implementation at the XIPH webpage defined in several RFCs. Moreover, all Ogg RFCs have a mirror copy in IETF's webpage. Ogg XIPH reference: https://xiph.org/ogg/doc/rfc3533.txt Ogg Media Types XIPH reference: https://tools.ietf.org/html/rfc5334
'IETF is a vendor neutral standard developing organisation and HTTPS is independent from any platform. HTTPS specification: https://tools.ietf.org/html/rfc2818 '
'Domibus, as an open-source messaging platform focused on secure and standardized message exchange, is designed to work with various underlying technologies. It is not tied to a specific technology and can be integrated with different components and systems depending on the implementation requirements. Domibus specification: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/Domibus'
'The purpose of LDAP is not related to e-accessibility. Therefore, this criterion is considered not applicable to the specification. LDAP IETF reference: https://tools.ietf.org/html/rfc4511'
'OAS can enable the delivery of European public services in the sense that it conveys a clear structure and procedure for the creation of APIs that can provide services that reduce the administrative burden. Using OAS, is a way to keep APIs documentation and source code synchronized, while the consumers are found to understand the capabilities of each operation on the API, and subsequently, interact without comprehending the implementation logic. OAS specification: https://spec.openapis.org/oas/latest.html#openapi-specification OAS in Github: https://github.com/OAI/OpenAPI-Specification/#participation'
'The version 1.0 of the specification, which is the previous version of the SMP, was identified within the List ICT technical specifications as reusable, meaning that the Service Metadata Publisher is considered. Even though the version being assessed is not the one identified, it can be considered that the SMP is listed within this repository at European Level. ICT technical specifications: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en'
'DCAT is included in the catalogues of five states, among which there are the Netherlands and Spain. Netherlands National Catalogue Reference: https://www.forumstandaardisatie.nl/open-standaarden/lijst Spanish National Catalogue Reference: https://administracionelectronica.gob.es/pae_Home/dam/jcr:9e2c2877-5103-4934-8440-c60ba2e10c48/Catalogue_of_Standards_NIF_Spain.pdf '
XSD provides schemas for the validation of XML and the proper data exchange by means of it. Therefore, by ensuring the well formation and validity of the documents being exchanged, XSD fosters the data portability between systems and administrations across borders.
'The ebXML specification has been published and is maintained by the Organization for the Advancement of Structured Information Standards (OASIS). In addition, the specification has joined now ISO organisation and it is now respnsible of the specification. OASIS Commitee reference: https://groups.oasis-open.org/communities/tc-community-home2?CommunityKey=eb27e05e-9bf5-4821-b1ed-018dc7d3f258 ebXML RegRep OASIS reference: https://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html ebXML RegRep ISO reference: https://www.iso.org/standard/83479.html'
'Syslog is a versatile logging protocol that allows for the comprehensive capture of administrative procedures, rules data, and services within a networked environment if combined with other specifications. This specification scopes comprehensibility by allowing standard user authentication and authorization, configuration changes, firewall and security rules, Intrusion Detection/Prevention Systems (IDS/IPS), network services, etc. Although it does not directly manage administrative procedures, it does provide the necessary data for these tasks. Syslog Protocol: https://datatracker.ietf.org/doc/html/rfc5424'
'The TGF specification provides a framework for ensuring the security and integrity of information, but its effectiveness in guaranteeing these protections will depend on how it is implemented and used in practice. TGF specification: http://docs.oasis-open.org/tgf/TGF/v2.0/cs01/TGF-v2.0-cs01.html'
'XBRL GL is machine readable data and as a interface format and does not require special software. XBRL is based on XML which is under the W3C. XBRL GL has the semantic information of XBRL GL, which can be used to drive Linked Data. The specification includes URI references extensively. While the primary representation of XBRL GL is with the syntax of XBRL, the semantic is reusable in many syntaxes, and unique in its design. XBRL worked closely with the W3C in evaluating the XBRL syntax and W3C specifications (https://www.w3.org/2009/02/xbrl-ig/charter.html), noting “Facts, concepts and links in XBRL documents can be readily mapped into the Semantic Web. XBRL concepts can be identified via the XML namespace for the schema document defining them as elements together with the element name for each concept.” Related to the levels of 5 star data: “make your stuff available on the Web (whatever format) under an open license” XBRL GL is freely licensed and royalty free “make it available as structured data (e.g., Excel instead of image scan of a table)” XBRL GL is a specification for structuring and expressing business data at any level of detail or aggregation “make it available in a non-proprietary open format (e.g., CSV instead of Excel)” XBRL is a non-proprietary open format. XBRL also can be expressed using JSON, CSV, and other formats. “use URIs to denote things, so that people can point at your stuff” While XBRL GL’s primary use is within the Enterprise and for data kept confidential by government agencies, such as tax filings, URIs are used internally, and the W3C has noted the ease of mapping XBRL syntax documents into Linked Data environments. “link your data to other data to provide context” XBRL GL has been uniquely designed to link both to source data and other contextual information at the detail level, and to unambiguously link to summary reporting information at the aggregate level. The SRCD portion of the Specification formalizes the summarization of XBRL GL detail to other reported open data. The specifications for relating to underlying source information are internally being harmonized with other open specifications for relating to other information, as part of other interoperability efforts under UN/CEFACT and the ISO. In this case, XBRL GL is a data representation schema that is based on XML; XBRL GL makes data available in a structured manner aligning with the second-star from Tim Berners-Lee approach. Therefore, the specification facilitates the publication of open data. About XBRL ( XBRL GL is based on) and linked data in general: https://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.232.971&rep=rep1&type=pdf '
'While the CSIP itself does not specifically facilitate organizational interoperability agreements, its implementation can indirectly support interoperability efforts by promoting standardized formats, metadata standardization, compliance with standards and regulations, and the development of data exchange guidelines. E-ARK CSIP specification: https://earkcsip.dilcis.eu/#introduction'
IETF is a consensus-based group, and authority to act on behalf of the community requires a high degree of consensus and the continued consent of the community. The process of creating and Internet Standard is straightforward: a specification undergoes a period of development and several iterations of review by the Internet community and revision based upon experience, is adopted as a Standard by the appropriate body... and is published. In practice, the process is more complicated, due to (1) the difficulty of creating specifications of high technical quality; (2) the need to consider the interests of all of the affected parties; (3) the importance of establishing widespread community consensus; and (4) the difficulty of evaluating the utility of a particular specification for the Internet community. The goals of the Internet Standards Process are: - Technical excellence; - prior implementation and testing; - clear, concise, and easily understood documentation; - openness and fairness; and - timeliness. The goal of technical competence, the requirement for prior implementation and testing, and the need to allow all interested parties to comment all require significant time and effort. The Internet Standards Process is intended to balance these conflicting goals. The process is believed to be as short and simple as possible without sacrificing technical excellence, thorough testing before adoption of a standard, or openness and fairness. See: https://www.ietf.org/standards/process/
SMP is a business domain agnostic specification that can be reused in a cross-domain way. The specification: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505000
'JSON can be utilized within the context of various technologies, such as APIs, web services, microservices, or client-server communication, to facilitate the definition and implementation of interfaces. JSON specification: https://www.ecma-international.org/wp-content/uploads/ECMA-404_2nd_edition_december_2017.pdf'
"The OData protocol is an application layer protocol for exchanging data through RESTful interfaces. In this sense, the specification enables exposure of any interface, including those interfaces providing access to public administration's services. OData reference: https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#_Toc31358832"
'Domibus Adherence to AS4 standard guarantees that messages exchanged through Domibus can be digitally signed, providing a mechanism to verify the authenticity and integrity of the data being transmitted. This helps ensure that messages originate from legitimate sources and have not been altered during transmission. Digital signatures contribute to data authenticity and help prevent tampering or unauthorized modifications. Domibus specification: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/Domibus AS4 specification: http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/profiles/AS4-profile/v1.0/AS4-profile-v1.0.html'
'OAS defines a standard, programming language-agnostic interface description for HTTP APIs, which allows both humans and computers to discover and understand the capabilities of a service without requiring access to source code, additional documentation, or inspection of network traffic. OAS usefulness, therefore, lies in the comprehensibility of the APIs development, as it facilitates coding and also documenting the development in an easy, understandable way. OAS specification: https://spec.openapis.org/oas/latest.html#openapi-specification OAS in Github: https://github.com/OAI/OpenAPI-Specification/#participation '
'The purpose of BFO is not related to secure exchange of data since the specification not provide any reference to security considerations. BFO reference: https://www.iso.org/standard/74572.html'
ELI is publicly available for its implementation and its use for free on ELI's webpage. Within ELI home page there are implementation resources, best practices and guidelines to ensure its proper implementation. ELI reference: https://eur-lex.europa.eu/eli-register/about.html
'Few DID methods support portability accross verifiable data registries. Moreover, DIDs can enhance portability, allowing users to seamlessly transfer their identifiers and related data between different platforms. Therefore, become system- and network-independent and enable entities to use their digital identifiers with any system that supports DIDs and DID methods. DIDs W3C github: https://w3c.github.io/did-imp-guide/FPWD/2021-08-26/#verifiable-data-registry DIDs W3C: https://www.w3.org/TR/did-core/#design-goals'
FTP is a protocol exclusively designed for the transfer of files which does not secure the traffic. However, there are existing extensions of FTP that secure the information delivery. For instance, FTP over TLS, known as FTPS, uses the Transport Layer Security (TLS) to secure FTP communications over a network. See: https://tools.ietf.org/html/rfc959 https://tools.ietf.org/html/rfc4217
'The purpose of OSI is not related to the protection of personal data managed by Public Administrations since the specification does not provide any privacy considerations. OSI reference https://www.iso.org/standard/20269.html'
'There are several success stories and implementation examples that provide visibility on the effectiveness of implementing ELI. It allows the description of legal resources and increases the shareability across borders enhancing the cooperation amongst European Institutions removing barriers. ELI reference: https://eur-lex.europa.eu/eli-register/about.html ELI highlights: https://eur-lex.europa.eu/eli-register/index.html ELI Testimonials: https://eur-lex.europa.eu/eli-register/testimonials.html'
'The dependency on different transport mechanism, such as HTTP, SMTP or LDAP, when sending an OCSP request in specific rollout scenarios suggests that the specification is not technology-agnostic. OCSP reference, section 4.1: https://datatracker.ietf.org/doc/html/rfc6960#section-4.1'
'The specification is independent from any particular software, hardware, or operating system. So, it can be said that EuroVoc is independent of any specific platform. EuroVoc: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource /dataset/eurovoc'
"Within the Roy Fielding dissertation of REST ou can find a chapter that addresses the experience and lessons learned from applying REST. REST's efficiency, as stated in the dissertation, is mainly based on its architectural constraints, which captures all of those aspects of a distributed hypermedia system that are considered central to the behavioral and performance requirements of the Web. R. Fielding dissertation. Chapter 6: experience and evaluation. https://www.ics.uci.edu/~fielding/pubs/dissertation/evaluation.htm"
The specification is available for its use and implementation at the EITF's webpage defined in several RFCs. See: https://tools.ietf.org/html/rfc791 https://tools.ietf.org/html/rfc1349 https://tools.ietf.org/html/rfc2474 https://tools.ietf.org/html/rfc6864
There are no Member States recommending TSP in their ICT National Catalogues. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'CPOV can be implemented in any platform and it is independent of any platform. CPOV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-organisation-vocabulary'
'Domibus has not been found recommended by any European Member State. Domibus specification: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/Domibus'
The purpose of IPv4 is not related to the delivery of multilingual services. Therefore this criterion is not applicable to this specification.
'The purpose of SHACL is not related to enable the secure exchange of data. Therefore this criterion is not applicable to this specification. SHACL W3C reference: https://www.w3.org/TR/shacl/'
Like all the IETF standards, FTPS is a free and open technical specification, built on IETF standards and licenses from the Open Web Foundation. Therefore, FTPS is licensed on a royalty-free basis. Intellectual Property Rights in IETF: https://tools.ietf.org/html/rfc3668
'CSV is included in 12 national catalogues of recommended specifications. They belong to the Netherlands, Estonia, Sweden and Spain, among others. The National Interoperability Framework (NIF) of these Member States is fully aligned with at least 2 out of 3 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO)factsheets. NIFO factsheets: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public-administration-factsheets-2022 CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards '
The main purpose of OWL2 is to allow accessing, importing, sharing, and reusing public ontologies. The data described by an ontology in the OWL family is interpreted as a set of "individuals" and a set of "property assertions" which relate these individuals to each other. So it helps administrations to infer knowledge over other administrations and stakeholders' data. It also happens in a bidirectional way, easing the visibility and the relationship between the data and datasets of the administrations. Moreover, it makes data reusable and visible, enhances, and fosters the decision-making process._x000D_ _x000D_ OWL2 W3C reference:_x000D_ https://www.w3.org/TR/owl2-overview/
'Secure processing of data can be provided by DNS adding the DNS Security Extensions (DNSSEC), which is, in fact, almost a mandatory extension between major stakeholders. Processing of data is secured by the encrytion under which the domain is protected provided by DNSSEC or other extensions addressing security issues. Resource Records for the DNS Security Extensions: https://datatracker.ietf.org/doc/html/rfc4034 Extension Mechanisms for DNS: https://datatracker.ietf.org/doc/html/rfc6891 DNS IETF reference: https://www.ietf.org/rfc/rfc1034.txt'
'XSLT includes features that allow extension by implementers or users, designed to maintain interoperability (see Section 2.9). XSLT Reference: https://www.w3.org/TR/xslt-30/#extensibility'
'There is no conformity test coming from the IETF, but there are existing free online documents that will help you validate LDAP specification when it is implemented. However, it is a manual process that does not provide 100% automatic validation. IBM testing LDAP authentication settings: https://www.ibm.com/support/knowledgecenter/SSZQFR_2.2.5/doc/iwd/ldap_test_settings.html Test LDAP configurations: https://docs.microfocus.com/itom/Operations_Orchestration:10.80/Develop/Working_with_API /Testing_LDAP_Configurations LDAP Tools: https://ldap.com/ldap-tools/'
'There is no evidence that AMQP is included on any initiative covering privacy aspects. Oasis AMQP Reference: http://docs.oasis-open.org/amqp/core/v1.0/amqp-core-complete-v1.0.pdf'
SAML 2.0 is included in the Slovakian national catalogue of recommended specifications. The National Interoperability Framework (NIF) of Slovakia is fully aligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets See: https://joinup.ec.europa.eu/collection/national-interoperability-framework-observatory-nifo/nifo-factsheets
'Publiccode.yml is a specification developed by the Italian Government. Even though the specification can be reusable and potentially included at European level as an asset, at the moment of the assessment it is not considered a European Standard. Publiccode.yaml documentation: https://docs.italia.it/italia/developers-italia/publiccodeyml-en/en/master/index.html'
'The ebXML specification is developed by a non-European organisation. Therefore, the specification cannot be considered a European standard. ebXML RegRep OASIS reference: https://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html'
'The purpose of EN 16234-1 e-CF is not related to enabling the long-term preservation of data, information nor knowledge. Therefore, this criterion does not apply to this specification. CEN reference, CEN/TC 428 - ICT Professionalism and Digital Competences (Published standards), EN 16234-1 e-CF: https://standards.cencenelec.eu/dyn/www/f?p=205:110:0::::FSP_PROJECT:67073&cs=15E62ED24D608A5F10D6BEE8E6D50FA10'
'ISO standards are not licensed on a royalty-free basis since they require an initial payment for accessing it and using it. Moreover, conformance testing requires payment in some cases. ISO 27001 foreword: https://www.iso.org/obp/ui/#iso:std:54534:en'
'As a vocabulary, the implementation of CPOV can be tested using methods like SHACL shapes and using semantic reasoners to ensure that the implementation is well-formed. These validation mechanisms can be used with open source tools or lite versions of tools like GrapghDB or Protégé. SHACL validation: https://graphdb.ontotext.com/documentation/free/shacl-validation.html#what-is-shacl-validation Semantic Reasoners List: http://owl.cs.manchester.ac.uk/tools/list-of-reasoners/'
'The EN 16234-1 e-CF framework is intended to serve as a device to represent the European e-Competence Framework, which focuses on skills and competences of the ICT professional workforce. There is no possibility of partial implementation of the specification, as EN 16234-1 e-CF has a single purpose. CEN reference, CEN/TC 428 - ICT Professionalism and Digital Competences (Published standards), EN 16234-1 e-CF: https://standards.cencenelec.eu/dyn/www/f?p=205:110:0::::FSP_PROJECT:67073&cs=15E62ED24D608A5F10D6BEE8E6D50FA10'
'IEEE Std 802.3-2022 primarily focuses on the physical and data link layers of Ethernet networking, helping to build a more efficient infrastructure capable of supporting European public services. This is why it has been included in the ICT Rolling Plan. Rolling Plan for ICT standardisation: https://joinup.ec.europa.eu/collection/rolling-plan-ict-standardisation IEEE Std 802.3-2022 Reference: https://ieeexplore.ieee.org/document/9844436'
'There are several studies assessing SOAP 1.2 performance and features in terms of efficiency and effectiveness. As REST and SOAP-based web services are living together nowadays, one of the topics is the performance comparison. Moreover, the comparison between different SOAP toolkits is an exploited topic. Performance and Usage Between REST and SOAP Reference: https://aaltodoc.aalto.fi/bitstream/handle/123456789/29224/master_Makkonen_Joni_2017.pdf?sequence=1&isAllowed=y SOAP Toolkits Assessment Reference: https://dl.acm.org/citation.cfm?id=1033266'
'Several developer platforms discuss XACML extensively, one prominent example being Stack Overflow. Stack Overflow operates as a community-driven forum where developers can ask questions, share insights, and provide solutions related to XACML. Stackoverflow XACML: https://stackoverflow.com/questions/2893247/who-uses-xacml'
'The purpose of TOSCA is not related to the publication of open data. Therefore, this criterion is not applicable to this specification. TOSCA reference, section 1.2: https://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.3/os/TOSCA-Simple-Profile-YAML-v1.3-os.html#_Toc26969412 Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/en/'
LegalDocML has been included within the European Commission's Rolling Plan for ICT Standarisation and in the related standardisation activities of the same report. Moreover, it was introduced as part of the ISA2 work programme back in 2016 as part of the LEOS project activity to investigate and work towards its implementation. The European Commission includes in its Rolling Plan for ICT Standarisation: https://ec.europa.eu/digital-single-market/en/rolling-plan-ict-standardisation ISA2 WORK PROGRAMME: https://www.ospi.es/export/sites/ospi/documents/documentos/ISA2-work-programme-2016-detailed-action-descriptions.pdf
'No formal agreements have been found between organisations or administrations including OData in a European public service provision. ICT Technical Specifications reference: https://ec.europa.eu/growth/single-market/european-standards/ict-standardisation/ict-technical-specifications_en'
The specification in itself acts as a method to ensure that policies and laws are developed, implemented and monitored and enhanced following a standardised method that includes, guidelines, recommendations and requirements to reach the objective of exhaustive and comprehensible laws and policies. Better Regulation Toolbox on European Comission webpage: https://ec.europa.eu/info/law/law-making-process/planning-and-proposing-law/better-regulation-why-and-how/better-regulation-guidelines-and-toolbox/better-regulation-toolbox_en
'Although MIME has been pointed out by the European Commission as one of the 27 technical specifications widely used for internet purposes eligible for referening in public procurement, it has been developed and maintained by the IETF, which implies it is not a European standard. Commission Implementing Decision (EU) 2017/168: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32017D0168 '
The purpose of RegOrg is not related to long term preservation of electronic records. Therefore, this criterion is considered not applicable to this specification. RegOrg Joinup reference: https://joinup.ec.europa.eu/solution/registered-organization-vocabulary
'TSP can be implemented in any platform and it is independent of any platform. TSP IETF reference: https://tools.ietf.org/html/rfc3161'
'TSP is used in many European Member States, using TSA for time stamping services. One of the countries in which TSA is used is in Spain, where the sealing service allows electronic document stamps to be issued by the bodies supplying the service. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards Spain TSA reference: https://administracionelectronica.gob.es/ctt/verIniciativaPInfoAdificional.htm?idIniciativa=tsa&idioma=en'
Although the Core Public Organisation Vocabulary is sufficiently mature for its use in the development of products and services, it does not have a good market acceptance because it has not been integrated with any official solution, it has only been tested on pilots. CPOV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-organisation-vocabulary
'LDES is currently a powerful tool covering data interoperability aspects in the configuration of data spaces. Given that the technology is well-positioned to support the interoperability, real-time data sharing, and data sovereignty goals of data spaces. Moreover, it can be found in the Data Space Support Center (DSSC) standards catalogue. LDESspecification: https://joinup.ec.europa.eu/collection/semic-support-centre/linked-data-event-streams-ldes DSSC Standards catalogue: https://dssc.eu/space/SE1/185794608/Data+Interoperability+standards+and+technologies+landscape'
'Dataspaces can contribute to improved data quality and governance by establishing a framework for managing metadata, ensuring data consistency, and enforcing data policies across the integrated datasets. IDSA Dataspace Protocol: https://docs.internationaldataspaces.org/ids-knowledgebase/v/dataspace-protocol/overview/readme'
'The purpose of MIME is not related to long term preservation of electronic records. Therefore, this criterion is considered not applicable to this specification. MIME specification: https://tools.ietf.org/html/rfc2045'
'While DCAT does not explicitly encourage the creation of communities or the sharing of data and results on national platforms, its use can help to enable these activities by providing a common format for describing and sharing metadata about data sets. By providing a standardized way of describing and sharing data, DCAT can help to facilitate the discovery, access, and reuse of data, which can in turn help to support collaboration and the creation of communities around data. DCAT (v2.0.0) reference: https://www.w3.org/TR/vocab-dcat-2/ '
'The purpose of Advanced Encryption Standard is not related to enabling the visibility of administrative procedures, rules data, and services. Therefore this criterion is not applicable to the specification. AES Standard Reference: https://csrc.nist.gov/pubs/fips/197/final'
'Domibus, as an eDelivery Access Point (AP) solution, is primarily designed to facilitate secure and reliable message exchange between different entities, particularly within the context of eGovernment services and cross-border data exchange. While Domibus itself focuses on message exchange, it can indirectly contribute to enabling the visibility of administrative procedures, rules data, and services by providing a platform for standardized communication. Domibus specification: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/Domibus'
There is no national or European platform with the specification FTPS available for free.
The purpose of Xforms is not related to the delivery of multilingual public services. Therefore, this criterion is not applicable to this specification. Xforms 2.0 W3C reference: https://www.w3.org/community/xformsusers/wiki/XForms_2.0
The adoption of CPOV as a data model does not hamper the scalability of systems. The use of existing data models for the development of common information systems facilitates the development of those systems and improves their interoperability. CPOV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-organisation-vocabulary
SHACL is a web standard whose only purpose is RDF data graphs validation. Therefore, in terms of scalability, there are no evidences that prove the scalability of SHACL.
'There is no possibility of tailoring the ISO 3166-1 country codes system, nor any kind of authorising process is allowed, as the specification was conceived for a unique purpose. ISO 3166-1 reference: https://www.iso.org/standard/72482.html '
After checking the assessments performed by CAMSS and the list of specifications identified by the Multi-stakeholder-platform (MSP), no assessment verifying the compliance of the specification with the European standardisation regulation has been found.
'RDF can facilitate organisational interoperability agreements by providing a standardised way to represent and exchange data, supporting the creation of common vocabularies and ontologies, and enabling the creation of semantic mappings between different data sources and formats. RDF primer document: https://www.w3.org/TR/rdf11-primer/'
The purpose of the specification is not related to portability between systems and applications. Therefore, this criterion is not applicable to this specification.
'The ELI specification allows for extensions. The ELI Task Force is responsible for proposing updates to the ELI specifications. They also provide resources like the ELI annotation tool and the ELI validator to assist in the implementation and validation of ELI metadata. ELI governance reference: https://eur-lex.europa.eu/content/eli-register/governance_rules.pdf ELI annitation and validator tool: https://eur-lex.europa.eu/eli-register/resources.html'
'SCIM is recommended by the Netherlands according to the CAMSS List of Standards, which means that this specification is included in their national catalogue of standards. Netherlands Standardisation Forum: https://www.forumstandaardisatie.nl/open-standaarden/aanbevolen '
'The AKN4EU specification itself does not provide specific mechanisms for the secure processing of data. However, it can be used as part of an overall approach to enable secure data processing. AKN4EU reference: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/akn4eu'
'TLS 1.3 specification simplifies the delivery of European public services by enhancing both the security and speed of online connections. The 0-RTT feature, which allows for faster reconnections and minimises delays, directly contributes to a more efficient user experience. Moreover, TLS 1.3 emphasis on security ensures that sensitive public service data remains protected. TLS 1.3 Major Differences from TLS 1.2 Reference: https://www.rfc-editor.org/rfc/rfc8446.html#section-1.2'
ADMS is an RDF vocabulary for representing concepts of a repository, intended to facilitate the co-operation. By describing the assets, releases, and distributions of a repository, it fosters the publications of data and its discoverability. _x000D_In fact, ADMS is the basis for the ADMS-AP used in Joinup to describe the different reusable solutions and make them better discoverable and reusable across borders. _x000D_ _x000D_ ADMS in Joinup:_x000D_ https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/adms
'At this moment, even though the specification is developed by the European Commission, since it is not developed by any of the European Standardisation Bodies, it cannot be considered a European Standard. However, since the European Commission works and develops specifications under the standardisation regulation, the EIRA meets the requirements set under the regulation, which make it a good option to use in procurement process and in the public sector in general. EIRA reference: https://interoperable-europe.ec.europa.eu/collection/european-interoperability-reference-architecture-eira /solution/eira/release/610 EIRA Github Repository: https://github.com/CarTool-EC/EIRA'
The purpose of Xforms is not related to the availability of interfaces with internal information systems. Therefore, this criterion is not applicable to this specification. Xforms 2.0 W3C reference: https://www.w3.org/community/xformsusers/wiki/XForms_2.0
TSP is not included in any Member States' catalogues of recommended specifications. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
Data on the Web Best Practices W3C is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, it can define the interoperability aspects of the "Data Publication Component" and "Data Publication Service" ABBs of the EIRA Technical Infrastructure View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/solution/elis/release/v100
'The purpose of DNS is not related with data portability. Therefore, this criterion is not applicable to this specification. DNS IETF reference: https://datatracker.ietf.org/doc/html/rfc8499 Domain Names - Implementation and Specification: https://tools.ietf.org/html/1035'
'The purpose of AMQP does not enable the e-accessibility. Therefore, this criterion is not applicable to this specification. OASIS AMQP Reference: http://docs.oasis-open.org/amqp/core/v1.0/amqp-core-complete-v1.0.pdf'
Although XHTML is aligned with the different levels of maturity of Tim Berners-Lee's 5-star schema for Open Data, it does not support the different principles of Linked Open Data. XHTML W3C reference: https://www.w3.org/TR/xhtml1/ 5-star linked open data: https://www.w3.org/DesignIssues/LinkedData.html
The purpose of FTP is not related to the delivery of multilingual European public services. Therefore this criterion is considered not applicable specification.
'The purpose of WAI-ARIA is increasing accessibility of web content and applications for a large range of users, either with special needs or without disabilities. Therefore, this specification addresses and enables e-accessibility. WAI-ARIA reference, section 1: https://www.w3.org/TR/wai-aria/'
The LegalDocML is available for free at the SDO's webapge but it is also accessible through LEOS project and sofware application documentation, which can be found in joinup. LegalDocML reference: https://www.oasis-open.org/committees/legaldocml/charter.php LEOS: https://joinup.ec.europa.eu/collection/justice-law-and-security/solution/leos-open-source-software-editing-legislation
8 Member States are recommending XHTML in their ICT National Catalogues. This Member States are Estonia, France, Germany, Greece, Norway, Poland, Slovenia and Spain. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'The purpose of the specification is not related to the publication of public data as Open Data. Therefore this criterion is not applicable to the specification. YAML specification: https://yaml.org/spec/1.2.2/'
'The PROV Family of Documents are the final output of the Provenance Working Group chartered to specify a representation of provenance of data and information to facilitate its exchange over the Web. Since its first publication, the Working Group has continuously been updating the specifications and correcting errata. The group finished its liaison with W3C on 2013 as it can be seen in the WG Charter, along with all the related activities to the development of the specifications. PROV WG Charter: https://www.w3.org/2011/01/prov-wg-charter PROV errata: https://www.w3.org/2011/prov/errata.html PROV Primer document: https://www.w3.org/TR/prov-primer/ '
The W3C Royalty-Free IPR licenses granted under the W3C Patent Policy apply to all W3C specifications, including ODRL. W3C patent practice: https://www.w3.org/TR/patent-practice#ref-AC
'The specification itself does not provide a built-in access control mechanism. Therefore, this criterion is not applicable to the specification. AKN4EU reference: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/akn4eu'
Nowadays, at the moment of performing the assessment WSDL is wide used specification involved in the implementation of the Service-Oriented Architectures (SOAs). SOAP along with REST are the main ways to build web services, the first one uses WSDL to describe services and guaranteeing access to them. Therefore, WSDL is involved in the development of solutions, including innovative ones.
'The purpose of NFVI is not related to the publication of open data. Therefore, this criterion is not applicable to this specification. NFVI reference: https://www.etsi.org/deliver/etsi_gs/NFV-INF/001_099/001/01.01.01_60/gs_NFV-INF001v010101p.pdf Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/en/'
'The purpose of Core Location Vocabulary is not related to the protection against unauthorised changes. Therefore this criterion is considered not applicable to the specification. Core Location Vocabulary: https://interoperable-europe.ec.europa.eu/collection/semic-support-centre/solution/core-location-vocabulary/release/100'
'It is possible to customize the UDDI node with the properties we want, including the mandatory properties of the node. IBM customize reference: https://www.ibm.com/docs/en/was-zos/9.0.5?topic=registry-setting-up-customized-uddi-node'
'Protocols for remote digital signature creation can indeed enable visibility into administrative procedures, rules data, and services, but the extent of this visibility depends on the specific protocol and its implementation. Remote digital signature protocols often involve interactions between a client (the party requesting the signature) and a server (where the signature is generated). The protocol may include mechanisms for users, verifying the integrity of documents, and ensuring the security of the signature generation process. ETSI TS 119 432: https://www.etsi.org/deliver/etsi_ts/119400_119499/119432/01.02.01_60/ts_119432v010201p.pdf'
ASiC Baseline Profile is available for free at the ETSI’s Catalogue of Standards. It can be found at ETSI’s webpage. See: https://www.etsi.org/deliver/etsi_ts/103100_103199/103174/02.02.01_60/ts_103174v020201p.pdf https://www.etsi.org/standards
XHTML is publicly available for implementation and study for free on W3C's webpage. XHTML W3C reference: https://www.w3.org/TR/xhtml1/
The DCAT vocabulary has a strong support from the interest groups and is extensively used by public administrations’ for the exchange of data across borders and sectors. Additionally, the specification is widely used by public administrations profiling or extending it to fit domain-specific or national requirements - DCAT-AP: Application Profile for Public Sector Datasets. - DCAT-AP-BE: Extension of DCAT-AP for Belgium specific requirements. - StatDCAT-AP: Extension of DCAT-AP for the publication of statistical data. See DCAT Implementations: https://www.w3.org/2011/gld/wiki/DCAT_Implementations
'There has been found some studies assessing the effectiveness of PROV. Between some of the studies, we can find one assessing the effectiveness of PROV when applied to signatures and validation methods. More assessment samples can be found below. Measuring PROV provenance on the web of data: http://provenanceweek.org/2016/p3yl/papers/paper_89.pdf The rationale of PROV: https://www.sciencedirect.com/science/article/pii/S1570826815000177 A Canonical Form for PROV Documents and Its Application to Equality, Signature, and Validation: https://dl.acm.org/doi/abs/10.1145/3032990'
'W3C provides a free source for RDF validation. RDF validator: https://www.w3.org/RDF/Validator/'
'By allowing individuals to control their own digital identities, DIDs can help avoid administrative burden. With DIDs, citizens can manage their own data, share it selectively, and authenticate their identities without dependence on centralized authorities, which can be regarded as a good service simplifier. DIDs W3C: https://www.w3.org/TR/did-core/'
"The main purpose of HTTP Cookies is to track and store user's data on the webpage, and to use this data to remember the user's preferences (such as language, name, etc) for a certain period of time, so that you don't have to re-enter them when browsing around the site during the same visit. For that matter, HTTP Cookies, to some degree, enables the visibility of administrative procedures, rules data, and services. HTTP Cookies reference: https://developer.mozilla.org/en-US/docs/Web/HTTP/Cookies#creating_cookies"
'COMMISSION IMPLEMENTING DECISION (EU) 2016/120: "The XBRL 2.1 should therefore be identified as ICT technical specification eligible for referencing in public procurement," and " The eXtensible Business Reporting Language version 2.1 is eligible for referencing in public procurement." XBRL GL is a taxonomy based on xbrl. https://eur-lex.europa.eu/legal-content/EN/TXT/?toc=OJ%3AL%3A2016%3A023%3ATOC&uri=uriserv%3AOJ.L_.2016.023.01.0077.01.ENG '
XAdES is within the European eIDAS regulation which is legally binding for all EU members states.
ODF is included in 4 national catalogues of recommended specifications. They belong to Denmark, Estonia, the Netherlands and Sweden. The National Interoperability Framework (NIF) of these Member States is fully aligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. CAMSS List of standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards National Interoperability Framework Observatory: https://joinup.ec.europa.eu/collection/national-interoperability-framework-observatory-nifo/nifo-factsheets
TIFF/IT is included in 2 national catalogues of recommended specifications. They belong to Estonia and Spain. The National Interoperability Framework (NIF) of these Member States is fully aligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. National catalogue Estonia: https://www.mkm.ee/sites/default/files/interoperability-framework_2011.doc National catalogue Spain: https://administracionelectronica.gob.es/pae_Home/pae_Estrategias/pae_Interoperabilidad_Inicio/pae_Normas_tecnicas_de_interoperabilidad.html#CATALOGOESTANDARES NIFO factsheets: https://joinup.ec.europa.eu/collection/national-interoperability-framework-observatory-nifo/nifo-factsheets
'The specification is developed and maintain within GitHub and in a public repository. Everyone can participate proposing new changes via issue or pull request. There is no limitation to participate in the development process. Users need just need a GitHub account. Publiccode.yaml contributing: https://github.com/publiccodeyml/publiccode.yml/blob/main/CONTRIBUTING.md'
'The specification itself does not encourage the creation of communities at European platforms. It makes use of OASIS community to share data and results among their contributors. SAML2.0 Reference: http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-tech-overview-2.0.html OASIS Members Reference: https://www.oasis-open.org/members/ '
'OAIS defines a set of concepts and principles for the long-term preservation of digital information, and it does not prescribe any particular technology or system for implementing those principles. The reference model is designed to be flexible and adaptable to a wide range of technological environments, and it emphasizes the importance of maintaining the independence of the preservation system from the technology used to create, store, and manage the digital objects. OAIS specification: https://public.ccsds.org/Pubs/650x0m2.pdf'
'An important aspect of UBL design is its support for customization to meet the needs of individual organizations while maintaining complete interoperability within the standard framework. To suit the requirements of specific relationships, data structures of arbitrary complexity can be added to UBL documents without breaking XML validation against the standard schemas. UBL v2.3 reference: http://docs.oasis-open.org/ubl/os-UBL-2.3/UBL-2.3.html Developer community OASIS. UBL functionalities: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ubl#functionality UBL Guidelines for customization: https://docs.oasis-open.org/ubl/guidelines/UBL2-Customization1.0cs01.pdf'
The purpose of DNS is not related to e-accessibility. Therefore this criterion is not applicable specification.
' Being in a low maturity level of development DPV is being developed under the guidelines proposed by W3C. Consequently, DPV is still not a standard nor is it in the W3C standards track, and it is not a European Standard. DPV specification: https://w3c.github.io/dpv/dpv/ DPV primer document: https://w3c.github.io/dpv/primer/#introduction '
'The specification Asset Administration Shell (AAS) clearly mentions that the designator elements (properties of the asset) need to be properly defined in the metamodel in order to reuse the information of the assets, if this condition is met the info can be shared once and reused as needed. Details of the Asset Administration Shell (AAS) https://industrialdigitaltwin.org/en/wp-content/uploads/sites/2/2024/06/IDTA-01001-3-0-1_SpecificationAssetAdministrationShell_Part1_Metamodel.pdf '
MIME is maintained and developed by IETF which is an international community developing open standards. Developer community IETF: https://www.ietf.org/about/
The purpose of PDF 1.7 is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification.
The purpose of IPSec is not related to the publication of public data as open data. Therefore this criterion is not applicable to this specification.
The purpose of this Core Vocabulary is not related to security and privacy of the data exchange. Therefore, this criterion is not applicable to this specification. CPSV-AP reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-service-vocabulary-application-profile
Ogg was designed to create an open source multimedia container which it is independent of any vendor. However, Ogg is dependant of some open source technologies that make it up. The audio layer is most commonly provided by Vorbis format or its successor Opus. Lossless audio compression formats include FLAC, and OggPCM. Ogg XIPH reference: https://xiph.org/ogg/doc/rfc3533.txt
'There is no evidence this specification is recommended by any European Member State. GITB TDL reference: https://www.itb.ec.europa.eu/docs/tdl/latest/introduction/index.html#introduction'
There are many free online tools that validate the conformity of TIFF/IT files. They show possible errors and warnings regarding ISO compliance, some example: DPF Manager: http://dpfmanager.org/ IBM TIFF Validation: https://www.ibm.com/support/knowledgecenter/SSRH46_3.0.0/chqizvctifval.html
'The XACML specification is mentioned in the DSSC catalogue as a Data Sovereignty and Trust standard. This catalogue can be useful for expert groups working on technical building blocks for choosing the recommended standards and reference implementations in the Technical Specifications of the BBs, or other users. DSSC catalogue: https://dssc.eu/space/SE1/185794711 /Data+Sovereignty+and+Trust+standards+and+technologies+landscape'
'There has been found few academic papers addressing the effectiveness and efficiency of E-ARK tools. One of them describes It describes E-ARK eco-system, analysing the E-ARK Specifications for Common Information Package, and shows some success stories from its implementation. Metadata profiles for interoperability : the E-ARK specifications for e-archiving: https://www.torrossa.com/it/resources/an/5004900'
'There are existing documentation and studies proposing the usage of ODRL as an efficient method for representing more fine-grained access policies for Linked Data. Moreover, there are studies that also checked the completion of the specification and its actual implementation and providing other formal semantics to improve the application of the specification and its purpose. Defining Expressive Access Policies for Linked Data using the ODRL Ontology 2.0: https://www.researchgate.net/profile/Simon-Steyskal/publication/266652655_Defining_expressive_access_policies_for_linked_data_using_the_ODRL_ontology_20/links/565dc7a408aeafc2aac88d98/Defining-expressive-access-policies-for-linked-data-using-the-ODRL-ontology20.pdf Formalising ODRL Semantics using Web Ontologies: https://www.researchgate.net/publication/235902060_Formalising_ODRL_Semantics_using_Web_Ontologies'
The purpose of XSD 1.1 is not related to delivery of multilingual European public services. Therefore this criterion is considered not applicable to this specification.
'AMQP specification demonstrates technology-agnostic characteristics as it is designed to function independently of specific technologies, ensuring reliable information exchange between parties across diverse systems. OASIS AMQP Reference: http://docs.oasis-open.org/amqp/core/v1.0/amqp-core-complete-v1.0.pdf'
'DQV provides a standardised vocabulary for describing data quality information, including dimensions, metrics, indicators, and constraints. By adopting DQV, organisations can ensure consistency and interoperability in how data quality is represented and communicated. This standardised approach enables the reuse of quality-related information across different datasets, systems, and applications. Data Quality Vocabulary: https://www.w3.org/TR/vocab-dqv/'
'SOAP 1.2 specification does allow for partial implementation to a certain extent. It defines a core set of features that must be supported by all conforming SOAP implementations. These core features include the SOAP envelope structure, the processing model, and the SOAP encoding rules. It also defines additional capabilities that a SOAP node may support, such as message transmission optimization, reliable messaging, or security features. SOAP modules, on the other hand, define sets of related features that can be grouped together. SOAP Reference: https://www.w3.org/TR/soap12/ '
The Core Location Vocabulary has a good market acceptance for its use in the development of products and services. For example, it has been used to create the OSLO Vocabulary which is a simplified, reusable and extensible data model that captures the fundamental characteristics of information exchanged by public administration in Flanders. OSLO Vocabulary: https://joinup.ec.europa.eu/collection/oslo-open-standards-local-administrations-flanders/solution/oslo-open-standards-linked-administrations-flanders/about CLV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-location-vocabulary
FTPS does not define a cross-sector reusable data model, but defines a network protocol for exchange data. FTPS IETF reference: https://tools.ietf.org/html/rfc4217
The CPOV eases the description and publication of datasets including information of different public organisations, their services and responsibilities. These descriptions are done using human and redeable formats which ease the reusability and the information exchange across-borders. CPOV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-organisation-vocabulary 5-star linked open data: https://www.w3.org/DesignIssues/LinkedData.html
'Core Public Organisation Vocabulary facilitates the information sharing. The trustworthy data depends on the publisher, but Public administrations can complement CPOV with other specifications added to ensure secure data exchange. CPOV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-organisation-vocabulary'
As one of the official European Standardisation Organisation, ETSI develops standards that are compliant with the European Standardisation Regulation 1025/2012 . See: https://www.etsi.org/about/etsi-in-europe
'While SCIM itself is not designed for exposing interfaces to access public administration services, identity management plays a crucial role in various service-oriented systems, including those in public administration. SCIM can be a component of a broader identity and access management (IdAM) strategy within public administration, ensuring efficient and secure management of user identities across different systems. SCIM: https://scim.cloud/'
SOAP 1.2 is a messaging protocol for exchanging information in a structured way, it provides endpoints that foster the availability of interfaces containing data from internal information systems of a public administration. See: https://www.ibm.com/support/knowledgecenter/en/SSAW57_8.5.5/com.ibm.websphere.nd.multiplatform.doc/ae/cwbs_soapverdiffs.html
The purpose of RDF is not related to organisational interoperability. Therefore, this criterion is not applicable to the specification.
'YAML is not specifically designed for the long-term preservation of data, information, or electronic records. One of its functions is to transmit and store data in a human-readable and easy-to-write format. However, organizations can leverage YAML in conjunction with other practices to contribute to the long-term preservation of relevant information. For example, it is possible to store and transmit python objects using YAML format. YAML specification: https://yaml.org/spec/1.2.2/ Pythonforbeginners reference: https://www.pythonforbeginners.com/basics/convert-python-dictionary-to-yaml#htoc-what-is-the-yaml-format'
'There can be found many assessments that confirm the usefulness of the OAS. In terms of effectiveness, there are articles analysing OAS for security design issues, or others that prove the effectiveness of the automatic generation of test cases for REST APIs using OAS. Analyzing OpenAPI Specifications for Security Design Issues: https://ieeexplore.ieee.org/abstract/document/9652639 Automatic Generation of Test Cases for REST APIs: A Specification-Based Approach: https://ieeexplore.ieee.org/abstract/document/8536162 OAS specification: https://spec.openapis.org/oas/latest.html#openapi-specification'
'The Core Public Organisation Vocabulary facilitates information sharing between governments, businesses, and citizens. The CPOV contributes to the managment of cross-border repositories of public services and organisations. So, it fosters data portability between systems and applications supporting the implementation and evolution of European public services. CPOV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-organisation-vocabulary'
'The specification purpose is to enable communications over the Internet. IPv6 is the new version of IPv4 which is a widely used protocol, thus it is not dependent of any specific technology. Consequently, the adoption of IPv6 does not hamper the interoperability. IPv6 IETF: https://www.rfc-editor.org/rfc/rfc2460'
'This Core Vocabulary helps public administration with the publication of datasets that includes criteria and evidence. So, it is aligned with the principles of Linked Open Data. Core Criterion and Core Evidence Vocabulary reference (v1.0.0): https://joinup.ec.europa.eu/release/core-criterion-and-core-evidence-vocabulary-v100 5-star linked open data: https://www.w3.org/DesignIssues/LinkedData.html'
JSON sector agnostic specification that can be reused in any business domain requiring a common format to exchange data between different programs.
'When comparing SOAP architectures with RESTful architectures, SOAP provides more built-in features and standards for modeling and executing complex business processes. When it comes to modeling and executing complex business processes with built-in features and standards, SOAP architectures provide a more comprehensive and established framework. RESTful architectures, while suitable for simpler interactions and resource-based APIs, may require additional layers or tools to achieve the same level of process modeling and orchestration capabilities. SOAP Reference: https://www.w3.org/TR/soap12/ Difference between SOAP and REST: https://aws.amazon.com/compare/the-difference-between-soap-rest/?nc1=h_ls'
'JSON is already associated with EIRA ABBs in the EIRA Library Of Specifications (ELIS). Specifically, JSON can define the interoperability aspects of the "Machine to machine interface" ABB of the EIRA Technical View, the "Data Quality Service" and "Data Quality Component" of the EIRA Technical Application view, the "Legal Act Representation" , "Representation" and "Open Data" of the EIRA Semantic view. ELIS reference: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/v501 '
Like all the IETF standards, SMTP is a free and open technical specification, built on IETF standards and licenses from the Open Web Foundation. SMTP is therefore licensed on a royalty-free basis. Intellectual Property Rights in IETF: https://tools.ietf.org/html/rfc3668
The Zaragoza's city council is using HTML5 to developments services in an independent way from the platform used by the citzens. See: https://www.w3.org/2012/12/html5-cr.html.en
'Specification has the support of many communities listed in the following link as "Supporting Organizations", including Universities, private and public companies. However, there are not any community sharing data and results on national platforms. Portal ETSI reference: https:// portal.etsi.org/webapp/workprogram/Report_WorkItem.asp?WKI_ID=56725'
'The IPv6 specification is mentioned in the "Commission Implementing Decision of 3 April 2014 on the identification of ICT technical specifications eligible for referencing in public procurement". In this decision, the IPv6 specification is set as one of the ICT technical specifications that may be eligible for referencing in public procurement. "Commission Implementing Decision of 3 April 2014 on the identification of ICT technical specifications eligible for referencing in public procurement" reference: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32014D0188'
'DPV is a Core Vocabulary, and as such, the specification enables data portability and the transmission of personal data in an interoperable way. Personal data and open data are compatible in the sense that users can decide where to store their data and what use this data might have. DPV specification: https://w3c.github.io/dpv/primer/ '
'There are several studies assessing ShEx effectiveness when it comes to modelling and validating RDF graphs. An interesting study assesses the effectivenes of ShEx when describing and validating FHIR (Fast Healthcare Interoperability Resources) RDF data; pointing out the benefits of using ShEx RDF validator. Modeling and validating HL7 FHIR profiles using semantic web Shape Expressions (ShEx): https://www.sciencedirect.com/science/article/pii/S1532046417300345 Using Shape Expressions (ShEx) to Share RDF Data Models and to Guide Curation with Rigorous Validation: https://link.springer.com/chapter/10.1007/978-3-030-21348-0_39 '
'Advanced Encryption Standard is already associated to EIRA ABBs in the EIRA Library of Interoperability Specifications (ELIS). More specifically, Advanced Encryption Standard can define the interoperability aspects of the "Integrity Verification" ABB of the EIRA Technical View. EIRA Library of Interoperability Specifications (ELIS): https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/v610 AES Standard Reference: https://csrc.nist.gov/pubs/fips/197/final'
'Assessments of the efficiency of genericode primarily involve evaluating the performance, scalability, and practicality of implementations. For instance, a 2017-paper related to identification of further research fields related to the combination of standardised and regulatory data pools with public data feeds in financial data mentions that genericode is one of the 5 aggregated standards chosen by the Frankfurt Group Technical Workshop (FGTW) on Data Standards Interoperability in this matter. Overview of international experiences with data standards and identifiers applicable for big data analysis: https://files.stample.com/stample-1587417530204-ifcb44c.pdf '
'The implementation of the E-ARK CSIP guidelines can contribute to the simplification of public services delivery by improving information management, interoperability between information sharing systems, and by laying the basis for the long-term preservation and reuse of data within public administration, a clear example of its implementation in European Public Services is the CEF eArchiving solution. E-ARK CSIP specification: https://earkcsip.dilcis.eu/#introduction CEF eArchiving: https://joinup.ec.europa.eu/collection/egovernment/solution/cef-earchiving/about'
'The Better Regulation Guidelines and Toolbox does not contemplate data integrity measures as an element to define regulatory elements. Therefore, the criterion is not applicable. Better Regulation Guidelines and Toolbox reference: https://commission.europa.eu/law/law-making-process/better-regulation/better-regulation-guidelines-and-toolbox_en Better Regulation Toolbox reference: https://commission.europa.eu/document/download/9c8d2189-8abd-4f29-84e9-abc843cc68e0_en?filename=BR%20toolbox%20-%20Jul%202023%20-%20FINAL.pdf'
After being evaluated compliant with the regulation on standardisation 1025/2012, CSV has been identified by Commission Implementing Decision. See: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en
'The Better Regulation Guidelines and Toolbox fosters the secure and trustworthy data exchange between citizens, businesses and public administrations by proposing methods to ensure that ICT systems and solutions developed under the scope of public services in the EU include security regarding personal data exchanged between parties. In this sense, the Tool 28 covers this element extensively. Better Regulation Guidelines and Toolbox reference: https://commission.europa.eu/law/law-making-process/better-regulation/better-regulation-guidelines-and-toolbox_en Better Regulation Toolbox reference: https://commission.europa.eu/document/download/9c8d2189-8abd-4f29-84e9-abc843cc68e0_en?filename=BR%20toolbox%20-%20Jul%202023%20-%20FINAL.pdf'
'By allowing the authentication for using services SAML 2.0 can contribute and promote the visibility of administrations by simplifying access to administrations’ services. Moreover, it can be used internally by public officers which enhances the decision-making process, but it is not its main purpose. SAML 2.0 Reference: http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-tech-overview-2.0.html'
The purpose of HTML is not related to the availability of interfaces with internal information systems. Therefore, this criterion is not applicable to this specification. HTML W3C reference: https://www.w3.org/TR/html401/
After checking the different standard catalogues at supra-national level, there is no evidence of the inclusion of OWL2 within any European catalogue of standards. ICT technical specifications: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en CEN search tool catalogue: https://standards.cen.eu/dyn/www/f?p=CENWEB:105::RESET:::: CENELEC search tool catalogue: https://www.cenelec.eu/dyn/www/f?p=104:107:0::::FSP_LANG_ID:25
'ETSI TS 119 612 is part of the Electronic Signatures Infrastructure (ESI) family of specifications. The ESI dates back to 2012, when the General Policy Requirements for Trust Service Providers supporting Electronic Signatures (ETSI EN 319 401) specification was first issued. Since its first publication, there have been many extensions one of which is ETSI TS 119 612, whose version 2.2.1 was released in 2016 when the eIDAS regulation identified the need to create protocols to develop preservation services for trust service providers, as mentioned in ETSI SR 019 510. ESI specification history: https://standards.globalspec.com/std/14387016/EN%20319%20401 ETSI TS 119 612 specification: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf ETSI EN 319 401 specification: https://www.etsi.org/deliver/etsi_en/319400_319499/319401/02.03.01_60/en_319401v020301p.pdf ETSI SR 019 510 specification reference: https://www.etsi.org/deliver/etsi_sr/019500_019599/019510/01.01.01_60/sr_019510v010101p.pdf eIDAS blog, New APIs for the eIDAS-Ecosystem: https://blog.eid.as/tag/etsi-ts-119-512-en/'
'IEEE Std 802.3-2022 is widely accepted and used globally across various industries. It ensures interoperability among different vendors’ equipment, crucial for seamless technology integration. Ongoing reports and projects highlight its future-proof nature and continuous evolution. IEEE Std 802.3-2022 Reports and Projects: https://mentor.ieee.org/802-ec/dcn/24/ec-24-0045-00-00EC-ieee-802-3-ethernet-working-group-march-2024-closing-report.pdf IEEE Std 802.3-2022 Reference: https://ieeexplore.ieee.org/document/9844436'
'Although it is mostly suited for public administrations, ETSI TS 119 512 protocols can be used in any business domain. For example, the specification uses different preservation schemes that build the so called preservation profiles (see eIDAS reference). ETSI TS 119 511 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119511/01.01.01_60/ts_119511v010101p.pdf eIDAS blog, New APIs for the eIDAS-Ecosystem: https://blog.eid.as/tag/etsi-ts-119-512-en/'
"NUTS was originally created to be used in a statistical environment and its field of application is not expected to change in the short term. However, NUTS could be used 'as-is' to other domains, in the sense that territorial divisions are also interesting in other statistical research areas like tourism (see NUTS tourism-application reference), and not only limited to the fields of policy and demography. EUROSTAT reference, NUTS Principles and Characteristics section: https://ec.europa.eu/eurostat/web/nuts/principles-and-characteristics NUTS tourism-application reference: https://journals.sagepub.com/doi/abs/10.1177/0047287520979673"
'The specification is more towards semantic interoperability and does not adress UX and data representation layers.'
"There are assessment evaluating the specification's efficiency, such as the LEOS tool, which uses AKN4EU proving that the specification can be efficient. LEOS Tool Reference: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/solution/eif-toolbox/solution-leos-software-components-under-eupl"
'The Better Regulation Guidelines and Toolbox fosters the secure and trustworthy data exchange between citizens, businesses and public administrations by proposing methods to ensure that ICT systems and solutions developed under the scope of public services in the EU include security regarding personal data exchanged between parties. In particular this can be seen on the tool 55 (horizontal matters) on the toolbox. Better Regulation Guidelines and Toolbox reference: https://commission.europa.eu/law/law-making-process/better-regulation/better-regulation-guidelines-and-toolbox_en Better Regulation Toolbox reference: https://commission.europa.eu/document/download/9c8d2189-8abd-4f29-84e9-abc843cc68e0_en?filename=BR%20toolbox%20-%20Jul%202023%20-%20FINAL.pdf'
'The effectiveness of the SCIM (System for Cross-domain Identity Management) specification is typically assessed based on its adoption, implementation, and how well it meets the identity management needs of organizations. For instance, a 2023 paper by the Institute of Electrical and Electronics Engineering (IEEE) highlights how SCIM is a relevant industry standard for Identity and Access Management (IdAM) and how Role-Based Access Control (RBAC) can fix some some opening points encountered in SCIM implementations. SCIM: Survey and Enhancement With RBAC: https://ieeexplore.ieee.org/abstract/document/10214272'
'ebXML is included in 2 national catalogues of recommended specifications. They belong to Germany and Norway. The National Interoperability Framework (NIF) of these Member States varies when aligned with the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. While Norway performs well above the EU average, Germany shows an imbalanced level of implementation of the EIF Principles due the absence of data on this respect. Catalogue reference Germany: https://www.cio.bund.de/Web/DE/Architekturen-und-Standards/SAGA/SAGA%205-aktuelle%20Version /saga_5_aktuelle_version_node.html Catalogue reference Norway: https://www.difi.no/fagomrader-og-tjenester/digitalisering-og-samordning/standarder NIFO factsheets: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public- administration-factsheets-2021'
As XML is used to encode all communications all over the internet, XSD fosters the visibility and comprehensibility of administrations by providing validation of exchanged data.
The adoption of XAdES as an electronic signature format helps citizens, business and administrations to secure documents. So it does not hamper the scalability of systems. XAdES ISO reference: https://www.iso.org/standard/56025.html XAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/101900_101999/101903/01.04.02_60/ts_101903v010402p.pdf
'LDAP is maintained and developed by IETF which is an international community developing open standards. In addition, the OpenLDAP Foundation is another community centered around the distribution and maintenance of the open source version of the specification. Developer community IETF: https://www.ietf.org/about/ OpenLDAP website: https://www.openldap.org/'
DCAT, as a data vocabulary, can be used for large amounts of data and does not hamper the scalability of systems using it. It is evidenced by the several implementations at the national or European level. See: https://www.w3.org/2011/gld/wiki/DCAT_Implementations
ASiC Baseline profile is a specification that defines a set of features needed for the successful creation of containers containing data and information related to eSignatures. The specification performance is closely related to the different specifications involved in electronic signatures across borders. (E.g. CAdEs Baseline Profile, XAdES Baseline Profile). In the context of the European internal market, it can be considered as an asset for the creation of solutions enhancing the interoperability between administrations and businesses when eSignature is needed.
'UBL is highly adaptable to the business-specific needs, allowing for partial implementations depending on the requirements of any particular context where it is to be applied. UBL v2.3 reference: http://docs.oasis-open.org/ubl/os-UBL-2.3/UBL-2.3.html'
Like other vocabularies, ADMS reuses components from other vocabularies. (e.g. foaf, dcat), and also the resource Description Framework (RDF). This causes a dependency that can hamper the interoperability in those cases where new releases of the reused vocabularies are not backward compatible. ADMS Specification W3C: https://www.w3.org/TR/vocab-adms/
'The DNS over HTTPS (DoH) protocol itself is language-agnostic, and its functionality is not dependent on the language used for communication. Additionally, the User-Agent and Accept-Language request header fields often convey specific information about the client version or locale but, these aspects are typically addressed at the application layer rather than in the DoH protocol itself. DoH specification: https://datatracker.ietf.org/doc/html/rfc8484'
'ODRL can contribute to managing digital rights in certain contexts, nonetheless, its impact on the simplification of delivering European public services is indirect and dependent on how it is integrated into specific systems and use cases. The broader landscape of standards, regulations, and user experience considerations will also play significant roles in the overall delivery of public services. W3C specification reference: https://www.w3.org/TR/odrl-vocab/#vocab-core'
'The purpose of OCSP is not related to the allowance of extensions. OCSP reference: https://datatracker.ietf.org/doc/html/rfc2560'
'While the ESPD does not directly ensure or enable data processing accuracy, it includes features that can help to improve the accuracy of the data collected and processed in a public procurement process. The responsibility for ensuring data processing accuracy ultimately rests with the supplier and the contracting authority. Moreover, the ESPD model provides descriptions and suggests which data is relevant to suppliers of data. Commission Decision (EU, Euratom) 2017/46 of 10 January 2017 on the security of communication and information systems in the European Commission: https://eur-lex.europa.eu/legal-content/EN/TXT/?qid=1548093747090&uri=CELEX:32017D0046 ESPD business handbook: https://docs.ted.europa.eu/ESPD-EDM/latest/xml_business_handbook.html'
"TLS 1.3 requires the use of symmetric encryption algorithms. These algorithms produce an authentication tag alongside encrypted data, which the receiving peer uses to verify the data's integrity. TLS 1.3 Record Payload Protection Reference: https://www.rfc-editor.org/rfc/rfc8446.html#section-5.2"
'ebXML RegRep is data preservation enabler. Specifically, the specification stores and indexes any type of electronic content and preserves it as defined in the ebXML Part 1 on the ebRIM (see ebXML Part 1 reference). ebXML reference: http://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html ebXML Part 1 reference: http://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-rim-v4.0-os.html#__RefHeading__39647_1821683062'
'As a specification that aim to allow and stablish exchange of documents, MIME can be used for the exchange of documents solving administrative burden. Additionally, it can avoid the exchange of non-digital documents that are generally a source of administrative burden. MIME specification: https://tools.ietf.org/html/rfc2045'
The purpose of XAdES is not related to the publication of public data as linked open data. Therefore, this criterion is not applicable to this specification. 5-star linked open data: https://www.w3.org/DesignIssues/LinkedData.html XAdES ISO reference: https://www.iso.org/standard/56025.html XAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/101900_101999/101903/01.04.02_60/ts_101903v010402p.pdf
"ETSI TS 119 432 was part of ENISA's 2018 Trust Services Forum. The European Union Agency for Cybersecurity (ENISA) is the Union's agency dedicated to achieving a high common level of cybersecurity across Europe.ENISA contributes to EU cyber policy, enhances the trustworthiness of ICT products, services and processes with cybersecurity certification schemes, cooperates with Member States and EU bodies, and helps Europe prepare for the cyber challenges of tomorrow. ENISA ETSI ESI and Signature Validation Services: https://www.enisa.europa.eu/events/tsforum-caday-2018/presentations/C03_Rock.pdf"
'The provisions for the use of different languages in the ESPD are described in Article 61 of Directive 2014/24 /EU on public procurement. According to this article, contracting authorities must ensure that all procurement related documents, including the tender documents and the contract, are available in the official language(s) of the member state where the procurement is taking place. Directive 2014/24/EU: https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=CELEX:32014L0024 ESPD business handbook: https://docs.ted.europa.eu/ESPD-EDM/latest/xml_business_handbook.html'
ASiC Baseline Profile is a business sector agnostic specification which is reusable beyond the domain for which it was developed. Specifically, it can be implemented whether electronic signatures are needed even it is focused on implementations within the European internal market.
'The NFVI specification, as a sum of hardware and software components that builds up a virtual environment, reduces the dependency on dedicated infrastructure, and therefore enables for customisation. ISG NFV Deliver, Terminology for main concepts: https://www.etsi.org/deliver/etsi_gr/NFV/001_099/003/01.06.01_60/'
CSV is one of the most used formats. It can be concluded that accomplishes the user needs.
'The specification is associated with EIRA ABB's in the EIRA Library of Interoperability Specifications (ELIS). More specifically, the specification uses the ABB's "Data Quality Component" and "Data Quality Service". ELIS link: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /solution/elis/release/v110'
'ISO 639-2 is included in 3 national catalogues of recommended specifications. They belong to Ireland, Norway and Spain. The National Interoperability Framework (NIF) of these Member States varies when aligned with the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets.For both Norway and Spain, interoperability has a high performance in all the interoperability layers. In the case of Ireland, there is a need of improvement in Interopearability Governance, the Legal and Organisational layers. National catalogue Ireland: https://data.gov.ie/pages/opendatatechnicalframework#recommended-standards-for-open-data National catalogue Norway: https://www.digdir.no/samhandling/verktoy-og-ressurser-digitalisering/2150 National catalogue Spain: https://administracionelectronica.gob.es/pae_Home/pae_Estrategias/pae_Interoperabilidad_Inicio/pae_Normas_tecnicas_de_interoperabilidad.html#CATALOGOESTANDARES'
'While ISO/IEC 7498:1 may not directly address data protection, the specification can be part of a broader IT infrastructure that, when implemented and managed in accordance with applicable standards and regulations, contributes to a secure and reliable network environment for the handling of personal data by public administrations. ISO/IEC 7498:1: https://www.iso.org/standard/20269.html'
'FTP has been widely used for the exchange of data in the past years and has been supported for long time by most of the web browsers. However, there are other FTP alternatives, such as SFTP and HTTPS, that are highly recommended as they are much easier to configure, as well as additional network protocols, such as AS2, that are also potencial replacements of the FTP specification. Five Alternatives to FTP - Secure File Transfers: https://pro2col.com/blog/five-alternatives-to-ftp-secure-file-transfers FTP Specification Reference: https://datatracker.ietf.org/doc/html/rfc959'
'ADMS does not directly help with the provision of application programming interfaces (APIs) or Web services. However, the specification allows to provide of a standardised description for assets in a repository. As well, it allows the discoverability of resources from a single access point. An example of this is the European platform, Joinup. ADMS on Joinup: https://joinup.ec.europa.eu/solution/asset-description-metadata-schema-adms/about ADMS Specification W3C: https://www.w3.org/TR/vocab-adms/'
FTP is developed and maintained by IETF, a widely recognised open international community developing standards to enhance the internet. See: https://www.ietf.org/
'The specification can be used as an annex in interoperability agreements. Through the use of XBRL GL Profiles, organisations that wish to interchange data can communicate and agree upon the scope, amount, and restrictions on the data to be interchanged and, where feasible, automate the evaluation of conformation and data quality being exchanged.'
'OAS has been proven very efficient when it comes to converting programming languages, as it is stated in the paper "From Open API to Semantic Specifications and Code Adapters", where OAS is tested for the conversion of a semantic OWL-S specification. From Open API to Semantic Specifications and Code Adapters: https://ieeexplore.ieee.org/abstract/document/8029798 OAS specification: https://spec.openapis.org/oas/latest.html#openapi-specification '
The purpose of EuroVoc is to allow the exchange of documents between systems and applications. EuroVoc webpage: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/eurovoc
After checking the different standard catalogues at supra-national level, there is no evidence of the inclusion of PNG within any European catalogue of standards. ICT technical specifications: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en CEN search tool catalogue: https://standards.cen.eu/dyn/www/f?p=CENWEB:105::RESET:::: CENELEC search tool catalogue: https://www.cenelec.eu/dyn/www/f?p=104:107:0::::FSP_LANG_ID:25
'The purpose of DAPS is not related to the delivery of multilingual public services. Therefore, this criterion is not applicable to this specification. DAPS: https://github.com/International-Data-Spaces-Association/IDS-G/tree/main/Components/IdentityProvider/DAPS'
SOAP 1.2 is publicly available for implementation and study for free on W3C's webpage. See: https://www.w3.org/TR/soap12/
'As Verifiable Credentials defines the standard way to present credentials/certificates on the internet in a common digital way, it ensures the availability of interfaces to these systems and the data they handle. In turn, interoperability facilitates the reuse of systems and data and enables these to be integrated into larger systems. Verifiable Credentials: https://www.w3.org/TR/vc-data-model/'
CAMSS Assessment of XML EIF Scenario v1.0.0
'There are already existing assessments assessing the efficiency and effectiveness of the ISO27001. An example of such assessment can be viewed on the following link. ISO/IEC 27001 assessment: https://www.researchgate.net/publication/286651142_Evaluating_the_Effectiveness_of_ISO_27001_2013_Based_on_Annex_A'
'The specification can address long-term preservation of electronic resources because XSD can contribute to metadata preservation following that XSD is an XML extension. XSD Reference: https://www.w3.org/TR/2012/REC-xmlschema11-1-20120405/'
The Standard for Public Code provides public organizations with a model for building their open source solutions to enable successful future reuse by similar public organizations in other places. Moreover, the standard also addressed the fact that the generated code needs to be published and documented enabling other implementations. Furthermore, its openness and wide scalability allow the creation of solutions focused on the creation and publication of Linked Open Data. This fact, however, is subjected to the aim of implementors and the development of the solutions. The specification is a mean to achieve the Linked Open Data but it does not imply de facto Linked Open Data when implementing it. The Standard for Public Code webpage: https://standard.publiccode.net/ 5-star linked open data: https://www.w3.org/DesignIssues/LinkedData.html
'The purpose of the NFVI specification is not related to the visibility of administrative procedures, rules data, and services. NFV reference: https://www.etsi.org/technologies/nfv/nfv'
'As defined on the OASIS ebXML Registry Technical Committee (TC), only TC members are involved in the development of the ebXML specification. External contribution to this committee is possible through open channels (see Mail Lists and Comments reference). OASIS ebXML Registry Technical Committee reference: https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=regrep Mail Lists and Comments reference: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=regrep#feedback'
'DAPS ensures data portability as it improves identity and access management to IDS. Only the needed attributes can be included in the DAT. This limits information leakage, so only needed attributes are communicated. Furthermore, baseline certificates can be issued to enable connector deployment in uncomplicated manner. DAPS: https://github.com/International-Data-Spaces-Association/IDS-G/tree/main/Components/IdentityProvider/DAPS'
The purpose of XAdES is not related to organisational interoperability. Therefore, this criterion is not applicable to the specification. XAdES ISO reference: https://www.iso.org/standard/56025.html XAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/101900_101999/101903/01.04.02_60/ts_101903v010402p.pdf
'Registered Organization Vocabulary helps to the exposure of interfaces to access the public administration's services by providing a structured vocabulary for describing organisations that have gained legal entity status through a formal registration process. Furthermore, the Registered Organization Vocabulary, despite not being maintained anymore, is still used by the Open Standards for Linking Organizations (OSLO), more concrete in the application profile of "Slimme Stadsdistributie". In the application profile previously mentioned an example, could be to access mobility permit data exposed by an administration and understand who is the "Registered Organisation" holding the permit is and what its "legal name" is simply by following the definitions provided by the profile and vocabularies thanks to the Registered Organization Vocabulary properties. Registered Organization Vocabulary reference: https://www.w3.org/TR/vocab-regorg/ OSLO Smart City Distribution - Application profile Reference: https://data.vlaanderen.be/doc/applicatieprofiel/slimme-stadsdistributie/'
'There have been found some studies assessing UTF-8 in terms of effectiveness. For example, ""A case study in SIMD text processing with parallel bit streams: UTF-8 to UTF-16 transcoding"" or a study on the influence of UTF coded data in HDB-3 operation efficiency. A case study in SIMD text processing with parallel bit streams: UTF-8 to UTF-16 transcoding: https://dl.acm.org/doi/abs/10.1145/1345206.1345222 Compatibility of UTF-8 Encoding System to HDB-3 Scrambling Method: https://koreascience.kr/article/JAKO201322045164159.page USING UTF-8 TO EXTRACT MAIN CONTENT OF RIGHT TO LEFT LANGUAGE WEB PAGES: https://d1wqtxts1xzle7.cloudfront.net/48691891/Using_UTF-8_to_Extract_Main_Content_of_R20160908-2680-142ekn6-libre.pdf?1473403996=&response-content-disposition=inline%3B+filename%3DUsing_UTF_8_to_Extract_Main_Content_of_R.pdf&Expires=1681810571&Signature=L81oWxuCSbKBEjZutRFI60cE2AZQIrVRvVOOwZRL~RqRBiljibUAzXWYjJ7PhUPmI4FQmeotkmYICafh0fwP8pzSbXoaPjxgXFeiM9OaDqjcQS42K~acPonBHCWwQv~bx3HkpbnBjygdTUyxfLBTuXVsoKy997PH5gxPDklji-c1ML7uiPEkCyeKesaVDaRbxoGOVqoaBAEBhopXSRXx2hV0pREbuIjoUZ2HMB~QYCx8DG7iE1rm1V~nogGMPnZCVzBafoWs2ZbYvyVChU15f0eHI7mXuqwibzLmMAwNGAxRYPr~EQpOsYvEJKBWEN-XPG~PO7iz9njPWt8KqLa5PQ__&Key-Pair-Id=APKAJLOHF5GGSLRBV4ZA" '
There are several conformance validators for ODF, for example, The Document Foundation validator. The Document Foundation ODF Validator: https://odfvalidator.org/
'TSP can be partially implemented depending on specific needs and constraints of a system. It is flexible enough to be used in scenarios where only certain aspects of transaction management require timestamp-based ordering, allowing for tailored applications that address specific concurrency or consistency issues without fully implementing the protocol across all system operations. TSP IETF reference: https://tools.ietf.org/html/rfc3161 Weisser Zwerg implementations reference: https://weisser-zwerg.dev/posts/trusted_timestamping/#free-implementations'
IPsec is used by the TESTA project, which provides a secure cross-border data communication network service for public administrations. EuroDomain, the TESTA building block that allows data transfer and services between TESTA stakeholders, implements IPsec to enhance security settings in order to prevent eavesdropping and to enable encryption mechanisms. See: https://ec.europa.eu/idabc/en/document/2097.html
"XSD 1.1 is supporting the second level of maturity of Tim Berners-Lee's 5-stars schema for open data. It eases the availability of the data and structures XML files. Additionally, XSD 1.1 is implied within the RDF 1.1 XML Syntax, used for the serialisation of RDF documents as XML. Therefore, XSD fosters the publication of data as Linked Open Data. Moreover, although XSD is not related directly with Open Vocabularies, it can be found included within the Linked Open Vocabularies. It is possible because datatypes defined by XSD are commonly used as rdfs:range by properties. Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/en RDF Syntax Grammar Reference: https://www.w3.org/TR/rdf-syntax-grammar/ XSD Reference: https://www.w3.org/TR/2012/REC-xmlschema11-1-20120405/"
'The E-ARK CSIP specification is not related to te provision of access control mechanisms. Therefore, this criterion is not applicable to the specification. E-ARK CSIP specification: https://earkcsip.dilcis.eu/#introduction'
"The ISO 15000-3:2023 standard is protected by copyright, and its official version must be purchased from ISO or authorised bodies. While it can be implemented in systems, use of any embedded patents may require licensing under FRAND terms. Reproduction and distribution of the standard's content is restricted without permission. Thus, its application involves both access limitation and potential royalty considerations. ebXML RegRep OASIS reference: https://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html ebXML RegRep ISO reference: https://www.iso.org/standard/83479.html"
'The SMP 2.0 specification enables digital service delivery channels. By providing a standardized approach to service metadata publishing and discovery, the specification supports the integration and utilization of digital services across different platforms and channels. SMP OASIS reference: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505009'
The LegalDocML is XML base, which allow the estructuration of legal documents data and its exchange between systems. This can also be used for instance, in combination with the e-translation building block, to translate the content to other languages in the European Union. Then the collaboration between Member States can be improved using the method for the alignment of legal frameworks. LegalDocML reference: https://www.oasis-open.org/committees/legaldocml/charter.php
'Syslog can contribute to data portability between systems and applications supporting the implementation or evolution of European public services as it provides a standardized protocol for message logging, which is crucial in security and traceability matters. Syslog Protocol: https://datatracker.ietf.org/doc/html/rfc5424'
'Since the specification is focused on testing the Trusted Lists established on web services and their schema according to the requirements established in ETSI TS 119 612, the implementation and usage of the specification can increase the visibility and reliabilityof public organisations procedures and rules. ETSI TS 119 614-1 reference: https://www.etsi.org/deliver/etsi_ts/119600_119699/11961401/01.01.01_60/ts_11961401v010101p.pdf'
After checking the different standard catalogues at supra-national level, there is no evidence of the inclusion of HTML4 within any European catalogue of standards. ICT technical specifications: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en CEN search tool catalogue: https://standards.cen.eu/dyn/www/f?p=CENWEB:105::RESET:::: CENELEC search tool catalogue: https://www.cenelec.eu/dyn/www/f?p=104:107:0::::FSP_LANG_ID:25
'TGF is not tied to any specific software or operating system, given that it is intended to provide guidance and best practices for the delivery of government services. TGF specification: http://docs.oasis-open.org/tgf/TGF/v2.0/cs01/TGF-v2.0-cs01.html'
'TLS 1.3 specification does not directly address the long-term preservation of data, information, or knowledge, including electronic records. Therefore this criterion is not applicable to this specification. TLS 1.3 Reference: https://www.rfc-editor.org/rfc/rfc8446.html'
'SCIM is designed to facilitate the secure exchange of identity-related data between identity providers and service providers within an organization. While SCIM itself does not provide encryption or security mechanisms at the protocol level, it leverages underlying security features of the HTTP protocol and can be implemented in a secure manner. SCIM: https://scim.cloud/'
'UDDI organizes and exposes web service metadata but does not validate its accuracy. Ensuring data correctness in UDDI registries is the responsibility of the service providers who enter the information. UDDI supports service discoverability, not data validation. Security UDDI reference: https://www.ibm.com/docs/en/was/8.5.5?topic=curs-access-control-uddi-registry-interfaces'
The purpose of Data on the Web Best Practices is not related to the availability of interfaces with internal information systems. Therefore, this criterion is not applicable to this specification. W3C Reference: https://www.w3.org/TR/dwbp/
'There has not been found any Member State recommending ESPD, however, being a mandatory standard document needed for the delivery of e-procurement services. Public Procurement Directive 2014/24/EU: https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=CELEX:32014L0024 Commission Implementing Regulation (EU) 2016/7: https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=CELEX:32016R0007'
"The specification actively promotes and supports exposure of interfaces to access the public administration's services as it is completely aligned with eIDAS, a project that allows the European recognition of electronic identities, specifically, the acceptance of the electronic IDs in services of other European administrations as well as the identification of European citizens outside their home country. In addition, it also facilitates the connection of interfaces for trust service providers and to access digital services through authentication and authorisation mechanisms. ETSI TS 119 432: https://www.etsi.org/deliver/etsi_ts/119400_119499/119432/01.02.01_60/ts_119432v010201p.pdf eIDAS Regulation: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv%3AOJ.L_.2014.257.01.0073.01.ENG"
'GraphQL was open sourced by Facebook in 2015, and became a neutrally governed project managed by the Linux Foundation in 2019. In keeping with best practices, the technical governance of the GraphQL project is separate and distinct from the financial and policy governance of the GraphQL Foundation. The GraphQL project is chartered under the Joint Development Foundation (JDF). JDF is a part of the Linux Foundation family, and is an organization specifically dedicated to making open standards easier to manage. GraphQL foundation: https://graphql.org/foundation/join/ '
There are several documentation from European agencies on standardisation and cyber security about the possibilities and benefits of using SAMM as the bases to ensure the creation of secure services and software solutions. SAMM webpage: https://owaspsamm.org SAMM Documentation: https://github.com/OWASP/samm/blob/master/Supporting%20Resources/v2.0/OWASP-SAMM-v2.0.pdf ETSI SmartM2M; Security; Standards Landscape and best practices: https://www.etsi.org/deliver/etsi_tr/103500_103599/103533/01.01.01_60/tr_103533v010101p.pdf ENISA Advancing Software Security in the EU: https://www.enisa.europa.eu/publications/advancing-software-security-through-the-eu-certification-framework ENISA Good Practices for Security of IoT - Secure Software Development Lifecycle: https://www.enisa.europa.eu/publications/good-practices-for-security-of-iot-1
PM2 is a light and easy-to-implement methodology that project teams can tailor to their specific needs. PM2 incorporates elements from a wide range of globally accepted project management best practices, captured in standards and methodologies. Then, it can be said that OpenPM2 is a commonly accepted business process modelling specification. Moreover, it has been commonly used for the development of projects at European Institutions over time and with its openness, all interested groups can be involved in the development of projects and the design of business processes while doing them efficiently. OpenPM2 specification reference: https://op.europa.eu/en/publication-detail/-/publication/ac3e118a-cb6e-11e8-9424-01aa75ed71a1/language-en/format-PDF/source-83307127
'Currently there are no European open repository/catalogue of standards that include OpenTelemetry. OpenTelemetry: https://opentelemetry.netlify.app/docs/specs/otel/'
XHTML is maintained by W3C which is an international community developing open standards. Developer community W3C: https://www.w3.org/Consortium/
'UTF-8 can facilitate organizational interoperability agreements by enabling the exchange and processing of data in different languages or scripts. It can also help to promote the adoption of international standards or frameworks for interoperability, which can improve the compatibility and interoperability of different systems or organizations. UTF-8 specification: https://datatracker.ietf.org/doc/html/rfc3629'
'iCalendar is not included in any supra-national catalogue. Identification of ICT specifications: https://digital-strategy.ec.europa.eu/en/policies/identification-ict-specifications'
'One of the great advantages of using LDES is its flexibility. LDES can be easily customised and adapted to different contexts and applications. LDES specification: https://joinup.ec.europa.eu/collection/semic-support-centre/linked-data-event-streams-ldes'
'The specification is associated with EIRA ABB's in the EIRA Library of Interoperability Specifications (ELIS). More specifically, the specification uses the ABB's "Data Quality Component" and "Data Quality Service". ELIS link: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /solution/elis/release/v110 '
'The main purpose of the Indexed Database API is the storage of information. In this context, the specification is ideal for storing information locally and retrieving it when needed. In addition, the specification allows data to be stored permanently and deleted when it is unnecessary or no longer needed. Indexed Database API: https://www.w3.org/TR/IndexedDB/'
RPKI statements are published by network services of the Dutch Ministry of Justice and the Central Government See: https://rpki-validator.ripe.net/announcement-preview?asn=AS29311&prefix=2a04:9a04::%2F32 https://rpki-validator.ripe.net/announcement-preview?asn=AS41887&prefix=178.22.80.0%2F21
'The purpose of NUTS is not related to enabling digital service delivery channels. Therefore, this criterion does not apply to this specification. EUROSTAT reference, NUTS Principles and Characteristics section: https://ec.europa.eu/eurostat/web/nuts/principles-and-characteristics'
'LDAP provides communication between clients and AD, which means it is responsible for transporting highly sensitive information. For that matter LDAP can be developed to meet high performance security standards, including those related to data processing. An example for that could be the layer/transport layer security (SSL/TLS) encryption can add vital protection to information shared through LDAP and enhance the security of organizations’ communication channels. LDAP Authentication methods and security mechanisms: https://www.rfc-editor.org/rfc/rfc4513.txt '
The specification is involved in the creation of interoperable solutions for data exchange across borders, which aims to evolve public administrations to reduce administrative burdens meanwhile adapt to new ICT needs. CEF’s Building Blocks can be considered as innovative solutions in the field of eAdministrations and eGovernment, therefore, eDelivery SMP 1.10 fosters the creation of innovative solutions. See: https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/Background
'ETSI TS 119 612 is part of the Electronic Signatures and Infrastructure (ESI) family of specifications and is dependent on some of the protocols and semantics they convey, therefore, this specification is not technology agnostic. See Annex B for an example. ETSI TS 119 612 specification, page 52 Annex B: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf'
DCAT supports the evolution of European Public Services by enhancing the searchability and discoverability of datasets across borders. DCAT is an interoperability enabler. See: https://www.w3.org/TR/vocab-dcat-2/
'This Core Vocabulary is included in the Center for transfer of technology (CTT), in the Spanish ICT National Catalogue. ICT technical specifications: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en CEN search tool catalogue: https://standards.cen.eu/dyn/www/f?p=CENWEB:105::RESET:::: CENELEC search tool catalogue: https://www.cenelec.eu/dyn/www/f?p=104:107:0::::FSP_LANG_ID:25'
'The specification is designed to provide a standard way to represent legal documents in a machine-readable format. While the specification was initially developed for the legal domain, it is not limited to this domain and can be used in other domains as well. AKN4EU reference: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/akn4eu'
The specification does not define a cross-sector reusable data model. EuroVoc is a taxonomy created for helping the data processing across EU Administrations. Its use can be extended to external users and improves the searchability of information, but it is not a data model. EuroVoc webpage: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/eurovoc
UTF-8 is included in the catalogue of recommended specifications of 10 Member States. See CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standard
'The purpose of UDDI is not related to e-accessibility. Therefore this criterion is considered not applicable to this specification. UDDI OASIS reference: https://www.oasis-open.org/committees/uddi-spec/doc/spec/v3/uddi-v3.0.2-20041019.htm#_Toc85907967'
'ISO/IEC 19944-1 primarily provides a classification scheme for organizing and categorizing data within cloud computing environments, and it does not impose specific technology requirements or prescribe the use of particular technologies. ISO/IEC 19944-1 specification: https://www.iso.org/standard/60545.html'
'The implementation of SMP can ease the implementation of the Once-Only principle. Since the specification is related to ease the identification of services and the exchange of data, it can be useful for administrations to reuse and exchange information already available reducing the interactions that users need to do with them. SMP OASIS reference: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505009'
'The specification counts with some major releases, making visible that it has some wide-spread use that indicates market acceptance as they are working towards newer releases of the specification. AKN4EU reference: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/akn4eu '
The purpose of this Core Vocabulary is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification. CCCEV reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-criterion-and-core-evidence-vocabulary
'SCIM is not focused on enabling e-accessibility as it was designed to make identity management in cloud-based applications and services easier. SCIM: https://scim.cloud/'
Like all the IETF standards, TSP is a free and open technical specification, built on IETF standards and licenses from the Open Web Foundation. TSP is therefore licensed on a royalty-free basis. TSP IETF reference: https://tools.ietf.org/html/rfc3161
'The effectiveness of SAREF is often evaluated through various means, including practical implementations and pilot projects. For instance, a 2018-paper by the Ontology Engineering Group from Universidad Politécnica de Madrid asserts that the SAREF ontology represents a reference model for smart appliances, originally focused on the smart home domain and creates an extension for building devices as well as their location, which demonstrates the effectiveness of SAREF. Extending the SAREF ontology for building devices and topology: https://ceur-ws.org/Vol-2159/02paper.pdf'
'The OAIS reference model is designed to be a flexible and adaptable framework that can be used to support the long-term preservation and management of digital information in a wide range of contexts, including those that span multiple business domains and industries. OAIS specification: https://public.ccsds.org/Pubs/650x0m2.pdf'
"As it happens with all the e-Government Vocabularies, it has the SEMIC action from the ISA2 as responsible for the maintenance of the development. Additionally, there's a post on W3C in open government community group that talks about the specification. CPOV page on Joinup: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-organisation-vocabulary CPOV post in W3C: https://www.w3.org/community/opengov/2016/02/21/core-public-organisation-vocabulary/"
'UDDI has several authorization methods to protect data and information from unauthorised cahnges. UDDI security API ensure authorization trough authInfo element. Furthermore it is possible ensure authorization trough tModels representing authorization concepts. Authorization UDDI reference: http://www.uddi.org/pubs/uddi_v3.htm#_Ref8981734:~:text=the%20authorization%20policy.-,9.4.9%20Modeling%20Authorization,-A%20policy%20that'
'According to the SFIA licensing, public sector organisations can use SFIA on the same terms as the corporate user licence (SFIA reference, Choosing a licence). The SFIA Foundation ensures royalty-free basis under certain use cases, then the specification does not provide a royalty-free licence in most cases. SFIA reference, Choosing a licence: https://sfia-online.org/en/licensing-sfia/choosing-a-licence SFIA reference, Corporate user licence: https://sfia-online.org/en/licensing-sfia/corporate-user-licence'
'The ShEx Community Group is a group of developers tasked around the maitenance and evolution of the ShEx specification. This group also operates via Github, where anyone interested can raise issues and pull requests about its implementation. ShEx primer document: https://shexspec.github.io/primer/ ShEx Community Group: https://www.w3.org/community/shex/ ShEx Github: https://github.com/shexSpec/spec/issues'
CAdES Baseline profile is not defining a cross-sector reusable data model. The specification defines the requirements and conformance levels for AdES Signatures used across borders on digital communications or transactions.
The rules on European standardisation allow the European Commission to identify information and communication technology (ICT) technical specifications - that are not national, European or international standards - to be eligible for referencing in public procurement. This allows public authorities to make use of the full range of specifications when buying IT hardware, software and services, allowing for more competition in the field and reducing the risk of lock-in to proprietary systems. After being evaluated compliant with the regulation on standardisation 1025/2022, IPSec has been identified by Commission Implementing Decision. See: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en
'ETSI TS 119 512 is maintained by ETSI, one of the European agencies for standardisation. ETSI organisation: https://www.etsi.org/about ETSI TS 119 512 Working group: https://portal.etsi.org/webapp/workprogram/Report_WorkItem.asp?WKI_ID=61427'
'The purpose of ETSI TS 119 614-1 is not related to the reuse of information. Therefore this criterion is not applicable to this specification. ETSI TS 119 614-1 reference: https://www.etsi.org/deliver/etsi_ts/119600_119699/11961401/01.01.01_60/ts_11961401v010101p.pdf'
" LDES can be interpreted as a publishing strategy by which a data provider allows multiple third parties to stay in sync with the latest version of the data source in a resource and cost-effective manner. Thanks to this specification, the exposure of interfaces to access the public administration's services would improve. LDES specification: https://joinup.ec.europa.eu/collection/semic-support-centre/linked-data-event-streams-ldes"
'ISO 19941 is not included in any national catalogue of recommended specifications whose Member State NIF has a high performance on interoperability according to NIFO factsheets. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards'
'The specification does not specify whether the implementation can be or not partially done; howver, there are aspects that the specification can be used as a whole or partially. DCAT (v2.0.0) reference: https://www.w3.org/TR/vocab-dcat-2/ '
'The ODRL Information Model does not directly express sensitive personal information such as the identity of the existence of Assets containing such data related to Parties. However, ODRL vocabularies (such as the ODRL Common Vocabulary and ODRL Profiles) may define terms that may relate to personal information. These specifications should inform implementations that produce or consume such ODRL expressions to take steps to communicate to all relevant users the manner in which the policy is being used, the identity of any other party with whom that policy is being shared, and the reason the policy is being shared with other parties. SERAMIS: https://cordis.europa.eu/docs/projects/cnect/2/612052/080/deliverables/001-D55v4GDPR.pdf ODRL Information Model 2.2: https://www.w3.org/TR/odrl-model/#privacyConsiderations'
The purpose of JEPG is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification. JEPG ISO reference: https://www.iso.org/standard/18902.html JPEG public reference: https://jpeg.org/jpeg/
'The use of the ESPD in conjunction with other digital solutions and services can help to increase transparency and comprehensibility in public procurement processes. For example, e-procurement platforms and tools can provide a centralized location for publishing procurement-related information, such as contract notices, tender documents, and evaluation criteria, which can improve access to procurement-related data and services. ESPD Business handbook: https://docs.ted.europa.eu/ESPD-EDM/latest/xml_business_handbook.html'
'The message returned by a Service Metadata Publisher service is signed using one or more XML-Signatures. Moreover, the purpose of the specification is to ease and ensure the discoverability of different parties to exchange the desired information. The specification defines a set of requirements regarding the authentication of parties that ensures secure and trustworthy processing of data. SMP OASIS reference: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505009'
By providing necessary compliance requirements for the implementation of AdES signatures in the context of the European internal market, the selection and implementation of CAdES Baseline Profile does not hamper the interoperability of systems. In fact, it has been developed to ensure the interchange of digital documentation on electronic procedures and communications across borders.
The purpose of TSP is not related to organisational interoperability. Therefore, this criterion is not applicable to the specification. TSP IETF reference: https://tools.ietf.org/html/rfc3161
The purpose of PDF 1.7 is not related to the once-only principle. Therefore, this criterion is not applicable to the specification.
The fact that the specification has been adopted by different organisations demonstrates that the specification has sufficient completeness and consistency for the use and development of products and services. Additionally, the quality of the specification is evidenced by the fact that its underlying specifications are known, well adopted and stable exchange formats. This will allow further interoperability with systems implementing them.
CAMSS Assessment of ISO 7498-1 EIF Scenario v1.0.0
'The EIRA is maintained by the European Commission in an active manner, with teams working specifically on EIRA and related specifications such as eGovERA. This guarantees that the specification evolves as stakeholders and the interoperability environment detect new needs. The success stories of the Interoperability Architecture Solutions is a good example of how the Commission supports the evolution of the specification by providing assistance to stakeholders. From the collaborations between the EIRA and Member States, the specification evolves from real needs and expectations on Digital Public Service provision. EIRA reference: https://interoperable-europe.ec.europa.eu/collection/european-interoperability-reference-architecture-eira /solution/eira/release/610 EIRA Github Repository: https://github.com/CarTool-EC/EIRA Interoperability Architecture Solutions Success Stories: https://interoperable-europe.ec.europa.eu/collection/european-interoperability-reference-architecture-eira/success-stories'
'There are already existing studies and documents that evaluate and document the characteristics of the UDDI and provide possible improvements in its performance, among other aspects. In "Indexing traditional UDDI for efficient discovery of web services" it is proposed a framework which combine the traditional UDDI with search engines to get a more efficient web services discovery. And in "Binding Now or Binding Later" various "UDDI modes of operation are evaluated using performance tests of the UDDI's implementations", to obtain the most efficient use of UDDI in different cases. "Indexing traditional UDDI for efficient discovery of web services" reference: https://www.researchgate.net/publication/303921682_INDEXING_TRADITIONAL_UDDI_FOR_EFFICIENT_DISCOVERY_OF_WEB_SERVICES "Binding Now or Binding Later" reference: https://www.academia.edu/14435163/Binding_now_or_binding_later_The_performance_of_UDDI_registries'
'Currently OpenTelemetry has not been selected for its use in any European Cross-border project/initiative yet. OpenTelemetry: https://opentelemetry.netlify.app/docs/specs/otel/'
The specification is included within the EIRA Interoperability Specification Library (ELIS) listed as a possible specification to be used for implementing two of EIRA's ABBs. Also, IETF 3161 Time Stamp Protocol (TSP) is considered as the basis of the European Standard Electronic Signatures and Infrastructures (ESI); Time-stamping protocol and time-stamp token profiles from ETSI. Within the document, it is recognised as the basis to which ETSI standard applied constraints. ETSI Catalogue: https://www.etsi.org/standards-search#Pre-defined%20Collections ETSI EN 319 422: Electronic Signatures and Infrastructures (ESI); Time-stamping protocol and time-stamp token profiles
'Information about the three versions of the SHACL specification is provided on the W3C website. Additional details can be found on the W3C GitHub and other GitHub pages that assess the SHACL specification. Furthermore, SHACL has integrated some parts of the SPARQL 1.1 specification, showcasing its richness through detailed documentation and even mentioning a SPARQL implementation. All information about SHACL, including documentation and references to SPARQL and RDF specifications, has been published by the W3C organisation. sparql should be only a proof of richness of shacl since it publish detailed documentation and goes even further by mentioning a sparql implementation. SHACL github W3C reference: https://w3c.github.io/data-shapes/shacl/ SHACL W3C reference: https://www.w3.org/TR/shacl/'
'EuroVoc is published by the Publications Office of the EU so, all major and minor releases foresee a public review. Nonetheless, collected feedback is not publicly visible. EU Vocabularies Releases: https://op.europa.eu/en/web/eu-vocabularies/releases EuroVoc: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource /dataset/eurovoc'
Although XHTML's purpose is not to foster the delivery of multilingual European public services, several websites contain multilingual parallel texts and are developed in XHTML. In the following link, there is an explanation of the architecture of multilingual websites. Open architecture for multilingual websites: http://dragoman.org/mws/oamws.pdf XHTML W3C reference: https://www.w3.org/TR/xhtml1/
'The rules on European standardisation allow the European Commission to identify information and communication technology (ICT) technical specifications - that are not national, European or international standards - to be eligible for referencing in public procurement. This allows public authorities to make use of the full range of specifications when buying IT hardware, software and services, allowing for more competition in the field and reducing the risk of lock-in to proprietary systems. After being evaluated compliant with the regulation on standardisation 1025/2012, FTP has been identified by Commission Implementing Decision and included in the European list of ICT Standards for e-procurement. FTP Specification Reference: https://datatracker.ietf.org/doc/html/rfc959'
The purpose of TLS 1.2 is not related to the availability of interfaces. Therefore this criterion is considered not applicable specification.
'ETSI EN 319 422 can be found on the specifications and standards repository of its own standards development organization, the European Telecommunication Standards Institute (ETSI). ETSI Standards Repository Search: https://www.etsi.org/standards#page=1&search=ETSI%20TS%20319%20422&title=1&etsiNumber=1&content=1&version=0&onApproval=1&published=1&historical=1&startDate=1988-01-15&endDate=2022-07-25&harmonized=0&keyword=&TB=&stdType=&frequency=&mandate=&collection=&sort=1'
The purpose of this Core Vocabulary is not related to the modelling of organisational interoperability aspects. Therefore, this criterion is not applicable to the specification. CPSV-AP reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-service-vocabulary-application-profile
'For TLS 1.3 to function correctly, it is essential to include a core set of mandatory components to ensure proper operation and avoid interoperability issues. Specifically, a TLS 1.3 compliant application must implement the TLS_AES_128_GCM_SHA256 cipher suite. While TLS 1.3 allows for extensibility with optional features, omitting these fundamental requirements, including the mandatory cipher suite, can result in a partial implementation likely to encounter client/server connection failures and communication issues with other compliant systems. TLS 1.3 Partial implementations Reference : https://www.rfc-editor.org/rfc/rfc8446.html#section-9.1 '
The purpose of XML is not related to the delivery of multilingual public services. Therefore, this criterion is not applicable to the specification.
HTTP is already associated to an EIRA ABB in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, HTTP can define the interoperability aspects of the "Network Service", "Network Component" "Private Network" and "Public Network" ABBs of the EIRA Technical View. See: https://joinup.ec.europa.eu/solution/elis/distribution/eliscataloguev100betaxlsx
'The purpose of OSI is not related to the restriction to data/information but there are agreements on security aspects that facilitates the restriction of access to data, but without providing specific requirements. OSI reference https://www.iso.org/standard/20269.html'
'TGF is designed to simplify the delivery of public services by promoting the use of digital technologies and best practices in government service delivery. The TGF emphasises the importance of creating user-centred digital solutions and services that are accessible, inclusive, and easy to use. TGF specification: http://docs.oasis-open.org/tgf/TGF/v2.0/cs01/TGF-v2.0-cs01.html'
'HTTP specification is designed for universal use across diverse business domains and is not limited to business-specific applications. Its open-ended nature, support for diverse data types, content negotiation capabilities, and efficient caching mechanisms make it a robust foundation for communication. HTTP /1.1 RFC 2616 Reference: https://www.rfc-editor.org/rfc/rfc2616.html'
The purpose of WS-BPEL is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification.
The purpose of MIME is not related to organisational interoperability. Therefore, this criterion is not applicable to the specification. MIME reference: https://tools.ietf.org/html/rfc2045
'The OData protocol provides support for both user and version-driven extensibility by means of different extension methods, through a combination of versioning, conventions and explicit extension points. OData reference on extensibility: https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#_Toc31358848'
There is no validation or conformance test for the implementation of CCCEV. CCCEV: https://joinup.ec.europa.eu/solution/core-criterion-and-core-evidence-vocabulary/about
RDF is maintained by W3C which is an international community developing open standards. See: https://www.w3.org/Consortium/ https://www.w3.org/TR/rdf11-primer/
"Genericode is maintained by the OASIS Code List Representation Technical Commitee (TC), which requires registration and membership approval. According to OASIS' guidelines for the TC process, members of OASIS Technical Commitees come together to develop specifications using their open process and IP policy. Even so, external contribution to this committee is possible through open channels. Technical Commitee (TC) Process: https://www.oasis-open.org/policies-guidelines/tc-process-2017-05-26/ OASIS Code list Representation TC: https://groups.oasis-open.org/communities/tc-community-home2?CommunityKey=7558fd85-f7ac-4dd7-b57b-018dc7d3f6f7"
CAMSS Assessment of ADMS EIF Scenario v1.0.0
'The efficiency of the ebXML specification has been assed by the Institute of Electrical and Electronics Engineers, dedicated to standardisation and development in technical areas. In the "ebXML and Web services" study, it is seen an overview of the ebXML and the Web services architecture (WSA) specifications. In this sense, it is also offered a comparision between both specifications. "ebXML and Web services" study: https://ieeexplore.ieee.org/abstract/document/1200304 ebXML RegRep OASIS reference: https://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html'
The purpose of the specification is not related to the availability and comprehensibility of public administrations data.
'At the time of elaborating this assessment, FTP does not foster the creation of innovative solutions. Since its development in 1971, it has been used in combination with other specifications in order to enhance security (e.g. TLS & SSL). However, there are other FTP alternatives, such as SFTP and HTTPS, that are highly recommended as they are much easier to configure. Five Alternatives to FTP - Secure File Transfers: https://pro2col.com/blog/five-alternatives-to-ftp-secure-file-transfers Securing FTP with TLS Reference: https://datatracker.ietf.org/doc/html/rfc4217 FTP Specification Reference: https://datatracker.ietf.org/doc/html/rfc959'
By ensuring that XML files are well formed and valid, XSD fosters the digital exchange of information between administrations and stakeholders. At the same time, it avoid the non-digital information exchange helping to the reduction of administrative burdens.
5 Member States are recommending PDF/A in their ICT National Catalogues. This Member States are Estonia, Germany, Spain, Sweden and UK. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
XACML is available for its study and use at OASIS’s webpage. Therefore it can be reused by the organisations, administrations, open communities, etc. that developed it. XACML OASIS reference: http://docs.oasis-open.org/xacml/3.0/errata01/xacml-3.0-core-spec-errata01.html
'After checking the different standard catalogues at supra-national level, there is no mention of SFIA in any official document stating its conformance in regards to Regulation 1025/2012. ICT technical specifications: https://ec.europa.eu/growth/single-market/european-standards/ict-standardisation/ict-technicalspecifications_en CENELEC and CEN search tool catalogue:https://standards.cencenelec.eu/dyn/www/f?p=CEN:105::RESET::::'
The purpose of PAdES is to foster the use of electronic signature. Therefore, it is clear that it reduces the administrative burden by making signing possible electronically. PAdES ISO reference: https://www.iso.org/standard/67937.html PAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/102700_102799/10277801/01.01.01_60/ts_10277801v010101p.pdf
RegOrg is not included in any Member States' catalogues of recommended specifications. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'The main purpose of ETSI TS 119 432 is to provide the means for a secure and trustworthy exchange of data through digital signatures. Digital Signature Values (DSV) are created using a signing key held within a cryptographic security module named Signature Creation Device (SCDev) operated by a Signature Creation Service Provider (SCSP). ETSI TS 119 432: https://www.etsi.org/deliver/etsi_ts/119400_119499/119432/01.02.01_60/ts_119432v010201p.pdf'
'ETSI TS 119 511 is a component derived from the actions implemented on the basis of the Regulation (EU) No 910/2014 of the European Parliament and of the Council of 23 July 2014 on electronic identification and trust services for electronic transactions in the internal market. The aim of this regulation is to enhance interoperability when it comes to e-signatures trust services of in the European context. Regulation (EU) No 910/2014 of the European Parliament and of the Council of 23 July 2014 on electronic identification and trust services for electronic transactions in the internal market: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv:OJ.L_.2014.257.01.0073.01.ENG ETSI TS 119 511 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119511/01.01.01_60/ts_119511v010101p.pdf'
'RDF is a business domain agnostic specification that can be used at any business domain requiring RDF features. RDF primer document: https://www.w3.org/TR/rdf11-primer/'
The purpose of IPSec is not related to organisational interoperability. Therefore, this criterion is not applicable to the specification.
There are several studies assessing SOAP 1.2 performance and features in terms of efficiency and efficacy. As REST and SOAP-based web services are living together nowadays, one of the topics is the performance comparison. Moreover, the comparison between different SOAP toolkits is an exploited topic. See: https://aaltodoc.aalto.fi/bitstream/handle/123456789/29224/master_Makkonen_Joni_2017.pdf?sequence=1&isAllowed=y https://dl.acm.org/citation.cfm?id=1033266
'CCCEV does not enforce the information carried in an Evidence to be directly accessible i.e. contained within the payload of the response. Core Criterion and Core Evidence Vocabulary reference (v1.0.0): https://joinup.ec.europa.eu/release/core-criterion-and-core-evidence-vocabulary-v100 '
'The purpose of PROV is not related to access control mechanisms. Therefore this criterion is not applicable to the specification. PROV Primer document: https://www.w3.org/TR/prov-primer/ PROV Ontology: https://www.w3.org/TR/2013/REC-prov-o-20130430/ PROV Data Model: https://www.w3.org/TR/2013/REC-prov-dm-20130430/'
'The ETSI EN 319 401 specification, which is complementary to ETSI TS 119 512, defines a mechanism to guarantee the that only authorised persons can make entries and changes to the stored data. Using this mechanism, data changes are limited to those who have permission to do so, therefore, it guarantees data integrity. ETSI TS 119 512: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.01_60/ts_119512v010101p.pdf ETSI EN 319 401: https://www.etsi.org/deliver/etsi_en/319400_319499/319401/02.03.01_60/en_319401v020301p.pdf'
'The Extensible Forms Description Language (XFDL) specification plays a role in some niche software, used to create digital signatures or legally binding forms. Although it is used in niche software, it is domain-agnostic and can be implemented in any domain. XFDL specification domain-agnostic reference: https://amazingalgorithms.com/definitions/extensible-forms-description-language/ Extensible Forms Description Language reference: https://www.w3.org/TR/NOTE-XFDL'
CSV is one of the most popular formats for publishing data on the web. An example of those developments is CSV Dialect which aims to deal with a reasonably large subset of the features which differ between dialect. Add history, structured data, support from wide range of organisations (private and public) See: https://frictionlessdata.io/specs/csv-dialect/
Xforms 2.0 can be used independently of any other technical specifications or operating system. However, Xforms is based on XML, so it can be dependent on conventions and rules for the correct XML usage. Xforms 2.0 W3C reference: https://www.w3.org/community/xformsusers/wiki/XForms_2.0
'The purpose of SHACL is not related to the delivery of multilingual services. Therefore this criterion is not applicable to this specification. SHACL W3C reference: https://www.w3.org/TR/shacl/'
CAdES as an electronic signature will proportionate a secure and trustworthy eSignature for the data exchange between citizens and administrations. CAdES ISO reference: https://www.iso.org/standard/64756.html CAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/101700_101799/101733/02.01.01_60/ts_101733v020101p.pdf
The rules on European standardisation allow the European Commission to identify information and communication technology (ICT) technical specifications - that are not national, European or international standards - to be eligible for referencing in public procurement. This allows public authorities to make use of the full range of specifications when buying IT hardware, software and services, allowing for more competition in the field and reducing the risk of lock-in to proprietary systems. After being evaluated compliant with the regulation on standardisation 1025/2012, TLS 1.2 has been identified by Commission Implementing Decision. See: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en
'At the moment of performing the assessment, no initiative at national or European level has been found to use ADMS to cover privacy aspects. ADMS Specification W3C: https://www.w3.org/TR/vocab-adms/'
'DPV is independent of any specification and can be implemented without any dependency on platforms. DPV specification: https://w3c.github.io/dpv/primer/ '
'Although it is mostly suited for public administrations, ETSI TS 119 512 protocols can be used in any business domains. For example, the specification uses different preservation schemes that build the so-called preservation profiles (see eIDAS reference) ETSI TS 119 512 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.02_60/ts_119512v010102p.pdf eIDAS blog, New APIs for the eIDAS-Ecosystem: https://blog.eid.as/tag/etsi-ts-119-512-en/'
"DNS is a de-facto standard. It's extensive use as an enabler of the Internet can be summarised by the DNS4EU initiative. DNS Domain Names: https://datatracker.ietf.org/doc/html/rfc8499 DNS - implementation and specification: https://tools.ietf.org/html/1035 DNS4EU initiative https://www.joindns4.eu/"
'The TrainingDML-AI Standard is primarily design for geospatial machine learning training data. While it facilitates the development and deployment of AI/ML applications within the geospatial realm, it alsoi mprovides valuable guidelines applicable across various industries. These guidelines can enhance data management and AI/ML model development practices beyond the geospatial domain. OGC TrainingDML-AI Standard: https://docs.ogc.org/is/23-008r3/23-008r3.html'
'Verifiable Credentials is included in the Rolling Plan for ICT standardisation regarding electronic identification and trust services including e-signatures. Rolling Plan for ICT Standardisation: https://joinup.ec.europa.eu/collection/rolling-plan-ict-standardisation/electronic-identification-and-trust-services-including-e-signatures'
'The specification is domain-agnostic, its main purpose has to do with document exchange and therefore can be used in either public administrations or any other kind of organization. ETSI EN 319 532-3 reference: https://www.etsi.org/deliver/etsi_en/319500_319599/31953203/01.02.01_60/en_31953203v010201p.pdf'
'The NFV distribution has been included in several European projects. NFV offers virtualised network environments, dynamically configurable and fully automated, that automatically respond to the needs of the traffic and services running on it. This is the reason why the NFVI component has been included in last European projects such as T-NOVA, or in ongoing ones such as the 5G network deployment in the Digital Single Market. NFV reference: https://www.etsi.org/technologies/nfv/nfv T-NOVA reference: http://www.t-nova.eu/ 5G roll plan reference: https://joinup.ec.europa.eu/collection/rolling-plan-ict-standardisation/5g 5G NFV whipe paper: http://portal.etsi.org/NFV/NFV_White_Paper_5G.pdf'
'No member state has been found including the Open Systems Interconnection (OSI) in its national catalogue of recommended specifications. CAMSS list of standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
'The purpose of OGC TrainingDML-AI is not related to e-accessibility. Therefore, this criterion is considered not applicable to this specification. OGC TrainingDML-AI Standard: https://docs.ogc.org/is/23-008r3/23-008r3.html'
'XSD provides schemas for the validation of XML and the proper data exchange by means of it. Therefore, by ensuring the well formation and validity of the documents being exchanged, XSD fosters the data portability between systems and administrations across borders. XSD Reference: https://www.w3.org/TR/2012/REC-xmlschema11-1-20120405/'
As a document exchange format, SVG is a valuable tool for sharing information through the internet between administrations and stakeholders. Allowing sharing data and information the standard fosters the visibility of administration data and services. Fostering the collaboration between public administrations, the specification eases the decision-making process of institutions. SVG W3C reference: https://www.w3.org/TR/SVG11/
"BFO's aim is to provide a foundation for further developments of ontologies or other external resources. BFO reference: https://www.iso.org/standard/74572.html"
'There are existing studies assessing the efficiency of DNS. Particularly, there seems to be a general interest on the efficiency of DNS security extension mechanisms, and on the DNS Tunneling tools. Exploring Domain Name-Based Features on the Effectiveness of DNS Caching: https://ccronline.sigcomm.org/wp-content/uploads/2017/01/p36-hao.pdf A Comparative Performance Evaluation of DNS Tunneling Tools: https://www.researchgate.net/profile/Alessio_Merlo/publication/221271469_A_Comparative_Performance_Evaluation_of_DNS_Tunneling_Tools/links/00b4951c1e5065b0e6000000/A-Comparative-Performance-Evaluation-of-DNS-Tunneling-Tools.pdf Performance assessment and analysis ofDNS tunneling tools: https://www.researchgate.net/publication/235996771_Performance_assessment_and_analysis_of_DNS_tunneling_tools A survey of domain name system vulnerabilities and attacks: https://www.researchgate.net/publication/345017736_A_survey_of_domain_name_system_vulnerabilities_and_attacks'
'ETSI TS 119 512 is part of the Electronic Signatures and Infrastructure (ESI) family of specifications, and it is dependent on some of their protocols and semantics they convey; therefore, this specification is not technology agnostic. ETSI TS 119 512 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.02_60/ts_119512v010102p.pdf'
RDF has been selected within several initiatives at European level in order to provide open data and linked data to be used for Member States, citizens, and businesses. An example of RDF use is the European cross-border project ESCO (European Skills, Competences, Qualifications, and Occupations). The project uses Turtle extension of RDF in order to make available the project's data. At ESCO's webpage can be found the link to data resources and as well as information resources needed for the proper use of provided data. Additionally, RDF has been selected as one of the core elements on the euCASES project, a platform for linking legal documentation and offer it as Linked Open Data. See: https://ec.europa.eu/esco/portal/escopedia/RDF http://eucases.eu/start.html
'The specification is designed to be implemented in any domain, as it can describe any web resource and its not related to any specific domain. DCMI About: https://www.dublincore.org/about/ Dublin Core Application Profile: https://www.dublincore.org/blog/2011/application_profile/ '
'ETSI TS 119 612 is a component derived from the actions implemented based on the Regulation (EU) No 910/2014 of the European Parliament and of the Council of 23 July 2014 on electronic identification and trust services for electronic transactions in the internal market. This regulation aims to enhance interoperability when it comes to the trust services of e-signatures in the European context. Regulation (EU) No 910/2014 of the European Parliament and of the Council of 23 July 2014 on electronic identification and trust services for electronic transactions in the internal market: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv:OJ.L_.2014.257.01.0073.01.ENG ETSI TS 119 612: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf'
PAdEs and PAdES Baseline profile are included in the ETSI’s catalogue of standards. As ETSI is considered an official standardisation organisation, it can be considered that the specifications are included in a supra-national catalogue. See: https://www.etsi.org/deliver/etsi_ts/103100_103199/103172/02.02.02_60/ts_103172v020202p.pdf https://www.etsi.org/standards
'XBRL International and the community around it provides support for the specification. National XBRL organisations provide support to members. https://www.xbrl.org/guidance/'
' No evidence nor disclosures have been found in the specification regarding fostering or harming the long-term preservation of information. ETSI TS 119 614-1 reference: https://www.etsi.org/deliver/etsi_ts/119600_119699/11961401/01.01.01_60/ts_11961401v010101p.pdf'
No Member State includes ODRL in their national catalogue with The National Interoperability Framework (NIF) aligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards NIFO: https://ec.europa.eu/isa2/solutions/nifo_en
The purpose of CAdES is not related to the availability of interfaces with internal information systems. Therefore, this criterion is not applicable to this specification. CAdES ISO reference: https://www.iso.org/standard/64756.html CAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/101700_101799/101733/02.01.01_60/ts_101733v020101p.pdf
'Implementation of OAIS can be carried out under any combination of operating system and underlying processor architecture. Therefore, the specification is platform-agnostic. OAIS specification: https://public.ccsds.org/Pubs/650x0m2.pdf'
'SAREF is designed to support the reuse of relevant information when needed. The principle of reuse and alignment of concepts and relationships are embedded in SAREF, contributing to the ability to reuse information effectively across different contexts and applications within the domain of smart appliances and the Internet of Things (IoT). SAREF: https://saref.etsi.org/core/v3.1.1/ '
The purpose of LegalRuleML is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification. LegalRuleML reference: http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/legalruleml-core-spec-v1.0.html
'The use of genericode, a standardised format for representing code lists and controlled values, can contribute to simplifying the delivery of European public services by providing a common format for representing code lists, which improves standardisation so that public administrations can establish clear data governance policies and procedures. Code List Representation (genericode): https://docs.oasis-open.org/codelist/genericode/v1.0/os/genericode-v1.0-os.html'
"Schema.org, as a cross-border and cross-sector vocabulary, increases government-to-government reuse of data and therefore can prevent citizens or businesses from providing information multiple times. According to the Publications Office (OP) of the EU, as a mark-up schema, the specification may boost governmental data reuse helping to achieve the once-only principle in future releases of DCAT-AP, once this schema is mapped to schema.org which will result in the Schema.org profile of DCAT-AP (DCAT-AP-SDO). OP reference, 'DCAT-AP standard can become a tool for internal information governance purposes' section: https://ec.europa.eu/isa2/dcat-ap-key-european-data-publishers-reach-data-consumers-and-create-european-open-data-ecosystem_en DCAT-AP-SDO reference: https://ec-jrc.github.io/dcat-ap-to-schema-org/"
'The effectiveness of LDES is often evaluated through various means, including practical implementations and pilot projects. A 2021-paper for the International Conference on Web Engineering (ICWE) introduces the concept of a Linked Data Event Stream (LDES) for publishing base registries like air quality sensors and observations or a registry of officially registered addresses, which demonstrates the effectiveness of LDES. Publishing Base Registries as Linked Data Event Streams: https://link.springer.com/chapter/10.1007/978-3-030-74296-6_3'
WSDL helps to make administrations and stakeholders' web services available, with information related to them and endpoints that ease the consumption. This fact supports the reuse of data and web services avoiding administration and stakeholders to carry out unnecessary steps or transactions.
The main purpose of RegOrg is to capture the typical details recorded by business registers and thereby facilitate information exchange between them. So it facilitates the visibility of the different legal entities' data, including public administrations. RegOrg about Joinup reference: https://joinup.ec.europa.eu/solution/registered-organization-vocabulary/about
WSDL is available for free at W3C's webpage and administrations and organisations are free to use or implement. See: https://www.w3.org/TR/wsdl20/
'The ETSI and any of its committees, in charge of the development of ETSI TS 119 511, operates under the ETSI Intellectual Property Rigths (IPRs) and IPR Policy. The specification is licensed on a (F)RAND basis. ETSI ownership of IPRs section: https://www.etsi.org/intellectual-property-rights'
'AMQP Working Group is part of the OASIS consortium and is responsible for maintaining and evolving the AMQP specification. They provide resources and forums for developers and organizations to collaborate and share their experiences. AMQP Working Group Reference: https://www.amqp.org/product/different'
'The specification is related to being usable beyond business-specific domains as it can describe any web resource. The specification makes use of extension vocabularies that broaden the field of applicability of the Dublin Core Ontology, also known as DCAM. DCMI About: https://www.dublincore.org/about/ Dublin Core Application Profile: https://www.dublincore.org/blog/2011/application_profile/'
'SCIM is designed to be flexible, and it does allow for partial implementations. SCIM defines a set of core features, including the ability to create, read, update, and delete user identities and their associated attributes. Additionally, it supports features like filtering, sorting, and pagination for querying user information. However, not all features need to be implemented for a system to claim SCIM compliance. SCIM: https://scim.cloud/'
'The implementation of the specification is still underway in Finland and Estonia. The mandate for the use of XBRL GL by all companies with any significant sales in Turkey is an indication of the impact on ERP developers for those enterprises to implement XBRL GL in their systems. Estonia: https://ec.europa.eu/digital-building-blocks/wikis/display/CEFDIGITAL/2021/03/22/eInvoicing+helping+standardise+transactional+data+in+Estonia Turkey: https://www.ifrs.org/content/dam/ifrs/publications/jurisdictions/filing-profiles/turkey-18-november-2015.pdf https://www.edefter.gov.tr/edeftermevzuat.html '
'ELI (European Legislation Identifier) is designed to be platform-agnostic. This means that it is intended to work independently of specific computing platforms or environments. ELI is formulated to be flexible and adaptable across various technology platforms, ensuring compatibility and interoperability regardless of the underlying infrastructure. This platform-agnostic approach enables ELI to be implemented and integrated into different systems and applications without being constrained by the specifics of a particular platform. ELI reference: https://eur-lex.europa.eu/eli-register/about.html'
The specification is independent of any software or platform. The Core Location Vocabulary can be used by any organisation. CLV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-location-vocabulary
'XHTML specification itself does not directly provide built-in mechanisms for restricting access to information or data. Therefore, this criterion is not applicable to the specification. XHTML W3C reference: https://www.w3.org/TR/xhtml1/'
'The main goal of DPV is to develop a taxonomy of privacy terms, which include in particular terms from the new European General Data Protection Regulation (GDPR) in order to ease proof of compliance with the GDPR and related privacy protection regulations. DPV specification: https://w3c.github.io/dpv/ DPV primer document: https://w3c.github.io/dpv/primer/#introduction'
"There are existing documentation and studies assessing and analysing the performance and effectiveness of IPsec in different contexts and application areas. For instance ENISA provides documentation recommending the use of IPsec in order to improve security. Semantics Scholar, TCP/UDP network performance evaluation of various IPSEC algorithms: https://pdfs.semanticscholar.org/8971/9848f632259138d5d4b1052ad24ede803625.pdf ENISA reference, 'Algorithms, Key Sizes and Parameters Report' document: https://www.enisa.europa.eu/publications/algorithms-key-sizes-and-parameters-report/at_download/fullReport ResearchGate, 'Interoperability Issues for VPN IPsec Solutions' document: https://www.researchgate.net/publication/228437109_Interoperability_Issues_for_VPN_IPsec_Solutions"
'XBRL international supports the above by national and international communities to further develop and support the implementation of the specification. e.g. https://fi.xbrl.org/, https://www.xbrl.org/tag/spain/ XBRL GL provides a standardized toolset for the broad adoption of relevant data standardization, but the developers recognized that local extensions and variations will be necessary. Under the auspices of local XBRL jurisdictions or other organizations, further standardization leveraging XBRL GL are expected, encouraged and facilitated. http://www.xbrl.org/int/gl/2015-03-25/GLTFTA-REC-2015-03-25.html#section-how-to-create-extensions-within-the-gl-taxonomy-framework '
DNS is publicly available for implementation and use, and therefore for everyone to study, for free on IETF's webpage. See: https://tools.ietf.org/html/1034 https://tools.ietf.org/html/1035
After being evaluated compliant with the regulation on standardisation 1025/2012, IPv6 has been identified by Commission Implementing Decision and included in the European list of ICT Standards for e-procurement. See: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en
'TrainingDML-AI does not directly facilitate the publication of the data on the web but it is used to train, validate, and test AI/ML models defining a UML model and encodings consistent with the OGC Standards baseline to exchange and retrieve the training data in the Web environment. Nonetheless, we consider this criterion is not applicable to the specification. TrainingDML-AI OGC reference: https://docs.ogc.org/is/23-008r3/23-008r3.html#_ba9834c4-89de-4391-8aba-042e48d74fa1'
"There is no evidence of any study directly assessing the efficiency of the EN 303 645 specification. However, there are some organisations from the private sector, offering solutions based on the specification's performance with respect to the market, that indirectly assess the specification's efficiency. It is the case of TÜV SÜD, which offers testing against the EN 303 645 specification. TÜV SÜD-EN 303 645 reference: https://www.tuvsud.com/en-us/industries/consumer-products-and-retail/iot-cybersecurity/"
'As defined by the OASIS Technical Commitee (TC), the Oasis Code List Representation TC is involved in the release lifecycle of the specification publicly and external contribution to this committee is possible through open channels like mailing lists. OASIS and the Code List Representation TC welcome comments at any time, not just during public review cycles and they may be submitted to the TC by any person through the use of the OASIS TC Comment Facility. OASIS Code list Representation TC: https://groups.oasis-open.org/communities/tc-community-home2?CommunityKey=7558fd85-f7ac-4dd7-b57b-018dc7d3f6f7'
There is a validatoin tool available within the ELI online documentation site. ELI validator: https://webgate.ec.europa.eu/eli-validator/
'There are existing documentation and studies assessing the efficiency of IPv6. The "IPv4 and IPv6 Protocols: A Comparative Performance Study" aims to perform a comparative study on the performance of IPv4 and IPv6 on voice and video network traffic flow using performance metrics such as jitter, typo, and packet loss. "IPv4 and IPv6 Protocols: A Comparative Performance Study" reference: https://www.researchgate.net/publication/335863969_IPv4_and_IPv6_Protocols_A_Comparative_Performance_Study'
'TGF has not been found included in any repository/catalogue at European level. TGF Specification: http://docs.oasis-open.org/tgf/TGF/v2.0/cs01/TGF-v2.0-cs01.html'
PAdES Baseline profile provides four levels of conformance that are linked with different types of documents and their functional requirements. Each level of conformance is defining a profile, these profiles are listed from less specificity to the maximum level. Therefore, the specification can be implemented according to the necessities of users without hampering interoperability.
Even though ODRL is a powerful tool for public administrations and the development of valuable public services for citizens and bussiness, the specification does not impact positively the implementation of the once-only principle. W3C specification reference: https://www.w3.org/TR/odrl-vocab/#vocab-core
'Extensible Forms Description Language is not included in any national catalogue of recommended specifications whose Member State NIF has a high performance on interoperability according to NIFO factsheets. NIFO Factsheets: https://interoperable-europe.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public-administration-factsheets-2024 CAMSS list of standards: https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
5 Member States are recommending WS-Security in their ICT National Catalogues. See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
ADMS provides a standardised method for describing assets and their distributions. Therefore, while providing a common way and components for the metadata provision, it helps the comprehensibility of data and services of Public administrations across borders. ADMS on Joinup: https://joinup.ec.europa.eu/solution/asset-description-metadata-schema-adms/about ADMS Specification W3C: https://www.w3.org/TR/vocab-adms/
'A test suite for XSLT, containing over 11,000 test cases, is available. The metadata for each test case describes any dependencies on optional or implementation-defined features of the specification, and provides expected results for each test. Test Suite Page: https://dvcs.w3.org/hg/xslt30-test/'
'SAREF is designed to be compatible with a multilingual context to some extent. This specification allows the use of labels and annotations for concepts, properties, and individuals. These labels can be provided in multiple languages to support a multilingual environment. Implementers can use language tags or annotations to indicate the language of the labels. SAREF: https://saref.etsi.org/core/v3.1.1/ '
OpenPM2's purpose is to enable Project Managers (PMs) to deliver solutions and benefits to their organisations by effectively managing the entire lifecycle of their project. Besides, since it helps to deliver different solutions, it helps foster to the visibility of administrative data and to support the decision-making process. Therefore, by being involved in the quality assurance of projects and data generated, it can help to enhance the visibility of public data and services, and also helping the decision-making process. OpenPM2 specification reference: https://op.europa.eu/en/publication-detail/-/publication/ac3e118a-cb6e-11e8-9424-01aa75ed71a1/language-en/format-PDF/source-83307127
'OData builds incrementally. Customers can easily build a very basic standards-compliant service. Only additional work will be needed to support extra or or add-on capabilities. OData reference: https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#_Toc31358832'
'Web Services Description Language (WSDL) allows for extension through its extensibility mechanisms. The extensibility features of WSDL enable users to include additional information beyond the core elements defined by the standard. This extensibility is crucial for accommodating specific requirements, custom features, or domain-specific details that may not be covered by the standard WSDL elements. W3C WSDL specification: https://www.w3.org/TR/wsdl20/#extensions-and-modules'
'The purpose of SFIA is not related to the secure exchange of data. Therefore, this criterion does not apply to this specification. SFIA reference: https://sfia-online.org/en/sfia-8'
'HTTPS is included in 7 national catalogues of recommended specifications. They belong to Croatia, Cyprus, France, Germany, Greece, Portugal, and Sweden. CAMSS List of standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards National Catalogue of France: https://www.numerique.gouv.fr/uploads/Referentiel_General_Interoperabilite_V2.pdf'
WSDL is a markup language based on XML and uses some conventions, features, and constraints coming from it. Despite this, XML is widely adopted and well known and this fact allows to not hamper the interoperability. However, WSDL is involved in the SOAs implementation, along with UDDI and SOAP. In this performance, WSDL relies on SOAP to invoke services.
'XSLT can contribute to the reuse of information. However, this is a limited functionality since the specification only enables the reuse of some pieces of data be means of variables. XSLT Reference: https://www.w3.org/TR/xslt-30'
'Tools & Libraries for assessing the conformance of datasets with DCAT or its extensions have been developed by the community. DCAT Validator References: http://www.dcat.be/validator/ https://www.npmjs.com/package/dcat-validator https://joinup.ec.europa.eu/solution/dcat-ap-validator '
"The purpose of Extensible Forms Description Language is not related to enabling the exposure of interfaces to access the public administration's services. Therefore this criterion is not applicable to the specification. Extensible Forms Description Language reference: https://www.w3.org/TR/NOTE-XFDL"
'OData offers a way to both break down data silos and increase the shared value of data. The specification contributes creating an ecosystem where data consumers and producers can interoperate more than ever, allowing more applications to make sense of a broader set of data and eases the delivery of European public services (see the Netherlands Advisory report stating the usability of OData as a solution to streamline the delivery of public services). Interoperable Europe Portal OASIS Open Data Protocol reference: https://interoperable-europe.ec.europa.eu/collection/ict-standards-procurement/solution/odp-oasis-open-data-protocol-odata-tc Netherlands OData Advisory report reference: https://www.forumstandaardisatie.nl/open-standaarden/odata '
UTF-8 supports many languages and can accommodate pages and forms in different cases including a mixture of these languages. The fact of allowing encoding with several languages allows the data consumption by the different linguistic groups that form the EU. Therefore, UTF-8 fosters the delivery of European multilingual services. See: https://www.w3.org/International/questions/qa-choosing-encodings.en
WS-BPEL is included in some national catalogues from Member States. A total of 3 countries listed the WS-BPEL within their national catalogues. They belong to Cyprus, France and Germany. See CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
TLS 1.2 is a protocol cryptographic protocol that provides end-to-end security of data sent between applications over the Internet. See: https://www.internetsociety.org/deploy360/tls/basics/
'By establishing constraints on the creation and exchange of XML documents XSD fosters the trustworthy data exchange between administrations and stakeholders. However, XSD does not include security features in itself. Despite this, XML includes several recommendations in order to ensure the security of data and users. XSD Reference: https://www.w3.org/TR/2012/REC-xmlschema11-1-20120405/ '
'Such as IPv6, which is an advanced version of IPv4, the core specification is not customisable. Despite this, there are aspects such as implementations that can be tailored to meet specific needs. IPv4 IETF: https://www.rfc-editor.org/rfc/rfc791'
'Indexed Database API is not included in any national catalogue of recommended specifications whose Member State NIF has a high performance on interoperability according to NIFO factsheets. NIFO Factsheets: https://interoperable-europe.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public-administration-factsheets-2024 CAMSS list of standards: https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
'DNS is included in 9 national catalogues of recommended specifications. Some of these catalogues are: France, Germany and Spain. The National Interoperability Framework of France, Germany and Spain is fully aligned with the 3 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. NIFO Factsheets France: https://joinup.ec.europa.eu/sites/default/files/inline-files/NIFO_2024%20DPAF_France_vFinal_rev.pdf NIFO Factsheets Germany: https://joinup.ec.europa.eu/sites/default/files/inline-files/NIFO_2024%20DPAF_Germany_vFinal.pdf NIFO Factsheets Spain: https://joinup.ec.europa.eu/sites/default/files/inline-files/NIFO_2024%20DPAF_Spain_vFINAL.pdf CAMSS list of standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
'W3C has a defined and publicly available Process for the Development and approval process of the specification as a recommended standard. Also, a clear Release Notes tracking the changes of the different versions is archived. W3C Process document: https://www.w3.org/2018/Process-20180201/#Policies '
HTML is a markup language to develop web resources to share content. By allowing to exchange data via online websites, HTML fosters the secure and trustworthy data exchange between administrations and stakeholders. HTML W3C reference: https://www.w3.org/TR/html401/
'The ebXML specification can prevent unauthorised data access by establishing authorisation and authentication mechanisms. As described in the Oracle document about security features,using these settings, organisations can ensure that data cannot be accessed by non-verified users, making it trustworthy and confidential. ebXML security: https://www.oracle.com/technical-resources/articles/enterprise-architecture/ebxml-security1.html ebXML RegRep OASIS reference: https://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html'
'OAS includes support for REST APIs. A RESTful API is a clear enabler of the exposure of interfaces, given that it performs information exchange with secure, reliable and efficient software communication standards. OAS specification: https://spec.openapis.org/oas/latest.html#openapi-specification OAS in Github: https://github.com/OAI/OpenAPI-Specification/#participation'
'IETF is a vendor neutral SDO. However, FTP relies on TCP to ensure that all data exchanged is sent correctly to the proper destination. FTP Specification Reference: https://tools.ietf.org/html/rfc959 Transmission Control Protocol (TCP) Reference: https://tools.ietf.org/html/rfc793'
XSLT is extensively supported in the web browsers and it helps to transform a wide number of formats including HTML, XSL, Formatting Objects, PDF, PostScript and PNG.
'WAI-ARIA is primarily focused on improving the accessibility of web content, especially for users with disabilities, by providing additional information about the semantics and behavior of user interface components in web applications. It is not designed as a tool for publishing or structuring open data in the way that formats like JSON, XML, or RDF are. However, improving accessibility can indirectly contribute to the openness and inclusivity of web content, which aligns with broader principles of open data. WAI-ARIA reference: https://www.w3.org/TR/wai-aria/ '
'SMP can be implemented in any platform, and it is independent of any technology. SMP OASIS reference: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505009'
By securing the communication through computer networks it allows the data exchange and information reuse between public administrations.
XAdES is independent of any software, hardware, or operating system. So it can be said that the specification is independent of any specific technology or platform. XAdES ISO reference: https://www.iso.org/standard/56025.html XAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/101900_101999/101903/01.04.02_60/ts_101903v010402p.pdf
'GITB TDL provides a framework for testing the efficient and secure exchange of information. See an example of this characteristics in the reference provided. GITB TDL example reference: WMS client request validation https://www.itb.ec.europa.eu/docs/tdl/latest/examples/index.html#example-6-wms-client-request-validation'
The ISO 14533-2:2012 which refers to XAdES is not available for free for everyone to study. Payment is needed to reach access to the standard. XAdES ISO reference: https://www.iso.org/standard/56025.html
CAMSS Assessment of DNS EIF Scenario v1.0.0
'There are already existing documents and studies about the XACML performance in different environments. An example of this is the research article "A Performance Analysis of the XACML Decision Process and the Impact of Caching", which analyses the performance of XACML involved in the decision process of web services developed in the cloud and the impact of caching. Also, there is an article focused on the testing of XACML policies, which provides different approaches to improve effectivity. A Performance Analysis of the XACML Decision Process and the Impact of Caching: https://www.researchgate.net/publication /283307011_A_Performance_Analysis_of_the_XACML_Decision_Process_and_the_Impact_of_Caching'
HTTPS is already associated to an EIRA ABB in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, HTTPS can define the interoperability aspects of the "Network Service", "Network Component" "Private Network" and "Public Network" ABBs of the EIRA Technical View. See: https://joinup.ec.europa.eu/solution/elis/distribution/eliscataloguev100betaxlsx
8 Member States are recommending XSD in their ICT National Catalogues. See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
TLS 1.3 offers better performance compared to earlier versions due to TLS false start and Zero Round Trip Time (0-RTT). These performance improvements are especially evident in browser traffic and less with server-server connection (ebMS). The biggest improvements are in the area of security, because a number of security risks are limited. This is because unsafe options from TLS 1.2 are excluded, SHA-1, RC4, DES, 3DES, AES-CBC and MD5, which reduces the chance of the protocol being configured in an unsafe manner. Configuration is also simpler, which means there is less chance of incorrect configuration
'E-ARK CSIP has not been found included in any initiative covering privacy aspects neither at national nor at European level. E-ARK CSIP specification: https://earkcsip.dilcis.eu/#introduction'
'The implementation of ISAE 3402 could, for example, allow administrations to properly track how the different organisations providing digital public services are distributing funds. Or also to ensure that the procedures and transactions with stakeholders are properly mapped. ISAE 3402 auditing tool, is designed to be used in any domain. ISAE 3402 handbook reference: https://www.ifac.org/system/files/downloads/b014-2010-iaasb-handbook-isae-3402.pdf'
The purpose of XACML is not related to data portability. Therefore, this criterion is not applicable to this specification. XACML OASIS reference: http://docs.oasis-open.org/xacml/3.0/errata01/xacml-3.0-core-spec-errata01.html
ODRL has been used in several use cases developed in the context of development of data protection related solutions as SPECIAL (Scalable Policy-aware Linked Data Architecture For Privacy, Transparency and Compliance), an H2020 European project which involves ODRL for compliance check. Approaches for GDPR compliance utilising Semantic Web: https://harshp.com/research/publications/035-representing-activities-processing-personal-data-consent-semweb-gdpr-compliance SPECIAL Deliverable: https://www.specialprivacy.eu/images/documents/SPECIAL_D17_M17_V10.pdf
'There are several existing mechanisms to assess JSON conformity. Different types of validators depending on users’ needs. TestBed JSON validation: https://www.itb.ec.europa.eu/docs/guides/latest/validatingJSON/index.html JSON Test suite in Github: https://github.com/nst/JSONTestSuite JSON Compare: https://jsoncompare.com/#!/simple/ JSON Formatter: https://jsonformatter.curiousconcept.com/ '
There are many documents and studies around the JPEG, functionalities, and effectiveness, and efficiency. An example of this is an article in The International society for optics and photonics. It is published in the SPIE Library, and it is about the evolution of the standard and the different capabilities of the specification in terms of image representation. SPIE Library: https://www.spiedigitallibrary.org/journals/journal-of-electronic-imaging/volume-27/issue-04/040901/JPEG-1-standard-25-years--past-present-and-future/10.1117/1.JEI.27.4.040901.full?SSO=1
CSV can be considered a facilitator to publish public administrations data as open data. As 5 Stars Open Data model of Tim Berners-Lee states, CSV makes sure content is available on the web, structures data and makes it usable in a non-proprietary open format. See: https://5stardata.info/en/
By helping administrations to access and reuse information across borders, the implementation of XHTML and other standards from HTML family can help to foster and ease the Once-Only Principle. XHTML W3C reference: https://www.w3.org/TR/xhtml1/
'REST enables digital service delivery channels by providing a widely-used architectural style designed for client-server applications. REST reference: https://restfulapi.net/'
'CPSV-AP is already associated to an EIRA ABB in the EIRA Library Of Specifications (ELIS) and so is the 3.1. Specifically, this Core Vocabulary can define the interoperability aspects of the ""Core Data Model"" and ""Data"" ABBs from the EIRA Semantic view. The specification covers Digital Public service Catalogue from the Organisational View, Controlled Vocabulary, Data, Data Model, Data Syntax, Forms Structure, Hash Code and Metadata from the Semantic View and API Discovery and Catalogue Service from the Technical View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/v501'
'TSA can be used to protect data using Time-Stamp Tokens and making documentation accessible only to certain requesters, who could be public administrations in this case. Therefore, TSP can help to ensure the protection of personal data managed by Pubic Administrations. TSP/TSA IETF reference: https://www.rfc-editor.org/rfc/rfc3161'
DCAT-AP, as a data vocabulary, can be used for large amounts of data and does not hamper the scalability of systems using it. It is evidenced by the several implementations at the national or European level. See: https://www.w3.org/2011/gld/wiki/DCAT_Implementations
'The effectiveness of HTTP has been shown through its evolution into HTTP/3. HTTP/3 improves speed and reliability by using modern transport protocols, addressing the limitations of earlier versions. These advancements show that HTTP continuously adapts to meet new technological and security demands, proving its lasting effectiveness. HTTP /1.1 RFC 2616 Reference: https://www.rfc-editor.org/rfc/rfc2616.html Measuring HTTP/3: Adoption and Performance: https://arxiv.org/pdf/2102.12358'
LDAP can be found for free along within the European Collaborative Platform, Joinup. LDAP in Joinup platform: https://joinup.ec.europa.eu/solution/lightweight-directory-access-protocol/distribution/rfc4511-lightweight-directory-access-protocol-ldap-protocol
XAdES (ISO 14533-2:2012) is already associated to an EIRA ABB in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, ISO 14533-2:2012 can define the interoperability aspects of the "e-Seal Preservation Service" and "e-Signature Preservation Service". Specifically, this Core Vocabulary can define the interoperability aspects of the Technical infrastructure view ABB from the EIRA Semantic view. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/solution/elis/release/v100
'There is no Member State recommending schema.org in its ICT National Catalogue. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
'OData services are used by a large community of users. These services use a common data model, which allows any client to interact with the service in a well-defined way (see OData reference). In this sense, the specification is domain-agnostic. For example, there are the Cambridge Weather-Pyslet demo service and the City of Medicine Hat Open Data Portal, in the field of academics and medicine, respectively. OData ecosystem, Live services reference: https://www.odata.org/ecosystem/ Cambridge Weather-Pyslet demo reference: https://github.com/OData/odataorg.github.io/blob/master/_ecosys/liveservices/Cambridge-Weather-Pyslet-demo-service.md Medicine Hat Open Data Portal: https://www.medicinehat.ca/en/home-property-and-utilities/mymh-portal.aspx OData reference: https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#_Toc31358832'
'MIME allows for customization through the creation of custom content types, headers, and encoding methods to adapt to specific requirements while following certain standards. MIME specification: https://tools.ietf.org/html/rfc2045'
'There is no evidence of the inclusion of SFIA in an open repository/catalogue of standards at European level. EUOS repository of standards: https://www.standict.eu/standards-repository CENELEC and CEN search tool catalogue: https://standards.cencenelec.eu/dyn/www/f?p=CEN:105::RESET::::'
'The purpose of UDDI is not related to long term preservation of electronic records. Therefore this criterion is considered not applicable to this specification. UDDI OASIS reference: https://www.oasis-open.org/standard/uddi/'
'There are numerous studies that have been conducted to evaluate the effectiveness of TLS 1.3, offering detailed insights into how this version addresses critical security challenges, optimises performance, and meets modern technological demands. TLS 1.3 in Practice: How TLS 1.3 Contributes to the Internet by Hyunwoo Lee, Doowon Kim, and Yonghwi Kwon: https://dl.acm.org/doi/fullHtml/10.1145/3442381.3450057 The Era of TLS 1.3: Measuring Deployment and Use with Active and Passive Methods by Ralph Holz, Johanna Amann, Abbas Razaghpanah, Narseo Vallina-Rodriguez: https://arxiv.org/abs/1907.12762 '
'There are several reports assessing how DCAT-AP is effective and efficient for the publication of open data. For example, the study of DCAT-AP representation of Czech National Open Data Catalog and its impact, or an assessment of the application of DCAT-AP in the European Data Portal. DCAT-AP Specification: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/dcat-application-profile-data-portals-europe/release/200 DCAT-AP representation of Czech National Open Data Catalog and its impact: https://www.sciencedirect.com/science/article/abs/pii/S1570826818300532 Linked Data in the European Data Portal: A Comprehensive Platform for Applying DCAT-AP: https://link.springer.com/chapter/10.1007/978-3-030-27325-5_15'
'OSI is a reference model that provides a common basis for the coordination of standards development for the purpose of systems interconnection. The OSI model has been included in the Interoperable Europe Portal catalogue of ICT standards, encouraging the creation of communities along with the sharing of their data and results as its purpose is to improve cloud computing portability and interoperability, thus improving communication between different actors. OSI reference https://www.iso.org/standard/20269.html'
'The specification of the Dataspace Protocol is the release candidate and considered to be stable. Since version 0.8 the specification is stable and tracks amendments on a detailed basis. All changes made to the specification can be reviewed in the GitHub repository. A versioning scheme beside the commits to the repository is not available but will be provided in the future. IDSA Dataspace Protocol Specification: https://github.com/International-Data-Spaces-Association/ids-specification/tree/main/releases/2024-1'
The purpose of XAdES is not related to organisational interoperability. Therefore, this criterion is not applicable to the specification.
The DCAT vocabulary defines the "Distribution" concept which can be used for publishing datasets in different languages. See: https://www.w3.org/TR/vocab-dcat-2/#Class:Dataset
CAMSS Assessment of IPv6 EIF Scenario v1.0.0
'DCAT, as a cross-border and cross-sector vocabulary increases government-to-government reuse of data and therefore can prevent citizens or businesses from providing standard information several times. Like all common vocabularies, DCAT facilitates the implementation of the once-only principle. DCAT-AP & Once-Only Principle reference: https://ec.europa.eu/isa2/dcat-ap-key-european-data-publishers-reach-data-consumers-and-create-european-open-data-ecosystem_en'
WSDL as a part of the stack of specifications that perform in order to make available and discoverable the web services, helps to the implementation of the once-only principle. As an example of implementation is the SELIS project, which aims to make available a web services regarding the eInvoicing. This topic is included within the Once-only Principle and Digital Single Market frameworks. See: https://joinup.ec.europa.eu/collection/eprocurement/document/secure-electronic-invoicing-service-selis
XSLT does not provide a cross sector reusable data model. The specification transforms XML documents into other formats.
"DNS Queries over HTTPS (DoH) security and privacy considerations are based on RFC 8446, IETF's Transport Layer Security (TLS) Protocol. The standard defines confidentiality and how the record layer of the protocol should provide it. AEAD encryption provides confidentiality and integrity for the data. DoH specification: https://datatracker.ietf.org/doc/html/rfc8484 Transport Layer Security (TLS) Protocol RFC 8446: https://www.rfc-editor.org/rfc/rfc8446"
The purpose of SVG is not related to the delivery of multilingual public services. Therefore, this criterion is not applicable to the specification. SVG W3C reference: https://www.w3.org/TR/SVG11/
'No evidence of direct implementation of DPV in any particular business domain could be found, although use cases can be found in which the DPV vocabulary is intended to be applied, such as online shopping. Data Protection Aspects of Online Shopping - A use case: https://www.w3.org/community/dpvcg/2019/12/12/data-protection-aspects-of-online-shopping-a-use-case/ DPV specification: https://w3c.github.io/dpv/primer/ '
'The GITB TDL is used in the GITB test bed software, nonetheless it is not tied to it. It can also be processed by any test bed implementation that conforms to the GITB specifications. GITB TDL reference: https://www.itb.ec.europa.eu/docs/tdl/latest/introduction/index.html#where-is-it-used'
'IEEE Std 802.3-2022 enhances the visibility of administrative procedures, rules, data, and services by providing standardised protocols for clear communication. It offers extensive documentation for implementation and management and facilitates interoperability among equipment from multiple vendors. IEEE Std 802.3-2022 Reference: https://ieeexplore.ieee.org/document/9844436'
"LDES is a conceptual framework where a list of immutable objects can be used to describe and publish real-time event data and it is not mandatory to use all objects. It can be used for basic events' publication, or focus on adopting LDES alongside other existing data exchange mechanisms, creating a hybrid model that embraces the strengths of each approach. LDES specification: https://joinup.ec.europa.eu/collection/semic-support-centre/linked-data-event-streams-ldes"
'The purpose of OAIS is not related to e-accessibility, therefore, this criterion is not applicable to the specification. OAIS specification: https://public.ccsds.org/Pubs/650x0m2.pdf'
'​The Semantic Interoperability Community (SEMIC) that developed this specification, is in charge of developing solutions to help European public administrations perform seamless and meaningful cross-border and cross-domain data exchanges. They develop semantic specifications and interoperability solutions under the ISA² Programme. When a new solution release is finished, it is submitted for a public review with a minimum period of four weeks. Specification development process by the ISA Programme: https://interoperable-europe.ec.europa.eu/collection/semic-support-centre/document/description-change-management-release-and-publication-process-structural-metadata-specifications Detailed document ISA Programme: https://interoperable-europe.ec.europa.eu/sites/default/files/document/2016-10/description_of_a_change_management_release_and_publication_process_for_structural_metadata_specifications_developed_by_the_isa_progr.pdf Core Location Vocabulary: https://interoperable-europe.ec.europa.eu/collection/semic-support-centre/solution/core-location-vocabulary/release/100'
The application of the once-only principle in all EU Member States public administrations aims at reducing the administrative burden. To achieve this, interoperability between public administrations is a sine qua non condition. SAML 2.0 is a format that allows seamless cross-border interoperability between systems, independent of implementation. The specification allows cross-domain single sign-on, which reduces the administrative burden of the system administrators and the users. By using SAML 2.0, avoid the user to deal with several credentials nor provide information twice.
'ISO/IEC 19944-1 includes provisions that address data integrity by promoting the implementation of security controls, data governance practices, and compliance with relevant standards and regulations. By following these provisions and complementing them with additional best practices, organisations can ensure the integrity of data within cloud computing environments. ISO/IEC 19944-1 specification: https://www.iso.org/standard/60545.html'
The specification can help understand the data of public administration by adding high quality print-ready pages. In this case, the specification can play an active role on the representation of the information in the visual way. This fact can consider TIFF/IT to foster the comprehensibility of administrative rules and data. TIFF/IT ISO reference: https://www.iso.org/standard/34342.html TIFF/IT explanation: https://www.prepressure.com/library/file-formats/tiffit
'The purpose of XACML is not related to the delivery of multilingual public services. Therefore, this criterion is not applicable to the specification. XACML OASIS reference: https://docs.oasis-open.org/xacml/3.0/xacml-3.0-core-spec-os-en.html'
'The specification has been evolved as part of its lifecycle and the previous version has been the basis for SMP eDelivery software and European Solutions regarding the development of interoperable services. This fact ensures that the specification reaches a proper market acceptance for its implementation for the development of products and services. SMP OASIS reference: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505009'
The Core Public Service Vocabulary Application Profile is a business domain agnostic specification that can be reused in a cross-domain way. CPSV-AP reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-service-vocabulary-application-profile
'There is existing documentation and studies assessing the effectiveness of Extensible Forms Description Language. The "XFDL: Creating electronic commerce transaction records using XML" study, discusses the issues surrounding the creation of legally-binding electronic transaction records on the Internet and outlines an XML-based solution called XFDL. Moreover, digital signatures and existing Web-based technology are studied, and finally, XFDL is explained in detail. However, in the 'Sustainability of Digital Formats: Planning for Library of Congress Collections' report, it is mentioned that there are simpler technologies preferred nowadays. "XFDL: Creating electronic commerce transaction records using XML" study: https://www.sciencedirect.com/science/article/pii/S1389128699000286 "Sustainability of Digital Formats: Planning for Library of Congress Collections" report about XFDL: https://www.loc.gov/preservation/digital/formats/ Extensible Forms Description Language reference: https://www.w3.org/TR/NOTE-XFDL'
'The purpose of REST is not related to the protection of personal data. Therefore, this criterion is not applicable to this specification. REST reference: https://restfulapi.net/'
Xforms 2.0 is an XML markup for a new generation of forms and other applications on the Web. An XForms-based application gathers and processes data using an architecture that separates presentation, purpose and content. Xforms 2.0 W3C reference: https://www.w3.org/community/xformsusers/wiki/XForms_2.0
'DCAT-AP is made available by SEMIC for free on Joinup, the collaborative platform created by the European Commission to share and reuse IT solutions and good practices. DCAT-AP Specification: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/dcat-application-profile-data-portals-europe/release/200'
"NUTS can contribute to the comprehensibility of administrative procedures, rules data and services, since this classification narrowly reflects the territorial administrative division of the Member States and supports the availability of data and the capacity to implement national and European policies by using interactive maps like the GISCO's database, which eases the understanding of these divisions. EUROSTAT reference, NUTS Principles and Characteristics section: https://ec.europa.eu/eurostat/web/nuts/principles-and-characteristics GISCO's database reference: https://ec.europa.eu/eurostat/web/gisco"
'The purpose of the specifications is not related to the publication of Open Data. Therefore, this criterion is not applicable to this specification. GITB TDL reference: https://www.itb.ec.europa.eu/docs/tdl/latest/introduction/index.html#what-is-the-gitb-tdl'
'Verifiable Credentials support selective disclosure, allowing individuals to share only the relevant pieces of information necessary for a particular transaction or interaction. The specification provides mechanisms that support the selective sharing and reuse of relevant information, contributing to more efficient and privacy-preserving interactions in various scenarios. Verifiable Credentials: https://www.w3.org/TR/vc-data-model/'
FTPS is a protocol for data exchange, it allows the communication between multiple endpoints and it makes available interfaces for public administrations systems. FTPS IETF reference: https://tools.ietf.org/html/rfc4217
The specification is included in 10 Member States' catalogues of recommended specifications. Some examples of Member States including RDF on their catalogues are the Netherlands, Slovenia, Spain or Sweden. See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'The specification is supporting the implementation of eIDAS regulation. Therefore, European organisations in charge of public services are prone to share and improve shared public services and the results of applying them. ETSI TS 119 614-1 reference: https://www.etsi.org/deliver/etsi_ts/119600_119699/11961401/01.01.01_60/ts_11961401v010101p.pdf'
'The XML specification is part of the eIDAS Regulation requirements as stated by ENISA. Overview of Standards for eIDAS document: https://www.enisa.europa.eu/publications/assessment-of-standards-related-to-eidas-i eIDAS Regulation: https://digital-strategy.ec.europa.eu/en/policies/eidas-regulation ENISA Reference: https://www.enisa.europa.eu/'
SMTP defines a standardised method and elements for the electronic mail exchange that can be reused broadly across sectors, but it is not defining a data model. SMTP IETF reference: https://tools.ietf.org/html/rfc5321
'ISAE 3402 was developed to provide an international assurance standard for allowing public accountants to issue a report for use by user organizations and their auditors (user auditors) on the controls at a service organization that are likely to impact or be a part of the user organization’s system of internal control over financial reporting. The main purpose of ISAE 3402, therefore, is to assure the integrity of data and preserving the confidentiality of the information being exchanged, thus, ensuring the protection of personal data. ISAE 3402 overview webpage: https://www.isae3402.com/ISAE3402_overview'
W3C has a defined and publicly available Process for the Development and approval process of the specification as a recommended standard, including a public review. W3C Process document: https://www.w3.org/TR/2010/WD-html5-20100624/
'SOAP 1.2 is maintained by W3C which is an international community developing open standards. As part of the W3C organisation, it encourages the creation of community to organise and develop open standards. W3C Consortium: https://www.w3.org/Consortium/'
After carrying out the reserch of conformity test or certifications, an open tool that allows testing with time stamping commands helping to ensure that the implementations are properly developed has been found. TSP certification tool: https://www.freetsa.org/index_en.php OpenSSL: https://www.openssl.org/docs/manmaster/man1/ts.html
'This specification provides a conceptual model of roles, states and properties that can be used to increase the accessibility and interoperability of web content and web applications. In this sense, the specification eases the development of European public services. WAI-ARIA reference: https://www.w3.org/TR/wai-aria/'
'ODRL provides a standardized format for expressing digital rights, which can contribute to interoperability between systems that support the specification. This interoperability might be beneficial in digital service delivery channels where different platforms or services need to exchange information about digital rights. W3C specification reference: https://www.w3.org/TR/odrl-vocab/#vocab-core'
'GraphQL supports data manipulation using the mutation functionality, but cannot ensure its protection against unauthorised changes. Any mutation implying changes can be only prevented by the owner of the credential authenticating the API request. GraphQL specification: https://graphql.org/learn/schema/'
'WAI-ARIA provides a set of attributes to convey information about the roles, states, and properties of user interface components within web applications that can be used to increase the accessibility and interoperability of web content. WAI-ARIA reference: https://www.w3.org/TR/wai-aria/'
The purpose of CSV is not related to the availability assurance. Therefore, this criterion is not applicable to the specification.
'The ETSI TS 119 512 specification is part of the ETSI (European Telecommunications Standards Institute) specifications organisation. ETSI was created in 1988 by the European Conference of Postal and Telecommunications Administrations (CEPT) in response to proposals from the European Commission. A special report, ETSI SR 019 510, was first created in ETSI ESI as a basis for the development of technical specifications in the field of preservation services. Based on this report, the development of the actual protocol standard, ETSI TS 119 512, and the associated “Policy and Security Requirements,” ETSI TS 119 511, took place, and all documentation and supporting processes have been published. In addition, the ETSI TS 119 512 specification was carried out in 2020, and it establishes new mechanisms that can be used in conjunction with ETSI TS 119 511. ETSI specification history: https://www.etsi.org/about ETSI TS 119 512 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.02_60/ts_119512v010102p.pdf ETSI TS 119 511 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119511/01.01.01_60/ts_119511v010101p.pdf eIDAS blog, New APIs for the eIDAS-Ecosystem: https://blog.eid.as/tag/etsi-ts-119-512-en/'
'CSV makes sure content is available on the web, structures data and makes it usable in a non-proprietary open format. Consequently the CSV fosters the simplification of the delivery of European public services as it makes files available for any system. CSV reference: https://datatracker.ietf.org/doc/html/rfc4180'
' While ISO/IEC 7498:1 itself does not directly address the delivery of public services, it plays a foundational role in the development and interoperability of networking protocols, which directly impacts the efficiency and effectiveness of various services. Moreover, the principles it espouses underpin the design and operation of many digital services today. Governments and public sector organizations that leverage these principles can enhance the delivery of services, making them more accessible, reliable, and user-friendly for the public. ISO/IEC 7498:1: https://www.iso.org/standard/20269.html'
CAdES (ISO 14533-1:2014) has the ISO community that supports the development of: International standards, Technical Specifications, Technical Report and Publicly Available Specification. The ISO standardization process: http://www.isotc292online.org/projects/iso-process/
'The purpose of ISO/IEC 19944-1 is not related to the publication of data on the web, therefore, this criterion is no applicable to the specification. ISO/IEC 19944-1 specification: https://www.iso.org/standard/79573.html'
'Domibus, is generally domain-agnostic in the sense that it can be used in various industries and sectors for facilitating communication between different entities. It provides a framework for exchanging electronic messages and documents while ensuring security, reliability, and adherence to standards like the AS4 (Applicability Statement 4) profile of the ebMS (ebXML Messaging Service) standard. Domibus specification: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/Domibus AS4 Profile of ebMS 3.0: http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/profiles/AS4-profile/v1.0/AS4-profile-v1.0.html '
SAMM is not included in European or National platforms, however, openness and the benefits for the creation of public and reusable solutions is the philosophy of the specification. Besides, it is fully accessible for its consultation, study, implementation or contribution to its development. Additionally, ENISA and ETSI which are European agencies for the development of security and standards recommend the specification as a best practices in terms of security in software development. SAMM webpage: https://owaspsamm.org/ ETSI SmartM2M; Security; Standards Landscape and best practices: https://www.etsi.org/deliver/etsi_tr/103500_103599/103533/01.01.01_60/tr_103533v010101p.pdf ENISA Advancing Software Security in the EU: https://www.enisa.europa.eu/publications/advancing-software-security-through-the-eu-certification-framework ENISA Good Practices for Security of IoT - Secure Software Development Lifecycle: https://www.enisa.europa.eu/publications/good-practices-for-security-of-iot-1
The specification allows user to access and maintain distributed directories information over the Internet, which reduces the administrative burden of the system administrators and the users. By ensuring the access to different directory services, it fosters the implementation of digital services, supporting the principle of digital-first. LDAP IETF reference: https://tools.ietf.org/html/rfc4511
'There are three Member States recommending UBL in their ICT National Catalogues. These Member States are The Netherlands, Malta and Greece. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
"EN 303 645 does not define any specific methodology for testing its provisions' conformance, but it provides for each each of the implemented features a recording template that eases conformity testing in a structred way (see the Implementation Conformance Statement proforma in Annex B of the EN 303 645 specification). On the other hand, there is the ETSI TS 103 701 conformance assessment methodology for consumer IoT devices, which is intended to set a provisions conformance testing with respect to ETSI EN 303 645, giving test cases and assessment criteria for each provision. EN 303 645 reference, Annex B: https://www.etsi.org/deliver/etsi_en/303600_303699/303645/02.01.01_60/en_303645v020101p.pdf TS 103 701 reference: https://etsi.org/deliver/etsi_ts/103700_103799/103701/01.01.01_60/ts_103701v010101p.pdf "
'By allowing the association of information with a domain, DNS facilitate the identification of interfaces. Practically, instead of having a list of interfaces as "IP Addresses", DNS allows the identification "by name" of domain. DNS IETF reference: https://datatracker.ietf.org/doc/html/rfc8499 Domain Names - Implementation and Specification: https://tools.ietf.org/html/1035 '
'With all the missions DCMI carry it can be seen that it can facilitate the business processes, with the development and curation of metadata terms namespaces and other duties it carries. DCMI About: https://www.dublincore.org/about/'
At the moment of performing the assessment, LegalDocML is considered by the European Union as part of the standarisation activity. And, at the same time, it is used by LEOS, the European Project for Legal Texts Development. So LegalDocML can be considered as an asset to build innovative solutions. The European Commission includes in its Rolling Plan for ICT Standarisation: https://ec.europa.eu/digital-single-market/en/rolling-plan-ict-standardisation LEOS: https://joinup.ec.europa.eu/collection/justice-law-and-security/solution/leos-open-source-software-editing-legislation
'There are a number of security considerations that issuers, holders, and verifiers should be aware of when processing data described by this specification. There is a specific section in the specification that attempts to highlight a broad set of security considerations. Implementers are urged to seek the advice of security and cryptography professionals when implementing mission critical systems using the technology outlined in this specification. Verifiable Credentials Security Considerations: https://www.w3.org/TR/vc-data-model/#security-considerations'
"The specification does not dwell in the exposure of interfaces to access the public administration's services in a direct way but it can ease the process. BFO reference: https://www.iso.org/standard/74572.html"
'Only nationally recognised members as well as national and CEN-recognised working groups are allowed to contribute to the development of the EN 16234-1 e-CF specification. There is no evidence of external and individual contributions, and there is no provision made for them in the CEN Internal Regulations (see CEN-CENELEC Internal Regulations reference, Part 2, section 3). Depending on the degree of involvement, financial contributions could be also applicable (CEN-CENELEC Internal Regulations reference, Part 1, CEN (1A) section, Annexes). CEN-CENELEC Internal Regulations reference, CEN Statuses, Members (IV) section: https://boss.cen.eu/reference-material/refdocs/pages/ CEN-CENELEC Internal Regulations reference, Part 2, section 3: https://boss.cen.eu/reference-material/refdocs/pages/ CEN-CENELEC Internal Regulations reference, Part 1, CEN (1A) section, Annexes: https://boss.cen.eu/reference-material/refdocs/pages/'
'DQV is designed to be independent of any specific data format or storage technology. It focuses on providing a standardised vocabulary for describing data quality information in a machine-readable format. As a result, DQV can be implemented and utilized across different platforms and environments without being tied to any particular data format or technology stack. Data Quality Vocabulary: https://www.w3.org/TR/vocab-dqv/'
"The purpose of OData is not related to the organisational interoperability agreements. Moreover, one of the MS recommending this specificacion, the Netherlands, confirms its not applicability over organisational aspects. Therefore, this criterion is not applicable to the specification. OData reference: https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html Netherland's OData report: https://www.forumstandaardisatie.nl/open-standaarden/odata"
'Implementations and some news regarding Domibus can be found in the Joinup platform, a European repository for IT solutions. Domibus in Joinup: https://joinup.ec.europa.eu/search?keys=domibus&sort_by=relevance&f%5B%5D='
'ISO/IEC 7498:1, defining the OSI (Open Systems Interconnection) model, does not mention extension of the specification. Even so, extension would be most likely possible as long as it does not interfere with the main requirements of the specification. ISO/IEC 7498:1: https://www.iso.org/standard/20269.html'
By defining an XML schema for office documents, it allows the transformation using XSLT to other formats ensuring the availability and data portability, and therefore, supporting the development of European Public Services. ODF ISO reference: https://www.iso.org/standard/66363.html ODF OASIS reference: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office
'The OData specification is included in the EUOS European catalogue of standards. EUOS reference: https://www.standict.eu/standards-repository/working-group/oasis-open-data-protocol-odata-tc'
'As the specification is a profile of DCAT , it can be interpreted that it allows extension of the specification it comes from. ADMS Specification W3C: https://www.w3.org/TR/vocab-adms/'
"The specification's namespaces terms make sure to identify the language they are working with, but it does say anything about any multilingual context. DCMI About: https://www.dublincore.org/about/ "
Ogg started as a simple project of audio compression in 1993. In 2003, two Internet RFCs were published relating to the Ogg format. The Ogg bitstream published as RFC 3533 and RFC 3534 which includes the Internet content type of Ogg. It became very popular for being an open source multimedia container format. So it is mature enough for its use in the development of products and services. Ogg XIPH reference: https://xiph.org/ogg/doc/rfc3533.txt
'The specification is independent of any software, hardware, or operating system. So it can be said that Core Criterion and Core Evidence Vocabulary is independent of any specific technology or platform. Core Criterion and Core Evidence Vocabulary reference (v1.0.0): https://joinup.ec.europa.eu/release/core-criterion-and-core-evidence-vocabulary-v100 '
After being identified by the MSP, SEMIC has developed a SHACL expression of DCAT-AP 1.2
'TrainingDML-AI Standard’s efficiency has undergone a internal rigorous review and approval process. The effectiveness of the standard would likely depend on factors such as its adoption rate, the performance of AI /ML models trained using data prepared according to the standard, and feedback from the user community. OGC TrainingDML-AI Standard: https://docs.ogc.org/is/23-008r3/23-008r3.html OGC TrainingDML-AI approach for making EO training datasets ready in deep learning frameworks paper: https://ieeexplore.ieee.org/document/10233498'
'EN 16234-1 e-CF is already associated with EIRA ABBs in the EIRA Library Of Specifications (ELIS). More specifically, the e-CF can define the interoperability aspects of the Interoperability Skill ABB of the EIRA Organisational View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /solution/elis/release/v110 '
IPsec is included in the Spanish catalogue of standards. Spain complies with at least 4 out of 5 sections of the EIF according to the NIFO factsheets. See: https://administracionelectronica.gob.es/pae_Home/pae_Estrategias/pae_Interoperabilidad_Inicio/pae_Normas_tecnicas_de_interoperabilidad.html#CATALOGOESTANDARES
'Principle 2.4 from the E-ARK CSIP specification states any Information Package should have an identifier which is globally unique and persistent, fact that allows repositories to participate more easily in cross-institutional information exchange and reuse scenarios. E-ARK CSIP specification: https://earkcsip.dilcis.eu/#introduction'
'In some aspects, OAS can facilitate the modelling of business processes since it is a tool to document the design of an API in an automated manner as well as to develop RESTful APIs themselves in a simpler and more efficient way. OAS specification: https://spec.openapis.org/oas/latest.html#openapi-specification OAS in Github: https://github.com/OAI/OpenAPI-Specification/#participation '
eDelivery SMP 1.10 does not define a cross-sector reusable data model per se, this profile defines a set of implementation guidelines for the OASIS SMP Specification applied to eDelivery. However, OASIS standard defines a data model for the retrieving interface. See: https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery+SMP+-+1.10 http://docs.oasis-open.org/bdxr/bdx-smp/v1.0/bdx-smp-v1.0.html
The purpose of PDF/A is not related to the implementation of the once-only principle. Therefore, this criterion does not apply to this specification. PDF/A reference: https://www.iso.org/standard/38920.html https://www.iso.org/standard/50655.html
"The purpose of ETSI TS 119 612 is not related to enabling the exposure of interfaces to access the public administration's services. Therefore this criterion is not applicable to the specification. ETSI TS 119 612: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf"
'DNS follows strict standards to ensure the global consistency and interoperability of domain name resolution. Extension Mechanisms for DNS: https://datatracker.ietf.org/doc/html/rfc6891'
'XACML is a business domain agnostic specification, notably recommended in the implementation of policies in a software infrastructure (e.g., in public administrations, data spaces). XACML OASIS reference: https://docs.oasis-open.org/xacml/3.0/xacml-3.0-administration-v1-spec-cs-01-en.html DSSC catalogue: https://dssc.eu/space/SE1/185794711 /Data+Sovereignty+and+Trust+standards+and+technologies+landscape'
'XML is used by XML Gate, the EU DG SANCO single entry point for Member States submissions of structured data in XML format via web services. Gate Reference: https://webgate.ec.europa.eu/sante-xmlgate/ui/help/Content/Home.htm'
At the moment of performing the assessment, CAdES is recommended by the European Union as an eSignature standard to ensure that electronic signatures can be created and validated anywhere in Europe. So, CAdES can be considered as an asset to build innovative solutions. eSignature standards: https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eSignature+standards CAdES ISO reference: https://www.iso.org/standard/64756.html CAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/101700_101799/101733/02.01.01_60/ts_101733v020101p.pdf
There are existing mechanisms to carry out WS-Security conformity. For instance, Weak WS-SecurityPolicy: Insecure Transport, Weak WS-SecurityPolicy: Insufficient Supporting Token Protection and Weak WS-SecurityPolicy: Tokens Not Protected See: https://github.com/YalcinYolalan/WS-SecurityAT
'The purpose of ISO 639-2 is not related to the implementation of the once-only principle. Therefore, this criterion does not apply to this specification. ISO 369-2 FAQs: https://www.loc.gov/standards/iso639-2/faq.html#5'
The purpose of the IPv4 is to enable communications over the internet, so much so it does not hamper the scalability of systems. By using IPv4, administrations, citizens or businesses can provide or consume data over the Internet without hampering the interoperability between systems. Despite the progressive adoption of the new version, IPv4 and IPv6 are meant to coexist for years. The mechanisms to enable the compatibility avoid interoperability hampering.
'XSD 1.1 is maintained by W3C which is an international community developing open standards. It also encourages people to join and contribute to making the community bigger. W3C Consortium Reference: https://www.w3.org/Consortium/'
'Confidentiality is mentioned as a security matter in DQV. It is a quality dimension described as the degree to which data has attributes that ensure that it is only accessible and interpretable by authorised users in a specific context of use. Confidentiality in Data Quality Vocabulary: https://www.w3.org/TR/vocab-dqv/#DimensionsOfISOIEC25012'
'The ELI specification allows for customization and partial implementations. It’s designed with modularity, enabling implementers to select and prioritize components based on their needs. The ELI Task Force provides resources like the ELI annotation tool, an open-source solution that can be customized and used to create and publish vocabularies in SKOS format. Thus, ELI offers a flexible framework tailored to individual requirements. ELI reference: https://eur-lex.europa.eu/eli-register/about.html ELI annotation tool reference: https://eur-lex.europa.eu/eli-register/resources.html'
The purpose of PDF 1.7 is not related to ensuring the availability of interfaces with internal information systems of a public administration. Therefore, this criterion is not applicable to the specification.
'AMQP specification is designed to define a binary wire-level protocol that allows for the reliable exchange of business messages between two parties for business messaging and does not focus on publishing data on the web. Therefore, this criterion is not applicable for the specification. OASIS AMQP Reference: http://docs.oasis-open.org/amqp/core/v1.0/amqp-core-complete-v1.0.pdf'
OpenPM2 is not included in any Member States' catalogues of recommended specifications. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
The purpose of TIFF/IT is not related to organisational interoperability. Therefore, this criterion is not applicable to the specification. TIFF/IT ISO reference: https://www.iso.org/standard/34342.html
After checking the different standard catalogues at supra-national level, there is no evidence of the inclusion of Ogg within any European catalogue of standards. ICT technical specifications: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en CEN search tool catalogue: https://standards.cen.eu/dyn/www/f?p=CENWEB:105::RESET:::: CENELEC search tool catalogue: https://www.cenelec.eu/dyn/www/f?p=104:107:0::::FSP_LANG_ID:25
'TSP is a business domain agnostic specification that can be applied in any field requiring the management of transaction orders and ensuring data consistency. TSP IETF reference: https://tools.ietf.org/html/rfc3161'
After carrying out an exhaustive search concerning LegalRuleML validation, conformance and certification, no tool has been found available for free for these purposes.
XSLT is publicly available for implementation and use for free on W3C's webpage. See:https://www.w3.org/TR/xslt-30/
The purpose of MIME is not related to the delivery of multilingual public services. Therefore, this criterion is not applicable to this specification. MIME reference: https://tools.ietf.org/html/rfc2045
'Registered Organization Vocabulary is not included in any initiative at European or National level covering privacy aspects, since its main function is to describe organisations that have gained legal entity status through a formal registration process, typically in a national or regional register. Therefore, this criterion is considered not applicable to this specification. Registered Organization Vocabulary reference: https://www.w3.org/TR/vocab-regorg/'
'Web Services Description Language (WSDL) itself does not inherently address or influence e-accessibility. WSDL is a specification designed for describing the interfaces and operations of web services, focusing on the technical aspects of communication between software systems. W3C WSDL specification: https://www.w3.org/TR/wsdl20/'
At the time of elaborating this assessment, this specification is not included in any EIRA ABB in the current EIRA Library Of Interoperability Specifications (ELIS). Although, this Core Vocabulary is included in a supranational catalogue of standards. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/solution/elis/release/v100
'This specification was published by the W3C Verifiable Credentials Working Group as a method to help solve problems related to integrity and privacy of personal information on the Web. For this reason, W3C recommends the wide deployment of this specification as a standard for the Web. W3C Verifiable Credentials: https://www.w3.org/TR/vc-data-model/'
The standard provides security features that foster the trustworthy data exchange between administration and stakeholders. PDF/A protects in itself data integrity, but also provides capabilities to protect with passwords and user roles the access to the document. PDF/A reference: https://www.iso.org/standard/38920.html https://www.iso.org/standard/50655.html
'The specification can be implemented partially, the REM introduction side can be implemented without the Electronic Signature part of the message. ETSI EN 319 532-3 reference: https://www.etsi.org/deliver/etsi_en/319500_319599/31953203/01.02.01_60/en_31953203v010201p.pdf'
The purpose of OWL2 is not related to organisational interoperability. Therefore, this criterion is not applicable to the specification. OWL2 W3C reference: https://www.w3.org/TR/owl2-overview/
'The Core Location Vocabulary can be related with the INSPIRE project. In this context, the CLV is specifically designed to aid the publication of data that is interoperable with EU INSPIRE Directive. INSPIRE in CLV: https://www.philarcher.org/isa/locn-v1.00.html Core Location Vocabulary: https://interoperable-europe.ec.europa.eu/collection/semic-support-centre/solution/core-location-vocabulary/release/100'
'IEEE Std 802.3-2022 provides a comprehensive framework for Ethernet networking. It includes standardised protocols for clear communication, extensive documentation for implementation and management, and ensures interoperability among equipment from multiple vendors. While it supports administrative procedures and data management indirectly, its primary focus is on technical specifications. IEEE Std 802.3-2022 Reference: https://ieeexplore.ieee.org/document/9844436'
'The purpose of EN 303 645 is not related to the delivery of multilingual public services. Therefore, this criterion is not applicable to this specification. EN 303 645 reference: https://www.etsi.org/deliver/etsi_en/303600_303699/303645/02.01.01_60/en_303645v020101p.pdf'
"Genericode supports custom extensions to accommodate additional requirements beyond the standard specification. Users can introduce custom elements or attributes to extend Genericode's functionality according to their specific needs and include additional metadata elements alongside code values. This metadata can provide further context, descriptions, or usage guidelines for the codes within code lists, enhancing the richness and utility of the data. Code List Representation (genericode): https://docs.oasis-open.org/codelist/genericode/v1.0/os/genericode-v1.0-os.html"
'A DID document can express verification methods, such as cryptographic public keys, which can be used to authenticate or authorize interactions with the DID subject or associated parties. For example, a cryptographic public key can be used as a verification method with respect to a digital signature; in such usage, it verifies that the signer could use the associated cryptographic private key. DIDs core properties W3C: https://www.w3.org/TR/did-core/#core-properties'
'The specification supports and makes possible reporting for different needs from the same data. The well-documented vision of XBRL GL driving its development was “A piece of business information, once entered into any computer, anywhere, never needs to be retyped as it flows through the business reporting supply chain.” http://raw.rutgers.edu/carlab/Cohen.html'
'W3C provides a Markup Validation Service for free to validate SOAP 1.2 implementations. W3C Validator: https://validator.w3.org/feed/docs/soap.html'
'The purpose of Indexed Database API is not related to data accuracy. Therefore, this criterion is not applicable to the specification. Indexed Database API: https://www.w3.org/TR/IndexedDB/'
'The purpose of XHTML is not related to the modelling of business processes. Therefore, this criterion does not apply to the specification. XHTML W3C reference: https://www.w3.org/TR/xhtml1/'
'ETSI TS 119 511 is designed to support possible customisations depending on the business-specific needs and requirements. E.g. If there is a need to create a preservation service with long or short-term storage, or even without storage. ETSI TS 119 511 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119511/01.01.01_60/ts_119511v010101p.pdf'
'The specification was created and is continuously developed by the IETF working group. Because of this development, the specification has reached version 6.0.0 and includes many implementations and extensions. Moreover, although it is not an organisation itself, people discuss implementations and how to use them in various forums. IPSec reference: https://www.rfc-editor.org/rfc/rfc6071.html IETF organisation: https://www.ietf.org/ Netgate IPsec forum: https://forum.netgate.com/category/17/ipsec'
As most of the vocabularies, DCAT reuses several existing ones (e.g. "adms", "foaf") and the Resource Description Framework (RDF). This results in a dependency that can hamper interoperability, especially in the case where new releases of the reused vocabularies are not backward compatible.
'TLS is recommended by eight Member States, including Cyprus, France, Germany, Greece, Malta, the Netherlands, Norway, and Spain. France National Catalogue of Standards (Referentiel General Interoperabilite) Reference: https://www.numerique.gouv.fr/uploads/Referentiel_General_Interoperabilite_V2.pdf Netherlands National Catalogue of Standards TLS Reference: https://www.forumstandaardisatie.nl/open-standaarden/tls CAMSS list of standards: https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-andspecifications-camss/camss-list-standards'
As a vocabulary, the implementation of CPSV-AP can be tested using methods like SHACL shapes and using semantic reasoners to ensure that the implementation is well-formed. These validation mechanisms can be used with open source tools or lite versions of tools like GrapghDB or Protégé. SHACL validation: https://graphdb.ontotext.com/documentation/free/shacl-validation.html#what-is-shacl-validation Semantic Reasoners List: http://owl.cs.manchester.ac.uk/tools/list-of-reasoners/
'Indexed Database API is already associated to EIRA ABBs in the EIRA Library of Interoperability Specifications (ELIS). More specifically, Indexed Database API can define the interoperability aspects of the "Data Management" and "Cache Manager" ABBs of the EIRA Technical View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/v610'
'GraphQL is used in the SmartM2M project, which proposes guidelines for using semantic interoperability in the industry in ETSI TR 103 535, where IoT systems address trustworthiness, privacy, data protection and security by combining different ontologies and practices. GraphQL specification: https://graphql.org/learn/schema/ ETSI TR 103 535 specification: https://www.etsi.org/deliver/etsi_tr/103500_103599/103535/01.01.01_60/tr_103535v010101p.pdf SmartM2M - Study for oneM2M (ETSI): https://www.etsi.org/deliver/etsi_tr/103700_103799/103715/01.01.01_60/tr_103715v010101p.pdf'
'The specification is included in 10 Member States catalogues of recommended specifications. This Member States are Austria, Croatia, France, Germany, Greece, Malta, Netherlands, Spain, Sweden and Cyprus. Moreover, LDAP is used in the ULISSE project as a database to store user credentials, and controls user access to tools as well, with some exceptions. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards ULISSE project reference: https://cordis.europa.eu/project/id/218815/reporting'
'Estonia plans wide use of XBRL-GL: "In order to create necessary preconditions for data-driven reporting with the public sector and enable companies to exchange machine-readable transaction information, the standard XBRL Global Ledger Taxonomy framework has been confirmed. The same standard is implemented also in the Estonian Tax and Customs Board “Aruandlus 3.0” (Reporting 3.0) project." https://www.mkm.ee/en/objectives-activities/real-time-economy/projects http://www.baltic-course.com/eng/good_for_business/?doc=159557'
The specification is a key enabler of trusted connections and data exchange across borders, between administrations or business. The eSignature is method increasing lately thanks to its benefits reducing burdens. PAdES Baseline profile is involved in the electronic signature of PDFs documents, and as an asset to ease secure and trustworthy data exchange between parties it foster the creation of solutions, including innovative solutions.
There is no Member State that includes CPOV in their national catalogue with the National Interoperability Framework (NIF) aligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'As can be seen in the Crypto Publication Review Board, the NIST organisation establishes periods for initial comments, and then, they make a decision proposal, taking into account all the comments. In addition, all the comments collected in the "call for comments" period can be found in each specification section in the Crypto Publication Review Board. This process for the crypto standards, can be extended to other type of solutions. NIST crypto standards release lifecycle: https://csrc.nist.gov/projects/crypto-publication-review-project AES Standard Reference: https://csrc.nist.gov/pubs/fips/197/final'
'The purpose of REST is not related to the delivery of multilingual public services. Therefore, this criterion is not applicable to this specification. REST reference: https://restfulapi.net/'
The purpose of SOAP 1.2 is to store, transport and exchange data through interoperable systems. Moreover, SOAP 1.2 uses XML which defines a set of rules for encoding documents in a human-readable format and machine-readable format enhancing the reusability of data and stimulating the interoperability of systems and services. Additionally, W3C develops its specification independently from any vendor. Thus, the adoption of SOAP 1.2 does not hamper the data portability of data expressed with it. In fact, the adoption of SOAP endorses the binding and invoking of web services allowing data exchange across borders. See: https://www.w3.org/TR/2006/REC-xml11-20060816/ https://www.w3.org/TR/soap12/
'The objective of the specification is to allow the different partners to share manufacturing assets to facilitate their interoperability. Details of the Asset Administration Shell (AAS) https://industrialdigitaltwin.org/en/wp-content/uploads/sites/2/2024/06/IDTA-01001-3-0-1_SpecificationAssetAdministrationShell_Part1_Metamodel.pdf'
The Wheat Data Interoperability Guidelines Specification covers a specific area of application, wheat-related data exchange; that is actually not covered by any other technical specification being under consideration to become a European standard. This conclusion has been drawn from the examination of all the programming mandates addressed to CEN, CENELEC and ETSI to the date, CEN’s webpage , CENELEC’s webpage , CEN-CENELEC’s webpage ICT section , the EC Information Providers Guide, Directive (EU) 2016/2102 of the European Parliament and of the Council of 26 October 2016 on the accessibility of the websites and mobile applications of public sector bodies , the standards and tools for exchange and processing of actionable information inventory of ENISA and the ENISA Programming Document 2018-2020 .
'TGF has only been found to be used in the British PAS 182:2014 standard on smart cities, which builds on the TGF specification. PAS 182:2014 standard: https://knowledge.bsigroup.com/products/smart-city-concept-model-guide-to-establishing-a-model-for-data-interoperability/standard'
"The infrastructure component DAPS in a given IDS ecosystem enables enrichment of identities of organisations and connectors with additional attributes thus, facilitating the publication of data on the Web. Furthermore, DAPS' license is OpenSource/Apache2 so, it incorporates open standards. DAPS: https://github.com/International-Data-Spaces-Association/IDS-G/tree/main/Components/IdentityProvider/DAPS"
After searching in the different official European websites, there is no evidence of any cross-border project that uses PAdES (ISO 14533-3:2017) nor explicit agreements involving the usage of the specification. However, the specification PAdES from ETSI, is involved in some cross-border projects as "Analysis of standards related to Trust Service Providers" developed by ENISA (European Union Agency for Network and Information Security) which is a centre of network and information security expertise for the EU, its member states, the private sector and Europe’s citizens. ENISA project: https://www.enisa.europa.eu/publications/tsp_standards_2015/at_download/fullReport PAdES ISO reference: https://www.iso.org/standard/67937.html PAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/102700_102799/10277801/01.01.01_60/ts_10277801v010101p.pdf
'XACML is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, XACML can define the interoperability aspects of the "Access Management", "Authorisation", "Digital-ready Policymaking", "Public Policy" and "Agreement on Privacy" ABBs of the EIRA Technical, Legal and Organisational View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications camss /solution/elis/distribution/elis-v600xlsx'
'At the time of the assessment, ShEx is not recommended by any European Member State. ShEx primer document: https://shexspec.github.io/primer/ ShEx Community Group: https://www.w3.org/community/shex/ ShEx Github: https://github.com/shexSpec/spec/issues CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards'
The IETF is a consensus-based group, and authority to act on behalf of the community requires a high degree of consensus and the continued consent of the community. The process of creating an Internet Standard is straightforward: a specification undergoes a period of development and several iterations of review by the Internet community and revision based upon experience, is adopted as a Standard by the appropriate body and is published. In practice, the process is more complicated, due to (1) the difficulty of creating specifications of high technical quality; (2) the need to consider the interests of all the affected parties; (3) the importance of establishing widespread community consensus; and (4) the difficulty of evaluating the utility of a particular specification for the Internet community. The goals of the Internet Standards Process are: - Technical excellence; - prior implementation and testing; - clear, concise, and easily understood documentation; - openness and fairness; and - timeliness. The goal of technical competence, the requirement for prior implementation and testing, and the need to allow all interested parties to comment all require significant time and effort. The Internet Standards Process is intended to balance these conflicting goals. The process is believed to be as short and simple as possible without sacrificing technical excellence, thorough testing before adoption of a standard, or openness and fairness. Standard process IETF: https://www.ietf.org/standards/process/
'The ETSI and any of its committees, in charge of the development of ETSI TS 119 612, operates under the ETSI Intellectual Property Rigths (IPRs) and IPR Policy. The specification is licensed on a Royalty-free. ETSI ownership of IPRs section: https://www.etsi.org/intellectual-property-rights'
'The purpose of this specification is not related to the delivery of multilingual public services. Therefore, this criterion is not applicable to this specification. Even so, database internationalisation plays a pivotal role in fostering seamless communication and collaboration in a multilingual context. By incorporating robust internationalisation features, databases empower organisations to effortlessly adapt their data structures and content to meet the specific needs of users around the world. IDSA Dataspace Protocol: https://docs.internationaldataspaces.org/ids-knowledgebase/v/dataspace-protocol/overview/readme'
'While ISO/IEC 7498:1 is not prescriptive about specific technologies or protocols, it does allow for customisation given that it provides a structure that can be adapted to different needs and environments. Customisation within the OSI model can occur at various levels such as layering adaptations and interface definitions. ISO/IEC 7498:1: https://www.iso.org/standard/20269.html'
After carrying out an exhaustive search, no evidence has been found regarding XSD 1.1 compliance with the European Regulation on Standardisation.
'The specification is considered sufficiently mature on the 2.2 version of the specification. At the same time version 3.1.0 is going through a public review in 2023. CPSV-AP Joinup webpage: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/core-public-service-vocabulary-application-profile/release/22 CPSV-AP release 3.1.0: https://joinup.ec.europa.eu/collection/semic-support-centre/solution/core-public-service-vocabulary-application-profile/release/310'
'ISO/IEC 19944-1 has been found recommended in a digitalisation report by the Spanish Standardisation Association (UNE) and the Louxembourg Institute for standardisation (ILNAS) as one of the specifications "addressing business challenges and supporting related ICT development". UNE digitalisation report: https://www.une.org/normalizacion_documentos/Informe%20Transformaci%C3%B3n%20Digital_20201127.pdf ILNAS Technical standardisation report: https://portail-qualite.public.lu/dam-assets/publications/normalisation/2022/report-technical-standardization-cloud-computing.pdf'
'W3C provides a test suit for WSDL 2.0 implementations. Moreover, the specification document contains a reference to verify the conformity of a WSDL document. It can be found in section 1.3 of the specification. W3C WSDL 2.0 Test Suite https://dev.w3.org/2002/ws/desc/test-suite/index.html W3C WSDL specification: https://www.w3.org/TR/wsdl/#markup '
The flexibility provided by UDDI allows its use in a public or internal way. The information model is widely adaptable to user needs, what means that UDDI nodes and registries can be modelled following Informational model guidelines. The implementation of UDDI does not hamper the scalability of systems.
The purpose of the specifications is not related to the availability of interfaces with internal information systems. Therefore, this criterion is not applicable to this specification. SMTP IETF reference: https://tools.ietf.org/html/rfc5321
'There have been found some assessments directly addressing CPSV-AP effectiveness. Below two examples: the first one of CPSV-AP being evaluated for comprehensiveness and compliance with EU policies, and the second one, a study on the use of CPSV-AP to publish public service descriptions as linked open data. Public Service Models: A Systematic Literature Review and Synthesis: https://ieeexplore.ieee.org/abstract/document/8823991 On using CPSV-AP to publish public service descriptions as linked open data: https://link.springer.com/article/10.1007/s11761-022-00344-6'
'While it may not specifically facilitate the modeling of business processes, it can provide valuable information about the assets involved in business processes, such as data models, ontologies, vocabularies, and other related resources. These assets can be utilized in the modeling and implementation of business processes, but the ADMS specification itself is not designed explicitly for business process modeling. ADMS Specification W3C: https://www.w3.org/TR/vocab-adms/ ADMS in Joinup: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/adms '
'SAREF itself does not explicitly include mechanisms for ensuring or enabling data processing accuracy. The responsibility for ensuring data processing accuracy lies with the implementers and the systems that use SAREF. SAREF: https://saref.etsi.org/core/v3.1.1/ '
'The purpose of SFIA is not related to e-accessibility. Therefore, this criterion does not apply to this specification. SFIA reference: https://sfia-online.org/en/sfia-8'
After being evaluated compliant with the regulation on standardisation 1025/2012, IPv6 has been identified by Commission Implementing Decision. See: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en
The specification of SVG is available for free, it can be checked on the W3C official webpage. SVG W3C reference: https://www.w3.org/TR/SVG11/
'AMQP specification allows for partial implementations, meaning that certain behaviours or features might not be supported by every implementation. This flexibility enables adaptation to specific use cases and system requirements. One worthy implementation is RabbitMQ, which is supported by most major operating systems and platforms. It is open-source under the Mozilla Public License. RabbitMQ is designed for business messaging and provides messaging through adapters, SMTP, STOMP, HTTP, and lightweight web messaging. OASIS AMQP Reference: http://docs.oasis-open.org/amqp/core/v1.0/amqp-core-complete-v1.0.pdf RabbitMQ Implementation: https://www.rabbitmq.com/docs/protocols'
'JSON itself does not foresee access control mechanisms. These are typically implemented at the application level or within the systems that handle JSON data. The responsibility for access control lies with the applications, APIs, or servers that process JSON data. JSON specification: https://www.ecma-international.org/wp-content/uploads/ECMA-404_2nd_edition_december_2017.pdf'
'After searching in different catalogues and repositories, there is no evidence found of ETSI TS 119 512 being included in the catalogue of any Member State. ETSI TS 119 512 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.02_60/ts_119512v010102p.pdf'
OWL is developed as a vocabulary extension of RDF and is derived from the DAML+OIL Web Ontology Language. So it can be said that OWL2 is dependent of RDF. OWL2 W3C reference: https://www.w3.org/TR/owl2-overview/
IETF is a vendor neutral standard developing organisation and HTTPS is independent from any technology or platform. See: https://tools.ietf.org/html/rfc2818
IETF is a vendor neutral SDO. However, FTP relies on TCP to ensure that all data exchanged is sent correctly to the proper destination. See: https://tools.ietf.org/html/rfc959 https://tools.ietf.org/html/rfc793
'The Interoperability Test Bed (ITestBed) is used to allow the conformance of any model developed from EIRA. It is called the Interoperability Architecture Solutions Validator, that not only can validate models from EIRA but also the different specialisations such eGovERA models. Interoperability Architecture Solutions Validators: https://www.itb.ec.europa.eu/eira/upload EIRA reference: https://interoperable-europe.ec.europa.eu/collection/european-interoperability-reference-architecture-eira /solution/eira/release/610 EIRA Github Repository: https://github.com/CarTool-EC/EIRA'
The adoption of TLS 1.2 does not affect the system scalability. However, the new 1.3 version has improved security. Despite having this situation the interoperability is not affected due to its fluid interconectness.
'The OASIS ebXML Core (ebCore) Technical Committee promotes the sharing of data and results and helps accelerate the specification adoption throughout the international community, particularly within government agencies. In this sense, the specification encourages both the creation of communities and the sharing of their data and results on international platforms. OASIS ebXML Core (ebCore) Technical Committee reference: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ebcore'
As specification to structure data in order to allow the maximum interoperability between systems, RDF fosters the data portability between administrations at the same time that helps to enhance data discoverability and enabling the cross-data set queries using SPARQL. Specifically, RDF helps data portability and exchange between databases. The serialisation of RFD has several forms that ensure the availability of data. See: https://www.w3.org/TR/rdf11-primer/
'The Nordic Institute for Interoperability Solutions mentions the Dataspace Protocol in the making of Road-X 8, an open source data exchange layer solution that enables organizations to exchange information over the Internet. Road-X 8 Proof of Concept (PoC) started to integrate the standard Dataspace Protocol into X-Road and concentrate on the trust framework later. NIIS Making of X-Road 8 - PoC: https://www.niis.org/blog'
'The DCMI specification is not included in any Member State catalogue of recommended specifications. List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
'DIDs does not directly address data processing accuracy, but can be complemented with others specifications to guarantee a certain degree of data accuracy. DIDs is often used in conjuntion with VCs, which allow users to share claims in a verifiable manner. DIDs enhance data processing accuracy by ensuring data originates from verified sources, maintaining immutable records, enabling detailed traceability, implementing role-based data entry, automating data verification, and allowing selective disclosure. Therefore, using DIDs, individuals can control and manage their version controls, ensuring the accuracy of the information shared. DIDs data accuracy W3C: https://www.w3.org/TR/did-core/ VCs W3C: https://www.w3.org/TR/vc-data-model/ '
'There is existing documentation and studies assessing the effectiveness of Indexed Database API. In "Evaluating IndexedDB Performance on Web Browsers" study, is conducted a comparative analysis of IndexedDB performance on four renowned browsers. In this sense, IndexedDB operations are explored in each browser and a statistical analysis is conducted to compare the performance of these operations on each browser. "Evaluationg IndexedDB Performance on Web Browsers" study: https://ieeexplore.ieee.org/abstract/document/8080047'
'There are several validators for ORDL that help to ensure that the implementation and description of datasets are conformant with the requirements set out in the specification. ODRL Implementation: http://odrlapi.appspot.com/ ODRL Implementation evaluator: http://odrlapi.appspot.com/apidoc/index.html'
'The specification performs efficiently in accordance with the TR-ESOR middleware techincal guidelines. The goal of the TR-ESOR Guideline is to assist in the process of choosing and using suitable security measures for the preservation of evidence of signed electronic documents over long periods of time. The document outlines security requirements that implementations must meet, ensuring the integrity, authenticity, and non-repudiation of digital signatures. TR-ESOR Preservation of Evidence of Cryptographically Signed Document: https://www.bsi.bund.de/SharedDocs/Downloads/EN/BSI/Publications/TechGuidelines/TR03125/TR-03125_v1_2_2-main-doc.pdf?__blob=publicationFile&v=1 ETSI TS 119 512 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.02_60/ts_119512v010102p.pdf'
'CPOV is a business domain agnostic data model that can be applied in any field requiring the management of transaction orders and ensuring data consistency. CPOV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-organisation-vocabulary'
'The specification promotes visibility to business data and harmonizes the data contents thus enabling better usability for the data.'
The purpose of Xforms is not related to organisational interoperability. Therefore, this criterion is not applicable to the specification. Xforms 2.0 W3C reference: https://www.w3.org/community/xformsusers/wiki/XForms_2.0
'Nowadays people entrust their personal data to an increasing number of services, which are connected to their devices and homes. In this sense, the specification explicitly addresses and enables the secure and trustworthy data processing (see EN 303 645 reference, provisions 5.4, 5.10 and 5.11). EN 303 645 reference: https://www.etsi.org/deliver/etsi_en/303600_303699/303645/02.01.01_60/en_303645v020101p.pdf'
'The Advanced Encryption Standard is a fundamental tool that allows public administrations to protect the confidentiality of personal data through the use of a strong and standardised encryption algorithm. By adhering to this specification, public entities can ensure that sensitive information remains secure and is only accessible to authorised parties. AES Standard Reference: https://csrc.nist.gov/pubs/fips/197/final'
'The purpose of HTTP Cookies is not related to the delivery of multilingual European public services. Therefore this criterion is considered not applicable to this specification. HTTP Cookies reference: https://datatracker.ietf.org/doc/html/rfc6265#section-1'
ADMS is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, ADMS can define the interoperability aspects of the "Data" ABB from the Semantic View, and "Metadata Management Component”, “Metadata Management Service”, “Data Publication Component”, and “Data Publication Service” ABBs of the EIRA Technical View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/solution/elis/release/v100
'The purpose of ETSI TS 119 511 is not related to e-accessibilty; therefore, this criterion does not apply to the specification. ETSI TS 119 511 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119511/01.01.01_60/ts_119511v010101p.pdf'
The purpose of DNS is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification.
The specification was formally defined between 2015 and 2017 with the experience and the expertise of the Member States that were closely working together to consolidate the specification. This fact demonstrates that guidelines have been agreed taking into account the experience from different stakeholders and it ensures its maturity by the time being. Better Regulation Toolbox reference: https://ec.europa.eu/info/sites/info/files/better-regulation-toolbox_2.pdf
'Several implementations from the open source and proprietary sectors exist, as well as fully featured servers and libraries for building custom applications. An example of this is the Windows server, which since 2009 includes the OCSP protocol. Microsoft reference, Implementing OCSP responder: https://techcommunity.microsoft.com/t5/ask-the-directory-services-team/implementing-an-ocsp-responderpart- i-introducing-ocsp/ba-p/396493'
'The puropes of ETSI TS 119 512 is not related to the exposure of interfaces. Therefore this criterion is not applicable to this specification. ETSI TS 119 512 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.02_60/ts_119512v010102p.pdf'
'The purpose of DCAT is not related to organisational interoperability. Therefore this criterion is not applicable to this specification. DCAT (v2.0.0) reference: https://www.w3.org/TR/vocab-dcat-2/ '
The purpose of CSS is not related to security and privacy of the data exchange. Therefore, this criterion is not applicable to the specification. CSS v2.1 W3C reference: https://www.w3.org/TR/2011/REC-CSS2-20110607/
'The purpose of ESI/REM is not related to supporting the evolution of European public services, therefore it does not promote or hinder it. ETSI EN 319 532-3 reference: https://www.etsi.org/deliver/etsi_en/319500_319599/31953203/01.02.01_60/en_31953203v010201p.pdf'
XSD is widely used when exchanging information in XML is needed. There are two european initiatives that are using XSD to provide services. The first initiative is TED eSentool, a free web service of the Publications Office which is focused in allow eSenders to follow-up the process of their notices until publication. The ESPD, is another cross border initiative using XSD for the validation of the XML documents generated while generating eProcurement process and documentation. See: https://esentool.ted.europa.eu/ https://ec.europa.eu/growth/single-market/public-procurement/digital/espd
'As EN 16234-1 e-CF was designed as a common standardised framework for Europe-wide application, resulting from a common effort between the public and private domains, the specification has sufficient market acceptance for its use in the development of digital solutions and services. Nowadays the IT Professionalism Europe (ITPE) is in charge of carrying out all the consultive efforts regarding the EN 16234-1 e-CF specification (see CEN/TC 428 "ICT Professionalism and Digital Competences" Business Plan 2022 reference, section 1.1). CEN/TC 428 "ICT Professionalism and Digital Competences" Business Plan 2022 reference, section 1.1: https://standards.cencenelec.eu/BPCEN/1218399.pdf IT Professionalism Europe (ITPE) reference, e-Competence Framework: https://itprofessionalism.org/about-it-professionalism/competences/the-e-competence-framework/'
'The purpose of UDDI is not related data portability, therefore this criterion is considered not applicable to this specification. UDDI OASIS reference: https://www.oasis-open.org/committees/uddi-spec/doc/spec/v3/uddi-v3.0.2-20041019.htm#_Toc85907967'
'Genericode is recommended by four different European Member States. For instance, it is included in the Dutch ICT National Catalogue as a useful standard for defining code lists. *No encuentro los otros catalogos con genericode aunque en la lista pone que están. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards Netherlands Open Standards Catalogue: https://www.forumstandaardisatie.nl/open-standaarden/aanbevolen'
'LDAP is included in 9 national catalogues of recommended specifications. They belong to Croatia, Cyprus, France, Germany, Greece, Malta, Netherlands, Spain, Sweden. The National Interoperability Framework (NIF) of Spain is fully aligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. Nonetheless, countries like Sweden or Malta do not get a high perfomance, being alligned with 3 out of 5 and 2 out of 5 respectively. National catalogue Malta: https://www.forumstandaardisatie.nl/open-standaarden National catalogue Spain: https://administracionelectronica.gob.es/pae_Home/pae_Estrategias/pae_Interoperabilidad_Inicio /pae_Normas_tecnicas_de_interoperabilidad.html#CATALOGOESTANDARES National catalogue Sweden: https://www.avropa.se/globalassets/dokument/open-it-standards.pdf?_t_id=1B2M2Y8AsgTpgAmY7PhCfg% 3d%3d&_t_q=standards&_t_tags=language%3asv%2csiteid%3a95d515a5-23ca-47bf-87a9- 07b10d8ac360&_t_ip=178.139.72.144&_t_hit.id=Avropa_Core_Models_Media_GenericMedia/_ff07d720- f793-44b0-994d-27e79b28f6bd&_t_hit.pos=7 NIFO factsheets: https://joinup.ec.europa.eu/collection/national-interoperability-framework-observatory-nifo/nifo-factsheets'
'Registered Organization Vocabulary was previously developed and used by the ISA Programme. The ISA (Interoperability Solutions for European Public Administrations), is a European Union programme (implemented by the Commission) contributing to a European Union free from electronic barriers at national borders. However, according to recent discussions on the CBV GitHub, W3C has discontinued the Registered Organization Vocabulary and the community along with the continuation for the development moved to the Core Business Vocabulary. Registered Organization Vocabulary reference: https://www.w3.org/TR/vocab-regorg/ ISA Programmae Reference: https://publications.europa.eu/resource/cellar/c80c7ff1-14e7-43d6-a56f-99bf254c33f9.0001.02/DOC_1 Core Business Vocabulary Github reference: https://github.com/SEMICeu/Core-Business-Vocabulary/tree/master Core Business Vocabulary Github Issue 51 - RegOrg maintenance reference: https://github.com/SEMICeu/Core-Business-Vocabulary/issues/51'
'HTTP does provide a basic framework and elements that can be built upon to enable access control features like offering an authentication framework (Like Proxy-Authorization), method-specific semantics (Such as: GET, HEAD, OPTIONS), and relevant status codes (Such as: 401 Unauthorized,403 Forbidden or 405 Method Not Allowed). HTTP/1.1, RFC 2616 Reference: https://www.rfc-editor.org/rfc/rfc2616 HTTP/1.1 Authentication, RFC 9110 Reference: https://www.rfc-editor.org/rfc/rfc9110#name-http-authentication'
'HTTP does focus on ensuring the accurate transmission of data between clients and servers. It incorporates mechanisms that contribute to maintaining accuracy during the transmission and storage of data in caches. HTTP/1.1, RFC 2616 Reference: https://www.rfc-editor.org/rfc/rfc2616 HTTP/1.1 Caching, RFC 9111 Reference: https://www.rfc-editor.org/rfc/rfc9111 HTTP/1.1 Authentication, RFC 9110 Reference: https://www.rfc-editor.org/rfc/rfc9110#name-http-authentication'
'The purpose of DCAT-AP is not related to the provision of access control mechanisms. Therefore, this criterion is not applicable to the specification. DCAT-AP Specification: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/dcat-application-profile-data-portals-europe/release/200'
'JSON is a text format that is completely language independent. The specification uses conventions that are familiars to C-family of languages, including C, C++, C#, Java, JavaScript, Perl, Python, and many others. For these reasons, JSON is an optimum data exchange and interchange language. JSON specification: https://www.ecma-international.org/wp-content/uploads/ECMA-404_2nd_edition_december_2017.pdf'
'Currently the specification does not include a public review of the release life-cycle although the specification and its releases are publicly available. BFO reference: https://www.iso.org/standard/74572.html'
'The specification provides a standard format for representing legal documents, which can facilitate data portability between systems and applications supporting the implementation of European public services. By using a standard format, different systems and applications can exchange legal documents in a common language, which can help to avoid compatibility issues and ensure interoperability. AKN4EU reference: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/akn4eu'
'JSON in itself does not provide security features, which is a weakness per se. The storage of private data as JSON format is not recommended in order to avoid malicious activities against stored information. Despite this, there are several additional features with the aim of protecting data exchange. How do you secure and encrypt JSON and XML data in web communication: https://www.linkedin.com/advice/0/how-do-you-secure-encrypt-json-xml-data-web-communication'
'Syslog is considered platform-agnostic, as it is not tied to a specific operating system or hardware platform. The syslog protocol is designed to provide a standardized method for message logging and can be implemented on various operating systems, including Unix, Linux, Windows, and others. Additionally, syslog is used on a wide range of network devices, such as routers, switches, firewalls, and servers, making it platform-independent at the application layer. Syslog Protocol: https://datatracker.ietf.org/doc/html/rfc5424'
XAdES Baseline Profile function is to facilitate the electronic signature in compliance with eIDAS, campliant with the European Directive of electronic signature of the European Parliament and the Council. See: https://www.etsi.org/deliver/etsi_ts/103100_103199/103171/02.01.01_60/ts_103171v020101p.pdf
'There are assessments that analyse and demonstrate the efficiency of AMQP and other similar specifications. For a detailed explanation of AMQP's efficiency and a comparison with other messaging protocols, refer to the document "Choice of Effective Messaging Protocols for IoT Systems: MQTT, CoAP, AMQP and HTTP." Numerous real-world scenarios and products utilise the AMQP specification, proving its efficiency. AMQP connects hundreds of systems in various sectors, including telecommunications, defence, manufacturing, internet, and cloud computing, as well as many other market segments. Notable examples include Deutsche Börse, VMware, and Mozilla, among others. Choice of Effective Messaging Protocols for IoT Systems: MQTT, CoAP, AMQP and HTTP Reference: https://pure.port.ac.uk/ws/portalfiles/portal/12197128/IoT_Messaging_Protocols_Naik.pdf Products and Success Stories - AMPQ.org Reference: https://www.amqp.org/about/examples Deutsche Börse Reference: https://www.deutsche-boerse.com/dbg-de/ VMware Reference https://www.vmware.com/ Mozilla Reference https://www.mozilla.org'
'OCSP is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, OCSP can define the interoperability aspects of the Trust Registry Component, Trust Registry Service and Trust Registry Provisioning Component ABBs of the EIRA Technical View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/v110'
WS-Security is not licensed on a (F)RAND basis.
'The SHACL specification is included in 3 Member States catalogues of recommended specifications. This Member States are Belgium, Malta, Malta and the Netherlands. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards SHACL W3C reference: https://www.w3.org/TR/shacl/'
There are many testimonials from OASIS consistories that are a reliable example to know that WS-BPEL is a cross-sector reusable data model as it uses several XML specifications :WSDL 1.1, XML Schema 1.0, XPath 1.0 and XSLT 1.0. XML Schema type definitions provide the data model used by WS-BPEL processes. The specification: http://docs.oasis-open.org/wsbpel/2.0/OS/wsbpel-v2.0-OS.html
After checking the different standard catalogues at supra-national level, there is no evidence of the inclusion of PAdES (ISO 14533-3:2017) within any European catalogue of standards. ICT technical specifications: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en CEN search tool catalogue: https://standards.cen.eu/dyn/www/f?p=CENWEB:105::RESET:::: CENELEC search tool catalogue: https://www.cenelec.eu/dyn/www/f?p=104:107:0::::FSP_LANG_ID:25
After carrying out information retrieval, no document or study has been found assessing the PDF/A in terms of efficiency or effectiveness.
The version which is being assessed was released in 2012, fact that demonstrates the maturity of the specification for its use in the development of products and services. Moreover, XSD is an open specification supported by products and services and it is involved in the development of web services as XML schemas are needed for validating XML files.
'The specification is not widespread known and used. However, it is a national initiative from Italy, which is encouraging to use from its Digital transformation team. Publiccode.yml issued in Italy to describe the software created in the country. This has permitted the creation of a national catalogue of software by crawling the content of the publiccode.yaml available within the software repositories. Moreover, the specification is also applied in opencode.de, Germany’s registry for open-source software in public administration. Publiccode.yaml documentation: https://docs.italia.it/italia/developers-italia/publiccodeyml-en/en/master/index.html Italian National Software Catalogue: https://developers.italia.it/ Open CoDE: https://opencode.de/en'
SAML 2.0 is not available at any European or National platform for its use and implementation. Despite this, the specification is available at OASIS’s webpage. See: http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-tech-overview-2.0.html
The current version of the specification was released back in 2018 and has been tested with real implementors to demonstrate its usefullness and application. However, it is a specifications that has room for improvements and it is one of the focus of the W3C working group. W3C specification reference: https://www.w3.org/TR/odrl-vocab/#vocab-core W3C Working Group Github space: https://github.com/w3c/odrl
'HTTP provides a foundation for communication over a computer network, offering tools for extending the protocol, which could potentially enhance data exchange between systems supporting European public services. HTTP /1.1 RFC 2616 Reference: https://www.rfc-editor.org/rfc/rfc2616.html'
'Although CCCEV shapes a general framework around these core concepts, implementers have to make decisions on how the framework is actually used by further elaborating the Core Vocabulary to make it applicable in their specific context. Core Criterion and Core Evidence Vocabulary reference (v1.0.0): https://joinup.ec.europa.eu/release/core-criterion-and-core-evidence-vocabulary-v100 '
'After carrying out a search, two projects involving the specification were found: the Data Dictionary (DD) system developed under the IDA/EINRC framework running at the European Environment Agency’s site, and eCertis under ISA². European Environment Agency reference: http://dd.eionet.europa.eu ISA² reference: https://ec.europa.eu/isa2/solutions/e-certis_en#:~:text=e-Certis%20is%20a%20free%20online%20tool%20mapping%20documents,%28e.g.%20tax%2C%20social%20security%20obligations%2C%20criminal%20records%2C%20etc.%29.'
"The conformance of the ELI specification’s implementations can be assessed using the ELI validator. This online tool checks the compliance of ELI metadata with the ELI ontology requirements. In addition to the validator, the ELI specification also includes an annotation tool. This open-source tool enables the labeling of different legal resources, description, and publishing of metadata in machine-usable format. ELI's annotation and validator tool: https://webgate.ec.europa.eu/eli-validator/"
XAdES ensures the interoperability of electronic signatures when the documents they authenticate are transferred and processed through different systems and it can be preserved for a long term. XAdES ISO reference: https://www.iso.org/standard/56025.html XAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/101900_101999/101903/01.04.02_60/ts_101903v010402p.pdf
There is no national or European platform with the specification TIFF/IT available for free.
"1 Member State is recommending OCSP in its ICT National Catalogue. This Member State is Spain and CERES is the digital public service procured by OCSP. National catalogue Spain: https://administracionelectronica.gob.es/pae_Home/pae_Estrategias/pae_Interoperabilidad_Inicio /pae_Normas_tecnicas_de_interoperabilidad.html#CATALOGOESTANDARES CERES' OCSP reference: https://www.cert.fnmt.es/en/catalogo-de-servicios/validacion-de-certificados/ocsp"
'Currently the Asset Administration Shell (AAS) is maintained by the Platform Industrie 4.0 and has a dedicated working group in Github. In order to participate in the development of the specification, users must be members of the Industrie 4.0 consortium in the Digital Twin initiative (IDTA). IDTA members: https://industrialdigitaltwin.org/en/about-idta/become-a-member Asset Administration Shell (AAS) Github documentation: https://admin-shell-io.github.io/aas-specs-antora/index/home/index.html Details of the Asset Administration Shell (AAS) https://industrialdigitaltwin.org/en/wp-content/uploads/sites/2/2024/06/IDTA-01001-3-0-1_SpecificationAssetAdministrationShell_Part1_Metamodel.pdf'
'Any organisations can customise and adapt ISO/IEC 19944-1 scheme to align with their specific circumstances. Customisation can involve various aspects of ISO/IEC 19944-1, such as the classification categories, the criteria used for categorisation, or the specific data elements within each category. Organisations can tailor the classification scheme to accommodate their specific data types, regulatory requirements, business objectives, and industry-specific considerations. An example can be found in the Windows diagnostic data, which provides references to equivalent definitions for the data types and examples from ISO/IEC 19944-1. Windows diagnostic data https://github.com/MicrosoftDocs/windows-itpro-docs/blob/public/windows/privacy/windows-diagnostic-data.md ISO/IEC 19944-1 specification: https://www.iso.org/standard/60545.html '
'The purpose of NFVI is not related to the long-term preservation of data/information/knowledge. Therefore, this criterion is considered not applicable to this specification. NFVI Deliver, Infrastructure Overview: https://www.etsi.org/deliver/etsi_gs/NFV-INF/001_099/001/01.01.01_60/ '
'The effectiveness of the ebXML specification has been assed by the Institute of Electrical and Electronics Engineers, dedicated to standardisation and development in technical areas. In the "ebXML: status, research issues, and obstacles" study, it is seen that the status of ebXML is adressed, and open research issues to be solved in order to meet some of the obstacles on the way to a commercial application of ebXML are identified. "ebXML: status, research issues, and obstacles" study: https://ieeexplore.ieee.org/abstract/document/995093 ebXML RegRep OASIS reference: https://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html'
'The specification has a namespace which focus is to know information about who access the resource or provides an indication of its security status, the namespace may include information regarding access or restrictions based on privacy, security or other policies. DCMI About: https://www.dublincore.org/about/ DCMI Access Rights: https://www.dublincore.org/specifications/dublin-core/dcmi-terms/terms/accessRights/'
"Functionalities of ShEx are well stated in its primer document, and there are known implementations, such as for the sharing of RDF data models and to guide its curation with rigorous validation, although, being a validator for RDF graphs, there haven't been found many market uptake indicators. ShEx primer document: https://shexspec.github.io/primer/ ShEx Community Group: https://www.w3.org/community/shex/ ShEx Github: https://github.com/shexSpec/spec/issues Using Shape Expressions (ShEx) to Share RDF Data Models and to Guide Curation with Rigorous Validation: https://link.springer.com/chapter/10.1007/978-3-030-21348-0_39"
As a vocabulary, the implementation of CPOV can be tested using methods like SHACL shapes and using semantic reasoners to ensure that the implementation is well-formed. These validation mechanisms can be used with open source tools or lite versions of tools like GrapghDB or Protégé. SHACL validation: https://graphdb.ontotext.com/documentation/free/shacl-validation.html#what-is-shacl-validation Semantic Reasoners List: http://owl.cs.manchester.ac.uk/tools/list-of-reasoners/
The CCCEV is used in several cross-border projects that are regulated using Legal acts. Examples are ESPD-EDM, the TOOP, and the eCertis, all projects are focused in the field of eProcurement, and use the CCCEV as the basis for building up the requierements in procurement procedures. CCCEV Joinup page: https://joinup.ec.europa.eu/solution/core-criterion-and-core-evidence-vocabulary/about
Internet Protocol Security (IPsec), a protocol providing a network layer security (authentication and encryption), is included as a mandatory feature in the IPv6 specification. IPv6 is more secure than the alternative Internet protocol, IPv4, its previous version. See: https://tools.ietf.org/html/rfc2460
'According to the specification, a compliant DAPS must offer Server Metadata according to RFC 8414 (OAuth 2.0 Authorization Server Metadata). This offers informative metadata such as dates involved in the release of the solutions described, which means that the reliability of the exchanged data is improved. DAPS: https://github.com/International-Data-Spaces-Association/IDS-G/tree/main/Components/IdentityProvider/DAPS RFC 8414 (OAuth 2.0 Authorization Server Metadata): https://datatracker.ietf.org/doc/html/rfc8414'
'There are existing mechanisms to carry out SAML 2.0 conformity. For instance, SAMLtool.com provides a SAML Response XML validation on open source that can be found at their Github. SAML XML Validator Reference: https://www.samltool.com/validate_response.php'
As it happens with all the e-Government Vocabularies, it has the SEMIC action from the ISA2 as responsible for the maintenance of the development. Additionally, there's a post on W3C in open government community group that talks about the specification. CPOV page on Joinup: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-organisation-vocabulary CPOV post in W3C: https://www.w3.org/community/opengov/2016/02/21/core-public-organisation-vocabulary/
"IEEE Std 802.3-2022 has been found in the Standard reference list for European Smart City initiatives. These cities integrate traditional infrastructure with cutting-edge digital solutions to enhance efficiency and quality of life. While the standard itself isn't explicitly mentioned in other projects, its underlying network infrastructure and Ethernet extensions can provide a robust foundation for these projects. Report of TWG Smart Cities: Landscape of Smart Cities Standards reference: https://www.standict.eu/sites/default/files/2021-12/StandICT.eu2023_Smart%20Cities%20Landscape%20Report_Booklet_V1.0.pdf Smart Cities Project: https://digital-strategy.ec.europa.eu/en/policies/smart-cities-and-communities "
Although HTML can be used independently of other technical specifications, it can be enhanced along other specifications, for example, it can be used with CSS to give a visual format to the HTML code. HTML W3C reference: https://www.w3.org/TR/html401/
ASiC Baseline profile depends on the different electronic signature standards (CAdES, PAdES, XAdES), and its settings regarding the level of conformity to provide a convenient result. Even though all the specifications above mentioned are interrelated, each one takes into account the others avoiding interoperability issues by indicating the requirements of each use case.
'OData builds incrementally. Customers can easily build a very basic standards-compliant service. Only additional work will be needed to support extra or or add-on capabilities. OData, 2 Overview: http://docs.oasis-open.org/odata/odata/v4.0/errata03/os/complete/part1-protocol/odata-v4.0-errata03-os-part1-protocol-complete.html#_Toc453752201'
"DIDs are globally unique and language-neutral, consisting of an alphanumeric string that remains consistent across different languages. This consistency ensures seamless interoperability, regardless of the user's preferred language. DIDs structure W3C: https://www.w3.org/TR/did-core/#a-simple-example"
'The Better Regulation Guidelines and Toolbox does not contemplate data accuracy measures as an element to define regulatory elements. Therefore the criterion is not applicable. Better Regulation Guidelines and Toolbox reference: https://commission.europa.eu/law/law-making-process/better-regulation/better-regulation-guidelines-and-toolbox_en Better Regulation Toolbox reference: https://commission.europa.eu/document/download/9c8d2189-8abd-4f29-84e9-abc843cc68e0_en?filename=BR%20toolbox%20-%20Jul%202023%20-%20FINAL.pdf'
Information shared by an IPv4 packet, which is the smallest message entity exchanged via the Internet Protocol, contains structured information which can be considered a cross-border reusable data model. That structure is relevant for proper consumption and data exchange.
'YAML is not included in any initiative at European or National level covering privacy aspects. Therefore, this criterion is considered not applicable to this specification. YAML specification: https://yaml.org/spec/1.2.2/'
'The specification is focused on ensuring risk management regarding the security of information, therefore, this criterion does not apply due to the scope of the specification. ISO/IEC 27001 reference website: https://www.iso.org/standard/54534.html'
The purpose of SAML 2.0 is not related to the publication of data as Open Data. Therefore, this criterion is not applicable to this specification.
'IEEE Std 802.3-2022 is highly usable beyond the business-specific domain, enabling its application across various sectors due to several key factors. The specification offers a versatile and reliable foundation for networking needs across multiple domains, enhancing its usability and effectiveness in diverse settings. IEEE Std 802.3-2022 Reference: https://ieeexplore.ieee.org/document/9844436'
'IPv6 incorporates some improvements in terms of security and flexibility to its predecessor, IPv4. The specification guarantees better security by making it safer against cyber attacks. The specification is being used by some countries such as Germany, and also by some companies to continue improving their privacy. In addition, it helps in the creation of more IP adresses, which is necessary to support all the new devices connected to the internet. Therefore, the IPv6 has sufficient market acceptance and creates new solutions to the new problems. IPv6 IETF: https://www.rfc-editor.org/rfc/rfc2460 National catalogue of Germany: https://www.cio.bund.de/Web/DE/Architekturen-und-Standards/SAGA/SAGA%205-aktuelle%20Version /saga_5_aktuelle_version_node.html'
'There is no signal of the specification providing an access control mechanism. XSD Reference: https://www.w3.org/TR/2012/REC-xmlschema11-1-20120405/'
UTF-8 is publicly available for implementation and use, and therefore for everyone to study, for free on IETF's webpage. See: https://tools.ietf.org/html/rfc3629
'Through the Github platform, the OAS community is encharged of reviewing all the releases as well as raising issues and proposing improvements. OAS specification: https://spec.openapis.org/oas/latest.html#openapi-specification OAS in Github: https://github.com/OAI/OpenAPI-Specification/#participation'
CAdES is included in 2 national catalogues of recommended specifications. They belong to the Netherlands, and Spain. The National Interoperability Framework (NIF) of these Member States is fully aligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. See: https://joinup.ec.europa.eu/collection/national-interoperability-framework-observatory-nifo/nifo-factsheets
'Code List Representation (genericode) is associated with EIRA ABB's in the EIRA Library of Interoperability Specifications (ELIS). More specifically, genericode is associated with the "Reference Data” ABB from the Semantic view. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /solution/elis/release/600rf'
'There is no evidence of the inclusion of Registered Organization Vocabulary within any European catalogue of standards at supra-national level. However, the specification is being migrated to the Core Business Vocabulary. Consequently, this vocabulary can be found on the SEMIC website, within the Interoperable Europe Portal. Registered Organization Vocabulary reference: https://www.w3.org/TR/vocab-regorg/ ICT technical specifications: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en'
'The PROV family of documents does not provide direct means for authentication. Authenticity and authentication are typically implemented at the system or application level through security mechanisms, authentication protocols, and authorization frameworks. These mechanisms determine who has access to specific information and under what conditions. PROV Primer document: https://www.w3.org/TR/prov-primer/'
'AMQP License Agreement grants developers a broad set of rights to encourage widespread distribution and implementation of AMQP. The TC grant a worldwide, perpetual, royalty-free, non-transferable, nonexclusive license to copy, display, distribute, and implement the AMQP specification. AMQP Licence Reference: https://www.amqp.org/legal/amqp-license OASIS AMQP Reference: http://docs.oasis-open.org/amqp/core/v1.0/amqp-core-complete-v1.0.pdf'
ECMA International's purpose is to make available the developed standards and specifications in a non-discriminatory and free of charges. Therefore, JSON is licensed under (F)RAND and Royalty-free basis. Terms and conditions for IPR disclosures can be found in ECMA's webpage. See: http://www.ecma-international.org/memento/Ecma%20IPR%20policies.htm
'The purpose of IPsec is not related to the modelling of business processes. IPsec is primarily an internet protocol designed to enhance security in communications between Public Administrations, and it does not inherently focus on modelling business processes. IPSec reference: https://www.rfc-editor.org/rfc/rfc6071.html'
'the CEF Digital eArchiving project aims to create a model that keeps important information accessible and reusable over long periods of time. The E-ARK specifications are used in this solution for describing the most common principles and requirements for the preservation of information packages. CEF Digital e-archiving: https://digital-strategy.ec.europa.eu/en/activities/earchiving'
The Core Public Service Vocabulary Application Profile is publicly available for implementation and use for free on Joinup's webpage. Therefore, it can be reused by the organisations, administrations, open communities, etc. that developed it. CPSV-AP reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-service-vocabulary-application-profile
'The publiccode.yml specification does not directly address e-accessibility, as it primarily focuses on metadata for cataloguing public sector software. However, by promoting software transparency, reuse, and sharing, publiccode.yml can indirectly support the development of digital public services that adhere to accessibility standards, such as WCAG. The specification could facilitate the discovery and adoption of accessible software components, encouraging developers to prioritise e-accessibility principles in the creation and reuse of public sector software. Publiccode.yaml documentation: https://docs.italia.it/italia/developers-italia/publiccodeyml-en/en/master/index.html'
LDAP is still excellent with authenticating Linux-based applications including many open source solutions, for example: OpenVPN, Jenkins, Kubernetes. It is often used to complement Active Directory (AD) as a directory services protocol. Therefore, it is demonstrated that LDAP has enough market acceptance for its use in the development of products and services. LDAP used with OpenVPN: https://openvpn.net/vpn-server-resources/openvpn-access-server-on-active-directory-via-ldap/
'The purpose of EuroVoc is not related to enabling the secure processing of data. Therefore, this criterion is not applicable to this specification. EuroVoc: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource /dataset/eurovoc'
'ISO 3166-1 provides a collection of codes for the names of countries, dependent territories and special areas of geographical interest, regardless of any specific domain. Therefore, the specification can be implemented in any domain. ISO 3166-1 reference: https://www.iso.org/standard/72482.html '
IPv4 is maintained and developed by IETF which is an international community developing open standards. Additionally, it has support from the different Regional Internet Registries (RIRs) in order to ensure the proper development beyond borders. See: https://www.arin.net/ https://www.ripe.net/ https://afrinic.net/ https://www.apnic.net/ https://www.lacnic.net/
'There are many ways on which customisations can be added to RDF such as the custo graph views provided by GraphDB, or also by creating custom datatypes in order to assign a URI in a controlled namespace. GraphDB Custom Graph View: https://graphdb.ontotext.com/documentation/9.3/free/devhub/custom-graph-views.html'
The purpose of IPv4 is not related to long term preservation of electronic records. Therefore this criterion is considered not applicable to this specification.
'As an internet standard, IPv6 promotes a common framework for communication. This can help facilitate agreements between organisations to define a unique method for communicating. Moreover, the IPsec protocol, which is included in the IPv6 protocol, allows organisations to share information safely. IPv6 IETF: https://www.rfc-editor.org/rfc/rfc2460'
'While genericode itself does not directly ensure or enable data processing accuracy, by adhering to the genericode standard, organisations can establish clear data processing policies and procedures. Standardisation helps reduce inconsistencies and errors in data processing by ensuring that data is represented consistently across different systems and applications. Code List Representation (genericode): https://docs.oasis-open.org/codelist/genericode/v1.0/os/genericode-v1.0-os.html'
"After carrying out information retrieval, an expert group from The Netherlands has been assessing the OData in terms of efficiency. These experts anounced a fast data processing. Expert group's OData analysis: https://www.forumstandaardisatie.nl/open-standaarden/odata"
'The purpose of ShEx is not related to the protection of personal data; therefore, this criterion is not applicable to the specification. ShEx primer document: https://shexspec.github.io/primer/ ShEx Community Group: https://www.w3.org/community/shex/ ShEx Github: https://github.com/shexSpec/spec/issues'
'According to the CEN-CENELEX Guide 8, EN 16234-1 e-CF is available with any restrictions related to (F)RAND. CEN-CENELEC Guide 8 reference, section 5: https://www.cencenelec.eu/media/Guides/CEN-CLC/cenclcguide8.pdf'
'The purpose of OCSP is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification. OCSP reference: https://datatracker.ietf.org/doc/html/rfc2560'
The purpose of PNG is not related to the availability of interfaces with internal information systems. Therefore, this criterion is not applicable to this specification. PNG W3C reference: https://www.w3.org/TR/PNG/ PNG ISO reference: https://www.iso.org/standard/29581.html
'The purpose of OAS is not related to organisational interoperability agreements, therefore this criterion is not applicable to the specification. OAS specification: https://spec.openapis.org/oas/latest.html#openapi-specification OAS in Github: https://github.com/OAI/OpenAPI-Specification/#participation'
PAdES as an electronic signature that uses PDF will proportionate a secure and trustworthy eSignature for the data exchange between citizens and administrations. PAdES ISO reference: https://www.iso.org/standard/67937.html PAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/102700_102799/10277801/01.01.01_60/ts_10277801v010101p.pdf
The specification reduces the administrative burden by allowing public administration to publish online data that can be administrative documents, videos etc. HTML W3C reference: https://www.w3.org/TR/html401/
'ISO/IEC 19944-1 supports the implementation of secure processing of data through its emphasis on security controls, data classification, and data governance. Nonetheless, organisations should complement ISO/IEC 19944-1 with relevant industry standards, best practices, and legal requirements to ensure the secure processing of data within their cloud computing environments. ISO/IEC 19944-1 specification: https://www.iso.org/standard/60545.html'
The purpose of PAdES is not related to the implementation of the once-only principle. Therefore, this criterion does not apply to this specification. PAdES ISO reference: https://www.iso.org/standard/67937.html
ADMS can be found for free along within the European Collaborative Platform, Joinup. ADMS on Joinup: https://joinup.ec.europa.eu/solution/asset-description-metadata-schema-adms/about
'There is a Member state recommending the specification ( Spain ) in its ICT National Catalogue. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards Spain National Catalogue Reference: https://administracionelectronica.gob.es/ctt/verPestanaGeneral.htm?idIniciativa=cccev&idioma=en#.ZC1dvXvP02w'
'The PROV family of documents has not been found included in any open repository/catalogue of standards at national level. PROV Primer document: https://www.w3.org/TR/prov-primer/ PROV Ontology: https://www.w3.org/TR/2013/REC-prov-o-20130430/ PROV Data Model: https://www.w3.org/TR/2013/REC-prov-dm-20130430/'
OWL2 is included in 2 national catalogues of recommended specifications. They belong to the Netherlands and Spain. The National Interoperability Framework (NIF) of these Member States is fully aligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. National catalogue the Netherlands: https://www.forumstandaardisatie.nl/open-standaarden National catalogue Spain: https://administracionelectronica.gob.es/pae_Home/pae_Estrategias/pae_Interoperabilidad_Inicio/pae_Normas_tecnicas_de_interoperabilidad.html#CATALOGOESTANDARES NIFO factsheets: https://joinup.ec.europa.eu/collection/national-interoperability-framework-observatory-nifo/nifo-factsheets
'XSLT include facilities for adapting the output of a transformation to meet local expectations: examples include the formatting of numbers and dates, and the choice of collations for sorted output. XSLT Reference: https://www.w3.org/TR/xslt-30/#imp-def-feature'
'E-ARK CSIP can be found at the webpage of its own development organisation, the European based DILCIS Board. Moreover, the board publishes all the necessary documentation in the github repository. DILCIS Board Github: https://github.com/DILCISBoard/'
'ebXML RegRep is used within the EU TOOP project, which is an enabler of the Once-Only Principle and has currently three pilot studies in progress. A pilot is the Peppol Tool Directory, which stores and indexes data from different providers for searcheability purposes. Once-Only Principle reference: https://ec.europa.eu/isa2/isa2conf18/once-only-principle-project-toop_en Peppol Tool Directory reference: https://directory.acc.exchange.toop.eu/public/locale-en_US/menuitem-about'
'MIME allows for extension through the creation of new MIME specifications and profiles. These extensions can introduce additional content types, headers, or encoding methods to support evolving requirements and technologies in internet communication. MIME specification: https://tools.ietf.org/html/rfc2045'
'This specification is domain-agnostic as it can be implemented or used in any domain. The focus of ISO/IEC 19941:2017 is on the broader aspects of cloud computing interoperability and portability thus, it is applicable across different domains. ISO 19941: https://www.iso.org/obp/ui/en/#iso:std:iso-iec:19941:ed-1:v1:en'
'According to section 4.4 of the ETSI TS 119 512 specification document, the Profile element outlines the technical details of a preservation profile, allowing a client to use the preservation interface to communicate with the preservation service. Full implementation of specific provisions is achieved when combined with its companion documents, ETSI TS 119 511. This combination enhances the visibility of administrative procedures, rules, and services. ETSI TS 119 512 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.02_60/ts_119512v010102p.pdf ETSI TS 119 511 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119511/01.01.01_60/ts_119511v010101p.pdf'
"This specification's releases do not foresee public reviews. While the life cycle of ISO/IEC 7498:1 is completely public, its content is not published on the web. ISO/IEC 7498:1: https://www.iso.org/standard/20269.html"
'SFIA is a framework that is not aligned to any specific platform, provider or industry. Therefore, the specification is platform agnostic. SFIA reference: https://sfia-online.org/en/sfia-8'
The CPSV-AP allows describing public services in a standard human and machine-readable format. This fact fosters the discoverability of the datasets containing the information of public services. Moreover, enhances its reuse and visibility. CPSV-AP Joinup webpage: https://joinup.ec.europa.eu/solution/core-public-service-vocabulary-application-profile/release/22 5-star linked open data: https://www.w3.org/DesignIssues/LinkedData.html On using the core public sector vocabulary (CPSV) to publish a "citizen's guide" as linked data: https://www.researchgate.net/publication/325495548_On_using_the_core_public_sector_vocabulary_CPSV_to_publish_a_citizen's_guide_as_linked_data
'HTTPS is an internet protocol for the data exchange over an Internet network. It supports the first level of maturity defined in the Tim Berners-Lee´s 5 stars Open Data deployment scheme, ""Make your data accessible on the web". Moreover, When a website uses HTTPS, it allows the secure transmission of data between the server hosting the website and the users accessing it. This secure transmission ensures that the data being published, such as web pages, images, videos, documents, and other resources, can be safely transmitted to the users. Tim Berners-Lee 5 star Open Data: https://5stardata.info/en/ '
8 Member States are recommending SMTP in their ICT National Catalogues. These Member States are Croatia, France, Germany, Greece, Malta, the Netherlands, Spain and Sweden. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'ETSI TS 119 512 has been developed to provide services for the long-term preservation of data in general. The specification fosters the implementation of the once-only principle by ensuring data is well preserved and stored, and that it can also be retrieved when needed. ETSI TS 119 512 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.02_60/ts_119512v010102p.pdf'
'One of the main uses of HTTP Cookies is to authenticate when a user is logged in, and with which account they are logged in. Without the cookie, users would need to authenticate themselves by logging in on each page containing sensitive information that they wish to access. Cookies can also be used to save for subsequent use information that the user previously entered into form fields, such as names addresses and passwords. For that matter, this specification helps enabling digital service delivery channels. HTTP Cookies reference: https://datatracker.ietf.org/doc/html/rfc6265#section-1'
CSS v2.1 is a business domain agnostic specification that can be reused in a cross-domain manner. CSS v2.1 W3C reference: https://www.w3.org/TR/2011/REC-CSS2-20110607/
'In Taxes in Europe database, to access the Web service for accessing the VAT rates in the EU, which includes SOAP in combination with the WS-Security standard. Web service for accessing the VAT rates: https://taxation-customs.ec.europa.eu/online-services/online-services-and-databases-taxation/tedb-taxes-europe-database_en'
'Nowadays people entrust their personal data to an increasing number of services, which are connected to their devices and homes. In this sense, the specification explicitly addresses and enables the secure and trustworthy data exchange (see EN 303 645 reference, provision 5.8). EN 303 645 reference: https://www.etsi.org/deliver/etsi_en/303600_303699/303645/02.01.01_60/en_303645v020101p.pdf'
'NFVI is included in the EUOS European catalogue of standards. EUOS reference: https://www.standict.eu/standards-repository'
The purpose of RDF is not related to e-accessibility. Therefore this criterion is considered not applicable to this specification.
UTF-8 is a format involved in data exchange as a key point by encoding data. Facilitating the digital data exchange, the specification helps to avoid the non-digital documentation exchange reducing the administrative burden. UTF-8 eases the digital data exchange between administration and stakeholders, therefore, it is a mean for the reduction of administrative burden.
'OASIS have defined a clear Technical Committee (hereby TC) process where all the stakeholders involved have the opportunity to participate in the development of the specification being formulated. Review process OASIS: https://www.oasis-open.org/policies-guidelines/tc-process-2017-05-26'
Simple Mail Transfer Protocol (SMTP) was defined in 1982 as a method for e-mail transmission. Nowadays, it is still widely used between mail servers for e-mail messages exchange. Therefore, it is demonstrated that SMTP has enough maturity for its use in the development of products and services. SMTP IETF reference: https://tools.ietf.org/html/rfc5321
CSV has documentation regarding Use Cases and Requirements which analyses its efficiency. See: https://www.w3.org/TR/csvw-ucr/
'The purpose of WAI-ARIA is increasing accessibility of web content and applications for a large range of users, either with special needs or without disabilities. Therefore, this specification addresses and enables e-accessibility. WAI-ARIA reference: https://www.w3.org/TR/wai-aria/'
'The SHACL specification ensures the authenticity and authentication of the roles and agents involved in data transactions by establishing comprehensive SHACL access control lists. These lists define the criteria for validating the identity and authorisation of each agent, thereby safeguarding the integrity of the data transactions. "SHACL-ACL: Access Control with SHACL" study: https://link.springer.com/chapter/10.1007/978-3-031-43458-7_4 SHACL-ACL github: https://github.com/SDM-TIB/SHACL-ACL SHACL W3C reference: https://www.w3.org/TR/shacl/'
'As a mark-up language that describes resources in the web, the specification may increase government-to-government reuse of data and therefore can prevent citizens or businesses from providing information multiple times; however, this is not consistently done. DCMI About: https://www.dublincore.org/about/'
SHACL can be used to validate the data of a public administration while published as RDF. Therefore it could foster its comprehensibility. An evidence of this is CELLAR, which is the semantic repository of the Publications Office. CELLAR recognises SHACL as its standard of preference for data validation in the Semantic Web. See: https://publications.europa.eu/en/publication-detail/-/publication/658088eb-c071-11e8-9893-01aa75ed71a1/language-en/format-PDF/source-86108820
'While JSON does not directly relate to e-accessibility, there can be found resource that allow for JSON to create Accessible Rich Internet Applications (ARIA) widgets. Therefore, it can enable e-accessibility if combined with other specifications. JSON specification: https://www.ecma-international.org/wp-content/uploads/ECMA-404_2nd_edition_december_2017.pdf JSON ARIA: https://wiki.mozilla.org/Accessibility/JSON_ARIA'
"The specification is a widely used de-facto standard. Thus, it is sufficiently mature for the development of products and services. Since it's release 1995, IPsec overcame most of its initial problems and has been used by many products and services (see IBM products and services and Oracle Solaris reference). IBM z/OS operating system: https://www.ibm.com/it-infrastructure/z/zos IBM AIX operating system: https://www.ibm.com/it-infrastructure/power/os/aix Oracle Solaris 11: https://www.oracle.com/solaris/solaris11/ List of IPSec Implementations: http://www.mit.edu/~tytso/ipsec/surv9607.html"
ELI is publicly available for its use and implementation within the Publications Office's website . Moreover, it is available for everyone to study with no cost. ELI reference: https://eur-lex.europa.eu/eli-register/about.html ELI Technical Information: https://eur-lex.europa.eu/eli-register/technical_information.html
'UDDI is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). Specifically, UDDI can define the interoperability aspects of the "Service Discovery Component", "Service Discovery Service", "Service Registration Service "and "Service Registry Component" ABBs of the EIRA Technical View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/600'
'While ISO/IEC 7498:1 may not be directly applicable to business process modeling, it is essential for establishing communication standards and protocols in networked systems, given that the concepts and structured approach it embodies can provide valuable insights and principles that can be applied to the modeling, analysis, and improvement of business processes, especially in environments where information systems and networked operations play a critical role. ISO/IEC 7498:1: https://www.iso.org/standard/20269.html'
The purpose of the specification is not related to the preservation of information. Therefore, this criterion is not applicable to the specification. ODF ISO reference: https://www.iso.org/standard/66363.html ODF OASIS reference: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office
The purpose of DNS is not related to secure and trustworthy data exchange. Therefore this criterion is not applicable specification.
There are no Member States recommending LegalDocML in their ICT National Catalogues. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
OWL2 is publicly available for implementation and study for free on W3C's webpage. OWL2 W3C reference: https://www.w3.org/TR/owl2-overview/
SAMM is supported by many public technologists and its own community that are able to contribute on the development of the standard at the same time all the contributors review those updates. SAMM webpage: https://owaspsamm.org/ SAMM documentation: https://github.com/OWASP/samm/blob/master/Supporting%20Resources/v2.0/OWASP-SAMM-v2.0.pdf
"The specification supports multiple physical layer options (such as copper and fibre), enabling customisations based on each organisation's infrastructure. IEEE Std 802.3-2022 Reference: https://ieeexplore.ieee.org/document/9844436"
'The purpose of this Core Vocabulary is not related to providing means for restriction of access to information or data. Therefore, this criterion is considered not applicable to this specification. Core Criterion and Core Evidence Vocabulary reference (v1.0.0): https://joinup.ec.europa.eu/release/core-criterion-and-core-evidence-vocabulary-v100 '
'The Dataspace Protocol is aligned with various European regulations regarding privacy aspects. Some of the regulations include the Data Governance Act (DGA), which aims to make more data available by regulating the reuse of publicly/held, protected data, and the Data Act Proposal (DA-E), which aims to ensure fairness in the digital environment, stimulate a competitive data market, open opportunities for data-driven innovation and make data more accessible. IDSA Rulebook Legal Dimension: https://docs.internationaldataspaces.org/ids-knowledgebase/v/idsa-rulebook/idsa-rulebook/6_legal_dimension Data Governance Act (DGA): https://ec.europa.eu/commission/presscorner/detail/en/ip_22_1113 Data Act Proposal (DA-E): https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32022R0868'
The first version of OWL was released in 2004 which was designed as representation languages for authoring ontologies. Some years later, in 2009, a new W3C working group started to extend OWL with several new features. W3C announced the new version, OWL2, on 27 October 2009. This new version soon found its way into semantic editors such as Protégé and semantic reasoners such as Pelle, so this specification is mature enough for its use. OWL2 W3C reference: https://www.w3.org/TR/owl2-overview/
"OData services return URLs to identify resources requested by clients. Where possible, interoperability increases by exploiting the information found in the route part of the URL. However, attention must be paid to those URLs including custom transformations (query options) and clients must be aware of it in future requests to the identified resource. In this sense any user that imports data needs to check the URL provided by the system since it might contain certain parameters that filter the values (ID's, dates,...) for more information consult the Microsoft guide to import OData values onto powerBI/Excel. Analyze sales data from Excel and an OData feed https://learn.microsoft.com/en-us/power-bi/connect-data/desktop-tutorial-analyzing-sales-data-from-excel-and-an-odata-feed OData reference on extensibility: https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#_Toc31358848"
'When it comes to the preservation mechanisms, ETSI TS 119 512 specifies a data structure "EvidenceExchange", which contains preservation objects and preservation evidences to support seamless export and import from one preservation service to another one, using evidence records; therefore enhancing interoperability between systems and ensuring data portability. ETSI TS 119 512 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.02_60/ts_119512v010102p.pdf'
'The purpose of OCSP is not related to the implementation of the once-only principle. Therefore, this criterion does not apply to this specification. OCSP reference: https://datatracker.ietf.org/doc/html/rfc2560'
The OASIS UDDI Specification Technical Committee in charge of the development of UDDI, operates under RF on RAND Mode of the OASIS IPR Policy. The specification is licensed on a Royalty-free and (F)RAND basis. See: https://www.oasis-open.org/policies-guidelines/ipr https://www.oasis-open.org/committees/uddi-spec/ipr.php
'The specification is included in Spain’s catalogue of recommended specifications, as shown in the official consolidated document BOE-A-2023-16284. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards Spanish Consolidated Legislation: https://www.boe.es/buscar/act.php?id=BOE-A-2023-16284'
'The purpose of JSON is not related to long-term preservation of electronic records. Therefore this criterion is considered not applicable to this specification. JSON specification: https://www.ecma-international.org/wp-content/uploads/ECMA-404_2nd_edition_december_2017.pdf'
'The Semantic Interoperability Community (SEMIC) has established Working Groups. These Working Groups are open to the participation of everyone interested in semantic solution working for public administrations in the Member States or in EU institutions. SEMIC working groups: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/about'
'DAPS is used to provide dynamic, up-to-date attribute information about Participants and Connectors in International Data Spaces. Therefore, its use improves the interoperability, data sovereignity and standardization of the IDS ecosystem, which is important for the visibility of administrative procedures, rules data, and services. DAPS: https://github.com/International-Data-Spaces-Association/IDS-G/tree/main/Components/IdentityProvider/DAPS'
'AMQP can be used as a component within a larger business process management (BPM) system. AMQP can be enabled as an asynchronous communication and message queuing within your BPM system, which can help in orchestrating and automating business processes more efficiently. RabbitMQ AMQP Model Reference: https://www.rabbitmq.com/tutorials/amqp-concepts'
'The Semantic Interoperability Community (SEMIC) develops solutions to help European public administrations perform seamless and meaningful cross-border and cross-domain data exchanges. They develop semantic specifications and interoperability solutions under the ISA² Programme. Specification development process by the ISA Programme: https://joinup.ec.europa.eu/collection/semic-support-centre/solution/core-public-service-vocabulary\x02application-profile/about#8 Detailed document ISA Programme: https://joinup.ec.europa.eu/sites/default/files/document/2016-10 /description_of_a_change_management_release_and_publication_process_for_structural_metadata_specifi cations_developed_by_the_isa_progr.pdf'
'DIDs is already associated with EIRA ABBs in the EIRA Library Of Specifications (ELIS). More specifically, DIDs can define the interoperability aspect of the “Blockchain Ledger” ABB of the EIRA Technical Infrastructure View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /solution/elis/'
'The purpose of TSP is not related to the delivery of multilingual public services. Therefore, this criterion is not applicable to the specification. TSP IETF reference: https://tools.ietf.org/html/rfc3161'
XML is a de-fact standard markup language that is used in a wide variety of solutions, including innovative solutions.
The purpose of Ogg is not related to the delivery of multilingual public services. However, Ogg as an open multimedia container, could add subtitles as text to foster the delivery of multilingual in media files. Ogg XIPH reference: https://xiph.org/ogg/doc/rfc3533.txt
'Joinup offers several services that aim to help e-Government professionals share their experience with each other. Joinup supports them to find, choose, re-use, develop and implement interoperability solutions. CPOV appears in many Joinup entries as a discussion topic, and the specification is distributed and can also be found in the platform. Joinup discussion CPOV: https://joinup.ec.europa.eu/collection/semic-support-centre/solution/core-public-organisation-vocabulary/discussion/boundaries-cpov Joinup distribution CPOV: https://joinup.ec.europa.eu/collection/semic-support-centre/solution/core-public-organisation-vocabulary'
'The purpose of the specification is not related to protect information against unauthorised changes. Therefore, this criterion is not applicable to this specification. XSLT Reference: https://www.w3.org/TR/xslt-30'
'ODRL specification itself is primarily focused on expressing and managing digital rights for content and does not directly address e-accessibility concerns. Nevertheless, implementing ODRL can still take steps to ensure that the systems and content are accessible. This may incorporate accessibility features into user interfaces, ensuring compatibility with assistive technologies, and following best practices for accessible design. W3C specification reference: https://www.w3.org/TR/odrl-vocab/#vocab-core'
'XSLT demonstrates market acceptance through extensive testing, proving its reliability and maturity. Its design prioritises interoperability with standards like HTML, XPath, and XDM, allowing seamless integration into digital solutions. It also efficiently processes large datasets via streaming and supports formats like JSON. There are multiple real use cases where XSLT is used, for example, one scenario can be EFT/EDI transformations using XSLT involve processing large, denormalised XML extractions for tasks like nested regrouping, sorting, and calculations to produce plain text output. Real use cases of XSLT: https://www.w3.org/TR/xslt-21-requirements/#scenarios XSLT References: https://www.w3.org/TR/xslt-30/#xml-versions https://www.w3.org/TR/xslt-30/#streaming'
The Core Public Organisation Vocabulary was released in December 2016. Its first aspiration was to become a common data model for describing public organisations in the European Union. So, CPOV is mature enough for its use in the development of products and services. CPOV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-organisation-vocabulary
'To prevent unauthorised changes, TLS 1.3 employs Authenticated Encryption with Associated Data (AEAD) algorithms. These symmetric encryption algorithms provide both confidentiality and integrity protection. Every data record is authenticated, enabling detection of any tampering. This per-record authentication ensures robust protection against unauthorised changes. TLS 1.3 Record Layer Reference: https://www.rfc-editor.org/rfc/rfc8446.html#appendix-E.2'
'DNS over HTTPS (DoH) usability extends beyond a specific business domain, and it can be employed across various sectors and contexts. DoH can be used by individuals, organisations, and businesses across different industries for securing DNS traffic. Any entity, regardless of the business domain, can benefit from using DoH to protect sensitive information and prevent eavesdropping on DNS traffic. DoH specification: https://datatracker.ietf.org/doc/html/rfc8484'
HTTPS is included within at least 7 Member States' ICT Catalogues (e.g. the Netherlands, Sweden) See CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'The specifications that form the Dataspace Protocol are organised in 5 documents, all of which can be implemented separately, depending on the purpose of implementing the protocol. Specifications can be used for dataspace modelling, common functionalities, cataloguing, contract negotiations and transfer processes. IDSA Dataspace Protocol Specification: https://docs.internationaldataspaces.org/ids-knowledgebase/v/dataspace-protocol/overview/readme'
There are already existing documents and studies about the XACML performance in different environments. An example of this is the research article "A Performance Analysis of the XACML DecisionProcess and the Impact of Caching", which analyses the performance of XACML involved in the decision process of web services developed in the cloud and the impact of caching. Also, there is an article focused on the testing of XACML policies, which provides different approaches to improve effectiveness and effectivity. A Performance Analysis of the XACML DecisionProcess and the Impact of Caching: https://www.researchgate.net/publication/283307011_A_Performance_Analysis_of_the_XACML_Decision_Process_and_the_Impact_of_Caching Approaches for Testing and Evaluation of XACML Policies: https://www.researchgate.net/publication/279192661_Approaches_for_Testing_and_Evaluation_of_XACML_Policies
Throught the example of DFKI using HTML5 that fosters the multilingual web, it can be said that it promotes the former. See: https://www.w3.org/2012/12/html5-cr.html.en
'ISO/IEC 27001 can be found in the EIRA Library of Interoperable Specifications (ELIS), more specifically to the "Security Framework" ABB in the Organizational view. ELIS referenece: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /solution/elis/release/v110'
There is no national or European platform with the specification WS-BPEL available for free.
The last version of the specification was launched in 2013 by the European Telecommunications Standards Institute. The fact of being a European Standard maintained and promoted by ETSI, provides value on its maturity and market acceptance to be used in the development of products.
'The specification does enable the exposure of interfaces. For example, government agencies can use the specification to create machine-readable versions of administrative procedures and rules data, which can then be used to automate various processes, such as the processing of applications and requests, or the generation of reports and statistics. These machine-readable versions can be made available through APIs (Application Programming Interfaces) or other interfaces, which can be used to enable access to public administration services. AKN4EU reference: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/akn4eu'
'Annex E of CIM NGSI-LD API contains an RDF-compatible specification of NGSI-LD meta-model, which facilitates the publication of data on the web and does not require propietary software for the processing of its related data. The standardisation that CIM NGSI-LD API provides promotes interoperability and facilitates the sharing and publication of data on the web in a consistent and understandable manner. GS CIM 009: https://www.etsi.org/deliver/etsi_gs/CIM/001_099/009/01.07.01_60/gs_CIM009v010701p.pdf'
'ISO/IEC 19944-1 can indirectly contribute to the effective management and governance of cloud services, including those related to public administration. By adopting the recommended practices outlined in the specification, organizations can establish clearer governance structures, define service management processes, and enhance data management practices. ISO/IEC 19944-1 specification: https://www.iso.org/standard/60545.html'
The purpose of XACML is not related to the delivery of multilingual public services. Therefore, this criterion is not applicable to the specification. XACML OASIS reference: http://docs.oasis-open.org/xacml/3.0/errata01/xacml-3.0-core-spec-errata01.html
'There is no evidence found that the ISAE 3402 encourages the creation of communities along with the sharing of their data and results on national platforms. ISAE 3402 handbook reference: https://www.ifac.org/system/files/downloads/b014-2010-iaasb-handbook-isae-3402.pdf'
'Registered Organization Vocabulary does not enable the secure processing of data. The main purpose of the specification is to define a standardised way of describing organisations that have gained legal entity status through a formal registration process. Therefore, this criterion is considered not applicable to this specification. Registered Organization Vocabulary reference: https://www.w3.org/TR/vocab-regorg/'
MIME is a business domain agnostic specification that can be reused in a cross-domain way. It can be used for the exchange of files addressing any domain. MIME reference: https://tools.ietf.org/html/rfc2045
'WAI-ARIA enhances assistive technologies to interact with accessibility APIs and can restructure, simplify, stylise, or rescale content to help a different set of users. WAI-ARIA reference, section 1.6: https://www.w3.org/TR/wai-aria/'
'The purpose of IPv4 is not related to the delivery of multilingual services. Therefore this criterion is not applicable to this specification. IPv4 IETF: https://www.rfc-editor.org/rfc/rfc791'
IETF defined the first version of TLS in 1999 and the current version is TLS 1.3 defined in August 2018. This evidences that the specification is mature, in the sense that it has been developed for a sufficient period of time to overcome most of its initial problems.
'Anyone can contribute to OpenTelemetry documentation, which includes improving existing content, creating new content, updating the OTel Registry and improving the code that builds the site. Before you can contribute, you will need to sign the Contributor License Agreement. To contribute, you need to be familiar with the following techs and tools: git, GitHub, Markdown (CommonMark) and YAML. OpenTelemetry Contributing: https://github.com/open-telemetry/community/blob/main/CONTRIBUTING.md'
WS-Security is being used in the Delegated Regulation (EU) N° 885/2013 of 15 May 2013 with regard to the provision of information services for safe and secure parking places for trucks and commercial vehicles See: https://ec.europa.eu/transport/sites/transport/files/themes/its/doc/safe-and-secure-parkings/user_manual_web_service_datexii_upload_v1_1.pdf
DNS is included in the catalogue of recommended specifications of 7 Member States. See CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
"While YAML doesn't guarantee accurate data, its structure and readability can facilitate manual review and integration with data validation tools. Therefore, the specification can contribute to data processing accuracy when used together with other applications or specifications. YAML specification: https://yaml.org/spec/1.2.2/"
8 Member States are recommending JSON in their ICT National Catalogues. See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
After carrying out information retrieval, no document or study has been found assessing the CAdES Baseline profile in terms of efficiency or effectiveness.
'The specification does not explicitly address whether it includes an access control mechanism. Regarding data quality and provenance, the specification likely incorporates elements to ensure data reliability. OGC TrainingDML-AI Standard: https://docs.ogc.org/is/23-008r3/23-008r3.html'
'Up to date, the EN 303 645 specification does not enable digital service delivery channels. Nonetheless, the specification could enable new channels once the EU cybersecurity certification framework for ICT products is consolidated. EU cybersecurity framework reference: https://digital-strategy.ec.europa.eu/en/policies/cybersecurity-certification-framework'
'The support for digital signatures that Domibus offers, which renders possible digitally signed messages, constitutes a mechanism to verify the authenticity and integrity of the data being transmitted. Domibus specification: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/Domibus AS4 specification: http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/profiles/AS4-profile/v1.0/AS4-profile-v1.0.html'
'LDAP is maintained and developed by IETF which is an international community developing open standards. In addition, the Open LDAP Foundation is a community which is centered in the maintenance and the distribution of the open source version of the specification, with the feedback of the community people. Developer community IETF: https://www.ietf.org/about/ OpenLDAP website: https://www.openldap.org/'
'The ESPD is designed to enable e-accessibility, ensuring that it can be used by all users, including those with disabilities or impairments. The ESPD is available in various formats, including electronic forms, and structured data formats such as XML, which can be read and processed by assistive technologies used by people with disabilities. It can also be adapted to diverse users if combined with other specifications such as HTML which has tags to use for this puropse. ESPD business handbook: https://docs.ted.europa.eu/ESPD-EDM/latest/xml_business_handbook.html'
'The Github repository is a developer community that hosts many discussions around UBL implementation in domain-specific business contexts. These discussions also share their data and results and are open to contributions. UBL in Github: https://github.com/oasis-tcs/ubl'
'The Open Data initiative of the Government of Spain mentions the use of the standard NGSI-LD data exchange protocol/API and the extended Smart Data Models for the adoption of the information model defined by the IDS architecture. This is crucial for the technical convergence of the Data Spaces Business Alliance (DSBA). Technical Convergence DSBA: https://datos.gob.es/en/blog/technical-convergence-dsba Data Space Business Alliance (DSBA): https://data-spaces-business-alliance.eu/'
'One of the key features of the ESPD is the digital signature functionality tool, which allows contracting authorities and suppliers to electronically sign and verify the authenticity of the document. The digital signature provides a mechanism to verify that the document has not been tampered with, and that the information contained within it is authentic and accurate. It is important to note that the e-signature functionality is something that is built on top of the ESPD model, and each Member State is responisble of implementing it on their respective procurement digital services. Commission Decision (EU, Euratom) 2017/46 of 10 January 2017 on the security of communication and information systems in the European Commission: https://eur-lex.europa.eu/legal-content/EN/TXT/?qid=1548093747090&uri=CELEX:32017D0046 ESPD business handbook: https://docs.ted.europa.eu/ESPD-EDM/latest/xml_business_handbook.html'
'NUTS has been developed and deployed by the European Commission; therefore, the specification is a European Standard. EUROSTAT reference, NUTS Principles and Characteristics section: https://ec.europa.eu/eurostat/web/nuts/principles-and-characteristics'
'ISAE 3402 is licensed royalty-free and can be certified by any public auditor. ISAE 3402 reference: https://www.ifac.org/system/files/downloads/b014-2010-iaasb-handbook-isae-3402.pdf'
'Within the specification there is section 4.3 that indicates .... such as S/MIME (RFC3851). This section also defines the structure of a REM message bases on MIME format, and a REM message does not exist as a sel-standing object, therefore, justifies the fact of not being technology agnostic. S/MIME Message Specification: https://datatracker.ietf.org/doc/html/rfc8551 ETSI EN 319 532-3 reference: https://www.etsi.org/deliver/etsi_en/319500_319599/31953203/01.02.01_60/en_31953203v010201p.pdf'
Despite the openness provided by eDelivery Governance Space, which purpose is to enable different parties to get involved in the development of the Building Blocks and all their components, a public review is not part of the decision-making-process. See: https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery+SMP+-+1.10
'Domibus is designed to ensure the protection of personal data during the process of electronic message exchange. As an eDelivery Access Point (AP) solution, Domibus follows messaging standards such as the AS4 (Applicability Statement 4) profile of the ebMS (ebXML Messaging Service) standard, which includes features and mechanisms to enhance data security and privacy. Domibus specification: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/Domibus AS4 Profile of ebMS 3.0: http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/profiles/AS4-profile/v1.0/AS4-profile-v1.0.html '
'The publiccode.yml specification does not directly support business process modelling, as its primary focus is on metadata for cataloguing public sector software rather than process documentation. However, by establishing a standard for software documentation, it can indirectly contribute to organisational interoperability. The shared metadata framework allows public administrations to organise and align software-related information, which can complement business process models and support a cohesive approach to delivering European public services. Publiccode.yaml documentation: https://docs.italia.it/italia/developers-italia/publiccodeyml-en/en/master/index.html'
CAdES is independent of any technology or platform. Moreover, it is independent of any environment, so it can be applied to any environment, for example, smart cards, GSM SIM cards, special programs for electronic signatures, etc. CAdES ISO reference: https://www.iso.org/standard/64756.html CAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/101700_101799/101733/02.01.01_60/ts_101733v020101p.pdf
'ISO/IEC Publicly Available Standard (PAS) such as ISO 19944-1 go through a systematic review process every three years, during which the members re-assess the standard and propose updatings. ISO public review guide: https://www.iso.org/files/live/sites/isoorg/files/store/en/PUB100413.pdf '
'The purpose of Domibus is not related to the secure processing of data. Therefore this criterion is not applicable to the specification. Domibus specification: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/Domibus AS4 specification: http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/profiles/AS4-profile/v1.0/AS4-profile-v1.0.html'
'The Open Geospatial Consortium (OGC) provides public support for the specification and manages its maintenance through a community-driven process. The OGC has a dedicated Working Group (WG) for Training and Education, which is responsible for developing and maintaining the Training Data Markup Language. OGC Community: https://www.ogc.org/about-ogc/community/'
The evidence to justify this criterion is reflected in the section "Scope and motivation" of the technical specification, which proves that SHACL positively impacts interoperability. See: https://www.w3.org/TR/shacl-ucr/
'the OAIS reference model does not specifically enable the exposure of interfaces, it instead provides a framework for managing digital objects over the long term, which can support the development of such interfaces by ensuring the preservation and accessibility of digital information. The metadata and descriptive information associated with digital objects can also be used to develop interfaces for accessing the objects, depending on the specific needs and requirements of the organization. OAIS specification: https://public.ccsds.org/Pubs/650x0m2.pdf'
The purpose of SVG is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification. SVG W3C reference: https://www.w3.org/TR/SVG11/
'Verifiable Credentials is developed by W3C, a standard development organisation based in the US, thus, sharing of their data and results in national and/or European platforms is out of their scope. Nevertheless, the specification can contribute to the creation of communities and the sharing of data and results, particularly in the context of digital identity, credentialing, and related applications as they offer a standard for credentials being exchanged, its format, and structure. Verifiable Credentials: https://www.w3.org/TR/vc-data-model/'
'EuroVoc is included in the Controlled Vocabulary ABB in the current EIRA Library Of Interoperability Specifications (ELIS). EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /solution/elis/release/600'
'YAML allows for efficient reuse of relevant information through anchors, aliases, and references. Anchors enable defining reusable content, while aliases let you reuse these anchors throughout the document. Additionally, references can merge different mappings, allowing you to combine and use them at any point, enhancing flexibility and reducing redundancy. YAML specification: https://yaml.org/spec/1.2.2/#3222-anchors-and-aliases '
"Ecma International, The standards development organisation developing JSON, is a European non-profit organisation dedicated to the standardisation of information and communication systems. Ecma's development of standards and technical reports is done in co-operation with the appropriate national, European, and international organizations. Therefore, JSON is a European standard. JSON specification: https://www.ecma-international.org/wp-content/uploads/ECMA-404_2nd_edition_december_2017.pdf"
'TGF is designed to be extensible and customisable, allowing government agencies to tailor the framework to their specific needs and requirements, while still benefiting from the underlying principles and best practices of the framework. For example, TGF principles may be extended to include additional security or privacy aspects that are specific to the operations of a given government agency. TGF specification: http://docs.oasis-open.org/tgf/TGF/v2.0/cs01/TGF-v2.0-cs01.html'
As all the IETF specifications, UTF-8 is licensed on a Royalty-free basis according to the documents “Rights Contributors Provide to the IETF Trust” and ”IETF Trust's Legal Provisions Relating to IETF Documents” See: https://tools.ietf.org/html/rfc3629 https://trustee.ietf.org/
'The ETSI TS 119 612 specification is included in e-signature when implementing eIDAS regulation. In this context, the specification is mentioned to be used in establishment, publication and mantainment of trusted lists. ETSI TS 119 612 eIDAS: https://ec.europa.eu/digital-building-blocks/sites/display/DIGITAL/Standards+and+specifications ETSI TS 119 612: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf'
The rules on European standardisation allow the European Commission to identify information and communication technology (ICT) technical specifications - that are not national, European or international standards - to be eligible for referencing in public procurement. This allows public authorities to make use of the full range of specifications when buying IT hardware, software and services, allowing for more competition in the field and reducing the risk of lock-in to proprietary systems. After being evaluated compliant with the regulation on standardisation 1025/2012, HTTP has been identified by Commission Implementing Decision. During the evaluation process, all the Member States are invited to share their doubts. The positive evaluation of HTTP and its identification is considered an interoperability agreement. See: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en
'Linked Data Event Streams (LDES) primarily focuses on representing and publishing real-time event data on the web using Linked Data principles. It provides a framework for expressing events in a standardized and machine-readable format. While LDES itself is not designed explicitly for modeling business processes, the data it represents can be used as part of a broader ecosystem that involves business process modeling. LDES specification: https://joinup.ec.europa.eu/collection/semic-support-centre/linked-data-event-streams-ldes'
The W3C Royalty-Free IPR licenses granted under the W3C Patent Policy apply to all W3C specifications, including WSDL. See: https://www.w3.org/TR/patent-practice#ref-AC
"All major and minor releases foresee a public review during which collected feedback is publicly visible through DAPS' GitHub, accesible to any user. DAPS: https://github.com/International-Data-Spaces-Association/IDS-G/tree/main/Components/IdentityProvider/DAPS"
SVG is supported by several products and services like WordPress, HTML, or different versions of CSS. Also, it is widely used for the development of the icons with different purposes as logos for webpages or as part of the content of these web pages. Moreover, it is a step further from other graphical representation specifications by allowing a better description and representations of vectors and d mixed vector/raster. SVG W3C reference: https://www.w3.org/TR/SVG11/
"SAML 2.0 is specifically designed to address issues related to the authenticity and authentication of agents (users or systems) involved in data transactions. The specification provides a structured means for an Identity Provider (IdP) to assert claims about a subject (typically a user) to a Service Provider (SP), especially concerning the subject's authentication status and associated attributes. SAML 2.0 Reference: http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-tech-overview-2.0.html"
'OData was approved as an OASIS Standard in 2014 and as an ISO standard in 2017. Currently, there is OData version 4.1. Microsoft, as other corporations (see OData ecosystem reference) and organisations such as the World Health Organization (WHO), are using this specification in some of their systems. Besides, the OData Technical committee is active in terms of new releases. OData Blog: https://www.odata.org/blog/OData-Published-as-an-ISO-Standard/ OData Technical Committee: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=odata#technical OData ecosystem reference: https://www.odata.org/ecosystem/ Microsoft-OData reference: https://docs.microsoft.com/es-es/odata/ WHO reference: https://www.who.int/data/gho/info/gho-odata-api'
'Currently, no national catalogues of member States include ETSI TS 119 512. CAMSS list of standads: https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
After being evaluated compliant with the regulation on standardisation 1025/2012, MIME has been identified by Commission Implementing Decision and included in the European list of ICT Standards for e-procurement. ICT technical specifications: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en
'The ELI system itself is not specifically included in any initiative at the European or National level covering privacy aspects. Therefore, this criterion is considered not applicable to this specification. ELI reference: https://eur-lex.europa.eu/eli-register/about.html'
The specification was produced in 2019. The standard evolution involves many public technologists, policymakers, however, it is an ongoing work that can be further improved. At the same time, it can be implemented for the creation of products and services as part of the improvement process. Although the specification maturity has room for improvement, it is important to consider the option when developing products and services. The Standard for Public Code webpage: https://standard.publiccode.net
There is no national or European platform with the specification PAdES (ISO 14533-3:2017) available for free. However, there are some free documents in Joinup that cover PAdES. PAdES Joinup reference: https://joinup.ec.europa.eu/solution/electronic-signatures-and-infrastructures-esi-pdf-advanced-electronic-signature-formats-pades-part-2
The purpose of this Core Vocabulary is to support the exchange of information between organisations that define criteria and organisations that respond to these criteria by means of evidences. CCCEV reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-criterion-and-core-evidence-vocabulary
'One of the goals of the Verifiable Credentials Data Model is to enable permissionless innovation. To achieve this, the data model needs to be extensible in a number of different ways. For instance, the W3C Community Group has created a document that serves as an informative registry for all known Verifiable Credentials extensions, regardless of its stability. Verifiable Credentials Extensibility: https://www.w3.org/TR/vc-data-model/#extensibility Verifiable Credentials Extension Registry: https://w3c-ccg.github.io/vc-extension-registry/'
There are several CSV conformance validators available. An example is CSV Lint, which provides a conformance validation for its readability. Another example is CSV Validator from The National Archive of United Kingdom. This validator provides tools for validating CSV by using CSV Schema. See: https://csvlint.io/ https://github.com/digital-preservation/csv-validator
The purpose of PNG is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification. PNG W3C reference: https://www.w3.org/TR/PNG/ PNG ISO reference: https://www.iso.org/standard/29581.html
The main objective of the Portable Document Format (PDF) is to allow text format and images to be independent and work for any software, hardware or operating system while transferring. Additionally, PDF is widely used by administrations in order to share their information and data. Fostering the availability of data and information, PDF fosters the data portability by means of documents.
CPOV is publicly available for its use and implementation. Moreover, it is available for everyone to study with no cost on Joinup webpage. CPOV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-organisation-vocabulary
'No Member State includes the ShEx in their national catalogue with Their National Interoperability Framework (NIF) in alignment with the three categories 1. Conceptual model for integrated public servicesprovision, 2. interoperability layers, and 3. interoperability principles. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
'According to principle 3.2 from the E-ARK CSIP specification, information packages should ensure that data and metadata are physically separated from one another in order to allow digital preservation tools and systems to update respective data or metadata portions of an Information Package without endangering the integrity of the whole package, therefore, addressing the implementation of mechanisms to guarantee data integrity. E-ARK CSIP principle 3.2: https://earkcsip.dilcis.eu/#principle3.2:'
'OData is a protocol of querying and sharing, and as such is not supposed to offer long-term preservation of data. Therefore, this criterion is considered not applicable to this specification. OData reference: https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#_Toc31358832'
'The SFIA Foundation provides and organises webinars, conference and trainings where users of country-specific platforms can share their data and results on the use of the SFIA specification. SFIA reference, Get Help section, SFUA partners: https://sfia-online.org/en/get-help/partners'
'10 Member States are recommending the specification in their ICT National Catalogues. SOAP Reference: https://www.w3.org/TR/soap12/'
'Web Services Description Language (WSDL) itself does not provide mechanisms for guaranteeing the authenticity and authentication of the roles or agents involved in data transactions. WSDL is primarily a specification for describing the interfaces and operations of web services, focusing on the technical aspects of communication. W3C WSDL specification: https://www.w3.org/TR/wsdl20/'
'There is no Member State that includes WAI-ARIA in their national catalogue with The National Interoperability Framework (NIF) in alignment with the three categories 1. Conceptual model for integrated public services provision, 2. interoperability layers, and 3. interoperability principles. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards '
'The purpose of Core Location Vocabulary is not related to the restriction of access to information/data. Therefore this criterion is considered not applicable to the specification. Core Location Vocabulary: https://interoperable-europe.ec.europa.eu/collection/semic-support-centre/solution/core-location-vocabulary/release/100'
The purpose of WSDL is not related to e-accessibility. Therefore, this criterion is not applicable to the specification.
XAdES Baseline Profile accomplishes with the European Directive of electronic signature of the European Parliament and the Council to allow the electronic signature through eIDAS, so it can be deducted that the needs are proportionate to the users needs. See: https://www.w3.org/TR/XAdES/
The LegalDocML TC works to advance worldwide best practices for the use of XML within a Parliaments', Assembly's or Congress' document management processes, within courts' and tribunals' judgment management systems, and generally in legal documents including contracts. The specification as can be domonstrated for its implementation in LEOS project and pilot, can ease and foster the visibility of data, administrative rules and ease the decision making process of public administrations. LegalDocML reference: https://www.oasis-open.org/committees/legaldocml/charter.php LEOS: https://joinup.ec.europa.eu/collection/justice-law-and-security/solution/leos-open-source-software-editing-legislation
The specifications promotes innovation as CSV Dialect to simplify the format to be able to describe various CSV dialects. Rewrite, more detail See: https://frictionlessdata.io/specs/csv-dialect/
"The NFVI specification boosts hardware acceleration by using persistent memory resources, which contributes to enabling data portability (see see IEEXplore's report, section 8.3). IEEEXplore's NFV report reference: https://ieeexplore.ieee.org/document/7513857/"
'ISAE 3402 audits can be helpful when it comes to recommending best practices regarding data confientiality and security, thus, making it a standard that facilitates the modelling of business processes. ISAE 3402 handbook reference: https://www.ifac.org/system/files/downloads/b014-2010-iaasb-handbook-isae-3402.pdf'
The implementation of SMP can ease the implementation of the Once-Only principle. Since the specification is related to ease the identification of services and the exchange of data, it can be useful for administrations to reuse and exchange information already available reducing the interactions that users need to do with them. The specification: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505000
'There is no signal of ensuring the protection of personal data management by the specification. Therefore this criterion is considered not applicable to this specification. XSD Reference: https://www.w3.org/TR/2012/REC-xmlschema11-1-20120405/'
'This is an ISO International Standards. In this context, standards are developed by groups of experts called technical committees. These experts are put forward by ISO’s national members. If a user interested in getting involved, they ought to contact their national standards body. Companies and individuals are not eligible to join ISO as members. ISO Technical committees: https://www.iso.org/get-involved.html ISO International Standards: https://www.iso.org/deliverables-all.html#IS'
'The six architectural constraints of REST emphasize the scalability of interactions between components, uniform interfaces, independent deployment of components and the creation of layered architecture to facilitate its usage across business domains. REST reference: https://restfulapi.net/'
'The Authentication Header (AH) and Encapsulating Security Payload (ESP) protocols, which can be used with IPv4, ensure that transmitted data has not been modified by anyone. Additionally, mechanisms such as Access Control Lists (ACLs) ensure that only authorised individuals have access to and can modify the data. AH and ESP protocols: https://www.ibm.com/docs/en/zos/2.1.0?topic=ipsec-ah-esp-protocols IPv4 ACL: https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst2960l/software/15-2_6_e/configuration_guide/b_1526e_consolidated_2960l_cg/m_sec_acls_cg_danube_2960l_cdb.html'
'The GraphQL specifications allows for a wide variety of extensions. For example, the Schema extension which is used to represent a schema that has been extended from an original shcema. GraphQL schema extension: https://spec.graphql.org/October2021/#sec-Schema-Extension'
'AES encryption can indirectly contribute to protecting information against such alterations. However, protection against unauthorised changes is significantly enhanced when AES is used in conjunction with dedicated integrity verification mechanisms like MACs (Message Authentication Codes). This combination ensures both the confidentiality and integrity of the data, making it more secure against tampering and unauthorised modifications. Message Authentication Codes (MAC) specification reference: https://csrc.nist.gov/projects/message-authentication-codes Geeksforgeeks AES reference: https://www.geeksforgeeks.org/advanced-encryption-standard-aes/ AES Standard Reference: https://csrc.nist.gov/pubs/fips/197/final'
'Data protection encompasses data confidentiality, integrity and access control. NFVI proposes specific provisions based on other specifications. These provisions depends on each use case. Some of these data protection techniques are Transport Layer Security (TLS), Internet Protocol Security (IPSec) or Secure Shell (SSH). NFVI Deliver, Infrastructure Overview section 6.7: https://www.etsi.org/deliver/etsi_gs/NFV-INF/001_099/001/01.01.01_60/'
This Core Vocabulary is a reusable and extensible data model for harmonising the way public services are described in a machine-readable format. CPSV-AP reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-service-vocabulary-application-profile
'Open Systems Interconnection (OSI) is not related to data publication, therefore the criterion is not applicable. OSI reference https://www.iso.org/standard/20269.html'
Even though the specification defines conformance criteria, no testing mechanism or tool has been found to validate an SMP implementation. The specification: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505000
Even though the specification is not listed in catalogues of the European Standardisation (CEN, CENELEC, ETSI), the OpenPM2 is highly recommended and promoted within European organisations. It is published within the Publications Office website, and also it is included within ISA2 catalogue of solutions, which can be considered as a set of solutions (specs included) that are standardised at the European level. Publication Office of the European Union: https://op.europa.eu/en/home OpenPM2 reference: https://op.europa.eu/en/publication-detail/-/publication/ac3e118a-cb6e-11e8-9424-01aa75ed71a1/language-en/format-PDF/source-search ISA2 Solution Page: https://ec.europa.eu/isa2/solutions/open-pm2_en
"EU Member States' trusted lists were established in the EU and aimed primarily at supporting the validation of advanced electronic signatures supported by a qualified certificate and advanced electronic signature supported by both a qualified certificate and by a secure signature creation device, as far as they included as minimum trust service probided supervised/accredited for issuing qualified certificates. This method can explicitly address and enable the secure and trustworthy exchange of data as it is using an advanced electronic signature which is supported by a qualified certificate and a secure signature creation device. ETSI TS 119 612 specification: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf "
'The purpose of RDF is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification. RDF primer document: https://www.w3.org/TR/rdf11-primer/'
The purpose of LDAP is not related to the comprehensibility of administrative information, data or services. Therefore, this criterion is not applicable to this specification. LDAP IETF reference: https://tools.ietf.org/html/rfc4511
'The purpose of ETSI TS 119 612 is not related to enabling the visibility of administrative procedures, rules, data and services. Therefore this criterion is not applicable to the specification. ETSI TS 119 612: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf'
XSD 1.1 is an Open specification which is implied in the validation of XML documents. As XML is a de-facto standard implied in in the creation of solutions, including innovative ones, XSD is also fostering the creation of innovative solutions.
'OData is tied up to RESTful APIs communication. Although the OData service declares its own data model in a machine-readable form, which allows customers to interact with the service on a generic basis, OData relies on RESTful APIs in order to be implemented. OData reference: https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#_Toc31358832'
'SOAP 1.2 is a messaging protocol for exchanging information in a structured way, it provides endpoints that foster the availability of interfaces containing data from internal information systems of a public administration. SOAP Reference: https://www.w3.org/TR/soap12/ Differences in SOAP Versions: https://www.ibm.com/support/knowledgecenter/en/SSAW57_8.5.5/com.ibm.websphere.nd.multiplatform.doc/ae/cwbs_soapverdiffs.html'
'GITB TDL does not deal with personal data protection given that its purpose is to provide a language for interoperability and conformance testing. Therefore this criterion is not applicable to this specification. GITB TDL reference: https://www.itb.ec.europa.eu/docs/tdl/latest/introduction/index.html#introduction'
'The conformance of implementations of the AKN4EU specification can be assessed using a number of different tools and methods. One approach is to use validation tools that check the syntax and structure of documents to ensure that they conform to the specification. Another approach is to conduct interoperability tests to ensure that systems can properly exchange documents using the specification. Regarding the conformance of the implementation: https://ec.europa.eu/isa2/solutions/nifo_en. AKN4EU reference: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/akn4eu'
The purpose of JSON is not related to long-term preservation of electronic records. Therefore this criterion is considered not applicable to this specification.
' By testing the requirements established in ETSI TS 119 612, which aims to enable a trusted list for validating the status of services, the specification can help to enhance and upgrade the delivery of digital public services. ETSI TS 119 614-1 reference: https://www.etsi.org/deliver/etsi_ts/119600_119699/11961401/01.01.01_60/ts_11961401v010101p.pdf'
'"At the moment of performing the assessment, Linked Data and Open Data repositories and initiatives are a key point, and public administrations are putting efforts to develop a cross-border environment for open data exchange and reuse. Many initiatives and projects are raising using RDF as a foundation to collide their purpose and objectives. The creation of Linked Open Data solutions can be considered as innovative solutions as they help to evolve the eGoverment. RDF primer document: https://www.w3.org/TR/rdf11-primer/'
'ISO 3166-1 can enable visibility of administrations when combined with other specifications, notably Internet protocols (e.g. Domain Name System, DNS) or those specifications inherent to the interface of a given public service. For example, the specification prompts visibility of administrations in e-procurement (see CEF Digital home reference, eProcurement section) by allowing, for instance, the display of data associated to the country or territory where a user is submitting an ESPD (European Single Procurement Document) form. ISO 3166-1 reference: https://www.iso.org/standard/72482.html Internet Assigned Numbers Authority (IANA) reference, DNS section: https://www.iana.org/domains CEF Digital home reference, eProcurement section: https://ec.europa.eu/digital-building-blocks/wikis/display/CEFDIGITAL/eProcurement?msclkid=1d426d24aa8311ec89f38d676363e47d ESPD reference, Legal framework and context section: https://docs.ted.europa.eu/ESPD-EDM/3.0.1/xml_business_handbook.html#_i_1_1_legal_framework_and_context'
'The purpose of DQV is not related to the secure processing of data. Therefore, this criterion is considered not applicable to the specification. DQV reference: Data Quality Vocabulary: https://www.w3.org/TR/vocab-dqv/'
The purpose of FTPS is not related to the delivery of multilingual public services. Therefore, this criterion is not applicable to this specification. FTPS IETF reference: https://tools.ietf.org/html/rfc4217
"The purpose of the Core Location Vocabulary is to capture the fundamental characteristics of a location, represented as an address, a geographic name or geometry. It was developed from November 2011 until February 2012. It had some updates, and it was finally published in May 2012. In addition, in April 2021, version 2.0.0 was released after a series of five webinars. The latest version dates to February 2024, when the editors' draft of version 2.1.0 was released for public review. However, the 1.0.0 version is one of the most importants because the combination of Core Business, Core Location and Core Person Vocabulary. This fact shows that CLV is mature enough for its use in the development of products and services. In addition, all specifications produced by SEMIC follow the versioning rule described by the SEMIC Style Guide. SEMIC Style Guide: https://semiceu.github.io/style-guide/1.0.0/gc-publication-conventions.html#sec:pc-r3 Core Location Vocabulary: https://interoperable-europe.ec.europa.eu/collection/semic-support-centre/solution/core-location-vocabulary/release/100"
'The effectiveness of OpenTelemtry is often evaluated through various means, including practical implementations and pilot projects. For instance, a 2024-paper about network insights in OpenTelemetry explores the integration of network telemetry data into OpenTelemetry, aiming to provide a holistic understanding of application performance and detect network-related issues. The resulting enhancements empower the system to offer insights into latency, network component processing time, and their correlation with requests and existing traces, which proves the effectiveness of the specification. Network insights in OpenTelemetry: https://eprints.ost.ch/id/eprint/1165/'
The purpose of DNS is not related to long term preservation of electronic records. Therefore this criterion is considered not applicable to this specification.
The purpose of this document is not related to reduce administrative burden. However, it encourages and enables the continued expansion of the Web as a medium for the exchange of data. Best Practices cover different aspects related to data publishing and consumption, like data formats, data access, data identifiers and metadata. Therefore, this criterion is considered not applicable to this specification. W3C Reference: https://www.w3.org/TR/dwbp/
PAdES Baseline profile does not define a data model, but defines a set of conformance levels that have to be taken into account when creating electronic signatures applications over PDF format. Thus, PAdEs Baseline Profile is not defining a cross-sector reusable data model.
'IPv4 is developed by IETF which is based in the USA, thus the specification cannot be regarded as a European Standard. However, the Réseaux IP Européens (RIPE) organisation act as the Regional Internet Registry (RIR) providing global Internet resources and related services (IPv4, IPv6 and AS Number resources) to members in his service region. RIPE organisation: https://www.ripe.net/'
As most of the vocabularies, DCAT reuses several existing ones (e.g. "adms", "foaf", DCAT) and the Resource Description Framework (RDF). This results in a dependency that can hamper interoperability, especially in the case where new releases of the reused vocabularies are not backward compatible.
'The REST standard is recommended in the national catalogue of Slovakia and Finland. Joinup reference: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards Finland national catalogue: https://joinup.ec.europa.eu/sites/default/files/inline-files/Finland%20Factsheet%20Validated.pdf Slovakia national catalogue: https://joinup.ec.europa.eu/sites/default/files/inline-files/Slovakia%20Factsheet_0.pdf'
'No initiatives has been found related to cover privacy aspects at European or National level. Therefore, this criterion is not applicable to the specification. XHTML W3C reference: https://www.w3.org/TR/xhtml1/'
JPEG is a valuable image format for sharing information through the internet between administrations and stakeholders in a graphical manner. Allowing sharing data and information the standard foster the visibility of administration data and services. Fostering the collaboration between public administrations, the specification eases the decision-making process of institutions. JEPG ISO reference: https://www.iso.org/standard/18902.html JPEG public reference: https://jpeg.org/jpeg/
The specification is included in 5 Member States' catalogues of recommended specifications. Examples of Member States including CAdES in their catalogues are France or Spain.See: See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'ODRL is a standard language that makes digital content rules clear, uniform and easy to automate across systems ensuring transparent and controlled access to content or services. ODRL also provides a flexible and interoperable information model, vocabulary, and encoding mechanisms for representing statements about the usage of content and services. By implementing it, enables visibility of administrative procedures, rules data, and services depending on the implementation and usage within different systems and applications. W3C specification: https://www.w3.org/TR/odrl-vocab/#vocab-core'
By allowing the exchange of digital graphics, it improves the representation of information avoiding sharing non-digital documents and therefore helps the reduction of the administrative burden. SVG W3C reference: https://www.w3.org/TR/SVG11/
'The specification acts as an interface and enables the business transaction level data being shared and reused in different systems - internal or external. https://unece.org/fileadmin/DAM/cefact/cf_forums/2019_Geneva/Conf_AccountAudit/PPT_1_2_XBRL_Koskentalo.pdf http://www.xbrl.org/GLWGNotes/XBRL-GL-WGN-FAQ-2007-08-01.htm '
'Although the specification has been implemented in some projects at European level, there is no evidence of the inclusion of the specification in an open repository or catalogue of standards at European level. List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
'There are no Member States recommending ETSI TS 119 432 in their ICT National Catalogues. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards '
The purpose of Ogg is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification. Ogg XIPH reference: https://xiph.org/ogg/doc/rfc3533.txt
'The purpose of DPV is not related to the long-term preservation of information; therefore, this criterion is not applicable to the specification. DPV specification: https://w3c.github.io/dpv/primer/'
IPv4 is publicly available for implementation and use, and therefore for everyone to study, for free on IETF webpage. See: https://tools.ietf.org/html/rfc791 https://tools.ietf.org/html/rfc1349 https://tools.ietf.org/html/rfc2474 https://tools.ietf.org/html/rfc6864
OWL2 is an extension of RDF for accessing, importing, sharing and reusing public ontologies. Using OWL2 helps to reduce the administrative burden by easing the publication and reusing the administration's data. _x000D_ _x000D_ OWL2 W3C reference:_x000D_ https://www.w3.org/TR/owl2-overview/
The purpose of Xforms is not related to long term preservation of electronic records. Therefore, this criterion is considered not applicable to this specification. Xforms 2.0 W3C reference: https://www.w3.org/community/xformsusers/wiki/XForms_2.0
'The specification aggregates data from multiple UI components in order to not repeat code or queries to get the desired data. GraphQL includes reusable units called fragments which let you construct sets of fields, and then include them in queries where you need to. GraphQL Multiple UI Site: https://graphql.org/learn/queries/#fragments'
There are existing documentation and studies assessing and analysing the performance of IPsec in different contexts and application areas. For instance ENISA provides documentation recommending the use of IPsec in order to improve security. See: http://ijns.femto.com.tw/contents/ijns-v20-n5/ijns-2018-v20-n5-p811-819.pdf https://pdfs.semanticscholar.org/8971/9848f632259138d5d4b1052ad24ede803625.pdf https://www.enisa.europa.eu/publications/algorithms-key-sizes-and-parameters-report/at_download/fullReport https://www.researchgate.net/publication/228437109_Interoperability_Issues_for_VPN_IPsec_Solutions
"There are multiple mentions in the specification's document of access points but none about a mechanism to control the access. SMP OASIS reference: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505009"
'The protocol aims at supporting electronic signatures and electronic seals, including qualified electronic signatures and qualified electronic seals according to the Regulation (EU) No 910/2014 of the European Parliament and of the Council of 23 July 2014 on electronic identification and trust services for electronic transactions in the internal market and repealing Directive 1999/93/EC (the eIDAS Regulation). Regulation (EU) No 910/2014: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=celex%3A32014R0910 Directive 1999/93/EC: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:31999L0093'
'TGF has not been found to be included in an open repository/catlogue of standards at national level. TGF specification: http://docs.oasis-open.org/tgf/TGF/v2.0/cs01/TGF-v2.0-cs01.html'
'CLV is already associated to EIRA ABBs in the EIRA Library of Interoperability Specifications (ELIS). More specifically, Core Location Vocabulary can define the interoperability aspects of the "Controlled Vocabulary", "Data", "Data Model", "Hash Code", "Linked Data", "Linked Open Data", "Metadata" and "Open Data" ABBs of the EIRA Semantic View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/v610 Core Location Vocabulary: https://interoperable-europe.ec.europa.eu/collection/semic-support-centre/solution/core-location-vocabulary/release/100'
'TGF is designed to be flexible and modular, which means it can be implemented in a partial or phased manner. The TGF approach allows government and agencies to adopt the parts that are most relevant and beneficial to them. TGF specification: http://docs.oasis-open.org/tgf/TGF/v2.0/cs01/TGF-v2.0-cs01.html'
'The purpose of SAREF is not related to enabling the secure processing of data. Therefore, this criterion is not applicable to this specification. SAREF: https://saref.etsi.org/core/v3.1.1/ '
As an internet protocol for data exchange, FTPS can be used for secure exchange of documents over the Internet, which can reduce administrative burden. Moreover, FTPS can avoid the exchange of non-digital documents that are generally source of administrative burden. FTPS IETF reference: https://tools.ietf.org/html/rfc4217
'The Spanish data protection agency is recommending DoH for its use in data confidentiality verification, to mitigate the risk of data interception and tampering. Spanish data protection agency: https://www.aepd.es/guides/technical-note-dns-privacy.pdf'
ODRL is maintained by W3C which is an international community developing open standards. W3C specification reference: https://www.w3.org/TR/odrl-vocab/#vocab-core
'ETSI TS 119 612 provides a common time-stamping protocol and token profiles for a Trusted List Scheme Operator (TLSO) to provide information on the status and history of Trusted Service Provider (TSP) services. Since it has had two major versions it would be acceptable to consider it has a sufficient market acceptance for its use. ETSI TS 119 612 specification: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf'
'The iCalendar specification is a widely adopted and standardized format for representing calendar data, making it suitable for applications in different industries and sectors due to its interoperability and compatibility with different calendaring systems and services. iCalendar specification: https://www.rfc-editor.org/rfc/rfc5545'
'ETSI TS 119 512 is maintained by ETSI, one of the European Agencies for Standardisation. About ETSI: https://www.etsi.org/about ETSI TS 119 512 Working group: https://portal.etsi.org/webapp/workprogram/Report_WorkItem.asp?WKI_ID=61427'
Different documents and studies are assessing the effectiveness and efficiency of the SVG while rendering images and textures. Also, there are other studies and documentation about the usage of the specification in another context such as the creation of graphical content for comics, even though it is not under the scope of this assessment it can demonstrate the potential of SVG for graphical content. eCommons: Feature Based-Textures: https://ecommons.cornell.edu/handle/1813/5648
'SAREF is not included in any national catalogue of recommended specifications whose Member State NIF has a high performance on interoperability according to NIFO factsheets. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards '
XSLT is not related to fostering the creation of innovative solution.
8 Member States are recommending CSS2 v2.1 in their ICT National Catalogues. This Member States are Croatia, France, Malta, the Netherlands, Norway, Poland Spain and Sweden. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'EIRA supports the whole data publication process by providing Semantic building blocks representing data that can be related to the application services in technical view. By providing this traceability, the EIRA supports the creation of solutions that can be used for publication of data in the web. EIRA reference: https://interoperable-europe.ec.europa.eu/collection/european-interoperability-reference-architecture-eira /solution/eira/release/610'
The purpose of XSD 1.1 is not related to long-term preservation of electronic documents. Therefore this criterion is considered not applicable to this specification.
DCAT is already associated to EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, DCAT can define the interoperability aspects of the "Data Publication Component" and "Data Publication Service" ABBs of the EIRA Semantic View. See: https://joinup.ec.europa.eu/sites/default/files/distribution/access_url/2019-03/76cb237b-0de8-464c-84ca-1327945eac3e/EIRA_v3_0_0_Overview.pdf
'The "The Advanced Encryption Standard Algorithm Validation Suite (AESAVS)" document offers a guide on how to test the Advanced Encryption Standard. In this sense, it specifies the procedures involved in validating implementations of the Advanced Encryption Standard (AES) algorithm in FIPS 197 : Advanced Encryption Standard. The AESAVS is designed to perform automated testing on Implementations Under Test (IUTs). In addition, NIST has developed a validation program to test implementations for conformance to the algorithms in this standard. AESAVS Test guidelines: https://csrc.nist.rip/groups/STM/cavp/documents/aes/AESAVS.pdf Cryptographic Module Validation Program (CMVP) Reference: https://csrc.nist.gov/projects/cryptographic-module-validation-program AES Standard Reference: https://csrc.nist.gov/pubs/fips/197/final'
'OSI is included in an open repository/catalogue of standards at national level, Spain. OSI in Spainish standarization body UNE https://www.une.org/encuentra-tu-norma/busca-tu-norma/norma/?c=norma-une-en-27498-1989-n0022067 OSI reference https://www.iso.org/standard/20269.html'
'As ETSI TS 119 614-1 was released in 2016, it has 2 years of maturity and can be proof that demonstrates it has overcome possible difficulties. ETSI TS 119 614-1 reference: https://www.etsi.org/deliver/etsi_ts/119600_119699/11961401/01.01.01_60/ts_11961401v010101p.pdf'
'The purpose of this core Vocabulary is not related to ensuring the protection of personal data managed by Public Administrations. Therefore, this criterion does not apply to this specification. CPSV-AP Joinup webpage: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/core-public-service-vocabulary-application-profile/release/22'
'AMQP specification provides SASL authentication mechanisms. By authenticating the client, the system can then determine what level of access to grant. OASIS AMQP Reference: http://docs.oasis-open.org/amqp/core/v1.0/amqp-core-complete-v1.0.pdf'
'The application of the once-only principle in all EU Member States public administrations aims at reducing the administrative burden. To achieve this, interoperability between public administrations is a sine qua non condition. The specification allows cross-domain single sign-on, which reduces the administrative burden of the system administrators and the users. By using SAML 2.0, avoid the user to deal with several credentials nor provide information twice. SAML 2.0 Reference: http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-tech-overview-2.0.html'
The specification is included in 6 Member States' catalogues of recommended specifications. Some examples of Member States including IPv4 on their catalogues are the Netherlands or Sweden. See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
CAMSS Assessment of RDF EIF Scenario v1.0.0
'IEEE Std 802.3-2022 can be mapped to the EIRA Library of Interoperability Specifications (ELIS) in the "Local Area Network", “Physical Communication Infrastructure”, “Firewall”, “Physical Computing Infrastructure”, "Private subnetwork" and “Physical Network Infrastructure” under Technical Infrastructure view. IEEE Std 802.3-2022 Reference: https://ieeexplore.ieee.org/document/9844436'
'OAS can be a good visibility enabler when it comes to documenting and creating new APIs. Performing code generation for documentation, clients and servers, OAS contributes to the visibility of administrative procedures given that it facilitates APIs implementation, improving understandability and interaction for clients. OAS specification: https://spec.openapis.org/oas/latest.html#openapi-specification OAS in Github: https://github.com/OAI/OpenAPI-Specification/#participation '
JSON highly supports Tim Berners Lee's 5 star schema for open data. The adoption of JSON fosters the publication of data as open data by means of providing structured data and the usage of non-proprietary formats. Moreover, it helps to link data by means of embedding metadata. Moreover, there is an existing extension of JSON which aims to help and support the Linked Open Data environments. The extension has been developed by the W3C working group specifically in charge of JSON-LD development. Additionally, the W3C has developed a syntax for RDF serialisation using JSON, and JSON-LD is recommended. See: https://www.w3.org/community/json-ld/ https://json-ld.org
There are no disclosures of ISO IPR Database to identify the licensing under the specification. ISO 12639:2004 (TIFF/IT) is not listed in ISO/IEC/ITU Common Patent policy, so it cannot be confirmed that the specification is licensed on a royalty-free basis. ISO patents: https://www.iso.org/iso-standards-and-patents.html ISO standards and patents IPR database: http://isotc.iso.org/livelink/livelink/13622347/Patents_database.xls?func=doc.Fetch&nodeId=13622347
The purpose of the specifications is not related to the comprehensibility of administrative information, data or services. Therefore, this criterion is not applicable to this specification. SMTP IETF reference: https://tools.ietf.org/html/rfc5321
'The purpose of genericode is not related to e-accessibility. Therefore, this criterion is considered not applicable to this specification. Code List Representation (genericode): https://docs.oasis-open.org/codelist/genericode/v1.0/os/genericode-v1.0-os.html'
'ODRL is designed to be extensible, meaning that users can introduce custom elements, semantics, and vocabulary to meet their specific requirements. This extensibility allows for the adaptation of ODRL to a wide range of use cases and industries. A clear example of customizations is Core Vocabularies, which define a set of general requirements that could fit in any context and allow for the customization to fit specific business requirements in the implementation. W3C specification: https://www.w3.org/TR/odrl-vocab/#vocab-core'
The purpose of FTP is not related to the definition of a data model. Therefore this criterion is not applicable to this specification. See: https://tools.ietf.org/html/rfc959
Having checked the documentation included in point 2.2.1, the conclusion has been reached of the “RDA Wheat Data Interoperability Guidelines” specification not being foreseen to be transposed into a European standard within a reasonable time period.
XAdES Baseline Profile is included in the ETSI’s catalogue of standards. As ETSI is considered an official standardisation organisation, it can be considered that the specifications are included in a supra-national catalogue. See: https://www.etsi.org/deliver/etsi_ts/103100_103199/103174/02.02.01_60/ts_103174v020201p.pdf https://www.etsi.org/standards
'The specification is included in 6 Member States catalogues of recommended specifications. This Member States are Croatia, France, Germany, Netherlands, Norway and Sweden. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards'
The purpose of this core Vocabulary is not related to the availability of interfaces with internal information systems. Therefore, this criterion does not apply to this specification. CPSV-AP reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-service-vocabulary-application-profile
ADMS is publicly available for implementation and study for free on W3C's webpage. ADMS Specification W3C: https://www.w3.org/TR/vocab-adms/ ADMS in Joinup: https://joinup.ec.europa.eu/solution/asset-description-metadata-schema-adms/about
"The ELI Governance Rules Document outlines that decisions are reached through working group discussions and consensus, with no explicit provision for a public review process. While there isn't a formal mechanism like public consultations, the evolution of specifications is driven by the consensus among participants, who represent the Member States. ELI reference: https://eur-lex.europa.eu/eli-register/about.html Governance Rules: https://eur-lex.europa.eu/content/eli-register/governance_rules.pdf"
HTTP 1.1 is maintained by IETF which is an international community developing open standards. See: https://www.ietf.org/about/
CAMSS Assessment of IPv4 EIF Scenario v1.0.0
The purpose of this document is not related to the e-accesibility. Therefore, this criterion is not applicable to the specification. W3C reference: https://www.w3.org/TR/dwbp/
'DNS has some core functionalities that can not be implemented separately. Nonetheless, the specification has beed developed to support some requirements that are not mandatory but recommended. DNS IETF reference: https://datatracker.ietf.org/doc/html/rfc8499 Domain Names - Implementation and Specification: https://tools.ietf.org/html/1035'
'The specification is maintained by International Data Spaces Global (IDS-G) working groups and any user can contribute by proposing discussions on the IDS-G GitHub Discussion channel. IDS-G Discussions: https://github.com/International-Data-Spaces-Association/IDS-G/discussions IDSA Working Groups: https://internationaldataspaces.org/make/working-groups-and-task-forces/'
'Better Regulation Guidelines and Toolbox is independent from any software, hardware, or operating system since it is a specification for lawmaking. It can be used and applied independently from other standards, or software requirements. Better Regulation Guidelines and Toolbox reference: https://commission.europa.eu/law/law-making-process/better-regulation/better-regulation-guidelines-and-toolbox_en Better Regulation Toolbox reference: https://commission.europa.eu/document/download/9c8d2189-8abd-4f29-84e9-abc843cc68e0_en?filename=BR%20toolbox%20-%20Jul%202023%20-%20FINAL.pdf'
'The specification does not include any reference related to the possibility of being partially used, so it can be asumed CSV has to be used as a whole. CSV reference: https://datatracker.ietf.org/doc/html/rfc4180'
'ETSI TS 119 612 is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, ETSI TS 119 612 can define the "e-Signature Creation Service", the "e-Signature Verification and Validation Service" ABB and "Trust Service Provisioning Component" ABB of the EIRA Technical view. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/v500'
'Registered Organization Vocabulary provides a foundational set of terms for describing legally registered organisations, it is designed to be flexible and allows for customisation through the creation of application profiles. The application profiles enables the vocabulary to be adapted to specific needs and data exchange scenarios by incorporating external vocabularies and defining additional rules and terms. Registered Organization Vocabulary reference: https://www.w3.org/TR/vocab-regorg/'
The Standard for Public Code is not included in any Member States' catalogues of recommended specifications. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'Douglas Crockford was the creator of JSON. The system was sold to Sun Microsystems, Amazon.com and EDS. The website of the specification was launched in 2002. JSON reuses conventions from other programming languages, in consequence, many libraries of programming use it. Therefore, it is demonstrated that JSON has enough maturity and market acceptance for its use in the development of digital solutions and services. JSON.org: https://www.json.org/json-en.html'
The purpose of EuroVoc is to facilitate the processing of data of administations mainly European but also National. By allowing to make the data available to other persons or organisations, the EuroVoc Contributes to the development of eGovernment reducing the administrative burden. EuroVoc webpage: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/eurovoc
'The specification can help to define the framework for working within the organisation regarding data and information security. It also can help to establish a common view and method between administrations providing public services to ensure the proper treatment of information and how it should be done. ISO/IEC 27001 reference website: https://www.iso.org/standard/54534.html ENISA reference: https://www.enisa.europa.eu/topics/threat-risk-management/risk-management/current-risk/laws-regulation/rm-ra-standards/iso-iec-standard-27001 '
'UDDI appears in the Comission Implementing Regulation of 20 November 2018 amending Commission Regulation (EC) No 416/2007 concerning the technical specifications for Notices to Skippers. The WS-I Basic Profile 1.1. guarantee "interoperability guidance for a core set of non-proprietary web services specifications". One of the most relevants standards which is mentioned is UDDI. Comission Implementing Regulation of 20 November 2018 amending Commission Regulation (EC) No 416/2007 concerning the technical specifications for Notices to Skippers: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A02007R0416-20181229&qid=1712224257609'
'Solace provides a AMQP Protocol Conformance Validation Tool to validate AMQP implementations. AMQP 1.0 Protocol Conformance: https://docs.solace.com/API/AMQP/AMQP-Protocol-Conformance.htm'
"The Functional Requirements section of IDSA's Rulebook describes the mandatory functional requirements as well as optional elements for building trusted data spaces. The core function of a data space is to create secure data exchanging spaces and to negotiate available data contracts for enterprises, all of which is provided by the Dataspace Protocol. IDSA Functional Requirements: https://docs.internationaldataspaces.org/ids-knowledgebase/v/idsa-rulebook/idsa-rulebook/3_functional_requirements"
The European Legislation Identifier (ELI) is a system to make legislation available online in a standardised format, so that it can be accessed, exchanged and reused across borders. As can be found within the European Data portal, the ELI is used by the EU Open Data Portal to describe datasets from MS that have already implmented the specification. ELI reference: https://eur-lex.europa.eu/eli-register/about.html EU Open Data portal Examples: https://data.europa.eu/euodp/en/data/group/eli?groups=eli
SAML 2.0 is a format that allows seamless cross-border interoperability between systems, independently of existing implementations. To demonstrate this fact is worth to take into account that in the context of Connecting Europe Facility (CEF), the CEF eID Building Block has been developed to support the (eiDAS) regulation. This building block includes technical specifications composing the “eiDAS eiD profile”. Among these specifications, the eiDAS SAML Attribute Profile defines the SAML 2.0 attributes to be used for the assertion of natural and legal person identity between eIDAS nodes. See: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32013R1316 https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32015R1501https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eID https://joinup.ec.europa.eu/sites/default/files/document/2015-11/eidas_interoperability_architecture_v1.00.pdf
'IPsec allows the exchange of data between systems and is compatible with both versions of the Internet Protocol, IPv4 and IPv6. Therefore it prevents the storage of data in silos that are incompatible with one another. IPSec reference, About IPSec, Summary: https://datatracker.ietf.org/doc/html/rfc4301#section-1.1'
'ELI is not included in any national catalogue of recommended specifications whose Member State NIF is fully aligned with at least 2 out of 3 sections of the EIF according to NIFO factsheets. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards'
'Odata is included in 3 national catalogues of recommended specifications. They belong to France, Malta and The Netherlands. The National Interoperability Framework (NIF) of these Member States varies when aligned with the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. National catalogue France: http://references.modernisation.gouv.fr/sites/default/files/Referentiel_General_Interoperabilite_V2.pdf National catalogue Netherlands: https://www.forumstandaardisatie.nl/open-standaarden/lijst NIFO factsheets: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public-administration-factsheets-2021'
'The ETSI and any of its committees, in charge of the development of NFVI, operates under the ETSI Intellectual Property Rigths (IPRs) and IPR Policy. The specification is licensed on a Royalty-free. IPR Policy, ETSI ownership of IPRs section: https://www.etsi.org/intellectual-property-rights'
The purpose of PNG is not related to organisational interoperability. Therefore, this criterion is not applicable to the specification. PNG W3C reference: https://www.w3.org/TR/PNG/ PNG ISO reference: https://www.iso.org/standard/29581.html
'As a vocabulary to describe assets within a Repository, it provides concepts and properties identifying the content creators and other informative metadata such as dates involved in the release of the solutions described. These facts may increase the protection of the exchanged data. ADMS Specification W3C: https://www.w3.org/TR/vocab-adms/'
'There is a testing section which is about Testing multilingual string types. The Predicate of that Test is the value of the lang attribute which specifies the language of the message. ETSI TS 119 614-1 reference, page 9 (Testing multilingual string types): https://www.etsi.org/deliver/etsi_ts/119600_119699/11961401/01.01.01_60/ts_11961401v010101p.pdf'
By providing conformance levels and requirements in order to maintain eSignatures in the context of AdES signatures, it ensures and fosters the trustworthy data exchange between administrations and their stakeholders.
'The purpose of the Core Location Vocabulary is to create a reusable and extensible data model that captures the fundamental characteristics related to locations. By providing a set of information to describe data in the sectors mentioned before, it helps public administrations to save and comprehend in an orderly and standardised way, information related to people, locations or business. Core Location Vocabulary: https://interoperable-europe.ec.europa.eu/collection/semic-support-centre/solution/core-location-vocabulary/release/100'
'The purpose of OCSP is not related to the delivery of multilingual public services. Therefore, this criterion is not applicable to this specification. OCSP reference: https://datatracker.ietf.org/doc/html/rfc2560'
OWL allows accessing, importing, sharing and reusing public ontologies. OWL2 is based on elements of RDF and it adds more vocabulary for describing properties and classes. RDF is one of the proposed standards for the publication of data as Linked Open Data. So, the specification is highly aligned with the different levels of maturity of Tim Berners-Lee's 5-star schema for Open Data._x000D_ _x000D_ OWL2 W3C reference:_x000D_ https://www.w3.org/TR/owl2-overview/_x000D_ _x000D_ Tim Berners-Lee 5 star schema for Open Data: _x000D_ https://5stardata.info/en/
There are already existing documents and studies assessing WSDL performance and its features. The main topic are effectiveness while discovering, automatically classify web services or the poor query results. See: https://core.ac.uk/download/pdf/82569095.pdf https://thesai.org/Downloads/Volume10No5/Paper_25-Toward_Effective_Service_Discovery.pdf
'The XBRL specifications including XBRL GL are publicly available. https://specifications.xbrl.org/specifications.html'
'Some of the specifications that include the PROV family of documents allows for partial implementations, specifically PROV-DM, as long as the implementation and usage are identified as described in the PROV Implementation Report. PROV Primer document: https://www.w3.org/TR/prov-primer/ PROV list of reported implementations: https://www.w3.org/TR/2013/NOTE-prov-implementations-20130430/#implementations'
'E-ARK CSIP can enable digital service delivery channels insofar it can be used to create and adapt an archive, or develop applications that need conformance with eArchiving standards, thus enabling seamless delivery of information-related services. E-ARK CSIP specification: https://earkcsip.dilcis.eu/#introduction CEF eArchiving: https://joinup.ec.europa.eu/collection/egovernment/solution/cef-earchiving/about'
'The purpose of ETSI TS 119 614-1 is not related to the secure exchange of data. Therefore this criterion is not applicable to this specification. ETSI TS 119 614-1 reference: https://www.etsi.org/deliver/etsi_ts/119600_119699/11961401/01.01.01_60/ts_11961401v010101p.pdf'
'The purpose of DPV is not related to e-acceesibility, therefore, this criterion is not applicable to the specification. DPV specification: https://w3c.github.io/dpv/dpv/ DPV primer document: https://w3c.github.io/dpv/primer/#introduction'
After carrying out information retrieval, no document or study has been found assessing the W3C Best Practices in terms of efficiency or effectiveness.
9 Member States are recommending IPv6 in their ICT National Catalogues. See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'Although it is mostly suited for public administrations, ETSI TS 119 512 protocols can be implemented in any business domains. For example, the specification uses different preservation schemes that build the so-called preservation profiles (see eIDAS reference) ETSI TS 119 512 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.02_60/ts_119512v010102p.pdf eIDAS blog, New APIs for the eIDAS-Ecosystem: https://blog.eid.as/tag/etsi-ts-119-512-en/'
All the IETF specifications are made available free of charge to the general public via the website. IETF drafts are published publicly discussions take place online in archived mailing lists. Moreover, the IETF Datatracker is the day-to-day front-end to the IETF database for people who work on IETF standards. It contains data about the documents, working groups, meetings, agendas, minutes, presentations, and more, of the IETF. During the development of a specification, draft versions of the document are made available for informal review and comment by placing them in the IETF's Internet-Drafts directory. This makes an evolving working document readily available to a wide audience, facilitating the process of review and revision. See: https://datatracker.ietf.org/ http://www.ietf.org/id-info/
'ADMS as a profile of DCAT, is an RDF vocabulary for representing data catalogues that allows data owners to provide metadata about the datasets they publish. By describing catalogues, datasets and resources, a publisher makes them easily searchable and discoverable. Following the previous statement it can be said that ADMS can simplify the delivery of European public services. ADMS Specification W3C: https://www.w3.org/TR/vocab-adms/'
After searching for a conformity test to validate PNG format, no tool has been found with this purpose.
"While DoH plays a crucial role in enhancing the security and privacy of DNS communication, it doesn't comprehensively address or provide visibility into administrative procedures, rules data, or services. These aspects are typically managed through other networking protocols, configurations, and tools at different layers of the networking stack. DoH specification: https://datatracker.ietf.org/doc/html/rfc8484"
'One of the main purpose of the DPV is to model the legal aspects of data portability, in order to link them with more technical aspects of electronic data echange. DPV suggests mechanisms for the data to be protected, and data transfers in contexts where cross-border exchange is needed. DPV data model is flexible and can be modified according to the laws applying in each particular time, therefore, supporting the evolution of European public services. DPV specification: https://w3c.github.io/dpv/dpv/ DPV primer document: https://w3c.github.io/dpv/primer/#introduction'
'ShEx can be very useful for data portability as it is a tool that allows for the communication of data structures associated with some process or interface. Moreover, ShEx also allows for the serialization in different human and machine-readable formats, use cases that ease the transfer of data between systems, at the same time it eases comprehenisbility for humans. An example of the ShEx implementation would be the Hercules ASIO project, whose objective is to create a Research Management System (RMS) based on semantic open data that offers a global view of the research data of the Spanish University System (SUE), to improve management, analysis and possible synergies between universities and the general public. therefore, ShEx supports the evolution of European public services. ShEx primer document: https://shexspec.github.io/primer/ ShEx Community Group: https://www.w3.org/community/shex/ ShEx Github: https://github.com/shexSpec/spec/issues Hercules ASIO project: https://github.com/HerculesCRUE/ib-shex-lite'
'According to this specification, IDS connectors request a digitally signed JSON web token (JWT) from a central International Data Space (IDS) component called Dynamic Attribute Provisioning Service (DAPS) in order to authenticate themselves. Without these DAPS tokens called Dynamic Attribute Token (DATs), no connector can participate in the IDS. For this reason, DAPS is only meant to be used as a whole. DAPS: https://github.com/International-Data-Spaces-Association/IDS-G/tree/main/Components/IdentityProvider/DAPS'
'EIRA has been successfully used together with eGovERA in several initiatives at national level, and in some of them, included privacy aspects. These privacy aspects come from EIRA, and as the process of analysis and design evolve, the building blocks are specialised making use of the flexibility. This fact helps these initiatives to ensure their specific needs are covered. Some of these projects can be found in the Interoperability Architecture Solutions collection in the Interoperable Europe Portal. Interoperability Architecture Solutions Success Stories: https://interoperable-europe.ec.europa.eu/collection/european-interoperability-reference-architecture-eira/success-stories EIRA reference: https://interoperable-europe.ec.europa.eu/collection/european-interoperability-reference-architecture-eira /solution/eira/release/610 EIRA Github Repository: https://github.com/CarTool-EC/EIRA'
'SOAP 1.2 has been included within several European cross-border initiatives as can be read in the European Interoperability Architecture (EIA) called Common Vision for an EIA. e-SENSE, e-PSOS or SPOCS are initiatives that implemented SOAP 1.2 in order to carry out their purposes. All the projects are related to the enhancement of interoperability between European administrations across borders and across sectors. ETSI SR 019 050 Reference where SOAP is included: https://www.etsi.org/deliver/etsi_sr/019000_019099/019050/01.01.01_60/sr_019050v010101p.pdf '
CAMSS Assessment of DPV EIF Scenario v1.0.0
'The purpose of DPV is not related to e-acceesibility, therefore, this criterion is not applicable to the specification. DPV specification: https://w3c.github.io/dpv/primer/'
"BFO's aim is to provide a foundation for further developments of ontologies. BFO reference: https://www.iso.org/standard/74572.html"
'ISAE 3402 depends on NIA 402 and ISAE 3000. ISAE 3402 states that assurance engagements should be performed in accordance with the ISAE 3000 standard. ISAE 3402 exposure draft: https://www.ifac.org/system/files/uploads/Trans/ISAE%203402%20(definitiva%202013).pdf'
'IEEE Std 802.3-2022 provides the essential physical and data link layers that enable devices to communicate effectively. However, while IEEE Std 802.3-2022 is crucial for data transmission, it does not directly facilitate the modelling and optimization of business processes; therefore, this criterion is not applicable to the specification. IEEE Std 802.3-2022 Reference: https://ieeexplore.ieee.org/document/9844436'
"HTTP Cookies allow for partial implementations depending on the needs and requirements of the webpage on which it is implemented. For example, a developer can manage the user's session and not make use of the web tracking functionality. HTTP Cookies reference: https://datatracker.ietf.org/doc/html/rfc6265#section-5.2"
'The Dataspace Protocol supports the publication of data on the web by providing a framework that balances the need for open data access and collaboration with the requirements for security, compliance, and data sovereignty. It enables organizations to share data in a controlled manner, fostering innovation within secure and trusted data ecosystems. Some of the most relevant standards reused in this protocol include: DCAT for dataset deployment, ODRL for usage control and HTTPS for secure transfering. IDSA Dataspace Protocol: https://docs.internationaldataspaces.org/ids-knowledgebase/v/dataspace-protocol/overview/readme'
IPv4 is a protocol that allows the exchange of data through the internet, therefore, the specifications fosters the data portability. Moreover, the European Commission launched in 2012 a programme to ensure the coexistence and the proper transition to the new version of internet protocol. See: https://ec.europa.eu/commission/presscorner/detail/en/MEMO_12_414
The specification is independent of any software, hardware, or operating system. So it can be said that SVG is independent of any specific technology or platform. SVG W3C reference: https://www.w3.org/TR/SVG11/
'TOSCA allows extension as long as each implementation fully supports all required functionality of the specification exactly as specified. Cloud services execution and their lifecycle management are dependent on the availability of all the TOSCA corresponding artefacts (deployment and implementation artefacts) in all cloud environment use cases. TOSCA reference, Artifact types section: https://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.3/os/TOSCA-Simple-Profile-YAML-v1.3-os.html#_Toc26969466 TOSCA reference, Conformance section: https://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.3/os/TOSCA-Simple-Profile-YAML-v1.3-os.html#_Toc26969508'
The specification allows the exchange of authentication and authorization data between parties. It is mainly used to ensure single sign-on (SSO). It extends SSO across security domains independently from any platform which prevents non-interoperable proprietary technologies. For instance, a relevant implementation of SAML 2.0 is SAML Web Browser SSO profile. This profile was specified to promote interoperability by allowing the authentication to service providers through external identity providers.
'Every time the protocol is used, the whole information needed has to be rewritten and re-provided to maintain the protocol secure. ETSI EN 319 422 reference: https://www.etsi.org/deliver/etsi_en/319400_319499/319422/01.01.01_60/en_319422v010101p.pdf'
'ISO 3166-1 is intended to identify a country, dependencies and special areas of geographical interest. This specification relates to metadata, and can be used in any system that ingests metadata. Therefore, it can be considered platform-agnostic. ISO 3166-1 reference: https://www.iso.org/standard/72482.html '
'The purpose of BFO is not related to data accuracy. Therefore, this criterion is not applicable to the specification. BFO reference: https://www.iso.org/standard/74572.html'
'TOSCA does not foresee any public review. As defined on the OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) Technical Committee (TC), only this TC is involved in the release lifecycle of the specification. External contribution to this committee is possible through the Comment List. OASIS TOSCA TC reference: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=regrep Mail Lists and Comments reference: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=tosca#feedback'
There are already existing studies and documentation assessing different RDF features. For example, there is a study assessing the effectiveness and efficiency of RDF queries. As well there are studies focused on specific topics as is the fact of using RDF in the Smart Cities Modelling. See: https://www.researchgate.net/publication/221466941_Effective_and_Efficient_Entity_Search_in_RDF_Data https://www.sciencedirect.com/science/article/pii/S1045926X1730246X
LegalDocML is XML based, however, it is not dependent on any other technology or platform, so it can be implemented independently from specific technologies or platforms. LegalRuleML reference: http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/legalruleml-core-spec-v1.0.html
HTML is publicly available for implementation and study for free on W3C's webpage. HTML W3C reference: https://www.w3.org/TR/html401/
Core Public Organisation Vocabulary facilitates the information sharing. It enables G2G (Government-to-Government), G2B (Government-to-Business) and G2C (Government-to-Citizen) information sharing. CPOV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-organisation-vocabulary
'XBRL International has a special working group that maintains and develops the specification further. The working group is open to direct members of XBRL International or its national jurisdictions. Links to the original source of information and/or references to working groups: https://www.xbrl.org/the-consortium/join/ https://www.xbrl.org/the-consortium/members/working-group-enrollment/ '
eDelivery SMP 1.10 has the support of CEF eDelivery team which is in charge of the maintenance of the profile. Moreover, the SMP 1.0 is developed by OASIS, one of most relevant international standardisation organisations See: https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery+SMP+-+1.10
The purpose of ODF is not related to the once-only principle. Therefore, this criterion is not applicable to the specification. ODF ISO reference: https://www.iso.org/standard/66363.html ODF OASIS reference: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office
'TrainingDML-AI Standard does not explicitly address the visibility of administrative procedures, rules data, and services. Its primary focus is on the development of a UML model and encodings for geospatial machine learning training data. However, the detailed metadata provided by the TrainingDML-AI Standard could potentially be used to inform such procedures and rules, particularly in the context of preparing and managing training data for AI/ML applications. OGC TrainingDML-AI Standard: https://docs.ogc.org/is/23-008r3/23-008r3.html'
'By using ADMS to describe assets/solutions, the administrations ensure and enhance the visibility of these solutions and assets that are involved in the development of EU administrations’ activity. ADMS on Joinup: https://joinup.ec.europa.eu/solution/asset-description-metadata-schema-adms/about ADMS Specification W3C: https://www.w3.org/TR/vocab-adms/'
'Syslog is not directly designed to enable digital service delivery channels. Instead, syslog is primarily used for the collection and centralization of log messages from various devices and applications within an IT infrastructure. Syslog Protocol: https://datatracker.ietf.org/doc/html/rfc5424'
The term of CAdES was first introduced in 2005 as CMS Advanced Electronic Signatures (CAdES) on ETSI Technical specifications. In 2008 was introduced in IETF webpage as a copy of the ETSI specification. So, it is mature enough for its use in the development of products and services. ETSI TS 101 733 V1.6.3 (2005-09): https://www.etsi.org/deliver/etsi_ts/101700_101799/101733/01.06.03_60/ts_101733v010603p.pdf IETF CAdES: https://tools.ietf.org/html/rfc5126.html
'HTTP specification does not address or provide any insights into the modeling of business processes. HTTP /1.1 RFC 2616 Reference: https://www.rfc-editor.org/rfc/rfc2616.html'
'UDDI Specification Technical Committee was composed by members coming from the most important IT companies as are IBM, Microsoft or Oracle. Along with SOAP and the WSDL stack, UDDI is the cornerstone of Web services implementation. UDDI is a key enabler for creating an effective service ecosystem. Additionally, the main market share companies support the use and implementation of UDDI, so it is demonstrated its maturity and market acceptance. UDDI OASIS reference: http://www.uddi.org/pubs/uddi_v3.htm#_Toc85907974'
'The specification does not ensure and enable data processing accuracy.Therefore, this criterion is not applicable to the specification. AKN4EU reference: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/akn4eu'
There are existing validation tools for UTF-8. See: https://github.com/digital-preservation/utf8-validator
'OAIS is not related to the visibility of administrative procedures, therefore this criterion is not applicable to the specification. OAIS specification: https://public.ccsds.org/Pubs/650x0m2.pdf'
'ETSI TS 119 612 specification is distributed from the ETSI platform. ETSI supports European regulations and legislation through the creation of Harmonised European Standards. ETSI’s mission is to provide platforms where interested parties come together and collaborate on the development and promotion of standards for Information and Communication Technology (ICT) systems and services. ETSI TS 119 612 specification: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf'
Even though the version being assessed is not included in the ICT technical specification in itself, the version 1.0 of the specification was already identified and included within this list of specifications that are compliant with the standardisation regulation for being user in eProcurement. Moreover, the SMP has been the basis for the development of the CEF eDelivery Building Block which helps public administrations to exchange electronic data and documents with other public administrations, businesses and citizens, in an interoperable, secure, reliable and trusted way. ICT technical specifications: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en CEF eDelivery Building Block: https://ec.europa.eu/inea/sites/inea/files/building_block_dsi-introdocument_edelivery_v1_00.pdf
Like all the IETF standards, HTTPS is a free and open technical specification, built on IETF standards and licenses from the Open Web Foundation. FTP is therefore licensed on a royalty-free basis. See: https://tools.ietf.org/html/rfc3668
"Schema.org opted for a flexible data model and adapted its vocabulary for authoring practices (see Schema.org reference, Data model section, Notes for toolmakers and schema authors section). Moreover, schema.org project, in its commitment to turn schema.org into a more flexible model, introduced 'hosted extensions' (see Schema.org Hosted Extensions reference), which offer simplified schema.org vocabularies, more generic than the original vocabularies, in order to allow customised use of the specification. Therefore, the specification allows customisation. The schema.org project highly recommends the use of schema validators for testing the conformance of authoring use cases. Schema.org reference, Data model section, Notes for toolmakers and schema authors section: https://schema.org/docs/datamodel.html Schema.org Hosted Extensions reference: https://schema.org/docs/extension.html Schema.org reference, Data model section, Conformance section: https://schema.org/docs/datamodel.html"
'CPOV contributes to the accuracy of data processing by providing a standardized and consistent data model. This reduces errors and ambiguities in describing and managing information about public organizations, improving the quality and accuracy of the processed data. CPOV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-organisation-vocabulary'
'OpenTelemetry significantly enhances the visibility of administrative procedures by providing comprehensive observability tools that offer deep insights into system performance, reliability, and behavior. This visibility is crucial for maintaining efficient, compliant, and optimized administrative operations. OpenTelemetry: https://opentelemetry.netlify.app/docs/specs/otel/'
As a document exchange format, ODF is a valuable tool for sharing information through the internet between administrations and stakeholders. Also, the XML schema allows the transformation of the content using XSLT by XML based tools. Allowing sharing data and information the standard foster the visibility of administration data and services. Fostering the collaboration between public administrations, the specification eases the decision-making process of institutions. UK Sharing and collaborating with government documents https://www.gov.uk/government/publications/open-standards-for-government/sharing-or-collaborating-with-government-documents ODF ISO reference: https://www.iso.org/standard/66363.html ODF OASIS reference: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office
'The specification needs both parts, the client and the server to be operative and meet the requirements of the time-stamping. Additionally, the specification defines a set of requirements to be followed that can be complemented with the usage of other specifications or standards. ETSI EN 319 422 reference: https://www.etsi.org/deliver/etsi_en/319400_319499/319422/01.01.01_60/en_319422v010101p.pdf'
'OAS is already mapped into the EIRA Library of Interoperable Specifications in the machine to machine interface ABB from the EIRA Technical View. ELIS referenece: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/v500'
'After searching the different national catalogues, no European Member State has been found to recommend the Indexed Database API. Indexed Database API: https://www.w3.org/TR/IndexedDB/'
There are several studies assessing WS-Security is mentioned in the SOAP 1.2 performance. See: https://aaltodoc.aalto.fi/bitstream/handle/123456789/29224/master_Makkonen_Joni_2017.pdf?sequence=1&isAllowed=y
'The OGC TrainingDML-AI standard is a developing framework with the goal of offering a universal language for describing AI models and their data. Although still in the process of widespread adoption, it has undergone multiple iterations and testing phases. Despite its current limited usage, there is potential for it to enhance the development of AI-driven digital solutions, especially as several OGC members are interested in developing similar standards. Moreover, the specification encompasses published documentation regarding supporting processes like change management and release management. OGC TrainingDML-AI Standard: https://www.opengeospatial.org/standards/trainingdml-ai OGC Member List: https://www.ogc.org/about-ogc/ogc-member-list/ OGC Technical Committee Policies and Procedures reference: http://docs.opengeospatial.org/pol/05-020r29/05-020r29.html'
In the context of eSignatures and Seals, the European Commission has stated an Implementing decision (2015/1506) where urged the Member States and other Public services providers to recognise CAdES, PAdES, XAdES, and ASIC as formats for electronic signatures purposes. See: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32015D1506
'HTTP involves storing copies of responses to reduce server load and improve response times by the catching method. While primarily intended for performance optimisation, caching can indirectly contribute to preservation by creating redundant copies of content, though not for long-term retention. HTTP /1.1 RFC 2616 Reference: https://www.rfc-editor.org/rfc/rfc2616.html HTTP/1.1 Caching, RFC 9111 Reference: https://www.rfc-editor.org/rfc/rfc9111'
'IPsec is a business domain agnostic specification, thus can be used in any domain. IPSec reference: https://www.rfc-editor.org/rfc/rfc6071.html'
'The specification is delivered in English, therefore here it is limiting multilingualism of itself. However, EIRA foresee some components that are in line with ensuring that digital public services can be provided in different languages. An example is the "machine translation" components. EIRA reference: https://interoperable-europe.ec.europa.eu/collection/european-interoperability-reference-architecture-eira /solution/eira/release/610 EIRA Github Repository: https://github.com/CarTool-EC/EIRA'
'DQV allows to show the quality of data security, as well as credibility, but it is not aimed at secure data exchange. Therefore, this criterion is considered not applicable to the specification. Data Quality Vocabulary: https://www.w3.org/TR/vocab-dqv/'
CAMSS Assessment of UDDI EIF Scenario v1.0.0
'According to the 5 star Open Data model suggested by Tim Berners-Lee about how to publish linked data, the forth star corresponds to represent data with URIs. According to the OData home page, OData enables the publication of open data. This specification supports REST-based data services, allowing any resource, as well as open data, to be published and edited via simple HTTP messages. Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/en/ OData reference: https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#_Toc31358832'
'OpenTelemetry is not related to providing means for restriction of access to information/data. Therefore, this criterion is considered not applicable to this specification. OpenTelemetry: https://opentelemetry.netlify.app/docs/specs/otel/'
'The purpose of ISAE 3402 standard is other than enabling e-accessibility, therefore, this criterion is not applicable to the standard. ISAE 3402 handbook reference: https://www.ifac.org/system/files/downloads/b014-2010-iaasb-handbook-isae-3402.pdf'
'The application of the once-only principle in all EU Member States public administrations aims at reducing the administrative burden. To achieve this, interoperability between public administrations is a sine qua non condition. SOAP addresses and facilitates the exchanging of information within cross border services and impacts positively the development of eGovernment. SOAP Reference: https://www.w3.org/TR/soap12/'
"The specification takes no stance on what technologies are used in the platform it's being used on."
"Despite being publicly available (though with potential licensing costs), its widespread adoption, compatibility, interoperability, and continuous updates solidify its critical role in modern networking. Furthermore, the IEEE's commitment to FRAND principles ensures fairness and transparency in patent licensing, fostering innovation and preventing unfair competition by having low costs for the patents related to the standard. IEEE SA Standards Board Bylaws: https://standards.ieee.org/about/policies/bylaws/ IEEE Std 802.3-2022 Reference: https://ieeexplore.ieee.org/document/9844436"
'XHTML is a superseded specification that was maintained by W3C which is an international community developing open standards. Developer community W3C: https://www.w3.org/Consortium/'
WSDL helps to describe and make available administration’s web services, which contain public data and information to be reused. The data is structured as WSDL is an XML based language. Taking into account these facts, WSDL is supporting several maturity levels from Tim Berners Lee’s 5 stars schema for Open Data. Additionally, there are existing W3C recommendation and notes regarding the semantics on WSDL. Known as Semantic Annotations Web Services Description Language (SAWSDL). As well, a technical report from the Web Services Description Working Group that maps the representation of the WSDL model in RDF. See: https://5stardata.info/en/ https://www.w3.org/TR/wsdl20-rdf/ https://www.w3.org/TR/sawsdl/
'The European Parliament demonstrates its strong commitment to better law-making principles, as outlined in the new Interinstitutional Agreement on Better Law-Making (IIA-BLM), reinforcing the goal of enhancing transparency in public policy and law-making while increasing the visibility of public administration decision-making processes. Better Regulation Guidelines and Toolbox reference: https://commission.europa.eu/law/law-making-process/better-regulation/better-regulation-guidelines-and-toolbox_en IIA-BLM briefing: https://www.europarl.europa.eu/RegData/etudes/BRIE/2016/579076/EPRS_BRI(2016)579076_EN.pdf#:~:text=The%20new%20Interinstitutional%20Agreement%20on%20Better%20Law-Making%2C%20adopted,initially%20presented%20its%20proposal%20on%2019%20May%202015. Objective of Better Regulation Toolbox: https://commission.europa.eu/law/law-making-process/better-regulation_en#what-is-better-regulation'
The purpose of ELI is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification. Moreover, not informacion has been found to support the positive or negative answer to this criterion. ELI reference: https://eur-lex.europa.eu/eli-register/about.html
'HTTP is designed to be platform agnostic. This design has been crucial for HTTP widespread adoption and ability to connect diverse systems across the internet. HTTP /1.1 RFC 2616 Reference: https://www.rfc-editor.org/rfc/rfc2616.html HTTP versions usage: https://blog.cloudflare.com/http3-usage-one-year-on/'
Ogg is a business domain agnostic specification that can be reused in a cross-domain way. Ogg XIPH reference: https://xiph.org/ogg/doc/rfc3533.txt
The adoption of RDF helps to the reduction of the administrative burden by easing the publication and reuse of the administration's data. The publication of administrations' data allows the consumption by stakeholders avoiding extra steps while information is needed. In addition, the availability of public information fosters the development of efficient eGovernment and the reduction of administrative burden. Additionally, its availability for free is as well an interesting point on the reduction of administrative burden.
'Currently there are assessments regarding the specification effectiveness, The IDTA initiative provides the relevant information regarding the efficiency of the specification. This assessments where presented in the Smart Production Solutions in Nuremberg in the fall of 2024. IDTA in Smart Production Solutions fair: https://industrialdigitaltwin.org/en/news-dates/idta-shows-at-sps-in-nuremberg-how-consistent-data-flow-is-ensured-throughout-the-entire-lifecycle-6600 IDTA reference: https://industrialdigitaltwin.org/en/ Details of the Asset Administration Shell (AAS) https://industrialdigitaltwin.org/en/wp-content/uploads/sites/2/2024/06/IDTA-01001-3-0-1_SpecificationAssetAdministrationShell_Part1_Metamodel.pdf'
'The OASIS Technical Committee, in charge of the development of UBL, operates under RF (royalty-free) on RAND Mode of the UBL IPR Policy. Therefore, the specification is licensed on a (F)RAND basis. OASIS Intellectual Property Rights Policy, section 10.2.2: https://www.oasis-open.org/policies-guidelines/ipr/ UBL Intellectual Property Rights policy: https://docs.oasis-open.org/ubl/os-UBL-2.3/UBL-2.3.html#S-IPR-POLICY'
JSON is a data-interchange format is used by APIs, which are involved in the delivery of information between platforms, and in consequence service delivery. This fact makes JSON an element that fosters de delivery of European Public services, including multilingual ones.
'An ebXML RegRep stores any type of electronic content, such as text documents, images, sound or video, and provides a set of protocols enabling data transfer among systems. For example, ebMS (part of the broader ebXML framework) contributes by providing the header structure necessary for message exchange over AS4. OOTS AS4 reference: https://code.europa.eu/oots/tdd/tdd_chapters/-/tree/86290aa801fb9a8e56486fc49019addcc1321a95/OOTS-EDM/xml/Request-Response%20Samples ebXML RegRep OASIS reference: https://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html'
This document does not define a cross-sector reusable data model, but gives public organizations a model for building their own open source solutions to enable successful future reuse by similar public organizations in other places. The Standard for Public Code webpage: https://standard.publiccode.net/
The specification being assessed is a sector agnostic specification that is able to be reused when structured data needs to be exchanged. Additionally, CSV is designed to enable you to reuse the same schema when publishing multiple CSV files, even if those files are created by different organisations and therefore reside in different places.
'Access control, which involves determining who can access specific resources or perform certain operations, is typically addressed at the implementation and deployment levels rather than within the WSDL specification. Access control mechanisms are often implemented in the runtime environment or the infrastructure supporting the web service. W3C WSDL specification: https://www.w3.org/TR/wsdl20/'
'According to section 8.8 of the protocol "The syslog protocol does not have mechanisms to provide confidentiality for the messages in transit". Syslog Protocol Message Observation: https://datatracker.ietf.org/doc/html/rfc5424#section-8.8'
'One common way to extend JSON is by incorporating additional fields within the JSON objects. These additional fields can contain custom data or specific information that goes beyond the standard JSON structure. By adding custom fields, applications can include extra metadata or define application-specific attributes while still adhering to the overall JSON format. JSON specification: https://www.ecma-international.org/wp-content/uploads/ECMA-404_2nd_edition_december_2017.pdf'
"As a common data exchange format, CSV comprehensibly fosters the visibility of administration's data. It eases the publication of structured data for the consumption by the different stakeholders. Therefore, CSV fosters the visibility of administrations data. Additionally, it can be used internally easing as well de decision-making process. CSV reference: https://datatracker.ietf.org/doc/html/rfc4180"
'There are already studies and documentation assessing the specification in terms of effectiveness and efficiency. The topics are different, for instance, there is a study assessing the capabilities of XML Schema for the defense against Signature Wrapped Attacks. Another field of documentation is the XML Schema clustering, and its effectiveness and efficiency for the improvement of user results. ResearchGate XML Schema Validation Reference: https://www.researchgate.net/publication/252053794_On_the_effectiveness_of_XML_Schema_validation_for_countering_XML_Signature_Wrapping_attacks ResearchGate Effectiveness & Efficiency Assessment Reference: https://www.researchgate.net/publication/254858700_XML_schema_matching_balancing_efficiency_and_effectiveness_by_means_of_clustering'
'The Asset Administration Shell (AAS) specification is yet to be included in a member state catalogue. Details of the Asset Administration Shell (AAS) https://industrialdigitaltwin.org/en/wp-content/uploads/sites/2/2024/06/IDTA-01001-3-0-1_SpecificationAssetAdministrationShell_Part1_Metamodel.pdf'
'TOSCA v1.0 was released in 2013, including the XML schema that users are meant to use when deploying their IT infrastructure (see TOSCA wiki reference, Quick Links and Older Technical Work sections). Two minor releases, TOSCA v1.1 and TOSCA v1.2 were published in 2017 (see OASIS TOSCA TC reference, TOSCA in 2018 and beyond section). In 2020, TOSCA v1.3 prescribed TOSCA v1.2, and changed its name to TOSCA Simple Profile in YAML v1.3. The specification has a draft version of TOSCA v2.0 which aims at easing the portability of cloud applications and services. Additionally, the specification provides OASIS TOSCA TC-independent technical reports and documents/platforms proving its usefulness in the industry (see TOSCA wiki reference, Quick Links section), showing its maturity in the market. TOSCA wiki reference, Quick Links section: https://wiki.oasis-open.org/tosca/FrontPage OASIS TOSCA TC reference, Older Technical Work section: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=tosca#technical TOSCA Simple Profile in YAML reference, section 1.2: https://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.3/os/TOSCA-Simple-Profile-YAML-v1.3-os.html#_Toc26969412 TOSCA Draft Version 2.0 reference, section 1.2: https://docs.oasis-open.org/tosca/TOSCA/v2.0/csd03/TOSCA-v2.0-csd03.html#_Toc56506175 OASIS TOSCA TC reference, TOSCA in 2018 and beyond section: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=tosca#2018'
'SHACL can be implemented across various platforms and systems that support RDF, making it versatile and adaptable to different technological environments. Its ability to validate RDF graphs ensures data integrity and consistency, which is valuable across multiple domains and platforms. Therefore, the specification is platform agnostic. SHACL Platform and Technology agnostic: https://medium.com/fluree/what-is-shacl-with-examples-2697f659d465 SHACL W3C reference: https://www.w3.org/TR/shacl/'
"The specification is included in 10 Member States' catalogues of recommended specifications. Some examples of Member States including SOAP on their catalogues are the Netherlands, Spain or France. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards "
After being evaluated compliant with the regulation on standardisation 1025/2012, UTF-8 has been identified by Commission Implementing Decision. During the evaluation process, all the Member States are invited to share their doubts. The positive evaluation of UTF-8 and its identification is considered an interoperability agreement. See: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en
'WSDL was developed by IBM, Microsoft, and Ariba initially in 2000. The following version was at their charge as well, introducing minor changes. The last version became a W3C recommendation in 2007. Nowadays, the international organisation is maintaining and developing WSDL. Moreover, it continues having support from companies with a wide market share. Therefore, it is demonstrated that WSDL has enough market acceptance and maturity for its use in the development of products and services. WSDL report: https://xml.coverpages.org/wsdl.html Implementation of WSDL in smart city Internet of Things: https://europepmc.org/article/MED/37521954 '
The ISO 19005-1:2005 and ISO 19005-2:2011 which refer to PDF/A-1 and PDF/A-2 are not available for free for everyone to study. Payment is needed to reach access to the standard. PDF/A reference: https://www.iso.org/standard/38920.html https://www.iso.org/standard/50655.html
'As a vocabulary, the implementation of CLV can be tested using methods like SHACL shapes and using semantic reasoners to ensure that the implementation is well-formed. These validation mechanisms can be used with open source tools or lite versions of tools like GrapghDB or Protégé. SHACL validation: https://graphdb.ontotext.com/documentation/free/shacl-validation.html#what-is-shacl-validation Semantic Reasoners List: http://owl.cs.manchester.ac.uk/tools/list-of-reasoners/ Core Location Vocabulary: https://interoperable-europe.ec.europa.eu/collection/semic-support-centre/solution/core-location-vocabulary/release/100'
'CPOV has significant market acceptance in the European context for two main factors, institutional support and adoption by government entities and member states such as Spain, or the Netherlands. CPOV Spain national catalogue: https://administracionelectronica.gob.es/ctt/verPestanaActivosSemanticos.htm?idIniciativa=3351 EU Vocabularies: https://op.europa.eu/en/web/eu-vocabularies/corevocs CPOV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-organisation-vocabulary'
"UTF-8 allows for partial implementations since it's a variable-length encoding scheme that can represent any Unicode character using one to four bytes. Systems that use UTF-8 encoding can choose to implement only a subset of the Unicode character set, but this may limit their ability to handle text data from different languages and scripts. UTF-8 specification: https://datatracker.ietf.org/doc/html/rfc3629 "
PAdES has sufficient market acceptance for its use in the development of products. In the following link there is an example of integrating digital signatures like PAdES in a framework. Digital signature service: https://ec.europa.eu/cefdigital/DSS/webapp-demo/doc/dss-documentation.html
'The Transformational Government Framework (TGF) is supported by the TGF Technical Committee, which is responsible for overseeing the development, maintenance, and promotion of the framework. TGF Technical Committee: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=tgf'
'The specification provides features and guidelines that can help to support e-accessibility for legal documents. Specifically, the specification supports the use of structural markup and semantic tagging, which can help to facilitate the processing and presentation of legal documents in a variety of formats and contexts, including for users with disabilities. AKN4EU reference: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/akn4eu'
"There are existing documentation and studies assessing and analysing the performance and efficiency of IPsec in different contexts and application areas. For instance ENISA provides documentation recommending the use of IPsec in order to improve security. Semantics Scholar, TCP/UDP network performance evaluation of various IPSEC algorithms:https://pdfs.semanticscholar.org/8971/9848f632259138d5d4b1052ad24ede803625.pdf ENISA reference, 'Algorithms, Key Sizes and Parameters Report' document: https://www.enisa.europa.eu/publications/algorithms-key-sizes-and-parameters-report/at_download/fullReport ResearchGate, 'Interoperability Issues for VPN IPsec Solutions' document: https://www.researchgate.net/publication/228437109_Interoperability_Issues_for_VPN_IPsec_Solutions"
There are existing documentation and studies proposing the usage of ODRL as an efficient method for representing more fine-grained access policies for Linked Data. Also, there are studies that also checked the completion of the specification and its actual implementation and providing other formal semantics to improve the application of the specification and its purpose. Defining Expressive Access Policies for Linked Data using the ODRL Ontology 2.0: https://www.researchgate.net/profile/Simon-Steyskal/publication/266652655_Defining_expressive_access_policies_for_linked_data_using_the_ODRL_ontology_20/links/565dc7a408aeafc2aac88d98/Defining-expressive-access-policies-for-linked-data-using-the-ODRL-ontology-20.pdf Formalising ODRL Semantics using Web Ontologies: https://www.researchgate.net/publication/235902060_Formalising_ODRL_Semantics_using_Web_Ontologies
"The specification is included in 8 Member States' catalogues of recommended specifications. Some examples of Member States including XSD on their catalogues are the Netherlands, Slovenia, Spain or Portugal. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards Spain National Catalogue: https://administracionelectronica.gob.es/pae_Home/dam/jcr:9e2c2877-5103-4934-8440-c60ba2e10c48 /Catalogue_of_Standards_NIF_Spain.pdf "
'GraphQL is a good enabler for the exposures of interfaces insofar it does not mandate a particular programming language or storage system for application services that implement it. Instead, application services take their capabilities and map them to a uniform language, type system, and philosophy that GraphQL encodes. This provides a unified interface friendly to product development and a powerful platform for tool-building. GraphQL specification: https://spec.graphql.org/October2021/#sec-Overview'
"The specification is associated with EIRA ABB's in the EIRA Library of Interoperability Specifications (ELIS). It is associated with the ABB Binding Instrument and it's View is Legal. It is also associated with Legal Act Representation, Open Data and Representation of the Semantic View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/v501"
'As a protocol for data exchange, FTP allows the provision of data using an endpoint and therefore makes available interfaces of public administrations internal information systems. An example of implementation support this fact would be the Flemish initiative MAGDA. This initiative provides a platform that allows the different administrations to reuse the information contained within their registries. FTP has been selected by MAGDA to enable data exchange between the different registries. Magda Platform About: https://joinup.ec.europa.eu/solution/magda-platform/about FTP Specification Reference: https://datatracker.ietf.org/doc/html/rfc959'
'The specification does not specify if it ensures the protection of personal data managed by Public Administrations. Therefore, this criterion is not applicable to the specification. ADMS Specification W3C: https://www.w3.org/TR/vocab-adms/'
WSDL can be extended according to constraints defined in section 6 of the specification. This fact allows users to implement changes without hampering the interoperability and scalability of systems. See: https://www.w3.org/TR/wsdl/#language-extensibility
"While genericode's first committee specification was published on the 28th of December of 2000, genericode is currently on its 1.0 version, last revised on the 31th of January of 2023. Furthermore, the submitting of Code List Representation (genericode) Version 1.0 OASIS Standard to ISO/IEC JTC1 was approved in 2023. Code List Representation (genericode): https://docs.oasis-open.org/codelist/genericode/v1.0/os/genericode-v1.0-os.html Approve submitting Code List Representation (genericode): https://groups.oasis-open.org/communities/community-home/digestviewer/viewthread?GroupId=1681&MessageKey=b519e373-2919-495d-a9b3-893ccc16e8b8&CommunityKey=7558fd85-f7ac-4dd7-b57b-018dc7d3f6f7"
'While SCIM may not be used for modeling broader business processes, it can be part of a larger ecosystem that includes business process modeling tools, identity and access management (IdAM) systems, and other components. In this context, SCIM serves a specific role in handling identity-related tasks within the broader framework of business operations. SCIM has several implementations that can facilitate the modelling of business processes. SCIM: https://scim.cloud/'
No formal interoperability agreement has been found involving European public services providers.
FTPS is a network protocol for transferring files over the Internet. It has the same specifications as FTP but it uses the Transport Layer Security (TLS) to secure the communications. FTPS IETF reference: https://tools.ietf.org/html/rfc4217
'TSP is not included in any national catalogue of recommended specifications whose Member State NIF is fully aligned with at least 2 out of 3 sections of the EIF according to NIFO factsheets. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
'Like all SEMIC services, SEMIC is the responsible for the maintenance and growth of the LDES development, as well as the community around it. In addition, SEMIC has launched a GitHub where contributions and discussions can be made freely. SEMIC Joinup: https://joinup.ec.europa.eu/collection/semic-support-centre LDES GitHub: https://github.com/SEMICeu/LinkedDataEventStreams'
'XSLT specification does not address or facilitate organisational interoperability agreements. XSLT Reference: https://www.w3.org/TR/xslt-30'
'The specification allows for customization to a certain extent. It provides mechanisms that enable developers to define their own extensions, headers, and data types within the SOAP framework. SOAP Reference: https://www.w3.org/TR/soap12/ '
The specification was carried out in 2001 and has been developed and maintained by OASIS. It has suffered 1 minor update (SAML 1.1) and a major one (SAML 2.0). This fact demonstrates the maturity of the specification that is being assessed. Moreover, it is also implemented by IT vendors and suppliers having a market dominance. For instance, SAML 2.0 is implemented by Microsoft for the Microsoft Azure Active Directory and by Amazon for Amazon Web Services. Therefore, it is demonstrated that SAML 2.0 has enough maturity and market acceptance for its use in the development of products and services.
'While genericode itself primarily focuses on providing a standardised format for representing code lists and controlled values, it can indirectly contribute to the visibility of administrative procedures, rules data, and services by promoting clarity and consistency in how administrative procedures and rules are communicated and implemented, improving semantic richness, interoperability and integration of systems. Code List Representation (genericode): https://docs.oasis-open.org/codelist/genericode/v1.0/os/genericode-v1.0-os.html'
'WAI-ARIA specification does not deal with ensuring data processing accuracy or the integrity of data transactions. Therefore, this criterion is not applicable to this specification. WAI-ARIA reference: https://www.w3.org/TR/wai-aria-1.2/'
'After checking the different standard catalogues at supra-national level, there is no evidence of TOSCA as a European standard. ICT technical specifications: https://ec.europa.eu/growth/single-market/european-standards/ict-standardisation/ict-technical-specifications_en CENELEC and CEN search tool catalogue: https://standards.cencenelec.eu/dyn/www/f?p=CEN:105::RESET::::'
'After looking in the European Library of Interoperability Specifications, we can conclude UBL has not been mapped into the EIRA, although it is planned to be added in the Data Model ABB (semantic view). EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/v110'
The W3C Royalty-Free IPR licenses granted under the W3C Patent Policy apply to all W3C specifications, including XSLT.
'IEEE Std 802.3-2022 conformance test is based on the Protocol Implementation Conformance Statement (PICS), is essential to ensure that a network device functions correctly and is interoperable with other devices on the network. This process, while not guaranteeing absolute interoperability, facilitates the identification of incompatibilities and ensures a level of confidence in adherence to the standard. IEEE Std 802.3-2022 Reference: https://ieeexplore.ieee.org/document/9844436 '
'Whenever the user intends to use or reuse the CSV specification, information needs to be provided every time. CSV reference: https://datatracker.ietf.org/doc/html/rfc4180'
By helping administrations to access and reuse information across borders, the implementation of HTML4 and other standards from HTML family can help to foster and ease the Once-Only Principle. HTML W3C reference: https://www.w3.org/TR/html401/
'The INSPIRE (Infrastructure for Spatial Information in the European Community) project partly relies on the ISO 3166-1 specification (see INSPIRE Data Specification on Administrative Units reference). INSPIRE is a key delivery agent of European public services which addresses the exchange, sharing, access and use of interoperable spatial data and spatial data services at different levels of public authority and in different sectors. Therefore, the specification may contribute to simplify the delivery of European public services. ISO 3166-1 reference: https://www.iso.org/standard/72482.html INSPIRE Data Specification on Administrative Units reference: https://inspire.ec.europa.eu/id/document/tg/au INSPIRE reference, Directive 2007/2/EC document, Article 1: https://inspire.ec.europa.eu/inspire-legislation/26'
'As REST is an architectural style, it is designed to be implemented in any platform, and does not rely on any other standard or specification. REST reference: https://restfulapi.net/rest-architectural-constraints/'
'The NFVI specification is composed of different virtualised resources that activates depending on the task (see NFVI Deliver, section 6.4.2.1). Therefore, the NFVI specification can be implemented partially. NFVI Deliver, Infrastructure Overview: https://www.etsi.org/deliver/etsi_gs/NFV-INF/001_099/001/01.01.01_60/'
'As it is stated in the "Implementation and Specification" document "The goal of domain names is to provide a mechanism for naming resources in such a way that the names are usable in different hosts, networks, protocol families, internets, and administrative organizations." Therefore, by allowing the association of information with domain names, DNS facilitates their comprehension of data and services in a network. DNS IETF reference: https://datatracker.ietf.org/doc/html/rfc8499 Domain Names - Implementation and Specification: https://tools.ietf.org/html/1035 '
'Verifiable Credentials can be used to represent different types of credentials, including those related to identity, qualifications, certifications, and more. The specification mentions that it is important to follow accessibility guidelines and standards, such as WCAG21, to ensure that all people, regardless of ability, can make use of this data. Verifiable Credentials: https://www.w3.org/TR/vc-data-model/ WCAG: https://www.w3.org/TR/WCAG21/'
"Tracking cookies, and especially third-party tracking cookies, are commonly used as ways to compile long-term records of individuals' browsing histories, a potential privacy concern that prompted European lawmakers to take action in 2011. For that concern legislation or regulations that cover the use of HTTP Cookies in the EU include The General Data Privacy Regulation (GDPR) and the ePrivacy Directive. With a global reach, these regulations apply to any site on the World Wide Web accessed by users under these jurisdictions. HTTP Cookies reference: https://developer.mozilla.org/en-US/docs/Web/HTTP/Cookies#creating_cookies GDPR reference: https://gdpr-info.eu/ ePrivacy Directive: https://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=CONSLEG:2002L0058:20091219:EN:PDF "
'The specification has been developed by the European Commission for its implementation across borders to improve the accountability and development of public policies and laws, in this sense the specification can be considered compliant with the different European Regulations. Moreover, one of the main goals of the specification is to foster the consistency and proper development of the general public laws and policies. Better Regulation Guidelines and Toolbox reference: https://commission.europa.eu/law/law-making-process/better-regulation/better-regulation-guidelines-and-toolbox_en'
'[NOT FINAL ANSWER] The specification purpose is to help in the description of software, a metadata schema based on YAML. The publiccode.yaml file is the outcome of using the specification, and it is to be published in the repository where the solution is hosted. This allows the easy discoverability and automatic processing of solutions information, easing its reuse, evaluation or indexation in catalogues. Publiccode.yaml documentation: https://docs.italia.it/italia/developers-italia/publiccodeyml-en/en/master/index.html'
'The purpose of SMP seems to not be related to fostering the e-accessibility. Moreover, no information regarding this topic has been found to answer positively or negatively to the criterion. SMP OASIS reference: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505009'
'The Semantic Interoperability Community (SEMIC) has established Working Groups. These Working Groups are open to the participation of everyone interested in semantic solutions working for public administrations in the Member States or in EU institutions. SEMIC working groups: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/about'
'TOSCA is to be used for a variety of cloud services and is not tied to any specific cloud paradigm. Therefore, the specification is platform-agnostic. TOSCA reference: https://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.3/os/TOSCA-Simple-Profile-YAML-v1.3-os.html'
'XHTML does not enable modern digital service delivery channels because it lacks the flexibility, multimedia support, and responsiveness of newer web standards like HTML5. Therefore, XHTML is not suitable for supporting the complex, interactive, and cross-platform digital services that public administrations need today. XHTML W3C reference https://www.w3.org/TR/xhtml1/'
The purpose of HTTPS is not related to organisational interoperability. Therefore, this criterion is not applicable to the specification.
'TGF promotes the reuse of relevant information within and across government organisations. One of the core principles of the TGF is ""reuse before buy or build,"" which encourages organisations to leverage existing solutions, services, and data before developing new ones. It provides guidance and best practices for identifying, assessing, and reusing existing information assets, such as data, documents, and processes, to improve efficiency and reduce costs. By promoting the reuse of relevant information, the TGF aims to improve collaboration and knowledge sharing within and across government organizations, and ultimately enhance the delivery of public services. TGF specification: http://docs.oasis-open.org/tgf/TGF/v2.0/cs01/TGF-v2.0-cs01.html'
"The specification's purpose is not related to privacy. Therefore, has not been found included in any initiative neither at European nor on national level covering privacy aspects. GS CIM 009: https://www.etsi.org/deliver/etsi_gs/CIM/001_099/009/01.07.01_60/gs_CIM009v010701p.pdf"
Standard for Public Code has a defined and publicly available Process for the Development and approval process of the specification as a recommended standard. Moreover, the standard is currently evolving and the defined process is open, with complete access and rights to contribute meaning that everyone can participate with suggestions, issues, or problems while contributors can also make changes and document them directly. In this sense, the decision making process is constantly open to the community. The Standard for Public Code webpage: https://standard.publiccode.net/ The Standard for Public Code contributing section: https://standard.publiccode.net/CONTRIBUTING.html
'RDF is built around specifications as XML or URL (URI). Even though, both web standards are well known and widely extended avoiding interoperability hampering. RDF primer document: https://www.w3.org/TR/rdf11-primer/'
'The specification performs efficienetly in accordance with the TR-ESOR middleware techincal guidelines. ETSI TS 119 512 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.02_60/ts_119512v010102p.pdf TR-ESOR Preservation of Evidence of Cryptographically Signed Document: https://www.bsi.bund.de/EN/Service-Navi/Publications/TechnicalGuidelines/TR03125/TechnicalGuidelines_03125_node.html'
'The Apache License 2.0 is known for being permissive and allowing users to freely use, modify, and distribute the software. It does not impose restrictions on how the software can be used in proprietary or open-source projects. IDSA License: https://github.com/International-Data-Spaces-Association/ids-specification/blob/main/LICENSE Apache 2.0: https://www.apache.org/licenses/LICENSE-2.0'
The specification is included in 1 Member States' catalogue of recommended specifications. The Member State that includes this Core Vocabulary on their catalogue is Belgium. Belgium national catalogue: https://www.belgif.be/nl/specifications
'There are many available public online channels for the exchange of help and knowledge among REST users. See the links below for such examples. Microsoft developer network reference: https://social.msdn.microsoft.com/Forums/es-ES/d720e383-96ca-4b8a-9d53-ad78bc51eeee/web-api-rest-c-json Opentext developer reference: https://forums.opentext.com/forums/developer/discussion/235439/rest-api-categories'
'The purpose of OData is not related to the delivery of multilingual public services. Therefore, this criterion is not applicable to this specification. OData reference: https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#_Toc3135883'
e-Delivery SMP 1.10 is part of eDelivery stack, which allows document and data exchange between different parts within a public or private network. The implementation of the specification along with the eDelivery Building Block stack, is a key enabler for data exchange, which allows administrations to reduce administrative burdens. Some of the administrative burdens are the non-digital data exchange or the time that implies these exchanges among others.
'HTTP is included in 12 national catalogues. The Member States that includes the specification are Bulgaria, Croatia, Cyprus, Finland, France, Germany, Greece, Netherlands, Norway, Portugal, Spain and Sweden. They belong to Member States which comply with at least 4 out of 5 sections of the EIF according to the NIFO factsheets. National Interoperability Framework Observatory Factsheets: https://interoperable-europe.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public-administration-factsheets-2024 List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
'The specification has multiple methods to protect the information against unauthorised changes such as: -Digital Signatures: SAML assertions and protocol messages can be digitally signed using XML Digital Signature. -Message Encryption: SAML assertions can be encrypted for a specific recipient using XML Encryption. While encryption primarily ensures confidentiality, it also adds an additional layer of protection against tampering. -Binding Profiles: Various SAML binding profiles, like the HTTP POST and Artifact bindings, have specific mechanisms to ensure the integrity and authenticity of the SAML messages transported using those bindings. And more to be described. SAML 2.0 Reference: http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-tech-overview-2.0.html'
TLS 1.2 is published on Joinup, the collaborative platform for reusable IT Solutions funded by the European Commission. See: https://joinup.ec.europa.eu/solution/tls-rfc-5246-transport-layer-security-protocol
'IPv6 is developed by IETF which is based in the USA, thus the specification cannot be regarded as a European Standard. However, in Europe, IPv6 address space can be obtained from an upstream provider or from the regional internet registrar for Europe: Requirements for IPv6 in ICT Equipment (RIPE). IETF reference: https://www.ietf.org/ "Guidelines and Process: IPv6 for Public Administrations in Europe" reference: https://joinup.ec.europa.eu/sites/default/files/document/2019-12/Plum-EC-IPv6-Guidelines.pdf'
Although HTML purpose is not to foster the delivery of multilingual European public services, it has various components that help to publish online data in different languages. In fact, HTML allows to have the same website online in different languages. HTML W3C reference: https://www.w3.org/TR/html401/
"The specification is associated with EIRA ABB's in the EIRA Library of Interoperability Specifications (ELIS). It is associated with Data Exchange Component, Application Service, e-Signature Creation Service, Machine to Machine Interface from the Technical Application View. SOAP Reference: https://www.w3.org/TR/soap12/ ELIS link: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /solution/elis/release/v501 "
The standard for Public Code is supported by many public technologists and policymakers that can contribute to the development of the standard at the same time all the contributors review those updates. Moreover, it is focused on the development of open-source with an open development process, which fosters support from anyone with knowledge and interest in contributing. The Standard for Public Code update process: https://standard.publiccode.net/CONTRIBUTING.html
CAdES (ISO 14533-1:2014) is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, it can define the interoperability aspects of the "e-Seal Preservation Service" and "e-Signature Preservation Service" ABBs of the EIRA Technical Infrastructure View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/solution/elis/release/v100
'As of 2022, only one country has CPSV-AP included within the catalogue, which is Belgium and has a complying performance of 2 out of 3 sections of the EIF according to the NIFO factsheets. NIFO factsheets: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public-administration-factsheets-2022 CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards '
'The Advanced Encryption Standard is included in 4 Member States catalogues of recommended specifications. These Member States are Cyprus, Germany, Malta and The Netherlands. CAMSS List of Standards: https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards AES Standard Reference: https://csrc.nist.gov/pubs/fips/197/final'
'There are pieces of evidence that state OData is wide-spread and used (see OData ecosystem reference). Although there are some market alternatives to OData, such as GData (Google), it is worth to note that there is some evidence of OData as an innovative solutions creator. Moreover, the specification has a dedicated Github tailored by the Microsoft community. Stackshare-OData reference: https://stackshare.io/odata/alternatives OData ecosystem reference: https://www.odata.org/ecosystem/ OData-Microsoft Github reference: https://github.com/OData'
'HTTP primary role is to provide a standardised framework for web communication by using a request response functions between servers and clients facilitating the access to websites. However, it does not specify how to structure administrative data or functions for interfaces. Therefore, this criterion is not applicable to the specification. HTTP /1.1 RFC 2616 Reference: https://www.rfc-editor.org/rfc/rfc2616.html'
'The main purpose of the GITB TDL is to test the conformance and interoperability of specifications. GITB TDL reference: https://www.itb.ec.europa.eu/docs/tdl/1.2.0/introduction/index.html#what-is-the-gitb-tdl'
'The publiccode.yml specification does facilitate partial or incremental implementation by defining mandatory and optional components. It provides a foundational minimum level of implementation while allowing for additional fields to be included optionally for an extended configuration. This approach ensures flexibility, enabling adopters to start with core requirements and progressively integrate more detailed elements if desired. Thus, the specification does not require full implementation from the outset, supporting varied deployment contexts and needs. Publiccode.yaml documentation: https://docs.italia.it/italia/developers-italia/publiccodeyml-en/en/master/index.html'
'GITB TDL is Licensed on a royalty-free basis under the European Union Public License (EUPL). JOINUP reference: https://joinup.ec.europa.eu/sites/default/files/custom-page/attachment/eupl_v1.2_en.pdf GITB TDL reference: https://www.itb.ec.europa.eu/docs/tdl/latest/introduction/index.html#what-is-the-gitb-tdl'
"Despite being involved in several projects, ISO 3166-1 has no evaluations that assess it and no evidence of any technological solutions that indirectly assess the specification has been found. Therefore, there is no assessment of the specification's effectiveness. ISO 3166-1 reference: https://www.iso.org/standard/72482.html"
"The specification allows user to access and maintain distributed directories information over the Internet, which reduces the administrative burden of the system administrators and the users. LDAP, using SASL and TLS can manage users' access to directory services, as well as acting as an authentication method. Thus, it fosters the implementation of digital services, supporting the principle of digital-first. LDAP IETF reference: https://tools.ietf.org/html/rfc4511 TLS cloudfare reference: https://www.cloudflare.com/learning/ssl/transport-layer-security-tls/ SASL gnu reference: https://www.gnu.org/software/gsasl/manual/gsasl.html#SASL-Overview "
'Even if iCalendar has been discreetly used at a EU context (EUROSTAT), the specification defines a set of conventions that could be integrated in the depiction of future organisational interoperability agreements. Euro-indicators (EUROSTAT) release calendar: https://ec.europa.eu/eurostat/news/internet-calendar iCalendar specification: https://www.rfc-editor.org/rfc/rfc5545'
The W3C Royalty-Free IPR licenses granted under the W3C Patent Policy apply to all W3C specifications, including SHACL. See: https://www.w3.org/TR/patent-practice#ref-AC
'The purpose of EN 16234-1 e-CF is not related to the secure processing of data. Therefore, this criterion does not apply to this specification. CEN reference, CEN/TC 428 - ICT Professionalism and Digital Competences (Published standards), EN 16234-1 e-CF: https://standards.cencenelec.eu/dyn/www/f?p=205:110:0::::FSP_PROJECT:67073&cs=15E62ED24D608A5F10D6BEE8E6D50FA10'
'The specification is focused on the preservation of confidential data and its availability. The business domain is security, even though it can be implemented in any sector (e.g. eHealth). ISO/IEC 27001 reference website: https://www.iso.org/standard/54534.html'
'Verifiable Credentials simplifies the delivery of European public services by offering a standard format for the digital representation of credentials that are cryptographically secure, verifiable through machines, and that guarantee privacy. Thanks to this specification, digital documents related to European public services containing information about a person or entity that can be easily shared and automatically verified. Verifiable Credentials: https://www.w3.org/TR/vc-data-model/'
The purpose of EuroVoc is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification.
PNG defines a format extension to save image, but does not define a cross-sector reusable data model.
WSDL is included in 3 national catalogues of recommended specifications. They belong to the Netherlands, Spain, and Sweden. The National Interoperability Framework (NIF) of these Member States is fully aligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. See: https://joinup.ec.europa.eu/collection/national-interoperability-framework-observatory-nifo/nifo-factsheets
'Currently the Asset Administration Shell (AAS) has not been recommended by any European member state. But the Industrie 4.0 platform is promoted mainly by the German government, and this includes the AAS specification. etails of the Asset Administration Shell (AAS) https://industrialdigitaltwin.org/en/wp-content/uploads/sites/2/2024/06/IDTA-01001-3-0-1_SpecificationAssetAdministrationShell_Part1_Metamodel.pdf'
'The TrainingDML-AI Standard is also platform agnostic. It provides a model and encodings for exchanging and retrieving training data via the Web, which can be implemented on any platform that supports web technologies. OGC TrainingDML-AI Standard: https://docs.ogc.org/is/23-008r3/23-008r3.html'
'The specification is not related to the publication of public data as open data. Therefore this criterion is not applicable to this specification. ETSI TS 119 614-1 reference: https://www.etsi.org/deliver/etsi_ts/119600_119699/11961401/01.01.01_60/ts_11961401v010101p.pdf'
'EuroVoc was developed to support the processing of documentary information. Besides, since it helps to classify the knowledge domains and subdomains it is helpful fostering the visibility of administrative data and supporting the decision-making process. EuroVoc: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource /dataset/eurovoc'
HTTP 1.1 is available on Joinup, the collaborative platform for Reusable IT Solutions funded by the European Commission. See: https://joinup.ec.europa.eu/solution/http-over-tls
ASiC and ASiC Baseline profile are included in the ETSI’s catalogue of standards. As ETSI is considered an official standardisation organisation, it can be considered that the specifications are included in a supra-national catalogue. See: https://www.etsi.org/deliver/etsi_ts/103100_103199/103174/02.02.01_60/ts_103174v020201p.pdf https://www.etsi.org/standards
'After searching the different national catalogues, there has not been found any European Member State recommending ETSI TS 119 512. ETSI TS 119 512 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.02_60/ts_119512v010102p.pdf'
'Given that the aim of the DPV is to become a standard data model and vocabulary to be used across Europe, it is designed to support most of the languages used in the European Union. DPV specification: https://w3c.github.io/dpv/dpv/ DPV primer document: https://w3c.github.io/dpv/primer/#introduction '
DCAT-AP has a significant market acceptance. It has been successfully implemented by several European Union Institution: • The European Commission DG CONNECT with the European Data Portal • The Publications Office of the European Union with the European Union Open Data Portal • The European Commission DG JRC with the JRC Data Catalogue and National Public administrations across Europe: • The German GovData Business Office with the German Data Portal • The Belgian Federal Public Service for ICT with the Belgian open data portal • The Dutch Ministry of Interior and Kingdom Relations with the Dutch open data portal • The Open Data Portal of Switzerland with the Geocat CKAN Harvester • The Spanish Open Data Portal • The Swedish innovation agency VINNOVA and the Swedish national data portal • Swedish MetaSolutions and the EntryScape Catalogue See complete list of users/implementations: https://joinup.ec.europa.eu/solution/dcat-application-profile-data-portals-europe/about
'ISO 3166-1 is a key component in the development of some national and cross-border projects and initiatives. However, ISO 3166-1 does not encourage the creation of communities nor promotes the sharing of data and results in any national platform. ISO 3166-1 reference: https://www.iso.org/standard/72482.html'
'SAREF is developed and maintained by the European Telecommunications Standards Institute (ETSI). Its development involves contributions from industry experts and collaboration within ETSI working groups, particularly ETSI Technical Committee SmartM2M. This standardization body provides a foundational level of support for the ontology. ETSI takes into account the impact of users as they improve their standards and their relevancy. ETSI Technical Committee SmartM2M: https://www.etsi.org/committee/smartm2m'
ODRL is maintained by W3C which is an international community developing open standards. W3C Consortium home page: https://www.w3.org/Consortium/ W3C specification reference: https://www.w3.org/TR/odrl-vocab/#vocab-core W3C Working Group Github space: https://github.com/w3c/odrl
There are several reports assessing how DCAT-AP is effective and efficient for the publication of open data. See: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/dcat-ap
'The OASIS Technical Committee, in charge of the development of OData, operates under RF (royalty-free) on RAND Mode of the OASIS IPR Policy. Therefore, the specification is licensed on a (F)RAND basis. OData reference, section 1.0: https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html OASIS Intellectual Property Rights Policy, section 10.2.2: https://www.oasis-open.org/policies-guidelines/ipr/'
TLS 1.2 has been widely adopted by public administrations in order to secure the communications over Internet. An example of its use in a cross-border project is the Union Registry from the European Commission "Climate Action, Energy for a changing World". The initiative restricted its use to a web browsers supporting TLS 1.2. See: https://unionregistry.ec.europa.eu/euregistry/EU/index.xhtml
'REM is a type of electronic registered delivery, which increases usability and ensures integrity, confidentiality and non-repudiation and protects against the risk of loss, theft, damage and any illegitimate modification. ETSI EN 319 532-3 reference: https://www.etsi.org/deliver/etsi_en/319500_319599/31953203/01.02.01_60/en_31953203v010201p.pdf'
The purpose of EuroVoc is not related to the modelling of organisational interoperability aspects.Therefore, this criterion is not applicable to the specification
'No projects have been found that use CLV and cover privacy aspects. Core Location Vocabulary: https://interoperable-europe.ec.europa.eu/collection/semic-support-centre/solution/core-location-vocabulary/release/100'
'The purpose of TrainingDML-AI is not related to the secure exchange of data. While it doesn’t explicitly mention security, the use of standardized protocols and formats can contribute to secure data exchange. OGC TrainingDML-AI Standard: https://docs.ogc.org/is/23-008r3/23-008r3.html'
'The IPsec specification ensures the trustworthiness and integrity of tranferred data. IPsec can guarantee that data has not been modified by unauthorised users, that it remains unchanged from its original form when sent, and that it will reliably reach the receiver. IPSec reference: https://www.rfc-editor.org/rfc/rfc6071.html IPsec security reference: https://www.geeksforgeeks.org/ipsec-internet-protocol-security-tunnel-and-transport-modes/ AH and ESP protocols: https://netseccloud.com/ah-vs-esp-understanding-the-core-differences-in-ipsec-protocols'
'At least 7 Member States recommends the use of XSLT specification, this Member States are: Cyprus, France, Germany, Greece, Poland, Portugal and Sweden. National Catalogue of France: https://www.numerique.gouv.fr/uploads/Referentiel_General_Interoperabilite_V2.pdf National Catalogue of Sweden: https://www.avropa.se/globalassets/dokument/open-it-standards.pdf?_t_id=1B2M2Y8AsgTpgAmY7PhCfg% 3d%3d&_t_q=standards&_t_tags=language%3asv%2csiteid%3a95d515a5-23ca-47bf-87a9- CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards'
'There are several CSV conformance validators available. An example is CSV Lint, which provides a conformance validation for its readability. Another example is CSV Validator from The National Archive of United Kingdom, or the TestBed validator. This validator provides tools for validating CSV by using CSV Schema. CSV Lint and CSV Validator References: https://csvlint.io/ https://github.com/digital-preservation/csv-validator TestBed CSV validator Reference: https://joinup.ec.europa.eu/collection/interoperability-test-bed-repository/solution/csvvalidator/about CSV reference: https://datatracker.ietf.org/doc/html/rfc4180'
'ETSI TS 119 511 can be found on the specifications and standards repository of its own standards development organization, the European Telecommunication Standards Institute (ETSI). ETSI standards repository: https://www.etsi.org/committee/1399-esi'
'Developers can use WSDL to create interoperable web services that can be consumed by a variety of clients, regardless of the platforms or technologies they are built upon.This allows for the decoupling of the service description from the specific technologies or platforms used in the implementation. WSDL can achieve platform agnosticism by providing a high-level, abstract description of web service interfaces and operations. W3C WSDL specification: https://www.w3.org/TR/wsdl20/ '
'Assistive technologies convey suitable information to people with disabilities by introducing web widgets and structuring web content. In this sense, personal data protection is not addressed by this specification. WAI-ARIA reference, Abstract section: https://www.w3.org/TR/wai-aria/'
'The purpose of FTP is not related to e-accessibility. Therefore this criterion is considered not applicable to this specification. FTP Specification Reference: https://datatracker.ietf.org/doc/html/rfc959'
'DNS over HTTPS (DoH) is designed to be extensible, enabling the addition of new features, options, or improvements over time. This extensibility is crucial for accommodating evolving requirements, addressing new challenges, and incorporating feedback from the user community. DoH uses option codes to enable the inclusion of additional parameters or features in DNS queries and responses and provides a flexible structure that allows for the inclusion of extensions while maintaining compatibility with existing implementations. DoH specification: https://datatracker.ietf.org/doc/html/rfc8484'
The Core Public Service Vocabulary Application Profile can be found for free along within the European Collaborative Platform, Joinup. CPSV-AP reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-service-vocabulary-application-profile
'Currently, the specification has been used in Italy to describe the software created in the country. This has permitted the creation of a national catalogue of software by crawling the content of the publiccode.yml available within the software repositories. The standard is also applied in opencode.de, Germany’s registry for open-source software in public administration. Publiccode.yaml documentation: https://docs.italia.it/italia/developers-italia/publiccodeyml-en/en/master/index.html Italian National Software Catalogue: https://developers.italia.it/ Open CoDE: https://opencode.de/en'
'The EIRA is not just included in a repository of standards, it is included within the Interoperability Architecture Solutions in the Interoperable Europe Portal, the site that the Interoperable Europe Act foresees as the place where interoperability solutions should be published, and where Member States and their different administrative levels can go to find reusable solutions. EIRA reference: https://interoperable-europe.ec.europa.eu/collection/european-interoperability-reference-architecture-eira /solution/eira/release/610 EIRA Github Repository: https://github.com/CarTool-EC/EIRA'
'The ebXML specification is a family of XML-based standards that provides an open, XML-based infrastructure that enables the interoperable use of electronic business information. ebXML relies on XML, and therefore is not technology-agnostic. ebXML reference: http://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html'
'EuroVoc Hanbook serves as a guide on how to input data and update existing entries. Consistency is key in maintaining the specificaction, therefore, a long evaluation process takes place to ensure the correct implementation of changes in the thesaurus. EuroVoc Handbook: https://publications.europa.eu/resource/cellar/a2723a83-574f-11eb-b59f-01aa75ed71a1.0001.01/DOC_1 EuroVoc: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource /dataset/eurovoc'
JSON is available for its use an implementation at ECMA International and EITF's webpages. See: https://www.ecma-international.org/publications/standards/Ecma-404.htm https://tools.ietf.org/html/rfc8259#section-14.1
'CSV is one of the most popular formats for publishing data on the web. An example of those developments is CSV Dialect which aims to deal with a reasonably large subset of the features which differ between dialect. Add history, structured data, support from wide range of organisations (private and public) CSV reference: https://datatracker.ietf.org/doc/html/rfc4180'
The purpose of MIME is not related to the implementation of the once-only principle. Therefore, this criterion does not apply to this specification. MIME reference: https://tools.ietf.org/html/rfc2045
The specification defines not only the codebase for the development of reusable solutions but also how the code has to be developed to ensure the maximum standardised method and its possible future reuse by other solutions or initiatives. In this sense, the specification provides a set of elements that stakeholders using and contributing must take into account to increase the successful and efficient collaboration between parties. The Standard for Public Code webpage: https://standard.publiccode.net/
'The purpose of UTF-8 is not related to the protection of personal data. Therefore this criterion is not applicable to the specification. UTF-8 specification: https://datatracker.ietf.org/doc/html/rfc3629'
'The GITB TDL can be customised for a specific project’s testing, independent processing, messaging and validation extensions to address missing capabilities or domain-specific needs. JOINUP reference: https://joinup.ec.europa.eu/collection/interoperability-test-bed-repository/solution/interoperability-test-bed/about GITB TDL reference: https://www.itb.ec.europa.eu/docs/tdl/latest/introduction/index.html#where-is-it-used'
'Given that OAIS purpose is to provide a reference model for the long-term preservation of archives, its implementation is subject to the changes of specific use cases. Such changes can be seen as customisations since they allow to add multiple functionalities not covered by the specification itself. OAIS specification: https://public.ccsds.org/Pubs/650x0m2.pdf'
'The implementation of ELI ensures that legislation is accessible to diverse stakeholders within government frameworks. On one front, it facilitates interoperability among European Public Administrations, promoting seamless data exchange and improving the visibility of administrative data. On the other hand, it contributes to the availability of legislations, encouraging citizens and businesses to stay informed about the initiatives and actions undertaken by public administrations. ELI reference: https://eur-lex.europa.eu/eli-register/about.html'
'IPsec is not related to interfaces. Therefore, this criterion is not applicable to this specification. IPSec reference, What IPSec Does: https://datatracker.ietf.org/doc/html/rfc4301#page-7'
SHACL is not included in a national catalogue from a Member State. The only interest group that is currently supporting SHACL are the Semantic Web users. However, note that SHACL is starting to be promoted by EU Member States as a relevant standard of their national standard catalogue. e.g. the Flemish (Belgium) project OSLO (Open Standard for Local Administrations). See: https://joinup.ec.europa.eu/news/flemish-oslo-project-puts-add
XML is included in several national catalogues from EU Member States. A total of 14 countries listed the XML within their national catalogues (e.g. Belgium, France, Germany, etc.). See: https://www.belgif.be/nl/specifications http://references.modernisation.gouv.fr/sites/default/files/Referentiel_General_Interoperabilite_V2.pdf http://www.cio.bund.de/SharedDocs/Publikationen/DE/Architekturen-und-Standards/SAGA/saga_modul_tech_spez_de_bund_5_0_download.pdf?__blob=publicationFile
'There are two Member States recommending OData in their ICT National Catalogues. These Member States are The Netherlands and France. Netherlands Catalogue reference: https://www.forumstandaardisatie.nl/open-standaarden/aanbevolen France catalogue reference: https://www.numerique.gouv.fr/uploads/Referentiel_General_Interoperabilite_V2.pdf CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
'The iCalendar specification is technology agnostic. It is designed to be independent of any specific technology or platform, allowing it to be used across various software applications and systems for exchanging calendar data in a standardised format. iCalendar specification: https://www.rfc-editor.org/rfc/rfc5545'
Ogg is an open source container format which can multiplex a number of independent streams of audio, video, text (such as subtitles), and metadata. It does not support the first level of maturity of Tim Berners-Lee 5-star schema for Open Data which is to make data available on the Web. Ogg XIPH reference: https://xiph.org/ogg/doc/rfc3533.txt Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/en/
"There are many requirements in the documentation pdf but there's nothing related to conformance requirements, all references relate to the REM Structure and REM Signature requirements. ETSI EN 319 532-3 reference: https://www.etsi.org/deliver/etsi_en/319500_319599/31953203/01.02.01_60/en_31953203v010201p.pdf"
XSD 1.1 allows to define schemas according with specific needs, which allow citizens, businesses or administrations to create schemas. The creation of schemas eases the creation of XML complying with requirements for specific or general purposes. Thus, the implementation of XML schemas do not hamper the interoperability and scalability of systems.
'The specification in itself acts as a method to ensure that policies and laws are developed, implemented and monitored and enhanced following a standardised method that includes, guidelines, recommendations and requirements to reach the objective of exhaustive and comprehensible laws and policies. Better Regulation Guidelines and Toolbox reference: https://commission.europa.eu/law/law-making-process/better-regulation/better-regulation-guidelines-and-toolbox_en Better Regulation Toolbox reference: https://commission.europa.eu/document/download/9c8d2189-8abd-4f29-84e9-abc843cc68e0_en?filename=BR%20toolbox%20-%20Jul%202023%20-%20FINAL.pdf'
"There are already existing documents and studies assessing the JSON's features and performance. In some cases, the study has been carried out in a comprehensive comparison between XML and JSON. Behavior based Comparative analysis of XML and JSON web technologies: https://www.researchgate.net/profile/Hanif_Ullah/publication/321361853_Behavior_based_Comparative_analysis_of_XML_and_JSON_web_technologies/links/5a1eb56f0f7e9b9d5e000bfd/Behavior-based-Comparative-analysis-of-XML-and-JSON-web-technologies.pdf "
The ELI TF is the body in charge of the maintenance and development of the specification. In the ELI Governance document, it is defined how and by who the specification is evolved. Member States are open to participate in the evolution of the specification only with soft requirements like having implemented the specification at a national level and having the knowledge to contribute to the evolution of ELI. ELI reference: https://eur-lex.europa.eu/eli-register/about.html Governance Rules: https://eur-lex.europa.eu/content/eli-register/governance_rules.pdf
By providing structure for the registry of web services, the specification acts as a repository that contains web services descriptions, services providers data and information related to how to access these web services. These registries help to administration and stakeholders to provide information and meet each other with the minimum effort. More specifically, the specification contributes to putting together both, requester and provider, minimising efforts and creating effective services ecosystems. Evidence of its implication on the OOP is that SELIS project is included within one of the main Building Blocks for the accomplishment of the once-only principle, eInvoicing. See: https://joinup.ec.europa.eu/collection/eprocurement/document/secure-electronic-invoicing-service-selis https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/2018/10/25/TOOP%3A+The+Once-Only+Principle
'While it uses the EU’s General Data Protection Regulation (GDPR) as a guiding source for the creation and interpretation of concepts, the ambition and scope of DPV is to provide a broad globally useful vocabulary that can be extended to jurisdiction or domain specific applications. DPV primer document: https://w3c.github.io/dpv/primer/#introduction'
'There has not been found any community sharing their data and results on national platforms. However, IPv4 indirectly encourages the creation of communities on national and European platforms sharing news and updates about IPv4 addresses, such as RIPE organisation. IPv4 IETF: https://www.rfc-editor.org/rfc/rfc791 RIPE organisation: https://www.ripe.net/'
'Following the completion of research into conformity tests and certifications, a tool has been identified that enables the testing of implementations. The "SHACL Test Suite" can be used to test SHACL implementations. Additionally, the format of the tests and the process to evaluate SHACL implementations are defined on a GitHub page by W3C. Moreover, the Test Bed also allows to validate RDF content by means of SHACL shapes. SHACL Test Suite: https://w3c.github.io/data-shapes/data-shapes-test-suite/ SHACL Test Bed: https://interoperable-europe.ec.europa.eu/collection/interoperability-test-bed-repository/solution/interoperability-test-bed/news/shacl-validator-updates SHACL W3C reference: https://www.w3.org/TR/shacl/'
The purpose of IPv6 is not related to the delivery of multilingual services. Therefore this criterion is not applicable to this specification.
There are documents that compare different secured versions of FTP (FTPS and SFTP), and the main differences between them. From there, it can be assessed the efficiency and effectiveness of the usage of FTPS in comparison with other type of FTP. FTPS vs SFTP: https://www.goanywhere.com/blog/2016/11/23/sftp-vs-ftps-the-key-differences
Although TIFF/IT’s purpose is not the long-term preservation of data, it can be used to store data as print-ready pages. Moreover, TIFF is one of the safest image file types available with exclusive standout safety features. Moreover, OpenAire which is an European initiative founded by the European Commission, is recommending TIFF as one of the formats for the preservation of images. OpenAire Initiative: https://www.openaire.eu/about OpenAire Preservation guide: https://www.openaire.eu/data-formats-preservation-guide TIFF/IT ISO reference: https://www.iso.org/standard/34342.html
After searching in the different official European websites, there is no evidence of any cross-border project that use CPOV nor explicit agreements involving the usage of the specification.
'EuroVoc is used for data processing acrosss Europe by the European Insitutions and also the National ones. Moreover, there is the possibility to search European Laws amongst other documents using its classification. It can be done through a EurLex, the European Gateway for regulation. Additionally, it is used in the EU Open Data Portal as a method for knowledge classification. In the EU Open Data Portal, datasets are related and linked to EuroVoc domains that improve the searchability and reuse of information. EU Open Data Portal example: https://data.europa.eu/euodp/es/data/dataset/building-stock-observatory Search by EuroVoc: https://eur-lex.europa.eu/browse/eurovoc.html?params=12,1216#arrow_1216 Publication Office of the European Union: https://op.europa.eu/en/home'
'The specification is not related to the protection of personal data. Therefore this criterion is not applicable to this specification. DCMI About: https://www.dublincore.org/about/ '
'HTTP has been in use by the World-Wide Web global information since 1990. That fact evidences that the standard has the sufficient maturity. HTTP /1.1 RFC 2616 Reference: https://www.rfc-editor.org/rfc/rfc2616.html HTTP/1.1: Semantics and Content, RFC 7231 Reference: https://www.rfc-editor.org/rfc/rfc7231'
'AMQP specification is designed to be implemented and used across various business domains, facilitating the reliable exchange of messages between parties. Its versatility comes from characteristics like its symmetric protocol, interoperable data representation, and flexible messaging layer. OASIS AMQP Reference: http://docs.oasis-open.org/amqp/core/v1.0/amqp-core-complete-v1.0.pdf'
'While SCIM primarily focuses on identity management, its features promote the efficient and consistent reuse of relevant identity information across systems. Organizations can tailor their SCIM implementations to meet their specific needs and ensure that relevant information is exchanged and reused effectively in their identity management processes. SCIM: https://scim.cloud/'
DCAT is included in the catalogues of the Netherlands and Spain. See: https://www.forumstandaardisatie.nl/open-standaarden/lijst https://administracionelectronica.gob.es/pae_Home/dam/jcr:9e2c2877-5103-4934-8440-c60ba2e10c48/Catalogue_of_Standards_NIF_Spain.pdf
'CPOV defines a data model for describing public organisations in the European Union. The Core Public Organisation Vocabulary addresses specific needs of businesses, public administrations and citizens across the European Union. CPOV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-organisation-vocabulary'
JPEG is included in 2 national catalogues of recommended specifications. They belong to Estonia and Spain. The National Interoperability Framework (NIF) of these Member States is fully aligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. National catalogue Estonia: https://www.mkm.ee/sites/default/files/interoperability-framework_2011.doc National catalogue Spain: https://administracionelectronica.gob.es/pae_Home/pae_Estrategias/pae_Interoperabilidad_Inicio/pae_Normas_tecnicas_de_interoperabilidad.html#CATALOGOESTANDARES NIFO factsheets: https://joinup.ec.europa.eu/collection/national-interoperability-framework-observatory-nifo/nifo-factsheets
'The specification is not included in any initiative at European or National level covering privacy aspects. Therefore this criterion is considered not applicable to this specification. FTP Specification Reference: https://datatracker.ietf.org/doc/html/rfc959'
"Assessments of the efficiency of SAREF primarily involve evaluating the performance, scalability, and practicality of implementations. A 2020-paper for the Applied Ontology Journal explains the need for interoperability of IoT healthcare applications and the role of standardised ontologies to achieve semantic interoperability. Furthermore, there is a first attempt to extend SAREF for specific e-Health use cases related to ECG data, which highlights the specification's efficiency across different sectors. SAREF4health - Towards IoT standard-based ontology-driven cardiac e-health systems: https://content.iospress.com/articles/applied-ontology/ao200232"
'The European Union (EU) Member States are currently implementing the INSPIRE Directive and related regulations, included in the ISA programme. This projects includes the usage of XSLT for each member state of the Union. Infrastructure for Spatial Information in Europe: https://ies-svn.jrc.ec.europa.eu/projects/registry-development/wiki/Re3gistry_1_0_documentation#_cp3 '
"JSON strongly supports Tim Berners Lee's 5-star schema for open data. The adoption of JSON fosters the publication of data as open data by means of providing structured data and the usage of non-proprietary formats. Moreover, it helps to link data by means of embedding metadata. Moreover, there is an existing extension of JSON which aims to help and support the Linked Open Data environments. The extension has been developed by the W3C working group specifically in charge of JSON-LD development. Additionally, the W3C has developed a syntax for RDF serialisation using JSON, and JSON-LD is recommended. JSON LD Community: https://www.w3.org/community/json-ld/ JSONLD.org: https://json-ld.org Open Data Goldbook: https://www.europeandataportal.eu/sites/default/files/european_data_portal_-_open_data_goldbook.pdf Tim-Berners-Lee 5 star Open Data: https://5stardata.info/en/ "
The implementation of the specification does not hamper the scalability and interoperability of systems. As part of the stack of the eDelivery Building Block, eDelivery SMP 1.10 allows enabling users to grow according to administrations or businesses' needs. See: https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/Benefits+of+eDelivery
"Schema.org grants data processing permissions through the schema.org type DigitalDocumentPermission. Such metadata improves the reliability of processed data between citizens, businesses and public administrations. Schema.org homepage reference, 'About Schema.org' section: https://schema.org/docs/about.html"
'OASIS is a non-profit consortium that drives the development, convergence and adoption of open standards for the global information society. SAML 2.0 is developed and maintained by OASIS. It also has the support from CEF eID Services and the Connecting Europe Facility (CEF). OASIS Reference: https://www.oasis-open.org/org Connecting Europe Facility (CEF) Community: https://commission.europa.eu/funding-tenders/find-funding/eu-funding-programmes/connecting-europe-facility_en CEF eID Services https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/eIDAS+eID+Profile '
Although TIFF/IT supports the first level of maturity from the Tim Berners-Lee 5-star schema for the Open data, it does not support the main principles for the publication of data as Linked Open Data. 5-star linked open data: https://www.w3.org/DesignIssues/LinkedData.html https://www.w3.org/wiki/LinkedData TIFF/IT ISO reference: https://www.iso.org/standard/34342.html
'OAS supports the creation of APIs that follow the REST architectural style. RESTful APIs are encoded in JSON format which is a way to encode data structures like lists and dictionaries to strings that ensure that they are easily readable by machines. OAS specification: https://spec.openapis.org/oas/latest.html#openapi-specification Tim Berners-Lee in the 5-Stars approach: https://5stardata.info/en/'
UTF-8 is independent of any specification and can be implemented without dependencies with technologies or platforms.
'WSDL is designed to be extensible to accommodate specific requirements and features that may not be covered by the core specification. This extensibility is facilitated through the use of custom elements and attributes in the WSDL document. W3C WSDL specification: https://www.w3.org/TR/wsdl20'
'ETSI TS 119 511 protocols are designed in a way that can be implemented separately depending on the functional goals (see section 4.2) or the preservation service the organisation needs to implement (see section 4.3). Partial implementations, therefore, are allowed in this specification. ETSI TS 119 511 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119511/01.01.01_60/ts_119511v010101p.pdf'
DCAT does no directly help for the provision of application programming interfaces (APIs) or Web services. However, DCAT aims to ensure consistency by providing a standard description of the catalogues and datasets published by data portals across Europe. This description makes datasets more searchable and accessible for data reuse and encourages the data providers to use open data portals for dissemination of reusable data.
'The Core Location Vocabulary specification simplifies the delivery of European public services by providing a standardised framework for describing location data. In this sense, public administrations can offer more efficient and reliable digital services, minimising the need for manual data handling and non-digital document exchange. Core Location Vocabulary: https://interoperable-europe.ec.europa.eu/collection/semic-support-centre/solution/core-location-vocabulary/release/100'
'The purpose of HTTPS is not related to the long-term preservation of electronic records and other kinds of information. Therefore, this criterion is not applicable to this specification. HTTPS specification: https://tools.ietf.org/html/rfc2818 '
After being evaluated compliant with the regulation on standardisation 1025/2012, DNS has been identified by Commission Implementing Decision and included in the European list of ICT Standards for e-procurement. See: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en
The purpose of TIFF/IT is not related to e-accessibility. Therefore, this criterion is considered not applicable to this specification. TIFF/IT ISO reference: https://www.iso.org/standard/34342.html
'The available information does not specifically mention the authenticity and authentication of the roles agents involved in the data transactions. Therefore, this criterion is considered not applicable to this specification. OGC TrainingDML-AI Standard: https://docs.ogc.org/is/23-008r3/23-008r3.html'
The purpose of PAdES is not related to e-accessibility. Therefore, this criterion is considered not applicable to this specification. PAdES ISO reference: https://www.iso.org/standard/67937.html PAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/102700_102799/10277801/01.01.01_60/ts_10277801v010101p.pdf
'ODRL specification is mainly focused on the definition of a common vocabulary for the description and the exchange of access rights and digital materials consumption. In the context of digital content management, it can indirecly help to ensure the trustworthy exchange of data and to contribute the protection of personal by determining access rights and conditions to digital content within which possibly may be there personal data information. W3C specification reference: https://www.w3.org/TR/odrl-vocab/#vocab-core'
'As the specification is an extension of XML, XML can be used to represent the data related to business processes, such as the steps involved, the roles and responsibilities of stakeholders, and the inputs and outputs of each step. XSD Reference: https://www.w3.org/TR/2012/REC-xmlschema11-1-20120405/'
"The Dataspace Protocol is a crucial part of the IDS, as it ensures a minimum viable interoperability between these different frameworks, products, or services. Thanks to this, trust and data sovereignity is possible in International Data Spaces, making data exchanges and interactions inside IDS secure and thus, enabling the exposure of interfaces to access the public administration's services. IDSA Dataspace Protocol Specification: https://docs.internationaldataspaces.org/ids-knowledgebase/v/dataspace-protocol/overview/readme"
There are several studies where implementation of OWL2 has been carried out to prove its scalability. The first paper presents an implementation of OWL2, called Scalable OWL 2 Reasoning for Linked Data which purpose is to introduce scalable reasoning and querying techniques to Semantic Web researchers to make use of Linked Data and large-scale ontologies. The second paper presents a study that evaluates and optimizes an OWL2 implementation based on an Event-based eHealth Context with scalability issues. Moreover, as a general language for representing ontologies and therefore the reality of specific knowledge domains, it can be implemented and extended according to the specific needs without hampering the interoperability. Scalable OWL 2 Reasoning for Linked Data: http://aidanhogan.com/docs/rw_2011.pdf Evaluation and Optimized Usage of OWL 2 Reasoners in an Event-based eHealth Context: http://ceur-ws.org/Vol-1387/paper_6.pdf
'Given the nature of all the core vocabularies developed by the UE domain, platform agnosticism is a key feature, ensuring that the specification remains adaptable and applicable across various technological platforms and environments. Therefore, the specification is platform agnostic. Core Location Vocabulary: https://interoperable-europe.ec.europa.eu/collection/semic-support-centre/solution/core-location-vocabulary/release/100'
'The iCalendar specification (RFC 5545 and its updates) is sufficiently mature and widely adopted for use in the development of digital solutions and services related to calendaring, scheduling, and event management. iCalendar has been in use for many years and has become a de facto standard for representing and exchanging calendar data in the digital world. iCalendar specification: https://www.rfc-editor.org/rfc/rfc5545'
XHTML is included in 2 national catalogues of recommended specifications. They belong to Estonia and Spain. The National Interoperability Framework (NIF) of these Member States is fully aligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. National catalogue Estonia: https://www.mkm.ee/sites/default/files/interoperability-framework_2011.doc National catalogue Spain: https://administracionelectronica.gob.es/pae_Home/pae_Estrategias/pae_Interoperabilidad_Inicio/pae_Normas_tecnicas_de_interoperabilidad.html#CATALOGOESTANDARES NIFO factsheets: https://joinup.ec.europa.eu/collection/national-interoperability-framework-observatory-nifo/nifo-factsheets
'The specification eases the identification of parties capabilities and information to make proper and reliable data exchange between parties. Therefore, by implementing the specification administrative information is clearer and available to every interested party. SMP OASIS reference: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505009'
'The specification is used on the European Materials Modeling Ontology (EMMO) created by the European Materials Modelling Council (EMMC) in order to organise the top level ontology that leads to a better integration of business processes related to material processing. EMMO reference: https://emmo-repo.github.io/ BFO reference: https://www.iso.org/standard/74572.html'
"The specification is associated with the EIRA ABB's in the EIRA Library of Interoperability Specifications (ELIS). DCAT can define the interoperability aspects of the Base Registry, Controlled Vocabulary, Data, Data Model, Data Policies, Data Set, Data Set Catalogue, Data Syntax, Forms Structure, Hash Code, Metadata Reference Data ABBs of the EIRA Semantic View; and the Data Publication Component, Data Publication Service, Metadata Management Component, Metadata Management Service ABBs of the EIRA Technical View. ELIS reference: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/v501"
After checking the different standard catalogues at supra-national level, there is no evidence of the inclusion of JPEG within any European catalogue of standards. ICT technical specifications: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en CEN search tool catalogue: https://standards.cen.eu/dyn/www/f?p=CENWEB:105::RESET:::: CENELEC search tool catalogue: https://www.cenelec.eu/dyn/www/f?p=104:107:0::::FSP_LANG_ID:25
'There have been found some assessments directly addressing CPSV-AP efficiency. Below two examples: the first one of CPSV-AP being evaluated for comprehensiveness and compliance with EU policies, and the second one, a study on the use of CPSV-AP to publish public service descriptions as linked open data. Public Service Models: A Systematic Literature Review and Synthesis: https://ieeexplore.ieee.org/abstract/document/8823991 On using CPSV-AP to publish public service descriptions as linked open data: https://link.springer.com/article/10.1007/s11761-022-00344-6'
'Better Regulation Guidelines and Toolbox is a public asset developed by the European Commission and can be accessed and reused without any payment conditions. Therefore, it can be considered that the specifications is licensed under royalty-free basis and (F)RAND basis. Better Regulation Guidelines and Toolbox reference: https://commission.europa.eu/law/law-making-process/better-regulation/better-regulation-guidelines-and-toolbox_en Better Regulation Toolbox reference: https://commission.europa.eu/document/download/9c8d2189-8abd-4f29-84e9-abc843cc68e0_en?filename=BR%20toolbox%20-%20Jul%202023%20-%20FINAL.pdf'
'HTTPS is already associated to an EIRA ABB in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, HTTPS can define the interoperability aspects of the "Data Exchange Component" "Data Exchange Services" ABBs of the EIRA Technical Application View. ELIS reference: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /solution/elis/release/v501 '
'ETSI TS 119 612 can be applied in any domain and context where the use of time-stamping protocol is realized. Therefore, the specification is usable beyond any business-specific domain and can be used in any kind of organisation. It can be consulted in section 6.Operations in the following document. ETSI TS 119 612 specification: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf'
'iCalendar allows EU institutions to place their publications in the form of a calendar on the Internet. This is the case of EUROSTAT, which delivers the Euro-indicator release calendar in ics format for easy integration into the most popular calendar applications, such as Outlook or Google calendar. Euro-indicators release calendar: https://ec.europa.eu/eurostat/news/internet-calendar iCalendar specification: https://www.rfc-editor.org/rfc/rfc5545'
'CPOV can be implemented in any platform and it is independent of any technology. CPOV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-organisation-vocabulary'
As a vocabulary, the implementation of RegOrg can be tested using methods like SHACL shapes and using semantic reasoners to ensure that the implementation is well-formed. These validation mechanisms can be used with open source tools or lite versions of tools like GrapghDB or Protégé. SHACL validation: https://graphdb.ontotext.com/documentation/free/shacl-validation.html#what-is-shacl-validation Semantic Reasoners List: http://owl.cs.manchester.ac.uk/tools/list-of-reasoners/
CAMSS Assessment of HTTP EIF Scenario v1.0.0
'The Indexed Database API specification is designed to provide a way for web applications to store and retrieve large amounts of structured data locally in a browser, without being tied to a specific domain. Indexed Database API: https://www.w3.org/TR/IndexedDB/'
The adoption of PAdES as electronic signature using PDF for signing online documents does not hamper the scalability of systems. PAdES ISO reference: https://www.iso.org/standard/67937.html PAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/102700_102799/10277801/01.01.01_60/ts_10277801v010101p.pdf
HTML fosters the comprehensibility of administrative data by helping to understand the data published in various formats that makes the administrative data easier to comprehend. HTML W3C reference: https://www.w3.org/TR/html401/
SMTP is a business domain agnostic specification that can be reused in a cross-domain way. SMTP IETF reference: https://tools.ietf.org/html/rfc5321
The purpose of SAMM is not related to the publication of public data as open data. Therefore, this criterion is not applicable to this specification. SAMM webpage: https://owaspsamm.org/ SAMM documentation: https://github.com/OWASP/samm/blob/master/Supporting%20Resources/v2.0/OWASP-SAMM-v2.0.pdf
'DCAT does not directly help for the provision of application programming interfaces (APIs) or Web services. However, DCAT aims to ensure consistency by providing a standard description of the catalogues and datasets published by data portals across Europe. This description makes datasets more searchable and accessible for data reuse and encourages the data providers to use open data portals for dissemination of reusable data. DCAT (v2.0.0) reference: https://www.w3.org/TR/vocab-dcat-2/'
'ISO 3166-1 is intended to identify a country, dependencies and special areas of geographical interest. This specification relates to metadata, and can be used in any system that ingests metadata. Therefore, it can be considered technology-agnostic. ISO 3166-1 reference: https://www.iso.org/standard/72482.html '
'IPv4 provides addressing and routing mechanisms that allow devices and systems to communicate over the internet. This is essential for digital service delivery channels such as websites, mobile applications, cloud services, and APIs that rely on the internet to deliver services. IPv4 IETF: https://www.rfc-editor.org/rfc/rfc791'
'The specification explicitly addresses and enables the implementation of features to guarantee confidentiality such as data minimization. Section 8.4 of ISO 19941 directly mentions data policy portability and how these policies dictate shortened data retention periods, de-identification of data and erasure or masking of records not needed to provide the cloud service. ISO 19941: https://www.iso.org/obp/ui/en/#iso:std:iso-iec:19941:ed-1:v1:en'
The purpose of DCAT is not related to organisational interoperability. Therefore this criterion is not applicable to this specification.
WSDL is publicly available for implementation and study for free on W3C's webpage. See: https://www.w3.org/TR/wsdl20/
"ebXML allows extensibility or the addition of plugins in the specification's ebRIM and ebRS components. Although such extensibility is limited to some of the ebRIM and ebRS features, ebXML RegRep 4.0 - Part 1 and Part 2 specify how extensibility may be achieved, that is, either by extending ebRIM or modifying the ebRS service interface. It is the case of the ebXML RegRep SWG specification, which is an Open Geospatial Consortium's authoring of the ebXML specification and which deals with the use of geo-data in a variety of contexts. ebXML RegRep Part 1, Extending ebRIM section: http://docs.oasis-open.org/regrep/regrep-core/v4.0/csprd01/regrep-core-rim-v4.0-csprd01. html#__RefHeading__39225_1821683062 ebXML RegRep Part 2, Cataloguer Plugin section: http://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-rs-v4.0-os.html#__RefHeading__32575_422331532 ebXML RegRep SWG reference: https://www.ogc.org/projects/groups/ebxmlregrepswg ebXML RegRep OASIS reference: https://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html"
'ETSI TS 119 612 can be applied in any domain and context where the use of the time-stamping protocol is realized. Therefore, the specification is usable beyond any business-specific domain and can be used in any kind of organisation.. It can be consulted in section 6.Operations in the following document. ETSI TS 119 612 specification: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf'
'SAML 2.0 is not a European Standard. SAML2.0 Reference: http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-tech-overview-2.0.html'
At the moment of performing the assessment, XAdES is recommended by the European Union as an eSignature standard to ensure that electronic signatures can be created and validated anywhere in Europe. So, XAdES can be considered as an asset to build innovative solutions. eSignature standards: https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eSignature+standards XAdES ISO reference: https://www.iso.org/standard/56025.html XAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/101900_101999/101903/01.04.02_60/ts_101903v010402p.pdf
MIME is a specification exclusively designed for giving format of files which does not secure the traffic. However, there is an extension of MIME which is called S/MIME that secures the files. MIME reference: https://tools.ietf.org/html/rfc2045
This Core Vocabulary helps public administration with the publication of datasets that includes criteria and evidence. So, it is aligned with the principles of Linked Open Data. Core Criterion and Core Evidence Vocabulary reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-criterion-and-core-evidence-vocabulary 5-star linked open data: https://www.w3.org/DesignIssues/LinkedData.html
'Germany and Cyprus are recommending XACML in their ICT National Catalogues. National Catalogue of Germany: https://www.din.de/en/about-standards/din-standards National Catalogue of Cyprus: https://dits.dmrid.gov.cy/dmrid/dits/dits.nsf/all/B83AA8E4EB4EFD19C225855800288B10/$file/Cyprus% 20eGovernment%20Interoperability%20Framework_new%20EIF_v2.0-To%20Publish.pdf CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards '
Ogg is included in the Spanish national catalogue of recommended specifications. The National Interoperability Framework (NIF) of this Member States is fully aligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. National catalogue Spain: https://administracionelectronica.gob.es/pae_Home/pae_Estrategias/pae_Interoperabilidad_Inicio/pae_Normas_tecnicas_de_interoperabilidad.html#CATALOGOESTANDARES NIFO factsheets: https://joinup.ec.europa.eu/collection/national-interoperability-framework-observatory-nifo/nifo-factsheets
Core Public Service Vocabulary Application Profile is publicly available for its use and implementation. Moreover, it is available for everyone to study with no cost on Joinup webpage. CPSV-AP reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-service-vocabulary-application-profile
Although PNG’s purpose is not to foster the visibility administrative data or services, PNG can help to enhance the visualization and visibility of public administrations by providing content more visible and easy to read. In fact, the specification helps to store and to make images readable for the visualization of data of a public administration. PNG W3C reference: https://www.w3.org/TR/PNG/ PNG ISO reference: https://www.iso.org/standard/29581.html
There are tools assessing the conformity of implementations of the DNS. See: https://gitlab.isc.org/isc-projects/DNS-Compliance-Testing
'The purpose of SAML 2.0 is not related to organisational interoperability. Therefore, this criterion is not applicable to the specification. SAML2.0 Reference: http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-tech-overview-2.0.html'
'The publiccode.yml specification is relevant to data portability because it standardises essential information about public sector software, making it easier to share, adapt, and integrate such software across different platforms and jurisdictions. By creating a consistent, structured format for documenting code, it facilitates smoother data exchange and interoperability between systems, reducing dependency on proprietary formats. This approach aligns with data portability principles by enabling public administrations to reuse, transfer, or adapt software solutions with minimal effort, promoting openness and flexibility across technological solutions. Publiccode.yaml documentation: https://docs.italia.it/italia/developers-italia/publiccodeyml-en/en/master/index.html'
'OAIS appears to be discussed in Joinup as one of the standards eligible for the preservation of digital cinema. The EIF Toolbox, also found in Joinup, recommends OAIS as one of the solutions for the technical interoperability layer. OAIS EIF Toolbox: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/solution/eif-toolbox/solution-earchiving Preservation of digital cinema: https://joinup.ec.europa.eu/collection/rolling-plan-ict-standardisation/preservation-digital-cinema-1'
'ETSI TS 119 432 specifies generally applicable policy and security requirements for Trust Service Providers (TSPs) implementing a service component operating a remote signature creation device. While it does not explicitly address partial implementations, the document defines two different implementations for remote digital signature creation: A JSON-based Implementation based on the Cloud Signature Consortium specification and an XML-based Implementation that follows the OASIS DSS-X standard2. Overall, the specification allows partial implementations but there are essential componenets that ensure alignment with security requirements. ETSI TS 119 432: https://www.etsi.org/deliver/etsi_ts/119400_119499/119432/01.02.01_60/ts_119432v010201p.pdf Architectures and protocols for remote signature applications: https://cloudsignatureconsortium.org/wp-content/uploads/2020/01/CSC_API_V1_1.0.4.0.pdf Digital Signature Service Core Protocols, Elements, and Bindings Version 2.0: https://docs.oasis-open.org/dss-x/dss-core/v2.0/dss-core-v2.0.pdf'
The specification is independent of any software, hardware, or operating system. So it can be said that ODF is independent of any specific technology or platform. ODF ISO reference: https://www.iso.org/standard/66363.html ODF OASIS reference: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office
XAdES Baseline Profile is referenced in the ETSI collection at the European Platform Joinup. Moreover, it can be found for free at ETSI’s webpage See: https://joinup.ec.europa.eu/solution/electronic-signatures-and-infrastructures-esi-xml-advanced-electronic-signature-formats-xades-part-3 https://www.etsi.org/deliver/etsi_ts/103100_103199/103174/02.02.01_60/ts_103174v020201p.pdf
HTTPS is used for any solution using internet, including innovative solutions.
'ISO 19941 does not directly facilitate the publication of data on the web, but it contributes to the broader goal of creating accessible web content, including data, by providing metrics and measurement techniques for assessing accessibility. ISO 19941: https://www.iso.org/obp/ui/en/#iso:std:iso-iec:19941:ed-1:v1:en'
'The TrainingDML-AI Standard provides detailed metadata for formalizing the information model of training data, which could potentially support the long-term preservation of data. OGC TrainingDML-AI Standard: https://docs.ogc.org/is/23-008r3/23-008r3.html'
'IEEE 802.3 is included in several repositories and catalogues of standards at the European level. It is listed on platforms like StandICT.eu and Joinup. Joinup list: https://joinup.ec.europa.eu/collection/ict-standards-procurement/solution/ieee-8023-2015-8023-2015-ieee-standard-ethernet/distribution/ieee-8023-2015-8023-2015-ieee-standard-ethernet StandICT list: https://standict.eu/standards-repository/ieee-8023-2018-ieee-standard-ethernet'
'The publiccode.yml specification does not inherently provide mechanisms for restricting access to information or data. Its purpose is to define metadata for documenting public sector software to facilitate reuse, transparency, and interoperability. While it aids in standardising descriptions and promoting accessibility, it does not include features for controlling access to the documented information or for implementing data access restrictions.'
'The ebXML specification uses message-level security mechanisms to enhance data security. As described in the Oracle document about security features, these mechanisms provide sender authentication for long-running transactions. Thus, by authenticating the data sender, it helps to identify whether a user is verified or not. ebXML security: https://www.oracle.com/technical-resources/articles/enterprise-architecture/ebxml-security1.html ebXML RegRep OASIS reference: https://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html'
'There can be found serialisation extensions to RDF, such as TriG or N-Quads, which are used to encode multiple graphs. Turtle (TTL) is an extension of N-Triples, it introduces a number of syntactic shortcuts which are aimed to ease the parsing, writing and readability. RDF primer document: https://www.w3.org/TR/rdf11-primer/'
'ETSI TS 119 432 is currently in its 1.2.1 version thus, major releases have been published. In addition, public documentation inside the specification has been published about its supporting process, specifically related to change history and issues regarding every version. Annex D of the specification is dedicated to change history while any release related to ETSI TS 119 432 has been published in the TC ESI domain. ETSI TS 119 432: https://www.etsi.org/deliver/etsi_ts/119400_119499/119432/01.02.01_60/ts_119432v010201p.pdf ETSI Technical Committee ESI: https://www.etsi.org/committee/esi'
ODRL is publicly available for implementation and study for free on W3C's webpage. W3C specification reference: https://www.w3.org/TR/odrl-vocab/#vocab-core
ELI was developed in 2017 aiming to help and enhance interoperability across borders when exchanging legal documentation from the different Member States. It has been already implemented by many countries such as Austria, Belgium, Denmark and Finland, amongst others. Within ELI documentation some resources provide visibility on use cases or implementation from several actors. ELI reference: https://eur-lex.europa.eu/eli-register/about.html ELI Testimonials: https://eur-lex.europa.eu/eli-register/testimonials.ht ELI highlights: https://eur-lex.europa.eu/eli-register/index.html ELI Implementation Overview: https://eur-lex.europa.eu/eli-register/implementation.html
'The purpose of EN 16234-1 e-CF is not related to e-accessibility. Therefore, this criterion does not apply to this specification. CEN reference, CEN/TC 428 - ICT Professionalism and Digital Competences (Published standards), EN 16234-1 e-CF: https://standards.cencenelec.eu/dyn/www/f?p=205:110:0::::FSP_PROJECT:67073&cs=15E62ED24D608A5F10D6BEE8E6D50FA10'
'At present, SFIA brings together professional skills, knowledge and behavioural factors, promoting business modelling among the different actors in an organisation. SFIA can be applied by certification providers of all types (public and private). SFIA reference: https://sfia-online.org/en/sfia-8'
'The implementation of this specification improves the interoperability and portability of data in cloud platforms, which can facilitate collaboration and interoperability among different government agencies and departments. This can lead to more streamlined and integrated public services, reducing redundancy and improving the overall citizen experience. ISO 19941: https://www.iso.org/obp/ui/en/#iso:std:iso-iec:19941:ed-1:v1:en'
'SHACL allows for extensions, by including an extension mechanism that enables the expression of more complex conditions using languages such as SPARQL, for example. This flexibility allows users to define custom functions, targets, and rules, enhancing SHACL's capability to handle a wide range of data validation scenarios. In addition, it can also be mentioned the SHACL-ACL extension, which include access control mechanisms and is based on SPARQL. "SHACL-ACL: Access Control with SHACL" study: https://link.springer.com/chapter/10.1007/978-3-031-43458-7_4 SHACL-ACL github: https://github.com/SDM-TIB/SHACL-ACL SHACL W3C reference: https://www.w3.org/TR/shacl/'
After searching for a conformity test to validate JPEG format, no tool has been found with this purpose.
'UDDI has authenticity mechanisms to access, publish and update the data. UDDI, using the AuthenticationMode property and the AutoGetAuthToken property, guarantee an authentication method based on a token system, to publish services in the registry. Authenticating with a UDDI Server reference: https://learn.microsoft.com/en-us/previous-versions/windows/desktop/aa966219(v=bts.10) UddiConnection.AutoGetAuthToken Property reference: https://learn.microsoft.com/en-us/previous-versions/windows/desktop/aa969012(v=bts.10) UddiConnection.AuthenticationMode Property reference: https://learn.microsoft.com/en-us/previous-versions/windows/desktop/aa969010(v=bts.10)'
'ETSI TS 119 432 is maintained by the European Telecommunications Standards Institute (ETSI), a European Standards Organization (ESO) that is recognised as the regional standards body dealing with telecommunications, broadcasting and other electronic communications networks and services. ETSI TS 119 432: https://www.etsi.org/deliver/etsi_ts/119400_119499/119432/01.02.01_60/ts_119432v010201p.pdf'
After searching in the different official European websites, there is no evidence of any cross-border project that use PNG nor explicit agreements involving the usage of the specification.
'The purpose of TOSCA is not related to the implementation of the once-only principle. Therefore, this criterion does not apply to this specification. TOSCA reference: https://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.3/os/TOSCA-Simple-Profile-YAML-v1.3-os.html'
'The application of the once-only principle in all EU Member States public administrations aims at reducing the administrative burden. This specification provides a standardised approach for representing and publishing real-time event data on the web using Linked Data principles, fostering interoperability between public administrations, cross border services and impacts positively the development of eGovernment. LDES specification: https://joinup.ec.europa.eu/collection/semic-support-centre/linked-data-event-streams-ldes'
'The DPV taxonomy and data model can be adapted to the business-specific needs, allowing for partial implementations depending on the requirements of any particular context where it is to be applied. DPV specification: https://w3c.github.io/dpv/primer/'
'OAS takes into account essential safety aspects when it comes to the design of APIs. Security in OAS is tackled with the "Security Requiremet Object" where security mechanisms are settled in order to authorise requests. OAS Security Requirements Object: https://spec.openapis.org/oas/latest.html#security-requirement-object OAS specification: https://spec.openapis.org/oas/latest.html#openapi-specification OAS in Github: https://github.com/OAI/OpenAPI-Specification/#participation'
The purpose of SAMM is not related to the definition of a resusable data model. Therefore, this criterion is not applicable to the specification. SAMM webpage: https://owaspsamm.org SAMM documentation: https://github.com/OWASP/samm/blob/master/Supporting%20Resources/v2.0/OWASP-SAMM-v2.0.pdf 5-star linked open data: https://www.w3.org/DesignIssues/LinkedData.html
'There is no conformity test coming from the IETF, but the specification defines conformance as requirements that can be measured manually. OCSP reference, sections 2.1, 2.2, 2.3: https://datatracker.ietf.org/doc/html/rfc2560'
The purpose of MIME is not related to long term preservation of electronic records. Therefore, this criterion is considered not applicable to this specification. MIME reference: https://tools.ietf.org/html/rfc2045
'A DID is associated with a DID document. DID documents are expressed using the data model and can be serialized into a representation. There are three types of properties: DID document properties, verification method properties and service properties. In this categories there are required properties, but also optional properties which can be implemented depending users needs. DIDs W3C: https://www.w3.org/TR/did-core/#core-properties'
'3 Member States are recommending SHACL in their ICT National Catalogues. This Member States are Belgium, Malta and the Netherlands. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards SHACL W3C reference: https://www.w3.org/TR/shacl/'
'The IPsec specification can be used in conjunction with XAuth (Extended Authentication) to guarantee access only to authorised users. With this extension, it is possible to ensure that data has not been modified by third parties and has reliably reached the receiver. IPSec reference: https://www.rfc-editor.org/rfc/rfc6071.html XAuth authentication mechanism: https://docs.fortinet.com/document/fortigate/7.4.0/administration-guide/277729/using-xauth-authentication'
'SCIM supports publication of data on the web with an open license and in a structured, machine-readable format. The current version of the specification is an open API thus, it can be considered an open standard. SCIM: https://scim.cloud/'
'DCAT-AP is an EU cross-border project consisting in an application profile of DCAT for European data portals. DCAT Application Profile Data: https://joinup.ec.europa.eu/solution/dcat-application-profile-data-portals-europe/about '
'Web Services Description Language (WSDL) itself is not designed or intended to address the long-term preservation of data, information, or knowledge. W3C WSDL specification: https://www.w3.org/TR/wsdl20/'
'The GITB TDL can be used in the conformance and interoperability testing of various domains. For this matter, a large set of elements are defined to match its foreseen testing constructs. GITB TDL reference: https://www.itb.ec.europa.eu/docs/tdl/latest/introduction/index.html#what-is-the-gitb-tdl JOINUP reference: https://joinup.ec.europa.eu/collection/interoperability-test-bed-repository/solution/interoperability-test-bed/detailed-information#domainagnostic'
'A key component of ELI is the implementation of URI template patterns, which guarantee persistent access to resources over time. This feature promotes the long-term preservation of electronic documents, ensuring their continued availability. Furthermore, by providing access to legal documents in a machine-readable format, ELI encourages their reuse and adaptation to other formats, thereby facilitating the evolution of European Public Services. ELI reference: https://eur-lex.europa.eu/eli-register/about.html'
'As an open framework, the TGF specification is published and made freely available for use and adaptation by governments and other stakeholders. When new versions of the TGF are released or updated, they are typically made available for public review and feedback before being finalized. The public review process provides an opportunity for stakeholders to review and comment on the proposed changes, provides feedback on the usefulness and relevance of the framework, and suggests improvements or additions to the specification. OASIS document process: https://www.oasis-open.org/policies-guidelines/ipr/'
PAdES is included in 2 national catalogues of recommended specifications. They belong to the Netherlands, and Spain. The National Interoperability Framework (NIF) of these Member States is fully aligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. See: https://joinup.ec.europa.eu/collection/national-interoperability-framework-observatory-nifo/nifo-factsheets
'The OASIS Technical Committee, in charge of the development of TOSCA, operates under RF (royalty-free) on RAND (reasonable and non-discriminatory) Mode of the OASIS IPR Policy. Therefore, the specification is licensed on a (F)RAND basis. TOSCA reference, Notices section: http://docs.oasis-open.org/tosca/TOSCA/v1.0/os/TOSCA-v1.0-os.html OASIS Intellectual Property Rights Policy, section 10.2.2: https://www.oasis-open.org/policies-guidelines/ipr/'
HTML fosters e-accessibility through helping people with disabilities with digital signs, e-books and other HTML components that make browsing thought an HTML web easier. HTML W3C reference: https://www.w3.org/TR/html401/
'The purpose of OCSP is not related to e-accessibility. Therefore, this criterion is considered not applicable to this specification. OCSP reference: https://datatracker.ietf.org/doc/html/rfc2560'
The purpose of IPv6 is not related to long term preservation of electronic records. Therefore this criterion is considered not applicable to this specification.
'The purpose of MIME is not related to the publication of public data as open data. Therefore, this criterion is not applicable to this specification. MIME specification: https://tools.ietf.org/html/rfc2045 Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/en/ '
The W3C Royalty-Free IPR licenses granted under the W3C Patent Policy apply to all W3C specifications, including HTML5. See: https://www.w3.org/TR/2010/WD-html5-20100624/
'The PROV family of documents is being used by the GDProv project, which is an OWL2 ontology for representing the provenance of consent & data lifecycles with a view towards GDPR compliance. W3C GDPRov WorkingGroup: https://www.w3.org/community/dpvcg/wiki/GDPRov GDPRov ontology: https://github.com/coolharsh55/GDPRov'
'The specification is the basis for this question, therefore, it means that there is a 1 to 1 mapping with all components. EIRA reference: https://interoperable-europe.ec.europa.eu/collection/european-interoperability-reference-architecture-eira/solution/eira/release/610 EIRA Github Repository: https://github.com/CarTool-EC/EIRA'
The objective of the LegalRuleML TC is to extend RuleML with formal features specific to legal norms, guidelines, policies and reasoning; that is, the TC defines a standard (expressed with XML-schema and Relax NG) that is able to represent the particularities of the legal normative rules with a rich, articulated, and meaningful markup language. Moreover, by providing a common model that can close the gap between natural language, text description and semantic normatives the specification fosters the visibility and provision of legal resources and their interchange between systems. Concequently it can be said that the specification fosters the comprehensibility of administrative rules, data, services and decision-making of a public administration. LegalRuleML reference: http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/legalruleml-core-spec-v1.0.html
'Stakeholders and interested parties are suggested to provide feedback on the specification before it is finalized and released. After the public review is done, the development team may make changes to the specification based on the feedback provided by the public review. AKN4EU reference: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/akn4eu'
'The specification is based on XBRL/XML and might be supported in other data exchange formats in the future. The specification takes no stance on what technologies are used in internal business systems.'
The purpose of SMP seems not to be related to long term preservation of electronic records. Moreover, no information has been found to answer positively or negatively to this criterion. Therefore, this criterion is considered not applicable to this specification. SMP OASIS reference: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505009
'The specification is not included in any open repository/catalogue of standards at European level. Indexed Database API: https://www.w3.org/TR/IndexedDB/'
LDAP is a business domain agnostic specification that can be reused in a cross-domain way. LDAP IETF reference: https://tools.ietf.org/html/rfc4511
The Working Group in charge of developing the specification initially provides a light-weight maintenance plan however, it is not a complete maintenance and support process.
"The SHACL specification is highly versatile and can be used across various business domains beyond its initial business-specific applications. SHACL's primary function is to validate RDF (Resource Description Framework) graphs against a set of conditions, ensuring data integrity and consistency. However, this capability is not limited to any particular industry or sector. SHACL W3C reference: https://www.w3.org/TR/shacl/"
'IEEE Std 802.3-2022 does not directly address the secure processing of data. However, it covers data transmission, media access control, and network performance. IEEE Std 802.3-2022 Reference: https://ieeexplore.ieee.org/document/9844436'
'The OASIS Technical Committee, in charge of the development of TOSCA, operates under RF (royalty-free) on RAND (reasonable and non-discriminatory) Mode of the OASIS IPR Policy. Therefore, the specification is licensed on a Royalty-free basis. TOSCA reference, Notices section: http://docs.oasis-open.org/tosca/TOSCA/v1.0/os/TOSCA-v1.0-os.html OASIS Intellectual Property Rights Policy, section 10.2.2: https://www.oasis-open.org/policies-guidelines/ipr/'
There are no disclosures of ISO IPR Database to identify the licensing under the specification. ISO 19005-1:2005 (PDF/A-1) and ISO 19005-2:2011 (PDF/A-2) are not listed in ISO/IEC/ITU Common Patent policy, so it cannot be confirmed that the specification is licensed on a (F)RAND basis. ISO patents: https://www.iso.org/iso-standards-and-patents.html ISO standards and patents IPR database: http://isotc.iso.org/livelink/livelink/13622347/Patents_database.xls?func=doc.Fetch&nodeId=13622347
'LDAP enables the modification or addition of directory entries. Thanks to the authentication methods and access restrictions for certain functions, data accuracy is guaranteed with LDAP. LDAP IETF reference: https://tools.ietf.org/html/rfc4511 Geeksforgeeks reference: https://www.geeksforgeeks.org/lightweight-directory-access-protocol-ldap/'
'The specification can allow customisation under certain circumstances. In section 7.1 it is indicated that OWL custom datatypes can also be used as well as common identifier types, which can be served as RDF datatypes. DCAT (v2.0.0) reference: https://www.w3.org/TR/vocab-dcat-2/ '
TSP can be implemented in any platform and it is independent of any technology. TSP IETF reference: https://tools.ietf.org/html/rfc3161
'TLS 1.3 allows customisation through cipher suite configuration, enabling the prioritisation of specific encryption algorithms, and the adjustment of connection negotiation parameters, such as key exchange, session resumption, and post-handshake authentication, amongst others. TLS 1.3 Extensions reference: https://www.rfc-editor.org/rfc/rfc8446.html#section-4.2'
'ISO 639-2 has been extensively used in the library industry and can also be used for any domain that requires the expression of language in codes. This specification has been implemented in other domains where a linguistic solution was needed, for example in e-procurement (eForms). ISO 369-2 FAQs: https://www.loc.gov/standards/iso639-2/faq.html#5 eForms Language reference: https://docs.ted.europa.eu/eforms/0.5.0/codelists/index.html#_tailored_codelists'
'EuroVoc has the support of the Publication Office of the European Union as a developer community. Publication Office of the European Union: https://op.europa.eu/en/home'
'ISO/IEC 7498:1 is designed to be technology-agnostic. The OSI model is a conceptual framework that outlines the functions of a communication system and organises these functions into seven abstraction layers. It does not prescribe specific technologies, protocols, or implementations. ISO/IEC 7498:1: https://www.iso.org/standard/20269.html'
"The specification is associated with EIRA ABB's in the EIRA Library of Interoperability Specifications (ELIS). It is associated with Data Syntax, Forms Structure, Controlled Vocabulary, Data, Data Mapping, Data Model, Hash Code, Metadata from the Semantic View. ELIS link: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /solution/elis/release/v501 "
There are many testimonial from W3C consistorium that are a reliable example to know that HTML5 is a cross-sector reusable data model: ACCESS, Accessibility Foundation, Adobe, Ayuntamiento de Zaragoza, Ebay / PayPal, Facebook, Intel, Microsoft, NTT Communications, Rakuten, among others See: https://www.w3.org/2012/12/html5-cr.html.en
TIFF/IT is mainly used to store bitmap images that they will be intended to edit. TIFF/IT uses lossless compression, maintaining original quality while reducing in size. However, PSD extension is getting popular to store high quality images for later editing. It uses lossless compression as TIFF/IT and it is supported by any application. TIFF Image file explanation: https://www.canto.com/blog/tiff-image-file/
The purpose of CSS is to give format to web documents, including layout, colours and fonts. Therefore, it allows to improve the visualization so that the information is friendlier and its interpretation is easier. An example of this is EUR-Lex, the cross border gateway to EU Law. It is using CSS to present the different documentation contained in EUR-Lex. Presentation style sheets EU Vocabulary: https://op.europa.eu/en/web/eu-vocabularies/presentation-style-sheets EUR-Lex: https://eur-lex.europa.eu/homepage.html?locale=en
'The specification has not been included in any initiative at European or National level covering privacy aspects. CPSV-AP reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-service-vocabulary-application-profile'
'The ebXML specification can ensure the protection of personal data by establishing mechanisms such as encryption, using XML Encryption. As described in the Oracle document about security features, by using these mechanisms, public administrations can share information among themselves, ensuring that the information cannot be changed and is secured against possible attacks. ebXML security: https://www.oracle.com/technical-resources/articles/enterprise-architecture/ebxml-security1.html XML Encryption: https://www.w3.org/Encryption/2001/ ebXML RegRep OASIS reference: https://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html'
The standard or specification is included in 3 national catalogues. They belong to Member States which comply with at least 4 out of 5 sections of the EIF according to the NIFO factsheets (e.g. the Netherlands, Spain and Sweden) See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
XSD 1.1 is publically available at the European Platform for the reuse of ICT solutions, Joinup. See: https://joinup.ec.europa.eu/solution/w3c-xml-schema-definition-language-xsd-11-part-2-datatypes
The purpose of PDF/A is not related to the availability of interfaces with internal information systems. Therefore, this criterion is not applicable to this specification. PDF/A reference: https://www.iso.org/standard/38920.html https://www.iso.org/standard/50655.html
'ISO/IEC 7498:1 is designed to allow for partial implementations. The layering concept of the OSI model facilitates the development and deployment of network communication protocols in a modular and flexible manner. Each layer in the OSI model is responsible for specific functions, and the interfaces between layers are well-defined. This modular design enables developers to implement only the layers that are relevant to their specific needs. ISO/IEC 7498:1: https://www.iso.org/standard/20269.html'
"The first version of ISO/IEC 19944-1 was first published in 2020. Since then, there has not been made a public review, and there can't either be found market uptake indicators. Nonetheless, it updates the previous standard ISO/IEC 19941 and builds upon ISO/IEC 17788:2014 and ISO/IEC 17789:2014 which are widely used standards for the development of cloud-computing environments. ISO/IEC 17789: https://www.iso.org/standard/60545.html ISO/IEC 19944-1 Joint Technical Committee: https://www.iso.org/committee/601355.html"
'The classification scheme outlined in ISO/IEC 19944-1 can be applied to various types of data within cloud computing, regardless of the specific domain or industry. It provides a framework for categorizing data based on sensitivity, regulatory requirements, and business needs. It is important to note that ISO/IEC 19944-1 serves as a foundational standard for data classification within cloud computing, and organizations may need to consider additional domain-specific standards, regulations, or guidelines to address the specific requirements of their respective industries or sectors. ISO/IEC 19944-1 specification: https://www.iso.org/standard/60545.html'
'The XSLT specification improves the visibility of administrative procedures, rules, data, and services. Its data transformation capabilities, support for multiple output formats, and JSON handling make it a valuable tool for presenting information accessibly (see Section 3.2 for output formats and Section B for JSON transformation). XSLT Reference: https://www.w3.org/TR/xslt-30'
This standard is licensed CC-0, which essentially means that the project, along with the contributions is in the public domain in whatever jurisdiction possible, and everyone can do whatever they want with it. The Standard for Public Code webpage: https://standard.publiccode.net/
'IPv6 is maintained and developed by IETF which is an international community developing open standards. Moreover, the deployment of IPv6 is rapidly expanding in the Internet. Support for IPv6 by private corporations has been lagging behind but these companies, such as Apple, are taking steps to rectify this situation and raise awareness to the problem. IETF organisation: https://www.ietf.org/about/ IPv6 development: https://community.cisco.com/t5/jive-developer-archive-documents/ipv6-for-application-developers-whitepaper/ta-p/3647032'
"DAPS is a crucial part of Identity Providers in the IDS, as it provides short-lived tokens with up-to-date information about connectors. Thanks to this, data privacy and secure data exchange is possible in IDS, which enables the exposure of interfaces to access the public administration's services. DAPS: https://github.com/International-Data-Spaces-Association/IDS-G/tree/main/Components/IdentityProvider/DAPS"
'JSON is being features at the The ENISA 5G Security controls matrix, which is a comprehensive and dynamic matrix of security controls and best practices for 5G networks, to support the national authorities in the EU Member States with implementing the technical measures of the EU’s 5G Cybersecurity Toolbox. JSON specification: https://www.ecma-international.org/wp-content/uploads/ECMA-404_2nd_edition_december_2017.pdf ENISA: https://www.enisa.europa.eu/publications/5g-security-controls-matrix'
'There is no evidence that the specification can be partially implemented, so it is considered that it is only meant to be used as a whole. CPSV-AP Joinup webpage: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/core-public-service-vocabulary-application-profile/release/22'
'The publiccode.yml specification does support multilingualism by allowing metadata entries in multiple languages. This ensures that software documentation can be accessible and understandable to a diverse audience, aligning with the principle of making public services more inclusive across language barriers. By enabling multilingual entries, it caters to the needs of various user groups and supports interoperability at an international level, which is consistent with the EIF’s recommendation on multilingualism. Publiccode.yaml documentation: https://docs.italia.it/italia/developers-italia/publiccodeyml-en/en/master/index.html'
'JSON provides a flexible and widely supported data interchange format that can be leveraged to establish common ground for data exchange between organizations. By agreeing to use JSON as a common language for data representation, organizations can enhance their interoperability, and streamline communication and collaboration across different systems and entities. JSON specification: https://www.ecma-international.org/wp-content/uploads/ECMA-404_2nd_edition_december_2017.pdf'
XML is included in 5 national catalogues. They belong to Member States which comply with at least 4 out of 5 sections of the EIF according to the NIFO factsheets. See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'There is no Member State that includes ETSI TS 102 640-2 in their national catalogue with its National Interoperability Framework (NIF) in alignment with the three categories: 1. Conceptual model for integrated public services provision, 2. interoperability layers, and 3. interoperability principles. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards NIFO Factsheets: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public\x02administration-factsheets-2021'
'Given the number of organisations that contribute to the funding of OAS (Google, IBM, Microsoft, etc) there can be stated that the specification has widespread market acceptance. It is also being implemented in the RISIS project, which aims to develop an e-infrastructure that supports full virtual transnational access to research datasets. Automatic Query-centric API for Routine Access to Linked Data: https://iswc2017.semanticweb.org/wp-content/uploads/papers/MainProceedings/430.pdf RISIS webpage: https://www.risis2.eu/about/ OAS specification: https://spec.openapis.org/oas/latest.html#openapi-specification'
'CSV has been developed and maintained by IETF. Additionally, the W3C has published a recommendation enhancing specific features of the specification. Both organisation are International Organisations concerned with the development of the Internet. CSV reference: https://datatracker.ietf.org/doc/html/rfc4180'
'The specification is used by some Member States, Slovenia, Ireland and Cyprus. Being used is proof that the specification is valid enough to be recommended. List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
'The SHACL specification has been published and is maintained by the World Wide Web Consortium (W3C) organisation. Moreover, there is a W3C GitHub page for SHACL. SHACL github W3C reference: https://w3c.github.io/data-shapes/shacl/ SHACL W3C reference: https://www.w3.org/TR/shacl/'
'SCIM supports extensions as a means of expanding its functionality beyond the core specifications. Extensions in SCIM allow for the inclusion of additional features, attributes, or operations that are not part of the standard core schema. Extensions offer a way to customize and extend the capabilities of the protocol to meet specific requirements of organizations or applications. For instance, section 4.3 of the specification talks about a possible SCIM extension. SCIM: https://scim.cloud/ SCIM RFC Section 4.3: https://datatracker.ietf.org/doc/html/rfc7643#section-4.3'
CLV can be found for free along within the European Collaborative Platform, Joinup. CLV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-location-vocabulary
'The purpose of NUTS is not related to the secure exchange of data. Therefore, this criterion does not apply to this specification. EUROSTAT reference, NUTS Principles and Characteristics section: https://ec.europa.eu/eurostat/web/nuts/principles-and-characteristics'
'The purpose of the specification is not related to the publication of public data as Open Data. Therefore this criterion is not applicable to the specification. TSP Specification: https://tools.ietf.org/html/rfc3161 '
'The PROV family of documents is designed to be platform-agnostic, allowing organizations and developers to implement and utilize PROV concepts on various platforms without being restricted to a specific technology or operating system. PROV Primer document: https://www.w3.org/TR/prov-primer/'
'The purpose of TOSCA is not related to e-accessibility. Therefore, this criterion is considered not applicable to this specification. TOSCA reference: https://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.3/os/TOSCA-Simple-Profile-YAML-v1.3-os.html'
'The Registered Organization Vocabulary was developed by and published by the European Commission ISA Programme with support from the Directorate General Internal Market and Services (DG MARKT). Contributors included representatives of Member States of the European Union, operators of national repositories, standardisation bodies and independent experts whose work was published in May 2012. According to recent discussions on the Core Business Vocabulary GitHub, W3C has discontinued the Registered Organization Vocabulary and the community along with the continuation for the development moved to the Core Business Vocabulary. Currently, it is being used in Open Standards for Linking Organizations (OSLO), but it will be migrated to the Core Business Vocabulary in the near future. Registered Organization Vocabulary specification reference: https://www.w3.org/TR/vocab-regorg/ Directorate General Internal Market and Services (DG MARKT) reference: https://commission.europa.eu/about/departments-and-executive-agencies/internal-market-industry-entrepreneurship-and-smes_en Core Business Vocabulary Github reference: https://github.com/SEMICeu/Core-Business-Vocabulary/tree/master Core Business Vocabulary Github Issue 51 - RegOrg maintenance reference: https://github.com/SEMICeu/Core-Business-Vocabulary/issues/51 RegOrg used in OSLO reference: https://github.com/SEMICeu/Core-Business-Vocabulary/issues/27'
The purpose of the specifications is not related to the visibility of administrative information, data or services. Therefore, this criterion is not applicable to this specification. TSP IETF reference: https://tools.ietf.org/html/rfc3161
'Although some APIs are designed for the long-term preservation of data and information, no specific provisions are stated in OAS. OAS specification: https://spec.openapis.org/oas/latest.html#openapi-specification OAS in Github: https://github.com/OAI/OpenAPI-Specification/#participation'
"As a key enabler for the data exchange and interchange between administrations and stakeholders, JSON enhances the communication and information exchange across borders between public administrations. The flexibility of JSON's hierarchical structure allows for implicit reuse by organizing related information within nested objects. Developers can design their JSON structures to facilitate reuse or referencing based on the specific requirements of their applications or systems. JSON specification: https://www.ecma-international.org/wp-content/uploads/ECMA-404_2nd_edition_december_2017.pdf "
'The specification is done in itself to validate the conformity of the data. Therefore, it is not necessary any external testing platform to allow testing of implementations. DQV reference: https://www.w3.org/TR/vocab-dqv/'
There are no disclosures of ISO IPR Database to identify the licensing under the specification. ISO 15948:2004 (PNG) is not listed in ISO/IEC/ITU Common Patent policy, so it cannot be confirmed that the specification is licensed on a (F)RAND basis. ISO patents: https://www.iso.org/iso-standards-and-patents.html ISO standards and patents IPR database: http://isotc.iso.org/livelink/livelink/13622347/Patents_database.xls?func=doc.Fetch&nodeId=13622347
'HTTP includes features that promote information reuse, through caching and conditional requests. However, the specification also highlights limitations and scenarios where reuse is restricted or requires careful handling. For example, when requests involve authentication or shared caches, those accessible to multiple users, are generally prevented from reusing responses unless specific conditions are met. HTTP /1.1 RFC 2616 Reference: https://www.rfc-editor.org/rfc/rfc2616.html HTTP/1.1 Caching, RFC 9111 Reference: https://www.rfc-editor.org/rfc/rfc9111 '
PAdES does not define a cross-sector reusable data model, but defines an electronic signature format using PDF. PAdES ISO reference: https://www.iso.org/standard/67937.html PAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/102700_102799/10277801/01.01.01_60/ts_10277801v010101p.pdf
ODF does not define a cross-sector reusable data model, but it defines an open source file format. ODF ISO reference: https://www.iso.org/standard/66363.html ODF OASIS reference: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office
'DNS over HTTPS (DoH) is maintained by the Internet Engineering Task Force (IETF). The development and maintenance of DoH is carried out within the Internet Engineering Steering Group (IESG), who is responsible for technical management of IETF activities and the Internet standards process. Furthermore, there is a section in the RFC Editor where any user can report doubts or comments regarding RFC 8484. IESG IETF: https://www.ietf.org/about/groups/iesg/ RFC 8484 Editor Errata: https://www.rfc-editor.org/errata/rfc8484'
The specification is not recommended by any Member State within their national catalogues for ICT. Despite this, eDelivery SMP 1.10 is a European profile recommended by the European public bodies in order to establish a common interoperability framework.
'The XML specification itself does not provide explicit means for the restriction of access to information or data. XML is primarily focused on defining the structure and syntax of markup language documents.Therefore this criterion is not applicable to the specification.'
"Better Regulation Guidelines and Toolbox is not included in any Member States' catalogues of recommended specifications. Better Regulation Guidelines and Toolbox reference: https://commission.europa.eu/law/law-making-process/better-regulation/better-regulation-guidelines-and-toolbox_en CAMSS List of Standards: https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-andspecifications-camss/camss-list-standards"
The purpose of CAdES is not related to the delivery of multilingual public services. Therefore, this criterion is not applicable to this specification. CAdES ISO reference: https://www.iso.org/standard/64756.html CAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/101700_101799/101733/02.01.01_60/ts_101733v020101p.pdf
After being evaluated compliant with the regulation on standardisation 1025/2012, IPv6 has been identified by Commission Implementing Decision. During the evaluation process, all the Member States are invited to share their doubts. The positive evaluation of IPv6 and its identification is considered an interoperability agreement. See: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en
SAMM is a commonly used method for assessing and improving security aspects. It can be considered as a security framework that needs to be followed according to organisations needs to provide compliant and services and data that can be reused across border and institutions without hampering its usefulness and security features. SAMM webpage: https://owaspsamm.org SAMM Documentation: https://github.com/OWASP/samm/blob/master/Supporting%20Resources/v2.0/OWASP-SAMM-v2.0.pdf
'JSON allows the data exchange and consumption from different administrations stakeholders. Ensuring data exchange through applications avoids the interaction by means of reducing the non-digital data exchange. Therefore, the adoption of JSON eases the reduction of administrative burden. JSON specification: https://www.ecma-international.org/wp-content/uploads/ECMA-404_2nd_edition_december_2017.pdf'
'Reviews from CCSDS specification documents are not open to the general public. Instead, only members and associated agencies can take part in the review process by submitting their comment to the review coordinator. CCSDS review documents: https://public.ccsds.org/review/default.aspx'
'The CSV specification itself does not provide any built-in means for protecting against unauthorised changes. Although the CSV specification does not provide these features directly, they can be implemented in conjunction with the systems or applications that handle CSV files to ensure proper access control and data protection. CSV reference: https://datatracker.ietf.org/doc/html/rfc4180'
'The specification supports diverse technological environments given that it ensures broad applicability and adaptability. DIDs W3C: https://www.w3.org/TR/did-core/'
"The SCIM (System for Cross-domain Identity Management) standard is maintained by the Internet Engineering Task Force (IETF). The development and maintenance of SCIM are carried out within the IETF's SCIM working group. IETF Working Groups: https://www.ietf.org/how/wgs/"
The purpose of TIFF/IT is not related to the availability of interfaces with internal information systems. Therefore, this criterion is not applicable to this specification. TIFF/IT ISO reference: https://www.iso.org/standard/34342.html
"ebXML provides a set of components enabling users (data users) to store and work with any type of electronic content. The specification's ebRIM and ebRS components provides an ebXML infrastructure model, as well as a service interface contributing to this end. Therefore, ebXML facilitates the modelling of business processes. ebXML reference: http://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html"
"ESI/REM is already associated with EIRA ABB's in the EIRA Library of Interoperability Specifications (ELIS). More specifically, ESI/REM can define the interoperability aspects of the Registered Eletronic Delivery Service ABB of the EIRA Libreary of Interoperability Specifications. ELIS link: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /solution/elis/release/v110"
SOAP 1.2 can be used independently from any other technical specifications or operating system. As is shown in the SOAP 1.2 FAQ from W3C, SOAP can be adopted with no dependence on WSDL. See: https://www.w3.org/TR/soap12/ https://www.w3.org/2003/06/soap12faq.html
'Given the purpose of this specification, which is to enable organizations and individuals to create and share verified data, the secure exchange of data is explicitly addressed. Verifiable Credentials Security Considerations: https://www.w3.org/TR/vc-data-model/#security-considerations'
HTML5 is included in 2 national catalogues. They belong to Member States which comply with at least 4 out of 5 sections of the EIF according to the NIFO factsheets. See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
TSP can be found for free on IETF's webpage. TSP IETF reference: https://tools.ietf.org/html/rfc3161
'The Better Regulation Guidelines and Toolbox is an internal European Commission resource designed to provide more specific and operational guidance to those involved with the various better regulation instruments. The main goal is to provide simpler, lighter, and faster EU regulation for the citizens and foster the EU competitiveness. Better Regulation Guidelines and Toolbox reference: https://commission.europa.eu/law/law-making-process/better-regulation/better-regulation-guidelines-and-toolbox_en Better Regulation Toolbox reference: https://commission.europa.eu/document/download/9c8d2189-8abd-4f29-84e9-abc843cc68e0_en?filename=BR%20toolbox%20-%20Jul%202023%20-%20FINAL.pdf'
"The EIRA is already in its version 6.1.0, which in itself demonstrates maturity. Moreover, there are several cases where Member States have used EIRA as the basis for planning new Digital Public Services. An example is Madrid's Council, that planned a Smart City Data Space oriented to the efficient management of resources in the city. EIRA reference: https://interoperable-europe.ec.europa.eu/collection/european-interoperability-reference-architecture-eira /solution/eira/release/610 EIRA Github Repository: https://github.com/CarTool-EC/EIRA Interoperability Architecture Solutions Success Stories: https://interoperable-europe.ec.europa.eu/collection/european-interoperability-reference-architecture-eira/success-stories"
IPv6 is a business domain agnostic specification.
There is documentation and examples of the use of services of Regional Internet Services, and examples of tooling and rooter implementations: https://www.ripe.net/manage-ips-and-asns/resource-management/certification https://www.arin.net/resources/rpki/ https://www.apnic.net/get-ip/faqs/rpki/ https://afrinic.net/resource-certification https://www.lacnic.net/640/2/lacnic/general-information-resource-certification-system-rpki https://rpki.readthedocs.io/en/latest/ https://www.juniper.net/documentation/en_US/junos/topics/topic-map/bgp-origin-as-validation.html https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/iproute_bgp/configuration/15-s/irg-15-s-book/irg-origin-as.html https://infocenter.alcatel-lucent.com/public/7750SR160R4A/index.jsp?topic=%2Fcom.sr.unicast%2Fhtml%2Fbgp.html&cp=22_4_7_2&anchor=d2e5366 And there are various websites where compliance can be tested and is even present in various software packages that support the standard: https://ct.cloudflare.com/logs/cirrus https://nusenu.github.io/RPKI-Observatory/ https://rpki-validator.ripe.net/bgp-preview
OpenPM2 is a Project Management Methodology developed by the European Commission, it is focused on increasing project management capabilities. This is not strictly related to the publication of data as open data. Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/en/ OpenPM2 specification reference: https://op.europa.eu/en/publication-detail/-/publication/ac3e118a-cb6e-11e8-9424-01aa75ed71a1/language-en/format-PDF/source-83307127
The purpose of the Core Location Vocabulary is not related to organisational interoperability. Therefore, this criterion is not applicable to the specification. CLV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-location-vocabulary
eDelivery SMP 1.10 is not included in the catalogue of recommended standards of Member States that have a National Interoperability Framework fully aligned with the EIF. See: https://joinup.ec.europa.eu/collection/national-interoperability-framework-observatory-nifo/nifo-factsheets
The main purpose of the Registered Organisation Vocabulary, as well as the Core Business Vocabulary, is to support Public Administrations in the creation of interoperable solutions. So, the specification fosters the development of innovative solutions supporting the Digital Single Market. RegOrg Joinup reference: https://joinup.ec.europa.eu/solution/registered-organization-vocabulary Core Business Vocabulary reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-business-vocabulary
'DPV provides a data model of concepts that act as a vocabulary for the interoperable representation and exchange of information about personal data and its processing. It can help to facilitate interoperability agreements when it comes to applying privacy-friendly policies, as it represents concepts associated with privacy and data protection, primarily derived from GDPR. DPV specification: https://w3c.github.io/dpv/primer/'
At the time of elaborating this assessment, this specification is not included in any EIRA ABB in the last version of the EIRA Library Of Interoperability Specifications (ELIS). However, it has been associated to "Organisational Agreeement" of the Organisational view for the on-going version that is going to be published in May 2021. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis EIRA Library of Interoperability Specifications v1.0.1 (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/v101-0
'The Open API Initiative’s charter created, “an open source, Technical Developer Community (TDC), open to any participant, whether an OAI Member or not. ” The TDC is responsible for overseeing the evolution of the OpenAPI Specification, and for offering suggestions on how to improve it. OpenAPI participation: https://www.openapis.org/news/blogs/2016/07/you-can-get-involved-creating-openapi-specification-and-heres-how OAS specification: https://spec.openapis.org/oas/latest.html#openapi-specification'
The purpose of FTP is not related to long term preservation of electronic records. Therefore this criterion is considered not applicable to this specification
'The specification supports Tim Berners 5-star deployment scheme for Open data since: 1) BFO enables the publication of data on the web under an open licence (owl), 2) BFO makes data available in estructured way (owl), 3) BFO can be used to serialised data in an open format, such as TTL, 4) BFO relies on URIs to denote things, 5) BFO enables linking data in the context of other ontologies BFO reference: https://www.iso.org/standard/74572.html Tim Berners 5-star deployment scheme for Open data: https://5stardata.info/en/# '
'DAPS is not involved in enabling the secure processing of data. DAPS: https://github.com/International-Data-Spaces-Association/IDS-G/tree/main/Components/IdentityProvider/DAPS'
'WSDL has been selected within several cross-border initiatives with the purpose of confirming the description of the services provided in order to enhance the retrieval and support the reuse of the web service by any interested part. An example of a project involving WSDL is the SELIS project. This initiative is focused on eInvocing and its smooth integration within existing accounting software. Moreover, it is included within the framework of the European Digital Single Market and the OOP initiative. Secure Electronic Invoicing Service: https://joinup.ec.europa.eu/collection/eprocurement/document/secure-electronic-invoicing-service-selis'
PDF is included in 3 national catalogues of recommended specifications. They belong to the Netherlands, Spain, and Estonia. The National Interoperability Framework (NIF) of these Member States is fully aligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards https://joinup.ec.europa.eu/collection/national-interoperability-framework-observatory-nifo/nifo-factsheets
Nowadays, SOAP 1.2 is a de-facto messaging protocol for exchanging information in a structured way, and invoke web services SOAP-based. It is used in a wide variety of solutions, while REST is widely used as well, SOAP remains as one of the main protocol to implement SOAs, and this fact includes innovative solutions.
CAMSS Assessment of JSON EIF Scenario v1.0.0
The LegalRuleML is XML base, which allows the estructuration of legal documents data and its exchange between systems. This can also be used for instance, to translate the content to other languages in the European Union. Then the collaboration between Member States can be improved using the method for the alignment of legal frameworks. LegalRuleML reference: http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/legalruleml-core-spec-v1.0.html
FTPS is an extension of FTP that can be easily scaled if 4 principles are taken into account. These principles are explained in the following article. Highly Scalable FTP Site: https://www.ftptoday.com/blog/4-critical-features-of-a-highly-scalable-ftp-site
'EIRA as the reference architecture for developing digital public services in the European context, it covers horizontally from legal to technical aspects, going through organisational and semantic aspects. This way, the specification allows to approach data portability from different perspectives: 1) any possible legal conditions or requirements; 2) organisational limitations and agreements that help overcome transitions between systems; 3) data related requirements and limitations; and last but not least 4) technical requirements that ensure the reuse of best practices and components, as well as international standards that reduce risks. EIRA reference: https://interoperable-europe.ec.europa.eu/collection/european-interoperability-reference-architecture-eira /solution/eira/release/610 EIRA Github Repository: https://github.com/CarTool-EC/EIRA '
'AMQP specification does not guarantee authenticity and authentication of the roles/agents involved in data transactions, but provides mechanisms to facilitate it such as Hostname Verification, the hostname can be specified in the sasl-init frame and the open frame, allowing AMQP proxies to determine the correct back-end service and validate client credentials. OASIS AMQP Reference: http://docs.oasis-open.org/amqp/core/v1.0/amqp-core-complete-v1.0.pdf'
'The Indexed Database API specification is developed by a non-European organisation. Therefore, the specification cannot be considered a European standard. Indexed Database API: https://www.w3.org/TR/IndexedDB/'
The purpose of LegalRuleML aims also to support the semantic perspective of data by providing a core specification for modelling legal documents based on requirements of the business domain. It can be part of the Linked Open Data environment not only supporting the data structuring for raw data but also of rules in conjunction with their functionality and usage. Without rules or axioms, legal concepts constitute just a taxonomy. LegalRuleML reference: http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/legalruleml-core-spec-v1.0.html Linked Data W3C: https://www.w3.org/wiki/LinkedData
'The specification is aimed to represent information in order to be readable in both formats, machine-readable, and human-readable format. Despite this, RDF does not help the availability of interfaces with internal information. RDF primer document: https://www.w3.org/TR/rdf11-primer/'
"The TOSCA cloud-orchestration service provides both the structure of a cloud-based service and orchestration models describing the way the service is managed throughout its lifetime. Although TOSCA offers an end-to-end approach, the specification may facilitate the exposure of interfaces within public administration's services. It is the case of the past CELAR project, which was meant to provide automatic, multi-grained resource allocation for cloud applications and boost administrative performance (see CELAR project reference, Cloud Information System report). TOSCA reference, Glossary section: https://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.3/os/TOSCA-Simple-Profile-YAML-v1.3-os.html#_Toc26969419 CELAR project reference, Cloud Information System report: https://cordis.europa.eu/project/id/317790/reporting"
'The purpose of DAPS is not related to enabling the long-term preservation of data/information/knowledge (electronic records included). Therefore, this criterion is considered not applicable to this specification. DAPS: https://github.com/International-Data-Spaces-Association/IDS-G/tree/main/Components/IdentityProvider/DAPS'
'With the privacy architecture suggested by this specification, personal data can be exchanged on a private, peer-to-peer basis using communication channels identified and secured by verification methods in DID documents. Moreover, verifiable credentials, when associated with DIDs, enable users to assert their identity and qualifications in a privacy-preserving and tamper-evident manner. DIDs restriction of access W3C: https://www.w3.org/TR/did-core/#keep-personal-data-private Nasdaq Verifiable Credentials: https://www.nasdaq.com/articles/what-are-decentralized-identifiers-did-and-how-will-they-boost-web3'
'One of the key principles of the OAIS model is that digital objects and metadata must be preserved over long periods of time, and that their authenticity and integrity must be ensured throughout the preservation lifecycle. To support this principle, the OAIS model includes a range of features and functions that help to ensure the authenticity and integrity of digital objects and metadata such as the data provenance, data integrity and digital signatures. OAIS specification: https://public.ccsds.org/Pubs/650x0m2.pdf'
'The PROV family is a recommendation of the World Wide Web Consortium (W3C), an international community that develops web standards. The W3C is a global organization and not specific to any particular region or country. Therefore, the specification itself is not a European standard. PROV Primer document: https://www.w3.org/TR/prov-primer/ PROV Ontology: https://www.w3.org/TR/2013/REC-prov-o-20130430/ PROV Data Model: https://www.w3.org/TR/2013/REC-prov-dm-20130430/'
'Data processing accuracy is a broader concern that encompasses various aspects of information handling, including data input, processing algorithms, storage, and output. The accuracy of data processing is typically addressed at higher layers of the system architecture and involves considerations beyond the OSI model. ISO/IEC 7498:1: https://www.iso.org/standard/20269.html'
'OASIS has established a comprehensive Technical Committee (TC) process that invites participation from all relevant stakeholders during the specification development journey. For every major and minor release, a public review phase is incorporated, and during this period, feedback from the community is collected and made transparently available for everyone to view and consult. All details pertaining to TC activities are hosted and are readily accessible for reference. OASIS Policies Guidelines: https://www.oasis-open.org/policies-guidelines/tc-process-2017-05-26'
'The SMP is aimed to ease the identification of parties in data exchange. This data exchange can be part of a public service delivered by European Institutions. By easing the discoverability and the connection between parties, the specifications can help and foster the delivery of European Public Services including multilingual ones. SMP OASIS reference: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505009'
Following the purpose of the TC in charge of its development, LegalDocML can ease the accessibility of legal and administrative information commonly used and developed by public organisations and government bodies. The implementation within LEOS project demonstrates the usefulness of the specification in the visibility and the decision-making process of public administrations. Therefore, it can be concluded that the specification fosters the visibility of administrative rules, data, services and decision-making of a public administration. LegalDocML reference: https://www.oasis-open.org/committees/legaldocml/charter.php LEOS: https://joinup.ec.europa.eu/collection/justice-law-and-security/solution/leos-open-source-software-editing-legislation
'TLS 1.3 brings major improvements over its previous version, making it faster and more secure. One major change is the removal of older, less secure cryptographic algorithms like RC4 and SHA-1 and ciphers, ensuring only modern, robust encryption methods are used. TLS 1.3 Cryptographic Negotiation Reference: https://www.rfc-editor.org/rfc/rfc8446.html#section-4.1.1'
CSS is publicly available for implementation and study for free on W3C's webpage. CSS v2.1 W3C reference: https://www.w3.org/TR/2011/REC-CSS2-20110607/
'ShEx is not included in any open repository/catalogue of standards at national level. ShEx primer document: https://shexspec.github.io/primer/ ShEx Community Group: https://www.w3.org/community/shex/ ShEx Github: https://github.com/shexSpec/spec/issues'
PDF is document format highly adopted by organisations and administrations in order to make available their information. Almost all the European platforms share the results of studies and communications in PDF format. An example is the Once-Only principle initiative that provides the new steps and reports by means of PDF documents among others. See: http://toop.eu/deliverables
After checking the different standard catalogues at supra-national level, there is no evidence of the inclusion of CPSV-AP within any European catalogue of standards. ICT technical specifications: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en CEN search tool catalogue: https://standards.cen.eu/dyn/www/f?p=CENWEB:105::RESET:::: CENELEC search tool catalogue: https://www.cenelec.eu/dyn/www/f?p=104:107:0::::FSP_LANG_ID:25
HTTPS allows the access to websites providing information on administrative rules, procedures and services.
'The specification is currently a living document that evolves through its use. The current version is v0.4.0. It has already been implemented at the national level in Italy, serving as the basis for the creation of a national software catalogue. Furthermore, the specification is not only implemented in Italy; it is mandatory for all software developed in the country to comply with it. Publiccode.yaml documentation: https://docs.italia.it/italia/developers-italia/publiccodeyml-en/en/master/index.html Italian National Software Catalogue: https://developers.italia.it/'
As one of the main markup languages for encode web resources, HTML5 is involved in the data exchange. HTML5 files are largely used to exchange information through the web.
'No evidence of direct implementation of DPV in any particular business domain could be found, although use cases can be found in which the DPV vocabulary is intended to be applied, such as online shopping. Data Protection Aspects of Online Shopping - A use case: https://www.w3.org/community/dpvcg/2019/12/12/data-protection-aspects-of-online-shopping-a-use-case/ DPV specification: https://w3c.github.io/dpv/dpv/ DPV primer document: https://w3c.github.io/dpv/primer/#introduction'
'UTF-8 is a sector agnostic specification which means that can be used in any business domain requiring data encoding. UTF-8 specification: https://datatracker.ietf.org/doc/html/rfc3629 '
'The Better Regulation Guidelines and Toolbox fosters the secure and trustworthy access to personal between citizens, businesses and public administrations by proposing methods to ensure that any system and solution developing a public services under the EU law include security regarding data access between the parties involved. In this sens, the Tool 3 provides the stakeholders with some solutions in regards the transmission of confidential information (in this case to a third body, the regulatory board). Better Regulation Guidelines and Toolbox reference: https://commission.europa.eu/law/law-making-process/better-regulation/better-regulation-guidelines-and-toolbox_en Better Regulation Toolbox reference: https://commission.europa.eu/document/download/9c8d2189-8abd-4f29-84e9-abc843cc68e0_en?filename=BR%20toolbox%20-%20Jul%202023%20-%20FINAL.pdf'
'The specification being assessed is a sector agnostic specification that is able to be reused when structured data needs to be exchanged. Additionally, CSV is designed to enable you to reuse the same schema when publishing multiple CSV files, even if those files are created by different organisations and therefore reside in different places. CSV reference: https://datatracker.ietf.org/doc/html/rfc4180'
'The XACML specification contributes to the exposure and management of interfaces for accessing public administration services by enabling a common policy interface across different and diverse systems and devices. XACML OASIS reference: https://docs.oasis-open.org/xacml/3.0/xacml-3.0-core-spec-os-en.html'
TLS is the de-facto open standard for securing internet traffic. It is therefore very important that it is used safely. TLS is used for client-server links and server-server links. Large-scale personal information is exchanged by government parties through these last links. When parties work on (too) old versions of TLS, vulnerable situations arise for the secure exchange of data.
The business domain in which the specification was developed was mainly the administrations and the management of legal, political/administrative and contract management. However, this can be extended to other business domains where this kind of documents are basic for the development of the activity. LegalDocML TC: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=legaldocml
'The PROV Implementation Report describes how to extend PROV specifications by reusing elements of other vocabularies, as defined in the list of reported implementations, thus enabling organizations or systems to extend the core PROV specifications with additional concepts, relationships, attributes, or constraints to accommodate specific requirements or domain-specific needs. Such is the case of PROV-SAID (Procenance of Social Media Information Diffussion) which enables the modelling of provenance of information diffusion in the context of social media. PROV-SAID: http://semweb.mmlab.be/ns/prov-said/ PROV Primer document: https://www.w3.org/TR/prov-primer/ PROV list of reported implementations: https://www.w3.org/TR/2013/NOTE-prov-implementations-20130430/#implementations '
XSLT is maintained by W3C which is an international community developing open standards. See: https://www.w3.org/Consortium/
'Currently no European Member State is recomending ETSI TS 119 512 in its national catalogue. ETSI TS 119 512 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.02_60/ts_119512v010102p.pdf'
'The purpose of ISO/IEC 27001 is other than enabling digital service delivery channels, therefore, this criterion is not applicable to this specification. ISO/IEC 27001 reference website: https://www.iso.org/standard/54534.html'
There are no disclosures of ISO IPR Database to identify the licensing under the specification. ISO 12639:2004 (TIFF/IT) is not listed in ISO/IEC/ITU Common Patent policy, so it cannot be confirmed that the specification is licensed on a (F)RAND basis. ISO patents: https://www.iso.org/iso-standards-and-patents.html ISO standards and patents IPR database: http://isotc.iso.org/livelink/livelink/13622347/Patents_database.xls?func=doc.Fetch&nodeId=13622347
'The OAS is an open-source, royalty-free specification. It is also available with any restrictions related to Fair, Reasonable, and Non Discriminatory ((F)RAND) rights, and it can be accessed from its website and in the Github repository. OAS specification: https://spec.openapis.org/oas/latest.html#openapi-specification OAS in Github: https://github.com/OAI/OpenAPI-Specification/#participation OAS governace rules: https://www.openapis.org/participate/how-to-contribute/governance'
Connecting Europe Facility (CEF) is meant to focus its activity on the improvement of European Cooperation processes and solutions, for both, private and public sectors. The development of the specifications included in the eDelivery building block performance are raised up by CEF eDelivery Team, which does not need to open their decisions by means of public consultations. However, CEF provides several communities focused on gather information related to best practices regarding the implementation of eDelivery. Moreover, the community eDelivery Governance aims to focus efforts to open the operational matters related to CEF building Blocks to all stakeholders for contribution. This fact helps to ensure that all parts take part in the development process, private sector, user organisations and standardisations See: https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery
Core Criterion and Core Evidence Vocabulary is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, CCCEV can define the interoperability aspects of the "Core Data Model" and "Data" ABBs of the EIRA Semantic View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/solution/elis/release/v100
The specification is included in 9 Member States' catalogues of recommended specifications. Some examples of Member States including JSON on their catalogues are the Netherlands, Spain or Belgium. See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'OAS is not included in an open repository/catalgue of standards at the European level. OAS specification: https://spec.openapis.org/oas/latest.html#openapi-specification ICT technical specifications: https://ec.europa.eu/growth/single-market/european-standards/ict-standardisation/ict-technical-specifications_en CENELEC and CEN search tool catalogue: https://standards.cencenelec.eu/dyn/www/f?p=CEN:105::RESET:::: CENELEC and CEN website: https://www.cencenelec.eu/'
'RDF specification does not give any provision for the protection of personal data, nonetheless, there can be found some communities addressing the way RDF-based restrictions for data protection can be applied. The academic paper below gives a framework for the compliance of RDF data processing against the General Data Protection Regulation (GDPR). RDF-based Restrictions for Data-protection: https://ceur-ws.org/Vol-2548/paper-07.pdf'
ETSI and ENISA are recommending its use for the development of software. It is a key aspect to consider that the specification is being considered and recognised for the development of public services. ETSI SmartM2M; Security; Standards Landscape and best practices: https://www.etsi.org/deliver/etsi_tr/103500_103599/103533/01.01.01_60/tr_103533v010101p.pdf ENISA Advancing Software Security in the EU: https://www.enisa.europa.eu/publications/advancing-software-security-through-the-eu-certification-framework ENISA Good Practices for Security of IoT - Secure Software Development Lifecycle: https://www.enisa.europa.eu/publications/good-practices-for-security-of-iot-1
WSDL has adopted the "+xml" convention that is described in the IETF RFC 3023 defining XML data types and its security considerations. As an XML document, every implementation can have different security requirements. Even though, taking into account the considerations WSDL allows the secure and trustworthy data exchange between the stakeholders involved. See: https://www.w3.org/TR/wsdl20/ https://www.ietf.org/rfc/rfc3023.txt
'E-ARK was initially funded by the European Commission under the E-ARK project. Like all European-funded project, it is distributed under a royalty-free license, and can be publicly accessed for anyone to study. E-ARK supporting guidelines: https://dilcis.eu/guidelines/supporting-guidelines'
'DCAT-AP is an RDF vocabulary for representing data catalogues that allows data owners to provide metadata about the datasets they publish. By describing catalogues, datasets and resources, a publisher makes them easily searchable and discoverable. In fact, DCAT-AP is used for the publication of datasets in linked open data portals at a National and European scale (European Data Portal) DCAT-AP for data portals in Europe: https://joinup.ec.europa.eu/solution/dcat-application-profile-data-portals-europe/releases DCAT-AP Specification: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/dcat-application-profile-data-portals-europe/release/200'
By providing information and access to web services across borders, WSDL eases the reuse of data and resources between administrations and stakeholders.
'In the specification's reference document, there is a list of referenced documents necessary for the application of the present document, among those referenced documents is included the "Secure Hash Standard (SHS)" that enables secure processing of data. ETSI TS 119 614-1 reference, page 7: https://www.etsi.org/deliver/etsi_ts/119600_119699/11961401/01.01.01_60/ts_11961401v010101p.pdf'
'OSI is independent of any technological specification and can be implemented without dependencies since its a reference model to facilitate the interconnection between open systems and being cross compatible. OSI reference https://www.iso.org/standard/20269.html'
XSD 1.1 is publicly available for implementation and study for free on W3C's webpage. See: https://www.w3.org/TR/xmlschema11-1/ https://www.w3.org/TR/xmlschema11-2/
Like all the IETF standards, SMTP is a free and open technical specification, built on IETF standards and licenses from the Open Web Foundation. SMTP is therefore licensed on a royalty-free basis. No IPR disclosures have been submitted directly on the SMTP specification (RFC 5321) Intellectual Property Rights in IETF: https://tools.ietf.org/html/rfc3668
'The purpose of the specification is not related to e-accessibility, therefore it does not promote or hinder it. ETSI EN 319 422 reference: https://www.etsi.org/deliver/etsi_en/319400_319499/319422/01.01.01_60/en_319422v010101p.pdf'
'DNS is independent of any specification and can be implemented without relying on other technologies. UBL v2.3 reference: http://docs.oasis-open.org/ubl/os-UBL-2.3/UBL-2.3.html'
'The purpose of JSON is not related to the protection of personal data. Therefore, this criterion is not applicable to the specification. JSON specification: https://www.ecma-international.org/wp-content/uploads/ECMA-404_2nd_edition_december_2017.pdf'
'While HTTPS can contribute to the security and privacy of the data being transmitted, it does not comprehensively address the overall management, visibility, or control of administrative procedures, rules, data, and services. HTTPS specification: https://tools.ietf.org/html/rfc2818'
'DNS over HTTPS (DoH) primarily focuses on securing the transport of DNS queries and responses, adding an additional layer of security to the DNS resolution process. DoH significantly improves online security and privacy by securing DNS queries and minimizing exposure of sensitive information during resolution processes, which is crucial in secure processing of data. DoH specification: https://datatracker.ietf.org/doc/html/rfc8484'
'SCIM is a standardized protocol, and its specifications are designed to work across different technology stacks and platforms. SCIM is not tied to any specific programming language, operating system, or identity management system. SCIM: https://scim.cloud/'
'In terms of administrative procedures, rules data, and services, the OGC TrainingDML-AI standard does not explicitly mention these aspects. However, the detailed metadata it provides could potentially be used to inform such procedures and rules, particularly in the context of preparing and managing training data for AI/ML applications. OGC TrainingDML-AI Standard: https://docs.ogc.org/is/23-008r3/23-008r3.html'
The main purpose of ODF is to exchange information through the internet, and its purpose is not related to the availability of interfaces. Therefore, this criterion is not applicable to the specification. ODF ISO reference: https://www.iso.org/standard/66363.html ODF OASIS reference: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office
'There is not enough information to determine that the ISAE 3402 has been included within an agreement between organisations or countries involved in the provision of public services. ISAE 3402 handbook reference: https://www.ifac.org/system/files/downloads/b014-2010-iaasb-handbook-isae-3402.pdf'
RegOrg is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, RegOrg can define the interoperability aspects of the "Core Data Model" and "Data" ABBs of the EIRA Semantic View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/solution/elis/release/v100
'After searching the different national catalogues, no European Member State has been found to recommend the Extensible Forms Description Language specification. Extensible Forms Description Language reference: https://www.w3.org/TR/NOTE-XFDL'
'The Core Location Vocabulary facilitates the process for institutions to describe data about the location aspects of public organisations, citizens, and businesses. In this context, although the specification is not designed for data reuse, it can help to reuse information among administrations and systems, improving the delivery of public services. Core Location Vocabulary: https://interoperable-europe.ec.europa.eu/collection/semic-support-centre/solution/core-location-vocabulary/release/100'
'Section 5.1.3.2 of the specification is about cloud data portability, which is the ability to transfer data from one cloud service to another cloud service or between a cloud service customer’s system and a cloud service. This section talks about different considerations related to this topic, specially the retrieval of cloud service customer data, which is closely related to long-term preservation of eletrconic resources. ISO 19941: https://www.iso.org/obp/ui/en/#iso:std:iso-iec:19941:ed-1:v1:en'
'The NUTS classification has been developed by a lage community within the European Commission (EC) and all the EC patents are available with any restrictions related to (F)RAND. European Commission reference, Regulation (EC) No 1059/2003 document: https://eur-lex.europa.eu/legal-content/EN/TXT/?qid=1405939838475&uri=CELEX:32003R1059 '
eDelivery SMP 1.10 is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). Specifically, eDelivery SMP 1.10 can define the interoperability aspects of “Metadata Management Component”, “Metadata Management Service”, and “Interoperable European Solution Component” ABBs of the EIRA Technical View. See: https://joinup.ec.europa.eu/solution/elis/distribution/eliscataloguev100betaxlsx
'The purpose of the ESPD is not related to the secure processing of data. Therefore, this criterion is not applicable to the specification. ESPD business handbook: https://docs.ted.europa.eu/ESPD-EDM/latest/xml_business_handbook.html'
'The use of UTF-8 encoding can help to simplify the delivery of public services by supporting multiple languages and scripts, streamlining data processing and exchange, and facilitating integration with international standards and systems UTF-8 specification: https://datatracker.ietf.org/doc/html/rfc3629"'
The specification is one of the main markup languages to develop web resources. XHTML is aligned with 3 out of 5 levels of maturity of Tim Berners-Lee's 5-star, it makes data available on the Web, it publishes the data in a structured way and it makes data available in a non-proprietary open format. So, the specification is highly aligned with the different levels of maturity of Tim Berners-Lee's 5-star schema for Open Data. XHTML W3C reference: https://www.w3.org/TR/xhtml1/ Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/en/
"Yes, the specification is included as part of the solutions and specification in Joinup's collection. Joinup collection reference: https://joinup.ec.europa.eu/collection/support-centre/solution/asset-description-metadata-schema-adms/release/100"
There are several case studies regarding the deployment of IPv6 in Mexico, Greece, USA. See: https://www.internetsociety.org/deploy360/ipv6/case-studies/
'There is specific section in the specification regarding conformance called "Best Practices", which mentions that they are created and published by the International Data Spaces Association and are not considered to be normative. The specification of the Dataspace Protocol itself is normative. Furthermore, IDSA has an interoperability compliance test for technical components to achieve large-scale adoption. Dataspace Protocol Best Practices: https://github.com/International-Data-Spaces-Association/ids-specification/tree/main/best.practices IDSA Reference TestBed: https://internationaldataspaces.org/offers/reference-testbed/'
ASiC Baseline Profile does not define a cross-sector reusable data model. The specification is defining the basic set of requirements for the container formats in the context of AdES. In this requirements are included the three levels of conformance that have to be supported in order to validate electronic signatures.
The purpose of PAdES is not related to the comprehensibility of administrative information, data or services. Therefore, this criterion is not applicable to this specification. PAdES ISO reference: https://www.iso.org/standard/67937.html PAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/102700_102799/10277801/01.01.01_60/ts_10277801v010101p.pdf
The purpose of this Core Vocabulary is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification. CPSV-AP reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-service-vocabulary-application-profile
'HTTP Cookies is a business domain agnostic specification that can be reused in a cross-domain way. HTTP Cookies: https://datatracker.ietf.org/doc/html/rfc6265'
'There are existing documentation and studies assessing the effectiveness of IPsec. In "Testing topologies for the evaluation of IPsec implementations", the IPsec effectiveness is assessed. In this study, IPsec is tested in order to achieve confidence in its effectiveness and correctness. The study also concludes that IPsec architecture supplies a superior standard of protection when it is used with a proper configuration and over a correct implementation. "Testing topologies for the evaluation of IPsec implementations" study: https://www.researchgate.net/publication/221435103_Testing_Topologies_for_the_Evaluation_of_IPSEC_Implementations'
'The Technical Committee (TC) CYBER (Cybersecurity) provides feature requests to open source projects and results of implementation experience to open source communities; however, not in national platforms. TC CYBER reference: https://www.etsi.org/cyber-security/tc-cyber-roadmap'
There is no Member State that includes CLV in their national catalogue with The National Interoperability Framework (NIF) aligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'The Semantic Interoperability Community (SEMIC) develops solutions to help European public administrations perform seamless and meaningful cross-border and cross-domain data exchanges. They develop semantic specifications and interoperability solutions under the ISA² Programme. Specification development process by the ISA Programme: https://joinup.ec.europa.eu/collection/semic-support-centre/solution/core-public-service-vocabulary-application-profile/about#8 Detailed document ISA Programme: https://joinup.ec.europa.eu/sites/default/files/document/2016-10/description_of_a_change_management_release_and_publication_process_for_structural_metadata_specifications_developed_by_the_isa_progr.pdf'
'There is no evidence of the inclusion of WAI-ARIA in an open repository/catalogue of standards at European level. EUOS repository of standards: https://www.standict.eu/standards-repository CENELEC and CEN search tool catalogue: https://standards.cencenelec.eu/dyn/www/f?p=CEN:105::RESET::::'
'CPOV enabels digital service delivery channels in many ways among which we could highlight the browse of public organizations by its function, managing a cross-border repository of public services and organizations, and sharing information G2G (government to government), G2B (government to business) and G2C (government to citizen). CPOV joinup: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/core-public-organisation-vocabulary/distribution/core-public-organisation-vocabulary-version-100-pdf'
'There is no study analysing the effectiveness of OCSP. However, there are several papers claiming that the CRL (certificate revocation list) has been bypassed in favour of the OCSP specification (e.g. from the IEEE), as well as forums (e.g. stackexchange) stating that OCSP offers a faster service. IEEExplore reference: https://ieeexplore.ieee.org/abstract/document/1045949 Stackexchange reference: https://security.stackexchange.com/questions/134100/difference-between-ocsp-crl-and-cdp'
'DQV is useful for describing the quality of the different categories of a dataset. It can help identify where a dataset has more or less quality. Therefore, the specification facilitates the modeling of business processes. DQV reference: https://www.w3.org/TR/vocab-dqv/'
'IPsec is developed by IETF which is based in the USA, thus the specification cannot be regarded as a European Standard. IPSec reference: https://www.rfc-editor.org/rfc/rfc6071.html'
SAML 2.0 is not included in any catalogue of standards at supra-national level.
'While CIM NGSI-LD API does not mention any specific action to support the reuse of relevant information when needed, the principle of reuse and alignment of concepts and relationships are embedded in CIM NGSI-LD API, Linked Data principles can be applied to create a web of interconnected and reusable data, which aligns with the goal of the Once-Only Principle to avoid redundant data collection. GS CIM 009: https://www.etsi.org/deliver/etsi_gs/CIM/001_099/009/01.07.01_60/gs_CIM009v010701p.pdf'
'UBL fosters digital exchange of business documents and invoices by establising a commonly agreed vocabulary of business information transfer. An example of a project implementing UBL for such purpose is ESPD, whose main objective is to create a single procurement document for all European Member States. UBL v2.3 reference: http://docs.oasis-open.org/ubl/os-UBL-2.3/UBL-2.3.html ESPD Handbook: https://docs.ted.europa.eu/ESPD-EDM/3.0.1/xml_business_handbook.html'
'OCSP is maintained and developed by IETF which is an international community developing open standards. IETF developer community: https://www.ietf.org/about/'
'WAI-ARIA is meant to augment semantics in languages such as HTML5 and SVG2, or to serve as an accessibility enhancement technology in other languages that do not specifically include support for ARIA. In this sense, customisation may evolve faster than other web host standards, enabling additional digital service delivery channels. WAI-ARIA reference, section 1.4: https://www.w3.org/TR/wai-aria-1.2/#co-evolution'
'The SAML 2.0 specification allows for customization to a certain extent, and this flexibility is one of the reasons for its widespread adoption. However, there are boundaries to ensure interoperability and security. SAML 2.0 Reference: http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-tech-overview-2.0.html'
'IPv4 offers addresses spaces allowing public services to have unique, globally routable IP addresses for every device. This can simplify direct access to various administrative services without the need for complex NAT (Network Address Translation) configurations. IPv4 IETF: https://www.rfc-editor.org/rfc/rfc791'
'The Dataspace Protocol defines the schemas and protocols required for entities to publish data, negotiate usage agreements, and access data as part of a federation of technical systems termed a dataspace. Therefore, its use improves the interoperability, data sovereignity and standardization of the IDS ecosystem, which is important for the visibility of administrative procedures, rules data, and services. IDSA Dataspace Protocol Specification: https://docs.internationaldataspaces.org/ids-knowledgebase/v/dataspace-protocol/overview/readme'
XSD 1.1 is supporting the second level of maturity of Tim Berners-Lee's 5-stars schema for open data. It eases the availability of the data and structures XML files. Additionally, XSD 1.1 is implied within the RDF 1.1 XML Syntax, used for the serialisation of RDF documents as XML. Therefore, XSD fosters the publication of data as Linked Open Data. Moreover, although XSD is not related directly with Open Vocabularies, it can be found included within the Linked Open Vocabularies. It is possible because datatypes defined by XSD are commonly used as rdfs:range by properties. See: https://5stardata.info/en/ https://www.w3.org/TR/rdf-syntax-grammar/ https://lov.linkeddata.es/dataset/lov/vocabs/xsd
'One of the supporting documents of this CIM NGSI-LD API is ETSI GR CIM 007, which identifies the security and privacy aspects that are relevant when building systems based on the NGSI-LD API and the NGSI-LD information model. In this case, the specification is aligned with the General Data Protection Regulation (Regulation (EU) 2016/679, abbreviated GDPR) is a European Union regulation on information privacy in the European Union (EU) and the European Economic Area (EEA). GR CIM 007: https://www.etsi.org/deliver/etsi_gr/CIM/001_099/007/01.01.02_60/gr_cim007v010102p.pdf GDPR: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32016R0679'
It is worth to note that the specifications is freely available at the SDO's website. Moreover, SMP previous version can be found for free at the European Platform Joinup for its consultation and use. The specification: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505000
'The Testing, Experimentation and Open Source (TST) Working Group provides feature requests to open source projects and results of implementation experience to open source communities. ETSI, as an acknowledged European standardisation, offers different channels for the creation of communities and the sharing of data and results in European platforms. TST NFV reference: https://portal.etsi.org/TB-SiteMap/NFV/NFV-WGs-amp-EGs-ToR'
'The purpose of this Core Vocabulary is not related to provide means for restriction of access to information / data. Therefore, this criterion is not applicable to this specification. CPSV-AP reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-service-vocabulary-application-profile'
'ShEx can be used to validate the data of a public administration while published as RDF. Therefore it could foster its comprehensibility. ShEx primer document: https://shexspec.github.io/primer/ ShEx Community Group: https://www.w3.org/community/shex/ ShEx Github: https://github.com/shexSpec/spec/issues'
The specification is available for its use and implementation at the IETF's webpage defined in several RFCs. LDAP - The Protocol W3C reference: https://tools.ietf.org/html/rfc4511 LDAP - Technical Specification W3C reference: https://tools.ietf.org/html/rfc4510 LDAP - Schema for User Applications W3C reference: https://tools.ietf.org/html/rfc4519
'There is no Member State that includes SFIA in their national catalogue with its National Interoperability Framework (NIF) in alignment with the three categories: 1. Conceptual model for integrated public services provision, 2. interoperability layers, and 3. interoperability principles. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
'The efficiency of the Advanced Encryption Standard specification has been assed by the Institute of Electrical and Electronics Engineers (IEEE), dedicated to standardisation and development in technical areas. In the "Integrated design of AES (Advanced Encryption Standard) encrypter and decrypter" study, a method for integrating the AES encrypter and the AES decrypter into a full functional AES crypto-engine is proposed. "Integrated design of AES (Advanced Encryption Standard) encrypter and decrypter" study: https://ieeexplore.ieee.org/abstract/document/1030726 AES Standard Reference: https://csrc.nist.gov/pubs/fips/197/final'
CSV makes sure content is available on the web, structures data and makes it usable in a non-proprietary open format. Consequently the CSV fosters data portability as it makes available files for any system.
'The European platform Joinup holds many discussion forums and topics regarding the implementation of the ESPD as well as the sharing of solutions related to the specification. ESPD in Joinup: https://joinup.ec.europa.eu/searckeys=ESPD&sort_by=relevance&f%5B0%5D=type%3Adiscussion&f%5B1%5D=type%3Asolutio'
'Contributions to the development of Domibus can be proposed through the eDelivery Governance space, which hosts the eDelivery Operational Management Board (OMB). The OMB provides a vehicle for stakeholders to handle all operational matters of the CEF building block. It aims to ensure that the European Commission leads the implementation process of the building block with the advice of the Member States and to ensure that the private sector, user organisations and standardisation bodies play a role. Domibus FAQs: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/Domibus+FAQs Domibus specification: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/Domibus eDelivery governance space: https://ec.europa.eu/digital-building-blocks/wikis/display/EDELGOV/eDelivery+Governance'
XML is maintained by W3C which is an international community developing open standards. See: https://www.w3.org/Consortium/
Like all the IETF standards, DNS is a free and open technical specification, built on IETF standards and licenses from the Open Web Foundation. DNS is therefore licensed on a royalty-free basis. See: https://tools.ietf.org/html/1034 https://tools.ietf.org/html/1035 https://trustee.ietf.org/
'OData follows REST principles and there exists some kind of privacy mechanisms based on the conformity of the users to third party specifications.The purpose of OData is not related to the security and privacy of the data exchange per se, for this OData relies on the conformity of the user to implement RFC 7231 (HTTP secure transfer). RFC 7231 reference: https://datatracker.ietf.org/doc/html/rfc7231 OData reference: https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#_Toc3135883'
'The effectiveness of genericode is often evaluated through various means, including practical implementations and pilot projects. A 2018-paper related to quantitative finance and economics mentions genericode as one of the standards to follow when researching on big data in finance, which demonstrates the effectiveness of the specification. Complexity, big data and financial stability: https://www.aimspress.com/fileOther/PDF/QFE/QFE-02-03-637.pdf'
'DIDs is included in 1 national catalogue of recommended specifications. It belong to Spain. The National Interoperability Framework (NIF) of Spain is fully aligned with at least 2 out of 3 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards NIFO factsheets: https://joinup.ec.europa.eu/collection/national-interoperability-framework-observatory-nifo/nifo-factsheets Action plan for the deployment of data spaces: https://portal.mineco.gob.es/RecursosNoticia/mineco/prensa/noticias/2024/OdDPlan_actuaciones_despliegue_espacios_datos_v1-0.pdf'
'DCAT-AP is recommended by Belgium, and Denmark. These Member States extended DCAT-AP to meet the specific national needs. CAMSS Lis of standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards Danish catalogue of specifications: https://arkitektur.digst.dk/specifikationer/datasaet'
'GITB provides a framework for conformance and interoperability testing. The test bed increases the efficiency and reliability of interoperable implementation of standards as well as it assures unbiased and objective nature of the standards implementation assessment process. In this regard, there are solutions that include GITB TDL in its implementation procesess, that is the case of eDelivery and the European Single Procurement Document (ESPD) between others. JOINUP reference: https://joinup.ec.europa.eu/collection/interoperability-test-bed-repository/solution/interoperability-test-bed/detailed-information#capabilities GITB document: https://www.itb.ec.europa.eu/docs/tdl/latest/_downloads/0dc573d06adafa1a273edd793577016d/CEN_WS_GITB3_CWA_Final.pdf'
'SAREF is designed to capture the semantics of smart appliances and their functionalities, focusing on interoperability and data exchange within the IoT ecosystem. Therefore, comprehensibility of administrative procedures, rules data, and services are not explicitly within the primary scope of SAREF. SAREF: https://saref.etsi.org/core/v3.1.1/ '
'Yes, the specification can provide means for the restriction of access to information/data, although it is not the primary focus of the schema itself. AKN4EU is primarily designed for structuring and representing legislative documents in a standardized format. AKN4EU reference: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/akn4eu'
"DQV allows to publish, exchange and consume quality metadata, for every step of a dataset's lifecycle. Therefore, the possibility to publish and exchange quality metadata, encourages the implementation of digital services, supporting the principle of digital-first. DQV reference: https://www.w3.org/TR/vocab-dqv/"
PDF/A is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, PDF/A can define the interoperability aspects of the "e-Archiving Component" and "e-Archiving Service" ABBs of the EIRA Technical Infrastructure View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/solution/elis/release/v100
The specification is independent of any software, hardware, or operating system. So it can be said that Core Criterion and Core Evidence Vocabulary is independent of any specific technology or platform. CCCEV reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-criterion-and-core-evidence-vocabulary
Better Regulation Toolbox is publicly available for everyone to study with no cost. Better Regulation Toolbox reference: https://ec.europa.eu/info/sites/info/files/better-regulation-toolbox_2.pdf
'SAML 2.0 is recognized at the European level as part of various initiatives and repositories of standards, most notably within the context of eIDAS. SAML 2.0 Reference: http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-tech-overview-2.0.html CEF eID Services: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/eIDAS+eID+Profile '
SHACL has been used by different vendors such as TopQuadrant for its ontology editor, which is called Topbraid, or Netage, which is using smart data to prevent first responders getting injured. See: https://w3c.github.io/data-shapes/data-shapes-test-suite/
The specification is included in 9 Member States' catalogues of recommended specifications. This Member States are Croatia, Estonia, France, Germany, Greece, Norway, Poland, Spain and Sweden. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'JSON is a langualge-independent data interchange format, which means it can be used with any programming language or platform that supports text-based data transmission and parsing, therefore it can be considered platform-agnostic. JSON specification: https://www.ecma-international.org/wp-content/uploads/ECMA-404_2nd_edition_december_2017.pdf'
'ISO/IEC 27001 can be considered a defacto standard for security and risk management in IT systems. The specification is a common method to ensure securing information and data in IT systems. ISO/IEC 27001 foreword: https://www.iso.org/obp/ui/#iso:std:54534:en '
'The Indexed Database API specification indirectly supports interoperability agreements by providing a standardised method for client-side data storage across different web applications and platforms. While it does not directly address inter-organisational data exchange, it helps ensure that web apps across different organisations can store and access structured data consistently. Indexed Database API: https://www.w3.org/TR/IndexedDB/'
'Every International Standard published by ISO alone, or jointly with the IEC, is subject to a systematic review in order to determine whether it should be confirmed, revised/amended, converted to another form of deliverable, or withdrawn. Moreover, the specification has not been reviwed yet, and it is not a Publicly Available Standard (PAS). ISO public review guide: https://www.iso.org/files/live/sites/isoorg/files/store/en/PUB100413.pdf ebXML RegRep OASIS reference: https://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html ebXML RegRep ISO reference: https://www.iso.org/standard/83479.html'
10 Member States are recommending PDF in their ICT National Catalogues. See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'WSDL specification is not included in a formal open repository or catalog of standards at the European level, such as those maintained by organizations like CEN (European Committee for Standardization) or ETSI (European Telecommunications Standards Institute).'
'IPsec is a business domain agnostic specification and therefore can be implemented in any domain. IPSec reference, Where IPSec can be implemented: https://datatracker.ietf.org/doc/html/rfc4301#page-10'
'The purpose of GITB TDL is not related with data portability. Therefore, this criterion is not applicable to this specification. GITB TDL reference: https://www.itb.ec.europa.eu/docs/tdl/latest/introduction/index.html#what-is-the-gitb-tdl'
"The specification is included in 1 Member State' catalogue of recommended specifications. This Member State is Ireleand. National catalogue Ireland: https://data.gov.ie/pages/opendatatechnicalframework#recommended-standards-for-open-data CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards"
'The Dataspace Protocol is mentioned as one of the bulding blocks that exist in the Data Space Support Centre. The technical building blocks provide a view on the capabilities needed in a data space and provide specifications and references to standards which can assist in their implementation. In this case, the specification is part of the process model of the Control Plane. DSSC Control plane vs. Data plane: https://dssc.eu/space/BBE/178422298/Control+plane+vs.+Data+plane'
'The purpose of EuroVoc is not related to providing an access control mechanism. Therefore, this criterion is not applicable to this specification. EuroVoc: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource /dataset/eurovoc'
'The purpose of IPsec is not related to comprehensibly administrative procedures, rules data, and services. Therefore this criterion is not applicable to this specification. IPSec reference: https://www.rfc-editor.org/rfc/rfc6071.html'
Although SMTP is widely used in the context of e-mail services, having enough maturity and market acceptance for the development of products and services, no evidence has been found that SMTP contributes to the creation of innovative solutions. Despite the findings on many implementations using SMTP, it is not possible to determine the implication of the specification on the creation of innovative solutions.
'The purpose of TLS 1.3 is not related to the modelling of business processes. Therefore, this criterion does not apply to the specification. TLS 1.3 Reference: https://www.rfc-editor.org/rfc/rfc8446.html'
'While SAREF itself is not explicitly designed for data portability, it contributes to broader interoperability goals within the IoT domain as it provides a common formal language for smart appliances. Standardising and structuring IoT data enables an easier and more efficient data portability across different systems and domains in the IoT ecosystem. SAREF: https://saref.etsi.org/core/v3.1.1/ '
The purpose of XHTML is to publish administrative data on the web. By allowing to publish custom data in an understandable format, it fosters the comprehensibility of administrative data. Moreover, it also eases the decision-making process by ensuring the data exchange and data reuse. XHTML W3C reference: https://www.w3.org/TR/xhtml1/
'The purpose of TLS 1.3 is not related to e-accessibility. Therefore this criterion is considered not applicable to this specification. TLS 1.3 Reference: https://www.rfc-editor.org/rfc/rfc8446.html'
After exhaustive research, several cross-border projects or initiatives that use OWL have been found. CELLAR is the repository of the Publications Office of the European Union. His main purpose is to disseminate the content and metadata created by the Publication Office. It drives the Publications Office’s major portals and its resources are semantically described by the CDM (Common Data Model), which is an OWL ontology. Another implementation at European Level is the Application Profile of DCAT developed for the description of the data included in the European Data Portal contributing to the openness of European data._x000D_ CELLAR publication:_x000D_ https://op.europa.eu/en/publication-detail/-/publication/50ecce27-857e-11e8-ac6a-01aa75ed71a1/language-en/format-PDF/source-73059305_x000D_ _x000D_ CELLAR description:_x000D_ https://data.europa.eu/euodp/data/dataset/sparql-cellar-of-the-publications-office_x000D_ _x000D_ DCAT-AP Specification: _x000D_ https://joinup.ec.europa.eu/solution/dcat-application-profile-data-portals-europe/distribution/dcat-ap-121-pdf
The purpose of SHACL is not related in any way to the delivery of multilingual public services. Therefore, this criterion is not applicable.
'AMQP specification is not a European Standard. However, it is an International Standard designated as ISO/IEC 19464:2014. ISO.org Standard Catalog Reference: https://www.iso.org/standard/64955.html'
'The purpose of ESI/REM is not related to the comprehensibility of administrative procedures, rules data and services, therefore it does not promote or hinder it. ETSI EN 319 532-3 reference: https://www.etsi.org/deliver/etsi_en/319500_319599/31953203/01.02.01_60/en_31953203v010201p.pdf'
The specification was developed in 1991 by the IETF group, and it has become a widely used format for the transaction of different types of files over the internet. It is focused on the transfer via email, and it is supported by numerous mail software. This fact demonstrates the maturity of MIME for its use for the development of services and products. MIME reference: https://tools.ietf.org/html/rfc2045
The specification is included in 5 Member States' catalogues of recommended specifications. Examples of Member States including PAdES in their catalogues are France or Spain. See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'ETSI TS 119 612 provides a common time-stamping protocol and token profiles for a Trusted List Scheme Operator (TLSO) to provide information on the status and history of Trusted Service Provider (TSP) services. Since it has had three major versions it would be acceptable to consider it has a sufficient market acceptance for its use. ETSI TS 119 612: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf'
The purpose of UDDI is not related to long term preservation of electronic records. Therefore this criterion is considered not applicable to this specification.
'WSDL provides a standardized way to describe web service interfaces, enabling interoperability between different software systems. This interoperability is crucial when building digital service delivery channels that involve communication between diverse applications and platforms. W3C WSDL specification: https://www.w3.org/TR/wsdl20/'
'The standardised terms and concepts within CIM NGSI-LD API can facilitate clearer communication and understanding between systems, which is beneficial for secure data exchange protocols. When different entities use the same standardised terms and classifications, it can reduce ambiguity and errors during data transmission, contributing to more secure and accurate exchanges. ETSI Context Information Management (CIM); Security and Privacy: https://www.etsi.org/deliver/etsi_gr/CIM/001_099/007/01.01.02_60/gr_cim007v010102p.pdf'
TSP is a business domain agnostic specification that can be reused in a cross-domain way. TSP IETF reference: https://tools.ietf.org/html/rfc3161
'The main purpose of BFO is related to the provision of a hierarchy of categories to be used in multiple fields to classify and organise data. This core element of BFO is what gives it the possibility to be developed into an ontology dedicated to long term preservation of data, for example by referencing linked data via the use of IRIs. BFO reference: https://www.iso.org/standard/74572.html'
After searching in the different official European websites, agencies such as ENISA or ETSI are recommending SAMSS as one of the reference frameworks for the development of secure software solutions. ETSI SmartM2M; Security; Standards Landscape and best practices: https://www.etsi.org/deliver/etsi_tr/103500_103599/103533/01.01.01_60/tr_103533v010101p.pdf ENISA Advancing Software Security in the EU: https://www.enisa.europa.eu/publications/advancing-software-security-through-the-eu-certification-framework ENISA Good Practices for Security of IoT - Secure Software Development Lifecycle: https://www.enisa.europa.eu/publications/good-practices-for-security-of-iot-1
XSD 1.1 is an open specification that can be used independently from other technologies or platforms. However, XSD 1.1 is defining datatypes which depend on definitions in XML and Namespaces in XML. This fact is not hampering the adoption of XSD as XML is worldwide adopted.
'CAdES does not directly define or expose technical interfaces for accessing public administration services._x000D_ However, the specification provides a standardised, machine and human-readable structure for electronic signatures on electronic documents, which facilitates interaction between citizens and public administrations when submitting information through public administration portals. In this regard, using another specifications based on CAdES like XAdES or PAdES for the most used fileformats like XML or PDF it becomes more simple to share documents among the stakeholders._x000D_ _x000D_ eIDAS regulation: _x000D_ https://digital-strategy.ec.europa.eu/en/policies/eidas-regulation_x000D_ _x000D_ CAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31912201/01.03.01_60/en_31912201v010301p.pdf_x000D_ _x000D_ PAdES reference: _x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31914201/01.02.01_60/en_31914201v010201p.pdf_x000D_ _x000D_ XAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31913201/01.03.01_60/en_31913201v010201p.pdf_x000D_ '
'The efficiency of the CAdES specification has been assessed on the article from the conference 2024 Innovations in Intelligent Systems and Applications Conference (ASYU) in Ankara. In the conference the authors defined the properties for long term data preservation related to CAdES an its efficiency._x000D_ _x000D_ "Unlocking the Size Advantage of New Standard: CAdES Signatures with Long-Term Validity" reference:_x000D_ https://doi.org/10.1109/ASYU62119.2024.10757034_x000D_ _x000D_ CAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31912201/01.03.01_60/en_31912201v010301p.pdf'
'CAdES guarantees that signed data on electronic format remains authentic, integral, and legally defensible when transmitted or archived. CAdES signatures, especially when based on Qualified Certificates (which are common in Public Administrations under eIDAS), link the document directly to a verified identity._x000D_ _x000D_ CAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31912201/01.03.01_60/en_31912201v010301p.pdf'
'ETSI’s decision-making process includes a public review, where stakeholders involved can provide technical feedback in order to enhance and maximize the quality and accuracy of the standards. ETSI standard-making process: https://portal.etsi.org/Resources/Standards-Making-Process/Process'
'The CAdES specification is not related to data portability of data between systems/applications. Therefore this criterion is not applicable to the specificaction._x000D_ _x000D_ CAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31912201/01.03.01_60/en_31912201v010301p.pdf'
'The CAdES Baseline Signature function is to facilitate the electronic signature in compliance with eIDAS regulation. The signature of a document can provide the involved stakeholders with the possibility to use the extensions on the signature in order to define specific legal or policy references relevant to the context of the signed document like confidentiality._x000D_ _x000D_ CAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31912201/01.03.01_60/en_31912201v010301p.pdf'
"The CAdES Baseline signatures helps users simplify the usage of electronic signatures in electronic documents by (at the most basic signature level) using the SignedData.certificates attribute which includes the signed data itself, the signature value, and enough information to identify the signatory's certificate at the time of signing. This way, the users are provided with the relevant information about the document and it's signataires straightforward, thus enhancing user understanding of the document._x000D_ A practical example of this is the CEF Digital Signature Service (DSS), which leverages CAdES to provide clear and verifiable electronic signatures. Through DSS, users can easily verify signature validity and timestamp information, helping improve trust and transparency in_x000D_ electronic communications._x000D_ _x000D_ DSS reference: _x000D_ https://ec.europa.eu/digital-building-blocks/DSS/webapp-demo/doc/dss-documentation.html#CAdES_x000D_ _x000D_ eIDAS regulation: _x000D_ https://digital-strategy.ec.europa.eu/en/policies/eidas-regulation_x000D_ _x000D_ CAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31912201/01.03.01_60/en_31912201v010301p.pdf"
'CAdES started development as RFC 5126 by IETF, which was built on the already existing standards RFC 5652, ISO/IEC 9594-8/ITU-T Recommendation X.509, RFC 3280 and RFC 3161 (as section-9.1 and 2 of the specification)._x000D_ _x000D_ The specification at that point introduced the concept of multiple signature forms to achieve increasing levels of security and preservation. With the enforcement of the eIDAS Regulation (EU No 910/2014) the CAdES specification was restructured and aligned with the core principles of the regulation by ETSI._x000D_ Therefore, the major difference with the previous release of the specification (ETSI TS 119 122-1) from 2015 is the aligment with the eIDAS Regulation but also the incorporation of technical updates to align with ETSI TS 119 312 (Cryptographic Suites) to support more secure algorithms and address the latest advances in cryptographic evolution._x000D_ Alongside this, CAdES has had a regular flow of minor releases to clarify certain technical aspects as it can be seen on the Annex F of the specification. This means CAdES is a consolidated and mature enough specification to use in the development of digital solutions and services. _x000D_ _x000D_ ETSI TS 119 312 (Cryptographic Suites) reference:_x000D_ https://www.etsi.org/deliver/etsi_ts/119300_119399/119312/01.04.03_60/ts_119312v010403p.pdf_x000D_ _x000D_ CAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31912201/01.03.01_60/en_31912201v010301p.pdf_x000D_ _x000D_ eIDAS Regulation reference:_x000D_ https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv:OJ.L_.2014.257.01.0073.01.ENG_x000D_ _x000D_ RFC 5652 Cryptographic Message Syntax (CMS) reference:_x000D_ https://www.ietf.org/rfc/rfc5652.txt_x000D_ _x000D_ ISO/IEC 9594-8/ITU-T Recommendation X.509 Public-key and attribute certificate frameworks reference:_x000D_ https://www.iso.org/obp/ui/#iso:std:iso-iec:9594:-8:en_x000D_ _x000D_ RFC 3280 Certificate and Certificate Revocation List (CRL) Profile reference:_x000D_ https://www.rfc-editor.org/info/rfc3280_x000D_ _x000D_ RFC 3161 Internet X.509 Public Key Infrastructure Time-Stamp Protocol (TSP) reference:_x000D_ https://www.ietf.org/rfc/rfc3161.txt_x000D_ _x000D_ RFC 5126 reference: https://www.rfc-editor.org/rfc/rfc5126'
'ETSI has provided a conformance testing tool for electronic signatures. The conformity testing tool involves different standards applied in the development of eSignatures, including PAdES, CAdES and XAdES and their respective baseline profiles. _x000D_ _x000D_ CAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31912201/01.03.01_60/en_31912201v010301p.pdf_x000D_ _x000D_ Conformance Checker reference _x000D_ https://signatures-conformance-checker.etsi.org/'
'The CAdES Baseline Signatures is a set of well-defined technical specifications developed by ETSI to ensure both interoperability and legal validity of electronic signatures across Europe, in line with the eIDAS Regulation. The specification includes several signature levels: CAdES-B, CAdES-T, CAdES-LT, and CAdES-LTA, which can be implemented individually based on the desired properties._x000D_ These levels are designed to be incremental, meaning that a basic signature (CAdES-B) can be progressively enhanced to include additional features like timestamps or long-term validation data, depending on user or system requirements._x000D_ _x000D_ CAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31912201/01.03.01_60/en_31912201v010301p.pdf_x000D_ _x000D_ eIDAS regulation: _x000D_ https://digital-strategy.ec.europa.eu/en/policies/eidas-regulation'
'The CAdES Baseline signatures function is to facilitate the electronic signature in compliance with eIDAS. In this sense, the specification provides with the "complete-certificate-references" attribute, which shall contain the reference to the certificate of the trust anchor if such certificate does exist._x000D_ This means that a system receiving the signed document doesn't need to perform an entirely new validation process from scratch. It can reuse the included data to verify the signature's authenticity._x000D_ _x000D_ CAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31912201/01.03.01_60/en_31912201v010301p.pdf'
'The CAdES Baseline Signatures includes mechanisms for long-term validation, such as timestamps and embedded certificate information. This means that a signed public record or contract can be securely archived and remain legally verifiable for some time. In this regard the preservation of the date of signature is a partial preservation of the record. The highest baseline level, CAdES-LTA (Long-Term Archival), facilitates the long term data preservation through the Document Time-Stamp (Archive Time-Stamp Token attribute) which is a cryptographic seal placed over the entire document structure and all embedded signatures._x000D_ When a new Document Time-Stamp is applied (a form of periodic extension), it essentially reuses the integrity of all preceding data, including the certificate data already present in the document certificate._x000D_ This proves that the validation data (certificates and revocation checks) existed and was valid at the time the Document Time-Stamp was applied, effectively "re-certifying" the entire package against the threat of future cryptographic breaking or certificate expiry._x000D_ _x000D_ CAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31912201/01.03.01_60/en_31912201v010301p.pdf'
'The CAdES specification can be found used in different European projects and also by Member States. Since it is suitable for advanced electronic signatures in electronic documents, it is used by companies and public administrations to sign multiple documents. In this context, the specification has been selected within the CEF Digital Signature Service (DSS) along with PAdES, ASiC and XAdES Baseline profiles. Digital Signature Service is an open-source software library for electronic signature creation and validation supporting the interoperability of electronic signatures. The initiative is an enabler for cross borders interoperability between administrations and businesses. Applications such as eCoSignature from the Ministry of Industry and Commerce of Spain use CAdES as one of their base specifications. _x000D_ _x000D_ _x000D_ eCoSignature reference (EN):_x000D_ https://firmaelectronica.gob.es/en/ciudadanos/cosas-deberias-saber/formatos-firma_x000D_ _x000D_ DSS reference:_x000D_ https://ec.europa.eu/cefdigital/DSS/webapp-demo/doc/dss-documentation.html _x000D_ _x000D_ eSignatureHub - Digital Signature Service DSS:_x000D_ https://ec.europa.eu/digital-building-blocks/sites/spaces/DIGITAL/pages/467109107/Digital+Signature+Service+-+DSS _x000D_ _x000D_ CAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31912201/01.03.01_60/en_31912201v010301p.pdf'
'The CAdES Baseline signatures guarantees authenticity by cryptographically linking the signature to a specific individual and their certificate. In this sense the signature must be applied after the file has been encrypted. So, while the encryption is done beforehand it will be intrinsically tied to the user signing the document._x000D_ _x000D_ CAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31912201/01.03.01_60/en_31912201v010301p.pdf'
'CAdES is within the European eIDAS regulation which is legally binding for all EU members states. CAdES is also a core element of the EUDI Wallet initiative of the European Union, defined under the revised eIDAS Regulation 2.0. It is a secure, EU-backed digital wallet (typically a mobile application) designed to empower EU citizens, residents, and businesses with a universally recognised, user-centric, and privacy-preserving means of digital identification and authentication across the entire European single market. _x000D_ _x000D_ EUDI Wallet reference:_x000D_ https://eur-lex.europa.eu/eli/reg_impl/2024/2979/oj_x000D_ _x000D_ CAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31912201/01.03.01_60/en_31912201v010301p.pdf'
'While the primary purpose of the CAdES Baseline Profile may not be focused on data integrity, its design supports mechanisms that uphold it. The different signature levels allow stakeholders to incorporate additional fields that can facilitate the detection of unauthorised changes, thereby reinforcing document integrity._x000D_ _x000D_ CAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31912201/01.03.01_60/en_31912201v010301p.pdf'
'The purpose of the CAdES Baseline Signatures is not related to modelling business processes. Therefore, this_x000D_ criterion is not applicable to this specification._x000D_ _x000D_ CAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31912201/01.03.01_60/en_31912201v010301p.pdf'
'CAdES is maintained by ETSI, one of the European Agencies for Standardisation, specifically by the ETSI Technical Committee Electronic Signatures and Trust Infrastructures (ESI)._x000D_ _x000D_ ETSI reference:_x000D_ https://www.etsi.org/about _x000D_ _x000D_ Electronic Signatures and Trust Infrastructures (ESI) reference:_x000D_ https://www.etsi.org/committee/1399-esi_x000D_ _x000D_ CAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31912201/01.03.01_60/en_31912201v010301p.pdf'
'ETSI’s standards-making process has been clearly defined after years of experience. The organisation has adopted the open approach which means direct participation and consensus as a basis to develop standards. All the stakeholders have the opportunity to participate directly in the process of standardisation through the technical committees created to develop ETSI’s technical specifications and standards. ETSI Standard-making process: https://portal.etsi.org/Resources/Standards-Making-Process/Process'
'CAdES is not related to publication of data on the web. Therefore, this criterion is not applicable to the specification._x000D_ _x000D_ CAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31912201/01.03.01_60/en_31912201v010301p.pdf'
"CAdES is included in 5 national catalogues of recommended specifications. They belong to Croatia, Cyprus, France, Poland and Spain. The National Interoperability Framework (NIF) of Spain and France are aligned with at least 3 out of 4 scoreboards of the EIF Monitoring according to the National Interoperability Framework Observatory (NIFO) factsheets._x000D_ _x000D_ CAMSS List of Standards: https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards_x000D_ _x000D_ NIFO Factsheets:_x000D_ https://interoperable-europe.ec.europa.eu/collection/iopeu-monitoring/digital-public-administration-factsheets-2024_x000D_ _x000D_ France's catalogue:_x000D_ https://www.numerique.gouv.fr/offre-accompagnement/reference-interoperabilite-rgi/_x000D_ _x000D_ Spains's catalogue:_x000D_ https://administracionelectronica.gob.es/pae_Home/dam/jcr:97912041-c1c3-47c4-b517-df9f51db321d/Guia_aplicacion_Norma_Tecnica_Interoperabilidad_Catalogo_de_estandares.pdf_x000D_ _x000D_ Poland's catalogue: http://isap.sejm.gov.pl/isap.nsf/download.xsp/WDU20170002247/O/D20172247.pdf _x000D_ _x000D_ Cyprus catalogue: https://dits.dmrid.gov.cy/dmrid/dits/dits.nsf/all/B83AA8E4EB4EFD19C225855800288B10/$file/Cyprus%20eGovernment%20Interoperability%20Framework_new%20EIF_v2.0-To%20Publish.pdf _x000D_ _x000D_ Croatia's catalogue:_x000D_ https://ssi.gov.hr/en/catalogue _x000D_ _x000D_ _x000D_ CAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31912201/01.03.01_60/en_31912201v010301p.pdf"
'The CAdES Baseline signatures provides the involved stakeholders with a legally binding signature structure to formalise interoperability agreements. In this sense it provides the foundation of any agreement among any kind of participants. The specification also fosters and facilitates agreements by establishing a common method for signing electronic documents and data in a secure and trustworthy manner. This enables documents to be exchanged in an interoperable way, ensuring that all parties can access the documents and trust the information or data contained within them. By providing a standardised approach, CAdES helps to build confidence between parties and supports the reliable execution of digital transactions._x000D_ _x000D_ CAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31912201/01.03.01_60/en_31912201v010301p.pdf'
'The effectiveness of the CAdES specification has been assessed in conjunction with other electronic signature specifications in an article on the "Special Issue Advanced Research in Technology and Information Systems" of the "Electronics" publication called "A Comprehensive and Privacy-Aware Approach for Remote Qualified Electronic Signatures". In the article the authors value the specification effectiveness in the integration with other cryptographic resources like blockchain and its eIDAS conformity._x000D_ _x000D_ CAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31912201/01.03.01_60/en_31912201v010301p.pdf_x000D_ _x000D_ A Comprehensive and Privacy-Aware Approach for Remote Qualified Electronic Signatures reference:_x000D_ https://doi.org/10.3390/electronics13040757'
'CAdES baseline signatures provides the stakeholders with the certainty that the exchanged documents are truthful for all. In this regard the different signature levels (B Basic, T Time, LT Long-Term and LTA Long-Term Archive) that can be embedded on the document provide a wide arrangement of security levels to guarantee the correct and secure transmission of data and no tempering of it._x000D_ _x000D_ CAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31912201/01.03.01_60/en_31912201v010301p.pdf'
'CAdES achieves multilingual support through its reliance on the Cryptographic Message Syntax (CMS) and the old X.509 certificates, which are fundamentally based on international standards like Unicode/UTF-8._x000D_ _x000D_ In particular, the entire structure of a CMS object is defined using ASN.1 (Abstract Syntax Notation One) and then encoded into a binary format. ASN.1 encoding rules (GSER) include a string type called UTF8String, which ensures that the characters are encoded using UTF-8._x000D_ _x000D_ _x000D_ Generic String Encoding Rules (GSER) for ASN.1 Types reference:_x000D_ https://datatracker.ietf.org/doc/html/rfc3641_x000D_ _x000D_ CAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31912201/01.03.01_60/en_31912201v010301p.pdf'
"The CAdES baseline signatures has sparked some online communities that discuss the specification's implementation in regards to others as well as the data related to it. It also created numerous questions and debates on developer forums like stackoverflow._x000D_ _x000D_ Docusign community: https://community.docusign.com/esignature-111/xades-cades-or-pades-2917_x000D_ _x000D_ Stack-overflow communities and discussions:_x000D_ https://stackoverflow.com/questions/tagged/cades_x000D_ _x000D_ CAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31912201/01.03.01_60/en_31912201v010301p.pdf"
'The purpose of the CAdES baseline signatures is not related to data processing. Therefore this criterion is not applicable to this specification._x000D_ _x000D_ CAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31912201/01.03.01_60/en_31912201v010301p.pdf'
'The purpose of the CAdES Baseline Signatures is not related to e-accessibility. Therefore, this criterion is not applicable to this specification._x000D_ _x000D_ CAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31912201/01.03.01_60/en_31912201v010301p.pdf'
'CAdES Baseline Signatures is a business sector agnostic specification which is reusable beyond the domain for_x000D_ which it was developed. Specifically, implemented to facilitate the electronic signature in compliance with_x000D_ eIDAS. _x000D_ _x000D_ eIDAS regulation: _x000D_ https://digital-strategy.ec.europa.eu/en/policies/eidas-regulation_x000D_ _x000D_ CAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31912201/01.03.01_60/en_31912201v010301p.pdf'
'The CAdES Baseline signatures function is to facilitate the electronic signature documents in compliance with eIDAS regulation. In this sense, the specification, in conjuction with other specifications such as PAdES, ASiC and XAdES can enable the visibility of administrative procedures, as shown with the CEF Digital Signature Service (DSS). _x000D_ _x000D_ eIDAS regulation: https://digital-strategy.ec.europa.eu/en/policies/eidas-regulation_x000D_ _x000D_ DSS reference: https://ec.europa.eu/cefdigital/DSS/webapp-demo/doc/dss-documentation.html _x000D_ _x000D_ CAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31912201/01.03.01_60/en_31912201v010301p.pdf'
'The CAdES Baseline Signatures main purpose is to provide the stakeholders involved in any electronic transaction with the certainty that the exchanged documents are truthful for all. In this sense the different signature levels (B Basic, T Time, LT Long-Term and LTA Long-Term Archive) provide a wide arrangement of security but it is not exhaustive._x000D_ _x000D_ It is worth mentioning that the specification is based on CMS, which enables data encryption and supports secure data exchange._x000D_ _x000D_ CMS reference:_x000D_ https://datatracker.ietf.org/doc/html/rfc5652_x000D_ _x000D_ CAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31912201/01.03.01_60/en_31912201v010301p.pdf'
"The CAdES Baseline signature is designed to guarantee the authenticity and authentication of the agents involved in data transactions. It achieves this by focusing on the signer's identity and their role, which is a core requirement of the eIDAS regulation._x000D_ _x000D_ eIDAS Regulation: _x000D_ https://digital-strategy.ec.europa.eu/en/policies/eidasregulation_x000D_ _x000D_ CAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31912201/01.03.01_60/en_31912201v010301p.pdf"
Assessment of the CAMSS Assessment of VC DM 2.0 EIF Scenario with the Common Assessment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of VC DM 2.0 EIF Scenario v1.0.0
'VC DM 2.0 is technology agnostic, as it defines an abstract and extensible data model for expressing verifiable credentials without mandating a specific implementation technology, protocol, or infrastructure. Therefore, different cryptographic methods, proof formats, and transport mechanisms can be used._x000D_ _x000D_ W3C Verifiable Credentials 2.0 reference:_x000D_ https://www.w3.org/TR/vc-data-model-2.0/'
'VC DM 2.0 is not related with enable the long-term preservation of data/information/knowledge (electronic records included). Therefore, this criterion is not related to this specification._x000D_ _x000D_ W3C Verifiable Credentials 2.0 reference:_x000D_ https://www.w3.org/TR/vc-data-model-2.0/'
'VC DM 2.0 can enable the exposure of interfaces if combined with other specifications. Therefore, additional specifications are required, such as OpenID for Verifiable Credential Issuance and OpenID for Verifiable Presentations._x000D_ _x000D_ OpenID for Verifiable Presentations Reference:_x000D_ https://openid.net/specs/openid-4-verifiable-presentations-1_0.html_x000D_ _x000D_ OpenID for Verifiable Credential Issuance Reference: v_x000D_ https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0.html_x000D_ _x000D_ W3C Verifiable Credentials 2.0 reference:_x000D_ https://www.w3.org/TR/vc-data-model-2.0/'
'VCDM 2.0 simplifies the delivery of European public services by providing a standard format for the digital representation of credentials that are secure, machine-verifiable, and privacy-preserving. Verifiable credentials can help simplify administrative procedures by allowing individuals to easily present trusted information about their identity, qualifications, residence, permits, or other personal circumstances. Public administrations and authorities can then automatically verify this information without relying on paper documents or repeated manual checks. This can make procedures faster and more efficient, while helping individuals gain access to public services, benefits, or administrative processes in a more secure and user-friendly way._x000D_ _x000D_ W3C Verifiable Credentials 2.0 reference:_x000D_ https://www.w3.org/TR/vc-data-model-2.0/'
'VC DM 2.0 is not related to enable the e-accessibility. Therefore, this criterion is not related to this specification._x000D_ _x000D_ W3C Verifiable Credentials 2.0 reference:_x000D_ https://www.w3.org/TR/vc-data-model-2.0/'
'VC DM 2.0 supports interoperability and standard compliance by providing evaluations and validation tools for verifiable credentials. Several frameworks are available to test implementations against W3C requirements. For example, the W3C VC Test Suite, hosted on GitHub, provides automated Node.js tests to ensure that applications generate Verifiable Credentials compliant with the VC Data Model 1.0. Additionally, the EBSI VC Validator is a web-based tool that allows manual validation of Verifiable Credentials or Verifiable Presentations in JWT format by directly pasting the credential content._x000D_ _x000D_ W3C Verifiable Credentials 2.0 Reference:_x000D_ https://www.w3.org/TR/vc-data-model/_x000D_ _x000D_ EBSI VC Validator Reference:_x000D_ https://hub.ebsi.eu/tools/vc-validator_x000D_ _x000D_ Verifiable Credentials conformance:_x000D_ https://www.w3.org/TR/vc-data-model/#conformance_x000D_ _x000D_ W3C Verifiable Credentials Working Group Test Suite: _x000D_ https://github.com/w3c/vc-test-suite'
'VC DM 2.0 allows partial implementations. This means that implementers can adopt only the components they need, such as specific proof types, credential features, or data structures, without having to support the full specification or ecosystem. Core mechanisms like selective disclosure or credential status checking are optional, not mandatory. Selective disclosure allows holders to reveal only parts of a credential, and credential status enables verification of revocation, but neither is required for a compliant implementation of VC DM._x000D_ _x000D_ W3C Verifiable Credentials 2.0 reference:_x000D_ https://www.w3.org/TR/vc-data-model-2.0_x000D_ _x000D_ W3C RDF Dataset Canonicalization Reference:_x000D_ https://www.w3.org/TR/rdf-canon/'
'VCDM 2.0 is not recommended by any European Member State._x000D_ _x000D_ However, VC DM has several implementations at the US Home Security, California Driving Licenses, GS1, work done by the Government of Singapore. It will be used for the UNECE work on the supply chains and Digital Product Passports. _x000D_ _x000D_ Moreover, VC DM 2.0 is also used in the Spanish Cartera Digital for Age Verification, implying there is a broad adoption worldwide. In this project, VCDM 2.0 is recommended. Since this project is from the Ministry for Digital Transformation and Civil Service, the specification is indirectly recommended by Spain. See the comment in the Spanish Consolidated Legislation reference._x000D_ _x000D_ UNECE Digital Product Passport Reference:_x000D_ https://untp.unece.org/docs/0.6.0/specification/DigitalProductPassport/#:~:text=All%20DPPs%20are%20issued%20as%20W3C%20Verifiable%20Credentials%20and%20MUST%20conform%20to%20the%20VCDM%202%2E0%2E_x000D_ _x000D_ Age verification system for access to online content Reference:_x000D_ https://digital.gob.es/content/dam/portal-mtdfp/especificaciones-t%C3%A9cnicas/2024-06-30_Protocolo_de_verificacion_de_edad-v1_0eng.pdf.pdf_x000D_ _x000D_ CAMSS List of Standards:_x000D_ https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards_x000D_ _x000D_ Spanish Consolidated Legislation: _x000D_ https://www.boe.es/buscar/act.php?id=BOE-A-2023-16284'
'VC DM 2.0 ensures the protection of personal data by giving individuals control over their credentials, allowing them to decide when and with whom to share information. _x000D_ _x000D_ Selective disclosure further enhances privacy by transmitting only the specific information required for a transaction, so public administrations cannot access sensitive or unnecessary personal data, supporting both data minimisation and privacy-preserving interactions._x000D_ _x000D_ W3C Verifiable Credentials 2.0 reference:_x000D_ https://www.w3.org/TR/vc-data-model-2.0/#privacy-considerations'
'VCDM 2.0 ensures data processing accuracy by making credentials tamper-evident: since they are digitally signed, any alteration after issuance is detectable, so the data remains exactly as the issuer intended._x000D_ _x000D_ W3C Verifiable Credentials 2.0 reference:_x000D_ https://www.w3.org/TR/vc-data-model-2.0'
'VC DM 2.0 facilitates aspects of business process modelling by providing a standardised way to represent, share, and verify credentials across different systems and organisations._x000D_ _x000D_ W3C Verifiable Credentials 2.0 Reference:_x000D_ https://www.w3.org/TR/vc-data-model-2.0/'
'VC DM 2.0 allows credential holders to control which information is shared through a mechanism called Selective Disclosure. This means holders can reveal only specific claims from a credential without exposing the entire content, enhancing privacy and data minimisation. _x000D_ _x000D_ In addition, verifiable credentials rely on cryptographic mechanisms and digital signatures, which ensure the integrity, authenticity, and tamper-evidence of the credential. Together, these mechanisms make credentials trustworthy while allowing holders to retain control over their personal data._x000D_ _x000D_ W3C Verifiable Credentials 2.0 reference:_x000D_ https://www.w3.org/TR/vc-data-model-2.0'
'VCDM 2.0 enables the secure exchange of data by defining a framework for credentials that can be cryptographically verified. Credentials can be digitally signed using proof mechanisms such as Verifiable Credentials Data Integrity (VCDI) or JSON Web Signature (JWS), allowing receiving parties to verify the authenticity and integrity of the data._x000D_ _x000D_ W3C Verifiable Credentials 2.0 reference:_x000D_ https://www.w3.org/TR/vc-data-model-2.0_x000D_ _x000D_ W3C Verifiable Credential Data Integrity reference:_x000D_ https://www.w3.org/TR/vc-data-integrity/_x000D_ _x000D_ JSON Web Signature Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7515.html'
'VCDM 2.0 guarantees the authenticity and authentication of roles involved in data transactions by enabling credentials and presentations to include cryptographic proofs. These proofs allow verifiers to confirm the identity of the issuer and verify that the data has not been altered._x000D_ _x000D_ W3C Verifiable Credentials 2.0 reference:_x000D_ https://www.w3.org/TR/vc-data-model-2.0'
'VC DM 2.0 is not yet included in European repositories or catalogues of standards. However, VC DM 1.1 is referenced in the Rolling Plan for ICT Standardisation in the area of electronic identification and trust services, including electronic signatures._x000D_ _x000D_ Since VC DM 2.0 is the direct successor of VC DM 1.1 and remains compatible with it, this reference can also be considered indirectly relevant to VC DM 2.0. In practice, some systems, such as the EUDI Wallet OOTS PoC, still use VC DM 1.1, and the transition to VC DM 2.0 is expected to occur because both versions are backward compatible when the newer features of VC DM 2.0 are not used._x000D_ _x000D_ Rolling Plan for ICT Standardisation: _x000D_ https://interoperable-europe.ec.europa.eu/sites/default/files/custom-page/attachment/2025-04/RollingPlan_ICT_2025.pdf_x000D_ _x000D_ W3C Verifiable Credentials 2.0 Reference:_x000D_ https://www.w3.org/TR/vc-data-model/'
'VCDM 2.0 has not been included within the catalogue of any Member State._x000D_ _x000D_ CAMSS List of Standards:_x000D_ https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards_x000D_ _x000D_ W3C Verifiable Credentials Data Model 2.0 Reference:_x000D_ https://www.w3.org/TR/vc-data-model-2.0/'
'VC DM 2.0 is developed by W3C, a standard development organisation based in the US. Therefore, this criterion is not applicable to this specification._x000D_ _x000D_ W3C Verifiable Credentials 2.0 Reference:_x000D_ https://www.w3.org/TR/vc-data-model/_x000D_ _x000D_ W3C Organisation Reference:_x000D_ https://www.w3.org/about/'
'VCDM 2.0 supports secure management of credentials by enabling holders to store them in protected repositories, such as digital wallets, which limits exposure and reduces the risk of unauthorised access or tampering._x000D_ _x000D_ W3C Verifiable Credentials 2.0 reference:_x000D_ https://www.w3.org/TR/vc-data-model-2.0'
'VC DM 2.0 allows customisation. Developers can define custom properties using JSON-LD. The specification provides extension points for essential features (credential status, data schemas, proofs, refreshing, terms of use, evidence) and reserved points for experimental properties (e.g., confidenceMethod, renderMethod). This flexibility allows verifiers to apply their own business rules and ensures credentials can be adapted for specific use cases while remaining interoperable._x000D_ _x000D_ W3C Verifiable Credentials 2.0 reference:_x000D_ https://www.w3.org/TR/vc-data-model-2.0'
'VC DM 2.0 is maintained by the W3C Verifiable Credentials Working Group. This group is responsible for developing, maintaining, and updating the specification and its related standards within the Verifiable Credentials family. VC DM 2.0 was officially published as a W3C Recommendation on 15 May 2025 and is intended to be used for new implementations, while VC DM 1.1 remains valid mainly for existing deployments._x000D_ _x000D_ VC DM 2.0 is also within the EU Digital Identity Wallet standards and technical specifications repository, where addresses the adoption of VC DM 2.0 and its relationship with VC DM 1.1. The repository notes that VC DM 2.0 is fully backwards compatible with VC DM 1.1 provided that the new features introduced in v2.0 are not used_x000D_ _x000D_ W3C Organisation Reference:_x000D_ https://www.w3.org/_x000D_ _x000D_ Verifiable Credentials WG Reference:_x000D_ https://www.w3.org/groups/wg/vc/_x000D_ _x000D_ _x000D_ EUDI Wallet Github reference:_x000D_ https://github.com/eu-digital-identity-wallet/eudi-doc-standards-and-technical-specifications/issues/115 _x000D_ _x000D_ W3C Verifiable Credentials Data Model 2.0 Reference:_x000D_ https://www.w3.org/TR/vc-data-model-2.0/'
'VC DM 2.0 allows relevant information to be reused by enabling credentials to be issued once and later presented and verified across different systems and services. The data model ensures interoperability and enables the same trusted data to be reused in different contexts without the need for re-issuance or manual re-entry._x000D_ _x000D_ W3C Verifiable Credentials 2.0 reference:_x000D_ https://www.w3.org/TR/vc-data-model-2.0/_x000D_ _x000D_ W3C Linked Data Reference:_x000D_ https://www.w3.org/TR/ldp/'
'VCDM defines a data model for verifiable credentials and their exchange. It does not address the facilitation of the publication of data on the web. Therefore, this criterion is not applicable to the specification._x000D_ _x000D_ W3C Verifiable Credentials Data Model 2.0 Reference:_x000D_ https://www.w3.org/TR/vc-data-model-2.0/'
'VC DM 2.0 is designed to be domain-neutral, enabling its use across diverse sectors. It can be used to represent and express digital credentials from different domains, such as identity, education, health, transport, finance, and professional qualifications. This flexibility ensures interoperability across ecosystems and supports broad adoption beyond any one specific use case or industry._x000D_ _x000D_ W3C Verifiable Credentials 2.0 reference:_x000D_ https://www.w3.org/TR/vc-data-model-2.0/'
'VC DM 2.0 has been selected and adopted in multiple large-scale and cross-border initiatives. It is used by organisations such as the US Department of Homeland Security, in California digital driving licences, by GS1, and in projects led by the Government of Singapore. It is also being applied in initiatives of the United Nations Economic Commission for Europe related to supply chains, traceability, and Digital Product Passports._x000D_ _x000D_ In the context of UNECE, VC DM provides a secure and machine-verifiable way to represent digital credentials about products, facilities, organisations, certifications, and traceability events. This allows trusted information to be exchanged across different actors and systems without relying on paper documents or isolated databases. For example, a Digital Product Passport can include verifiable information about a product’s origin, materials, environmental impact, repairability, recycling characteristics, and compliance with sustainability or regulatory requirements. This supports transparency, due diligence, and regulatory compliance across complex international supply chains._x000D_ _x000D_ UNECE UN Transparency Protocol Reference:_x000D_ https://untp.unece.org/docs/about/Goals_x000D_ _x000D_ W3C Verifiable Credentials 2.0 Reference:_x000D_ https://www.w3.org/TR/vc-data-model/'
'VC DM 2.0 is widely used in public and private sector initiatives and is one of the main specifications used within the European Digital Identity Wallet ecosystem. In this context, verifiable credentials are used to represent digital attestations, such as identity data, educational qualifications, health information, and driving licences, which can be securely stored and presented by the user._x000D_ _x000D_ Within the EUDI Wallet, VC DM enables issuers to provide digitally signed credentials and allows holders to selectively disclose only the information required for a specific transaction._x000D_ _x000D_ VC DM 1.1 is expected to be progressively replaced by VC DM 2.0, as the newer version provides improved security, privacy, and support for selective disclosure and zero-knowledge proof mechanisms._x000D_ _x000D_ VC DM is also used in initiatives such as the United States Department of Homeland Security, California mobile driving licences, GS1, the Government of Singapore, Digital Product Passports, and supply chain traceability projects._x000D_ _x000D_ In the Spanish Cartera Digital age verification initiative, VC DM is used to allow users to prove that they are of legal age without providing information that would allow their identification or tracking on the Internet. Content platforms are only allowed to obtain the minimum information necessary to verify that the user is above the required age threshold, following the principle of data minimisation._x000D_ _x000D_ The system is based on verifiable credentials securely stored in a digital wallet. Instead of sharing a full identity document or exact date of birth, the user presents a cryptographic proof that they are over 18. This proof can be verified by the platform without revealing additional personal information._x000D_ _x000D_ EUDI Wallet Reference:_x000D_ https://eudi.dev/2.2.0/architecture-and-reference-framework-main/#534-w3c-verifiable-credentials_x000D_ _x000D_ UNECE Digital Product Passport Reference:_x000D_ https://untp.unece.org/docs/0.6.0/specification/DigitalProductPassport/#:~:text=All%20DPPs%20are%20issued%20as%20W3C%20Verifiable%20Credentials%20and%20MUST%20conform%20to%20the%20VCDM%202%2E0%2E_x000D_ _x000D_ Age verification system for access to online content Reference:_x000D_ https://digital.gob.es/content/dam/portal-mtdfp/especificaciones-t%C3%A9cnicas/2024-06-30_Protocolo_de_verificacion_de_edad-v1_0eng.pdf.pdf_x000D_ _x000D_ _x000D_ W3C Verifiable Credentials Data Model 2.0 Reference:_x000D_ https://www.w3.org/TR/vc-data-model-2.0/'
'VC DM 2.0 is designed to use JSON-LD, which enhances data portability by combining the widely adopted JSON format with linked data semantics. This allows credential information to be consistently shared, interpreted, and understood across diverse and heterogeneous systems._x000D_ _x000D_ W3C Verifiable Credentials 2.0 reference:_x000D_ https://www.w3.org/TR/vc-data-model-2.0'
'VC DM 2.0 is used in the Spanish Cartera Digital age verification initiative, where verifiable credentials allow users to prove that they are above the required age threshold without revealing unnecessary personal information. Through selective disclosure and privacy-preserving cryptographic mechanisms, only the minimum information required for the transaction is shared, reducing the risk of profiling, tracking, or unnecessary disclosure of personal data. This reflects the privacy principles established in Commission Implementing Regulation (EU) 2024/2979, which promotes user control, confidentiality, and data minimisation in European Digital Identity Wallets, ensuring that users remain in control of their credentials and can decide which information to share. _x000D_ _x000D_ Moreover, VC DM 2.0 will also be used in the work of the United Nations Economic Commission for Europe on supply chains and Digital Product Passports. In this context, verifiable credentials can be used to represent trusted information about products, such as origin, sustainability, conformity, repairability, and traceability. Privacy is also relevant in these scenarios, as only the necessary information about a product, supplier, or supply chain step may be disclosed, while commercially sensitive or confidential information can remain protected. This helps ensure transparency and traceability without exposing unnecessary business data._x000D_ _x000D_ Commission Implementing Regulation (EU) 2024/2979 Reference:_x000D_ https://eur-lex.europa.eu/eli/reg_impl/2024/2979/oj/eng_x000D_ _x000D_ UNECE Digital Product Passport Reference:_x000D_ https://untp.unece.org/docs/0.6.0/specification/DigitalProductPassport/#:~:text=All%20DPPs%20are%20issued%20as%20W3C%20Verifiable%20Credentials%20and%20MUST%20conform%20to%20the%20VCDM%202%2E0%2E_x000D_ _x000D_ Age verification system for access to online content Reference:_x000D_ https://digital.gob.es/content/dam/portal-mtdfp/especificaciones-t%C3%A9cnicas/2024-06-30_Protocolo_de_verificacion_de_edad-v1_0eng.pdf.pdf_x000D_ _x000D_ W3C Verifiable Credentials Data Model 2.0 Reference:_x000D_ https://www.w3.org/TR/vc-data-model-2.0/'
'VC DM 2.0 is platform-agnostic and can be implemented across different systems and infrastructures without dependence on a specific platform._x000D_ _x000D_ VC DM can be represented using both plain JSON and JSON-LD. Through the use of JSON-LD, it allows different systems to interpret credential data in the same way, even when credentials are issued by different organisations or sectors. This is particularly useful in cross-border and cross-domain environments, such as the EUDI Wallet, ensuring a structured and interoperable data exchange, but introducing complexity._x000D_ _x000D_ EUDI Wallet JSON-LD Reference:_x000D_ https://eudi.dev/2.8.0/architecture-and-reference-framework-main/_x000D_ _x000D_ W3C Verifiable Credentials 2.0 reference:_x000D_ https://www.w3.org/TR/vc-data-model-2.0/'
'VC DM 2.0 is already associated to EIRA ABBs in the EIRA Library of Interoperability Specifications (ELIS). More specifically, VC DM can define the interoperability aspects of the "Data Model", "Open Data" ABBs of the EIRA Semantic View and "Data Exchange" and "Integrity Verification" ABBs of the EIRA Technical Application Views._x000D_ _x000D_ EIRA Library of Interoperability Specifications (ELIS):_x000D_ https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/611'
'VC DM 2.0 facilitates organisational interoperability by providing a common and standardised way to issue, share, and verify credentials across different systems and organisations. This helps organisations establish trust, reduce administrative work, and support interoperability across sectors and borders. For example, a university can issue a digital diploma that an employer or public authority can easily verify and accept as proof of qualification._x000D_ _x000D_ W3C Verifiable Credentials 2.0 Reference:_x000D_ https://www.w3.org/TR/vc-data-model-2.0/'
'VCDM 2.0 enables digital service delivery channels and supports digitalisation and administrative simplification. Government-issued identity documents, such as national ID cards, can be represented as verifiable credentials, allowing them to be securely managed, presented, and verified while the individual remains in control of their personal data._x000D_ _x000D_ It can also simplify manual procedures by replacing paper-based or document-based processes with trusted digital channels. For example, a driving licence can be presented as a verifiable credential instead of requiring the user to upload or send a scanned PDF. The receiving authority can then verify the authenticity and validity of the credential directly, reducing manual checks, fraud risks, and administrative burden._x000D_ _x000D_ W3C Verifiable Credentials 2.0 reference:_x000D_ https://www.w3.org/TR/vc-data-model-2.0/'
'VC DM 2.0 enables the visibility and comprehensibility of public administrations data and services. This is achieved with VCDM because it standardises how credentials are expressed in a machine-readable format (typically JSON-LD) and how they include cryptographic proofs, enabling independent verification of their authenticity._x000D_ _x000D_ W3C JSON-LD Reference:_x000D_ https://www.w3.org/TR/json-ld11/_x000D_ _x000D_ W3C Verifiable Credentials 2.0 reference:_x000D_ https://www.w3.org/TR/vc-data-model-2.0/'
'The effectiveness of VC DM 2.0 has been assessed through practical implementations, pilot projects, academic studies, and community feedback. In the study “Towards a Standardized Model for Privacy-Preserving Verifiable Credentials,” researchers concluded that Verifiable Credentials can be enhanced to support privacy-preserving features, such as predicates and selective disclosure mechanisms. The study also provided guidance and validation tools to adapt these mechanisms to the VC Data Model and demonstrated their applicability through a proof-of-concept implementation, highlighting the potential for secure and privacy-aware credential exchange across diverse use cases._x000D_ _x000D_ Towards a standardized model for privacy-preserving Verifiable Credentials Reference:_x000D_ https://dl.acm.org/doi/abs/10.1145/3465481.3469204_x000D_ _x000D_ Verifiable Credentials Use Cases: _x000D_ https://www.w3.org/TR/vc-use-cases_x000D_ _x000D_ W3C Verifiable Credentials 2.0 reference:_x000D_ https://www.w3.org/TR/vc-data-model-2.0/'
'VC DM is designed to be extensible. Implementers can define additional credential types, claims, and vocabularies through JSON-LD contexts, which allow external vocabularies to be referenced. This enables new properties and credential types to be introduced without modifying the core data model._x000D_ _x000D_ W3C Verifiable Credentials 2.0 reference:_x000D_ https://www.w3.org/TR/vc-data-model-2.0_x000D_ _x000D_ W3C JSON-LD 1.1 reference: _x000D_ https://www.w3.org/TR/json-ld11/#the-context'
'VCDM 2.0 with JSON-LD organises credential data into clear, semantically defined properties, which improves readability, interoperability, and machine processing. Therefore, it fosters the visibility and comprehensibility of public administrations data and services_x000D_ _x000D_ W3C JSON-LD Reference:_x000D_ https://www.w3.org/TR/json-ld11/_x000D_ _x000D_ W3C Verifiable Credentials 2.0 reference:_x000D_ https://www.w3.org/TR/vc-data-model-2.0/'
'VC DM 2.0 is discussed across both specialised forums and general developer platforms such as Stack Overflow, LinkedIn and many more. The questions about implementation, security discussions, and best-practice exchanges demonstrates active adoption and continuous community participation_x000D_ _x000D_ LinkedIn Reference:_x000D_ https://www.linkedin.com/posts/pierregronlier_w3c-verifiable-credentials-20-specifications-activity-7329031162352332800-ZlJy/?skipRedirect=true_x000D_ _x000D_ Stack Overflow Reference:_x000D_ https://stackoverflow.com/questions/58882523/decentralised-identity-management/58883753#58883753_x000D_ _x000D_ Stack Exchange Network Reference:_x000D_ https://security.stackexchange.com/questions/263367/can-my-name-be-revealed-from-a-stolen-verifiable-credential/266361#266361_x000D_ _x000D_ eu-digital-identity-wallet / eudi-doc-standards-and-technical-specifications Github Reference:_x000D_ https://github.com/eu-digital-identity-wallet/eudi-doc-standards-and-technical-specifications/issues?q=is%3Aissue%20VCDM_x000D_ _x000D_ W3C Verifiable Credentials 2.0 Reference:_x000D_ https://www.w3.org/TR/vc-data-model/'
'The efficiency of VC DM 2.0 has been assessed by researchers from different academic institutions. In the “Certifying Provenance of Scientific Datasets with Self-sovereign Identity and Verifiable Credentials” study, it is concluded that Verifiable Credentials can provide a secure and efficient way to certify the provenance and authenticity of scientific datasets. The study also highlights that Verifiable Credentials can improve trust, scalability, and the verification of data quality across different environments and use cases._x000D_ _x000D_ Certifying Provenance of Scientific Datasets with Self-sovereign Identity and Verifiable Credentials Reference:_x000D_ https://arxiv.org/abs/2004.02796_x000D_ _x000D_ Verifiable Credentials Use Cases: _x000D_ https://www.w3.org/TR/vc-use-cases_x000D_ _x000D_ W3C Verifiable Credentials 2.0 reference:_x000D_ https://www.w3.org/TR/vc-data-model-2.0/'
'VC DM 2.0 can be used in a multilingual context as it supports expressing data in different languages and scripts, encouraging the use of standardised language tags and direction metadata to ensure correct interpretation. It also enables multiple language representations for the same data element (e.g. via language-tagged values or arrays), enhancing flexibility and interoperability across systems and formats._x000D_ _x000D_ W3C Verifiable Credentials 2.0 reference:_x000D_ https://www.w3.org/TR/vc-data-model-2.0'
'VCDM 2.0 protects information against unauthorised changes through cryptographic signatures. When a credential is issued, it is digitally signed by the issuer, so any modification to the credential after issuance can be detected._x000D_ _x000D_ W3C Verifiable Credentials 2.0 reference:_x000D_ https://www.w3.org/TR/vc-data-model-2.0'
'VCDM was first published as a public working draft in 2017 and has since evolved through two major versions, v1.0 and the current v2.0, supported by additional governance and maintenance documentation._x000D_ _x000D_ VCDM is also referenced in Commission Implementing Regulation (EU) 2024/2979. Although the regulation explicitly refers to VCDM 1.1, it effectively points to the current evolution of the specification, VCDM 2.0, as the regulation has not yet been updated._x000D_ _x000D_ VCDM 2.0 enhances the security and trustworthiness of credentialing with greater precision than VCDM v1.1 and v1.0. One of its key advancements is the flexibility to support selective disclosure, including zero-knowledge proofs, allowing holders to reveal only specific parts of a credential without exposing the entire content, particularly certain asserted claims._x000D_ _x000D_ _x000D_ _x000D_ W3C Recommendation Track: _x000D_ https://www.w3.org/2021/Process-20211102/#rec-track_x000D_ _x000D_ General Requirements for Technical Reports: _x000D_ https://www.w3.org/2021/Process-20211102/#recs-and-notes_x000D_ _x000D_ Commission Implementing Regulation (EU) 2024/2979_x000D_ https://eur-lex.europa.eu/eli/reg_impl/2024/2979/oj/eng_x000D_ _x000D_ W3C Verifiable Credentials Data Model 2.0 Reference:_x000D_ https://www.w3.org/TR/vc-data-model-2.0/'
'VCDM 2.0 enables the secure processing of data by enabling credentials to include cryptographic proofs that allow systems to verify the authenticity and integrity of the information during processing. By working together with Verifiable Credentials Data Integrity (VCDI) and JSON Web Signature (JWS) specifications, it ensures that data can be validated before it is used._x000D_ _x000D_ W3C Verifiable Credentials 2.0 reference:_x000D_ https://www.w3.org/TR/vc-data-model-2.0_x000D_ _x000D_ W3C Verifiable Credential Data Integrity reference:_x000D_ https://www.w3.org/TR/vc-data-integrity_x000D_ _x000D_ JSON Web Signature Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7515.html'
'VC DM 2.0 is not currently included in most Member States’ catalogues of recommended specifications. However, they are already being adopted in national initiatives. For example, Spain is using VC DM in its digital age verification system for access to online adult content. In this initiative, verifiable credentials are used to prove that a user is of legal age without revealing their identity, exact date of birth, or other unnecessary personal information._x000D_ _x000D_ CAMSS List of Standards:_x000D_ https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards_x000D_ _x000D_ W3C Verifiable Credentials 2.0 Reference:_x000D_ https://www.w3.org/TR/vc-data-model/'
Assessment of the SSH EIF Scenario with the Common Assessment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of SSH EIF Scenario v1.0.0
'SSH employs a DNS-based naming convention (e.g., name@domainname) for algorithms and methods, allowing anyone to define and use extensions in a local namespace without central registration. This capability is further enhanced by RFC 8308, which defines a formal mechanism for extension negotiation within the protocol._x000D_ _x000D_ Extension Negotiation in the Secure Shell (SSH) Protocol (RFC8308):_x000D_ https://www.rfc-editor.org/rfc/rfc8308_x000D_ _x000D_ SSH Transport Layer:_x000D_ https://www.rfc-editor.org/rfc/rfc4253.html_x000D_ https://www.rfc-editor.org/rfc/rfc4254.html'
'SSH is a low-level technical specification for secure remote login and encrypted transport. It does not provide the commonly accepted modelling techniques required to document or align administrative business processes for the delivery of public services._x000D_ _x000D_ SSH Transport Layer:_x000D_ https://www.rfc-editor.org/rfc/rfc4253.html_x000D_ https://www.rfc-editor.org/rfc/rfc4254.html'
'SSH facilitates the technical movement of data by providing secure communication channels, multiplexed logical channels, and TCP/IP port forwarding, which allow data to be moved securely between disparate systems. However, SSH does not enable data portability on its own; as a low-level transport protocol, it is "binary-transparent" and does not define the structure, format, or semantics of the data being transmitted._x000D_ _x000D_ SSH Transport Layer:_x000D_ https://www.rfc-editor.org/rfc/rfc4253.html_x000D_ https://www.rfc-editor.org/rfc/rfc4254.html'
'SSH is technology agnostic because it is designed to work over any 8-bit clean, binary-transparent transport. While it typically runs over TCP/IP, the specification explicitly states it can be used on top of any other reliable data stream. Furthermore, it does not mandate a single cryptographic technology; instead, it uses a negotiation mechanism where parties agree on encryption, integrity, and key exchange algorithms from a broad list of supported standards._x000D_ _x000D_ SSH Transport Layer:_x000D_ https://www.rfc-editor.org/rfc/rfc4253.html_x000D_ https://www.rfc-editor.org/rfc/rfc4254.html'
'SSH is selected for use in European initiatives as a foundational cryptographic protocol. It is specifically included in the ENISA Technical implementation guidance on cybersecurity risk management measures to assist entities in meeting the requirements of Commission Implementing Regulation (EU) 2024/2690. This guidance is designed for essential and important entities across the EU, facilitating secure cross-border digital operations_x000D_ _x000D_ ENISA Technical implementation guidance on cybersecurity risk management measures:_x000D_ https://www.enisa.europa.eu/sites/default/files/2025-06/ENISA_Technical_implementation_guidance_on_cybersecurity_risk_management_measures_version_1.0.pdf_x000D_ _x000D_ Commission Implementing Regulation (EU) 2024/2690:_x000D_ https://eur-lex.europa.eu/eli/reg_impl/2024/2690/oj/eng_x000D_ _x000D_ SSH Transport Layer:_x000D_ https://www.rfc-editor.org/rfc/rfc4253.html_x000D_ https://www.rfc-editor.org/rfc/rfc4254.html'
"SSH has been included in the CAMSS List of Standards, notably the French Référentiel Général d’Interopérabilité (RGI), which is a Member State's catalogue with high performance on interoperability according to the National Interoperability Framework Observatory (NIFO)._x000D_ _x000D_ CAMSS List of Standards:_x000D_ https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-andspecifications-camss/camss-list-standards_x000D_ _x000D_ Référentiel général d'interopérabilité (RGI) Reference:_x000D_ https://www.numerique.gouv.fr/uploads/Referentiel_General_Interoperabilite_V2.pdf_x000D_ _x000D_ SSH Transport Layer:_x000D_ https://www.rfc-editor.org/rfc/rfc4253.html"
'While SSH is a globally recognized protocol for secure remote administration, its status within specific national catalogues is not documented in the provided RFCs or ENISA guidance._x000D_ _x000D_ ENISA:_x000D_ https://www.enisa.europa.eu/#contentList_x000D_ _x000D_ SSH Transport Layer:_x000D_ https://www.rfc-editor.org/rfc/rfc4253.html_x000D_ https://www.rfc-editor.org/rfc/rfc4254.html'
'While SSH is an international specification, the protocol is a foundational element in European initiatives focused on the security and privacy of digital public services, providing guidance to public administrations on implementing secure remote access and encrypted communication. By providing strong encryption, cryptographic host authentication, and integrity protection, SSH acts as a critical technical enabler for the secure exchange of information._x000D_ _x000D_ ENISA Technical implementation guidance on cybersecurity risk management measures:_x000D_ https://www.enisa.europa.eu/sites/default/files/2025-06/ENISA_Technical_implementation_guidance_on_cybersecurity_risk_management_measures_version_1.0.pdf_x000D_ _x000D_ SSH Transport Layer:_x000D_ https://www.rfc-editor.org/rfc/rfc4253.html_x000D_ https://www.rfc-editor.org/rfc/rfc4254.html'
'SSH provides extensive means for access control through its User Authentication Protocol and its ability to enforce local security policies. The specification mandates that the server must ensure the local policy permits the user the specific access requested (e.g., shell access vs. file transfer). Additionally, it provides administrative mechanisms to restrict which services are exposed to a user, including the ability to disable features like TCP/IP port forwarding or X11 forwarding based on the level of trust._x000D_ _x000D_ SSH Transport Layer:_x000D_ https://www.rfc-editor.org/rfc/rfc4253.html_x000D_ https://www.rfc-editor.org/rfc/rfc4254.html'
'SSH is supported by a robust Internet community, originally organised through the Secsh Working Group and maintained via active mailing list discussions. Furthermore, because it utilises well-known, well-established cryptographic algorithms, it benefits from the support and scrutiny of the broader global security and research community._x000D_ _x000D_ Secsh Working Group:_x000D_ https://datatracker.ietf.org/wg/secsh/about/_x000D_ _x000D_ SSH Transport Layer:_x000D_ https://www.rfc-editor.org/rfc/rfc4253.html_x000D_ https://www.rfc-editor.org/rfc/rfc4254.html'
'SSH specification was developed specifically for the Internet community and explicitly requests discussion and suggestions for improvements. This has resulted in a robust support community, originally through the secsh Working Group and ongoing mailing list discussions, involving a wide array of academic and corporate contributors. While its focus is on technical evolution rather than sharing administrative results on national platforms, its open status fosters a global community of developers and researchers._x000D_ _x000D_ SSH Transport Layer:_x000D_ https://www.rfc-editor.org/rfc/rfc4253.html_x000D_ https://www.rfc-editor.org/rfc/rfc4254.html'
'SSH provides precise data type representations, standardised message formats, and assigned message numbers, which allow developers and auditors to verify that an implementation aligns with the architectural standard. However, because practical implementation is often dependent on the target environment, many systems provide their own tools for conformance and validation testing. For example, GitHub provides specific documentation and procedures for "Testing your SSH connection" to ensure that a user's local configuration and keys are correctly implemented and authenticated within their specific network and security infrastructure. This indicates that while the protocol defines the baseline, the final validation of conformance often occurs through system-specific testing platforms tailored to the operational environment._x000D_ _x000D_ Connecting to GitHub with SSH:_x000D_ https://docs.github.com/en/authentication/connecting-to-github-with-ssh_x000D_ _x000D_ SSH Transport Layer:_x000D_ https://www.rfc-editor.org/rfc/rfc4253.html_x000D_ https://www.rfc-editor.org/rfc/rfc4254.html'
'SSH provides the technical foundation for protecting data through strong encryption and integrity protection, which are essential components for securing the exchange of personal data. It mandates cryptographic host authentication to ensure that data is only shared with verified entities. However, as a low-level transport protocol, SSH does not define procedures for the management, classification, or long-term storage of personal data, nor does it explicitly reference specific European privacy regulations like the GDPR._x000D_ _x000D_ GDPR:_x000D_ https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng_x000D_ _x000D_ SSH Transport Layer:_x000D_ https://www.rfc-editor.org/rfc/rfc4253.html_x000D_ https://www.rfc-editor.org/rfc/rfc4254.html'
'As an Internet standards track protocol, the SSH specification has been subject to rigorous and continuous assessment by the IETF (secsh Working Group) and the broader global security community. Its effectiveness is documented through the publication of updating RFCs (such as RFC 8308 and RFC 9142) and the systematic reporting of errata, which demonstrate an ongoing evaluation of its ability to reach its expected security goals. Furthermore, its status as the de facto standard for secure remote administration—evidenced by its universal assignment to TCP port 22—serves as a practical assessment of its effectiveness in real-world environments._x000D_ _x000D_ Secsh Working Group:_x000D_ https://datatracker.ietf.org/wg/secsh/about/_x000D_ _x000D_ Extension Negotiation in the Secure Shell (SSH) Protocol (RFC 8308):_x000D_ https://www.rfc-editor.org/rfc/rfc8308_x000D_ _x000D_ Key Exchange (KEX) Method Updates and Recommendations for Secure Shell (SSH) (RFC 9142):_x000D_ https://www.rfc-editor.org/rfc/rfc9142_x000D_ _x000D_ SSH Transport Layer:_x000D_ https://www.rfc-editor.org/rfc/rfc4253.html_x000D_ https://www.rfc-editor.org/rfc/rfc4254.html'
'SSH demonstrates extensive market acceptance, evidenced by the fact that TCP/IP port 22 is officially and universally assigned for SSH services. To ensure global interoperability, the specification mandates that all implementations must support a minimal set of required algorithms, which has led to its inclusion in virtually all modern network operating systems._x000D_ _x000D_ TCP/IP port 22 reference (iOS):_x000D_ https://support.apple.com/en-us/103229_x000D_ _x000D_ SSH Transport Layer:_x000D_ https://www.rfc-editor.org/rfc/rfc4253.html_x000D_ https://www.rfc-editor.org/rfc/rfc4254.html'
'SSH is platform agnostic, intended to be portable across different environments. It achieves this by defining standardised message formats, data types (like uint32 and string), and terminal modes that allow some degree of independence of specific hardware or operating systems._x000D_ _x000D_ SSH Transport Layer:_x000D_ https://www.rfc-editor.org/rfc/rfc4253.html_x000D_ https://www.rfc-editor.org/rfc/rfc4254.html'
'SSH is defined as a secure remote login and low-level transport protocol designed for encrypted communication over insecure networks, this criterion is therefore not applicable._x000D_ _x000D_ SSH Transport Layer:_x000D_ https://www.rfc-editor.org/rfc/rfc4253.html_x000D_ https://www.rfc-editor.org/rfc/rfc4254.html'
'SSH has already been added to the ELIS, specifically under EIRA Data Exchange Application Service and Component ABB._x000D_ _x000D_ EIRA Library of Interoperability Specifications (ELIS):_x000D_ https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-andspecifications-camss/solution/elis/release/611_x000D_ _x000D_ SSH Transport Layer:_x000D_ https://www.rfc-editor.org/rfc/rfc4253.html_x000D_ https://www.rfc-editor.org/rfc/rfc4254.html'
'SSH is a low-level, binary-transparent transport protocol designed for secure remote login and command execution: its primary function is to provide an encrypted tunnel for communication, but does not manage, store, or define the structure of administrative data or citizen information, nor does it provide an information model for such data. Therefore, it does not directly address the Once-Only Principle, which aims to ensure that users are asked for relevant information only once by public administrations._x000D_ _x000D_ SSH Transport Layer:_x000D_ https://www.rfc-editor.org/rfc/rfc4253.html_x000D_ https://www.rfc-editor.org/rfc/rfc4254.html'
'SSH does not natively facilitate the publication of data on the web, as its primary purpose is to provide secure remote login and other secure network services over insecure networks. The protocol is a low-level secure transport and connection multiplexing protocol that does not define the metadata schemas, content formats, or web-based discovery mechanisms (such as W3C standards) typically used for data publication._x000D_ _x000D_ SSH Transport Layer:_x000D_ https://www.rfc-editor.org/rfc/rfc4253.html_x000D_ https://www.rfc-editor.org/rfc/rfc4254.html'
'SSH is designed specifically to provide secure remote login and other secure network services over an insecure network. It enables the secure exchange of information by establishing a transport layer that provides strong encryption, server authentication, and integrity protection for all data transmitted between the client and server._x000D_ _x000D_ SSH Transport Layer:_x000D_ https://www.rfc-editor.org/rfc/rfc4253.html_x000D_ https://www.rfc-editor.org/rfc/rfc4254.html'
'SSH is a foundational technical enabler for the digital delivery channels used by the European Commission and other public administrations. Its Connection Protocol enables the multiplexing of several logical channels into a single encrypted tunnel, which explicitly supports the secure tunneling (port forwarding) of arbitrary TCP/IP protocols, including HTTP._x000D_ _x000D_ SSH Transport Layer:_x000D_ https://www.rfc-editor.org/rfc/rfc4253.html_x000D_ https://www.rfc-editor.org/rfc/rfc4254.html'
'The SSH Transport Layer Protocol protects information against unauthorized changes by mandating the use of a Message Authentication Code (MAC) for every packet sent. This MAC is computed from a shared secret, packet sequence numbers, and the message content, ensuring that any attempt to modify data in transit will be detected and cause the connection to be terminated._x000D_ _x000D_ SSH Transport Layer:_x000D_ https://www.rfc-editor.org/rfc/rfc4253.html_x000D_ https://www.rfc-editor.org/rfc/rfc4254.html'
'SSH simplifies the delivery of European public services by providing a standardised and secure framework for remote login and other secure network services over an insecure network. By establishing a reliable, encrypted transport layer that handles server authentication and data integrity, it allows public administrations to manage digital infrastructure and perform administrative tasks remotely and securely._x000D_ _x000D_ SSH Transport Layer:_x000D_ https://www.rfc-editor.org/rfc/rfc4253.html_x000D_ https://www.rfc-editor.org/rfc/rfc4254.html'
'SSH is considered not applicable to this criterion since the delivery of multilingual public services is a low-level technical security framework designed for encrypted communication. It generally does not pass text that is intended for direct display to an end-user. However, the specification includes robust technical provisions to support internationalization and multilingualism whenever text exchange occurs._x000D_ _x000D_ SSH Transport Layer:_x000D_ https://www.rfc-editor.org/rfc/rfc4253.html_x000D_ https://www.rfc-editor.org/rfc/rfc4254.html'
"SSH is included in a French open repository and catalogues of standards at the national level (French Référentiel Général d’Interopérabilité, RGI), which serves as a national repository and catalogue of standards to ensure interoperability within public administration systems. _x000D_ _x000D_ This inclusion validates SSH as a recognised technical specification for providing the secure remote login and encrypted transport services necessary for national digital infrastructures. Its presence in such a catalogue aligns with its status as a mature, Internet standards track protocol suitable for the security requirements of modern public services._x000D_ _x000D_ Référentiel général d'interopérabilité (RGI) Reference:_x000D_ https://www.numerique.gouv.fr/uploads/Referentiel_General_Interoperabilite_V2.pdf_x000D_ _x000D_ SSH Transport Layer:_x000D_ https://www.rfc-editor.org/rfc/rfc4253.html_x000D_ https://www.rfc-editor.org/rfc/rfc4254.html"
'SSH specification is a technical framework for secure communications and does not manage or define the contents or logic of the data being processed. While its integrity mechanisms ensure that data is transmitted accurately (i.e., it is not modified in transit), it does not provide features to ensure the logical accuracy or completeness of the data processing performed by the applications using the protocol._x000D_ _x000D_ SSH Transport Layer:_x000D_ https://www.rfc-editor.org/rfc/rfc4253.html_x000D_ https://www.rfc-editor.org/rfc/rfc4254.html'
'SSH guarantees the authenticity of both parties involved in a data transaction through a multi-layered approach. The SSH Transport Layer Protocol provides cryptographic server host authentication to verify that the client is talking to the correct host. Simultaneously, the User Authentication Protocol authenticates the client-side user to the server using a suite of secure mechanisms, such as public key authentication, passwords, or host-based authentication._x000D_ _x000D_ SSH Transport Layer:_x000D_ https://www.rfc-editor.org/rfc/rfc4253.html_x000D_ https://www.rfc-editor.org/rfc/rfc4254.html'
'SSH is a low-level, binary-transparent transport protocol designed specifically for secure communication and remote access over insecure networks. Its primary function is to provide an encrypted tunnel for data in transit; it does not define, manage, or provide mechanisms for the long-term storage, archival, or preservation of electronic records, information, or knowledge._x000D_ _x000D_ SSH Transport Layer:_x000D_ https://www.rfc-editor.org/rfc/rfc4253.html_x000D_ https://www.rfc-editor.org/rfc/rfc4254.html'
'SSH is inherently domain-agnostic, as it is designed as a general-purpose tool for secure remote login and other secure network services over insecure networks. It provides a versatile foundation for a wide range of purposes, such as interactive shell sessions, remote command execution, and the tunneling of arbitrary TCP/IP ports, making it usable across any business domain requiring secure communication._x000D_ _x000D_ SSH Transport Layer:_x000D_ https://www.rfc-editor.org/rfc/rfc4253.html_x000D_ https://www.rfc-editor.org/rfc/rfc4254.html'
'While SSH provides a secure "encrypted tunnel" for data transmission, its primary focus is on the transport rather than the processing of data, meaning that the protocol provides the means for the "remote execution of commands," but it assumes "end point security". In other words, while the data is protected while moving, the security of the actual processing on the remote host depends on local security policies and the server's environment rather than the protocol's internal mechanics._x000D_ _x000D_ SSH Transport Layer:_x000D_ https://www.rfc-editor.org/rfc/rfc4253.html_x000D_ https://www.rfc-editor.org/rfc/rfc4254.html'
'SSH explicitly includes assessments of its own efficiency, specifically regarding packet size and overhead. The specification provides a technical analysis of how the protocol's headers and Message Authentication Codes (MAC) affect data fields, concluding that the increase is "negligible" for standard Ethernet and TCP/IP packets. Additionally, the protocol is designed to minimize the number of round-trips required for key exchange and authentication, ensuring an efficient connection setup process even in high-latency environments._x000D_ _x000D_ SSH Transport Layer:_x000D_ https://www.rfc-editor.org/rfc/rfc4253.html_x000D_ https://www.rfc-editor.org/rfc/rfc4254.html'
'SSH allows for partial implementations due to its modular architecture, which is divided into three distinct layers: the Transport Layer Protocol, the User Authentication Protocol, and the Connection Protocol. For instance, a developer could implement the Transport Layer to provide a secure, encrypted pipe without necessarily implementing the multiplexing features of the Connection Protocol._x000D_ _x000D_ SSH Transport Layer:_x000D_ https://www.rfc-editor.org/rfc/rfc4253.html_x000D_ https://www.rfc-editor.org/rfc/rfc4254.html'
'SSH includes a dedicated User Authentication Protocol designed to authenticate clients to the server using multiple secure methods, including public key authentication, passwords, and host-based authentication. Furthermore, its architecture allows for the enforcement of local security policies, enabling administrations to restrict the specific operations a user is permitted to perform (such as limiting a user to file transfers while denying interactive shell access). These features, combined with negotiated confidentiality algorithms (e.g., AES), provide robust means for restricting access to data._x000D_ _x000D_ SSH Transport Layer:_x000D_ https://www.rfc-editor.org/rfc/rfc4253.html_x000D_ https://www.rfc-editor.org/rfc/rfc4254.html'
'SSH is included in the ENISA guidance as a reference example of a cryptographic protocol for secure communications. As this guidance supports European regulation and is accessible to all relevant entities, it serves as a European-level repository for technical security standards._x000D_ _x000D_ ENISA Technical implementation guidance on cybersecurity risk management measures:_x000D_ https://www.enisa.europa.eu/sites/default/files/2025-06/ENISA_Technical_implementation_guidance_on_cybersecurity_risk_management_measures_version_1.0.pdf_x000D_ _x000D_ SSH Transport Layer:_x000D_ https://www.rfc-editor.org/rfc/rfc4253.html_x000D_ https://www.rfc-editor.org/rfc/rfc4254.html'
'SSH is a highly mature specification with a stable, modular architecture divided into the Transport Layer, User Authentication, and Connection protocols. Originally published in its current form in 2006, it has undergone continuous evolution and hardening through multiple extensions and updates to ensure it remains effective against modern cryptographic threats._x000D_ _x000D_ SSH Transport Layer:_x000D_ https://www.rfc-editor.org/rfc/rfc4253.html_x000D_ https://www.rfc-editor.org/rfc/rfc4254.html'
'While SSH is an internationally recognised standard, it is published by the Internet Engineering Task Force (IETF) as a Proposed Standard. According to the sources, European Standards are those specifically developed and published by organisations such as CEN, CENELEC, or ETSI for the European region._x000D_ _x000D_ SSH Transport Layer:_x000D_ https://www.rfc-editor.org/rfc/rfc4253.html_x000D_ https://www.rfc-editor.org/rfc/rfc4254.html'
'SSH is designed to provide technical security properties such as confidentiality and integrity. It does not define the organisational elements, such as Memorandums of Understanding (MoUs) or Service Level Agreements (SLAs), necessary to clarify and formalise relationships between public administrations as required for organisational interoperability._x000D_ _x000D_ SSH Transport Layer:_x000D_ https://www.rfc-editor.org/rfc/rfc4253.html_x000D_ https://www.rfc-editor.org/rfc/rfc4254.html'
'SSH is to establish technical security properties like confidentiality, integrity, and host authentication for network services. Its scope is restricted to the technical transport and connection layers and does not involve the design of user-facing interfaces. Consequently, the specification does not address e-accessibility requirements, such as those found in WCAG or WAI-ARIA, designed to ensure digital public services are accessible to persons with disabilities or the elderly._x000D_ _x000D_ SSH Transport Layer:_x000D_ https://www.rfc-editor.org/rfc/rfc4253.html_x000D_ https://www.rfc-editor.org/rfc/rfc4254.html'
'SSH allows for extensive customisation through the negotiation of parameters. Implementations can be configured to support specific sets of encryption, integrity, and compression algorithms based on local security policies. Additionally, it provides a system for naming algorithms and methods that allows organizations to implement their own proprietary or experimental features without conflicting with the base protocol._x000D_ _x000D_ SSH Transport Layer:_x000D_ https://www.rfc-editor.org/rfc/rfc4253.html_x000D_ https://www.rfc-editor.org/rfc/rfc4254.html'
Assessment of the OIDC with the Common Assesssment Method for Standards and Specifications (CAMSS)
CAMSS Assessment of OIDC EIF Scenario v1.0.0
'OIDC conformance can be effectively assessed through publicly available test tools, such as the OIDC Conformance Test Suite and OIDC Debugger, allow developers to validate flows (authentication, ID token validation, claims handling) against the specification._x000D_ _x000D_ OpenID Foundation Conformance Suite:_x000D_ https://openid.net/certification/about-conformance-suite/_x000D_ _x000D_ OIDC debugger by Nate Barbettini: _x000D_ https://oidcdebugger.com/_x000D_ _x000D_ OpenID Connect specification:_x000D_ https://openid.net/specs/openid-connect-core-1_0.html'
'OIDC enables secure transmission of identity information during authentication and identity services. It relies on established security mechanisms such as HTTPS, OAuth 2.0, and JWTs to ensure that data in transit is encrypted and tamper-resistant. The specification also enforces the principle of minimal disclosure by allowing only consented identity attributes to be shared with relying parties, supporting selective disclosure and user control._x000D_ _x000D_ Furthermore, OIDC’s optional parameters allow implementers to define precisely which data elements are exchanged, reducing unnecessary exposure of personal data._x000D_ _x000D_ OpenID Connect specification reference:_x000D_ https://openid.net/specs/openid-connect-core-1_0.html_x000D_ _x000D_ JSON Web Token - JWT Reference:_x000D_ https://www.rfc-editor.org/info/rfc7519_x000D_ _x000D_ OAuth 2.0 Client Authentication and Authorization Grants:_x000D_ https://www.rfc-editor.org/info/rfc7521'
'OIDC is included in the "Référentiel général d'interopérabilité", which is the French Catalogue of Standards._x000D_ _x000D_ CAMSS List of Standards:_x000D_ https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards_x000D_ _x000D_ OpenID Connect specification:_x000D_ https://openid.net/specs/openid-connect-core-1_0.html'
'OIDC is a platform-agnostic specification built on widely adopted standards such as HTTP, JSON and OAuth 2.0. It enables interoperable authentication across operating systems, devices and environments, without reliance on specific hardware, software or vendor technologies._x000D_ _x000D_ OpenID Connect specification reference:_x000D_ https://openid.net/specs/openid-connect-core-1_0.html'
'OIDC enforces the restriction of access to user identity data through a combination of scopes, consent mechanisms, and authorisation tokens. Services can request only the specific information required for a given transaction, and users retain control over which attributes are shared. Access to data is further protected by standard security protocols, including HTTPS and OAuth 2.0 token validation, ensuring that only authorised parties can retrieve or use identity information. This approach supports the principles of data minimisation and purpose limitation, providing Public Administrations and other relying parties with a secure and privacy-preserving framework for identity management._x000D_ _x000D_ OpenID Connect specification Authentication reference:_x000D_ https://openid.net/specs/openid-connect-core-1_0.html#Authentication_x000D_ _x000D_ OpenID Connect specification Privacy reference:_x000D_ https://openid.net/specs/openid-connect-core-1_0.html#Privacy'
'OIDC specification is designed to maximise the reuse of relevant information across identity and authentication processes. Through standardised token formats (such as JWT), claims, scopes, endpoints, and metadata, information issued in one context can be reliably consumed in another without modification._x000D_ _x000D_ OpenID Connect specification reference:_x000D_ https://openid.net/specs/openid-connect-core-1_0.html_x000D_ _x000D_ JSON Web Token (JWT) Reference:_x000D_ https://datatracker.ietf.org/doc/html/rfc7519'
'OIDC enables the secure exchange of identity data by ensuring confidentiality, integrity, and authenticity throughout authentication and authorisation processes. It relies on HTTPS to protect data in transit, signed tokens such as JWTs to guarantee data integrity and authenticity, and OAuth 2.0 authorisation mechanisms to control access. Together, these measures allow relying parties to securely obtain the information they need while preventing unauthorised access or tampering, providing a robust and interoperable framework for identity and credential exchange across public and private services._x000D_ _x000D_ OpenID Connect specification Security reference:_x000D_ https://openid.net/specs/openid-connect-core-1_0.html#ClientAuthentication'
'Public review is a stage of the OIDC release lifecycle, featuring fixed review periods of 45 days for Implementer’s Drafts and Errata, and 60 days for Final Specifications. During these windows, feedback is systematically incorporated to enhance clarity and interoperability. This process ensures transparency and community validation, as strictly mandated by the OpenID Foundation’s governance policies._x000D_ _x000D_ OpenID Foundation OIDC Working Group:_x000D_ https://openid.net/wg/connect/_x000D_ _x000D_ OpenID Foundation Intellectual Property & Contribution Agreements:_x000D_ https://openid.net/intellectual-property/openid-foundation-contribution-agreements/_x000D_ _x000D_ OpenID Connect specification reference:_x000D_ https://openid.net/specs/openid-connect-core-1_0.html'
'OIDC is used by major platforms (Google, Microsoft, Apple) and public administrations, indicating it can handle large-scale, high-frequency authentication efficiently. OIDC is built on OAuth 2.0 and uses lightweight JSON and HTTPS, reducing overhead and ensuring efficient performance in web, mobile, and API-based services. _x000D_ _x000D_ Additionally, several academic papers and industry reports discuss the efficiency and practical use of OIDC in large-scale deployments._x000D_ _x000D_ A Novel Secure and Privacy-Preserving Model for OpenID Connect Based on Blockchain:_x000D_ https://www.researchgate.net/publication/372115811_A_Novel_secure_and_privacy-preserving_model_for_OpenID_Connect_based_on_Blockchain#:~:text=Abstract%20and%20Figures,informally%20by%20discussing%20various%20attacks._x000D_ _x000D_ Understanding the Identity-Transformation Approach in OIDC-Compatible Privacy-Preserving SSO Services:_x000D_ https://arxiv.org/abs/2506.01325#:~:text=OpenID%20Connect%20(OIDC)%20enables%20a,variations%20of%20SSO%20security%20requirements._x000D_ _x000D_ OIDC²: Open Identity Certification with OpenID Connect_x000D_ https://www.researchgate.net/publication/378896695_OIDC2_Open_Identity_Certification_With_OpenID_Connect'
'OIDC is a highly mature and globally recognised standard, recently formalised as ITU-T Recommendation X.1285. With multiple certified implementations and adoption by a high amount of users,since its the specification behind the "log in with" method. Its integration into the eIDAS 2.0 framework further confirms its suitability for building interoperable, high-assurance government ecosystems that are both future-proof and vendor-neutral._x000D_ _x000D_ ITU-T Recommendation X.1285 Reference:_x000D_ https://www.itu.int/rec/T-REC-X.1285_x000D_ _x000D_ OpenID Connect specification reference:_x000D_ https://openid.net/specs/openid-connect-core-1_0.html_x000D_ _x000D_ EUDI Wallets with OpenID for Verifiable Credentials (OpenID4VC):_x000D_ https://docs.igrant.io/concepts/openID4vc/_x000D_ _x000D_ OIDC Certified Implementations:_x000D_ https://openid.net/developers/certified-openid-connect-implementations/'
'OIDC specificacion provides a standarised way for digital authentication and identity verification, which organisations and service providers can use as a foundation to build their own access solutions. This specification can be applied across different sectors and use cases, without being tied to a specific business domain._x000D_ _x000D_ OIDC Adoption examples:_x000D_ https://openid.net/certification/_x000D_ _x000D_ OpenID Connect specification reference:_x000D_ https://openid.net/specs/openid-connect-core-1_0.html'
'OIDC effectiveness is demonstrated through its widespread adoption, interoperability certifications, security evaluations, and successful use in industry and public sector projects. Projects like eIDAS 2.0 pilots and EBSI evaluate OIDC’s effectiveness for public sector authentication under European frameworks. Moreover, the extensive use of OIDC by major identity providers (Google, Microsoft, Apple) and government services indicates its effectiveness in providing secure, interoperable authentication._x000D_ _x000D_ ESBI OIDC Authorisation endpoint:_x000D_ https://hub.ebsi.eu/apis/conformance/conformance/v3/get-authorize_x000D_ _x000D_ OIDC²: Open Identity Certiﬁcation withOpenID Connect_x000D_ https://www.researchgate.net/publication/378896695_OIDC2_Open_Identity_Certification_With_OpenID_Connect_x000D_ _x000D_ OpenID Connect specification:_x000D_ https://openid.net/specs/openid-connect-core-1_0.html'
'OIDC specification introduces a secure and standardised authentication layer that supports organisational interoperability agreements, especially in environments requiring both authentication and delegated authorisation._x000D_ _x000D_ OpenID Connect specification:_x000D_ https://openid.net/specs/openid-connect-core-1_0.html'
'OIDC ensures the authentication and authenticity of users involved in data transactions by providing a standardised framework for verifying identities through trusted identity providers. It supports mechanisms such as signed ID tokens, standardised claims, and token validation, which allow relying parties to confirm that the user is who they claim to be. In addition, OIDC can authenticate applications or clients requesting data, ensuring that only authorised services can access user information._x000D_ _x000D_ OpenID Connect specification Authenticity and Authentication reference:_x000D_ https://openid.net/specs/openid-connect-core-1_0.html#IDToken_x000D_ _x000D_ How OKTA and OIDC works together:_x000D_ https://www.okta.com/openid-connect/'
'OIDC specification ensures long-term stability for public services. The OpenID Foundation (OIDF) follows a strictly documented process where every update must pass through three distinct stages: Draft, Implementer’s Draft, and Final Specification. Each stage requires mandatory public review and formal approval gates, ensuring that changes are predictable, backward-compatible, and consensus-based. This transparency guarantees that the specification evolves safely without sudden, disruptive changes._x000D_ _x000D_ OpenID Foundation:_x000D_ https://openid.net/foundation/_x000D_ _x000D_ OpenID Foundation Approving Specifications:_x000D_ https://openid.net/wg/resources/approving-specifications/_x000D_ _x000D_ OpenID Connect specification reference:_x000D_ https://openid.net/specs/openid-connect-core-1_0.html'
'1 Member State is recommending OIDC in its ICT National Catalogues. This Member States is France._x000D_ _x000D_ CAMSS List of Standards:_x000D_ https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards_x000D_ _x000D_ OpenID Connect specification:_x000D_ https://openid.net/specs/openid-connect-core-1_0.html'
'OIDC may be used freely and without royalties, with no restrictions on implementation beyond compliance with the specification and any applicable trademark guidelines. The OpenID Foundation (OIDF) grants to any Contributor, developer, implementer, or other interested party a non-exclusive, royalty free, worldwide copyright license to reproduce, prepare derivative works from, distribute, perform and display._x000D_ _x000D_ OpenID Foundation OIDC Working Group:_x000D_ https://openid.net/wg/connect/_x000D_ _x000D_ OpenID Foundation Intellectual Property & Contribution Agreements:_x000D_ https://openid.net/intellectual-property/openid-foundation-contribution-agreements/_x000D_ _x000D_ OpenID Connect specification reference:_x000D_ https://openid.net/specs/openid-connect-core-1_0.html'
'OIDC consists of a core specification and a set of optional features, allowing implementers to adopt the core components first and selectively add additional modules to meet their specific system requirements. For example, optional features include support for dynamic client registration, session management, single logout, token introspection, and advanced security profiles, which can be adopted as needed depending on the desired level of functionality and assurance._x000D_ _x000D_ OpenID Connect specification reference:_x000D_ https://openid.net/specs/openid-connect-core-1_0.html_x000D_ _x000D_ OpenID Connect specifications reference:_x000D_ https://openid.net/developers/specs/'
'OIDC enables identity portability but is not a mechanism for data portability, as it does not handle the export or transfer of a user’s full personal data between services. _x000D_ _x000D_ OpenID Connect specification reference:_x000D_ https://openid.net/specs/openid-connect-core-1_0.html'
'OIDC provides an access control mechanism for identity data during authentication by leveraging OAuth 2.0 tokens, scopes, and user consent. These mechanisms allow relying parties to request only the information necessary for a given transaction, while giving users control over what data is shared. However, OIDC’s access control is limited to authentication and authorisation flows and does not govern how applications handle, store, or further process the data once it has been received._x000D_ _x000D_ OpenID Connect specification reference:_x000D_ https://openid.net/specs/openid-connect-core-1_0.html'
'OIDC is already associated to an EIRA ABB in the EIRA Library of Interoperability Specifications (ELIS). More specifically, DNS can define the interoperability aspects of the "Cloud Private Network" ABB from Technical view - Infrastructure and "Authentication" and "Identificaction" ABB from Technical view - application._x000D_ _x000D_ EIRA Library of Interoperability Specifications (ELIS):_x000D_ https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/v610_x000D_ _x000D_ OpenID Connect specification:_x000D_ https://openid.net/specs/openid-connect-core-1_0.html'
'OIDC simplifies the business processes by providing secure user authentication and identity verification. It enables users to sign in to services such as cross-border public administration platforms, eGovernment portals, and EU digital identity initiatives using trusted identity providers._x000D_ _x000D_ OpenID Connect specification:_x000D_ https://openid.net/specs/openid-connect-core-1_0.html'
'OIDC enables digital service delivery channels by providing a standardised and interoperable framework for secure authentication and identity verification. It allows users to access web portals, mobile applications, and digital wallets with a single, trusted identity, reducing friction and the need for multiple credentials. By supporting consent-based attribute sharing, extensible claims, and profiles such as OIDC4VC and OIDC4VP, OIDC facilitates seamless access to both national and cross-border public services, including eGovernment, healthcare, taxation, and social services._x000D_ _x000D_ OpenID Connect specification:_x000D_ https://openid.net/specs/openid-connect-core-1_0.html_x000D_ _x000D_ OIDC4VC Reference:_x000D_ https://openid.net/sg/openid4vc/_x000D_ _x000D_ OIDC4VP Reference:_x000D_ https://openid.net/specs/openid-4-verifiable-presentations-1_0.html'
'OIDC simplifies the delivery of European public services by providing a secure user authentication and identity verification. It enables users to sign in to services such as cross‑border public administration platforms, eGovernment portals, and EU digital identity initiatives using trusted identity providers. For example, national digital identity schemes like itsme in Belgium (which supports government and citizen services), BankID in Norway, Sweden, and Finland (used for eGovernment access and public services), and FranceConnect in France utilise OIDC‑based authentication models in alignment with eIDAS trust frameworks._x000D_ _x000D_ OpenID Connect specification:_x000D_ https://openid.net/specs/openid-connect-core-1_0.html_x000D_ _x000D_ itsme - Belgium service Reference:_x000D_ https://www.itsme-id.com/_x000D_ _x000D_ BankID from Norway, Sweden, and Finland service:_x000D_ https://www.bankid.com/_x000D_ _x000D_ FranceConnect - French Service:_x000D_ https://www.franceconnect.gouv.fr/_x000D_ _x000D_ The eKYC & IDA Working Group Welcomes the Proposal of the European Commission to Extend the Scope of eIDAS Trust Services - OpenID Fundation Reference:_x000D_ https://openid.net/the-ekyc-ida-working-group-welcomes-the-proposal-of-the-european-commission-to-extend-the-scope-of-eidas-trust-services/'
'OIDC specification focuses on secure authentication and identity management rather than enabling the e-accessibility. Therefore, this criterion is not applicable to this specification._x000D_ _x000D_ OpenID Connect specification reference:_x000D_ https://openid.net/specs/openid-connect-core-1_0.html'
'OIDC functions as an identity layer built on top of the OAuth 2.0 protocol, providing a standardised framework for verifying end-user identity and obtaining profile information. The specification exposes web-based interfaces, specifically the Authorization, Token, and UserInfo endpoints, which allow systems to handle identity and profile data consistently and securely._x000D_ _x000D_ In practice, OIDC is the protocol behind “Log in with …” buttons on websites and applications. When a user chooses to log in with an external provider, OIDC manages the authentication process, allowing the service to redirect the user to a trusted identity provider, authenticate them, and then receive a secure confirmation of the user’s identity. This ensures interoperability between systems, enabling internal identity services to be reused across multiple applications while maintaining security and trust._x000D_ _x000D_ OpenID Connect specification reference:_x000D_ https://openid.net/specs/openid-connect-core-1_0.html_x000D_ _x000D_ OAuth 2.0 specification reference:_x000D_ https://datatracker.ietf.org/doc/html/rfc6749'
'OIDC enables real time authentication, ensuring the user’s identity information is accurate at the time of login. OIDC retrieves identity data directly from a trusted identity provider, reducing the risk of using outdated or incorrect user information during authentication._x000D_ _x000D_ OpenID Connect specification reference:_x000D_ https://openid.net/specs/openid-connect-core-1_0.html'
'OIDC does not enable the visibility of administrative procedures, rules data, and services as it instead focuses on providing a standard way to authenticate users and send identity information securely between parties. Therefore, this criterion is not applicable to this specification._x000D_ _x000D_ OpenID Connect specification reference:_x000D_ https://openid.net/specs/openid-connect-core-1_0.html'
'OIDC does not enable the long-term preservation of data/information/knowledge. Therefore, this criterion is considered not applicable to this specification._x000D_ _x000D_ OpenID Connect specification:_x000D_ https://openid.net/specs/openid-connect-core-1_0.html'
'The purpose of OIDC is not related to the publication of data on the web as it main purpose is the user authentication and identity management._x000D_ _x000D_ OpenID Connect specification reference:_x000D_ https://openid.net/specs/openid-connect-core-1_0.html#Authentication'
'OIDC uses JSON Web Tokens (JWTs) with digital signatures, enabling receiving applications to verify both the integrity of the data and its origin from a trusted identity provider. In addition, OIDC requires the use of HTTPS to protect data from interception or modification during transit. Together, these mechanisms ensure that identity and credential data are exchanged securely, maintaining confidentiality, integrity, and authenticity throughout authentication and authorisation processes._x000D_ _x000D_ OpenID Connect specification ID Token Validation reference:_x000D_ https://openid.net/specs/openid-connect-core-1_0.html#IDTokenValidation'
'OIDC defines a core set of mandatory and optional components while allowing additional functionality to be introduced through profiles, extensions, and optional parameters, without compromising the interoperability of the core specification. Its use of JSON-based structures, extensible token claims, scopes, endpoints, and metadata enables implementers and standards bodies to introduce new capabilities in a controlled and backwards-compatible manner._x000D_ _x000D_ This extensibility is demonstrated by several standardised profiles and extensions built on top of OIDC Core, including Identity Assurance, eKYC, and OpenID for Verifiable Credentials (OIDC4VC and OIDC4VP). These profiles leverage existing OIDC and OAuth 2.0 mechanisms while defining additional requirements, data models, and processing rules tailored to specific use cases. By doing so, they enable advanced identity scenarios, such as verifiable credentials and digital wallets, while preserving standards compliance, interoperability, and security._x000D_ _x000D_ OpenID Connect specification reference:_x000D_ https://openid.net/specs/openid-connect-core-1_0.html_x000D_ _x000D_ eKYC & IDA Working Group reference:_x000D_ https://openid.net/wg/ekyc-ida/_x000D_ _x000D_ IETF SD-JWT Reference:_x000D_ https://datatracker.ietf.org/doc/draft-ietf-oauth-selective-disclosure-jwt/22/'
'OIDC ensures that identity data is transmitted securely during authentication by leveraging HTTPS for encrypted communication and signed tokens, such as JWTs, to guarantee integrity and authenticity. This allows applications to verify that the received data originates from a trusted identity provider, reducing the risk of impersonation or tampering. However, it does not regulate how applications handle or store user data after it has been received. Implementers are therefore responsible for applying additional privacy and security measures, such as secure storage, access restrictions, and compliance with data protection regulations, to safeguard user information throughout its lifecycle._x000D_ _x000D_ OpenID Connect specification Security reference:_x000D_ https://openid.net/specs/openid-connect-core-1_0.html#ClientAuthentication'
'OIDC is included in European and national digital identity initiatives that cover privacy aspects, such as eSSIF-Lab (European Self-Sovereign Identity Framework Lab) or eIDAS projects, due to its support for secure, consent-based identity data sharing._x000D_ _x000D_ OpenID Foundation welcomes eIDAS trust services expansion:_x000D_ https://openid.net/the-ekyc-ida-working-group-welcomes-the-proposal-of-the-european-commission-to-extend-the-scope-of-eidas-trust-services_x000D_ _x000D_ European Self-Sovereign Identity Framework Lab:_x000D_ https://essif-lab.github.io/framework/docs/essifLab-vision_x000D_ _x000D_ European Self-Sovereign Identity Framework Lab Standards used:_x000D_ https://tno-ssi-lab.github.io/standardisation-overview/_x000D_ _x000D_ OpenID Connect specification Privacy reference:_x000D_ https://openid.net/specs/openid-connect-core-1_0.html#Privacy'
'OIDC is included in an italian repository that provides the specific technical consolidation, in accordance with National Guidelines, to improve the prospects of integration with the SPID and CIE id OIDC Federations for public and private Service Providers (RP), Identity Providers (OP), and Aggregators (SA)._x000D_ _x000D_ SPID/CIE OpenID Connect - AgID + Team per la Trasformazione Digitale Reference:_x000D_ https://docs.italia.it/italia/spid/spid-cie-oidc-docs/it/versione-corrente/index.html_x000D_ _x000D_ OpenID Connect specification:_x000D_ https://openid.net/specs/openid-connect-core-1_0.html'
'OIDC does not include administrative procedures, rules, or service management as it instead focuses on providing a standard way to authenticate users and convey identity information securely between parties. Therefore, this criterion is not applicable to this specification._x000D_ _x000D_ OpenID Connect specification reference:_x000D_ https://openid.net/specs/openid-connect-core-1_0.html'
'OIDC specification can be found in the OpenID Foundation Github where its development and maintenance can actively encourage and sustain open communities, discussions, and collaborative improvement of the specification and its implementations._x000D_ _x000D_ OpenID Github Reference:_x000D_ https://github.com/openid'
'OIDC allows the customisation of claims, scopes and user flows to align with specific service requirements while maintaining compliance with the core protocol specifications. Through the controlled definition of customised scope values and claims structures, issuers can precisely indicate the type and semantic context of the credential being requested or issued. OIDC can support verifiable credential use cases and wallet-based authentication flows without compromising interoperability._x000D_ _x000D_ This customisation enables selective disclosure mechanisms, allowing users to share only the specific attributes necessary for a given transaction. This approach reinforces privacy-by-design principles and ensures strict adherence to the principle of data minimisation, as required under European data protection frameworks._x000D_ _x000D_ OpenID Connect specification reference:_x000D_ https://openid.net/specs/openid-connect-core-1_0.html#Claims'
'OIDC is used in European cross-border initiatives and projects, including eIDAS 2.0 pilots and the European Digital Identity Wallet (EUDI Wallet) architecture, where it is utilised for secure authentication and authorisation. Its adoption in these initiatives is due to its maturity, interoperability, and alignment with web standards, making it suitable for cross-border identity federation and authentication scenarios._x000D_ _x000D_ EU Digital Identity Wallet Pilot implementation:_x000D_ https://digital-strategy.ec.europa.eu/en/policies/eudi-wallet-implementation_x000D_ _x000D_ eIDAS 2.0 Roadmap:_x000D_ https://utimaco.com/news/blog-posts/eidas-20-roadmap-toolbox-and-european-digital-identity-wallet-architecture'
'OIDC is maintained by the OpenID Foundation (OIDF), an international non-profit standards organisation. The specification is developed and updated by the AB/Connect Working Group. The AB/Connect working group is a combined working group of the Artifact Binding (AB) Working Group and the Connect Working Group aimed at producing the OAuth 2.0 based “OpenID Connect” specifications. It also includes a project named OpenID for Verifiable Credentials which consists of three specifications. _x000D_ _x000D_ OpenID AB/Connect Working Group:_x000D_ https://openid.net/wg/connect/_x000D_ _x000D_ OpenID Foundation Working Groups:_x000D_ https://openid.net/wg/_x000D_ _x000D_ OpenID Foundation Mailing Lists:_x000D_ https://openid.net/community/mailing-lists/'
'The development of the OIDC specification ensures broad technical input while maintaining a sustainable governance structure. At the technical level, allows the participation of any stakeholder, including individual developers, private companies, and public administrations, to join working groups and contribute to the drafting of specifications without requiring a paid membership. Contributors only need to sign a Contribution Agreement. All working groups operate openly with decisions on specifications being consensus-led._x000D_ _x000D_ Formal influence and organizational governance, however, are managed through a tiered membership structure. While technical contribution is free, becoming a "Member" involves annual dues, which are scaled to be accessible for different entities (e.g., $250/year for governments and non-profits). This membership grants formal voting rights on the final approval of specifications and the election of the Board of Directors. This balanced approach ensures that while the technical evolution of OIDC is driven by a global community of experts, its long-term sustainability and strategic direction are overseen by a formal, representative body of invested stakeholders._x000D_ _x000D_ OpenID Foundation Working Groups:_x000D_ https://openid.net/wg/_x000D_ _x000D_ OpenID Foundation OIDC Working Group:_x000D_ https://openid.net/wg/connect/_x000D_ _x000D_ OpenID Foundation bylaws reference:_x000D_ https://openid.net/oidf-updates-bylaws/_x000D_ _x000D_ OpenID Foundation Membership reference:_x000D_ https://openid.net/foundation/benefits-members/_x000D_ _x000D_ OpenID Foundation Intellectual Property & Contribution Agreements:_x000D_ https://openid.net/intellectual-property/openid-foundation-contribution-agreements/_x000D_ _x000D_ OpenID Connect specification reference:_x000D_ https://openid.net/specs/openid-connect-core-1_0.html'
'OIDC is a technology-agnostic specification, built on open standards such as HTTP, JSON, and OAuth 2.0. It enables interoperable authentication across a wide range of operating systems, devices, and programming environments. The specification defines a protocol for authentication and identity without imposing requirements on specific technologies, frameworks, or programming languages, allowing flexibility in implementation while ensuring consistency and compatibility._x000D_ _x000D_ OpenID Connect specification reference:_x000D_ https://openid.net/specs/openid-connect-core-1_0.html'
'OIDC is included in the French national catalogue of recommended specifications. The National Interoperability Framework of France is aligned with at least 3 out of 4 scoreboards of the EIF Monitoring according to the National Interoperability Framework Observatory (NIFO) factsheets._x000D_ _x000D_ NIFO Factsheets France:_x000D_ https://joinup.ec.europa.eu/sites/default/files/inline-files/NIFO_2024%20DPAF_France_vFinal_rev.pdf_x000D_ _x000D_ CAMSS list of standards:_x000D_ https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
'OIDC is not a European standard. It was developed by OpenID Foundation, a global non-profit organisation, and is based in the United States and supported by a worldwide community, including major industry stakeholders (e.g., Google, Microsoft, and others). However, OIDC has been adopted in Europe for authentication and identity federation, and is referenced in European cross-border initiatives (e.g., eIDAS 2.0, EUDI Wallet...) due to its interoperability and maturity._x000D_ _x000D_ EU Digital Identity Wallet Pilot implementation:_x000D_ https://digital-strategy.ec.europa.eu/en/policies/eudi-wallet-implementation_x000D_ _x000D_ eIDAS 2.0 Roadmap:_x000D_ https://utimaco.com/news/blog-posts/eidas-20-roadmap-toolbox-and-european-digital-identity-wallet-architecture_x000D_ _x000D_ OpenID Connect specification:_x000D_ https://openid.net/specs/openid-connect-core-1_0.html'
'OIDC can be effectively used in a multilingual context. Authorization requests and error messages can include language preferences, enabling relying parties and identity providers to present interfaces and content in the user’s preferred language_x000D_ _x000D_ OpenID Connect specification reference:_x000D_ https://openid.net/specs/openid-connect-core-1_0.html'
CAMSS Assessment of SAMM EIF Scenario 2.0.0
Assessment of the SAMM EIF Scenario with the Common Assessment Method for Standards and Specifications (CAMSS)
"The purpose of SAMM is not related to enable the exposure of interfaces to access the public administration's services. Therefore, this criterion is not applicable to this specification._x000D_ _x000D_ SAMM reference:_x000D_ https://owaspsamm.org/about/"
'The purpose of SAMM is not related to enable the secure processing of data. Therefore, this criterion is not_x000D_ applicable to this specification._x000D_ _x000D_ SAMM reference:_x000D_ https://owaspsamm.org/about/'
'SAMM is not included in any national catalogue of recommended specifications according to the CAMSS List of Standards._x000D_ _x000D_ CAMSS List of Standards:_x000D_ https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards_x000D_ _x000D_ SAMM reference:_x000D_ https://owaspsamm.org/about/'
'The purpose of SAMM is not related to enable the visibility of administrative information, data or services. Therefore, this criterion is not applicable to this specification._x000D_ _x000D_ SAMM reference:_x000D_ https://owaspsamm.org/about/'
'The efficiency of the SAMM specification has been assessed by the University of Porto. In the "Measuring the Efficiency of Software Security Maturity Models" study, the SAMM specification is proposed as a framework to evaluate the performance of security activities, facilitating the identification of more efficient ways to implement security practices and allocate resources effectively._x000D_ _x000D_ "Measuring the Efficiency of Software Security Maturity Models" study:_x000D_ https://repositorio-aberto.up.pt/handle/10216/128456_x000D_ _x000D_ SAMM reference:_x000D_ https://owaspsamm.org/about/'
'SAMM is already associated to EIRA ABBs in the EIRA Library of Interoperability Specifications (ELIS). More specifically, SAMM can define the interoperability aspects of the "Privacy Framework", "Security Framework" and "Conformance Test Scenario" ABBs of the EIRA Technical Application View and Organisational View._x000D_ _x000D_ EIRA Library of Interoperability Specifications (ELIS) v6.1.1:_x000D_ https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/611_x000D_ _x000D_ SAMM reference:_x000D_ https://owaspsamm.org/about/'
'The purpose of SAMM is not related to enable guarantee the authenticity and authentication of the roles agents_x000D_ involved in the data transactions. Therefore, this criterion is not applicable to this specification._x000D_ _x000D_ SAMM reference:_x000D_ https://owaspsamm.org/about/'
'SAMM is a flexible framework designed to improve software security across any type of organisation. Because it focuses on the security of the development process rather than the specific purpose of the software, it can be applied equally to health, business, legal, or government sectors._x000D_ _x000D_ SAMM reference:_x000D_ https://owaspsamm.org/about/'
'The purpose of SAMM is not related to facilitate the publication of data on the web. Therefore, this criterion is not applicable to this specification._x000D_ _x000D_ SAMM reference:_x000D_ https://owaspsamm.org/about/'
'SAMM is a framework designed to help organisations build better security into their software. It includes specific requirements for access control within its "Data Protection" and "Security Architecture" practices. While it does not provide the technical tools to perform access control, it explicitly defines the rules and maturity levels that organisations should follow to ensure only authorised people can access or change data._x000D_ _x000D_ OWASP SAMM - Data Protection Practice:_x000D_ https://owaspsamm.org/model/operations/operational-management/stream-a/_x000D_ _x000D_ OWASP SAMM - Security Architecture Practice:_x000D_ https://codific.com/implementing-the-secure-architecture-practice-in-owasp-samm/#:~:text=It%20is%20the%20practice%20of%20application%20security%20architecture,an%20architectural%20solution%20as%20well%20as%20technological%20implementation._x000D_ _x000D_ SAMM reference:_x000D_ https://owaspsamm.org/about/'
'The purpose of this specification is not related to enable the e-accessibility. Therefore, this criterion is not applicable to the specification. _x000D_ _x000D_ SAMM reference:_x000D_ https://owaspsamm.org/about/'
'The SAMM specification is maintained by the OWASP Foundation, which is an international organisation based in the United States. While it is not developed by a European-based SDO, it is widely used and recommended in several relevant European initiatives and guidelines. Because it is an international standard applied within the European context, this criterion is considered not applicable._x000D_ _x000D_ SAMM reference:_x000D_ https://owaspsamm.org/about/'
'SAMM helps different organisations work together by providing a common language and a standardised structure for software security. It includes specific practices like "Policy and Compliance" that help set clear expectations and security goals between parties. This makes it much easier for organisations to reach agreements on security standards._x000D_ _x000D_ OWASP SAMM - Policy and Compliance Practice:_x000D_ https://owaspsamm.org/model/governance/policy-and-compliance/_x000D_ _x000D_ SAMM reference:_x000D_ https://owaspsamm.org/about/'
'SAMM’s purpose is focused on helping and improving security capabilities within organisations and software development. By applying SAMM, public administrations can work towards ensuring secure and trustworthy data exchange with all stakeholders. The model includes a specific "Data Protection" practice that guides organisations on how to safeguard sensitive information and a "Policy and Compliance" practice to help them align with external regulatory requirements. While it provides the framework to ensure data remains authentic and intact, it focuses on the management processes rather than the specific technical implementation for data transmission._x000D_ _x000D_ OWASP SAMM - Data Protection Practice:_x000D_ https://owaspsamm.org/model/operations/operational-management/stream-a/_x000D_ _x000D_ OWASP SAMM - Policy and Compliance Practice:_x000D_ https://owaspsamm.org/model/governance/policy-and-compliance/_x000D_ _x000D_ SAMM reference:_x000D_ https://owaspsamm.org/about/'
'SAMM is recognised in European initiatives as a key framework for building secure and private software. The European Union Agency for Cybersecurity (ENISA) highlights the importance of using maturity models, such as SAMM in its reports on cybersecurity best practices. This helps organisations across the EU follow a structured approach to protecting data and meeting high security standards._x000D_ _x000D_ ENISA - Good Practices for Supply Chain Cybersecurity:_x000D_ https://www.enisa.europa.eu/publications/good-practices-for-supply-chain-cybersecurity_x000D_ _x000D_ SAMM reference:_x000D_ https://owaspsamm.org/about/'
'SAMM is licensed under CC, which essentially means that the commercial use of the work and possible derivative works is allowed, the distribution of which must be done with a license equal to the one that regulates the original work._x000D_ _x000D_ Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0):_x000D_ https://creativecommons.org/licenses/by-sa/4.0/_x000D_ _x000D_ SAMM reference:_x000D_ https://owaspsamm.org/about/'
"The SAMM specification follows a community-driven model where any interested stakeholder can join the working group, participate in discussions, and contribute to the model's evolution. Participation is primarily managed through public platforms such as GitHub, and there are no fees or restrictive registration processes required to contribute to the development of the specification._x000D_ _x000D_ SAMM GitHub Contribution:_x000D_ https://github.com/OWASP/samm/blob/master/Current%20Releases/head/contributing-to-git.md_x000D_ _x000D_ OWASP Foundation Membership and Participation:_x000D_ https://owasp.org/membership/_x000D_ _x000D_ SAMM reference:_x000D_ https://owaspsamm.org/about/"
'The SAMM specification includes requirements for the proper protection and management of data throughout its entire lifetime. Within the "Data Protection" practice, the model specifically guides organisations on how to handle data retention and disposal over time. While it does not provide the technical storage tools itself, it ensures that the necessary rules and processes for preserving information are built into the software development lifecycle._x000D_ _x000D_ OWASP SAMM - Data Protection Practice:_x000D_ https://owaspsamm.org/model/operations/operational-management/stream-a/_x000D_ _x000D_ SAMM reference:_x000D_ https://owaspsamm.org/about/'
'SAMM was first released in 2009 and has since become a leading framework for managing software security. It is highly relevant today as it helps organisations meet the high security standards required by European regulations, ensuring that digital services are built to be safe and reliable from the start._x000D_ _x000D_ The most recent major release, SAMM v2.0, marked a significant milestone by completely modernising the framework to align with modern development practices, such as Agile and DevOps. It is a stable, well-documented standard that gives organisations a clear and mature way to plan and measure their security programmes._x000D_ _x000D_ OWASP SAMM v2.0 Release Announcement:_x000D_ https://owasp.org/2020/02/11/SAMM-v2_x000D_ _x000D_ SAMM GitHub Repository (Release History):_x000D_ https://github.com/owaspsamm/core/releases_x000D_ _x000D_ SAMM reference:_x000D_ https://owaspsamm.org/about/'
'The purpose of SAMM is not related to enable the comprehensibility of administrative information, data or services. Therefore, this criterion is not applicable to this specification. _x000D_ _x000D_ SAMM reference:_x000D_ https://owaspsamm.org/about/'
'SAMM aims to help organisations analyse their current software security practices. By following and implementing SAMM European Institutions can improve and develop software that allows data portability ensuring maximum security on these information transactions._x000D_ _x000D_ SAMM reference:_x000D_ https://owaspsamm.org/about/'
'There is no evidence of SAMM being included as a formal standard. However, the specification is highly recognised and recommended by European agencies such as ENISA and ETSI within their guidelines and best practices for securing digital solutions._x000D_ _x000D_ ETSI SmartM2M; Security; Standards Landscape and best practices:_x000D_ https://www.etsi.org/deliver/etsi_tr/103500_103599/103533/01.01.01_60/tr_103533v010101p.pdf_x000D_ _x000D_ ENISA Advancing Software Security in the EU:_x000D_ https://www.enisa.europa.eu/publications/advancing-software-security-through-the-eu-certification-framework_x000D_ _x000D_ SAMM reference:_x000D_ https://owaspsamm.org/about/'
'SAMM is designed with a modular structure that explicitly allows incremental implementation. The model is divided into five business functions and fifteen security practices, enabling organisations to prioritise and implement specific areas based on their unique risk profile and available resources. This ensures that the framework can be adopted in stages, allowing a tailored approach to improving software security maturity over time._x000D_ _x000D_ SAMM reference:_x000D_ https://owaspsamm.org/about/'
'SAMM is actively used in several European cross-border initiatives to improve software security. For instance, the European Union Agency for Cybersecurity (ENISA) recommends it as a reference framework for secure software development lifecycles. This helps organisations across the EU adopt a common approach to building resilient and trustworthy digital services, ensuring that security standards are consistent across borders._x000D_ _x000D_ ENISA - Advancing Software Security in the EU:_x000D_ https://www.enisa.europa.eu/publications/advancing-software-security-through-the-eu-certification-framework_x000D_ _x000D_ ENISA - Good Practices for Security of IoT:_x000D_ https://www.enisa.europa.eu/publications/good-practices-for-security-of-iot-1_x000D_ _x000D_ SAMM reference:_x000D_ https://owaspsamm.org/about/'
'SAMM simplifies the delivery of public services by providing a clear and standardised roadmap for software security. Instead of each department creating its own security rules from scratch, they can follow this proven model to build digital public services more efficiently. This fact helps public administrations to create and implement secure digital public services without wasting time and means. _x000D_ _x000D_ SAMM reference:_x000D_ https://owaspsamm.org/about/'
'SAMM is supported by official resources that allow organisations to measure how well they are following the model. The OWASP Foundation provides the "SAMM Toolbox", which includes assessment spreadsheets and calculators designed to check and validate an organisation's security maturity levels. These tools ensure that the assessment process is structured and consistent, making it easy to track progress and measure results._x000D_ _x000D_ OWASP SAMM Assessment Tools:_x000D_ https://owaspsamm.org/assessment/_x000D_ _x000D_ SAMM reference:_x000D_ https://owaspsamm.org/about/'
'SAMM is not included in any national catalogue of recommended specifications._x000D_ _x000D_ CAMSS List of standards_x000D_ https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards_x000D_ _x000D_ DPA Factsheets_x000D_ https://interoperable-europe.ec.europa.eu/collection/iopeu-monitoring/digital-public-administration-factsheets-2025 _x000D_ _x000D_ SAMM reference:_x000D_ https://owaspsamm.org/about/'
'SAMM is technology agnostic as it focuses on security practices and maturity levels rather than specific technical implementations. It is designed to be applied to any software development project, regardless of the programming language, framework, or technology stack being used._x000D_ _x000D_ SAMM reference:_x000D_ https://owaspsamm.org/about/'
'The SAMM specification enables digital service delivery channels by providing a clear framework to secure the software used for public services. This allows administrations to move in-person procedures online with confidence, ensuring they are safe from cyber threats and reliable for the public._x000D_ _x000D_ SAMM reference:_x000D_ https://owaspsamm.org/about/'
'SAMM is designed to be flexible, allowing organisations to pick and choose the security practices that are most relevant to them. While the overall framework is fixed, users can customise their implementation by prioritising specific areas and setting their own maturity goals based on their unique risks and resources._x000D_ _x000D_ SAMM reference:_x000D_ https://owaspsamm.org/about/'
"SAMM is maintained by the OWASP Foundation. There is a dedicated project team and a large global community of volunteers who work together to keep the model updated and provide support to users. They manage the specification through public platforms, such as GitHub, ensuring that anyone can get help or contribute to the project's maintenance._x000D_ _x000D_ OWASP Foundation:_x000D_ https://owasp.org/_x000D_ _x000D_ SAMM GitHub Repository:_x000D_ https://github.com/owaspsamm/core_x000D_ _x000D_ SAMM reference:_x000D_ https://owaspsamm.org/about/"
'The SAMM specification follows an open development lifecycle where public review is a fundamental step for both major and minor releases. Before any version is officially finalised, drafts are made available for community feedback. This process is primarily conducted through GitHub, where all comments, suggestions, and discussions are publicly visible, ensuring a transparent and collaborative release process._x000D_ _x000D_ SAMM GitHub Issues (Public Review and Feedback):_x000D_ https://github.com/owaspsamm/core/issues_x000D_ _x000D_ OWASP Project Governance and Transparency:_x000D_ https://owasp.org/www-policy/operational/projects_x000D_ _x000D_ SAMM reference:_x000D_ https://owaspsamm.org/about/'
'SAMM is not currently included in any national catalogue of recommended specifications._x000D_ _x000D_ CAMSS List of Standards:_x000D_ https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards_x000D_ _x000D_ SAMM reference:_x000D_ https://owaspsamm.org/about/'
'SAMM is designed to help organisations improve their security, and a big part of that is making sure only the right people can access sensitive data. It includes a dedicated "Data Protection" practice that requires organisations to set up access controls and manage data confidentiality. While it doesn't provide the technical code to restrict access, it gives a clear set of requirements to ensure these protections are built into the software development process._x000D_ _x000D_ OWASP SAMM - Data Protection Practice:_x000D_ https://owaspsamm.org/model/operations/operational-management/stream-a/_x000D_ _x000D_ SAMM reference:_x000D_ https://owaspsamm.org/about/'
'The purpose of SAMM is not related to enable the secure exchenage of data. Therefore, this criterion is not_x000D_ applicable to this specification._x000D_ _x000D_ SAMM reference:_x000D_ https://owaspsamm.org/about/'
'SAMM was first created in 2009 and was later adopted by the OWASP Foundation as a flagship project. It has grown into a globally recognised standard that helps organisations build a clear strategy for software security, with version 2.0 being the most recent major update._x000D_ _x000D_ The model is very relevant for modern digital services, helping them stay secure and compliant with international standards. Its market acceptance is proven by its use in major initiatives, such as the SAMM Benchmark project, which tracks how different organisations across the globe are successfully implementing the framework to protect their software._x000D_ _x000D_ SAMM Benchmark Project:_x000D_ https://owaspsamm.org/benchmark/_x000D_ _x000D_ SAMM reference:_x000D_ https://owaspsamm.org/about/'
"SAMM is supported by a very active community that shares ideas and solutions on platforms like GitHub. Instead of traditional forums, developers and security experts use GitHub to discuss the model's implementation and suggest improvements in real-time._x000D_ _x000D_ SAMM GitHub Repository:_x000D_ https://github.com/owaspsamm/core_x000D_ _x000D_ SAMM reference:_x000D_ https://owaspsamm.org/about/"
'SAMM introduces a "Data Protection" practice that focuses on maintaining data integrity and preventing unauthorised modifications. Additionally, the "Requirements Testing" practice encourages thorough checks to make sure the software handles information correctly according to business rules._x000D_ _x000D_ OWASP SAMM - Data Protection Practice:_x000D_ https://owaspsamm.org/model/operations/operational-management/stream-a/_x000D_ _x000D_ OWASP SAMM - Requirements Testing Practice:_x000D_ https://github.com/OWASP/samm/blob/master/Current%20Releases/v2.0b/core/design/d-security-requirements.md_x000D_ _x000D_ SAMM reference:_x000D_ https://owaspsamm.org/about/'
'The scalability and broad character of the specification can make possible the creation and the availability of solutions fostering the reuse and availability of information between administrations and citizens. This fact demonstrates that the specification can foster the implementation of the once-only principle while ensuring the security and trustworthy data exchanges. _x000D_ _x000D_ SAMM reference:_x000D_ https://owaspsamm.org/about/'
'The SAMM specification is a framework designed to measure and improve software security maturity, rather than a language for modelling business processes. Therefore, this criterion is not applicable to this specification._x000D_ _x000D_ SAMM reference:_x000D_ https://owaspsamm.org/about/'
'SAMM allows organisations to extend the model by adding their own security activities or mapping it to other specific standards. This flexibility means that the specification can be adapted to include new functionalities or requirements that are not part of the core model, ensuring it remains relevant for different technical environments._x000D_ _x000D_ SAMM reference:_x000D_ https://owaspsamm.org/about/'
'The effectiveness of the SAMM specification has been assessed by researchers from the University of Maribor. In the "A Maturity Model for Sustainable Software Development: A Case Study of the OWASP SAMM" study, the SAMM specification is proposed as a framework to measure and improve the security of software development, facilitating the identification of security gaps and the implementation of better security practices._x000D_ _x000D_ "A Maturity Model for Sustainable Software Development: A Case Study of the OWASP SAMM" study:_x000D_ https://www.mdpi.com/2071-1050/15/12/9337_x000D_ _x000D_ SAMM reference:_x000D_ https://owaspsamm.org/about/'
'The purpose of this specification is not related to enable the delivery of multilingual public services. Therefore, this criterion is not applicable to the specification._x000D_ _x000D_ SAMM reference:_x000D_ https://owaspsamm.org/about/'
'SAMM is platform agnostic as it is not tied to any specific operating system, hardware, or cloud environment. It is designed to be a universal framework that can be applied by any organisation, regardless of the platforms they use to develop or host their software._x000D_ _x000D_ SAMM reference:_x000D_ https://owaspsamm.org/about/'
'SAMM includes a specific "Data Protection" practice that focuses on protecting data from unauthorised changes. It also covers "Secure Build" activities, which involve using mechanisms such as code signing to verify that software has not been tampered with. While SAMM does not provide the technical tools itself, it introduces the necessary requirements to ensure data integrity is maintained throughout the development process._x000D_ _x000D_ OWASP SAMM - Data Protection Practice:_x000D_ https://owaspsamm.org/model/operations/operational-management/stream-a/_x000D_ _x000D_ OWASP SAMM - Secure Build Practice:_x000D_ https://owaspsamm.org/model/implementation/secure-build/_x000D_ _x000D_ SAMM reference:_x000D_ https://owaspsamm.org/about/'
CAMSS Assessment of SD-JWT EIF Scenario v1.0.0
Assessment of the SD-JWT with the Common Assesssment Method for Standards and Specifications (CAMSS)
'Despite its relatively recent introduction and rapid standardisation, SD-JWT has already been adopted in European initiatives such as the European Blockchain Services Infrastructure (EBSI) and frameworks, such as IOTA Foundation, a Berlin-based open-source organisation developing technologies to support scalable and practical digital trust._x000D_ _x000D_ Additionally, it can be found in relevant European projects such as the EUDI Wallet Architecture and Reference Framework (ARF). SD-JWT is proposed as a technical specification relevant to both the “Attestation and PID Providers” and “Protocols and Interoperability” sections of the EUDI Wallet framework._x000D_ _x000D_ EBSI Hub Reference:_x000D_ https://hub.ebsi.eu/vc-framework/did/selective-disclosure-sd-jwt _x000D_ _x000D_ SD-JWT in EUDI Wallet reference:_x000D_ https://eudi.dev/2.6.0/technical-specifications/_x000D_ _x000D_ IOTA Refence:_x000D_ https://docs.iota.org/developer/iota-identity/how-tos/verifiable-credentials/selective-disclosure#:~:text=The%20issuer%20makes%20the%20values%20of%20%22locality%22,,the%20address%20to%20be%20disclosed%20and%20presented._x000D_ _x000D_ SD-JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc9901.html'
'SD-JWT specification can enable the secure exchange of data between parties, ensuring that unnecessary data is not shared during specific procedures. Instead, the user can select which property is revealed, thereby avoiding the sharing of other personal data._x000D_ _x000D_ SD-JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc9901.html'
'The SD-JWT specification is not related to enable e-accessibility. Therefore, this criterion is not applicable to the specification._x000D_ _x000D_ SD-JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc9901.html'
'SD-JWT supports the simplification of business processes by allowing a sender to selectively disclose claims of a signed JWT instead of sharing all data with every recipient._x000D_ _x000D_ SD-JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc9901.html'
'The specification first appeared as draft in June 2022 and, since November 2025, has been published as an RFC at Proposed Standard level. The available documentation provides clear details on all modifications introduced across the different released drafts._x000D_ _x000D_ Additionally, organisations have already begun adopting this standard. SD-JWT is an open specificacion utilised on multiple European projects and initiatives, such as European Blockchain Services Infrastructure (EBSI) meaning its sufficiently mature for its use in the development of digital solutions/services._x000D_ _x000D_ European Blockchain Services Infrastructure (EBSI) - SD-JWT reference:_x000D_ https://hub.ebsi.eu/arch-req/standards_x000D_ _x000D_ SD-JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc9901.html'
'SD-JWT is domain-agnostic, as it is primarily focused on the secure and selective disclosure of claims between parties. It ensures integrity through digital signatures and enables selective disclosure without invalidating the original signature, while confidentiality can be achieved when combined with encryption mechanisms. This mechanisms can be applied in different domains, such as business, or health._x000D_ _x000D_ SD-JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc9901.html'
'SD-JWT is maintained by IETF which is an international organisation based in Fremont, California. More specifically, the standard is developed by the OAuth working group._x000D_ _x000D_ OAuth Working Group Reference:_x000D_ https://oauth.net/specs/_x000D_ _x000D_ SD-JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc9901.html'
'SD-JWT relies on the JOSE framework, using the same header structure and processing rules as JWT. It adds selective disclosure, which lets users share only the claims they need from a signed credential. This way, personal data can be kept private while still allowing verification, reducing unnecessary exposure of information._x000D_ _x000D_ SD-JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc9901.html'
'SD-JWT is already associated to EIRA ABBs in the EIRA Library of Interoperability Specifications (ELIS). More specifically, SD-JWT can define the interoperability aspects of the "Access Management Application Component" and "Access Management Application Service" ABBs of the EIRA Technical View._x000D_ _x000D_ _x000D_ EIRA Library of Interoperability Specifications (ELIS):_x000D_ https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/611_x000D_ _x000D_ JWT standard:_x000D_ https://www.rfc-editor.org/rfc/rfc7519_x000D_ _x000D_ SD-JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc9901.html'
'SD-JWT is not related to scope administrative procedures, rules, data, or services. The specification enables the selective disclosure of claims from a digitally signed credential, allowing the holders to reveal only specific information while keeping other claims private. _x000D_ _x000D_ However, the ongoing work from IETF on SD-JWT VC could indirectly support the visibility of procedures, as it introduces a standard way to represent and present digital credentials related to qualifications, permits, or other official attributes._x000D_ _x000D_ Therefore, this criterion is not applicable to the specification._x000D_ _x000D_ IETF SD-JWT VC Reference:_x000D_ https://www.ietf.org/archive/id/draft-ietf-oauth-sd-jwt-vc-15.html_x000D_ _x000D_ SD-JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc9901.html'
'SD-JWT uses JSON to structure claims, which is inherently language-neutral and can carry text in any language or character set._x000D_ _x000D_ JSON specification:_x000D_ https://www.rfc-editor.org/rfc/rfc8259_x000D_ _x000D_ SD-JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc9901.html'
'SD-JWT contributes to secure and trustworthy data exchange by ensuring cryptographic integrity and authenticity. The issuer’s digital signature guarantees that data has not been altered, and selective disclosure mechanisms ensure that only verified claims from the original credential are processed. This supports protection against unauthorised modification during exchange._x000D_ _x000D_ SD-JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc9901.html'
'SD-JWT specification issuer’s digital signature (via JWS) protects the integrity of the credential, ensuring that the signed payload cannot be modified without invalidating the signature. In addition, each selectively disclosable claim is protected through cryptographic digests bound to the signed JWT. When SD-JWT+KB is used, the disclosed claims are protected, preventing any intermediary from adding, removing, or modifying disclosures, ensuring that the data is intact and exactly as originally._x000D_ _x000D_ Integration of SD-JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc9901.html#name-integrity-of-sd-jwts-and-sd_x000D_ _x000D_ JWS specification:_x000D_ https://www.rfc-editor.org/rfc/rfc7515_x000D_ _x000D_ JWT specification:_x000D_ https://www.rfc-editor.org/rfc/rfc7519_x000D_ _x000D_ SD-JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc9901.html'
'SD-JWT allows users to share only the necessary information during specific procedures, revealing selected properties while keeping other personal data private, t hereby preventing unnecessary data exposure._x000D_ _x000D_ SD-JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc9901.html'
'The effectiveness of the SD-JWT specification has been assessed by the NTT Social Informatics Laboratories. In the "Multiparty Selective Disclosure using Attribute-Based Encryption" study, the SD-JWT is analysed by evaluating its feasibility in a virtualised environment through measuring the processing times for token generation, encryption, and decryption. Performance is further assessed by varying the count of disclosures to determine the impact of computational overhead on scalability and real-time applicability._x000D_ _x000D_ "Multiparty Selective Disclosure using Attribute-Based Encryption" study:_x000D_ https://ieeexplore.ieee.org/abstract/document/11126722_x000D_ _x000D_ SD-JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc9901.html'
'SD-JWT can be extended through profiles that enhance security or adapt it to specific ecosystems. In light of this, the base SD-JWT protects the issuer’s signature and the integrity of individual claims, but the set of disclosed claims is not itself protected, meaning disclosures could technically be added or removed without breaking the signature. The SD-JWT+KB (Key Binding) extension addresses this by adding a Key Binding JWT, which binds the disclosed claims to a specific holder key and cryptographically protects the exact set of disclosures. _x000D_ _x000D_ SD-JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc9901.html'
'SD-JWT supports secure access to services, but it is not designed to enable the visibility of administrative procedures, rules data, and services. Its main purpose is to securely exchange and verify claims between parties, ensuring integrity through signatures and, optionally, confidentiality through encryption._x000D_ _x000D_ However, the ongoing work from IETF on SD-JWT VC could indirectly support the visibility of procedures, as it introduces a standard way to represent and present digital credentials related to qualifications, permits, or other official attributes._x000D_ _x000D_ Therefore, this criterion is not applicable to the specification._x000D_ _x000D_ IETF SD-JWT VC Reference:_x000D_ https://www.ietf.org/archive/id/draft-ietf-oauth-sd-jwt-vc-15.html_x000D_ _x000D_ SD-JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc9901.html'
'SD-JWT is discussed across both specialised forums and general developer platforms such as Swift Forums or Github repositories._x000D_ _x000D_ Github Repositories:_x000D_ https://github.com/search?q=SD+jwt&type=repositories_x000D_ _x000D_ Swift Forums SD-JWT:_x000D_ https://forums.swift.org/t/sd-jwt-support-in-jwsetkit-privacy-preserving-credentials-for-swift/83748_x000D_ _x000D_ SD-JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc9901.html'
'SD-JWT specification is not included in any national catalogue of recommended specifications. However, it is used by many European countries and has also been adopted in different European projects. Therefore, this criterion is not applicable to this specification._x000D_ _x000D_ CAMSS List of Standards: _x000D_ https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards_x000D_ _x000D_ SD-JWT Github References:_x000D_ https://github.com/search?q=SD+jwt&type=repositories_x000D_ _x000D_ SD-JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc9901.html'
'SD-JWT guarantees the authenticity and integrity of claims through the issuer’s digital signature (based on JWS), ensuring that the credential originates from a trusted issuer and has not been altered. When Key Binding (SD-JWT+KB) is used, the disclosed claims are cryptographically bound to the holder’s key, preventing replay or misuse and strengthening holder verification._x000D_ _x000D_ Integration of SD-JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc9901.html#name-integrity-of-sd-jwts-and-sd_x000D_ _x000D_ SD-JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc9901.html'
'SD-JWT is not related to the publication of data on the web, as it is designed to securely transmit information between parties. Therefore, this criterion is not applicable to this specification._x000D_ _x000D_ SD-JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc9901.html'
'SD-JWT is not included within the catalogue of any Member State. However, it is used by many European countries and has also been adopted in different European projects. Therefore, this criterion is not applicable to this specification._x000D_ _x000D_ CAMSS List of Standards: _x000D_ https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards_x000D_ _x000D_ SD-JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc9901.html'
'SD-JWT enables data portability, allowing claims to be used across different systems and applications. This makes it easier for services to share and verify information, while selective disclosure or encryption can be applied without affecting the underlying data._x000D_ _x000D_ SD-JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc9901.html'
'SD-JWT can simplify the delivery of European public services by securely transmitting selectively disclosed claims. This allows users to share only the information required for a specific procedure, reducing unnecessary data exposure and simplifying the collection and processing of information by public services._x000D_ _x000D_ EUDI Wallet Reference:_x000D_ https://ec.europa.eu/digital-building-blocks/sites/spaces/EUDIGITALIDENTITYWALLET/pages/694487811/Benefits _x000D_ _x000D_ SD-JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc9901.html'
'SD-JWT is developed by IETF, a non-European organisation. However, it is used by many European countries and has also been adopted in different European projects. Therefore, this criterion is not applicable to this specification._x000D_ _x000D_ IETF Organisation:_x000D_ https://www.ietf.org/_x000D_ _x000D_ SD-JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc9901.html'
'SD-JWT is adopted and reflected in relevant legal frameworks, such as the PID Rulebook of the EUDI Wallet Architecture Reference Framework (ARF). In this context, the specification covers privacy appears covering certain aspects ensuring selective disclosure of information and keeping undisclosed claims hidden while maintain signature validity._x000D_ _x000D_ ANNEX 3.1 - PID Rulebook; SD-JWT reference_x000D_ https://eudi.dev/1.4.0/annexes/annex-3/annex-3.01-pid-rulebook/_x000D_ _x000D_ SD-JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc9901.html'
'The efficiency of the SD-JWT specification has been assessed by the Wilfrid Laurier University. In the "Selective-Disclosure in Decentralised Identity: A Comparative Evaluation of BBS+ and SD-JWT" study, the SD-JWT specification is analysed through a systematic literature review that evaluates its security guarantees, empirical performance metrics like verification latency and proof size, and ecosystem maturity. It employs quantitative synthesis and qualitative assessment to compare these features against BBS+ signatures, highlighting SD-JWT's integration efficiency and standardisation status alongside its privacy trade-offs._x000D_ _x000D_ "Selective-Disclosure in Decentralised Identity: A Comparative Evaluation of BBS+ and SD-JWT" study:_x000D_ https://papers.ssrn.com/sol3/papers.cfm?abstract_id=5360529_x000D_ _x000D_ SD-JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc9901.html'
'SD-JWT allow the reuse of verified claims to be presented across multiple systems and contexts, enhancing interoperability without compromising confidentiality. The disclosed data comes from a single trusted source, and the same claim can be safely reused in different applications without requiring a new credential. For example, a citizen could prove they are over 18 to multiple public services without revealing their full date of birth or address._x000D_ _x000D_ SD-JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc9901.html'
'SD-JWT is platform agnostic since it is based on open standards such as JSON to structure the data, JSON Web Token (JWT) as the base format, JSON Web Signature (JWS) for signing and verification, and JSON Web Key (JWK) for handling keys, which is widely supported across programming languages and platforms. It works with Node.js on the backend, in web browsers using JavaScript, and in mobile frameworks like React Native._x000D_ _x000D_ JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7519.html_x000D_ _x000D_ JWS Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7515.html_x000D_ _x000D_ JWK Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7517.html_x000D_ _x000D_ Open wallet Foundation Github Reference:_x000D_ https://github.com/openwallet-foundation/sd-jwt-js_x000D_ _x000D_ SD-JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc9901.html'
'SD-JWT is used within the EU eIDAS 2.0 framework to secure verifiable credentials. This allows users to share only the necessary information, reducing data exposure and supporting efficient, interoperable digital public service delivery._x000D_ _x000D_ Moreover, the EUDI Wallet Architecture Reference Framework recommends the use of SD-JWT for the selective disclosure of claims from a JWS-protected JWT. In this context, the specification can also be extended with Key Binding (SD-JWT+KB) , providing additional security features and ensuring that the sender of the information is verified._x000D_ _x000D_ EUDI Wallet Architecture Reference Framework Reference:_x000D_ https://eudi.dev/2.8.0/_x000D_ _x000D_ EU eIDAS 2.0 Framework Reference:_x000D_ https://digital-strategy.ec.europa.eu/en/policies/eidas-regulation_x000D_ _x000D_ SD-JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc9901.html'
'SD-JWT allows customization within its specification. Its JWT and JSON structure lets issuers define custom claims, control which claims are disclosed, and optionally implement holder binding. As an example, the working draft of SD-JWT VC applies this same mechanism to Verifiable Credentials, enabling secure issuance and selective disclosure of claims in a VC context while keeping the core process simple and interoperable._x000D_ _x000D_ IETF SD-JWT VC Reference:_x000D_ https://www.ietf.org/archive/id/draft-ietf-oauth-sd-jwt-vc-15.html_x000D_ _x000D_ SD-JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc9901.html'
'SD-JWT provides a secure and standardised mechanism for representing claims that can be exchanged between organisations. By extending JWT and JWS, it enables cryptographically verifiable selective disclosure, allowing each organisation to share only the claims necessary for a specific agreement, reducing unnecessary data exposure and supporting trust and compliance across organisational boundaries._x000D_ _x000D_ JWS specification:_x000D_ https://www.rfc-editor.org/rfc/rfc7515_x000D_ _x000D_ JWT specification:_x000D_ https://www.rfc-editor.org/rfc/rfc7519_x000D_ _x000D_ SD-JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc9901.html'
'SD-JWT specification enables selective disclosure of claims, allowing users to share only the data they chose. This specification is builded on JWT and JWS by enabling cryptographically verifiable selective disclosure of individual claims from a signed payload. These mechanisms help ensure that data remains inaccessible to unauthorised parties during transmission and that the information received has not been altered in transit, thereby preserving both confidentiality and integrity._x000D_ _x000D_ JWT specification:_x000D_ https://www.rfc-editor.org/rfc/rfc7519_x000D_ _x000D_ JWS specification:_x000D_ https://www.rfc-editor.org/rfc/rfc7515_x000D_ _x000D_ SD-JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc9901.html'
'SD-JWT requires implementation of the core selective disclosure mechanism. From there, disclosures can be simple or more complex._x000D_ _x000D_ For example, in the EUDI Wallet, the full SD-JWT feature set is not used. Instead, the implementation relies on a signed JSON Web Token (JWT), the basic selective disclosure mechanism, and simple presentations derived from claims._x000D_ _x000D_ EUDI Wallet Reference:_x000D_ https://eudi.dev/2.8.0/_x000D_ _x000D_ SD-JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc9901.html'
'SD-JWT is not intended to provide access control mechanisms. Its purpose is to represent claims for secure transfer between two parties. The specification extends related standards such as JWT and JWS by adding cryptographically verifiable selective disclosure, allowing individual claims within a signed payload to be revealed without compromising the integrity of the remaining data. Therefore, this criterion is not applicable to the specification._x000D_ _x000D_ SD-JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc9901.html'
'SD-JWT conformance can be effectively assessed through publicly available test tools, such as the SD-JWT Debugger. This test tool allows developers to validate selective disclosure claims._x000D_ _x000D_ SD-JWT Debugger test tool reference:_x000D_ https://www.sdjwt.co/_x000D_ _x000D_ SD-JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc9901.html'
'SD-JWT is technology agnostic since it is defined as an open specification and is based on JSON, which is widely supported across programming languages and platforms, and guarantees technological neutrality and broad compatibility across diverse systems_x000D_ _x000D_ SD-JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc9901.html'
'SD-JWT is not related to enable long-term preservation of data, information, or knowledge. Therefore, this criterion is not applicable to this specification._x000D_ _x000D_ SD-JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc9901.html'
"SD-JWT is not addressed to enable the exposure of interfaces to access the public administration's services. Therefore, this criterion is not applicable to the specification._x000D_ _x000D_ SD-JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc9901.html"
'The SD-JWT specification is listed as one of the specifications used in the EUDI Architecture Reference Framework. Specifically, it is cited as a candidate standard for use in the EUDI Wallet, with no gaps identified in its applicability. Within this context, SD-JWT is applied to Verifiable Credentials, enabling the assurance of authenticity and integrity for PIDs or attestations, while also supporting selective disclosure of attributes._x000D_ _x000D_ SD-JWT in EUDI Wallet reference:_x000D_ https://eudi.dev/2.6.0/technical-specifications/_x000D_ _x000D_ SD-JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc9901.html'
'SD-JWT supports digital service delivery channels by ensuring privacy and control over personal data, as only the necessary information is disclosed. This aligns with eIDAS 2.0, which promotes secure access to services based on verified digital proofs by giving individuals more control over how their personal information is shared._x000D_ _x000D_ eIDAS Regulation Reference:_x000D_ https://digital-strategy.ec.europa.eu/en/policies/eidas-regulation_x000D_ _x000D_ Regulation on electronic identification and trust services Reference:_x000D_ https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv:OJ.L_.2014.257.01.0073.01.ENG_x000D_ _x000D_ SD-JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc9901.html'
CAMSS Assessment of DCAT-AP EIF Scenario v1.0.0
At the moment of performing the assessment, the specification is not included in a catalogue of standards at EU level.
'The Indexed Database API has been published and is maintained by the World Wide Web Consortium (W3C). Additionally, a GitHub repository exists where contributors can raise issues, providing a platform for community engagement around the specification. Indexed Database API: https://www.w3.org/TR/IndexedDB/ Indexed Database API github: https://github.com/w3c/IndexedDB'
'ISO/IEC 27001 is a security standard that formally specifies an Information Security Management system (ISMS) designed to keep information security under explicit management control. As a formal specification, it mandates requirements that define how to implement, monitor, maintain and continually improve the ISMS. It also indicates a set of recommended practices that include documentation requirements, divisions of responsibility, availability, access control, security, auditing, corrective and preventive measures. Certification to ISO/IEC 27001 helps organisations comply with numerous regulatory and legal provisions related to information security. ISO/IEC 27001 reference website: https://www.iso.org/standard/54534.html'
'The purpose of OSI is not related to authentication of the roles agents involved in the data transactions as such, but the specification addresses some authentication requirements on the transfer of data between systems. OSI reference https://www.iso.org/standard/20269.html'
At the moment of performing the assessment, HTML is barely used to develop web pages. With the appearance of XHTML and HTML5, no evidences have been found to consider HTML as an asset to build innovative solutions.
'The ETSI TS 119 512 specification is designed to specifies protocols for trust service providers providing long-term data preservation services of digital signatures and of general data. Using digital signatures or other mechanisms such as time-stamp tokens, data can be protected against unwanted changes. Therefore, when digitally signed data is exchanged by two or more entities, it is certain that they are accurate and have not been modified. ETSI TS 119 512: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.01_60/ts_119512v010101p.pdf'
'DQV focuses on describing data quality information in a standardised vocabulary rather than specifying a particular data format. This allows it to be applied to data stored in various formats, including structured formats like CSV, JSON, XML, as well as semi-structured and unstructured formats. DQV does not prescribe a specific data representation or serialisation format, making it technology agnostic in this aspect. Data Quality Vocabulary: https://www.w3.org/TR/vocab-dqv/'
The purpose of DNS is not related to organisational interoperability. Therefore, this criterion is not applicable to the specification.
As a specification used to encode a wide range of resources, it eases the codification of interfaces ensuring its availability, therefore, UTF-8 helps to ensure the availability of internal information systems from public administrations.
The main purpose of CPOV is to provide a reusable data model for describing public organisations in the European Union. The CPOV helps to identify where responsibilities and functions are duplicated or overlapped. So, it helps to comprehend the administrative rules and data of public administration. CPOV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-organisation-vocabulary
'The SAML 2.0 specification provides the mechanisms that can enable digital service delivery channels, especially in scenarios requiring identity verification, single sign-on, and access control. SAML 2.0 Reference: http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-tech-overview-2.0.html'
ELI can help the availability of administrations data in machine-readable format ensuring its reuse and exchange, however, ELI does not help the availability of interfaces with this internal information. ELI reference: https://eur-lex.europa.eu/eli-register/about.html
"NUTS facilitates organisational interoperability agreements as some of its elements are mappable to other EU Vocabularies elements through the European Legislation Identifier (ELI). However, provisions easing the drafting of such agreements are provided in auxiliary documentation (see ISA Programme-Joinup reference, 'Revise the NUTS RDF model' document). ISA Programme-Joinup reference, 'Revise the NUTS RDF model' document: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/document/supporting-implementation-persistent-uri-policy-eu-institutions"
'ETSI TS 119 612 plays a supportive role in securing trust services that public administrations may use, which in turn helps protect personal data by ensuring secure transactions, strong authentication, and data integrity. However, the specification does offer mechanisms for data protection, but without being exhaustive. ETSI TS 119 612: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf'
The specification was formally defined back in 2012, and version 1.0.0 was released by 2017 with the experience and the expertise of Member States that were closely working together to consolidate the specification. Within ELI home page it can be found different materials that help to visualise and understand how the specification has evolved and how it can be implemented smoothly by Member States increasing the interoperability and ensuring the cost-efficiency. The contribution from Member States helps the evolution of the specification to adapt to users needs. ELI reference: https://eur-lex.europa.eu/eli-register/about.html ELI highlights: https://eur-lex.europa.eu/eli-register/index.html
XSLT is a business domain agnostic specification.
'The Asset Administration Shell (AAS) is not related to public administration services but given that the specification creates the means to conceptualise assets among a group of organisations, they could be adapted in combination with other specification to provide better interfaces for public services. Details of the Asset Administration Shell (AAS) https://industrialdigitaltwin.org/en/wp-content/uploads/sites/2/2024/06/IDTA-01001-3-0-1_SpecificationAssetAdministrationShell_Part1_Metamodel.pdf'
'A few assessments have been carried on the specification efficiency. Given the nature of the Better Regulation Guidelines and Toolbox only a few assessments can be carried out since the specification is rather stable. In this sense, the CEPS report on the Better Regulation and Toolbox defines the specification as clear stepforward in terms of clarity for the administrations to follow although more attention is needed to consider impacts on innovation, especially when it comes to the legislative design and the quantification of impacts. Better Regulation Guidelines and Toolbox reference: https://commission.europa.eu/law/law-making-process/better-regulation/better-regulation-guidelines-and-toolbox_en "To the Commissioner responsible for better regulation" Bruegel's study: https://www.bruegel.org/wp-content/uploads/2019/09/MEMO-Better-Regulation.pdf Final report on the "Study supporting the interim evaluation of the innovation principle", CEPS Study: https://www.ceps.eu/wp-content/uploads/2019/11/KI0219819ENN.en_.pdf'
EuroVoc is not included in any Member States' catalogues of recommended specifications. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'DPV defines a broad notion of semantics for providing a conceptual model of concepts and relationships between them. DPV can facilitate the modelling of personal data categories, and also provides a data model of concepts that act as a vocabulary for the interoperable representation and exchange of information about personal data and its processing. From this point of view, DPV is a good enabler for the modelling of business concepts. DPV specification: https://w3c.github.io/dpv/primer/'
MIME can be found for free along within the European Collaborative Platform, Joinup. MIME in Joinup platform: https://joinup.ec.europa.eu/solution/multipurpose-internet-mail-extensions-mime-rfc-2048-multipurpose-internet-mail-extensions-mime
'OCSP helps easing the formalisation of Interoperability agreements. E.g., the Digital Signature Service. Digital Signature Service framework reference: https://ec.europa.eu/cefdigital/DSS/webapp-demo/doc/dss-documentation.html'
'Being a widely used standard covering privacy aspects, HTTPS has a wide accpetance amongst cross-border projects, including European ones. An interesting example is the TESTA network service – which stands for Trans European Services for Telematics between Administrations – provides a European backbone network for data exchange between a wide variety of public administrations. It is an ISA2 solution which has been designed to support the needs for a whole range of application architectures relying on protocols such as HTTPS. TESTA project: https://ec.europa.eu/isa2/solutions/testa_en '
'By establishing constraints on the creation and exchange of XML documents XSD fosters the trustworthy data exchange between administrations and stakeholders. However, XSD does not include security features in itself. Despite this, XML includes several recommendations in order to ensure the information is protected against unauthorised changes. XSD Reference: https://www.w3.org/TR/2012/REC-xmlschema11-1-20120405/'
ELI is a European Specification developed for its common reuse and to foster the shareability of legal document across borders. It is used within the EU Open Data Portal for the provision of data sets described using the main requirements established by ELI. Doing so, European institutions, businesses and citizens can access and reuse it in a machine-readable format. Moreover, since ELI was developed taking Common Data Model (CMD) from the OP and the implementations require to be compliant with it, it ensures that the content is available from CELLAR, which is an access point to all the open data generated by the Publications office. ELI reference: https://eur-lex.europa.eu/eli-register/about.html ELI technical Information: https://eur-lex.europa.eu/eli-register/technical_information.html EU Open Data Portal Data sets: https://data.europa.eu/euodp/en/data/group/eli?groups=eli
'IEEE Std 802.3-2022 is currently recommended by one Member State: Malta. CAMSS list of standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specificationscamss /camss-list-standards IEEE Std 802.3-2022 Reference: https://ieeexplore.ieee.org/document/9844436'
"There exist several projects developing NFVI solutions. There exist some reports assessing the efficiency of NFVI and other specifications, such as OpenStack. OpenStack is an open source project that provides an open source cloud management system, that has jointly published a gap analysis with the ETSI Testing, Experimentation and Open Source (TST) Working Group. ETSI-OpenStack wiki reference, 'ETSI NFV meets OpenStack workshop materials' section: https://nfvwiki.etsi.org/index.php?title=OpenStack_vs_IFA005006_Gaps"
'There is no Member State that includes GITB TDL in their national catalogue with The National Interoperability Framework (NIF) in alignment with the three categories 1. Conceptual model for integrated public services provision, 2. interoperability layers, and 3. interoperability principles. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
There are different documentation and studies related to the use of LegalRuleML. An example is "Evaluating LegalDocML and LegalRuleML as a Standard for Sharing Normative Information in the AEC/FM Domain analyses the LegalRuleML specification". Moreover, articles referencing the usage of LegalRuleML for automated compliance checking and enabling reasoning using the specification. Evaluating LegalDocML and LegalRuleML as a Standard for Sharing (...): https://www.researchgate.net/publication/318010726_Evaluating_LegalDocML_and_LegalRuleML_as_a_Standard_for_Sharing_Normative_Information_in_the_AECFM_Domain Semantic Business Process Regulatory Compliance Checking Using LegalRuleML https://www.semanticscholar.org/paper/Semantic-Business-Process-Regulatory-Compliance-Governatori-Hashmi/b246867def5e206e296d040ecfbfff06f71a43a6 Enabling Reasoning with LegalRuleML: https://arxiv.org/pdf/1711.06128.pdf
'TLS is included in the national catalogues of standards of at least two Member States, France and the Netherlands, out of the eight that have recommended it. These eight countries are Cyprus, France, Germany, Greece, Malta, the Netherlands, Norway, and Spain. France National Catalogue of Standards (Referentiel General Interoperabilite) Reference: https://www.numerique.gouv.fr/uploads/Referentiel_General_Interoperabilite_V2.pdf Netherlands National Catalogue of Standards TLS Reference: https://www.forumstandaardisatie.nl/open-standaarden/tls CAMSS list of standards: https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-andspecifications-camss/camss-list-standards'
'TLS is already associated to EIRA ABBs in the EIRA Library of Interoperability Specifications (ELIS). More specifically, TLS can define the interoperability aspects of the "Data Exchange" ABBs of the EIRA Technical View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/v610'
'The conformance of GraphQL implementations can be assessed in several ways since it is defined as a set of requirements. GraphQL Website: https://graphql.org/faq/#why-should-i-use-graphql'
'As stated in the specification home page and in Joinup, the application is under development and has not reached a major release v2.0. Nonetheless, the new version of the specification (v1.1) is available since 2017 and it has overcome the existing issues from its first delivery (v1.0) in 2014, and a draft version of the following release (v1.2) is also available from December 2021. WAI-ARIA reference: https://www.w3.org/TR/wai-aria/ WAI-ARIA roadmap reference: https://www.w3.org/WAI/ARIA/roadmap Joinup WAI-ARIA reference: https://joinup.ec.europa.eu/collection/w3c-standards-and-technical-reports/solution/using-wai-aria-html/about'
'The specification defines a set of markup elements that can be used to represent the various components of a legal document, such as sections, articles, paragraphs, and headings. These markup elements can be used to identify, scope comprehesibility and describe administrative procedures, rules data, and services contained within the document. AKN4EU reference: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/akn4eu'
The purpose of the specification is not related to secure and trustworthy data exchange. Therefore, this criterion is not applicable to this specification.
"The specification is associated with EIRA ABB's in the EIRA Library of Interoperability Specifications (ELIS). iCalendar is associated with Mycalendar Component and Mycalendar Application from the Technical Application View (in ELIS 5.0.1, note that the change of version may alterate these associations). iCalendar specification: https://www.rfc-editor.org/rfc/rfc5545 ELIS link: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /solution/elis/release/v501"
The purpose of HTTP is not related to the delivery of multilingual European public services. Therefore this criterion is considered not applicable specification.
'WSDL is maintained by W3C which is an international community developing open standards. W3C WSDL specification: https://www.w3.org/TR/wsdl20 World Wide Web Consortium (W3C): https://www.w3.org/about/'
The specification encompasses a set of requirements, recommendations and principles that need to be taken into account when planning, developing and also when implementing public policies. Within this set of principles defined within the different tools, the Better Regulation Process includes ICT aspects that also take into account interface issues (regarding end-user interfaces but also institutions access to interfaces). Better Regulation Toolbox reference: https://ec.europa.eu/info/sites/info/files/better-regulation-toolbox_2.pdf
'After searching in different catalogues, there is no evidence found of ETSI TS 119 612 being included in the catalogue of any Member State. ETSI TS 119 612 specification: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf'
PNG is a raster-graphics file format that supports lossless data compression. It was first designed for transferring images on the Internet in spite of not being the smallest size image format. Most websites use PNG image to publish their data. However, it is not enough to consider PNG as an asset to facilitate the publication of open data. The specification only complies with the first level of maturity of Tom Berners-Lee's 5-star schema for Open data. Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/es/ PNG W3C reference: https://www.w3.org/TR/PNG/ PNG ISO reference: https://www.iso.org/standard/29581.html
RDF was carried out initially in 1997 by the W3C working group that included representation from several companies with an important market share (e.g. IBM, Microsoft, Netscape, Nokia). RDF has been widely adopted and developed by means of W3C working groups that have worked on the continuous improvement and consolidation of the specification. RDF has strong support as a tool for publishing data as Linked Open Data. This support comes from public administrations but also for companies with relevant market share. This fact demonstrates the maturity and market acceptance for its use in the development of products and services.
"The purpose of HTTP Cookies is to enable web servers to store stateful information on the user's device or to track the user's browsing activity on a given website. Therefore this criterion is not apicable to this specification. HTTP Cookies reference: https://datatracker.ietf.org/doc/html/rfc6265"
'The purpose of the specification is to facilitate the exchange of structured event data. By allowing to make the data available to other persons or organisations, this specification reduces the administrative burden. LDES specification: https://joinup.ec.europa.eu/collection/semic-support-centre/linked-data-event-streams-ldes'
'The specification is focused on providing guidelines, recommendations and mechanisms for the proper development of public policies and laws. Within the recommendations and mechanisms, there are some implications for long-term preservation or archiving, mainly on tool 55 but it is only comprehensive if combined with another specification, the Management and long-term preservation of the European Commission’s Archives, registered under reference number DPR-EC-00837. Better Regulation Guidelines and Toolbox reference: https://commission.europa.eu/law/law-making-process/better-regulation/better-regulation-guidelines-and-toolbox_en Better Regulation Toolbox reference: https://commission.europa.eu/document/download/9c8d2189-8abd-4f29-84e9-abc843cc68e0_en?filename=BR%20toolbox%20-%20Jul%202023%20-%20FINAL.pdf Management and long-term preservation of the European Commission’s Archives https://ec.europa.eu/dpo-register/detail/DPR-EC-00837'
By ensuring the availability of eSignatures elements and metadata, the specification avoids the users to provide information more than one time. Therefore, CAdES fosters the implementation of the Once-only Principle.
eDelivery SMP has diverse implications in terms of Intellectual Property Rights. On one hand, the SMP 1.0 specification which is under non-assertion IPR policy, from OASIS IPR Policy. On the other hand, the ministry of Justice and the European Commission are in charge of part of the specification content. Therefore, the specification is licensed under (F) RAND basis and Royalty-free basis. See: https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery+SMP+-+1.10#eDeliverySMP-1.10-Ownership
'The XML specification itself does not provide inherent mechanisms to ensure or enable data processing accuracy.Therefore this criterion is not applicable to the specification.'
'OData offers access to information from relational databases, file systems, content management systems, traditional websites, and others. Therefore, it enables and reinforces the delivery of European public services. Interoperable Europe Portal OASIS Open Data Protocol reference: https://interoperable-europe.ec.europa.eu/collection/ict-standards-procurement/solution/odp-oasis-open-data-protocol-odata-tc'
'The protocol for remote digital signature creation itself may not directly address data portability, as its primary focus is on defining the technical procedures for creating digital signatures remotely. However, data portability can still be facilitated as part of the broader digital signature workflow that involves the use of such a protocol. Implementations of the protocol aims for interoperability, allowing digital signatures created using one system to be verified by another. This interoperability helps ensure that signed documents remain portable across different platforms and environments. ETSI TS 119 432: https://www.etsi.org/deliver/etsi_ts/119400_119499/119432/01.02.01_60/ts_119432v010201p.pdf'
'While syslog itself does not have direct features related to e-accessibility, the way syslog is implemented and integrated within systems can have implications for accessibility considerations. For instance, log content accessibility can be improved through this specification. The content of syslog messages can be crafted in a way that is accessible to individuals with disabilities. Syslog Protocol: https://datatracker.ietf.org/doc/html/rfc5424'
DNS is publicly available for implementation and use for free on IETF's webpage. See: https://tools.ietf.org/html/1034 https://tools.ietf.org/html/1035
'According to section 4.4 of the documentation, ETSI TS 119 511 provides an interface between users and preservation services, however, specific provision are fully achieved if it is combined with its companion documents ETS TS 119 511 therefore, enabling the visibility of administrative procedures, rules and services if combined with other specifications. ETSI TS 119 511 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119511/01.01.01_60/ts_119511v010101p.pdf TR-ESOR Preservation of Evidence of Cryptographically Signed Document: https://www.bsi.bund.de/EN/Service-Navi/Publications/TechnicalGuidelines/TR03125 /TechnicalGuidelines_03125_node.html'
The purpose of XAdES is not related to the long-term preservation of electronic records and other kinds of information. Therefore, this criterion is not applicable to the specification.
'While the data transfer is controlled by the Transfer Process Protocol mentioned above, the data transfer itself and especially the handling of technical exceptions is an obligation to the Transport Protocol. This specification does not cover the data transfer process as such. IDSA Dataspace Protocol: https://docs.internationaldataspaces.org/ids-knowledgebase/v/dataspace-protocol/overview/readme'
'The purpose of XHTML is to publish administrative data on the web. As one of the main languages used in web development, XHTML helps and fosters the visibility of administration data and services. Moreover, it also eases the decision-making process by ensuring the data exchange and data reuse among stakeholders. XHTML W3C reference: https://www.w3.org/TR/xhtml1/'
'There are existing mechanisms for assessing the conformity of XSD implementations. W3C provides with a XSD test suit that is available for free. Github XSD Test Reference: https://github.com/w3c/xsdtests'
The purpose of SMTP is not related to the publication of public data as open data. Therefore, this criterion is not applicable to this specification. SMTP IETF reference: https://tools.ietf.org/html/rfc5321 Five star open data: https://5stardata.info/en/
TSP is a cryptographic protocol for certifying timestamps using X.509 certificates and public key infrastructure, but it is not defining a data model. TSP IETF reference: https://tools.ietf.org/html/rfc3161
'There are several success stories and implementation examples that provide visibility on the efficiency of implementing ELI. It allows the description of legal resources and increases the shareability across borders enhancing the cooperation amongst European Institutions removing barriers. ELI reference: https://eur-lex.europa.eu/eli-register/about.html ELI highlights: https://eur-lex.europa.eu/eli-register/index.html ELI Testimonials: https://eur-lex.europa.eu/eli-register/testimonials.html'
'The European Union (EU) Member States are currently implementing the INSPIRE Directive and related regulations, included in the ISA programme. This projects includes the usage of XSLT for each member state of the Union. Infrastructure for Spatial Information in Europe: https://ies-svn.jrc.ec.europa.eu/projects/registry-development/wiki/Re3gistry_1_0_documentation#_cp3'
'OpenTelemetry significantly enhances data portability between systems and applications. Its standardised data formats, interoperability, modular design, compliance features, community support, cross-platform compatibility, and dynamic observability capabilities collectively ensure that telemetry data can be easily shared, migrated, and integrated across diverse environments. In fact, one of the main functionalities regarding OTel is to export telemetry data to back-end systems and platforms like ElasticSearch or Prometheus. Metrics Exporter - Prometheus: https://opentelemetry.io/docs/specs/otel/metrics/sdk_exporters/prometheus/ OpenTelemetry: https://opentelemetry.netlify.app/docs/specs/otel/'
"ISAE 3402 Intellectual property rights disclosures' are license-free, therefore it is available with any restrictions related to (F)RAND. ISAE 3402 reference: https://www.ifac.org/system/files/downloads/b014-2010-iaasb-handbook-isae-3402.pdf "
The specification is excellent for accessing and maintaining distributed directory information services over internet. The main function of LDAP is to help users connect to their IT resources safely. Because of this, they are often used in public administrations and have become staples of the identity management industry. LDAP IETF reference: https://tools.ietf.org/html/rfc4511
Several documents are stating positive feedback on the Better Regulation initiative at European Level, which include the Better Regulation Toolbox. Below there are few examples of the documentation providing insights on how important is the process, methodology and tools for the Governance of European Public Policies and laws. Study webpage: https://www.bruegel.org/wp-content/uploads/2019/09/MEMO-Better-Regulation.pdf Study supporting the interim evaluation of the innovation principle: https://www.ceps.eu/wp-content/uploads/2019/11/KI0219819ENN.en_.pdf
PAdES Baseline profile is included in the Connect Europe Facility’s (CEF) eSignature Building Block which helps public administration and stakeholders to accelerate the creation and verification of electronic signatures. Moreover, it eases interoperability across borders avoiding users to provide information on different occasions. Additionally, there is a service (Digital Signature Service) offered by CEF which aims to help the creation and use of eSignature in the context of the European Internal Market. See: https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/Services+eSignature
'The specification does not support the implementation of data integrity mechanisms or features itself. SOAP Reference, section 7 Security Considerations: https://www.w3.org/TR/soap12/#secconsiderations'
The purpose of the specifications is to define technical interoperability aspects. Therefore, the eDelivery SMP 1.10 does not define organisational interoperability aspects.
'Using the vocabulary, almost certainly augmented with sector or country-specific information, will facilitate the process for institutions publishing data about public organisations to keep track of the evolution of public organizations. Therefore, keeping track of the evolution of public administrations is a way to have information and data available from any time of these public administrations. Moreover, standardization allows data to be stored in interoperable and reusable formats, which is central to its long-term preservation, just as compatibility with linked data technologies facilitates the maintenance and continuous updating of information. CPOV Joinup reference: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/core-public-organisation-vocabulary/distribution/core-public-organisation-vocabulary-version-100-pdf'
'Indexed Database API does not rely on any specific technology. Indexed Database API: https://www.w3.org/TR/IndexedDB/'
'The specification only refers to programming languages, does not make any comment about natural languages distinction, only English. GraphQL Language Reference: https://graphql.org/faq/#what-is-a-graphql-client-and-why-would-i-use-one'
'While DoH is not intended for modeling business processes, it is a low-level networking protocol that operates at the DNS layer. It focuses on securing the transmission of DNS-related information between clients and DNS resolvers. Modeling business processes typically involves higher-level concepts and frameworks that go beyond the scope of network protocols like DoH. RFC 8484: https://datatracker.ietf.org/doc/html/rfc8484'
There are no Member States recommending PAdES (ISO 14533-3:2017) in their ICT National Catalogues. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
Better Regulation Toolbox is publicly available and aims to help public administrations in the development of public policies and laws according to real needs while it makes the process and data more transparent fostering the accountability of public administrations. Betterr Regulation Toolbox reference: https://ec.europa.eu/info/sites/info/files/better-regulation-toolbox_2.pdf Objective of Better Regulation Toolbox: https://ec.europa.eu/info/law/law-making-process/planning-and-proposing-law/better-regulation-why-and-how_en#objectives-of-the-better-regulation-agenda
By defining schemas for XML documents, which are involved in the data exchange across borders, XSD ensures and eases the implementation of the once-only principle.
'The purpose of BFO is not related to the protection of personal data managed by Public Administrations since the specification does not provide any privacy considerations. BFO reference: https://www.iso.org/standard/74572.html'
'UDDI is included in 1 national catalogue of recommended specifications. It belongs to France. The National Interoperability Framework (NIF) of France is fully aligned with at least 2 out of 3 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards NIFO factsheets: https://joinup.ec.europa.eu/collection/national-interoperability-framework-observatory-nifo/nifo-factsheets France National catalogue: http://references.modernisation.gouv.fr/sites/default/files/Referentiel_General_Interoperabilite_V2.pdf'
'After checking the different standard catalogues at the supra-national level, the European Commission has listed it within Better Regulation Toolbox with all the specifications and resources produced and used by European Institutions. Even though the specification is not listed in the ICT standards catalogue, it can be considered that is included within a European Catalogue because it is included within the European Commission solutions stack for the development of better digital administrations. Better Regulation Guidelines and Toolbox reference: https://commission.europa.eu/law/law-making-process/better-regulation/better-regulation-guidelines-and-toolbox_en Better Regulation Toolbox reference: https://commission.europa.eu/document/download/9c8d2189-8abd-4f29-84e9-abc843cc68e0_en?filename=BR%20toolbox%20-%20Jul%202023%20-%20FINAL.pdf'
'TS 119 614-1 is intentionally not linked to any software development platform and is also intentinoally agnostic on implementation strategies. This is one of the reasons why the test assertions set includes tests on the correctness of the structure of all the elements specified by the XML Schemas associated with ETSI TS 119 612. ETSI TS 119 614-1 reference: https://www.etsi.org/deliver/etsi_ts/119600_119699/11961401/01.01.01_60/ts_11961401v010101p.pdf'
'After searching in different catalogues and repositories, there is no evidence found of ETSI TS 119 511 being included in the catalogue of any Member State. ETSI TS 119 511 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119511/01.01.01_60/ts_119511v010101p.pdf'
'The purpose of XHTML is not related to facilitate organisational interoperability agreements. Therefore, this criterion does not apply to the specification. XHTML W3C reference: https://www.w3.org/TR/xhtml1/'
ECMA International has clearly defined the procedures that have to be carried out in order to publish standards or technical reports. The procedures are defined in a set of documents that can be found at ECMA's webpage. ECMA International’s decision procedure is basically a two-step process: The first decision step takes place on the level of the Technical Committee (TC) level where consensus is the primary target. The second step is approval at the ECMA International General Assembly. See: http://www.ecma-international.org/memento/policies.htm
'The specification outlines conformance as requirements that are manually measurable. An abstract test suite has been developed to manually verify the conformity of classes, with its feasibility confirmed through testing across multiple distinct implementations. OGC TrainingDML-AI, Abstract Test Suite section: https://docs.ogc.org/is/23-008r3/23-008r3.html#_5097f072-1f22-4e93-be63-429921ab323a OGC TrainingDML-AI Implementations: https://github.com/opengeospatial/TrainingDML-AI_SWG/tree/main/Implementations'
'According to the 5 star Open Data model suggested by Tim Berners-Lee about how to publish linked data, the second star corresponds to make data available as structured data, an area of application of XML. Additionally, RDF is a W3C specification that defines XML syntax for RDF, the de facto standard for publishing Linked Open Data. See: https://5stardata.info/en/ https://www.w3.org/TR/rdf-syntax-grammar/ '
'The Indexed Database API aligns with GDPR Regulation Article 32, which governs security aspects of personal data processing. In this context, within the Health360 project, the specification is used for data caching, ensuring data integrity and availability. While the Health360 project is not a European cross-border initiative, the specification is designed to ensure compliance with GDPR. Health360 GDPR project: https://www.mdpi.com/2076-3417/12/17/8441'
'The once-only principle is an e-government concept that aims to ensure that citizens, institutions, and companies only have to provide certain standard information to the authorities and administrations once. LDAP fosters the OOP in terms of accessibility by allowing administrations stakeholders to keep the contact and access to different distributed services without providing personal data for authentication more than strictly needed. LDAP IETF reference: https://tools.ietf.org/html/rfc4511 '
'The EIRA is in the Interoperable Europe Portal, where solutions related to interoperability and the creation of digital public services are published. Apart from being publicly available there, EIRA can play a crucial role approaching semantic interoperability from the analysis phase, where requirements are set at all levels of the solutions, from legal requirements to technical. By addressing semantic interoperability by design, EIRA can contribute to work towards finding common solutions and can also leverage from other solutions at European or national level related to data management or exchange. EIRA reference: https://interoperable-europe.ec.europa.eu/collection/european-interoperability-reference-architecture-eira /solution/eira/release/610 EIRA Github Repository: https://github.com/CarTool-EC/EIRA'
At the moment of performing the assessment, the specification is associated with several ABB from the latest version published of the ELIS. More specifically, Better Regulation Toolbox can define the interoperability aspects of the "Binding Instrument" , "Non-Binding Instrument", "Public Policy", "Public policy cycle", and ABBs of the EIRA Legal View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/v100
After carrying out information retrieval, no document or study has been found assessing the XHTML in terms of efficiency or effectiveness.
'There are no Member States recommending CIM NGSI-LD API in their ICT National Catalogues. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards '
The purpose of OWL2 is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification. OWL2 W3C reference: https://www.w3.org/TR/owl2-overview/
HTML5 is maintained by W3C which is an international community developing open standards. See: https://www.w3.org/2012/12/html5-cr.html.en
The application of the once-only principle in all EU Member States public administrations aims at reducing the administrative burden. To achieve this, interoperability between public administrations is a sine qua non condition. WS-Security makes safer the SOAP messages which facilitates the exchanging of information within cross border services and impacts positively the development of eGovernment.
OWASP is an open community dedicated to enabling organizations to conceive, develop, acquire, operate, and maintain applications that can be trusted. All of the OWASP tools, documents, forums, and chapters are free and open to anyone interested in improving application security. Moreover, the community has established different ways to contribute to the development of tools and documents. SAMM webpage: https://owaspsamm.org/ SAMM documentation: https://github.com/OWASP/samm/blob/master/Supporting%20Resources/v2.0/OWASP-SAMM-v2.0.pdf Contribute page: https://owaspsamm.org/contributing/
'The data and information encoding is a key point in data exchange and use. In addition, the adoption of the specification as an encoding format fosters the data portability and reuse of information between administrations thus, supporting the implementation and evolution of European public services. UTF-8 specification: https://datatracker.ietf.org/doc/html/rfc3629 '
'SHACL can be implemented across various technology stacks and environments that support RDF. Therefore, the specification is technology agnostic. SHACL Platform and Technology agnostic: https://medium.com/fluree/what-is-shacl-with-examples-2697f659d465 SHACL W3C reference: https://www.w3.org/TR/shacl/'
'There is no evidence found of the creation of any community along with the sharing of their data and results on European platforms. Therefore this criterion is not applicable to this specification. HTTP Cookies reference: https://datatracker.ietf.org/doc/html/rfc6265#section-1'
"iCalendar defines an access classification as the only component of the general security system within a calendar application. However, the access classification serves as a method for capturing the calendar owner's intention for accessing the calendar component. iCalendar specification: https://www.rfc-editor.org/rfc/rfc5545"
'W3C DIDs first public working draft was published in 2019. Since then, changes have been made and are available in the W3C web. In addition, different documentation on its supporting processes has been published to ensure the correct change and release of its content. For instance, section C of the specification explains changes made since the last published version. Revision History DIDs: https://www.w3.org/TR/did-core/#revision-history'
The Core Public Organisation Vocabulary fosters the delivery of multilingual services in European public institutions. In CPOV, the values of all properties with a data type “Literal” may exist in multiple languages. CPOV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-organisation-vocabulary
As a specification with the aim of helping to represent information which can be documents, persons, physical object or abstract objects, it helps administrations to provide information to stakeholders. Therefore, RDF fosters the visibility of the administration's data and services. As a way to make data reusable, it eases the decision-making process.
'TSP is developed by IETF which is based in the USA. Therefore, the specification cannot be regarded as a European Standard. IETF reference: https://www.ietf.org/'
'ETSI carries out the NFV Plugtests Programme. This programme offers a seamless and ubiquitous environment for collaborative testing and validation workshops between different organisations. The NFVI specification effectiveness was tested in different-purpose reports by the ETSI Centre for Testing and Interoperability. ETSI Plugtests Programme: https://www.etsi.org/technologies/nfv/nfv-plugtests-programme ETSI Centre for Testing and Interoperability: https://portal.etsi.org/Services/Centre-for-Testing-Interoperability/Downloads/TestReports'
Core Vocabularies can be used as the foundation of common export formats for data in base registries like cadastral, business registers or public service portals. The Core Location Vocabulary is a simplified, reusable and extensible data model that captures the fundamental characteristics of a location, represented as an address, a geographic name, or a geometry. By describing locations (addresses, geographical names, etc) in a common way using both human and machine-readable format, it allows the publication of information as open data for its consultation and reuse. Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/en/ CLV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-location-vocabulary Use cases and benefits of ISA² specifications: https://ec.europa.eu/isa2/sites/isa/files/docs/publications/isa2_study_use_cases_and_benefits_of_isa2_specifications_january_2019.pdf
'The purpose of WAI-ARIA is not related to the secure processing of data. Therefore, this criterion is not applicable to this specification. WAI-ARIA reference: https://www.w3.org/TR/wai-aria-1.2/'
By allowing the publication of administrative data in the web, as the main language used in the web processing, HTML5 helps and foster the visibility of administration data, and services. Moreover, it also is easing the decision-making process by ensuring the data exchange and reuse. See: https://www.w3.org/2012/12/html5-cr.html.en
'YAML can facilitate organisational interoperability agreements. The specification is easily readable by humans and data can be exchanged between organizations. This fact can help to improve organisational interoperability. YAML specification: https://yaml.org/spec/1.2.2/#11-goals'
'There are two Member States recommending OData in their ICT National Catalogues. These Member States are The Netherlands and France. Netherlands Catalogue reference: https://www.forumstandaardisatie.nl/open-standaarden/aanbevolen France catalogue reference: http://references.modernisation.gouv.fr/sites/default/files/Referentiel_General_Interoperabilite_V2.pdf CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
'Although there is no platform for testing Indexed Database API implementations, there are some resources that offer guides on how to test an Indexed Database API code. In this context, the "Testing your IndexedDB code with Jest" offers a guide on how to test two asynchronous IndexedDB functions with Jest.js. "Testing your IndexedDB code with Jest" guide: https://dev.to/andyhaskell/testing-your-indexeddb-code-with-jest-2o17'
"ebXML provides a set of components enabling users to store and work with any type of electronic content, fostering the visibility of administrations. As well as providing an electronic data interchange model (the ebRIM and the ebRS core components), the specification contributes and promotes to some degree to the visibility of public services' implementations. ebRIM component reference: http://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-rim-v4.0-os.html ebRS component reference: http://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-rs-v4.0-os.html ebXML RegRep OASIS reference: https://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html"
'Even though ISAE 3402 is more focused on auditing and ensuring the management of the information provided in transactions from the private sector, this specification could also help to ensure that the public services requiring information from both parties (Public administrations and the service consumers) are properly managed and monitored allowing the information to be secured and exchanged between public administrations fostering the once-only principle. ISAE 3402 handbook reference: https://www.ifac.org/system/files/downloads/b014-2010-iaasb-handbook-isae-3402.pdf'
'AMQP specification can be extended by using capabilities negotiation. This is where systems use "offered-capabilities" (e.g., high-priority messaging) to indicate the features they can provide, and "desired-capabilities" to indicate that it wants to receive messages that have been marked with a priority level. Additionally, the AMQP type system lets you add extra details to values, called annotations. These annotations provide more context and meaning to the values, making them easier to understand and work with. OASIS AMQP Reference: http://docs.oasis-open.org/amqp/core/v1.0/amqp-core-complete-v1.0.pdf'
PNG was first published as W3C recommendation in October 1996. Later in March 1997 was published in IETF's website as informational RFC 2083. In 2004, it became an ISO/IEC standard (15948:2004 PNG). Nowadays, there are millions of images with PNG extension over the Internet. So it is demonstrated that PNG has enough maturity for its use. RFC 2083 IETF - PNG informational: https://tools.ietf.org/html/rfc2083 PNG ISO reference: https://www.iso.org/standard/29581.html
'The purpose of DNS is not related to the delivery of multilingual services. Therefore this criterion is not applicable specification. DNS IETF reference: https://www.ietf.org/rfc/rfc1034.txt'
'OData offers access to information from relational databases, file systems, content management systems, traditional websites, and others. Therefore, it enables and renforce the delivery of European public services. Joinup reference: https://joinup.ec.europa.eu/collection/ict-standards-procurement/solution/odp-oasis-open-data-protocol-odata-tc/about'
"The specification is associated with EIRA ABB's in the EIRA Library of Interoperability Specifications (ELIS). It is associated with the Legal Act Representation, Open Data and Representation from the Semantic View. ELIS link: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/v501"
XAdED Baseline Profile provides basic authentication and integrity protection and satisfies the legal requirements for advanced electronic signatures as defined in the European Directive. See: https://www.etsi.org/deliver/etsi_ts/103100_103199/103171/02.01.01_60/ts_103171v020101p.pdf
'The purpose of DQV is not related to long term preservation of electronic records. Therefore this criterion is considered not applicable to this specification. DQV reference: https://www.w3.org/TR/vocab-dqv/'
'The purpose of TLS 1.3 is not related to scope of comprehensibly administrative procedures, rules data, and services. Therefore this criterion is not applicable to this specification. TLS 1.3 2018 Reference: https://www.rfc-editor.org/rfc/rfc8446.html'
The main purpose of FTPS as an extension of FTP is to allow the exchange of documents on the internet. So it clearly fosters data portability between systems and applications. FTPS IETF reference: https://tools.ietf.org/html/rfc4217
"EN 303 645 is associated to the consumer IoT devices domain. Prior to some adaptations, the specification could be extended and broaden to specific subsectors. As they state in their official website, CYBER is providing an EN 303 645 template that sets the principles for the specification to be extended. For example, the smart door locks extension is under development and is based on the EN 303 645 specification. EN 303 645, 'Vertical Standard' section: https://www.etsi.org/technologies/consumer-iot-security"
'iCalendar describes conventions for depicting a calendaring and scheduling model, and introduces definitions such as calendaring and scheduling roles that enable the modelling of business processes. iCalendar specification: https://www.rfc-editor.org/rfc/rfc5545 '
'SAREF is designed to be modular and extensible, allowing for partial implementations based on specific use cases and requirements. The flexibility of SAREF comes from its modular structure and the ability to create domain-specific extensions or profiles. This enables developers to focus on the parts of the ontology that are most relevant to their particular applications without necessarily implementing the entire SAREF ontology. SAREF: https://saref.etsi.org/core/v3.1.1/ '
'Verifiable Credentials aims to translate the benefits that physical credentials provide into digital credentials on the Web. Taking initial purpose of the specification, it can be considered that the specification is involved in fostering the comprehensibility of Public Administrations data as well as relevant data produced for the decision-making process. Verifiable Credentials: https://www.w3.org/TR/vc-data-model/'
'The purpose of BFO is not related to the provision of means for restriction of access to information/data since the specification does not provide any means of restriction. BFO reference: https://www.iso.org/standard/74572.html'
XAdES (ISO 14522-2:2012) has the ISO community that supports the development of: International standards, Technical Specifications, Technical Report and Publicly Available Specification. ISO Webpage: http://www.isotc292online.org/projects/iso-process/
At least 4 Member States are recommending IPsec in their ICT National Catalogues. See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'The XACML specification is valuable for enforcing access control within business processes. Its ability to define complex, fine-grained access control policies and dynamically enforce them makes it a critical component for securing business processes and ensuring they operate within the defined access control policies. XACML OASIS reference: https://docs.oasis-open.org/xacml/3.0/xacml-3.0-core-spec-os-en.html'
'As a mail format specification, MIME is a valuable tool for sharing information through the internet between administrations and stakeholders. It allows sharing data and information in a specific format, it fosters the visibility of administration data and services. MIME fosters the collaboration between public administrations and it eases the decision-making process of institutions. MIME reference: https://tools.ietf.org/html/rfc2045'
By listing and describing administrations' web services and improving the discoverability of them, UDDI fosters the visibility of public administration web services.
"At the moment of performing the assessment, SAML 2.0 is widely used to secure and authenticate access to the internal and external platforms as eases the single sign-on (SSO) processes. These types of SSO's are included in the development of platforms and services, including innovative solutions. SAML 2.0 Reference: http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-tech-overview-2.0.html"
JSON is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). Specifically, JSON can define the interoperability aspects of the "Machine to machine interface" ABB of the EIRA Technical View. In addition, JSON can define also the "representation" ABB of the EIRA semantic view. See: https://joinup.ec.europa.eu/solution/elis/distribution/eliscataloguev100betaxlsx
'The Better Regulation Toolbox includes accessibility within the requirements that ICT systems and solutions should cover for the proper implementation of a specific public policy (Tool 27). Therefore, it can be considered that the specification can positively impact the e-accessibility of public services and solutions. Better Regulation Guidelines and Toolbox reference: https://commission.europa.eu/law/law-making-process/better-regulation/better-regulation-guidelines-and-toolbox_en Better Regulation Toolbox reference: https://commission.europa.eu/document/download/9c8d2189-8abd-4f29-84e9-abc843cc68e0_en?filename=BR%20toolbox%20-%20Jul%202023%20-%20FINAL.pdf'
'There has not been found any platform to test conformance to ETSI TS 119 612, nevertheless, the specification lists a set of requirements needed to comply with to be conformant and can be checked manually whether or not applied (see Annex A). ETSI TS 119 612: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf'
'As defined on the OASIS Technical Committee (TC), the OData TC are involved in the release lifecycle of the specification. External contribution to this committee is possible through open channels. Up-to-date, the OData TC has announced three public reviews; however, the topic selection of these reviews is independent of the external contributors. OData OASIS Technical Committee reference: https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=odata OData OASIS Technical Committee, Overview reference: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=odata#overview OData TC third review reference: https://www.oasis-open.org/2021/12/09/invitation-to-comment-on-odata-extension-for-temporal-data-v4-0-3/'
'The purpose of ebXML is not related to the delivery of multilingual services. Therefore this criterion is not applicable to this specification. ebXML RegRep OASIS reference: https://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html'
There is no conformity test coming from the IETF, but there are existing free online documents that will help you validate LDAP specification when it is implemented. However, it is a manual process that does not provide 100% automatic validation. IBM testing LDAP authentication settings: https://www.ibm.com/support/knowledgecenter/SSZQFR_2.2.5/doc/iwd/ldap_test_settings.html Test LDAP configurations: https://docs.microfocus.com/itom/Operations_Orchestration:10.80/Develop/Working_with_API/Testing_LDAP_Configurations
'The W3C Data Quality Vocabulary (DQV) specification is designed to be modular and flexible, allowing for partial implementations based on specific use cases and requirements. For instance, it includes modules for defining quality dimensions, metrics, indicators, constraints, and results. Data Quality Vocabulary: https://www.w3.org/TR/vocab-dqv/'
'The specification is not included in any repository or catalogue of standards at European level. Although EUOS along with ETSI collaboration is considering the use of GraphQL in its catalogue, as stated in the SmartM2M initiative. EUOS - Context Information Management (CIM): Information Model (MOD0): https://www.standict.eu/standards-repository/context-information-management-cim-information-model-mod0 SmartM2M - Study for oneM2M (ETSI): https://www.etsi.org/deliver/etsi_tr/103700_103799/103715/01.01.01_60/tr_103715v010101p.pdf CAMSS Lists Of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
'The Data Archive Interoperability (DAI) Working Group (WG) working under the CCSDS is the communty in charge of the development and maintenance of the OAIS. Moreover, the DAI WG addresses all areas of Archive data formats, functions, services, operations, and interoperability for long-term preservation and exploitation for current and future user communities. Data Archive Interoperability Working Group (DAI WG): https://cwe.ccsds.org/fm/Lists/Charters/DispForm.aspx?ID=23 OAIS specification: https://public.ccsds.org/Pubs/650x0m2.pdf'
'DCAT is a domain-agnostic specification that can be reused for the description of any dataset independently from the business domain. For DCAT users having business-specific requirements, the specification is generally extended (e.g. StatDCAT-AP for statistical data) DCAT (v2.0.0) reference: https://www.w3.org/TR/vocab-dcat-2/ StatDCAT-AP Reference: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/statdcat-application-profile-data-portals-europe/release/100'
The specifications is not directly related with the data exchange, but it could be used to provide user-friendly appearance and detail to those public services accessible via HTML. CSS could support the implementation of digital services avoiding the non-digital ones. CSS v2.1 W3C reference: https://www.w3.org/TR/2011/REC-CSS2-20110607/
Anyone developing software or policy for a public purpose can use this standard to work towards higher-quality public services that are more cost-effective, with less risk and more control. It means that the specification can be applied and implemented for different organisations in different business domains at no cost. The Standard for Public Code webpage: https://standard.publiccode.net/
CAdES does not define a cross-sector reusable data model, but defines an electronic signature format. CAdES ISO reference: https://www.iso.org/standard/64756.html CAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/101700_101799/101733/02.01.01_60/ts_101733v020101p.pdf
'The ebRIM and ebRS core specifications constitute the implementation requirements of ebXML (see ebXML, Conformance reference). Each feature of the core components of the ebXML specification has a conformance requirement set for its implementation. By no means, their implementation is explicitly foreseen according to the ebXML documentation; moreover, there is no specific provision in order to do it separately. ebXML reference, Conformance section: http://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html#__RefHeading__53396_365468741'
'There are public pilot assessments made in Finland, Nordic countries and Estonia. However these are not official assessments endorsed by xbrl international. https://www.suomidigi.fi/sites/default/files/2020-12/Interaktiiviset%20tuotokset.pdf'
'ELI can help the availability of administrations data in machine-readable format ensuring its reuse and exchange, however, ELI does not help the availability of interfaces with this internal information. ELI reference: https://eur-lex.europa.eu/eli-register/about.html'
'RDF itself does not provide security mechanisms, but it can be used in combination with other technologies and standards to ensure the secure processing of data. This may include encryption of data transmission, access control mechanisms, and data validation and verification. RDF primer document: https://www.w3.org/TR/rdf11-primer/'
Ogg does not define a cross-sector reusable data model, but it defines an open standard for multimedia files. Ogg XIPH reference: https://xiph.org/ogg/doc/rfc3533.txt
"This specification is currently not included in the EIRA Library of Interoperability Specifications (ELIS), but will be included in the next release of the ELIS. The response to this criterion is positive because The Asset Administration Shell (AAS) is mappable to the European Interoperability Reference Architecture (EIRA). Currently the specification is listed in the following ABB's: Machine To Machine Interface, Digital Solution Component and Service ABBs. EIRA Library of Interoperability Specifications (ELIS): https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-andspecifications-camss/solution/elis/version-610"
'LDAP is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, LDAP can define the interoperability aspects of the “Registration Service” and “Service Registry Component” ABBs of the EIRA Technical Infrastructure View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/600 '
'AMQP is maintained and developed by OASIS, which is an international community developing open standards; specifically, by the Technical Committee (TC). The specification maintenance is transparent, and even if its development and the approval process is restricted to the specification TC, anyone can contribute by submitting feedback to the mailing list. All the contributions are publicly available. AMQP Organization Community: https://www.amqp.org/ OASIS AMQP Reference: http://docs.oasis-open.org/amqp/core/v1.0/amqp-core-complete-v1.0.pdf'
SOAP 1.2 is associated to an EIRA ABB in the EIRA Library Of Interoperability Specifications (ELIS). WS-Security is a SOAP 1.2 extension so it can be mapped in EIRA too. See: https://joinup.ec.europa.eu/release/eira-library-interoperability-specifications-elis/v100-beta
ADMS does not directly help with the provision of application programming interfaces (APIs) or Web services. However, the specification allows to provide a standardised description for assets in a repository. As well, it allows the discoverability of resources from a single access point. An example of this is the European platform, Joinup. ADMS on Joinup: https://joinup.ec.europa.eu/solution/asset-description-metadata-schema-adms/about ADMS Specification W3C: https://www.w3.org/TR/vocab-adms/
'DPV has not been found to be included in any open repository or catalogue of standards at national level. DPV specification: https://w3c.github.io/dpv/dpv/ DPV primer document: https://w3c.github.io/dpv/primer/#introduction'
SAMM is a business domain agnostic document that can be reused in a cross-domain environment. SAMM webpage: https://owaspsamm.org/ SAMM documentation: https://github.com/OWASP/samm/blob/master/Supporting%20Resources/v2.0/OWASP-SAMM-v2.0.pdf
LDAP is publicly available for implementation and use, and therefore for everyone to study, for free on IETF webpage. LDAP IETF reference: https://tools.ietf.org/html/rfc4511
'The Better Regulation Guidelines and Toolbox is not included in any national catalogue of recommended specifications. CAMSS List of Standards: https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
'No evidence nor disclosures have been found in the specification regarding fostering or harming the long-term preservation of information. ETSI EN 319 422 reference: https://www.etsi.org/deliver/etsi_en/319400_319499/319422/01.01.01_60/en_319422v010101p.pdf'
'The role of TSA is to time-stamp a datum to establish evidence indicating that a datum existed before a particular time. But the TSA can also be used to indicate the time of submission when a deadline is critical, or to indicate the time of transaction for entries in a log. However, for direct data accuracy, it should be complemented with validation checks, error correction algorithms, and quality control processes to ensure correctness and precision of data. TSP IETF reference: https://www.rfc-editor.org/rfc/rfc3161'
'DoH encrypts DNS traffic and requires authentication of the server. DoH improves the security of DNS queries by guaranteeing the authenticity of DNS resolves over HTTPS, thus preventing certain types of cyber-attacks and ensuring that the communication has not been tampered with. However, the typical use of DoH focuses on server authentication (authenticity) and does not usually involve explicit client authentication beyond the basic security measures provided by HTTPS such as SSL/TLS certificates to authenticate the identity of the server. DoH specification: https://datatracker.ietf.org/doc/html/rfc8484'
WSDL has been selected within several cross-border initiatives with the purpose of confirming the description of the services provided in order to enhance the retrieval and support the reuse of the web service by any interested part. An example of a project involving WSDL is the SELIS project. This initiative is focused on eInvocing and its smooth integration within existing accounting software. Moreover, it is included within the framework of the European Digital Single Market and the OOP initiative. See: https://joinup.ec.europa.eu/collection/eprocurement/document/secure-electronic-invoicing-service-selis
The purpose of ODF is not related to the delivery of multilingual public services. Therefore, this criterion is not applicable to the specification. ODF ISO reference: https://www.iso.org/standard/66363.html ODF OASIS reference: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office
'Cloud computing is crucial in the improvement of data processing accuracy. Cloud computing platforms provide scalable resources, allowing users to easily scale up or down based on their processing needs. This scalability ensures that sufficient computing resources are available for data processing tasks, reducing the likelihood of bottlenecks and errors caused by resource limitations. ISO 19941: https://www.iso.org/obp/ui/en/#iso:std:iso-iec:19941:ed-1:v1:en'
'There is no evidence of any assessment regarding the effectiveness of this specification, nor any evaluation submitted by a European administration. Publications Office reference: https://op.europa.eu/en/home Language codelist reference: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/language'
Better Regulation Toolbox is not included in any national catalogue of recommended specifications whose Member State NIF is fully aligned with at least 4 out of 5 sections of the EIF according to NIFO factsheets. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
There are no Member States recommending CAdES (ISO 14533-1:2014) in their ICT National Catalogues. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'The specification allows the user to access a register in which businesses, services and technical data on services are classified. Therefore, having a digital register in which the service can be published, and making it accessible for consultation and use by other organizations, encourages the implementation of digital services, supporting the principle of digital-first. Oracle reference: https://docs.oracle.com/cd/E11036_01/alsb30/consolehelp/uddi.html'
"ISO/IEC 7498:1 is part of Joinup's calogue of ICT Standards for Procurement. Joinup is the European Commission's one-stop shop for interoperable, open and free digital government ICT solutions, and an online space for e-Government professionals and enthusiasts to share and learn about digital public services and initiatives. ISO/IEC 7498:1 Joinup: https://joinup.ec.europa.eu/collection/ict-standards-procurement/solution/isoiec-7498-11994-information-technology-open-systems-interconnection-basic-reference-model-basic"
By means of validating if XML files are conformant with the schema established, the specification helps to ensure the availability of internal information systems of public administrations. It is worth to note that it is possible due to the fact that XML is used to encode communications over the internet.
PAdES is independent of any technology or platform. Moreover, it is independent of any environment, so it can be applied to any environment, for example, smart cards, GSM SIM cards, special programs for electronic signatures, etc. PAdES ISO reference: https://www.iso.org/standard/67937.html PAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/102700_102799/10277801/01.01.01_60/ts_10277801v010101p.pdf
PAdES (ISO 14533-3:2017) is not included in any Member States' catalogues of recommended specifications. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
Core Criterion and Core Evidence Vocabulary is publicly available for its use and implementation. Moreover, it is available for everyone to study with no cost in Joinup webpage. CCCEV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-criterion-and-core-evidence-vocabulary
SHACL is used in many industries and business sectors. The following are examples of this: Wimmics The web-instrumented man-machine interactions, communities and semantics is a research team that lists many projects that are implementing the Semantic web and therefore, RDF. In the context of Wimmics, a SHACL validator has been developed. It was developed using STTL, SPARDQL Template Transformation Language and LDScript. Netage Netage is a system that uses smart data to prevent fire fighters getting injured. For this purpose, Netage implements SHACL for data validation. See: http://wimmics.inria.fr/ http://netage.nl/en/home/
IPv6 has been selected within the TESTA, which provides a secure cross-border data communication network service for public administrations. See: https://ec.europa.eu/idabc/en/document/2097.html
'The EN 16234-1 e-CF framework represents the European e-Competence Framework, which focuses on skills and competences of the ICT professional workforce. Although the specification might evolve in accordance with different frameworks such as the European Qualifications Framework (EQF), European Skills, Competences, Qualifications and Occupations (ESCO), or the global skills and competency framework for the digital world (SFIA), the EN 16234-1 e-CF specification is not dependent on any other specification, and can be considered technology-agnostic (further information on CEN/TC 428 "ICT Professionalism and Digital Competences" Business Plan 2022 reference, section 3). CEN/TC 428 "ICT Professionalism and Digital Competences" Business Plan 2022 reference, section 3: https://standards.cencenelec.eu/BPCEN/1218399.pdf EQF reference: https://europa.eu/europass/en/european-qualifications-framework-eqf?msclkid=4e01b391b58811ec86a2e49c305e4614 ESCO reference: https://esco.ec.europa.eu/en/about-esco/what-esco SFIA reference: https://sfia-online.org/en/about-sfia'
'WSDL is a business agnostic specification that can be implemented in any domain requiring web services description and access, depeloved to be usable beyond business-specific domains and is designed to facilitate interoperability across a wide range of applications and industries. W3C WSDL specification: https://www.w3.org/TR/wsdl20/'
'MIME is a standardized format and set of rules for encoding and exchanging multimedia and non-ASCII data within messages and data on the internet. It is designed to work across different platforms, operating systems, and email clients. MIME specification: https://tools.ietf.org/html/rfc2045 Gmail using MIME: https://developers.google.com/gmail/api/guides/sending?hl=es-419'
'MIME is a business domain agnostic specification that can be reused in a cross-domain way. It can be used for the exchange of files addressing any domain. MIME specification: https://tools.ietf.org/html/rfc2045'
"Assessments of the efficiency of LDES primarily involve evaluating the performance, scalability, and practicality of implementations. For instance, a 2023-doctoral dissertation for Ghent University presents LDES as an open data interface for live data consumption in integrated services, which highlights the specification's efficiency. Linked Data Event Streams as an Open Data Interface for Live Data Consumption in Integrated Services: https://imec-publications.be/bitstream/handle/20.500.12860/41413/phdfinal-brechtvandevyvere.pdf?sequence=1"
The purpose of the Core Location Vocabulary is not related to the delivery of multilingual public services. Therefore, this criterion is not applicable to this specification. CLV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-location-vocabulary
'While is true that Core Business Vocabulary (CBV) gained more popularity on European aspects, the Registered Organization Vocabulary achieved W3C Recommendation status in 2013 indicates that it underwent a rigorous review process by the semantic web community and was deemed a sound and effective specification at that time. Moreover, the fact that CBV built upon the foundations of Registered Organization Vocabulary implies that the core concepts and design principles of Registered Organization Vocabulary were considered valuable and effective enough to be carried forward. Registered Organization Vocabulary reference: https://www.w3.org/TR/vocab-regorg/ Publication of the Core Business Vocabulary as RegOrg on the W3C standards track Reference: https://interoperable-europe.ec.europa.eu/collection/registered-organization-vocabulary/news/publication-core-busin Core Business Vocabulary Reference: https://semiceu.github.io/Core-Business-Vocabulary/releases/2.1.0/'
There are several studies assessing the strengths, weaknesses, effectiveness, and efficiency of TLS which include several references to the version that is being assessed. Moreover, the studies compare the performance form the different versions laying emphasis on strengths and weaknesses. See: http://www-brs.ub.ruhr-uni-bochum.de/netahtml/HSS/Diss/MeyerChristopher/diss.pdf https://arxiv.org/pdf/1902.02531.pdf
At the moment of performing the assessment, TIFF/IT format is used in some cases because it is great for printing images. However, no evidences have been found to consider TIFF/IT as an asset to build innovative solutions.
'ETSI TS 119 512 is indirectly mentioned in the Regulation (EU) No 910/2014 of the European Parliament and of the Council of 23 July 2014 on electronic identification and trust services for electronic transactions in the internal market. In this Regulation, one of the aspects that is mentioned is that the selected specification have to facilitate the implementation of the principle of privacy by design and ensure that personal data is processed in accordance with Directive 95/46/EC. "Regulation (EU) No 910/2014 of the European Parliament and of the Council of 23 July 2014 on electronic identification and trust services for electronic transactions in the internal market" reference: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv:OJ.L_.2014.257.01.0073.01.ENG'
"While there are mechanisms for public and stakeholder participation -including the 'call for evidence' on the 'Have your say' portal, targeted consultations with experts, and feedback opportunities on legislative proposals -the specification does not establish a process for public or stakeholder review and feedback during its development or update lifecycle. Better Regulation Guidelines and Toolbox reference: https://commission.europa.eu/law/law-making-process/better-regulation/better-regulation-guidelines-and-toolbox_en European Parliamentary Research Service briefing https://www.europarl.europa.eu/RegData/etudes/BRIE/2022/699463/EPRS_BRI(2022)699463_EN.pdf Have your say portal: https://ec.europa.eu/info/law/better-regulation/have-your-say_en European Comission webpage: https://commission.europa.eu/law/law-making-process/better-regulation_en#stakeholder-engagement"
'SHACL is already associated to EIRA ABBs in the EIRA Library of Interoperability Specifications (ELIS). More specifically, SHACL can define the interoperability aspects of the "Data Quality" and "Conformance Testing" ABBs of the EIRA Technical View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /solution/elis/release/v610 SHACL W3C reference: https://www.w3.org/TR/shacl/'
'The AMQP specification plays a crucial role in the Harmonised Turbulence project, which delivers turbulence forecast information for air traffic across up to nine flight levels in Europe. This information is retrieved via an AMQP 1.0 subscription, with the message comprising a binary GRIB2 file. Additionally, AMQP is utilised in the Data Management Working Group project within the DERA 2.0 Communication Layer module, providing a secure and reliable exchange protocol. Harmonised Turbulence https://eur-registry.swim.aero/services/dwd-harmonised-turbulence-amqp-10 Data management Working Group: https://bridge-smart-grid-storage-systems-digital-projects.ec.europa.eu/working-groups/data-management#:~:text=The%20Data%20Management%20Working%20Group%20is%20dedicated%20to,among%20stakeholders%2C%20to%20formulating%20rules%20for%https://bridge-smart-grid-storage-systems-digital-projects.ec.europa.eu/working-groups/data-management#:~:text=The%20Data%20Management%20Working%20Group%20is%20dedicated%20to,among%20stakeholders%2C%20to%20formulating%20rules%20for%20data%20exchange. Oasis AMQP Reference: http://docs.oasis-open.org/amqp/core/v1.0/amqp-core-complete-v1.0.pdf '
'ebXML boosts digitisation of data exchange and processing within organisations. It is the case of the Open source CPA toolkit, which is a web-service provider that simplifies business transactions, as it enables the creation of Collaboration Protocol Agreements (CPA). Open source CPA toolkit reference: http://ebxml.xml.org/news/open-source-cpa-toolkit Joinup CPA toolkit reference: https://joinup.ec.europa.eu/collection/ict-security/solution/cpa-creation-toolkit'
The adoption of JPEG as an image format for exchanging photographs helps citizens, business and administrations to share information. JEPG ISO reference: https://www.iso.org/standard/18902.html JPEG public reference: https://jpeg.org/jpeg/
'The OpenTelemetry specification is technology-agnostic, enabling it to be used across diverse technology stacks, platforms, and programming languages. Its standardised protocols, broad language support, modular architecture, and extensive integration capabilities make it a versatile and powerful tool for achieving comprehensive observability in any environment. OpenTelemetry: https://opentelemetry.netlify.app/docs/specs/otel/'
The purpose of WS-Security is not related to the delivery of multilingual public services. Therefore, this criterion is not applicable to the specification.
SHACL does not define organisational interoperability aspects.
'As RDF defines a common framework to express information that can be exchanged between applications without losing meaning, it fosters the trustworthy data exchange between administrations and stakeholders. RDF primer document: https://www.w3.org/TR/rdf11-primer/'
'No, the specification is not a European Standard. CSV reference: https://datatracker.ietf.org/doc/html/rfc4180'
HTTPS is publicly available for implementation and use, and therefore for everyone to study, for free on IETF's webpage. See: https://tools.ietf.org/html/rfc2818
The purpose of IPSec is not related to the definition of a data model. Therefore this criterion is not applicable to this specification. See: https://tools.ietf.org/html/rfc4301
'The purpose of SHACL is not related to enable digital service delivery channels. Therefore this criterion is not applicable to this specification. SHACL W3C reference: https://www.w3.org/TR/shacl/'
'The Asset Administration Shell (AAS) does allow for extensions, specially in the designation of assets, since those can have proprietary extensions in terms of characteristics and capabilities (in the industrial manufacturing context). Details of the Asset Administration Shell (AAS) https://industrialdigitaltwin.org/en/wp-content/uploads/sites/2/2024/06/IDTA-01001-3-0-1_SpecificationAssetAdministrationShell_Part1_Metamodel.pdf'
"RFC 8484 is currently on its 15th version, published in 2018 and has a public document history where any action related to the specification's content is reported. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). The process of creating a standard under IETF is clear: a specification undergoes a period of development and several iterations of review by the Internet community and revision based upon experience are taken place. Furthermore, The IETF welcomes the critical evaluation of protocols and has provided guidance for it. RFC 8484 History: https://datatracker.ietf.org/doc/rfc8484/history/ IESG IETF: https://www.ietf.org/about/groups/iesg/ Standard process IETF: https://www.ietf.org/standards/process/ Protocol Vulnerabilities IETF: https://www.ietf.org/standards/rfcs/vulnerabilities/"
Although the specification is a common method used by European Institutions for the development of projects, no formal agreement (SLAs among others) has been found to consider this criterion positive. However, it is worth to note that there are several initiatives that trust OpenPM2 for the development of projects and reach objectives. As an example, OpenPM2 supports CSDP Missions and Operations. CSDP Missions and Operations: https://www.pm2alliance.eu/our-news/pm2-in-support-of-csdp-missions-and-operations/ PM2 Alliance official webpage: https://www.pm2alliance.eu/
'The specification can be used as a communication protocol in systems that facilitate the delivery of European public services. It is commonly employed in web services architectures to enable interoperability and communication between different systems, which can be beneficial in the context of public service delivery. SOAP Reference: https://www.w3.org/TR/soap12/'
'The purpose of TOSCA is not related to the delivery of multilingual public services. Therefore, this criterion is not applicable to this specification. TOSCA reference: https://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.3/os/TOSCA-Simple-Profile-YAML-v1.3-os.html'
IPv6 is an extensible protocol open to new needs. It can develop together with new advanced application like: P2P, GRID, Ambient Intelligence. See: https://www.nro.net/wp-content/uploads/2010/12/ipv6_is_an_innovation_opportunity.pdf
'The specification does facilitate organisational interoperability agreements such as in the OGC service described in the referenced document. Inspire Network Services SOAP Framework: https://op.europa.eu/en/publication-detail/-/publication/54a89f97-0835-48e8-bf3c-37239e982fbd/language-en'
Although ODF supports the first level of maturity, it does not support the main principles for the publication of data as Linked Open Data. ODF ISO reference: https://www.iso.org/standard/66363.html ODF OASIS reference: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office 5-star linked open data: https://www.w3.org/DesignIssues/LinkedData.html
'The IPv4 specification can be extended with Access Control Lists (ACLs), which ensure that only authorised individuals can access the network. ACLs can help control which hosts can access different parts of the network or determine which types of traffic are forwarded or blocked at router interfaces. IPv4 ACL: https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst2960l/software/15-2_6_e/configuration_guide/b_1526e_consolidated_2960l_cg/m_sec_acls_cg_danube_2960l_cdb.html'
'The specification uses the TestBed service to validate GraphQL queries against GraphQL schemas and it can help simplify the delivery of European public services. Test Bed offers support for projects using GraphQL by launching a new GraphQL validator to validate queries against their target schemas. The validator is based on the GraphQL reference implementation and expects as input the query to validate as well as the target schema. TestBed & GraphQL reference: https://joinup.ec.europa.eu/collection/interoperability-test-bed-repository/solution/interoperability-test-bed/news/new-graphql-validation-service'
The fact that the specification describes the model for being serialised and represented in a machine-readable format fosters the exchange and reuse of information and its translation to other languages different from the original in which was developed the initial resource. Therefore, ODRL can be useful to ensure the availability of access datasets licensing and the related services in different languages, easing the multilingualism of digital public services. W3C specification reference: https://www.w3.org/TR/odrl-vocab/#vocab-core
'The extensibility of DCAT-AP makes the specification a versatile standard that can be adapted and customised to meet the specific needs of different organisations and use cases, while still maintaining compatibility with the core standard. DCAT-AP Specification: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/dcat-application-profile-data-portals-europe/release/200'
The purpose of XSLT is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification.
IETF 3161 Time Stamp Protocol (TSP) is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, IETF 3161 Time-Stamp Protocol (TSP) can define the interoperability aspects of the " e-Timestamp Creation Service", and “e-Timestamp Verification and Validation Service” ABBs of the EIRA Technical View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/solution/elis/release/v100
'The specification purpose is to enable communications over the Internet. IPv6 is the new version of IPv4 which is a widely used protocol thus it is not dependent of any specific platform. Consequently, the adoption of IPv6 does not hamper the interoperability. IPv6 IETF: https://www.rfc-editor.org/rfc/rfc2460'
"FTP is used as the main protocol for file exchange by many public organisations. By allowing public administration to share information with others, it fosters the visibility of data (e.g. Administrative rules, processes etc.) and facilitates public administrations decision-making. An example of implementation supporting this fact would be CIRCABC, a project with the purpose of enhancing the collaboration, communication and document exchange between different European Union's stakeholders. CIRCABC Reference: https://circabc.europa.eu/ui/welcome FTP Specification Reference: https://datatracker.ietf.org/doc/html/rfc959"
SAML 2.0 is a format that allows seamless cross-border interoperability between systems, independent of implementation. The specification allows cross-domain single sign-on, which reduces the administrative burden of the system administrators and the users. As well, providing authentication across sectors and platforms allows administrations and stakeholders to exchange and reuse data fostering the data portability across borders.
'E-ARK CSIP can indirectly support the visibility of administrative procedures and services by promoting the use of descriptive metadata. Descriptive metadata can provide information about the administrative context of records, such as their origin, creator, date of creation, and other relevant administrative details. This metadata helps users understand the administrative procedures and services associated with the records. E-ARK CSIP specification: https://earkcsip.dilcis.eu/#introduction'
The specification was developed in 2014 by Catalogue of Services actions, and it has been evolved taking into account the inputs of the different stakeholders involved according to the development process stated by SEMIC. It is supporting several initiatives at European level, this fact demonstrates the maturity for its use in the development of products and services. CPSV-AP reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-service-vocabulary-application-profile
The purpose of WS-Security is not related to the publication of data as Open Data. Therefore, this criterion is not applicable to this specification.
DNS facilitates the implementation and use of any solution using domains, including innovative solutions.
'The specification is a European Standard. It is a set of technical specifications developed by the European Commission to facilitate the implementation of digital public services across Europe. EU Vocabularies reference: https://op.europa.eu/en/web/eu-vocabularies/schemas'
'This Technical Specification (TS) has been produced by ETSI Technical Committee Smart Machine-to-Machine communications (SmartM2M). The participation in the technical group is reserved to ETSI members, who require registration, fees, and membership approval. Membership requires an annual contribution, determined by the size and nature of the member company or organization and, in the case of large companies, by their financial performance. ETSI Technical Committee SmartM2M: https://www.etsi.org/committee/smartm2m Member benefits: https://www.etsi.org/images/files/membership/Membership-leaflet.pdf'
The purpose of WS-Security is not related to organisational interoperability. Therefore, this criterion is not applicable to the specification.
HTTP is included within at least 11 Member States' ICT Catalogues (e.g. Spain, France, Sweden) See CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'The CSV specification itself does not provide any built-in means for guaranteeing the authenticity and authentication of the roles agents involved in the data transactions. Although the CSV specification does not provide these features directly, they can be implemented in conjunction with the systems or applications that handle CSV files to ensure proper access control and data protection. CSV reference: https://datatracker.ietf.org/doc/html/rfc4180'
'The Extensible Forms Description Language specification is developed by a non-European organisation. Therefore, the specification cannot be considered a European standard. Extensible Forms Description Language reference: https://www.w3.org/TR/NOTE-XFDL'
'XML is maintained by W3C which is an international community developing open standards. See: https://www.w3.org/Consortium/'
'The TGF specification provides guidance on the use of digital identities to support the authentication of roles and agents involved in data transactions. It recommends the use of existing standards for identity and access management, such as OAuth, OpenID Connect, and SAML, to ensure that the authentication of users and agents is secure and reliable. However, the specification itself does not provide guarantees of authenticity and authentication, as these depend on the specific implementation of the guidance and the technologies used. TGF specification: http://docs.oasis-open.org/tgf/TGF/v2.0/cs01/TGF-v2.0-cs01.html'
'The main purpose of the specification Asset Administration Shell (AAS) is to enable the portability of data among partners in the context of the manufacturing industry interoperability. This purpose is in part of the digital twins European initiative (IDTA) which is a German initiative that seeks to create a shared set of tools so manufacturing companies can seamlessly share their assets. IDTA reference: https://industrialdigitaltwin.org/en/ Details of the Asset Administration Shell (AAS) https://industrialdigitaltwin.org/en/wp-content/uploads/sites/2/2024/06/IDTA-01001-3-0-1_SpecificationAssetAdministrationShell_Part1_Metamodel.pdf'
'By allowing the data exchange between applications and systems talking different languages JSON fosters the data portability of European public services. JSON specification: https://www.ecma-international.org/wp-content/uploads/ECMA-404_2nd_edition_december_2017.pdf'
'After checking the different standard catalogues at supra-national level, there is no evidence of schema.org as a European standard. ICT technical specifications: https://ec.europa.eu/growth/single-market/european-standards/ict-standardisation/ict-technical-specifications_en CENELEC and CEN search tool catalogue: https://standards.cencenelec.eu/dyn/www/f?p=CEN:105::RESET::::'
'The purpose of ADMS is not related to guaranteeing authenticity nor authentication. Therefore, this criterion is not applicable to the specification. ADMS Specification W3C: https://www.w3.org/TR/vocab-adms/'
"This specification's protocol allows the connectors to authenticate themselves on DAPS with their X509v3 certificate and to receive an access token in exchange which they can use to access other connectors. Thus, DAPS has the potential to enhance privacy by providing more granular control over the sharing and management of user attributes. DAPS: https://github.com/International-Data-Spaces-Association/IDS-G/tree/main/Components/IdentityProvider/DAPS"
'The Open Geospatial Consortium (OGC) is an international Standards Development Organization headquartered in the United States.While it is based in the U.S., the OGC collaborates with organizations and experts from around the world to develop its standards and specifications. OGC Home: https://www.ogc.org/'
'The purpose of the ESPD is not related to confidentiality, Therefore, this criterion is not applicable to the specification. ESPD business handbook: https://docs.ted.europa.eu/ESPD-EDM/latest/xml_business_handbook.html'
'Although ESPD is not directly designed to facilitate organisational Interoperability agreements, it may indirectly support their development by streamlining the procurement process and reducing administrative burdens for businesses and public authorities. ESPD business handbook: https://docs.ted.europa.eu/ESPD-EDM/latest/xml_business_handbook.html European single procurement document and eCertis: https://single-market-economy.ec.europa.eu/single-market/public-procurement/digitalprocurement/europeansingle-procurement-document-and-ecertis_en'
'ODRL provides a flexible and extensible framework for expressing digital rights and permissions related to digital content, without being tied to a specific domain or industry, meaning that it is intended to be applicable across various industries and use cases. W3C specification: https://www.w3.org/TR/odrl-vocab/#vocab-core W3C ODRL Community: https://github.com/w3c/odrl'
'IPsec can be customised in the sense that the user might opt for one configuration or the other depending on the host implementation requirements needed to deploy the specification. IPSec reference, Where IPSec can be implemented: https://datatracker.ietf.org/doc/html/rfc4301#section-3.3'
'The purpose of LDAP is not related to the visibility of administrative procedures, rules data or services. Therefore, this criterion is not applicable to this specification. LDAP IETF reference: https://tools.ietf.org/html/rfc4511'
'The specification eases the access to information via webpages. Therefore, it reduces administrative burden for citizens, businesses and public administrations. HTTPS specification: https://tools.ietf.org/html/rfc2818'
'The IPv4 specification allows for partial implementations across various scopes, such as within the IP layer. RFC 791 mentions that there are many IP implementations available that can modify the user interface. IPv4 IP impementations https://datatracker.ietf.org/doc/html/rfc791#page-31'
'E-ARK CSIP is designed to be platform-agnostic, allowing organizations to select the platforms and systems that align with their requirements while following the standardized guidelines for information packaging, management, and preservation. E-ARK CSIP specification: https://earkcsip.dilcis.eu/#introduction'
'The purpose of BFO is not related to authenticity and authentication of the roles agents involved in the data transactions. In this sense the specification can be extended using other ontologies available like DCAT. BFO reference: https://www.iso.org/standard/74572.html DCAT reference: https://www.w3.org/TR/vocab-dcat-3/'
Having checked the documentation included in point 2.2.1, the conclusion has been reached of “Research Data Repository Interoperability Recommendations” not being foreseen to be transposed into a European standard within a reasonable time period.
'The PROV family of documents can potentially simplify the delivery of public services by promoting transparency, supporting decision-making, optimizing processes, facilitating interoperability, and enabling knowledge sharing. PROV Primer document: https://www.w3.org/TR/prov-primer/ PROV Ontology: https://www.w3.org/TR/2013/REC-prov-o-20130430/ PROV Data Model: https://www.w3.org/TR/2013/REC-prov-dm-20130430/'
'The specification is not related to enabling the visibility of administrative procedures, rules data and services, therefore it neither promotes nor hinders visibility. Although, it can enable visibility of administrations if it is combined with other specifications, the ECLI report is a good example of that case, where ECLI is based on the Dublin Core terms and eases interoperability in search practices within case law. ECLI Report: https://e-justice.europa.eu/175/EN/european_case_law_identifier_ecli DCMI About: https://www.dublincore.org/about/ '
The definition of the specification justifies this criterion. The Core Public Organisation Vocabulary (CPOV) provides a common data model for describing public organisations in the European Union. CPOV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-organisation-vocabulary
'The specification does not explicitly address the protection of personal data managed by Public Administrations. Therefore, this criterion is not applicable to the specification.'
JPEG is not available for free. It needs to be paid to get access to the specification's text. JEPG ISO reference: https://www.iso.org/standard/18902.html
'Since the CLV vocabulary reuses other vocabularies such as DCTerms, their classes and properties can be customised depending on the use cases. Core Location Vocabulary: https://interoperable-europe.ec.europa.eu/collection/semic-support-centre/solution/core-location-vocabulary/release/100'
'TLS 1.3 enables data portability by providing a robust, standardised, and secure transport mechanism that is independent of the application protocol. Furthermore, the extensibility of TLS 1.3 also offers potential for enhancements that could address specific data portability requirements if needed. TLS 1.3 Reference : https://www.rfc-editor.org/rfc/rfc8446.html'
ADMS is being used as the basis of the European Platform for sharing and reuse Interoperability Solutions Joinup. It is done by an application profile developed to address the specific requirements of the platforms and stakeholder. The ADMS-AP is the schema used for the description of the assets included in Joinup, aiming to increase the cooperation between participants. ADMS on Joinup: https://joinup.ec.europa.eu/solution/asset-description-metadata-schema-adms/about ADMS Specification W3C: https://www.w3.org/TR/vocab-adms/
'ISO/IEC 27001 was developed by the ISO/IEC joint technical committee JTC 1. The access to JTC 1 working area is restricted, and individuals or companies are not eligible as members of ISO. ISO has defined a clear procedure to develop its standards. It consists in a 6-steps process where everyone who is interested can participate. However, if you want to participate, you have to contact your national standards body and you have to be approved for joining the Technical committee (TC) who will develop the standard. ISO has defined the roadmap of standards, it is composed of 6 steps as before said. For the approval of a standard the two-thirds majority of P-members of TC is needed. If the result is negative, the document is returned to TC/SC to be further studied. The ISO standardization process: https://www.iso.org/stages-and-resources-for-standards-development.html ISO/IEC 27001 reference website: https://www.iso.org/standard/54534.html ISO membership reference: https://www.iso.org/get-involved.html'
"The purpose of EN 319 422 is not related to enabling the exposure of interfaces of public administration's services. Therefore,this criterion is not applicable to the specification. ETSI EN 319 422 reference: https://www.etsi.org/deliver/etsi_en/319400_319499/319422/01.01.01_60/en_319422v010101p.pdf"
Germany is recommending XACML in their ICT National Catalogues. Germany catalogue of standards: https://www.din.de/en/about-standards/din-standards CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'OpenTelemetry makes it easy to publish data on the web. It is an open source, vendor-neutral observability framework that enables you to instrument, generate, collect, and export telemetry data such as traces, metrics, and logs. Although client instrumentation for the browser is considered experimental and largely unspecified, OpenTelemetry supports methods for monitoring browser applications and publishing telemetry data. OpenTelemetry: https://opentelemetry.netlify.app/docs/specs/otel/'
"The exposure of interfaces to access public administration's services typically falls within the domain of service-oriented architectures, web services, and related standards. While SAREF itself does not explicitly address the exposure of interfaces, it provides the semantic foundations for better communication between interfaces, although these later depend on other technologies. SAREF: https://saref.etsi.org/core/v3.1.1/ "
'The specification OSI is meant to provide a common basis for the coordination of standards development for the purpose of systems interconnection. In this sense, it could be used to give visibility on the development of standards on interconnection as long as the users are able to navigate through the different layer described on the specification. OSI reference https://www.iso.org/standard/20269.html '
RDF is a business domain agnostic specification that can be used at any business domain requiring RDF features.
The Core Location Vocabulary is publicly available for its use and implementation. Moreover, it is available for everyone to study with no cost on Joinup webpage. CLV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-location-vocabulary
'IEEE Std 802.3-2022 is technology agnostic, supporting various physical media like copper, fibre optics, and wireless connections. Its layered architecture ensures interoperability across different hardware, making it a versatile and widely adopted standard in networking environments. IEEE Std 802.3-2022 Reference: https://ieeexplore.ieee.org/document/9844436'
CSV is included in 3 national catalogues of recommended specifications. They belong to the Netherlands, Estonia, and Sweden. The National Interoperability Framework (NIF) of these Member States is fully aligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO)factsheets. See: https://joinup.ec.europa.eu/collection/national-interoperability-framework-observatory-nifo/nifo-factsheets
'By ensuring that data conforms to predefined shapes and constraints, SHACL simplifies the understanding and accessibility of administrative information. This enhanced visibility enables public administrations to transparently share their processes and services with the public, thereby fostering greater trust and engagement. SHACL W3C reference: https://www.w3.org/TR/shacl/'
'IEEE Std 802.3-2022, despite its American origin, has become a widely adopted and referenced standard within European frameworks. Its inclusion in the standICT catalog underscores its key role in the European technology landscape. This established standard ensures compatibility and interoperability, making it an essential component of European network infrastructure. IEEE Std 802.3-2022 Reference: https://ieeexplore.ieee.org/document/9844436 StandICT list: https://standict.eu/standards-repository/ieee-8023-2018-ieee-standard-ethernet'
'The EN 303 645 specification is not included in any national catalogue. However, the specification has been recommended by some European national agencies like the Federal Office for Information Security (BSI) in Germany, or has been integrated in a public service like the Cybersecurity label in Finland to certify safe smart devices and assist consumers in buying safer products. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards Finnish Transport and Communications Agency Traficom reference: https://www.kyberturvallisuuskeskus.fi/en/news/finland-becomes-first-european-country-certify-safe-smart-devices-new-cybersecurity-label German BSI reference: https://www.bsi.bund.de/DE/Service-Navi/Presse/Pressemitteilungen/Presse2020/SmartHome_130720.html'
LegalRuleML has been selected in several European projects for its implementation and help to its evolution. The main example is LEOS a software for drafting legal resources. Also MIREL, an H2020 project "MIning and REasoning with Legal texts". LEOS: https://joinup.ec.europa.eu/collection/justice-law-and-security/solution/leos-open-source-software-editing-legislation MIREL: https://cordis.europa.eu/project/id/690974/results LegalRuleML reference: http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/legalruleml-core-spec-v1.0.html
'ISO 3166-1 has been adopted by different specifications and used in different contexts, indicating market acceptance. For example, at European level the Publications Office (OP) of the European Union has added ISO 3166-1 to the Country code list (compiled in EU Vocabularies). Moreover, the Domain Name System (DNS) of the Internet is based on the ISO 3166-1 standard which is massively used on a daily basis. ISO 3166-1 reference: https://www.iso.org/standard/72482.html EU Vocabularies reference, Country code list: https://op.europa.eu/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/country Internet Assigned Numbers Authority (IANA) reference, DNS section: https://www.iana.org/domains'
'GraphQL has an active and mutually beneficial collaboration with numerous GraphQL implementers. The GraphQL specification continually evolves under the care of the GraphQL Working Group, which consists of GraphQL experts and public contributors. At any given time, updates to the GraphQL specification are clearly documented reports and are accompanied by tests before deploying to production, often on a very large production scale. GraphQL development process: https://graphql.org/community/developers/#how-graphql-is-developed'
ASiC and ASiC Baseline profile are maintained by ETSI, one of the European Agencies for Standardisation. See: https://www.etsi.org/about
'There’s no explicit mention of partial implementations in the available documentation. However, the standard does provide flexibility in how the training data is prepared and how different metadata is specified for different Machine Learning (ML) tasks. OGC TrainingDML-AI Standard: https://docs.ogc.org/is/23-008r3/23-008r3.html'
'The application of the once-only principle in all EU Member States' public administrations aims at reducing the administrative burden. This Core Vocabulary fosters interoperability between public administrations, cross border services and impacts positively the development of eGovernment. Core Criterion and Core Evidence Vocabulary reference (v1.0.0): https://joinup.ec.europa.eu/release/core-criterion-and-core-evidence-vocabulary-v100 Joinup news page "CCCEV - a key enabler of the Once-Only Principle": https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/news/cccev-and-once-only-principle'
'While the OSI model itself is not a direct enabler of data portability, it can be part of the broader ecosystem of standards and frameworks that contribute to interoperability. Achieving effective data portability typically requires a combination of standardised data formats, well-defined APIs (Application Programming Interfaces), and adherence to relevant regulations and guidelines. ISO/IEC 7498: https://www.iso.org/standard/20269.html'
The Standard for Public Code is a business domain agnostic document that can be reused in a cross-domain. The Standard for Public Code webpage: https://standard.publiccode.net/
Even though the specification is related to the use and publication of metadata, it is not directly related to the publication of open data. The relation with metadata and its publication is focused on the availability and discoverability of access points and different parties for the exchange of data. Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/en/ The specification: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505009
'With the IPsec protocol it is possible to guarantee the authentication of the roles agents involved in transactions, and to allow or deny their access to data. Data is therefore secured against unwanted persons. In addition, it is also possible to set passwords to enter in an IPv6 address. Redhat IPsec reference: https://www.redhat.com/en/blog/ipv6-packets-and-ipsec'
"The IT Professionalism Europe (ITPE) publishes some analysis on the EN 16234-1 e-CF component in different sectors of the European economy. The e-Competence Framework was positively evaluated by the Estonian Association of Information Technology and Telecommunications (ITL) which demonstrated that its application is efficient in policy decision-making. IT Professionalism Europe (ITPE) reference, Reports & Publications section, 'e-CF for EU & national policy makers' document: https://itprofessionalism.org/app/uploads/2019/08/for-EU-national-policy-makers.pdf Estonian Association of Information Technology and Telecommunications (ITL) reference: https://itl.ee/en/"
Although the usage of Registered Organisation Vocabulary has been replaced by the Core Business Vocacabulary in the e-Government Core Vocabularies solution, it has the same content and it is sufficiently mature for the development of products and services. Specifically, there are implementations at European Level combining the Core Business Vocabulary and the Organisation Ontology as it can be seen in the following links. RegOrg Joinup reference: https://joinup.ec.europa.eu/solution/registered-organization-vocabulary Core Business Vocabulary reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-business-vocabulary EU Core Vocabularies in action: https://joinup.ec.europa.eu/sites/default/files/news/attachment/eu_core_vocabularies_in_action_using_core_business_vocabulary_in_the_eu_.pdf Describe organisations in RDF with Core Business Vocabulary and ORG Ontology: https://joinup.ec.europa.eu/collection/registered-organization-vocabulary/document/describe-organizations-rdf-core-business-vocabulary-and-org-ontology
The purpose of CSV is not related to organisational interoperability. Therefore, this criterion is not applicable to the specification.
DCAT-AP is a cross-sector and cross-border reusable vocabulary. In contexts where there are sector-specific or national requirements, the specification is extended (e.g. DCAT-AP-BE, DCAT-AP, StatDCAT-AP)
'This specification is supported by ISO. In order to participate in creating standards, the user must be part of their national standards body (assuming their country is part of ISO). On the other hand, another group that also supports OSI standardisation include Ecma International, an industry association dedicated to the standardization of information and communication systems. Ecma International: https://ecma-international.org/ ISO Technical committees: https://www.iso.org/get-involved.html'
The once-only principle is an e-government concept that aims to ensure that citizens, institutions, and companies only have to provide certain standard information to the authorities and administrations once. HTTPS is a protocol developed to exchange information over the internet environment. Thus, HTTPS eases the implementation of once-only principle by means of allowing administration's stakeholders reduce interaction. See: http://www.toop.eu/sites/default/files/D21_Federated_OOP_Architecture.pdf
"EN 303 645 is not included in any Member States' catalogues of recommended specifications. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards"
After carrying out information retrieval, no document or study has been found assessing the ODF in terms of efficiency or effectiveness.
'ADMS is developed by W3C, a standard development organisation based in the US. Moreover, ADMS specification does not appear in any of the main European standard development bodies, therefore, the specification is not a European standard. CEN-CENELEC homepage: https://www.cencenelec.eu/ ICT technical specifications: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en'
'There are already existing studies and documentation assessing different RDF features. For example, there is a study assessing the effectiveness and efficiency of RDF queries. As well there are studies focused on specific topics as is the fact of using RDF in the Smart Cities Modelling. Effective and Efficient Entity Search in RDF Data: https://www.researchgate.net/publication/221466941_Effective_and_Efficient_Entity_Search_in_RDF_Data Performance assessment of RDF graph databases for smart city services: https://www.sciencedirect.com/science/article/pii/S1045926X1730246X'
'The Core Criterion and Core Evidence Vocabulary is designed to support the exchange of information between organisations or persons (more generally Agents) defining Requirements and organisations or persons responding to these Requirements by means of structured or unstructured Evidences. The specification also uses codelists which are a valuable feature to provide accuracy. Core Criterion and Core Evidence Vocabulary reference (v1.0.0): https://joinup.ec.europa.eu/release/core-criterion-and-core-evidence-vocabulary-v100 '
'There are already existing studies and documents assessing and documenting UDDI features and providing possible improvements of its performance among other aspects. In "Indexing traditional UDDI for efficient discovery of web services" it is proposed a framework which combine the traditional UDDI with search engines to get a more efficient web services discovery. And in "Binding Now or Binding Later" various "UDDI modes of operation are evaluated using performance tests of the UDDI's implementations", to obtain the most efficient use of UDDI in different cases. "Indexing traditional UDDI for efficient discovery of web services" reference: https://www.researchgate.net/publication/303921682_INDEXING_TRADITIONAL_UDDI_FOR_EFFICIENT_DISCOVERY_OF_WEB_SERVICES "Binding Now or Binding Later" reference: https://www.academia.edu/14435163/Binding_now_or_binding_later_The_performance_of_UDDI_registries'
'The effectiveness of ISO/IEC 7498:1 is often evaluated through various means, including practical implementations and pilot projects. For instance, a 2016-paper uses the OSI Layer model, which has defined the theoretical architecture for network communications, as the starting point for innovating additional Layer 2 security requirements for a protected stack, which demonstrates the effectiveness of the specification as it is taken into account. Innovating additional Layer 2 security requirements for a protected stack: https://ro.ecu.edu.au/ism/184/'
'E-ARK CSIP allows for partial implementations, enabling organizations to adopt and implement specific components or aspects of the specification based on their needs and priorities. It provides flexibility for organizations to tailor their implementation while considering the potential impact on interoperability and long-term preservation. E-ARK CSIP specification: https://earkcsip.dilcis.eu/#introduction'
'Preservation of data and electronic records typically involve considerations beyond the scope of SCIM. Therefore, this criterion is not applicable to the specification. SCIM: https://scim.cloud/'
The purpose of HTML5 is not related to the long-term preservation of electronic records and other kinds of information. Therefore, this criterion is not applicable to the specification.
According to the 5 star Open Data model suggested by Tim Berners-Lee about how to publish linked data, the second star corresponds to make data available as structured data, an area of application of XML. See: https://5stardata.info/en/
'EuroVoc is managed by the Publications Office of the European Union, which moved forward to ontology based thesaurus management and semantic web technologies conformant to W3C recommendations as well as latest trends in thesaurus standards. EuroVoc: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource /dataset/eurovoc'
The Service Metadata Publishing describes also the binding of the specification with the REST interfaces for the Service Metadata Publication within a 4-Corner network. Therefore, the specification fosters the availability of interfaces containing information from the different parties involved in a 4-corner network. The specification: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505000
SMTP is included in 3 national catalogues of recommended specifications. They belong to the Netherlands, Spain and Sweden. The National Interoperability Framework (NIF) of these Member States is fully aligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. National catalogue the Netherlands: https://www.forumstandaardisatie.nl/open-standaarden National catalogue Spain: https://administracionelectronica.gob.es/pae_Home/pae_Estrategias/pae_Interoperabilidad_Inicio/pae_Normas_tecnicas_de_interoperabilidad.html#CATALOGOESTANDARES National catalogue Sweden: https://www.avropa.se/globalassets/dokument/open-it-standards.pdf?_t_id=1B2M2Y8AsgTpgAmY7PhCfg%3d%3d&_t_q=standards&_t_tags=language%3asv%2csiteid%3a95d515a5-23ca-47bf-87a9-07b10d8ac360&_t_ip=178.139.72.144&_t_hit.id=Avropa_Core_Models_Media_GenericMedia/_ff07d720-f793-44b0-994d-27e79b28f6bd&_t_hit.pos=7 NIFO factsheets: https://joinup.ec.europa.eu/collection/national-interoperability-framework-observatory-nifo/nifo-factsheets
'The SFIA Foundation provides and organises webinars, conference and trainings where users can share their data and results world-wide, including European platforms. SFIA reference, March 2022-SFIA update: https://sfia-online.org/en/news/march-2022-sfia-update?msclkid=16935e81bb4511ec9e5c03c7f99e833f'
'1 Member State is recommending ebXML in its ICT National Catalogue. It Member State is Norway. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards ebXML RegRep OASIS reference: https://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html'
The specification has already been assessed using the CAMSS method in the MSP scenario, which is fully compliant with the European Standardisation Regulation. _x000D_ _x000D_ CAMSS Library of Assessments: _x000D_ https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-assessments-library_x000D_ _x000D_ ICT technical specifications:_x000D_ https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en
"Some provisions on data storage are depicted in ISO/IEC 19944-1, nonetheless, specific guidelines to enable the long-term preservation of data are not in the specification's scope. ISO/IEC 19944-1 specification: https://www.iso.org/standard/60545.html"
The specification does not define a cross-sector reusable data model. PM2 is a light and easy-to-implement methodology which project teams can tailor to their specific needs. OpenPM2 specification reference: https://op.europa.eu/en/publication-detail/-/publication/ac3e118a-cb6e-11e8-9424-01aa75ed71a1/language-en/format-PDF/source-83307127
'While IndexedDB does not directly aid in modeling business processes, it can be part of a solution that enables the execution and management of business processes, especially in applications where local storage and offline functionality are required. Indexed Database API: https://www.w3.org/TR/IndexedDB/'
ETSI’s Intellectual Property Rights Policy is based on Standard Essential Patents (SEP). The policy implemented by the standardisation organisation seeks to reduce risks and ensure that the standards are available under (F) RAND basis and Royalty-free, meaning its costless or with the most optimum fee for the function that will be used. See: https://www.etsi.org/intellectual-property-rights
As an extension of DCAT, DCAT-AP by allowing the description of catalogues and datasets, aggregated DCAT-AP metadata can serve as a manifest file as part of the digital preservation process. See: https://www.w3.org/TR/vocab-dcat-2/
'RDF is developed by W3C, a standard development organisation based in the US. Moreover, RDF specification does not appear in any of the main European standard development bodies, therefore, the specification is not a European standard. CEN-CENELEC homepage: https://www.cencenelec.eu/ ETSI homepage: https://www.etsi.org/'
'By nature, LDAP is compatible with different operating systems and devices. However, different LDAP offerings may limit this flexibility; AD, for example, is Windows-centric and often requires add-ons to work seamlessly with additional operating systems. LDAP IETF reference: https://tools.ietf.org/html/rfc4511 LDAP with Active Directory: https://www.solarwindsmsp.com/blog/difference-between-ldap-ad'
ASiC Baseline Profile provides basic features needed to overcome barriers in the accomplishment of signed data interchange across borders. By providing different levels of conformity according to data transaction needs, it is highly scalable without hampering the interoperability between actors involved.
'OData follows REST principles and there exists some kind of data protection. However, the purpose of OData is not related to the security and privacy of the data exchange. OData reference: http://docs.oasis-open.org/odata/odata/v4.0/errata03/os/complete/part1-protocol/odata-v4.0-errata03-os-part1-protocol-complete.html#_Toc453752201'
Although the Core Public Organisation Vocabulary does not have a good market acceptance, it proportionates innovative benefits such as facilitate information sharing, facilitate the development of common information systems, and cross-border information exchange. CPOV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-organisation-vocabulary
'TLS 1.3 is developed and maintained by IETF, a widely recognised open international community developing standards to enhance the internet. IETF Reference: https://www.ietf.org/ TLS 1.3 2018 Reference: https://www.rfc-editor.org/rfc/rfc8446.html'
'ETSI TS 119 511 is maintained by ETSI, one of the European Agencies for Standardisation. Moreover, the ESI family of specifications is developed and maintained by a technical committee, and it is supported by some organisations such as BMWi or Cryptolog International. About ETSI: https://www.etsi.org/about ESI Technical Committee: https://www.etsi.org/committee/1399-es ESI work programme: https://portal.etsi.org/webapp/WorkProgram/Report_WorkItem.asp?WKI_ID=53589&curItemNr=1&totalNrItems=1&optDisplay=10&qSORT=HIGHVERSION&qETSI_ALL=&SearchPage=TRUE&qETSI_NUMBER=119+511&qINCLUDE_SUB_TB=True&qINCLUDE_MOVED_ON=&qSTOP_FLG=&qKEYWORD_BOOLEAN=&qCLUSTER_BOOLEAN=&qFREQUENCIES_BOOLEAN=&qSTOPPING_OUTDATED=&butSimple=Search&includeNonActiveTB=FALSE&includeSubProjectCode=&qREPORT_TYPE=SUMMARY'
'The specification explicitly addresses and enables data portability syntantic, semantic and policy wise. The goal of data portability in this ISO is to enable cloud service customers (CSCs) to move their data or applications between non-cloud and one or more cloud services and between cloud services. The critical considerations for portability discussions are the porting cost, the risks associated with the porting and how to control the costs and risks compared to the expected benefits. ISO 19941: https://www.iso.org/obp/ui/en/#iso:std:iso-iec:19941:ed-1:v1:en'
As a document format, ODF helps to make data available on the internet. This fact demonstrates that the standard is supporting the first level of maturity from Tim Berners-Lee's 5-star schema for Open data. ODF ISO reference: https://www.iso.org/standard/66363.html ODF OASIS reference: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/es/
'ISO/IEC 19944-1 can enable digital service delivery channels by leveraging cloud computing technologies. It provides guidelines for scalable and available services, promotes integration and interoperability, supports rapid deployment, and enhances the accessibility of digital services. ISO/IEC 19944-1 specification: https://www.iso.org/standard/60545.html'
'While publiccode.yml is not yet embedded in a specific European cross-border initiative, it holds clear potential to advance the goals of the Interoperable Europe Act. As a structured metadata specification for cataloguing public sector software, it would significantly aid in the discoverability and reuse of digital solutions, supporting cooperation, co-creation, and cross-border collaboration. By promoting transparency and interoperability, publiccode.yml could serve as a foundational tool in fostering a shared European digital ecosystem. Publiccode.yaml documentation: https://docs.italia.it/italia/developers-italia/publiccodeyml-en/en/master/index.html Interoperable Europe Act: https://eur-lex.europa.eu/legal-content/en/TXT/?uri=CELEX:32024R0903'
'The Registered Organization Vocabulary specification enables data portability for European public services by providing a standardised vocabulary based on established ontologies and supporting the use of European standard classifications. It shares foundational principles with the SEMIC Core Business Vocabulary (CBV), which captures key attributes of legal entities registered through formal processes. Registered Organization Vocabulary reference: https://www.w3.org/TR/vocab-regorg/ Core Business Vocabulary Github reference: https://github.com/SEMICeu/Core-Business-Vocabulary/tree/master'
'RDF was carried out initially in 1997 by the W3C working group that included representation from several companies with an important market share (e.g. IBM, Microsoft, Netscape, Nokia). RDF has been widely adopted and developed by means of W3C working groups that have worked on the continuous improvement and consolidation of the specification. RDF has strong support as a tool for publishing data as Linked Open Data. This support comes from public administrations but also for companies with relevant market share. This fact demonstrates the maturity and market acceptance for its use in the development of products and services. RDF primer document: https://www.w3.org/TR/rdf11-primer/'
'The specification includes a whole set of enablers related to security at different levels. Moreover, EIRA helps users when working on analysing the requirements for digital public services, and makes it by providing specific perspectives and viewpoints related to security and privacy. Going deeper in details, there are specific enablers related to identify the requirements for identity and access management, which are the building blocks that will ensure that access to data is controlled, e-signature, e-seal amongst others. Additionally, elements such Trust enablers or blockchain can be consider assets and components that can help to ensure data integrity and data authenticity. EIRA reference: https://interoperable-europe.ec.europa.eu/collection/european-interoperability-reference-architecture-eira /solution/eira/release/610 EIRA Github Repository: https://github.com/CarTool-EC/EIRA'
'XHTML has no mechanism to guarantees the authenticity and authentication of the roles agents involved in the data transactions. Therefore, this criterion is not applicable to the specification. XHTML W3C reference: https://www.w3.org/TR/xhtml1/'
8 Member States are recommending JPEG in their ICT National Catalogues. These Member States are Estonia, France, Germany, Greece, Norway, Poland, Slovenia and Spain. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
PDF 1.7 has the ISO community that supports the development of: International standards, Technical Specifications, Technical Report and Publicly Available Specification. See: http://www.isotc292online.org/projects/iso-process/
"The NUTS classification counts for funding projects within the EU, that is the European Regional Development Fund, the European Social Fund Plus and the Cohesion Fund. Besides, the specification RDF model has been revised in 2018, so that it could be mapped to a European Legislation Identifier (ELI), and as a consequence the NUTS classification can be linked to other EU Vocabularies and used in other European cross-border initiatives. EUR-LEX reference, COMMISSION IMPLEMENTING DECISION (EU) 2021/1130: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=celex%3A32021D1130 ISA Programme-Joinup reference, 'Revise the NUTS RDF model' document: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/document/supporting-implementation-persistent-uri-policy-eu-institutions"
There are no Member States recommending Xforms 2.0 in their ICT National Catalogues. However, Germany is recommending a previous version, Xforms 1.1. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'By allowing the exchange of datasets metadata, DCAT increases the searchability, visibility, discoverability and reuse of existing data, including information on processes and administrative rules. It is worth mentioning the DCAT-AP specification for European Data Portals as an example of the previous explanation. DCAT-AP & European Data Portals reference: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/dcat-application-profile-data-portals-europe DEU data provider manual: https://dataeuropa.gitlab.io/data-provider-manual/ DCAT (v2.0.0) reference: https://www.w3.org/TR/vocab-dcat-2/ '
The purpose of XSD 1.1 is not related to define organisational interoperability aspects. Therefore this criterion is considered not applicable to this specification.
The purpose of SHACL is not related in any way to e-accessibility. Therefore, this criterion is not applicable.
The Registered Organization Vocabulary is a simplified, reusable and extensible data model that captures the fundamental characteristics of a legal entity. It facilitates the information exchange between business sectors. So, it fosters data portability between systems and applications supporting the implementation and evolution of European public services. RegOrg Joinup reference: https://joinup.ec.europa.eu/solution/registered-organization-vocabulary RegOrg W3C reference: https://www.w3.org/TR/vocab-regorg/
'Domibus has been found being used at the core of the Multilingual Anonymisation for Public Administrations (MAPA) project, which aims at introducing NLP tools and at developing a toolkit for effective and reliable anonymisation of tect on the medical and legal fields. MAPA project: https://mapa-project.eu/2022/01/ Domibus specification: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/Domibus Regulation (EU) 910/2014: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv%3AOJ.L_.2014.257.01.0073.01.ENG'
'The ETSI TS 119 612 specification establishes security mechanisms, such as digital signatures, to guarantee the authentication of agents involved in data transactions. In this context, it ensures the authenticity of agents by signing a trusted list. ETSI TS 119 612: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf'
'At the time of elaborating this assessment, this specification is included in the "Linked Data Event Stream" ABB in the current EIRA Library Of Interoperability Specifications (ELIS), specifically the "Semantic View" layer. It is also included in the "Immutable Database Manager" ABB, which is in the "Technical-Infrastructure View" layer. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /solution/elis/release/600'
"AMQP specification allows systems to send and receive messages securely and efficiently. Once a message is successfully delivered and acknowledged, AMQP can delete it from the queue. This means that the data doesn't linger indefinitely, which helps in managing resources efficiently. OASIS AMQP Reference: http://docs.oasis-open.org/amqp/core/v1.0/amqp-core-complete-v1.0.pdf"
'There are existing documentation and studies assessing the efficiency of IPv4. The "Performance Evaluation of IPv6 and IPv4 for Future Technologies" aims to perform a comparative study on the performance of IPv4 and IPv6 for measuring the quality of VoIP calls. "Performance Evaluation of IPv6 and IPv4 for Future Technologies" study: https://link.springer.com/chapter/10.1007/978-3-030-39445-5_2'
The implementation of OpenPM methodology for developing projects including data portability steps would foster the proper development of European Public Services. OpenPM2 specification reference: https://op.europa.eu/en/publication-detail/-/publication/ac3e118a-cb6e-11e8-9424-01aa75ed71a1/language-en/format-PDF/source-83307127
IPv6 is already associated to EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, IPv6 can define the interoperability aspects of the "Network", "Networking Service", "Private Network" and "Public Network" ABBs of the EIRA Technical View. See: https://joinup.ec.europa.eu/solution/elis/distribution/eliscataloguev100betaxlsx
'XHTML has some features to prevent possible security vulnerabilities. Moreover, by allowing to exchange data via online websites. However, interactive sites increases vulnerabilities which may compromise the integrity of the user’s personal data. XHTML W3C reference: https://www.w3.org/TR/xhtml1/'
'ISO/IEC19944-1 does not directly relate to the modelling of business processes; however, the normative nature of the specification enphasizes the need for defined requirements and standardized approaches in cloud-service management. This way organisations can align their business processes with cloud service management outlined in the specification. ISO/IEC 19944-1 specification: https://www.iso.org/standard/60545.html '
'After some research, nothing related to licensing on royalty-free basis has been found. DCMI About: https://www.dublincore.org/about/ '
'The purpose of IPsec is not related to the publication of public data as open data. Therefore this criterion is not applicable to this specification. IPSec reference: https://www.rfc-editor.org/rfc/rfc6071.html'
'ODRL specification is primarily focused on expressing rights and permissions related to digital content, and it is not inherently designed for exposing interfaces to access public administration services. ODRL is more oriented towards digital rights management (DRM) and content distribution scenarios, allowing the specification and communication of policies regarding the usage and sharing of digital assets. W3C specification reference: https://www.w3.org/TR/odrl-vocab/#vocab-core'
"Verifiable Credentials is not included in any Member States' catalogues of recommended specifications. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards"
'DQV is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, DQV can define the interoperability aspects of the “Linked Data”, "Linked Open Data", "Open Data", "Controlled Vocabulary", "Data", "Data Format", "Data Model", "Hash Code", "Metadata", and "Ontology" ABBs of the EIRA Technical Infrastructure View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/600'
' HTTPS allows for extension through the addition of new features and functionalities. The HTTPS protocol itself is based on the HTTP protocol, and various extensions have been developed to enhance its capabilities and address specific requirements. One example of an extension to HTTPS is the Application-Layer Protocol Negotiation (ALPN), which allows the client and server to negotiate the application-layer protocol to be used over the secured connection. HTTPS specification: https://tools.ietf.org/html/rfc2818 ALPN specification: https://datatracker.ietf.org/doc/html/rfc7639 '
'This specification has specific sections that present facet models that can be adapted into bussiness models. Furthermore, cloud data portability has an important part where it is thoroughly described how to operate in different case scenarios. ISO 19941: https://www.iso.org/obp/ui/en/#iso:std:iso-iec:19941:ed-1:v1:en'
'The Belgian Interoperability Framework (Belgif) includes the OSLO framework, which is used for semantic interoperability in Belgium. Within OSLO, various key elements and properties from RegOrg are still being utilised. Therefore, the RegOrg vocabulary is still included in a national-level open catalogue of standards. Registered Organization Vocabulary reference: https://www.w3.org/TR/vocab-regorg/ Belgian Interoperability Framework (Belgif): https://www.belgif.be/page/specifications.en.html OSLO Smart City Distribution - Application profile Reference: https://data.vlaanderen.be/doc/applicatieprofiel/slimme-stadsdistributie/ ICT technical specifications: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en '
"The specification is a widely used de-facto standard. Thus, it is sufficiently mature for the development of products and services. Since it's recommendation by W3c in 1996, XML has been used by many products and services. See: https://www.w3.org/TR/2006/REC-xml11-20060816/"
'Indexed Database API does not rely on any specific platform. In this context, the specification is commonly implemented in all browsers. Indexed Database API: https://www.w3.org/TR/IndexedDB/'
'This is an ISO Publicly Available Specification (PAS). In this context, standards are developed by groups of experts called technical committees. These experts are put forward by ISO’s national members. If a user interested in getting involved, they ought to contact their national standards body. Companies and individuals are not eligible to join ISO as members. ISO Technical committees: https://www.iso.org/get-involved.html ISO Publicly Available Specification (PAS): https://www.iso.org/deliverables-all.html?type=pas#PAS '
'The IPsec protocol, included in the IPv6 specification, guarantees that data is exchanged securely. When IPsec operates in tunnel mode (Gateway-to-Gateway or Gateway-to-Host), the entire IPv6 packet is encrypted and authenticated. Therefore, the data exchanged between public administrations or citizens is protected. Redhat IPsec reference: https://www.redhat.com/en/blog/ipv6-packets-and-ipsec'
The purpose of XHTML is to publish administrative data on the web, as one of the main languages used in web development, XHTML helps and fosters the visibility of administration data and services. Moreover, it also eases the decision-making process by ensuring the data exchange and data reuse. XHTML W3C reference: https://www.w3.org/TR/xhtml1/
'The use of the ESPD can indirectly contribute to the development of digital service delivery channels by reducing administrative burden and increasing efficiency in procurement procedures. This can allow public authorities to invest in the development of digital services and infrastructure, which can in turn enable more efficient and effective delivery of public services through digital channels. ESPD Business handbook: https://docs.ted.europa.eu/ESPD-EDM/latest/xml_business_handbook.html'
'NUTS is intended to serve as a device to identify administrative zones in the EU and beyond the EU borders. There is no possibility of tailoring NUTS coding system, nor any kind of authorising process is allowed, as NUTS was conceived for a unique purpose. EUROSTAT reference, NUTS Principles and Characteristics section: https://ec.europa.eu/eurostat/web/nuts/principles-and-characteristics'
TSL 1.2 has been widely for cryptographic protocol that providing end-to-end security of data sent between applications over the Internet. However TSL 1.3 was created in 2018 which improved many characteristics of the former, consequently it can be said that it is the 1.3 version that is used for the development of products and services.
The purpose of FTP is not related to e-accessibility. Therefore this criterion is considered not applicable to this specification.
'TGF is chartered by the its technical committee at the Organization for the Advancement of Structured Information Standards (OASIS), which is a global consortium that develops and promotes open standards for the Internet. The TGF Technical committee at OASIS works to advance the TGF by developing technical standards and specifications that support its implementation and interoperability with other frameworks and systems. The group also provides a forum for discussion and collaboration among stakeholders who are working on TGF-related projects and initiatives. TGF Technical Committee: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=tgf'
'This specification has been included in a catalogue of cloud computing standardisation projects produced by Portail-Qualité, an initiative by ILNAS that constitutes a network of competencies in the field of quality, security and compliance at the service of competitiveness. Cloud Computing Published Standards: https://portail-qualite.public.lu/content/dam/qualite/publications/normalisation/2020/ans-smart-secure-ict/cloud-computing-standards-projects-V1.pdf'
CAMSS Assessment of WSDL EIF Scenario v1.0.0
The specification was developed by 2004, by OASIS, and has been evolved through different versions. The current version is the 2.0, which is available since the 2007, which demonstrates that it has overcome the possible issues hampering its use and now it is established and used. WS-BPEL OASIS reference: http://docs.oasis-open.org/wsbpel/2.0/OS/wsbpel-v2.0-OS.html OASIS webpage: https://www.oasis-open.org/
FTPS is an extension of the File Transfer Protocol (FTP) that adds support for the Transport Layer Security (TLS) to secure the data exchange. So it is dependant of FTP and TLS versions. FTPS IETF reference: https://tools.ietf.org/html/rfc4217
'Currently the Asset Administration Shell (AAS) is not included in any european catalogue. Details of the Asset Administration Shell (AAS) https://industrialdigitaltwin.org/en/wp-content/uploads/sites/2/2024/06/IDTA-01001-3-0-1_SpecificationAssetAdministrationShell_Part1_Metamodel.pdf'
The Standard is not included in European or National platforms, however, openness and the benefits for the creation of public and reusable solutions is the philosophy of the specification. Besides, it is fully accessible for its consultation, study, implementation or contribution to its development. Therefore, this criterion can be considered positively since the access and purpose is based on transparency and ethical principles. The Standard for Public Code webpage: https://standard.publiccode.net/
'The specification is not related to the publication of public data as open data. Therefore this criterion is not applicable to this specification. ETSI EN 319 532-3 reference: https://www.etsi.org/deliver/etsi_en/319500_319599/31953203/01.02.01_60/en_31953203v010201p.pdf '
'The DCAT specification explicitly mentions a section in its documentation about rights and obligations that can provide an access control mechanism. It can use the properties dcat:rights, dcat:accessRights and dcat:license to provide this access. DCAT (v2.0.0) reference (section 8): https://www.w3.org/TR/vocab-dcat-2/ '
'While the Dataspace Protocol is developed by a European standardisation organisation called IDSA and is widely used, it is not a European Standard in the sense of being developed and published by CEN or CENELEC specifically for the European region. International Data Spaces Association (IDSA): https://internationaldataspaces.org/'
The rules on European standardisation allow the European Commission to identify information and communication technology (ICT) technical specifications - that are not national, European or international standards - to be eligible for referencing in public procurement. This allows public authorities to make use of the full range of specifications when buying IT hardware, software and services, allowing for more competition in the field and reducing the risk of lock-in to proprietary systems. After being evaluated compliant with the regulation on standardisation 1025/2012, XML has been identified by Commission Implementing Decision. See: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en
'While OpenTelemetry itself is not a framework for creating organisational interoperability agreements, it significantly facilitates interoperability by standardising how telemetry data is collected, processed, and shared across different systems and organizations. By adopting OpenTelemetry, organisations can ensure consistent observability practices, seamless integration of monitoring tools, and enhanced collaboration across diverse IT environments. OpenTelemetry: https://opentelemetry.netlify.app/docs/specs/otel/'
XML is publicly available for implementation and study for free on W3C's webpage. See: https://www.w3.org/TR/2006/REC-xml11-20060816/
'The specification is technologically agnostic, is a specification based on YAML focused on the description of solutions, specifically, software. Publiccode.yaml documentation: https://docs.italia.it/italia/developers-italia/publiccodeyml-en/en/master/index.html'
'The specification is included in 7 Member States catalogues of recommended specifications. This Member States are Austria, Croatia, France, Germany, Netherlands, Norway and Sweden. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
'Domibus enables the reuse of relevant information through features like message templates, standardized formats, metadata, integration with backend systems, customization, and real-time communication within its messaging scope. Domibus specification: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/Domibus'
'The specification is excellent for accessing and maintaining distributed directory information services over internet. The main function of LDAP is to help users connect to their IT resources safely, as well as data protection. In this way, LDAP helps ensure data exchange using TLS and SSL mechanisms. It also allows authentication methods and access control lists using SASL and simple bind. Because of this, LDAP is often used in public administrations and has become an staple of the identity management industry. LDAP IETF reference: https://tools.ietf.org/html/rfc4511 SSL cloudfare reference: https://www.cloudflare.com/es-es/learning/ssl/what-is-ssl/ TLS cloudfare reference: https://www.cloudflare.com/learning/ssl/transport-layer-security-tls/ SASL gnu reference: https://www.gnu.org/software/gsasl/manual/gsasl.html#SASL-Overview'
The specification has been developed by European Institutions for its implementation across borders to improve the accountability and development of public policies and laws, the specification can be considered compliant with the different European Regulations. Moreover, one of the main goals of the specification is to foster the consistency and proper development of the general public laws and policies. European Comission Webpage: https://ec.europa.eu/info/index_en Betterr Regulation Toolbox reference: https://ec.europa.eu/info/sites/info/files/better-regulation-toolbox_2.pdf
The purpose of WS-Security is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification.
'The purpose of ESPD is not related to enabling the exposure of interfaces. Therfore this criterion is not applicable to the specification. ESPD Business handbook: https://docs.ted.europa.eu/ESPD-EDM/latest/xml_business_handbook.html'
'Assessments of the efficiency of OpenTelemetry primarily involves evaluating the performance, scalability, and practicality of implementations. A 2024-paper about the development of an OpenTelemetry extension for call graphs. Acall graph is an important feature in the application performance monitoring (APM) domain that helps users diagnose issues within their production applications. The techniques described in the study provide for extending OpenTelemetry agents to automatically collect data required for call graph creation, which highlights the efficiency of the specification. OpenTelemetry Extension for Supporting Call Graphs: https://www.tdcommons.org/dpubs_series/6992/'
SOAP 1.2 is a messaging protocol for exchanging information in a structured way, it uses XML for its message format. As the protocol is a messaging system for exchanging information in a structured way, it helps to promote the visibility and comprehensibility of the administrative rules. In addition, it is a key enabler for web services reuse across borders along with UDDI and WSDL. See: https://www.ibm.com/support/knowledgecenter/en/SSAW57_8.5.5/com.ibm.websphere.nd.multiplatform.doc/ae/cwbs_soapverdiffs.html
'While the E-ARK CSIP does not specifically address personal data protection, it promotes the use of metadata, including administrative metadata, which can include information about access controls, security measures, and data sensitivity. This metadata can assist in documenting and managing the security and privacy aspects of information packages, including personal data, throughout their lifecycle. E-ARK CSIP specification: https://earkcsip.dilcis.eu/#introduction'
'XHTML does not have built-in mechanisms to directly prevent unauthorized changes. Therefore, this criterion is not applicable to the specification. XHTML W3C reference: https://www.w3.org/TR/xhtml1/'
CELLAR is the semantic repository of the Publications Office, and it recognises SHACL as its standard of preference for data validation in the Semantic Web. See: https://publications.europa.eu/en/publication-detail/-/publication/658088eb-c071-11e8-9893-01aa75ed71a1/language-en/format-PDF/source-86108820
The specification can allow public administrations to define XML schemas with semantic bindings for the reuse of information across borders including reference to contracts or other legal documents without requiring the submission or provision more than once. LegalRuleML reference: http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/legalruleml-core-spec-v1.0.html
IETF is a non-profit making organisation. It is large open community of network designers, operators, vendors, and researchers. It is open to any interested individual with the evolution of the Internet architecture and the smooth operation of the Internet._x000D_ See: https://www.ietf.org/rfc/rfc3935.txt
'The purpose of SFIA is not related to enabling digital service delivery channels. Therefore, this criterion does not apply to this specification. SFIA reference: https://sfia-online.org/en/sfia-8'
There are different documentation and information that takes into account EuroVoc as part of the narrative and includes it as valuable. An article shows the usefulness of EuroVoc since it is included as the core of an application for the categorisation of documents (see link below). Also, an example of a use case for the Italian Chamber of Deputies. In here, the use case was presented in a EuroVoc conference to show the result and the effectiveness of using EuroVoc as the basis for the semi-automatic classification of documents. JRC EuroVoc Indexer JEX - A freely available multi-label categorisation tool https://www.researchgate.net/publication/256846257_JRC_EuroVoc_Indexer_JEX_-_A_freely_available_multi-label_categorisation_tool Eurovoc and parliamentary documents: A semi-automatic classification experience at the Italian Chamber of Deputies: https://expertsystem.com/expert-systems-cogito-semantic-platform-to-be-featured-at-eurovoc-conference/
"EN 303 645 is a set of security best practices for Internet-connected consumer devices and is intended to support all parties involved in the development and manufacture of consumer IoT devices. The specification's recommendations (provisions) are intended to depend on any product from the IoT domain, and therefore the specification cannot be considered technology-agnostic. EN 303 645 reference: https://www.etsi.org/deliver/etsi_en/303600_303699/303645/02.01.01_60/en_303645v020101p.pdf"
"Schema.org is a (structured data) mark-up schema that helps search engines understand the information on web pages and potentially provides richer search results. Therefore, the specification addresses data portability. In future scenarios, DCAT-AP-SDO (Schema.org profile of DCAT Application Profile for Data Portals in Europe) will potentially replace the common European DCAT Application Profile for Data Portals in Europe (DCAT-AP), which aims to enable data portability between information systems in the EU. Schema.org homepage reference, 'About Schema.org' section: https://schema.org/docs/about.html DCAT-AP-SDO reference: https://ec-jrc.github.io/dcat-ap-to-schema-org/ DCAT-AP reference: https://op.europa.eu/en/web/eu-vocabularies/dcat-ap"
'The purpose of HTTPS is not related to the delivery of multilingual European public services. Therefore this criterion is considered not applicable specification. HTTPS specification: https://tools.ietf.org/html/rfc2818'
'OAIS foresees access control mechanisms to restrict access to digital information. The model includes the concept of "user community" which refers to a set of users who are authorized to access the digital information managed by the archive. The model specifies that the archive should establish access control policies and procedures to ensure that only authorized users can access the digital information. OAIS specification: https://public.ccsds.org/Pubs/650x0m2.pdf'
'The specification is a protocol focused on the transaction of data. Even though it is related to data exchange, and it is aimed to ensure the delivery of data, it is not involved in data portability amongst systems fostering the European Public Services implementation and evolution. SMP OASIS reference: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505009'
'The specification has not been included in any initiative at European or National level covering privacy aspects. LDES specification: https://joinup.ec.europa.eu/collection/semic-support-centre/linked-data-event-streams-ldes'
The ISO 14533-3:2017 which refers to PAdES is not available for free for everyone to study. Payment is needed to reach access to the standard. PAdES ISO reference: https://www.iso.org/standard/67937.html
HTTP is publicly available for implementation and use for free on IETF's webpage. See: https://tools.ietf.org/html/rfc2616
DCAT-AP is Licensed on a royalty-free basis under the European Union Public License (EUPL). See: https://administracionelectronica.gob.es/ctt/dcatap/abstract#.XbFndZozY2w https://joinup.ec.europa.eu/sites/default/files/custom-page/attachment/eupl_v1.2_en.pdf
'DNS is widely used for EU cross-border projects. For instance, it is used by TESTA, the data communication network service operated by the European Commission. TESTA Overview & Service Catalogue https://ec.europa.eu/isa2/sites/default/files/testa_-_20_years_isa_2_web_page_-_01_2021.pdf'
'There are many extensions that can be implemented within the DNS standard protocol. Many of this extensions address security issues, while others are centered on its conformance testing or its integration in a broader framework. Extension Mechanisms for DNS: https://datatracker.ietf.org/doc/html/rfc6891'
'Yes, the specification is mapped to Ontology ABB semantic layer. DCMI About: https://www.dublincore.org/about/ ELIS: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/v500'
'ETSI TS 119 512 is a component derived from the actions implemented on the basis of the Regulation (EU) No 910/2014 of the European Parliament and of the Council of 23 July 2014 on electronic identification and trust services for electronic transactions in the internal market. The aim of this regulation is to enhance interoperability when it comes to trust services of e-signatures in the European context. Regulation (EU) No 910/2014 of the European Parliament and of the Council of 23 July 2014 on electronic identification and trust services for electronic transactions in the internal market: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv:OJ.L_.2014.257.01.0073.01.ENG'
"There are assessments that indirectly address the specification's effectiveness. For instance, this paper provides an overview of existing literature and reviews current open-source dataspace connector implementations that are compliant with the International Data Spaces (IDS) standard. By using this IDS standard, they are indirectly demonstrating its relevancy and effectiveness. A Survey of Dataspace Connector Implementations: https://arxiv.org/pdf/2309.11282.pdf"
The LegalDocumentXML Specs provides a common legal document standard for the specification of parliamentary, legislative and judicial documents, for their interchange between institutions anywhere in the world and for the creation of a common data and metadata model that allows experience, expertise, and tools to be shared and extended by all participating peers, courts, Parliaments, Assemblies, Congresses and administrative branches of governments. The specification is publicly available at OASIS webpage. LegalDocML reference: https://www.oasis-open.org/committees/legaldocml/charter.php
'The ebXML specification describes a set of security features of ebXML RegRep and incorporates different specifications to enable the secure exchange of data. For example, ebXML incorporates the WS-Security Core Specification (v1.1), which supports confidentiality of all ebXML RegRep protocols defined by this specification when those protocols are bound to SOAP. ebXML reference: http://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html ebXML RegRep Part 2: http://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-rs-v4.0-os.html#__RefHeading__32703_422331532'
'DNS has some core functionalities that can not be be implemented separately. Nonetheless, the specification has beed developed to support some requirements that are not mandatory but recommended. DNS IETF reference: https://tools.ietf.org/html/1034 Domain Names - Implementation and Specification: https://tools.ietf.org/html/1035 '
'The objective of ELI does not pertain to the modeling of business processes. Therefore, this criterion is not applicable to the specification. ELI reference: https://eur-lex.europa.eu/eli-register/about.html'
The FTP is published as a reusable solution in Joinup, the collaborative platform for Reusable IT Solutions funded by the European Commission. See: https://joinup.ec.europa.eu/solution/file-transfer-protocol/distribution/file-transfer-protocol
'The fact that there are mechanisms to ensure that only certain users can upload or modify a data record guarantees the secure processing of the data. In addition, it is possible to digitally sign and UDDI entities can use it to give more confidence in the data. IBM security reference: https://www.ibm.com/docs/en/was/9.0.5?topic=services-overview-version-3-uddi-registry'
ETSI has provided a conformance testing tool for electronic signatures according to the European Commission Mandate 460. The conformity testing tool involves different standards applied in the development of eSignatures, including CAdES baseline profile. See: https://signatures-conformance-checker.etsi.org/pub/CAdESConformanceTestChecker_v1.0.pdf https://signatures-conformance-checker.etsi.org/pub/index.shtml
'The specification was formally defined between 2015 and 2017 with the experience and the expertise of the Member States that were closely working together to consolidate the guidelines. In this sense, the Regulatory Scrutiny Board has published in their annual reports the evolution of the Better regulation framework implementation in terms of the quality derived from other pieces of legislation. This fact demonstrates that both guidelines and toolbox have been agreed as relevant instruments, therefore being mature enough for its use elsewhere. Regulatory board reports: https://commission.europa.eu/law/law-making-process/regulatory-scrutiny-board_en#annual-reports Better Regulation Guidelines and Toolbox reference: https://commission.europa.eu/law/law-making-process/better-regulation/better-regulation-guidelines-and-toolbox_en Better Regulation Guidelines reference: https://commission.europa.eu/document/download/d0bbd77f-bee5-4ee5-b5c4-6110c7605476_en?filename=swd2021_305_en.pdf Better Regulation Toolbox reference: https://commission.europa.eu/document/download/9c8d2189-8abd-4f29-84e9-abc843cc68e0_en?filename=BR%20toolbox%20-%20Jul%202023%20-%20FINAL.pdf'
'Organizations like the Cloud Standards Customer Council (CSCC) and the Object Management Group (OMG) are involved in the development and promotion of cloud standards, including ISO/IEC 19941. These groups work with various stakeholders to influence standards development and advance the adoption of cloud computing. OMG: https://www.omg.org/cloud/deliverables/CSCC-Interoperability-and-Portability-for-Cloud-Computing-A-Guide.pdf'
'8 Member States are recommending UDDI in their ICT National Catalogues. This Member States are Bulgaria, Cyprus, France, Germany, Greece, Malta, Netherlands and Spain. Joinup catalogue: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
'EN 16234-1 e-CF provides a reference framework for the ICT workforce and contributes inter alia to the adoption of the Shaping Europe's digital future approach (see CEN/TC 428 "ICT Professionalism and Digital Competences" Business Plan 2022 reference, section 1.4). Digital transformation sets out actions to the development of digital public services. CEN/TC 428 "ICT Professionalism and Digital Competences" Business Plan 2022 reference, section 1.4: https://standards.cencenelec.eu/BPCEN/1218399.pdf Shaping Europe's digital future reference: https://ec.europa.eu/info/strategy/priorities-2019-2024/europe-fit-digital-age/shaping-europe-digital-future_en'
'When XHTML became a W3C recommendation, it was well accepted, but with the introduction of HTML5, its usage has significantly declined. The following link provides a comparison of the usage of various HTML languages, showing that XHTML 1.0 is increasingly in decline, while HTML5 continues to rise. HTML vs XHTML version statistics: https://www.powermapper.com/blog/html-vs-xhtml-version-statistics/'
One of the tools provided by the specification is focused on evaluating if the needs of a new proposal require any ICT aspect that can be foreseen and adapted to the most efficient manner, ensuring that the new proposal fits its needs and at the same time the process is efficient. Having said this, it is worth noting that the purpose of the specification is not related to the business process definition, and therefore, this criterion does not apply to the specification. Betterr Regulation Toolbox reference: https://ec.europa.eu/info/sites/info/files/better-regulation-toolbox_2.pdf
'The specification is excellent for accessing and maintaining distributed directory information services over internet. The main function of LDAP is to help users connect to their IT resources safely. Because of this, they are often used in public administrations and have become staples of the identity management industry. LDAP IETF reference: https://tools.ietf.org/html/rfc4511'
SHACL is publicly available for implementation and use for free on Github. Also, TopQuadrant developped a service available for free in Javascript allowing the use of SHACL features for free. See: https://github.com/w3c/data-shapes http://shacl.org/playground/
'There are already existing documents and studies assessing WSDL performance and its features. The main topic are efficiency while discovering, automatic classification of web services or the poor query results. Improving Web Service descriptions for effective service discovery: https://core.ac.uk/download/pdf/82569095.pdf Towards Effective Service Discovery using Feature Selection and Supervised Learning Algorithms: https://thesai.org/Downloads/Volume10No5/Paper_25-Toward_Effective_Service_Discovery.pdf'
'Although ADMS’s purpose is not the long-term preservations, it can be used to document and store semantic assets. ADMS on Joinup: https://joinup.ec.europa.eu/solution/asset-description-metadata-schema-adms/about ADMS Specification W3C: https://www.w3.org/TR/vocab-adms/'
'There are already existing studies and documents assessing and documenting YAML features, which can help to discover how the specification can be efficient. Speciffically, the paper "YAML: A tool for hardware design visualization and capture" helps to understand how YAML can be used for achieve complex targets using YAML only. This paper describes an approach that helps to capture the structural aspects of a design at a high level of abstraction and enables the system designer to enter designs "schematically" using predefined structural and functional entities conforming to UML notation. "YAML: A tool for hardware design visualization and capture": https://ieeexplore.ieee.org/abstract/document/874023'
'SHACL enhances the semantic and technical interoperability of ontologies expressed as RDF (Resource Description Framework) graphs, which is a European Standard used by public administrations. By ensuring data validation through SHACL, DCAT-AP (Data Catalogue Application Profile) facilitates the description of public sector datasets, making them easily searchable across borders and sectors. This interoperability and searchability enable public administrations to expose interfaces for accessing their services more effectively, as seen in initiatives like the Open Data Support service by the European Commission. DCAT-AP specification reference: https://interoperable-europe.ec.europa.eu/collection/semic-support-centre/solution/dcat-application-profile-data-portals-europe SHACL W3C reference: https://www.w3.org/TR/shacl/'
'The SMP 2.0 specification developed by OASIS does not explicitly address the protection of information against unauthorized changes. SMP OASIS reference: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505009'
'IPsec is a set of open standards and protocols for securing the exchange of data packets over a computer network. Therefore, it ensures the secure and trustworthy data exchange between different stakeholders. IPSec reference, Where Can IPSec Be Implemented: https://datatracker.ietf.org/doc/html/rfc4301#page-11'
The purpose of LegalDocMC is not related to the publication of public data as linked open data. Therefore, this criterion is not applicable to this specification. LegalDocML reference: https://www.oasis-open.org/committees/legaldocml/charter.php
'There has not been found any assessment addressing the effectiveness of Domibus implementations. Domibus specification: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/Domibus'
'EIRA covers all LOST views, which means from legal requirements to how technically are there implemented. In relation to the availability of interfaces, the specification can be key, as it the first step to identify what should solutions include in terms of data and functional requirements. They have to be aligned from legal to technical aspects. In this sense, EIRA can help to provide different mechanisms to access and use these digital public services from these different perspectives as they are the end-user or the public organisations internally. EIRA reference: https://interoperable-europe.ec.europa.eu/collection/european-interoperability-reference-architecture-eira /solution/eira/release/610 EIRA Github Repository: https://github.com/CarTool-EC/EIRA '
'The Better Regulation Guidelines and Toolbox acknowledges the relevance of Open Data in the development of public policies. However, it does not provide extensive recommendations regarding the means of publishing data on the web (Tool #4 and #28 provide recommendations on integrating systems using open data), nor does it exclude the use of proprietary software, in line with DIRECTIVE (EU) 2019/1024 on open data and the re-use of public sector information. Better Regulation Guidelines and Toolbox reference: https://commission.europa.eu/law/law-making-process/better-regulation/better-regulation-guidelines-and-toolbox_en Better Regulation Toolbox reference: https://commission.europa.eu/document/download/9c8d2189-8abd-4f29-84e9-abc843cc68e0_en?filename=BR%20toolbox%20-%20Jul%202023%20-%20FINAL.pdf DIRECTIVE (EU) 2019/1024 on open data and the re-use of public sector information: https://eur-lex.europa.eu/eli/dir/2019/1024/oj/eng'
'The OASIS UDDI Specification Technical Committee in charge of the development of UDDI, operates under RF on RAND Mode of the OASIS IPR Policy. The specification is licensed on a Royalty-free and (F)RAND basis. Intellectual Property Rights (IPR) Policy: https://www.oasis-open.org/policies-guidelines/ipr Oracle OASIS UDDI Intellectual Property Disclosure: https://www.oasis-open.org/committees/uddi-spec/ipr.php'
'The GraphQL specification does not give any provisions for the management and protection of personal data, but there are some best practices that can be adopted to tackle this issue, that may come from the server side. GraphQL specifciation: https://spec.graphql.org/October2021/#sec-Overview'
'While the core specification is not customisable, there are aspects of its implementation and configuration that can be tailored to meet specific needs. IPv6 customisation: https://www.rfc-editor.org/rfc/rfc2460#section-4'
'The Dublin Core element set defines a set of metadata elements for cataloging library items and other electronic resources. Such items are known as "resources", and there exist certain relationships (Dublin Core calls these relationships "elements") between resources and other resources or data. DCMI Webpage: https://www.dublincore.org/about/ '
The purpose of MIME is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification. MIME reference: https://tools.ietf.org/html/rfc2045
'There are existing documentation and studies assessing the efficiency of SHACL. In "A Review of SHACL: From Data Validation to Schema Reasoning for RDF Graphs", the SHACL efficiency is assessed. In this study, different formal frameworks used to study this language and the various proposed semantics are reviewed. Moreover, practical aspects of SHACL are covered, discussing its implementations and state of adoption. "A Review of SHACL: From Data Validation to Schema Reasoning for RDF Graphs" study: https://link.springer.com/chapter/10.1007/978-3-030-95481-9_6 SHACL W3C reference: https://www.w3.org/TR/shacl/'
The purpose of TLS 1.2 is not related to e-accessibility. Therefore this criterion is considered not applicable to this specification.
'TGF is already mapped to the EIRA Library of Interoperability Specifications (EIRA). More specifically, TGF covers the Shared Governance Framework, Digital Governance, Digital Public Service Delivery, and Interoperability Framework from the Organisational view. TGF specification: http://docs.oasis-open.org/tgf/TGF/v2.0/cs01/TGF-v2.0-cs01.html'
The fact that the specification has been adopted by different organisations and initiatives demonstrates that the specification has sufficient completeness and consistency for the use and development of products and services. Additionally, the specification is easy to use, flexible and not bound to a particular business domain.
'The Dataspace Protocol is part of both private and public innovative solutions. As for private, it is included in the "Building data spaces for sustainability use cases" section of Amazon Web Services Prescriptive Guidance, which provides time-tested strategies, guides, and patterns to help accelerate cloud migration, modernization, and optimization projects. Regarding public initiatives, the Dataspace Protocol is mentioned in the making of Road-X, a robust and secure solution to exchange data and establish a collaborative ecosystem developed by the Nordic Institute for Interoperability Solutions (NIIS). It streamlines data exchange processes, enhances security, and facilitates interoperability, enabling organisations to derive greater value from their data assets. AWS Prescriptive Guidance: https://docs.aws.amazon.com/prescriptive-guidance/latest/strategy-building-data-spaces/dataspace-protocol.html NIIS Making of X-Road 8 - PoC: https://www.niis.org/blog'
'Taking the initial purpose of the specification, which is to reduce the cost and complexity of user management operations by providing a common user schema, an extension model, and a service protocol, it can be considered that the specification is indirectly involved in fostering the comprehensibility of Public Administrations data as well as relevant data produced for the decision-making process. SCIM: https://scim.cloud/'
After searching in the different official European websites, there is no evidence of any cross-border project that uses Xforms nor explicit agreements involving the usage of the specification.
As a business domain agnostic specification, FTP, can be used for the exchange of documents addressing any domain.
EuroVoc was developed for the first time in 1982 and has de full support from the European Union, since it was developed to support and help European and National institutions on their functions. The taxonomy categorises knowledge domains close to the European Institution. Therefore, it can be considered with market acceptance at eGovernment level for the development of products and services. EuroVoc over the time: https://op.europa.eu/es/web/eu-vocabularies/th-dataset/-/resource/dataset/eurovoc?target=About#Time Eurovoc: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/eurovoc
After checking the different standard catalogues at supra-national level, there is no evidence of the inclusion of CLV within any European catalogue of standards. ICT technical specifications: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en CEN search tool catalogue: https://standards.cen.eu/dyn/www/f?p=CENWEB:105::RESET:::: CENELEC search tool catalogue: https://www.cenelec.eu/dyn/www/f?p=104:107:0::::FSP_LANG_ID:25
'XSLT specification is designed to be technology-agnostic, focusing on data transformation and manipulation without being tied to any specific platform. (See Section 2.9) XSLT Reference: https://www.w3.org/TR/xslt-30/#extensibility'
'Currently Microsoft has provided some insights regarding the specification efficiency, but while it is implemented with other specifications, in this case via Microsoft network drivers. OSI and Microsoft https://learn.microsoft.com/en-us/windows-hardware/drivers/network/windows-network-architecture-and-the-osi-model OSI reference https://www.iso.org/standard/20269.html'
'Although HTTPS is not directly related to the reuse of information, in some cases, cache content over HTTPS can provide a mean to reuse information, but not in a consitent manner. HTTPS specification: https://tools.ietf.org/html/rfc2818'
'The application of the once-only principle in all EU Member States public administrations aims at reducing the administrative burden. This Core Vocabulary fosters interoperability between public administrations, cross border services and impacts positively the development of eGovernment. CPSV-AP Joinup webpage: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/core-public-service-vocabulary-application-profile/release/22'
'ShEx is built around RDF and is highly dependent from it since its purpose is to validate RDF graphs. Nonetheless, it has many known implementations that range through a variety of business domains allowing for RDF graphs validation across business domains. ShEx primer document: https://shexspec.github.io/primer/ ShEx Community Group: https://www.w3.org/community/shex/ ShEx Github: https://github.com/shexSpec/spec/issues '
'The ELI system does not inherently ensure or enable data processing accuracy. Therefore, this criterion is considered not applicable to this specification. ELI reference: https://eur-lex.europa.eu/eli-register/about.html'
'DAPS can typically be extended to meet specific organizational needs and requirements. The extensibility of such services allows organizations to adapt the provisioning system to their unique workflows, attribute types, and integration points. For instance, it is possible to extend custom attribute types beyond standard ones. DAPS: https://github.com/International-Data-Spaces-Association/IDS-G/tree/main/Components/IdentityProvider/DAPS'
'There has been found some studies assessing the efficiency of PROV. Among some of the studies, we can find one assessing the data provenance on the web of data, or another testing the PROV encoding with social science data. Measuring PROV provenance on the web of data: http://provenanceweek.org/2016/p3yl/papers/paper_89.pdf Encoding Provenance of Social Science Data: Integrating PROV with DDI: https://ddialliance.org/encoding-provenance-of-social-science-data-integrating-prov-with-ddi-0 '
JSON allows the data exchange and consumption from different administrations stakeholders. Ensuring data exchange through applications avoids the interaction by means of reducing the non-digital data exchange. Therefore, the adoption of JSON eases the reduction of administrative burden.
'The purpose of this Core Vocabulary is not included in any initiative at European or National level covering privacy aspects. Therefore, this criterion is considered not applicable to this specification. Core Criterion and Core Evidence Vocabulary reference (v1.0.0): https://joinup.ec.europa.eu/release/core-criterion-and-core-evidence-vocabulary-v100 '
'Understanding data exchange as the publication by the administration of data for its later consumption by citizens, the specification facilitates the trustworthy data exchange in RDF format by providing the means to validate RDF data graphs. ShEx primer document: https://shexspec.github.io/primer/ ShEx Community Group: https://www.w3.org/community/shex/ ShEx Github: https://github.com/shexSpec/spec/issues '
'DIDs is used in Self-sovereign identity (SSI) in eIDAS project. Self-sovering identity is the next step beyond user-centric identity. Moreover, DIDs is currently being implemented in dataspaces initiatives, which evidences its use in the development of innovative solutions. Data spaces reference: https://www.linkedin.com/pulse/what-data-space-dr-antonio-j-jara-sztrf SSI eIDAS: https://joinup.ec.europa.eu/collection/ssi-eidas-bridge'
'The specification focuses on the reuse of software from public administrations, but not data. Even though public services and software can be planned and implemented to foster and support the once only principle, the specification being analysed is does not focuses on that aspect. Publiccode.yaml documentation: https://docs.italia.it/italia/developers-italia/publiccodeyml-en/en/master/index.html'
'The DCAT specification uses the PROV specification that can explicitly address and ensure the data processing accuracy. PROV specification Reference: https://www.w3.org/TR/prov-overview/ DCAT (v2.0.0) reference: https://www.w3.org/TR/vocab-dcat-2/ '
'The purpose of RDF is not related to e-accessibility. Therefore this criterion is considered not applicable to this specification. RDF primer document: https://www.w3.org/TR/rdf11-primer/'
The ISO specifications are published to be able to respond to a market need which represent a consensus of an expert group. It was launched initially by Adobe in 1993 as a proprietary solution but free of charge. In July 1st, 2008 PDF became an Open Standard published by ISO. In addition, PDF is highly adopted as a document format for exchange information, which is technological independent. These facts demonstrate the maturity and market acceptance for its use in the development of products and services.
'The specification is not included per se in any supra-national catalogue. Despite this, SOAP 1.2 is part of the Electronic Signatures and Infrastructures (ESI); Rationalized framework of Standards for Electronic Registered Delivery Services Applying Electronic Signatures, which is an ETSI Special Report. ETSI SR 019 050 Reference where SOAP is included: https://www.etsi.org/deliver/etsi_sr/019000_019099/019050/01.01.01_60/sr_019050v010101p.pdf'
The specification has been creation to exchange information through the internet, it has not security layer. The extension of HTTP; HTTPS, uses other protocols for securing communications.
There are different documentation and studies related to the use of LegalDocML. An example is "Evaluating LegalDocML and LegalRuleML as a Standard for Sharing Normative Information in the AEC/FM Domain analyses the LegalDOCML specification" Evaluating LegalDocML and LegalRuleML as a Standard for Sharing (...): https://www.researchgate.net/publication/318010726_Evaluating_LegalDocML_and_LegalRuleML_as_a_Standard_for_Sharing_Normative_Information_in_the_AECFM_Domain
'The purpose of the specifications is not related to the comprehensibility of administrative information, data or services. Therefore, this criterion is not applicable to this specification. TSP IETF reference: https://tools.ietf.org/html/rfc3161'
'One of the supporting documents of this specification is ETSI GR CIM 007, which identifies the security and privacy aspects that are relevant when building systems based on the NGSI-LD API and the NGSI-LD information model. In this case, the use of secure enclaves is mentioned when talking about data processing. ETSI Context Information Management (CIM); Security and Privacy: https://www.etsi.org/deliver/etsi_gr/CIM/001_099/007/01.01.02_60/gr_cim007v010102p.pdf'
"TLS 1.3 offers a foundational level of access control by focusing on peer authentication. This means it verifies the identities of the server and, optionally, the client, ensuring they are who they claim to be. This verification is done using certificates (digital documents issued by trusted authorities that link a public key to an identity) or pre-shared keys (PSKs) (secret keys shared beforehand between the communicating parties). It's important to know that these mechanisms are for authentication only, confirming who is communicating, and not for data encryption. Therefore, TLS 1.3 itself does not control what actions a user can perform or what resources they can access. TLS 1.3 Resumption and Pre-Shared Key Reference: https://www.rfc-editor.org/rfc/rfc8446.html#section-4.2.9 TLS 1.3 Certificates and Authentication Reference: https://www.rfc-editor.org/rfc/rfc8446.html#appendix-C.2"
'Although the specification has been implemented in some projects at European level, there is no evidence of the inclusion of schema.org in an open repository/catalogue of standards at European level. EUOS repository of standards: https://www.standict.eu/standards-repository CENELEC and CEN search tool catalogue: https://standards.cencenelec.eu/dyn/www/f?p=CEN:105::RESET::::'
CPSV-AP is independent of any software, hardware, or operating system. So it can be said that the specification is independent of any specific technology or platform. CPSV-AP reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-service-vocabulary-application-profile
There are existing documentation and studies assessing the effectiveness and efficiency of LDAP. It is a comparison between LDAP 2 and LDAP 3. As well, the study shows the improvement of the different versions over time as resulting in more efficient protocol. Difference between LDAP2 and LDAP3: https://docs.microsoft.com/en-us/previous-versions/windows/desktop/ldap/differences-between-ldap-2-and-ldap-3
'The purpose of ISO 639-2 is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification. ISO 369-2 FAQs: https://www.loc.gov/standards/iso639-2/faq.html#5'
'The OGC TrainingDML-AI standard is available under the OGC Community Standard License, which allows for free use, modification, and distribution of the standard. There are no restrictions or royalties associated with the use of the standard. However, the OGC Community Standard License does not apply to any software or other implementations of the standard. OGC Community: https://www.ogc.org/about-ogc/community/ OGC Policies reference: https://www.ogc.org/about-ogc/policies/ipr'
'The six architectural constraints of REST emphasize the scalability of interactions between components, uniform interfaces, independent deployment of components and the creation of layered architecture to allow its implementation across business domains. REST reference: https://restfulapi.net/ '
'After checking the different standard catalogues at supra-national level, there is no evidence of the inclusion of XHTML within any European catalogue of standards. ICT technical specifications: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en CEN search tool catalogue: https://standards.cen.eu/dyn/www/f?p=CENWEB:105::RESET:::: CENELEC search tool catalogue: https://www.cenelec.eu/dyn/www/f?p=104:107:0::::FSP_LANG_ID:25'
'Genericode can facilitate the publication of data on the web by providing a standardised format for representing code lists. It defines a structured W3C XML Schema format for representing code lists. This structured format makes it easy to encode code lists in a machine-readable form, which is essential for publishing data on the web. Code List Representation (genericode): https://docs.oasis-open.org/codelist/genericode/v1.0/os/genericode-v1.0-os.html'
'After checking the SFIA Foundation homepage, there is no reference to (F)RAND values in the available documentation. SFIA reference, Choosing a licence: https://sfia-online.org/en/licensing-sfia/choosing-a-licence'
IPv6 is publicly available for implementation and use, and therefore for everyone to study, for free on IETF webpage. See: https://tools.ietf.org/html/rfc2460
'DNS over HTTPS (DoH) allows for customisation but the extent of customisation may vary depending on the DNS resolver or client software being used. For instance, ssers and administrators can choose the specific DNS resolver that supports DoH. In addition, users can also specify the URLs of the DoH servers they want to use, allowing flexibility in choosing service providers. DoH specification: https://datatracker.ietf.org/doc/html/rfc8484'
'Time Stamp Authority guarantee that the data has not been subjected to any form of unauthorized modification, thereby ensuring the integrity of the information in question. While TSP is a tool that can enhance data integrity and provide audit trails, it primarily helps in detecting unauthorized changes rather than preventing them. For comprehensive protection, it should be integrated into a broader security framework that includes preventive, detective, and corrective controls. Emudhra TSP reference: https://emudhra.com/blog/what-is-timestamping TSP/TSA IETF reference: https://www.rfc-editor.org/rfc/rfc3161'
'According to the 5 star Open Data model suggested by Tim Berners-Lee about how to publish linked data, the second star corresponds to the availability of data as structured data. ebXML is a standard that proposes an XML-based infrastructure enabling the user to store data in a structured manner. In addition, this specification has been established as an open standard. Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/en/ ebXML open standard: https://www.oasis-open.org/2023/02/23/oasis-ebxml-repreg-v4-0-approved-as-international-standard/ ebXML RegRep OASIS reference: https://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html'
'The CPOV, with its links between organizations, their departments and their responsibilities, structures the different relations and thereby spot similarities, duplications of effort or gaps in the system. Comparisons can also be made across borders so that potential efficiencies can be more easily identified. Therefore, with this function it is possible to have data sets with accuracy data. However, monitoring by public administrations is necessary to ensure that the published data is completely accurate. CPOV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-organisation-vocabulary'
The purpose of LegalDocML is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification. LegalDocML reference: https://www.oasis-open.org/committees/legaldocml/charter.php
'The purpose of FTP is not related to ensuring and enabling data processing accuracy. Therefore this criterion is considered not applicable to this specification. FTP Specification Reference: https://datatracker.ietf.org/doc/html/rfc959'
'OData promotes the sharing of data and results, and begs for its approval as an ISO/IEC Standard to help accelerate the specification adoption throughout the international community, particularly within government agencies. In this sense, the specification encourages both the creation of communities and the sharing of their data and results on European platforms. OData referenece, data exchange: https://www.oasis-open.org/news/pr/iso-iec-jtc-1-approves-oasis-odata-standard-for-open-data-exchange/'
'XML is a de-facto standard markup language that is used in a wide variety of solutions, including innovative solutions. See: https://www.w3.org/TR/2006/REC-xml11-20060816/'
'There has not explicitly been found any community sharing their data and results about the implementation of PROV. However, the fact that it is a widely citated specification in scholar papers, and it is also being used as the basis for the development of solutions, gives a glance of its popularity and usefulness, which in turn translates to the creation of communities implementing and discussing the standard. PROV Scholar citations: https://typeset.io/papers/prov-overview-an-overview-of-the-prov-family-of-documents-3hp1wrtnan DCMI Metadata Provenance Task Group: https://www.dublincore.org/groups/provenance/ The W3C PROV family of specifications for modelling provenance metadata: https://dl.acm.org/doi/abs/10.1145/2452376.2452478 '
'ODRL has been selected for a European H2020 project called SPECIAL which aims to use ODRL to validate GDPR compliance of Legislation being produced. Its use has also been implemented within SERAMIS a project which extended ODRL for the validation of GDPR aspects. SERAMIS: https://cordis.europa.eu/docs/projects/cnect/2/612052/080/deliverables/001-D55v4GDPR.pdf SPECIAL Deliverable: https://www.specialprivacy.eu/images/documents/SPECIAL_D17_M17_V10.pdf Representing Activities associated with Processing of Personal Data and Consent using Semantic Web for GDPR Compliance: https://harshp.com/research/publications/035-representing'
'DoH is not included in any national catalogue of recommended specifications whose Member State NIF has a high performance on interoperability according to the NIFO factsheets. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards 2023 NIFO factsheets: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public-administration-factsheets-2023'
'DNS over HTTPS (DoH) is the foundation for many different innovative solutions. For instance, BIND 9 by the Internet Systems Consortium (ISC). BIND (9.17.10) comes with initial support for DNS-over-HTTPS (DoH). Deployment of DoH is also a significant stepping stone for wider adoption of the Encrypted Client Hello (ECH) and Encrypted Server Name Indication (ESNI) features of the Transport Layer Security (TLS) protocol. These features further improve users’ privacy by preventing third parties from snooping, and by making it harder to block websites by analysing and intercepting TLS handshake requests. ISC DoH in BIND 9: https://www.isc.org/blogs/bind-implements-doh-2021/ Transport Layer Security (TLS) Protocol RFC 8446: https://www.rfc-editor.org/rfc/rfc8446'
'UTF-8 encoding can enable digital service delivery channels by supporting multiple languages and scripts, simplifying data processing and exchange, and improving accessibility for users who speak different languages. UTF-8 specification: https://datatracker.ietf.org/doc/html/rfc3629'
'The XSD specification contributed to enabling digital service delivery channels by contributing to the XML Europass 3.0 channels which is the final release for describing the domain of infromation for a learner. XSD Reference: https://www.w3.org/TR/2012/REC-xmlschema11-1-20120405/ Europass XML Schema 3.0 Reference: https://joinup.ec.europa.eu/collection/employment-and-working-conditions/solution/europass-xml-schema-v30/about'
"The purpose of LDAP is not related to the exposure of interfaces to access the public administration's services. Therefore, this criterion is not applicable to this specification. LDAP IETF reference: https://tools.ietf.org/html/rfc4511"
'Public services can offer authentication APIs that accept DIDs and verifiable credentials (VCs) to verify user identity. Moreover, Decentralized Identifiers allow one to discover the location of an authoritative public master data record of an entity. This mechanism can be used for organizations like public administrations. DIDs W3C: https://www.w3.org/TR/did-core/ DIDs use cases: https://www.w3.org/TR/did-use-cases/#crossPlatform'
'The specification builds on standards that are integrated within the ISO OSI model (ISO/IEC 7498-1:1994), whose purpose is to define interactions between information systems and describing how to implement it in an unambiguous and extensible way. IDSA Dataspace Protocol Specification: https://docs.internationaldataspaces.org/ids-knowledgebase/v/dataspace-protocol/overview/readme ISO/IEC 7498-1:1994: https://www.iso.org/standard/20269.html?browse=tc'
The specification protects in itself data integrity, but also provides capabilities to protect with passwords and user roles in order to the access to the document. Therefore, ODF provides security features that foster a trustworthy data exchange between administration and stakeholders. ODF ISO reference: https://www.iso.org/standard/66363.html ODF OASIS reference: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office
'Unauthorised changes are covered by the "Traceablity" dimension, which is part of the "Inherent and System-Dependent Data Quality" category. Integrity involves ensuring that data is accurate, consistent, and has not been altered in unauthorized ways. By using DQV to describe and communicate the integrity measures applied to a dataset, organizations can help ensure that the data remains secure throughout its lifecycle. Data Quality Vocabulary: quality dimensions: https://www.w3.org/TR/vocab-dqv/#DimensionsOfISOIEC25012'
'According to the 5 star Open Data model suggested by Tim Berners-Lee about how to publish linked data, the first star corresponds to publication of data under open license. OCSP describes the data to be used between an application that checks the status of one or more certificates and the server that provides the corresponding status. As a consequence, this specification supports the publication of data as open data. OCSP reference, section 2: https://datatracker.ietf.org/doc/html/rfc2560#section-2 Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/en/'
'The holistic approach of the specification ensures that there is a translation between legal requirements into the technical implementations. In the context of public administrations and the services they provide, the long-term preservation is sometimes subject to strict legal requirements. EIRA allows Public Administrations to identify the needs that will be needed at organisational, semantic, and technical to achieve the long-term preservation in the provision of services. Even it is not implementing in it self a feature saving files, EIRA plays a key role on identifying the requirements and components needed. EIRA reference: https://interoperable-europe.ec.europa.eu/collection/european-interoperability-reference-architecture-eira /solution/eira/release/610 EIRA Github Repository: https://github.com/CarTool-EC/EIRA'
'The purpose of XML is not related to the long-term preservation of electronic records and other kinds of information. Therefore, this criterion is not applicable to the specification.'
SVG is included in 4 national catalogues of recommended specifications. They belong to Estonia, the Netherlands, Spain and Sweden. The National Interoperability Framework (NIF) of these Member States is fully aligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. CAMSS List of Standards https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards NIFO FactSheets: https://joinup.ec.europa.eu/collection/national-interoperability-framework-observatory-nifo/nifo-factsheets
'The purpose of OAS is not related to e-accessibility, therefore, this criterion is not applicable to the specification. OAS specification: https://spec.openapis.org/oas/latest.html#openapi-specification OAS in Github: https://github.com/OAI/OpenAPI-Specification/#participation'
The specification has been selected within the scope of LEOS project to develop the LEOS software, which aims to ease the drafting and edition of legal documents. Moreover, LegalDocML has been included within the European Commission's Rolling Plan for ICT Standarisation and in the related standardisation activities of the same report. LEOS: https://joinup.ec.europa.eu/collection/justice-law-and-security/solution/leos-open-source-software-editing-legislation The European Commission includes in its Rolling Plan for ICT Standarisation: https://ec.europa.eu/digital-single-market/en/rolling-plan-ict-standardisation
Ogg is maintained and developed by XIPH. All standards developed by XIPH have a mirror copy in IETF webpage which is an international community developing open standards. Ogg XIPH reference: https://xiph.org/ogg/doc/rfc3533.txt Ogg mirror copy in IETF: https://tools.ietf.org/html/rfc3533 Developer community IETF: https://www.ietf.org/about/
'HTTP is more focused on how data is transferred over the web by using a request response functions between servers and clients, the specification itself does not scope comprehensibly administrative procedures, rules data, and services. Therefore, this criterion is not applicable to the specification. HTTP /1.1 RFC 2616 Reference: https://www.rfc-editor.org/rfc/rfc2616.html'
'4 Member States are recommending Advanced Encryption Standard in their ICT National Catalogues. These Member States are Cyprus, Germany, Malta and The Netherlands. CAMSS List of Standards: https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards AES Standard Reference: https://csrc.nist.gov/pubs/fips/197/final'
'CIM NGSI-LD API is currently in its 1.7.1 version thus, major releases have been published. In addition, public documentation inside the specification has been published about its supporting process, specifically related to change history and issues regarding every version. GS CIM 009: https://www.etsi.org/deliver/etsi_gs/CIM/001_099/009/01.07.01_60/gs_CIM009v010701p.pdf GS CIM 009 Remarks: https://portal.etsi.org/webapp/workprogram/Report_WorkItem.asp?WKI_ID=66918'
ELI defines a common data model focused on the description of legal data sets. It allows administrations to reuse documentation in a common and machine-readable format helping to create new services and enhance administrations data and rules visibility. However, it is domain-specific focused on the legal domain. Nonetheless, ELI is based on the Common Data Model (CMD) defined by the Publications Office that could be used instead across the sector for promoting data exchange. ELI reference: https://eur-lex.europa.eu/eli-register/about.html ELI Technical Documentation: https://eur-lex.europa.eu/eli-register/technical_information.html Common Data Model EU Vocabularies: https://op.europa.eu/es/web/eu-vocabularies/cdm
"The IndexedDB does not address the protection of personal data; it only addresses the storage of information. However, the specification offers a framework that can help achieve a more consistent privacy of data. In this context, the specification offers tips, such as deleting data when it is not necessary. Thus, the combination of the specification's functionalities and human techniques can achieve a certain degree of data privacy. Indexed Database API privacy: https://www.w3.org/TR/2025/WD-IndexedDB-3-20250110/#privacy"
The purpose of TSP is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification. TSP IETF reference: https://tools.ietf.org/html/rfc3161
'The purpose of RDF is not related to the delivery of multilingual services. Therefore this criterion is not applicable to this specification. RDF primer document: https://www.w3.org/TR/rdf11-primer/'
'The Better Regulation Guidelines and Toolbox includes guidelines, recommendations and requirements with regards to the internal market (tools 25, 28) and how policies and laws could benefit European citizens, business and institutions development reducing barriers and developing the once-only principle on lawmaking but without specific provisions. Better Regulation Guidelines and Toolbox reference: https://commission.europa.eu/law/law-making-process/better-regulation/better-regulation-guidelines-and-toolbox_en Better Regulation Toolbox reference: https://commission.europa.eu/document/download/9c8d2189-8abd-4f29-84e9-abc843cc68e0_en?filename=BR%20toolbox%20-%20Jul%202023%20-%20FINAL.pdf'
'YAML is not included in an open repository/catalogue of standards at European level. YAML specification: https://yaml.org/spec/1.2.2/'
The adoption of PNG as image format for exchanging data does not hamper the scalability of systems. It is widely adopted for this purpose because it is independent of any platform or software. PNG W3C reference: https://www.w3.org/TR/PNG/ PNG ISO reference: https://www.iso.org/standard/29581.html
EuroVoc can be found for free on its webpage. EuroVoc webpage: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/eurovoc
'The integration of Domibus with the broader digital service ecosystem can lead to an imporvement on the delivery of digital services related to messaging and data exchange, ensuring, seamless communication and data exchange between backend and user interfaces. While Domibus itself does not directly enable digital service delivery channels, it can play a role in supporting backend communication and data exchange between different components of a digital service delivery infrastructure. For example, it can be used to transmit messages related to service requests, notifications, or updates between different systems involved in the digital service delivery process. Domibus specification: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/Domibus'
"This specification refers to the System for Cross-domain Identity Management whose purpose is to securely automate the exchange of user identity data between a company's cloud applications and any service providers. It is inherently abstract and can be implemented and/or used in any domain as long as it fulfills the requirements. Therefore, its use goes beyond a specific business domain. SCIM: https://scim.cloud/"
'The SMP has been used as the basis for the development of the eDelivery SMP specification, which in turn is the basis for the implementation of the CEF eDelivery Building Block. The CEF eDelivery Building Block helps public administrations to exchange information with stakeholders (e.g. other administrations, businesses or citizens). SMP OASIS reference: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505009 eDelivery SMP specification: https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery+SMP CEF eDelivery Building Block: https://ec.europa.eu/inea/sites/inea/files/building_block_dsi-introdocument_edelivery_v1_00.pdf'
'XSLT is included in 6 national catalogues, this Member States are: Cyprus, France, Germany, Greece, Poland, Portugal and Sweden. They belong to Member States which are aligned with at least 3 out of 4 scoreboards of the EIF Monitoring according to the National Interoperability Framework Observatory (NIFO) factsheets. National Catalogue of France: https://www.numerique.gouv.fr/uploads/Referentiel_General_Interoperabilite_V2.pdf National Catalogue of Sweden: https://www.avropa.se/globalassets/dokument/open-it-standards.pdf?_t_id=1B2M2Y8AsgTpgAmY7PhCfg% 3d%3d&_t_q=standards&_t_tags=language%3asv%2csiteid%3a95d515a5-23ca-47bf-87a9- National Interoperability Framework Observatory Factsheets: https://interoperable-europe.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public-administration-factsheets-2024 List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
The purpose of this document is not related to long term preservation of electronic records. Therefore, this criterion is considered not applicable to this specification. W3C Reference: https://www.w3.org/TR/dwbp/
'The specification is intended to server as a code to identify a language name. Therefore, it is not designed to address nor prevent data long-term preservation. ISO 369-2 FAQs: https://www.loc.gov/standards/iso639-2/faq.html#7'
'The specification offers the possibility to define the metamodel of the assets among the partners in order to facilitate the interoperability of the assets. Furthermore, the core of the specification is to facilitate the data exchange among partners. Details of the Asset Administration Shell (AAS) https://industrialdigitaltwin.org/en/wp-content/uploads/sites/2/2024/06/IDTA-01001-3-0-1_SpecificationAssetAdministrationShell_Part1_Metamodel.pdf'
XACML is included in the German catalogue of recommended specifications. Germany catalogue of standards: https://www.din.de/en/about-standards/din-standards CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'JSON provides a flexible and widely supported format for representing structured data, which can be leveraged in combination with appropriate process modeling languages and notations to facilitate the modeling and execution of business processes. JSON specification: https://www.ecma-international.org/wp-content/uploads/ECMA-404_2nd_edition_december_2017.pdf'
The OASIS decision-making process for the approval of a specification is clearly defined. Decisions are taken based on votes requiring a Simple Majority Vote to pass. Furthermore, a public review is included in the TC process. See: https://www.oasis-open.org/policies-guidelines/tc-process-2017-05-26
'The purpose of MIME is not related to the implementation of the once-only principle. Therefore, this criterion does not apply to this specification. MIME specification: https://tools.ietf.org/html/rfc2045'
"The specification's version 2.2 defined a series of conformance status that CPSV-AP needs in order to be conform, as the latest release, 3.1, is based on the previous work of 2.2 it can be said that the specification defines conformance. CPSV-AP Joinup webpage: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/core-public-service-vocabulary-application-profile/release/22"
'ETSI TS 119 511 along with the whole Electronics Signature Infrastructure (ESI) family of specifications, has been proven efficient for the Preservation of Evidence of Cryptographically Signed Documents (TR-ESOR), a document from the German Federal Office of Information Security that specifies security-related requirements for the long-term preservation of evidence of cryptographically signed electronic documents and data along with associated electronic administrative data (metadata). TR-ESOR Preservation of Evidence of Cryptographically Signed Document: https://www.bsi.bund.de/SharedDocs/Downloads/EN/BSI/Publications/TechGuidelines/TR03125/TR-03125_B_v1_2_2.pdf?__blob=publicationFile&v=1 ETSI TS 119 511 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119511/01.01.01_60/ts_119511v010101p.pdf'
'Section 4.3.5 of the specification focuses on API Structure and Implementation Options, which highlights how it can be implemented incrementally or separately. For instance, the JSON-LD Context API is optional. The managing and serving of @contexts can also be handled by an independent, stand-alone component. GS CIM 009: https://www.etsi.org/deliver/etsi_gs/CIM/001_099/009/01.07.01_60/gs_CIM009v010701p.pdf'
'ETSI TS 119 511 has been developed by the European Telecommunication Standards Institute (ETSI), an independent, not-for-profit, standardization organization in the field of information and communications. About ETSI: https://www.etsi.org/about/about-us'
"The specification is associated with EIRA ABB's in the EIRA Library of Interoperability Specifications (ELIS). It is associated with Enterprise Service Bus, Internal Website from Technical Infrastructure. Application Component, Access Management Service, eProcurement Discovering Component, Knowledge Discovery Component, Knowledge Discovery Component Service, Metadata Management Component, Metadata Management Service from Technical Application. Controlled Vocabulary, Data Model, Data Syntax, Data Object, Hash Code, Metadata, Shared Knowledge Base from Semantic View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /solution/elis/release/v501 "
SOAP 1.2 is included in 2 national catalogues of recommended specifications. They belong to the Netherlands and Spain. The National Interoperability Framework (NIF) of these Member States is fully aligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO)factsheets. See: https://joinup.ec.europa.eu/collection/national-interoperability-framework-observatory-nifo/nifo-factsheets
'The purpose of ·EN 303 645 is not related to e-accessibility. Therefore, this criterion is considered not applicable to this specification. EN 303 645 reference: https://www.etsi.org/deliver/etsi_en/303600_303699/303645/02.01.01_60/en_303645v020101p.pdf'
The purpose of PNG is not related with data portability. Therefore, this criterion is not applicable to this specification. PNG W3C reference: https://www.w3.org/TR/PNG/ PNG ISO reference: https://www.iso.org/standard/29581.html
'There is no evidence found of the creation of any community along with the sharing of their data and results on European platforms. REST reference: https://restfulapi.net/'
'REM provides an e-mail service and security controls and mechanisms to protect transactions. Also the REM Signature feature is itself a secure processing of data method. ETSI EN 319 532-3 reference, section 6.2.7: https://www.etsi.org/deliver/etsi_en/319500_319599/31953203/01.02.01_60/en_31953203v010201p.pdf'
'The purpose of the EN 16234-1 e-CF framework is not related to facilitating the publication of open data. Therefore, this criterion is not applicable to this specification. CEN reference, CEN/TC 428 - ICT Professionalism and Digital Competences (Published standards), EN 16234-1 e-CF: https://standards.cencenelec.eu/dyn/www/f?p=205:110:0::::FSP_PROJECT:67073&cs=15E62ED24D608A5F10D6BEE8E6D50FA10'
'Following the completion of the research into conformity tests and certifications, a tool has been identified that enables the testing of implementations. The "Maxwell Pro's TCP/IP Test Suite" automatically identifies bugs in IPv4 and IPv6 implementations so developers can fix issues prior to release preventing product failures. Maxwell Pro's TCP/IP Test Suite: https://www.iwl.com/protocol-testing/ip'
All the IETF standards are free and open technical specification, built on IETF standards and licenses from the Open Web Foundation. See: https://www.ietf.org/rfc/rfc6749.txt
'There has not been found any platform to test conformance to ETSI TS 119 612, nevertheless, the specification lists a set of requirements needed to comply with to be conformant and can be checked manually whether or not applied. ETSI TS 119 612 specification: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf'
IPsec is included within at least 3 Member States' ICT catalogues: Spain, France and Greece. See CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
The objective of the LegalRuleML is to extend RuleML with formal features specific to legal norms, guidelines, policies and reasoning. The specification allows the exchange of legal resources under a common framework for its description and modelling. Consequently, it can be said that the specification fosters data portability between systems and applications. LegalRuleML reference: http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/legalruleml-core-spec-v1.0.html
RDA specification and recommendation processes are open from inception. Individual membership to RDA is free and open to all, as long as individuals subscribe to the RDA Guiding Principles (https://rd-alliance.org/about/get-involved.html): • Openness – Membership is open to all interested individuals who subscribe to the RDA’s Guiding Principles. RDA community meetings and processes are open, and the deliverables of RDA Working Groups will be publicly disseminated. • Consensus – The RDA moves forward by achieving consensus among its membership. RDA processes and procedures include appropriate mechanisms to resolve conflicts. • Balance – The RDA seeks to promote balanced representation of its membership and stakeholder communities. • Harmonization – The RDA works to achieve harmonization across data standards, policies, technologies, infrastructure, and communities. • Community-driven – The RDA is a public, community-driven body constituted of volunteer members and organizations, supported by the RDA Secretariat. • Non-profit - RDA does not promote, endorse, or sell commercial products, technologies, or services. Organisations may join RDA as members for an annual fee. Full details are provided at https://rd-alliance.org/organisation/rda-organisation-affiliate-members/rda-organisational-membership.html RDA Specifications, upon delivery, are assessed by the RDA Technical Advisory Board (TAB) and feedback / comments are given. All outputs go through an open and transparent Request for Comments process of 1 month on the RDA web platform. Details on the process are available at - https://www.rd-alliance.org/groups/creating-and-managing-rda-groups/working-group-outputs.htm
The purpose of CSV is not related to the delivery of multilingual public services. Therefore, this criterion is not applicable to the specification.
The purpose of XAdES is not related to the publication of public data as open data. Therefore, this criterion is not applicable to this specification. Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/en/ XAdES ISO reference: https://www.iso.org/standard/56025.html XAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/101900_101999/101903/01.04.02_60/ts_101903v010402p.pdf
'The purpose of XSD 1.1 is not related to e-accessibility. Therefore this criterion is considered not applicable to this specification. XSD Reference: https://www.w3.org/TR/2012/REC-xmlschema11-1-20120405/'
'WSDL itself does not inherently address or ensure data processing accuracy. WSDL is a specification used for describing the interfaces and operations of web services, focusing on the technical aspects of communication and data exchange. The accuracy of data processing is a broader consideration that involves various factors at both the design and implementation levels. W3C WSDL specification: https://www.w3.org/TR/wsdl20/'
'The Asset Administration Shell (AAS) has no direct provision for long term data preservation, but it mentions this capability can be implemented via extensions, but is not strictly related to long term preservation. Details of the Asset Administration Shell (AAS) https://industrialdigitaltwin.org/en/wp-content/uploads/sites/2/2024/06/IDTA-01001-3-0-1_SpecificationAssetAdministrationShell_Part1_Metamodel.pdf'
"ISAE 3402 is part of the International Federation of Accountants (IFAC) standard providing companies in the financial sector with an independent assessment tool on user entities' controls over financial reporting. ISAE 3402 auditing tool, therefore, does not allow for extensions. ISAE 3402 handbook reference: https://www.ifac.org/system/files/downloads/b014-2010-iaasb-handbook-isae-3402.pdf"
'YAML is a data serialization model that can be used in any domain. It is designed to be human-friendly, and works well with modern programming languages for common everyday tasks. YAML specification: https://yaml.org/spec/1.2.2/#chapter-1-introduction-to-yaml'
"NUTS was originally created to be used in a statistical environment and its field of application is not expected to change in the short term. However, NUTS could be implemented 'as-is' to other domains, in the sense that territorial divisions are also interesting in other statistical research areas, and not only limited to the fields of policy and demography. At the time being, there is no reference to any implementation use case of the NUTS specification. EUROSTAT reference, NUTS Principles and Characteristics section: https://ec.europa.eu/eurostat/web/nuts/principles-and-characteristics"
'The purpose of this specification is not related to security and privacy of the data exchange. Therefore, this criterion is not applicable to this specification. LDES specification: https://joinup.ec.europa.eu/collection/semic-support-centre/linked-data-event-streams-ldes'
ODF was initially published by OASIS, an international organisation aimed to develop open standards and specifications. Afterwards, it was standardised by ISO, which is also an international organisation with standardisation purposes. Moreover, the specification has the support of the Document Foundation, which is in charge of evolving the LibreOffice. The Document Foundation: https://wiki.documentfoundation.org/ODF ODF ISO reference: https://www.iso.org/standard/66363.html ODF OASIS reference: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office
"HTTP Cookies provides a way to define the lifetime of a Cookie. A permanent cookie expires at a specific date or after a specific length of time. For the permanent cookie's lifespan set by its creator, its information will be transmitted to the server every time the user visits the website that it belongs to, or every time the user views a resource belonging to that website from another website. Nonetheless, permanent Cookies have always an expiry date, addressing the long-term preservation of data in a limited manner. HTTP Cookies lifetine reference: https://developer.mozilla.org/en-US/docs/Web/HTTP/Cookies#define_the_lifetime_of_a_cookie"
DCAT has been developed for the publication of linked open data by the w3c Government Linked Data Working Group.
'ETSI TS 119 432 is not included in any national catalogue of recommended specifications whose Member State NIF has a high performance on interoperability according to NIFO factsheets. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards 2023 NIFO factsheets: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public\x02administration-factsheets-2023'
CAMSS Assessment of XHTML EIF Scenario v1.0.0
'The publiccode.yml specification does not directly facilitate the creation of organisational interoperability agreements like MoUs or SLAs. However, by providing a standardised framework for documenting software within public administrations, it indirectly supports organisational interoperability. It helps clarify relationships around software reuse and sharing, which can be an integral part of formalising agreements for cross-organisational collaboration and alignment, as outlined in EIF Recommendation 29. Publiccode.yaml documentation: https://docs.italia.it/italia/developers-italia/publiccodeyml-en/en/master/index.html'
'The specification can be found distributed in the Joinup repository. Joinup distribution CPOV: https://joinup.ec.europa.eu/collection/semic-support-centre/solution/core-public-organisation-vocabulary'
'The focus of IPsec is security. Although the specification does not directly prompt security considerations related to personal data management, IPsec enforces security policy for databases management; therefore, the specification ensures the protection of personal data. IPSec reference, Major IPSec Databases: https://datatracker.ietf.org/doc/html/rfc4301#section-4.4 IPSec reference, Security Considerations: https://datatracker.ietf.org/doc/html/rfc4301#page-72'
'UDDI is a sector agnostic specification that can be used under any business domain. In this regard, UDDI is only a register and a service directory, and does not define aspects of service execution. However, when a service is published in a UDDI register, it can be used in any domain. Oracle UDDI reference: https://docs.oracle.com/cd/E17904_01/admin.1111/e15867/uddi.htm#i1077361'
The specification in its essence aims to provide tools for the construction of global, coherent and fair policies and laws. In several of the tools proposed within the specification, multilingualism is considered as part of the requirements that ICT platforms developed for public services need to comply with and ensure. Therefore, the Better Regulation Toolbox fosters the creation of policies, and laws according to reach multilingualism ensuring the equality of European citizens. Betterr Regulation Toolbox reference: https://ec.europa.eu/info/sites/info/files/better-regulation-toolbox_2.pdf
'Being part of a test bed, GITB TDL does not deal with information that needs to be reused other than the test cases. Therefore, this criterion is not applicable. GITB TDL reference: https://www.itb.ec.europa.eu/docs/tdl/latest/introduction/index.html#introduction'
'IEEE Std 802.3-2022 primarily defines the physical and data link layers for wired Ethernet networks. Therefore, this criterion is not applicable to this specification. IEEE Std 802.3-2022 Reference: https://ieeexplore.ieee.org/document/9844436'
SVG is a specification that supports the graphical data exchange, which can be combined with XSL. It helps to the combination and exchange and integrations within other formats as XML, which is widely used for the data transmission across borders and between administrations. SVG and XSL: https://www.w3.org/People/maxf/papers/2002-07-SVGOpen/svgopen.html#id2590005
'The development of the ESPD is managed by the European Commission, which consults with stakeholders during the development process. This can include representatives from public authorities, business organizations, industry associations, and other interested parties. In addition, the Github platform hosts the larger community that contribute to the development of the specification. ESPD Business handbook: https://docs.ted.europa.eu/ESPD-EDM/latest/xml_business_handbook.html ESPD Issues in Github: https://github.com/OP-TED/ESPD-EDM/issues'
'The purpose of ShEx is not related to multilingualism; therefore, this criterion does not apply to the specification. ShEx primer document: https://shexspec.github.io/primer/ ShEx Community Group: https://www.w3.org/community/shex/ ShEx Github: https://github.com/shexSpec/spec/issues'
'ETSI TS 119 612 has been developed to establish, locate, access and authenticate a trusted like which makes available trust service status information, following the mentioned intention of the specification, it can be said it enables or helps to enable digital service delivery channels. ETSI TS 119 612 specification: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf'
'iCalendar is included in 5 national catalogues of recommended specifications. They belong to Croatia, France, Malta, the Netherlands and Sweden. CAMSS List of standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards iCalendar specification: https://www.rfc-editor.org/rfc/rfc5545'
'The purpopse of ETSI TS 119 612 is not related to enabling the visibility of administrative procedures, rules data and services, therefore this criterion is not applicable to the specification. ETSI TS 119 612 specification: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf'
'The IPsec specification is included in 5 Member States catalogues of recommended specifications. This Member States are France, Greece, Malta, Netherlands and Spain. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards'
XACML is a business domain agnostic specification. XACML OASIS reference: http://docs.oasis-open.org/xacml/3.0/errata01/xacml-3.0-core-spec-errata01.html
LegalDocML is not included in any Member States' catalogues of recommended specifications. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'Registered Organization Vocabulary provides a flexible framework that does not require a complete implementation of all defined terms. It can implement only the parts of the vocabulary that are relevant to their specific needs and data exchange scenarios. Registered Organization Vocabulary reference: https://www.w3.org/TR/vocab-regorg/'
'While DCAT-AP can help to facilitate the discovery and access of data by providing standardized metadata, it does not provide any mechanisms for securing the exchange of data itself. Nonetheless, other standards and technologies can be used in conjunction to support and enable the secure exchange of data. DCAT-AP Specification: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/dcat-application-profile-data-portals-europe/release/200'
After checking the different standard catalogues at supra-national level, there is no evidence of the inclusion of CSS v2.1 within any European catalogue of standards. ICT technical specifications: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en CEN search tool catalogue: https://standards.cen.eu/dyn/www/f?p=CENWEB:105::RESET:::: CENELEC search tool catalogue: https://www.cenelec.eu/dyn/www/f?p=104:107:0::::FSP_LANG_ID:25
'OAIS is being used in several European cross-border projects and initiatives. One example could be NEDLIB, which stands for Networked European Deposit Library a project that aims to develop a common architectural framework and basic tools for building deposit systems for electronic publications (DSEP) which is being modelled under the OAIS principles. NEDLIB Project: http://www.dlib.org/dlib/september99/vanderwerf/09vanderwerf.html'
EuroVoc is a public asset that fosters the reusability of information by helping data processing in a standardised way. Therefore, it lays down the Commission Decision of 12 December 2011 on the reuse of Commission documents. Commission Decision on the Reuse of Commission Documents: https://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=OJ:L:2011:330:0039:0042:EN:PDF
'ETSI TS 119 511 is itself a document that specifies the requirements related to policies and legal regulations that have to be applied for the creation of e-signature and long term preservation of data trust services. ETSI TS 119 511 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119511/01.01.01_60/ts_119511v010101p.pdf'
The purpose of WS-Security is not related to the publication of data as Linked Open Data. Therefore, this criterion is not applicable to this specification.
'OData offers a way to both break down data silos and increase the shared value of data. The specification contributes creating an ecosystem where data consumers and producers can interoperate more than ever, allowing more applications to make sense of a broader set of data and eases the delivery of European public services (see the Netherlands Advisory report stating the usability of OData as a solution to streamline the delivery of public services). Joinup reference: https://joinup.ec.europa.eu/collection/ict-standards-procurement/solution/odp-oasis-open-data-protocol-odata-tc/about Netherlands OData Advisory report reference: https://www.forumstandaardisatie.nl/open-standaarden/odata'
'The GraphQL specification, sub-specifications, and official reference implementations are developed using the working group model. The working groups meet monthly or as-needed in order to review ideas and plan their work. The GraphQL Working Group is the main group that plans and implements changes to the GraphQL specification. They meet actively and is the default place for discussion for topics which do not have a separate breakout working group. GraphQL Working groups: https://graphql.org/community/developers/#working-groups GraphQL participation agreement: https://github.com/graphql/graphql-wg/tree/HEAD/membership"'
"Although XHTML's purpose is not to foster the delivery of multilingual European public services, several websites contain multilingual parallel texts and are developed in XHTML. XHTML W3C reference: https://www.w3.org/TR/xhtml1/"
'After searching in the different official European websites and repositories, there is no evidence that the GITB TDL is included in an open repository/catalogue of standards at european level. GITB TDL reference: https://www.itb.ec.europa.eu/docs/tdl/latest/introduction/index.html#introduction'
'The specification partially address the protection of personal data managed by public administrations. It is possible to include additional metadata elements in DCAT to provide information on security, data protection and privacy. W3C Security and privacy indication: https://www.w3.org/TR/2023/WD-vocab-dcat-3-20230307/#security_and_privacy DCAT (v2.0.0) reference: https://www.w3.org/TR/vocab-dcat/ '
'Different existing reports point out the benefits of implementing ISAE 3402. An example of such assessment can be found in the following link: Report o ISAE 3402: https://isae3402.co.uk/sites/default/files/Whitepaper_ISAE_3402.pdf '
"The TrainingDML-AI Standard primarily focuses on creating a UML model and encodings for geospatial machine learning training data. However, the specification's goal of facilitating the exchange and retrieval of training data in a web environment indirectly supports the creation of web interfaces. These interfaces are crucial for manipulating and accessing geospatial data. OGC TrainingDML-AI Standard: https://docs.ogc.org/is/23-008r3/23-008r3.html"
'One of the aims of E-ARK CSIP is to allow data owners to build standardised interfaces for the export of their data regardless of the archives in question; and digital archives to build standardised interfaces for data ingest and access, regardless of their data providers and users in question. Therefore, it can be affirmed that E-ARK CSIP can be a good enabler of such interfaces. E-ARK CSIP specification: https://earkcsip.dilcis.eu/#introduction'
'SCIM has published documentation regarding change management and release management following the IETF internet standards process. The process of creating a standard under IETF is straightforward: a specification undergoes a period of development and several iterations of review by the Internet community and revision based upon experience. Furthermore, The IETF welcomes the critical evaluation of protocols and has provided guidance for it. Standard process IETF: https://www.ietf.org/standards/process/ Protocol Vulnerabilities IETF: https://www.ietf.org/standards/rfcs/vulnerabilities/'
'IEEE Std 802.3-2022 most important role in ensuring the network interoperability by providing a solid foundation for organizational interoperability agreements by establishing a common language, framework and physical layer specifications, ensuring backward compatibility, and promoting global adoption. IEEE 802.3-2022 Referenced in Smart Cities: https://climate-change.ieee.org/news/ieee-802/ IEEE Std 802.3-2022 Reference: https://ieeexplore.ieee.org/document/9844436'
'The ELI system does not inherently provide mechanisms for guaranteeing the authenticity and authentication of roles.Therefore, this criterion is considered not applicable to this specification. ELI reference: https://eur-lex.europa.eu/eli-register/about.html'
'By using SHACL, organisations can create formal profiles and constraints that ensure data consistency and compatibility, which can be crucial for interoperability agreements. SHACL W3C reference: https://www.w3.org/TR/shacl/'
By allowing the exchange of digital documents, PDF avoids to share non-digital documents and then helps to the reduction of administrative burden.
No study assessing the standard or specification in terms of effectiveness and efficiency has been found.
'The TSA is a TTP that creates time-stamp tokens in order to indicate that a datum existed at a particular point in time. In this way, TSP can contribute to improving secure loggins, as well as integrating with security protocols to improve confidenciality. Some of these mechanisms that can help guarantee the confidentiality of data are TLS or SASL. TSP/TSA IETF reference: https://www.rfc-editor.org/rfc/rfc3161 TLS cloudfare reference: https://www.cloudflare.com/learning/ssl/transport-layer-security-tls/ SASL gnu reference: https://www.gnu.org/software/gsasl/manual/gsasl.html#SASL-Overview'
'Advanced Message Queuing Protocol is only included in the Catalogue of the Member State of France. The Référentiel général d'interopérabilité (RGI) currently has AMQP "under observation", meaning that if the experiments prove conclusive, it will be included in a subsequent version of the General Interoperability Framework Status Explanation as "recommended". Référentiel général d'interopérabilité (RGI) Reference: https://www.numerique.gouv.fr/uploads/Referentiel_General_Interoperabilite_V2.pdf NIFO Factsheets: https://interoperable-europe.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public-administration-factsheets-2024 CAMSS list of standards: https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
'The main purpose of the IPsec specification is to ensure data protection and offer security mechanisms. One of the features that can be enabled is the confidentiality of data. In this context, IPsec can enable mechanisms to guarantee restrictions who can access to information. In this sense, it allows functionalities such as encrypting IP packets and preventing eavesdropping on network traffic. Eavesdropping is a type of cyberattack that can result in financial loss, identity theft, or privacy breaches. IPSec reference: https://www.rfc-editor.org/rfc/rfc6071.html IPsec security reference: https://www.geeksforgeeks.org/ip-security-ipsec/ IPsec eavesdropping attack reference: https://www.geeksforgeeks.org/what-is-an-eavesdropping-attack/'
'BFO is not a European Standard nor have been adopted as such within the EU. BFO reference: https://www.iso.org/standard/74572.html'
CAMSS Assessment of SAML EIF Scenario v1.0.0
"RDF has been selected within several initiatives at European level in order to provide open data and linked data to be used for Member States, citizens, and businesses. An example of RDF use is the European cross-border project ESCO (European Skills, Competences, Qualifications, and Occupations). The project uses Turtle extension of RDF in order to make available the project's data. At ESCO's webpage can be found the link to data resources and as well as information resources needed for the proper use of provided data. Additionally, RDF has been selected as one of the core elements on the euCASES project, a platform for linking legal documentation and offer it as Linked Open Data. euCASES website: https://ec.europa.eu/esco/portal/escopedia/RDF http://eucases.eu/start.html ESCO ontology: https://ec.europa.eu/esco/lod/static/model.html"
'UBL is included in 3 national catalogues of recommended specifications. They belong to Greece Malta and The Netherlands. The National Interoperability Framework of the Netherlands is fully aligned with 3 out of the 3 sections according to the European Interoperability Framework Observatory (NIFO) factsheets, while Greece is placed on the European average (2 out of 3) and Malta scores below average (1 out of 3). NIFO factsheets: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public-administration-factsheets-2021 National Catalogue of the Netherlands: https://www.forumstandaardisatie.nl/open-standaarden/aanbevolen National Catalogue of Malta: https://mccaa.org.mt/Section/Content?contentId=1243 National Catalogue of Greece http://www.e-gif.gov.gr/portal/pls/portal/docs/1/211041.PDF'
WS-BPEL is not included in any catalogue of standards at supra-national level.
TIFF/IT was released in 1996 as a standard for the exchange of digital adverts. It became an ISO standard in 1998 as ISO 12639:1998, the specification had some modifications and the current version was published in 2004. The last review of TIFF/IT was in 2017 and it was confirmed to be the latest version. So it is clear that the specification is mature enough for develop of products and services. TIFF/IT ISO reference: https://www.iso.org/standard/34342.html
'The purpose of Advanced Encryption Standard is not related to guarantee the authenticity and authentication of the roles agents involved in the data transactions. Therefore, this criterion is not applicable to the specification. Geeksforgeeks AES reference: https://www.geeksforgeeks.org/advanced-encryption-standard-aes/ AES Standard Reference: https://csrc.nist.gov/pubs/fips/197/final'
'While the CSIP does not explicitly focus on the secure exchange of data, its adherence to open standards, inclusion of administrative metadata, and alignment with best practices can indirectly support the secure exchange of data. Organizations implementing the CSIP should complement it with appropriate security measures, encryption, access controls, and compliance with data protection regulations to ensure secure data exchange. E-ARK CSIP specification: https://earkcsip.dilcis.eu/#introduction'
The purpose of ELI is to be a system to make legislation available online in a standardised format so that it can be accessed, exchanged and reused across borders. By allowing to make the data available amongst organisations, ELI Contributes to the development of eGovernment reducing the administrative burden. ELI reference: https://eur-lex.europa.eu/eli-register/about.html
WS-Security main function is to enforce security for messages as an extension of SOAP. So it can be considered that helps to process data.
After carrying out information retrieval, no document or study has been found assessing directly the HTML 4 in terms of efficiency or effectiveness. However, there is information that compares different versions of HTML (HTML4 and HTML5), and the main differences between them. From there, it can be inferred the effectivity and effectiveness of the usage of HTML4. HMTL5 vs HTML4: https://www.educba.com/html5-vs-html4/
After checking the list of specifications identified by the MSP Multi-stakeholder-platform, no assessment verifying the compliance of the specification with the European standardisation regulation has been found. ICT technical specifications: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en
This Core Vocabulary offers several services that aim to help e-Government professionals share their experience with each other, so it fosters the creation of innovative solutions. CPSV-AP reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-service-vocabulary-application-profile
Currently, JSON is a widely used specification for data interchange between applications and platforms. It is used in a REST API applications in order to ensure data exchange, this application is extensively used for the creation of solutions, including innovative ones.
Like all the IETF standards, MIME is a free and open technical specification, built on IETF standards and licenses from the Open Web Foundation. Therefore, MIME is licensed on a royalty-free basis. No IPR disclosures have been submitted directly on the MIME specification (RFC 2045). Intellectual Property Rights in IETF: https://tools.ietf.org/html/rfc3668
The purpose of CPSV-AP is related to the delivery of multilingual public services. All datatype properties with datatype “text” where the value for that property may exist in multiple languages, the property has multiple instances which are tagged with a language identifier for each language in which the value for that property exists. CPSV-AP reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-service-vocabulary-application-profile
eDelivery SMP 1.10 is an evolution of the previous e-SENS SMP, which evolves from the PEPPOL SMP specification and was standardised by OASIS. The assessed specification continues strictly related to SMP 1.0 as is an extended profile for eDelivery Building Block. Therefore, these facts demonstrate that eDelivery SMP 1.10 is mature enough to be used in the creation of products and solutions. Additionally, it is supported by Open sources and commercial, which ensures its market acceptance. See: https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/Background
'The Publications Office of the European Union publishes European Public Procurement Notices on the TED website. The new generation of these notices, eForms, has been restructured using UBL and the associated genericode files, genericode files in the notices have been made freely available for reuse in EU Vocabularies under the eProcurement Business Collection. eProcurement Business Collection: https://op.europa.eu/en/web/eu-vocabularies/e-procurement'
The purpose of HTTP is not related to organisational interoperability. Therefore, this criterion is not applicable to the specification.
'The specification guarantees the authenticity and authentication of the roles agents involved in the data transactions (issuer and holder) with a verifier, a role where an entity performs by receiving one or more verifiable credentials, optionally inside a verifiable presentation for processing. This specification describes mechanisms for ensuring the authenticity of Verifiable Credentials and similar types of constrained digital documents using cryptography, especially through the use of digital signatures and related mathematical proofs. Verifiable Credentials Data Integrity: https://www.w3.org/TR/vc-data-integrity/'
The purpose of the specifications is to define technical interoperability aspects. Therefore, eDelivery is used for business modelling processes.
'YAML can facilitate the modeling of business processes by providing a readable and structured format for defining workflows, configurations, and data exchanges. Its flexibility and compatibility with tools like BPMN (Business Process Model and Notation) and workflow automation platforms (e.g., Ansible, Kubernetes) make it useful for documenting and automating business processes efficiently. YAML specification: https://yaml.org/spec/1.2.2/ BPML generator for YAML: https://www.giancarlomangiagli.it/en/BPMNator_BPMN_generator_from_YAML.html'
'IPv6 is included in 7 national catalogues of recommended specifications. They belong to Austria, Croatia, France, Germany, Netherlands, Norway, and Sweden. The National Interoperability Framework (NIF) of Germany and Austria are fully aligned with at least 3 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. Nonetheless, countries like Sweden do not get a high performance, being aligned with 3 out of 5. National catalogue of Austria: https://neu.ref.wien.gv.at/at.gv.wien.ref-live/ag-ii-austrian-intero.-framework National catalogue of Germany: https://www.cio.bund.de/Web/DE/Architekturen-und-Standards/SAGA/SAGA%205-aktuelle%20Version/saga_5_aktuelle_version_node.html National catalogue of sweden: https://www.avropa.se/globalassets/dokument/open-it-standards.pdf?_t_id=1B2M2Y8AsgTpgAmY7PhCfg%3d%3d&_t_q=standards&_t_tags=language%3asv%2csiteid%3a95d515a5-23ca-47bf-87a9- NIFO factsheets: https://joinup.ec.europa.eu/collection/national-interoperability-framework-observatory-nifo/nifo-factsheets'
Nowadays, JSON is not included in any supra-national catalogue of standards.
'There have been found some academic papers assessing the use of DPV in terms of efficiency. These documents describe the use of DPV personal data handling policies and information about consent (see Personal Data Handling in Multi-Agent Systems Interaction) or assess the efficiency when it comes to discover the relevant information in privacy policies by means of integrating the knowledge represented in the DPV with the information modelled in BabelNet. Personal Data Handling in Multi-Agent Systems Interaction: https://link.springer.com/chapter/10.1007/978-3-030-49778-1_5 The role of Vocabulary Mediation to Discover and Represent Relevant Information in Privacy Policies: http://ebooks.iospress.nl/doi/10.3233/FAIA200851,'
PAdES Baseline profile has been selected within the CEF Digital Signature Service (hereby DSS) along with CAdES, XAdES and ASiC. DSS is a free service that allows interested users to get started in the development of eSignatures according to existing regulations. The initiative is an enabler for the cross borders interoperability between administrations and business. See: https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/Standards+and+specifications https://ec.europa.eu/cefdigital/DSS/webapp-demo/doc/dss-documentation.html
Xforms 2.0 is not included in any Member States' catalogues of recommended specifications. However, Germany includes a previous version in its catalogue of recommended specifications. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'Domibus provides means for restriction of access to information through its access control mechanisms, which allow to manage user roles, permissions, and access rights within the Domibus platfform. Interaction with specific information or functionalities can be managed by the access control settings. Domibus specification: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/Domibus AS4 specification: http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/profiles/AS4-profile/v1.0/AS4-profile-v1.0.html'
'OAS is developed by the OpenAPI initiative (OAI), an organisation operating under the Linux Foundation. Therefore, it is not a European standard. OAS specification: https://spec.openapis.org/oas/latest.html#openapi-specification OAS in Github: https://github.com/OAI/OpenAPI-Specification/#participation'
CSS is maintained by W3C which is an international community developing open standards. Developer community W3C: https://www.w3.org/Consortium/
'While XFDL is not designed to provide access control mechanisms, it can work with external systems to achieve more security. In this context, it is possible to implement role-based permissions and digital signatures. These mechanisms can be useful to secure data and ensure it is only accessed by verified users. Moreover, we can highlight the XML Signature Syntax and Processing specification, which offers a way to sign data of any type, improving security mechanisms. Extensible Forms Description Language reference: https://www.w3.org/TR/NOTE-XFDL'
The Core Criterion and Core Evidence Vocabulary (CCCEV) supports the exchange of information between organisations that define criteria and organisations that respond to these criteria by means of evidences. CCCEV reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-criterion-and-core-evidence-vocabulary
'The specification is implemented in a wide variety of business domains and fields. BFO reference: https://www.iso.org/standard/74572.htmll '
'The ELI specification promotes data portability in European public services by encouraging technological neutrality and providing clear recommendations. It supports the transferability of data among different systems to avoid lock-in and facilitate the free movement of data. Legal initiatives like the European Directive on patients’ rights and the NIS Directive, and frameworks like ISA², further enhance these capabilities. ELI Technological Neutrality and Data portability reference: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/solution/eif-toolbox /underlying-principle-5-technological-neutrality-and-data-portability ISA2 Framework reference: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=COM%3A2017%3A134%3AFIN ELI reference: https://eur-lex.europa.eu/eli-register/about.html'
'Following the completion of the research into conformity tests and certifications, a tool has been identified that enables the testing of implementations. The "Maxwell Pro's TCP/IP Test Suite" automatically identifies bugs in IPv4 and IPv6 implementations so developers can fix issues prior to release preventing product failures. Moreover, there are existing free online documents that will help you validate IPv6 specification when it is implemented. Maxwell Pro's TCP/IP Test Suite: https://www.iwl.com/protocol-testing/ip Document "The next generation Internet protocol and its test" for testing IPv6: https://ieeexplore.ieee.org/document/936305 Document "IPv6 Conformance Testing: Theory and Practice" for testing IPv6: https://dl.acm.org/doi/10.5555/1116164.1116526'
'According to the 5 star Open Data model suggested by Tim Berners-Lee about how to publish linked data, the second star corresponds to the availability of data as structured data. WAI-ARIA is a document-level markup language, therefore it structures data as any other mark-up languages (e.g. HTTP or XML). WAI-ARIA reference: https://www.w3.org/TR/wai-aria/ Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/en/ '
'The specification has a namespace which focus is to know information about who access the resource or an indication of its security status, the namespace may include information regarding access or restrictions based on privacy, security or other policies. The specification ensures and enables the secure processing of data. DCMI About: https://www.dublincore.org/about/ DCMI Access Rights: https://www.dublincore.org/specifications/dublin-core/dcmi-terms/terms/accessRights/'
'The purpose of the specification is not related to the publication of public data as Open Data. Therefore this criterion is not applicable to the specification. DIDs specification: https://www.w3.org/TR/did-core/'
There are no evidences of existing studies or documentation assessing the standard or specification in terms of effectiveness and efficiency to justify the criterion. Note that SHACL is th first W3C standard mechanism for defining data constraints.
ODF is already associated to an EIRA ABB in the EIRA Library Of Interoperability Specifications (ELIS). Specifically, ODF can define the interoperability aspects of the "Representation" ABB from the EIRA Semantic view. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/solution/elis/release/v100
'TOSCA allows customisation but authoring processes might be difficult to execute; hence the creation of related specifications based on other host languages (see TOSCA reference, TOSCA Simple Profile in YAML Objective section). Moreover, there is an attempt within the TOSCA TC to create a core TOSCA specification compatible with a variety of deployment use cases that would minimise the specification dependence on hosting technologies (see TOSCA Draft Version 2.0 reference, section 1.2). TOSCA reference, Cloud Service Archive (CSAR) reference: https://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.3/os/TOSCA-Simple-Profile-YAML-v1.3-os.html#_Toc26969474 TOSCA reference, TOSCA Simple Profile in YAML Objective section: https://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.3/os/TOSCA-Simple-Profile-YAML-v1.3-os.html#_Toc26969412 TOSCA Draft Version 2.0 reference, section 1.2: https://docs.oasis-open.org/tosca/TOSCA/v2.0/csd03/TOSCA-v2.0-csd03.html#_Toc56506175'
IPsec allows the exchange of data between systems and is compatible with both versions of the Internet Protocol, IPv4 and IPv6. Therefore it prevents the storage of data in silos that are incompatible with one another. See: https://tools.ietf.org/html/rfc4301
'The Better Regulation Guidelines and Toolbox is a European resource created by the Commission where privacy is defined through the implementation of privacy policies such as the GDPR. In this sense, the Tool 28 covers this element extensively. Better Regulation Guidelines and Toolbox reference: https://commission.europa.eu/law/law-making-process/better-regulation/better-regulation-guidelines-and-toolbox_en Better Regulation Toolbox reference: https://commission.europa.eu/document/download/9c8d2189-8abd-4f29-84e9-abc843cc68e0_en?filename=BR%20toolbox%20-%20Jul%202023%20-%20FINAL.pdf'
The specification was developed in 2012 by an Action of ISA2. In 2013, it was standardised by W3C. This fact demonstrates that the specification has overcome the initial problems. On 23 May 2012, the Coordination Group of the Interoperability Solutions for European Public Administrations (ISA) Programme renamed the specification to Core Business Vocabulary and it has been added to e-Government Core Vocabularies. So the specifications can be considered mature for its use in the development of products and services. RegOrg W3C reference: https://www.w3.org/TR/vocab-regorg/ RegOrg Joinup reference: https://joinup.ec.europa.eu/solution/registered-organization-vocabulary/about Core Business Vocabulary reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-business-vocabulary
'Being a Core Vocabulary for data privacy, an important aspect of DPV design is its support for customisation to meet the needs of individual organizations while maintaining complete interoperability within the standard framework. The aim of DPV is therefore to provide an upper-level abstract taxonomy of categories of legal bases that can be customised and applied as needed. DPV specification: https://w3c.github.io/dpv/primer/'
"Schema.org relies on more than one development community, mainly the Community Group and the Steering Group (see Schema.org homepage reference, 'About Schema.org' section). All information relating to this specification can be found in the schema.org homepage (see Schema.org reference, Releases section), as well as in relevant platforms supported by W3C (e.g., Mailing list and Github). See also the Github Wiki section to engage with other schema.org external communities (e.g., Stackoverflow). Schema.org homepage reference, 'About Schema.org' section: https://schema.org/docs/about.html Schema.org reference, Releases section: https://schema.org/docs/releases.html W3 community reference, Mailing List: https://lists.w3.org/Archives/Public/public-vocabs/ Schema.org-W3 Github reference: https://github.com/schemaorg/schemaorg/ Schema.org-W3 Github, Wiki section: https://github.com/schemaorg/schemaorg/wiki"
'TOSCA is already associated with an EIRA ABB in the EIRA Library Of Specifications (ELIS). More specifically, the specificaiton can define the interoperability aspects of the Orchestration Component and Orchestration Service ABBs of the EIRA Technical View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/v110'
'Better Regulation Guidelines and Toolbox can be used and applied independently from other standards, or software requirements. Therefore, Better Regulation Guidelines and Toolbox establishes guidelines and principles, ensuring applicability across all platforms. Better Regulation Guidelines and Toolbox reference: https://commission.europa.eu/law/law-making-process/better-regulation/better-regulation-guidelines-and-toolbox_en'
'WAI-ARIA specification itself does not provide an access control mechanism. Therefore, this criterion is not applicable to this specification. WAI-ARIA reference: https://www.w3.org/TR/wai-aria-1.2/'
'The publiccode.yml specification does not address data integrity protections or provide mechanisms to prevent unauthorised data alterations. Its scope is solely to document metadata regarding public code projects, and it does not include features or protocols to support data integrity. Consequently, it does not align with the data integrity requirements referenced in EIF Recommendation 15. Publiccode.yaml documentation: https://docs.italia.it/italia/developers-italia/publiccodeyml-en/en/master/index.html'
The purpose of SMTP is not related to e-accessibility. Therefore, this criterion is considered not applicable specification. SMTP IETF reference: https://tools.ietf.org/html/rfc5321
'ISO/IEC 19944-1 was developed by the ISO/IEC joint technical committee JTC 1. The access to JTC 1 working area is restricted, and individuals or companies are not eligible as members of ISO. ISO has defined a clear procedure to develop its standards. It consists in a 6-steps process where everyone who is interested can participate. However, if you want to participate, you have to contact your national standards body and you have to be approved for joining the Technical committee (TC) who will develop the standard. ISO has defined the roadmap of standards, it is composed of 6 steps as before said. For the approval of a standard the two-thirds majority of P-members of TC is needed. If the result is negative, the document is returned to TC/SC to be further studied. The ISO standardization process: https://www.iso.org/stages-and-resources-for-standards-development.html ISO membership reference: https://www.iso.org/get-involved.html'
'The specification is not included in any open repository/catalogue of standards at European level. SHACL W3C reference: https://www.w3.org/TR/shacl/'
Taking into account the initial purpose of the specification, it can be considered that the specification is involved in fostering the comprehensibility of Public Administrations' data as well as relevant data produced for the decision-making process. It is involved by providing consistent methodology for the creation and development of coherent public services and solutions. OpenPM2 specification reference: https://op.europa.eu/en/publication-detail/-/publication/ac3e118a-cb6e-11e8-9424-01aa75ed71a1/language-en/format-PDF/source-83307127
'The NFV project started in 2013, and the first release of the NFVI took place in 2014. All the NFV distribution set underwent through a second release by 2016, and a third release in 2019 including software modifications of this specification. A fourth release in 2020 worked on the lightweight virtualisation support of technology allowing to optimise the NFV specification. An ETSI OnLine (EOL) account is required to access to the ETSI NFV Issuer Tracker. ETSI NFV reference: https://www.etsi.org/technologies/nfv/nfv ETSI NFV release 3: https://www.etsi.org/deliver/etsi_gs/NFV-REL/001_099/006/03.01.01_60/gs_NFV-REL006v030101p.pdf NFVI Feature Tracker: https://nfvwiki.etsi.org/index.php?title=Feature_Tracking#FEAT03:_NFVI_software_modification ETSI NFV Issuer Tracker: https://nfvwiki.etsi.org/index.php?title=NFV_Issue_Tracker'
'EUROSTAT makes available a Linked Open Data section where the European Commission publishes data and all kinds of statistical analysis based on the NUTS classification, encouraging the creation of communities around the specification at European level. EUROSTAT reference, NUTS Linked Open Data section: https://ec.europa.eu/eurostat/web/nuts/linked-open-data'
'EN 319 532 substituted the previous TS 102 640, which indicates EN 319 532 as an effective service. Also, ENISA is recommending the specification in a Signature Verification document. ENISA document: https://www.enisa.europa.eu/events/tsforum-caday-2018/presentations/C03_Rock.pdf ETSI EN 319 532-3 reference: https://www.etsi.org/deliver/etsi_en/319500_319599/31953203/01.02.01_60/en_31953203v010201p.pdf'
'WAI-ARIA primarily addresses web accessibility concerns and is not designed to handle privacy-related matters.Therefore, this criterion is not applicable to this specification. WAI-ARIA reference: https://www.w3.org/TR/wai-aria-1.2/#privacy-and-security-considerations'
The Core Location Vocabulary is a business domain agnostic specification that can be reused in a cross-domain way. CLV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-location-vocabulary
'The purpose of SOAP 1.2 is to store, transport and exchange data through interoperable systems. Moreover, SOAP 1.2 uses XML which defines a set of rules for encoding documents in a human-readable format and machine-readable format enhancing the reusability of data and stimulating the interoperability of systems and services. Additionally, W3C develops its specification independently from any vendor. Thus, the adoption of SOAP 1.2 does not hamper the data portability of data expressed with it. In fact, the adoption of SOAP endorses the binding and invoking of web services allowing data exchange across borders. SOAP Reference: https://www.w3.org/TR/soap12/'
CAdES Baseline is available for free at the ETSI’s Catalogue of Standards. It can be found at ETSI’s webpage. See: https://www.etsi.org/standards#page=1&search=ETSI%20TS%20103%20173&title=1&etsiNumber=1&content=1&version=0&onApproval=1&published=1&historical=1&startDate=1988-01-15&endDate=2020-01-08&harmonized=0&keyword=&TB=&stdType=&frequency=&mandate=&collection=&sort=1
'The CPOV eases the description and publication of datasets including information of different public organisations, their services and responsibilities. These descriptions are done using human-readable formats which ease the reusability and the information exchange across-borders. CPOV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-organisation-vocabulary 5-star linked open data: https://www.w3.org/DesignIssues/LinkedData.html'
The recommendation is aiming to achieve seamless interoperability, trust, and ultimately to provide growth and employment opportunities by facilitating data exchange across organisations, disciplines and geographical borders.
Although FTPS is not the main specification used for FTP secured transfers, it has been selected for its use in the initiative "The Big Data Platform Initiative of the EC Joint Research Centre", it takes care of ensuring data transfer to EOS. JRC Big Data Platform (JEODPP): https://ec.europa.eu/eurostat/cros/system/files/dawos18_lecture.soille.jeodpp.pdf
The purpose of SAMM is not related to the availability of interfaces with internal information systems. Therefore, this criterion is not applicable to this specification. SAMM webpage: https://owaspsamm.org/ SAMM documentation: https://github.com/OWASP/samm/blob/master/Supporting%20Resources/v2.0/OWASP-SAMM-v2.0.pdf
'The specification is included in Slovakia’s catalogue of recommended specifications. Slovakia’s Catalogue: https://www.mirri.gov.sk/sekcie/informatizacia/governance-a-standardy/standardy-isvs/index.html CAMSS List of standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
The purpose of XACML is not related to organisational interoperability. Therefore, this criterion is not applicable to the specification. XACML OASIS reference: http://docs.oasis-open.org/xacml/3.0/errata01/xacml-3.0-core-spec-errata01.html
'The purpose of this Core Vocabulary is not related to e-accessibility. Therefore, this criterion is considered not applicable to this specification. Core Criterion and Core Evidence Vocabulary reference (v1.0.0): https://joinup.ec.europa.eu/release/core-criterion-and-core-evidence-vocabulary-v100 '
SAML 2.0 is a business domain agnostic specification.
SHACL is publicly available for implementation and use, and therefore for everyone to study, for free on Github. Also, TopQuadrant developped a service available for free in Javascript allowing the use of SHACL features. See: https://github.com/w3c/data-shapes http://shacl.org/playground/
'As the is specification is part of RDF, it can reuse partially core classes which can be implemented incrementally or separately to fulfill its function. ADMS Specification W3C: https://www.w3.org/TR/vocab-adms/'
As a set of protocols involved in the Internet Protocol Suite, IPsec allows a secure data exchange. It avoids the exchange of non-digital documents and therefore reduces the administrative burden. Moreover, IPsec is available for free, reduces vendor lock-in and therefore reduces administrative burden. See: https://tools.ietf.org/html/rfc4301 https://joinup.ec.europa.eu/solution/ietf-rfc-4301-2005-security-architecture-internet-protocol/distribution/ietf-rfc-4301-2005-security-architecture-internet-protocol
'The Asset Administration Shell (AAS) has at its core the idea of platform Industrie 4.0 that is the delivery of assets among partners and this simplifies the deliver of public services related to manufacturing. Industrie 4.0 initiative: https://www.plattform-i40.de/IP/Navigation/EN/Home/home.html Details of the Asset Administration Shell (AAS) https://industrialdigitaltwin.org/en/wp-content/uploads/sites/2/2024/06/IDTA-01001-3-0-1_SpecificationAssetAdministrationShell_Part1_Metamodel.pdf'
'CPOV is a European Standard as it was developed and recognized by the European standards organisations; it is also maintained by the semic community. CPOV Joinup reference: https://joinup.ec.europa.eu/collection/semic-support-centre/solution/core-public-organisation-vocabulary#:~:text=Core%20Public%20Organisation%20Vocabulary%201%20Description%20The%20SEMIC,publishing%20data%20about%20public%20organisations.%203%20Version%20information '
'WSDL helps to describe and make available administration’s web services, which contain public data and information to be reused. The data is structured as WSDL is an XML based language. Taking into account these facts, WSDL is supporting several maturity levels from Tim Berners Lee’s 5 stars schema for Open Data. Additionally, there are existing W3C recommendation and notes regarding the semantics on WSDL. Known as Semantic Annotations Web Services Description Language (SAWSDL). As well, a technical report from the Web Services Description Working Group that maps the representation of the WSDL model in RDF. Tim Berners-Lee 5 star open data: https://5stardata.info/en/ WSDL RDF Mapping: https://www.w3.org/TR/wsdl20-rdf/ WSDL Semantic annotations: https://www.w3.org/TR/sawsdl/'
As a document format, PDF 1.7 helps to make data available on the internet. This fact demonstrates that the standard is supporting the first level of maturity from Tim Berners Lee's 5 stars schema for Open data. See: https://5stardata.info/es/
ISO has defined a clear procedure to develop its standards. It consists in a 6-steps process where everyone who is interested can participate. However, if you want to participate, you have to contact your national standards body and you have to be approved for joining the Technical committee (TC) who will develop the standard. ISO has defined the roadmap of standards, it is composed of 6 steps as before said. For the approval of a standard the two-thirds majority of P-members of TC is needed. If the result is negative, the document is returned to TC/SC for further studied. The ISO standardization process: https://www.iso.org/stages-and-resources-for-standards-development.html
'Since XFDL is built on XML, it allows for the export and sharing of data with external systems. This enables both administrators and users to access data and gain insights into services outside of the XFDL environment, enhancing service visibility across a wider range of platforms. In this context, the study 'Signed XML: Experiences from the Creation of XFDL' demonstrates how it can be useful for e-commerce and digital signatures. "Signed XML: Experiences from the Creation of XFDL" study: https://www.w3.org/DSig/signed-XML99/present/UWI/01.HTM Extensible Forms Description Language reference: https://www.w3.org/TR/NOTE-XFDL'
The application of the once-only principle in all EU Member States public administrations aims at reducing the administrative burden. XACML addresses and facilitates interoperability between public administrations, cross-border services, and impacts positively the development of eGovernment. This is because it has been designed to evaluate and control access by ensuring the compliance of security policies. Also, the project SEMIRAMIS, uses this specification to ensure secure channels for the exchange and reuse of information. XACML OASIS reference: http://docs.oasis-open.org/xacml/3.0/errata01/xacml-3.0-core-spec-errata01.html SEMIRAMIS project: https://joinup.ec.europa.eu/solution/semiramis/about
'SAML 2.0 primarily focuses on the authentication and authorization aspects of user data exchange, rather than data protection per se. There are several features and best practices within the SAML specification can be leveraged to enhance the protection of personal data, especially when used by Public Administrations or other entities. SAML 2.0 Reference: http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-tech-overview-2.0.html'
"The XFDL specification helps protect information against unauthorised changes through its digital signature feature. When a form is signed, the digital signature ensures the authenticity and integrity of the data. In addition, the use of encryption in the signature's mimedata option further secures the data, ensuring that the original information remains intact. This approach is in line with the XML Signature Syntax and Processing specification, which defines how digital signatures are applied to XML documents, guaranteeing the data’s integrity and verifying the signer’s identity. XML Signature Syntax and Processing reference: https://www.w3.org/TR/xmldsig-core1/ XFDL security reference: https://www.w3.org/TR/NOTE-XFDL#button"
The specification is a widely used de-facto standard. It was launched for the first time in 1998 by engineers from Microsoft. Other companies with a wide market share are contributed to the development of the specification. Additionally, SOAP is developed and maintained by W3C and its working group. Thus, it is sufficiently mature for the development of products and services. See: https://www.w3.org/TR/soap12/
"The specification is intended to properly convey user interface behaviours and structural information to assistive technologies in document-level markup. The Spanish Public Administration, through the Observatory of Web Accessibility, is updating mobile user interfaces in all their services. WAI-ARIA reference, Abstract section: https://www.w3.org/TR/wai-aria/ PAe reference, 'Proceedings of the Observatory of Web Accessibility' section: https://administracionelectronica.gob.es/pae_Home/en/pae_Estrategias/pae_Accesibilidad/pae_Observatorio_de_Accesibilidad.html?idioma=en"
'In the European Union (EU), privacy and data protection are governed by the General Data Protection Regulation (GDPR), which outlines rules for the processing of personal data. Any implementation of web services, including those described using WSDL, should adhere to GDPR requirements and other relevant privacy laws at the European or national level. Web Services Description Language (WSDL) itself is a technical specification developed by the World Wide Web Consortium (W3C) and does not inherently include privacy-specific features or mechanisms. However, the adoption and use of WSDL in the context of European or national initiatives may be subject to compliance with privacy laws and regulations. EU-US Data Privacy Framework: https://ec.europa.eu/commission/presscorner/detail/en/qanda_23_3752 General Data Protection Regulation (GDPR): https://gdpr.eu/what-is-gdpr/ '
'OData is a recommendation and protocol for data exchange. Therefore, the specification enables secure and accurate data exchange between stakeholders and it is explicitly addressed via RFC 7230, RFC 7231, RFC 7232. OData reference: https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#_Toc3135883 Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing”, RFC 7230. https://tools.ietf.org/html/rfc7230. Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content”, RFC 7231. https://tools.ietf.org/html/rfc7231. Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests”, RFC 7232. https://tools.ietf.org/html/rfc7232.'
'The Core Criterion and Core Evidence Vocabulary (CCCEV) supports the exchange of information between organisations that define criteria and organisations that respond to these criteria by means of evidences. Core Criterion and Core Evidence Vocabulary reference (v1.0.0): https://joinup.ec.europa.eu/release/core-criterion-and-core-evidence-vocabulary-v100 '
"iCalendar focuses on providing a structured representation of events, tasks, and scheduling information, including features such as recurring events, time zones, attendee management, and reminders. While some administrative information can be included in event descriptions and custom properties, iCalendar is not intended as a comprehensive platform for managing or exposing public administration's services. iCalendar specification: https://www.rfc-editor.org/rfc/rfc5545"
There are existing tools to check if HTTPS implementation is performing well. See: https://gf.dev/tls-test
"There exist some studies assessing digital solutions' efficiency that are based on iCalendar; however, most of them are restricted to learning environments. One of these assessments evaluates how Google calendar contributes to an efficient reservation of a learning room. Google calendar in learning environments - Design and Implementation of a Study Room Reservation System: Lessons from a pilot program using Google Calendar: https://research.library.fordham.edu/cgi/viewcontent.cgi?article=1002&context=lib_staffpubs iCalendar specification: https://www.rfc-editor.org/rfc/rfc5545"
'The specification has four defined interoperability levels that serve as guidelines for determining the level of interoperability, having a defined level means that the previous levels to the one mentioned are included, so it is a level 3 conforming specification it automatically conforms level 1 and 2. The intention is to provide a "ladder of interoperability", specifying the choices, costs, and benefits involved in designing applications for increased levels interoperability. DCMI Interoperability Levels: https://www.dublincore.org/specifications/dublin-core/interoperability-levels/'
'By helping administrations to identify and manage possible risks, ISO/IEC 27001 ensures and fosters the continuous availability of administrations data and information. In the following link you can see an example of audits in public administration. Financial audits require the review of the IT part and with it the ISO/IEC 27001. Application of ISO/IEC 27001 in public administration: https://core.ac.uk/display/196275557'
The purpose of IPv6 is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification.
Although PNG supports the first level of maturity from the Tim Berners-Lee 5-star schema for the Open data, it does not support the main principles for the publication of data as Linked Open Data. 5-star linked open data: https://www.w3.org/DesignIssues/LinkedData.html https://www.w3.org/wiki/LinkedData PNG W3C reference: https://www.w3.org/TR/PNG/
'The AKN4EU specification supports multilingual content by allowing the use of multiple languages within the same document. This is achieved through the use of language attributes to identify the language of specific elements within the document. AKN4EU reference: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/akn4eu'
10 Member States are recommending RDF in their ICT National Catalogues. See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
10 Member States are recommending SVG in their ICT National Catalogues. They belong to the Croatia, Estonia, France, Germany, Malta, Netherlands, Norway, Poland, Spain and Sweden. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'After checking the different standard catalogues at supra-national level, there is no evidence of the inclusion of REST within any European catalogue of standards. ICT technical specifications: https://ec.europa.eu/growth/single-market/european-standards/ict-standardisation/ict-technical-specifications_en CENELEC and CEN search tool catalogue: https://standards.cencenelec.eu/dyn/www/f?p=CEN:105::RESET:::: CENELEC and CEN website: https://www.cencenelec.eu/'
At the moment of performing the assessment, the specification is not mapped with any EIRA ABBs and therefore is not included in the ELIS v1.0.1. However, it has been associated with interoperability agreements in all EIRA views and is being included in the on-gong version of the ELIS that will be released in May 2021. ELIS Solution: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis ELIS v1.0.1: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/v101-0
"The purpose of TS 119 614-1 is not related to enabling the exposure of interfaces of public administration's services. Therefore, this criterion is not applicable to the specification. ETSI TS 119 614-1 reference: https://www.etsi.org/deliver/etsi_ts/119600_119699/11961401/01.01.01_60/ts_11961401v010101p.pdf"
'XHTML is included in 9 national catalogues. The Member States that includes the specification are Cyprus, Estonia, France, Germany, Greece, Norway, Poland, Slovenia and Spain. At least Cyprus and Spain are aligned with at least 3 out of 4 scoreboards from the EIF Monitoring according to the National Interoperability Framework Observatory (NIFO) factsheets. National Catalogue of Cyprus: https://dits.dmrid.gov.cy/dmrid/dits/dits.nsf/all/B83AA8E4EB4EFD19C225855800288B10/$file/Cyprus% 20eGovernment%20Interoperability%20Framework_new%20EIF_v2.0-To%20Publish.pdf National Catalogue of Spain: https://administracionelectronica.gob.es/pae_Home/pae_Estrategias/pae_Interoperabilidad_Inicio /pae_Normas_tecnicas_de_interoperabilidad.html#CATALOGOESTANDARES National Interoperability Framework Observatory Factsheets: https://interoperable-europe.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory /digital-public-administration-factsheets-2024 List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards'
'The purpose of UTF-8 is not related to e-accessibility. Therefore this criterion is not applicable specification. UTF-8 specification: https://datatracker.ietf.org/doc/html/rfc3629 '
'The ebXML specification was launched in 1999 jointly by OASIS and the United Nations Centre for Trade Facilitation and Electronic Business (United Nations/ECE agency CEFACT), and was known as the Global XML Framework for Electronic Business. ebXML v1.0 was published in 2001, ebXML v2.0 in 2002 under the ebXML RegRep TC, and approved as ISO 15000-2 and ISO 15000-3 in 2004. A major release (ebXML v3.0) appeared in 2005, including the documents ebXML Registry Information Model (RIM) v3.0 and ebXML Registry Services and Protocols (RS) v3.0 (respectively, Part 1 and Part 2). Finally, the latest version (ebXML v4.0) was published in 2012. OASIS ebXML Registry TC reference, Announcements section: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=regrep#announcements ebxml.xml.org reference: http://ebxml.xml.org/milestones'
'The purpose of SFIA is not related to facilitating the publication of open data. Therefore, this criterion is not applicable to this specification. SFIA reference: https://sfia-online.org/en/sfia-8'
'This specification refers to the set of rules for data spaces so that they can be interoperable among them. Given that there are many data space projects with very different domains, requirements and architectures, Dataspace Protocol is inherently abstract and can be implemented and/or used in any domain as long as it fulfills the requirements. IDSA Dataspace Protocol Specification: https://docs.internationaldataspaces.org/ids-knowledgebase/v/dataspace-protocol/overview/readme'
The rules on European standardisation allow the European Commission to identify information and communication technology (ICT) technical specifications - that are not national, European or international standards - to be eligible for referencing in public procurement. This allows public authorities to make use of the full range of specifications when buying IT hardware, software and services, allowing for more competition in the field and reducing the risk of lock-in to proprietary systems. After being evaluated compliant with the regulation on standardisation 1025/2012, HTTP has been identified by Commission Implementing Decision. See: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en
"The Registered Organization Vocabulary's usability extends beyond business domains to include any organisation that gains legal entity status through a formal registration process. As a profile of the W3C Organization Ontology, the Registered Organization Vocabulary inherits the ontology’s agnostic nature, enabling flexible and interoperable representation of registered organisations while maintaining alignment with broader organisational modelling frameworks. Registered Organization Vocabulary reference: https://www.w3.org/TR/vocab-regorg/ W3C Organization Ontology reference: https://www.w3.org/TR/vocab-org/"
'Yes, the specification does encourage the creation of communities along with the sharing of their data on European platforms. Use case Integration Platform for Digital Transformation in Web Methods: https://joinup.ec.europa.eu/collection/joinup/discussion/integration-platform-digital-transformation-web-methods'
'Given the nature of all the core vocabularies developed by the UE domain, technology agnosticism is a key feature, ensuring that the specification remains adaptable and applicable across various technological platforms and environments. Therefore, the specification is technology agnostic. Core Location Vocabulary: https://interoperable-europe.ec.europa.eu/collection/semic-support-centre/solution/core-location-vocabulary/release/100'
'One of the main purpose of the DPV is to model the legal aspects of data portability, in order to link them with more technical aspects of electronic data echange. DPV suggests mechanisms for the data to be protected, and data transfers in contexts where cross-border exchange is needed. DPV specification: https://w3c.github.io/dpv/dpv/ DPV primer document: https://w3c.github.io/dpv/primer/#introduction'
'While DQV may not comprehensively cover administrative procedures, rules data, and services on its own, it can be integrated with service descriptions or metadata schemas to provide additional context about the quality of services. It can complement existing service description frameworks by incorporating data quality aspects. This integration enhances the overall understanding of services and their reliance on quality data. Data Quality Vocabulary: https://www.w3.org/TR/vocab-dqv/'
'There has not been found any assessment addressing the efficiency of the TGF specification. TGF specification: http://docs.oasis-open.org/tgf/TGF/v2.0/cs01/TGF-v2.0-cs01.html'
'ISO 639-2 was published in 1998. And this specification is reviewed every 5 years, last review was in 2021. ISO 639-2 reference: https://www.iso.org/standard/4767.html The Library of Congress Network Development & MARC 21 reference, change and release management: https://www.loc.gov/marc/languages/languagechg.html'
'The OASIS XACML Specification Technical Committee in charge of the development of XACML, operates under RF on RAND Mode of the OASIS IPR Policy. The specification is licensed on a Royalty-free and (F)RAND basis. OASIS Intellectual Property Rights (IPR) Policy: https://www.oasis-open.org/policies-guidelines/ipr/'
FTPS allows public administration to share and exchange information with others, so it helps with the visibility of data. However, FTPS is a protocol only intended to exchange the data, it doesn't help to comprehend it. FTPS IETF reference: https://tools.ietf.org/html/rfc4217
'REST architectural constraints are designed to ensure interoperability between different internet computer systems, thus rendering the communications between systems that conform to REST more efficient and easy. Consequently, REST can impact positivey in the creation of organisational interoperability agreements. REST reference: https://restfulapi.net/ R. Fielding dissertation: chapter 5. https://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm'
'While the ELI system itself does not specifically address the protection of personal data, any data processed within the EU is subject to the General Data Protection Regulation (GDPR). Therefore, this criterion is considered not applicable to this specification. ELI reference: https://eur-lex.europa.eu/eli-register/about.html GDPR Regulation (EU) 2016/679 reference: https://eur-lex.europa.eu/eli/reg/2016/679/oj'
'DNS over HTTPS (DoH) itself does not directly simplify the delivery of European public services. However, it can impact positively on the delivery of European public services as it improves security and privacy measures and facilitates interoperability between systems, which can be useful when establishing a reliable infrastructure. DoH specification: https://datatracker.ietf.org/doc/html/rfc8484'
'The specification allows user to access and maintain distributed directories information over the Internet, which reduces the administrative burden of the system administrators and the users. By ensuring the access to different directory services, while managing user identities, and implementing access control mechanisms, it fosters the implementation of digital services, supporting the principle of digital-first. LDAP IETF reference: https://tools.ietf.org/html/rfc4511'
'AMQP specification enables a secure exchange of data through security layers like TLS and SASL are employed to ensure authenticated and encrypted transport, which can be combined for enhanced security. OASIS AMQP Reference: http://docs.oasis-open.org/amqp/core/v1.0/amqp-core-complete-v1.0.pdf'
DCAT is not included in any supra-national catalogue of specifications or standards.
'The purpose of ETSI EN 319 422 is not related to multilingualism. Therefore this criterion is not applicable to this specification. ETSI EN 319 422 reference: https://www.etsi.org/deliver/etsi_en/319400_319499/319422/01.01.01_60/en_319422v010101p.pdf'
'The purpose of XML is not related to the delivery of multilingual public services. Therefore, this criterion is not applicable to the specification.'
'The purpose of UTF-8 is not related to long-term preservation of electronic records. Therefore this criterion is considered not applicable to this specification. UTF-8 specification: https://datatracker.ietf.org/doc/html/rfc3629'
"ebXML provides a set of components enabling users (data users) to store and work with any type of electronic content, fostering the visibility of administrations. As well as providing an electronic data interchange model (that is, the ebRIM and the ebRS core components), the specification contributes and promotes to some degree to the visibility of public services' implementations (see ebXML reference, Conformance section). For instance, there is the ESPD-EDM on EU procurement, which relies on the Universal Business Language (UBL) mark-up language and facilitates the promotion and support of the ESPD service. ebXML reference, Conformance section: http://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os. html#__RefHeading__53396_365468741 ESPD-EDM ebXML reference: https://docs.ted.europa.eu/ESPD-EDM/3.0.1/xml_technical_handbook.html#_adoption_of_ubl_2_3"
'At the moment of performing the assessment, the specification is not included in a catalogue of standards at EU level. XSD Reference: https://www.w3.org/TR/2012/REC-xmlschema11-1-20120405/'
The purpose of IPv6 is not related to e-accessibility. Therefore this criterion is considered not applicable specification.
'The Data Privacy Vocabularies and Controls Community Group (DPVCG) is in charge of mantaining and developing the DPV, it is a fairly open group that welcomes participation regarding extensions and refinement of terms. DPV specification: https://w3c.github.io/dpv/dpv/ DPV primer document: https://w3c.github.io/dpv/primer/#introduction'
'NUTS provides a statistical specification to address the needs for data harmonisation in terms of conducting surveys, applying policies and comparing data across the European Union. The specification should not be confused with the Administrative Territorial Unit (ATU) which is another specification representing the subdivisions of a country, mainly focuses on administrative purposes. EC reference, Regulation (EC) No 1059/2003 document: https://eur-lex.europa.eu/legal-content/EN/TXT/?qid=1405939838475&uri=CELEX:32003R1059 ATU-Joinup reference, About Administrative territorial unit type: https://joinup.ec.europa.eu/collection/eu-semantic-interoperability-catalogue/solution/administrative-territorialunit-type/about'
'The Better Regulation Guidelines and Toolbox provides specific and operational guidance to all the stakeholders implicated in developing legal framework instruments that will be used to create EU services delivery channels. Better Regulation Guidelines and Toolbox reference: https://commission.europa.eu/law/law-making-process/better-regulation/better-regulation-guidelines-and-toolbox_en Better Regulation Toolbox reference: https://commission.europa.eu/document/download/9c8d2189-8abd-4f29-84e9-abc843cc68e0_en?filename=BR%20toolbox%20-%20Jul%202023%20-%20FINAL.pdf'
'The IndexedDB specification is used in the Health360 national project, a framework designed as an integrated tool for managing and analysing data related to neuromuscular disorders. In this context, IndexedDB is utilised for data caching, making it easier to access. Additionally, this functionality can be combined with other specifications to secure cached data. Indexed Database API: https://www.w3.org/TR/IndexedDB/'
'The Core Location Vocabulary specification introduces some aspects that can contribute to data portability. In this context, for conformance with the Core Location Vocabulary, it is not mandatory that this happens in a RDF serialisation, but the exchanged format should be unambiguously transformable into RDF. Core Location Vocabulary: https://interoperable-europe.ec.europa.eu/collection/semic-support-centre/solution/core-location-vocabulary/release/100'
'RDF is included in 13 national catalogues of recommended specifications. They belong to Croatia, Cyprus, Denmark, France, Germany, Greece, Ireland, Malta, The Netherlands, Slovenia, Slovakia, Spain, and Sweden. The National Interoperability Framework (NIF) of Spain and The Netherlands is fully aligned with at least 2 out of 3 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. CAMSS List of standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards NIFO Factsheets: https://joinup.ec.europa.eu/collection/national-interoperability-framework-observatory-nifo/nifo-factsheets'
'The European Union Agency For Network And Information Security includes within a set of guidelines for implementing qualified electronic time stamps. That means that the specification, as part of this set of guidelines, is recommended when handling Timestamps. ENISA Security guidelines on the appropriate use of qualified electronic time stamps: https://security.stackexchange.com/questions/173652/how-to-timestamp-a-document-without-electronic-signature-under-eidas '
The adoption of RDF does not hamper the interoperability of systems as it was developed to improve the interrelationship between systems easing the information retrieval and data reuse. The common framework that establishes RDF allows using common parsers and exchange information between different applications avoiding interoperability hampering. The different RDF serialisation specifications help on this purpose. Additionally, the flexibility of RDF allows the creation of new vocabularies when users need/want to add new concepts without hampering interoperability.
"EuroVoc is a multidisciplinary thesaurus created for communication purposes in the European Union so, allowing customisation would dampen the specification's main purpose. Nonetheless, it is possible to create your own subsets and mappings (while maintaining the consistency of the structure and main classifications of the specification). EuroVoc: https://op.europa.eu/es/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource /dataset/eurovoc"
'XSLT specification is not designed to directly address privacy concerns aspects. Therefore this criterion is considered not applicable specification. XSLT Reference: https://www.w3.org/TR/xslt-30'
The SMP eases and fosters the discoverability of administrations data or services to others that can be administrations or other stakeholders. Easing this communication the specification allows different parties to discover others' capabilities and information to exchange documents amongst them. This fact increases the visibility of administrations' data and also improves and helps the decision-making processes. The specification: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505000
'After checking the different standard catalogues at supra-national level, there is no evidence of the inclusion of SFIA within any European catalogue of standards. ICT technical specifications: https://ec.europa.eu/growth/single-market/european-standards/ict-standardisation/ict-technical-specifications_en CENELEC and CEN search tool catalogue: https://standards.cencenelec.eu/dyn/www/f?p=CEN:105::RESET::::'
'IPsec, included in the IPv6 specification, can help prevent unauthorised changes with the AH and ESP transfer protocol. These ensure that sent data has not been altered by anyone. Therefore, data can be transferred without any change. In addition, there are ways to deny access to data by ensuring that only allowed persons can modify data. AH and ESP transfer protocols: https://www.ibm.com/docs/en/zos/2.1.0?topic=ipsec-ah-esp-protocols IPsec IONOS reference: https://www.ionos.es/digitalguide/servidores/know-how/ipsec-arquitectura-de-seguridad-para-ipv4-e-ipv6/ Access Control Lists for IPv6 reference: https://www.cisco.com/c/en/us/td/docs/routers/ios/config/17-x/sec-vpn/b-security-vpn/m_ip6-acls-xe.html#GUID-C7F3B9EF-CD1E-45E4-8A48-F301C746FAC1'
DNS is already associated to an EIRA ABB in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, DNS can define the interoperability aspects of the "Network Service" and "Network Component" ABBs of the EIRA Technical View. See: https://joinup.ec.europa.eu/solution/elis/distribution/eliscataloguev100betaxlsx
WS-Security main function is to enforce security for messages as an extension of SOAP, it can be said that is part ensuring the availability of the internal information.
'The JSON specification itself does not provide inherent features for ensuring data integrity, nonetheless, developers can incorporate security practices, cryptographic techniques, and data validation mechanisms to maintain data integrity when working with JSON. How do you secure and encrypt JSON and XML data in web communication: https://www.linkedin.com/advice/0/how-do-you-secure-encrypt-json-xml-data-web-communication Use Cases and Requirements for JSON Object Signing and Encryption (JOSE): https://www.rfc-editor.org/rfc/rfc7165.html'
'While genericode itself is not a dedicated business process modeling tool, its standardised representation of code lists and controlled values can support and enhance the modeling of business processes within organisations. By providing a common framework for representing data elements used in business processes, genericode contributes to semantic clarity, standardization, interoperability, and customisation, which are essential aspects of effective business process modeling. Code List Representation (genericode): https://docs.oasis-open.org/codelist/genericode/v1.0/os/genericode-v1.0-os.html'
'The purpose of UBL is other than ensuring the protection of personal data. Therefore this criterion is not applicable to this specification. UBL v2.3 reference: http://docs.oasis-open.org/ubl/os-UBL-2.3/UBL-2.3.html'
'Although ADMS was developed taking into account the perspective of the eGovernment System Development, it is a vocabulary that could be reused beyond this domain. It aims to ease the standardisation of assets description in assets repositories, to enhance the discoverability and reuse of assets and solutions. ADMS Specification W3C: https://www.w3.org/TR/vocab-adms/'
The standard or specification is included in 3 national catalogues. They belong to Member States which comply with at least 4 out of 5 sections of the EIF according to the NIFO factsheets. (e.g. the Netherlands, Spain, Sweden). See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
IPv4 is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, IPv4 can define the interoperability aspects of the "Network", "Networking Service", "Private Network" and "Public Network" ABBs of the EIRA Technical Application View. See: https://joinup.ec.europa.eu/solution/elis/distribution/eliscataloguev100betaxlsx
XHTML has been assessed by the CAMSS Team under the MSP scenario, which is fully compliant with the European standardisation regulation 1025/2012. However, the assessment under MSP scenario is XHTML 1.1 and in the current assessment is XHTML 1.0. XHTML 1.1 MSP scenario: https://joinup.ec.europa.eu/solution/camss-assessment-xhtml-11-msp-scenario
'In the section 6 of the specification, there is detailed information about its validation. Moreover, there exist validation services such as CEF eInvoicing, a test infrastructure that allows solution and service providers and public entities to check the compliance of their eInvoicing solution against the standard in a specific syntax: ISO/IEC 19845:2015 (UBL 2.1) or UN/CEFACT CII. CEF eInvoicing provides a ready to use testing platform, and supports the users of the CEF eInvoicing Conformance Testing service during the entire testing process. There can also be found the ESPD interoperability test bed platform to validate business rules and requirements. CEF e-invoicing conformance testing: https://github.com/ConnectingEurope/eInvoicing-EN16931/releases/tag/validation-1.3.8 ESPD Test bed: https://github.com/OP-TED/ESPD-EDM/wiki/Validation'
'The purpose of the specification is not related to the facilitation of organisational interoperability agreements, therefore this criterion is not applicable to this specification. ETSI TS 119 614-1 reference: https://www.etsi.org/deliver/etsi_ts/119600_119699/11961401/01.01.01_60/ts_11961401v010101p.pdf'
'The European collaborative platform Joinup shares a wide range of RDF-related solutions, and also hosts communities sharing their knowledge and holding discussions around RDF serialization methods and data processing. RDF Discussion forum in Joinup https://joinup.ec.europa.eu/search?keys=rdf&sort_by=relevance&f%5B0%5D=type%3Adiscussion'
PAdES and PAdES Baseline profile is referenced in the ETSI collection at the European Platform Joinup. Moreover, it can be found for free at ETSI’s webpage See: https://joinup.ec.europa.eu/solution/electronic-signatures-and-infrastructures-esi-pdf-advanced-electronic-signature-formats-pades-part-7 https://www.etsi.org/deliver/etsi_ts/103100_103199/103172/02.02.02_60/ts_103172v020202p.pdf
'OAIS is recommended by the France Natioanl Catalogue of IT standards. France national catalogue of IT standards: https://www.numerique.gouv.fr/uploads/Referentiel_General_Interoperabilite_V2.pdf'
'DNS over HTTPS (DoH) primarily focuses on securing the DNS (Domain Name System) communication by encrypting DNS queries and responses. While DoH ensures the confidentiality and integrity of DNS transactions, it does not directly address data processing accuracy beyond the DNS layer. Even so, concepts like mitigation of DNS spoofing and authentication of DNS resolvers help improve data processing accuracy as it ensures the security and authenticity of every data exchange. DoH specification: https://datatracker.ietf.org/doc/html/rfc8484'
XML is used to encode all communications between web services. Therefore, it fosters the visibility and comprehensibility of public administrations data and services. See: https://esentool.ted.europa.eu/
'UTF-8 itself does not guarantee the authenticity and authentication of the agents involved in data transactions. Authenticity and authentication can be addressed through separate mechanisms, such as digital signatures, encryption, and authentication protocols. UTF-8 specification: https://datatracker.ietf.org/doc/html/rfc3629 UTF-8 impact on authentication: https://www.ibm.com/docs/en/sva/8.0.0.4?topic=concepts-utf-8-impact-authentication'
There are many free online tools that perform numerous checking processes in order to verify the conformity of the ETSI Advanced Electronic Signatures which include PAdES. PAdES conformance testing: https://signatures-conformance-checker.etsi.org/pub/index.shtml
'The PROV family of documents has established itself as a key reference for representing provenance on the web. Its acceptance and usage continue to grow as more organizations recognize the value of capturing and utilizing provenance information to improve data quality, transparency, and decision-making processes. PROV WG Charter: https://www.w3.org/2011/01/prov-wg-charter '
The SMP is aimed to ease the identification of parties in data exchange. This data exchange can be part of a public service delivered by European Institutions. By easing the discoverability and the connection between parties, the specifications can help and foster the delivery of European Public Services including multilingual ones. SMP OASIS reference: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505009
'The IPv4 specification is mentioned in the "Alternative Bearers for Rail" project. The Shift2Rail initiative has developed a new Adaptable Communication System (ACS) to overcome shortcomings in current European rail control applications. In the project, IPv4 is analised, and some strategies for allowing the IPv4 and IPv6 interworking are proposed. "Alternative Bearers for Rail" project: https://cordis.europa.eu/project/id/101014517'
There is no national or European platform with the specification CAdES (ISO 14533-1:2014) available for free. However, there are some free documents in Joinup that covers CAdES digital signatures - Testing Conformance and Interoperability. CAdES Joinup reference: https://joinup.ec.europa.eu/solution/etsi-tr-119-124-series-electronic-signatures-and-infrastructures-esi-cades-digital-signatures
'There has not been found any community sharing their data and knowledge of ISO19944-1 in national nor in European platforms. ISO/IEC 19944-1 specification: https://www.iso.org/standard/60545.html'
'HTTPS verifies the integrity of transmitted data. By using cryptographic techniques, it ensures that the data remains unchanged during transit. If any tampering or modification occurs, the integrity check fails, and the connection is terminated or marked as compromised. HTTPS specification: https://tools.ietf.org/html/rfc2818'
'The purpose of UDDI is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification. UDDI OASIS reference: https://www.oasis-open.org/standard/uddi/'
'ISO 19941 defines general requirements for interoperability and portability related to cloud services thus, it does not mention extension of the specification. Even so, extension would be most likely possible as long as it does not interfere with the main requirements of ISO 19941. ISO 19941: https://www.iso.org/obp/ui/en/#iso:std:iso-iec:19941:ed-1:v1:en '
'IPv4 is maintained and developed by IETF which is an international community developing open standards. In addition, it has support from the different Regional Internet Registries (RIRs) in order to ensure the proper development beyond borders. IETF organisation: https://www.ietf.org/ American Registry for Internet Numbers: https://www.arin.net/ Regional Internet Registry for Europe: https://www.ripe.net/'
'DPV has not been found to be included in any open repository or catalogue of standards at European level. DPV specification: https://w3c.github.io/dpv/dpv/ DPV primer document: https://w3c.github.io/dpv/primer/#introduction '
There are already studies and documentation assessing the specification in terms of effectiveness and efficiency. The topics are different, for instance, there is a study assessing the capabilities of XML Schema for the defense against Signature Wrapped Attacks. Another field of documentation is the XML Schema clustering, and its effectiveness for the improvement of user results. See: https://www.researchgate.net/publication/252053794_On_the_effectiveness_of_XML_Schema_validation_for_countering_XML_Signature_Wrapping_attacks https://www.researchgate.net/publication/254858700_XML_schema_matching_balancing_efficiency_and_effectiveness_by_means_of_clustering
The Working Group in charge of developing the specification initially provides a light-weight maintenance plan . However, it does not consist in a process for a long-term maintenance of the specification. For instance, no development or review process are described, and no versioning policy is specified.
'The Library of Congress is de facto national library of the United States, and altogether with the ISO ensures the maintenance of this specification. However, ISO 639-2 does not encourage the creation of communities nor promotes the sharing of data and results in any national platform. The Library of Congress reference: https://www.loc.gov/standards/iso639-2/'
"ISO 3166-1 consists of a collection of codes for the names of countries, dependent territories and special areas of geographical interest. Although this collection can be mapped against this same collection to test the specification's implementation conformance, the specification does not publicly provide conformance testing requirements (see ISO 3166-1 reference, official preview documentation); the user may opt for their own techniques or for third-party software conformance services. ISO 3166-1 reference, official preview documentation: https://www.iso.org/obp/ui/#iso:std:iso:3166:-1:ed-4:v1:en"
The IETF is a consensus-based group, and authority to act on behalf of the community requires a high degree of consensus and the continued consent of the community. The process of creating an Internet Standard is straightforward: a specification undergoes a period of development and several iterations of review by the Internet community and revision based upon experience, is adopted as a Standard by the appropriate body... and is published. In practice, the process is more complicated, due to (1) the difficulty of creating specifications of high technical quality; (2) the need to consider the interests of all of the affected parties; (3) the importance of establishing widespread community consensus; and (4) the difficulty of evaluating the utility of a particular specification for the Internet community. The goals of the Internet Standards Process are: - technical excellence - prior implementation and testing; - clear, concise, and easily understood documentation; - openness and fairness; and - timeliness The goal of technical competence, the requirement for prior implementation and testing, and the need to allow all interested parties to comment all require significant time and effort. The Internet Standards Process is intended to balance these conflicting goals. The process is believed to be as short and simple as possible without sacrificing technical excellence, thorough testing before adoption of a standard, or openness and fairness. See:https://www.ietf.org/standards/process/
'The EN 303 645 specification facilitates business modeling, as the specification can be deployed into any architecture for consumer IoT in a home environment. The evidence for this is that consumer IoT devices are collections of hardware and software components, with physical or network interfaces, typically connected to online or local services. EN 303 645 reference, Annex A Basic concepts and models: https://www.etsi.org/deliver/etsi_en/303600_303699/303645/02.01.01_60/en_303645v020101p.pdf'
At the time of elaborating this assessment, TLS 1.2 does not foster the creation of innovative solutions. In 2018 the creation of TLS 1.3 updated and improved the older version. So the focus of creating innovative solution is focused on the latter.
'MIME (Multipurpose Internet Mail Extensions) itself does not enable the implementation of features to guarantee data accuracy. Data accuracy may be addressed at the application or system level through, validation, and quality assurance practices. MIME specification: https://tools.ietf.org/html/rfc2045 S/MIME specification: https://www.rfc-editor.org/rfc/rfc5751.html'
'ETSI’s standards-making process has been clearly defined after years of experience. The organisation has adopted the open approach which means direct participation and consensus as a basis to develop standards. All the stakeholders have the opportunity to participate directly in the process of standardisation through the technical committees created to develop ETSI’s technical specifications and standards. The decision-making process includes a public review, where stakeholders involved can provide technical feedback to enhance and maximize the quality and accuracy of the standards. ETSI standard making: https://www.etsi.org/standards/standards-making'
LegalRuleML extends RuleML and provides a framework that can help to reduce the gap between semantics, natural language and text description. In this sense, the specification can help to create and model constitutive rules, technical rules, and prescriptive rules enhancing the data exchange of legal resources such as documents defining property aspects, contracts and others. Providing a common framework for this purpose fosters the trustworthy data exchange between administration and stakeholders. LegalRuleML reference: http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/legalruleml-core-spec-v1.0.html
'SFIA is intended to serve as a device to represent skills and competences of any ICT professional workforce. There is no possibility of partial implementation of the specification, as SFIA has a single purpose. SFIA reference: https://sfia-online.org/en/sfia-8'
'ETSI EN 319 532-3 is to ensure a consistent form of service across Europe, especially concerning the form of evidence provided, to maximize interoperability even between e-mail domains governed by different policy rules. ETSI EN 319 532-3 reference: https://www.etsi.org/deliver/etsi_en/319500_319599/31953203/01.02.01_60/en_31953203v010201p.pdf'
'Within the DoH protocol, information (in this case, DNS query responses) is effectively provided once and then reused as necessary, leveraging caching mechanisms to optimize web browsing experience and network efficiency while maintaining privacy and security. In section 5.1 of the specification, Cache Interaction is explained, where caching mechanisms can be filtered and adjusted depending on the assigned HTTP freshness lifetime. Section 5.1 DoH specification: https://datatracker.ietf.org/doc/html/rfc8484#section-5.1'
"The motivation of DPV is to provide a 'data model' or a 'taxonomy' of concepts that act as a vocabulary for the interoperable representation and exchange of information about personal data and its processing. DPV specification: https://w3c.github.io/dpv/primer/"
'EN 16234-1 e-CF could be used in a multilingual context beyond its original purpose, which is the representation of a common and standardised e-Competence Framework at European level. CEN reference, CEN/TC 428 - ICT Professionalism and Digital Competences (Published standards), EN 16234-1 e-CF: https://standards.cencenelec.eu/dyn/www/f?p=205:110:0::::FSP_PROJECT:67073&cs=15E62ED24D608A5F10D6BEE8E6D50FA10'
'The specification is used for the certification of time-stamps, which provides information about the creation or modifications of certain documentation or data, it can be used when archiving electronic records as a manner to preserve the integrity of such data. Therefore, the IETF 3161 Time Stamp Protocol (TSP) fosters the preservation of electronic documents by providing a mechanism for clearly identify time stamps for these electronic documents. TSP IETF reference: https://tools.ietf.org/html/rfc3161'
'Although there is no platform to test ebXML specification implementations, some papers addressing the testing can be found. The "Conformance Testing and Certification Framework" document offers a guide on how to test ebXML. "Conformance Testing and Certification Framework" document: https://www.nist.gov/system/files/documents/itl/ssd/is/ebxml-test-framework.pdf ebXML RegRep OASIS reference: https://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html'
'The AKN4EU specification itself does not provide specific mechanisms for the secure exchange of data. However, it can be used as part of a broader approach to enable secure data exchange. AKN4EU reference: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/akn4eu'
'MIME can be found in the European collaborative platform Joinup. where it is the object of discussions about its implementation and the creation of ad-hoc solutions. MIME in joinup: https://joinup.ec.europa.eu/search?keys=mime&sort_by=relevance&f%5B0%5D=type%3Adiscussion'
'ADMS is used as the basis for the ADMS-AP, which is the backbone of the European cross-border platform for the reuse of interoperability solutions Joinup. ADMS on Joinup: https://joinup.ec.europa.eu/solution/asset-description-metadata-schema-adms/about'
'A group related to the Dublin Core was found which main purpose was the preservation, but their goals and records are non existant. DCMI About: https://www.dublincore.org/about/ DCMI Preservation Group: https://www.dublincore.org/groups/preservation/'
'The purpose of SMP seems not to be related to long-term preservation of electronic records. Moreover, no information has been found to answer positively or negatively to this criterion. Therefore, this criterion is considered not applicable to this specification. SMP OASIS reference: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505009'
CAMSS Assessment of XACML EIF Scenario v1.0.0
'At present, the publiccode.yml specification is not included within the Open Software Observatory (OSOR) in the Interoperable Europe Portal. It is not included as solution, which is understandable given that it is still in an early stage of adoption. However, considering its potential to support European interoperability initiatives and align with frameworks like the Interoperable Europe Act, the specification could be valuable for future EU projects. It could eventually serve as a foundational component for cataloguing software solutions across European repositories, enhancing discoverability and encouraging reuse at a cross-border level. Publiccode.yaml documentation: https://docs.italia.it/italia/developers-italia/publiccodeyml-en/en/master/index.html'
As one of the official European Standardisation Organisation, ETSI standards are compliant with the European Standardisation Regulation 1025/2012. See: https://www.etsi.org/about/etsi-in-europe
'[To improve] The specification is being developed publicly using Github, where the different users can participate. There is documentation available that is updated in a regular basis whenever new updates are made and published. However, there is not a big community or organisation giving active active support, so they act in a best-effort manner. Publiccode.yaml Github: https://github.com/publiccodeyml/publiccode.yml Publiccode.yaml Github Issues: https://github.com/publiccodeyml/publiccode.yml/issues'
The purpose of TLS 1.2 is not related to the fostering of publications of data as Linked Open Data. Therefore this criterion is considered not applicable to this specification.
HTTP is publicly available for implementation and use, and therefore for everyone to study, for free on IETF's webpage. See: https://tools.ietf.org/html/rfc2616
'TOSCA conformance can be manually assessed by following the TOSCA schema (CSAR) and the syntax and semantics defined in section 14 of the specification. Besides, the specification conformance requirements can be automatically measured via the OASIS Test Assertion Markup Language, as exemplified in TOSCA Github (see Github reference). TOSCA reference: https://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.3/os/TOSCA-Simple-Profile-YAML-v1.3-os.html TOSCA-Github reference: https://github.com/oasis-open/tosca-community-contributions/tree/master/tests'
'The ELI system does not inherently provide an access control mechanism. Therefore, this criterion is considered not applicable to this specification. ELI reference: https://eur-lex.europa.eu/eli-register/about.html'
'OAS is independent of any specification and can be implemented without relying on other technologies. OAS specification: https://spec.openapis.org/oas/latest.html#openapi-specification OAS in Github: https://github.com/OAI/OpenAPI-Specification/#participation'
'The purpose of IPv4 is not related to long term preservation of electronic records. Therefore, this criterion is considered not applicable to this specification. IPv4 IETF: https://www.rfc-editor.org/rfc/rfc791'
Even though the purpose of the SVG is not the availability of digital services from the administration to the stakeholders, the usage of SVG graphics to represent the information contained in Public Administration webpages can help to do so. It can help the understanding of the information provided allowing all people to access electronic public services. Moreover, the specification includes a few comments on how to improve the accessibility to the content making it more discoverable and accessible. SVG W3C reference: https://www.w3.org/TR/SVG11/access.html
'The specification is included in the EAR/PILAR methodology supported by ENISA, which includes an European level covering privacy aspects. EAR/PILAR methodology: https://www.enisa.europa.eu/topics/risk-management/current-risk/risk-management-inventory/rm-ra-tools/t_EAR_Pilar.html CSV Reference: https://datatracker.ietf.org/doc/html/rfc4180'
'As stated in the specification home page and in Joinup, the application is under development and has not reached a major release v2.0. Nonetheless, the new version of the specification (v1.2) is available since 06 June 2023. WAI-ARIA reference: https://www.w3.org/TR/wai-aria/ WAI-ARIA roadmap reference: https://www.w3.org/WAI/ARIA/roadmap Joinup WAI-ARIA reference: https://joinup.ec.europa.eu/collection/w3c-standards-and-technical-reports/solution/using-wai-aria-html/about'
'EN 16234-1 e-CF is a self-contained language intended to represent a common European description of the knowledge, skills and competences of the ICT professional workforce. In this sense, the specification allows relevant information to be reused. There is no evidence of any relation between e-CF and the Once-Only Principle (OOP). CEN reference, CEN/TC 428 - ICT Professionalism and Digital Competences (Published standards), EN 16234-1 e-CF: https://standards.cencenelec.eu/dyn/www/f?p=205:110:0::::FSP_PROJECT:67073&cs=15E62ED24D608A5F10D6BEE8E6D50FA10'
'While DoH does not directly enable or expose interfaces for accessing public administration services, it may be used by applications to perform DNS resolution to reach public administration services. DoH facilitates secure communication between clients (such as web browsers or applications) and servers hosting the services. HTTPS, in particular, ensures secure and encrypted communication, providing confidentiality and integrity for the exchanged data, which would indirectly help by making API access more secure and reliable or bypass DNS-based filtering or blocking DoH specification: https://datatracker.ietf.org/doc/html/rfc8484'
'YAML is supported and developed by the YAML organization, and by the YAML Language Development Team. The development team is in charge of the YAML releases and updates, and also sets the terms of the RFC process. Moreover, in github there is published content to understand how the specification works, as well as tools to test YAML, among other things. YAML Language Development Team: https://yaml.org/spec/1.2.2/ext/team/'
'No project covering privacy and using CPOV, has been found. Therefore this criterion is considered not applicable to this specification. CPOV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-organisation-vocabulary'
By allowing public administration to have an online domain where they can publish all types of administrative data, documents, videos, etc, the specification reduces the administrative burden. XHTML W3C reference: https://www.w3.org/TR/xhtml1/
'The Core Location Vocabulary specification is developed by SEMIC, an European organisation. Therefore, the specification can be considered a European standard. Core Location Vocabulary: https://interoperable-europe.ec.europa.eu/collection/semic-support-centre/solution/core-location-vocabulary/release/100'
XSLT is a language for transforming XML documents facilitating the process of it. Consequently, the implementation of eSignatures reduces the administrative burdens of the administration.
As Internet Protocol Stack, IPv4 has been selected by a wide range of European public administrations in order to ensure the data exchange between its different stakeholders. Therefore, the adoption of IPv4 fosters the administration's data visibility and eases the decision-making process.
'The data structure of YAML could facilitate the understanding in different languages. Despite this, the main purpose of YAML is not to be used in multilingual context. YAML specification: https://yaml.org/spec/1.2.2/'
'ETSI TS 119 612 can contribute to data portability by ensuring that digital identity information can be used and trusted across different digital services and borders. This ensures that citizens can easily access services, such as online government services, without the need to recreate their identity information each time. ETSI TS 119 612: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf'
'The specification is not tied to any specific technology or implementation, allowing it to be used in a wide variety of technology environments. ODRL is expressed using standard data formats such as XML and JSON. W3C specification: https://www.w3.org/TR/odrl-vocab/#vocab-core'
'10 Member States are recommending LDAP in their ICT National Catalogues. This Member States are Austria, Croatia, France, Germany, Greece, Malta, Netherlands, Spain, Sweden and Cyprus. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards '
'DCAT is an RDF vocabulary for representing data catalogues that allows data owners to provide metadata about the datasets they publish. By describing catalogues, datasets and resources, a publisher makes them easily searchable and discoverable. Following the previous statement it can be said that DCAT can enable digital service delivery channels. DCAT (v2.0.0) reference: https://www.w3.org/TR/vocab-dcat-2/ '
'There has notbeen found any project including RDF covering privacy aspects neither at national, nor at European level. RDF primer document: https://www.w3.org/TR/rdf11-primer/'
'By allowing public administration to share information with others in a specific format, it fosters the comprehensibility of data (e.g. Administrative rules, processes etc.) and facilitates public administrations decision-making. MIME reference: https://tools.ietf.org/html/rfc2045'
"DAPS can simplify the delivery of European public services as it offers a technique to modulate access to certain data in International Data Spaces, which aligns with Europe's vision of data. DAPS: https://github.com/International-Data-Spaces-Association/IDS-G/tree/main/Components/IdentityProvider/DAPS"
'While OpenTelemetry is not directly related to providing an access control mechanism, there are some provisions regarding access control mechanisms. The Collector supports running as a custom user and should not be run as a root/admin user. In fact, for the majority of use-cases, the Collector should not require privileged access to function. If for some reason access requirements are needed, component developers must document the requirements and why they are placed. OTel Security Best Practices: https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/security-best-practices.md'
'WSDL is a specification developed by the World Wide Web Consortium (W3C), which is an international standards organization responsible for many web-related standards. While WSDL itself is not a European Standard, its usage may be referenced or recommended in European initiatives and frameworks, such as the European Interoperability Framework (EIF), which provides guidelines for achieving interoperability among European public services. European Interoperability Framework: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/european-interoperability-framework-detail'
'OAS has been found to be used in the Research Infrastructure for Science and Innovation Policy Studies (named as RISIS) Where OpenAPI takes part in a project aiming to automatize query-centric APIs for accessing to Linked Data. Automatic Query-centric API for Routine Access to Linked Data: https://iswc2017.semanticweb.org/wp-content/uploads/papers/MainProceedings/430.pdf RISIS webpage: https://www.risis2.eu/about/'
"In accordance with Common Patent Policy for ITU-T/ITU-R/ISO/IEC the ISO 3166-1 is licensed under royalty-free basis. Although there are terms included that allow patent holder to apply specific costs. It is defined in IPR disclosures that can be found at ISO's webpage. ISO patents: https://www.iso.org/iso-standards-and-patents.html ISO standards and patents IPR database: http://isotc.iso.org/livelink/livelink/13622347/Patents_database.xls?func=doc.Fetch&nodeId=13622347 "
This Core Vocabulary was developed in 2014 and has good acceptance in the European Union. The CPSV-AP is already being used by public administrations in Belgium, Italy, Finland and Estonia to create a cross-border federated catalogue of public services. Moreover, it is the basis of the European Catalogue of Services CPSV-AP reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-service-vocabulary-application-profile CPSV-AP used in EU: https://www.ceps.eu/wp-content/uploads/2019/06/NO0119341ENN.en_.pdf Catalogue of Services: https://ec.europa.eu/isa2/catalogue-services-helping-eu-countries-catalogue-and-describe-public-services_en
'DCAT has been developed to facilitate the publication of linked open data by the W3C Government Linked Data Working Group.The specification is an RDF vocabulary for representing data catalogues that allows data owners to provide metadata about the datasets they publish. By describing catalogues, datasets and resources, a publisher makes them easily searchable and discoverable. In fact, DCAT is used for the publication of datasets in linked open data portals at European scale (European Data Portal). DCAT reference: https://www.w3.org/TR/vocab-dcat-2/ DCAT-AP & European Data Portals reference: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/dcat-application-profile-data-portals-europe'
Xforms was updated to version 2.0 in 2010 and has the full support from the W3C group, an international community where Member organizations, a full-time staff, and the public work together to develop Web standards. Xforms 2.0 W3C reference: https://www.w3.org/community/xformsusers/wiki/XForms_2.0
The specification has been evolved as part of its lifecycle and the previous version has been the basis for European Solutions regarding the development of interoperable services. This fact ensures that the specification reaches a proper market acceptance for its implementation for the development of products and services. The specification: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505009
'ETSI TS 119 612 specifies a format and mechanisms for establishing, locating, accessing and authenticating a trusted list which makes available trust service status information so that interested parties may determine the status of a listed trust service at a given time as well as enabling data portability between systems/applications. It defines the format and semantics of a TL as well as the mechanisms for accessing TLs. It also provides guides for locating and authenticating TLs. ETSI TS 119 612 specification: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf '
The Data Collections API specification covers a specific area of application, guidelines for the data collections exchange through APIs; that is actually not covered by any other technical specification being under consideration to become a European standard. This conclusion has been drawn from the examination of all the programming mandates addressed to CEN, CENELEC and ETSI to the date, CEN’s webpage , CENELEC’s webpage , CEN-CENELEC’s webpage ICT section , the EC Information Providers Guide, Directive (EU) 2016/2102 of the European Parliament and of the Council of 26 October 2016 on the accessibility of the websites and mobile applications of public sector bodies , the standards and tools for exchange and processing of actionable information inventory of ENISA and the ENISA Programming Document 2018-2020
"The W3C organisation has been developing the Indexed Database API since 2015 and has released three versions. Since then, the organisation has published all the information about the specification, which can be found on its website. In addition, the point of the specification is to preserve persistent data on users' devices, and this is available in almost all web browsers. Indexed Database API: https://www.w3.org/TR/IndexedDB/ IndexedDB RXdB: https://rxdb.info/articles/localstorage-indexeddb-cookies-opfs-sqlite-wasm.html"
'The purpose of CPOV is not related to e-accessibility. Therefore, this criterion is considered not applicable to this specification. CPOV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-organisation-vocabulary'
The rules on European standardisation allow the European Commission to identify information and communication technology (ICT) technical specifications - that are not national, European or international standards - to be eligible for referencing in public procurement. This allows public authorities to make use of the full range of specifications when buying IT hardware, software and services, allowing for more competition in the field and reducing the risk of lock-in to proprietary systems. After being evaluated compliant with the regulation on standardisation 1025/2012, FTP has been identified by Commission Implementing Decision. See: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en
'The Joinup platform holds a community of developers and government officials that discuss the implementation of the TGF. Moreover, there has been done some webinars on the use of the framework for the improvement of European digital public services. Rolling Plan for ICT standardisation: https://joinup.ec.europa.eu/collection/rolling-plan-ict-standardisation/e-government'
'IEEE Working Group may not directly engage in community initiatives, but it lays a strong foundation by promoting collaboration and knowledge sharing through its working groups and conferences. This approach might help to build communities around these technologies and facilitates collaboration among stakeholders, ultimately encouraging open data sharing and interoperability at EU level. IEEE Working Group Projects: https://www.ieee802.org/3/'
'The specification actively promotes and supports comprehensibility of data models, easing the modelling of business processes. GraphQL FAQ Site: https://graphql.org/faq/#why-should-i-use-graphql'
"The Industry Specification Groups (ISG), a working group in ETSI, are encharged of the development and maintenance of the NFVI specification. ISG members and ISG participants cooperate in developing and maintaining this specification, and contribute to the report writing. Participation is open prior a registration process and a financial contribution (see ETSI Directives' Rules of Procedure). ETSI Directives, Rules of Procedure: https://portal.etsi.org/Resources/ETSI-Directives ISG NFVI reference, NFV Member Agreement and NFV Participant Agreement: https://portal.etsi.org/TB-SiteMap/NFV/NFV-List-members"
There are several studies and documentation analysing the use of the IETF Time Stamp Protocol with different purposes and putting emphasis on its usage as an efficient way to implement Time-stamp services. Design and Implementation of a RFC3161-Enhanced Time-Stamping Service: https://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.101.7115&rep=rep1&type=pdf Study about the impementation of Secure Time Stamp Device: https://www.sans.org/reading-room/whitepapers/vpns/analysis-secure-time-stamp-device-746
The specification includes requirements for the alignment with relevant regulations at European level such as eIDAS, GDPR, Cybersecurity Act, etc. Ensuring that the development of policies and laws is aligned with the main legal acts, including the interoperability ones, the Better Regulation Toolbox supports the establishment of public services and tools fostering data portability. Better Regulation Toolbox reference: https://ec.europa.eu/info/sites/info/files/better-regulation-toolbox_2.pdf
eDelivery SMP 1.10 is an open specification based on the OASIS’s standard SMP 1.0. As SMP is an agnostic standard, eDelivery SMP 1.10 inherits this property. Thus, it can be reused in any business domain requiring metadata management and exchange.
IPSec is a set of open standards and protocols for securing the exchange of data packets over a computer network. Therefore, it ensures the trustworthy data exchange between different stakeholders.
The specification does not include security features to foster secure and trustworthy data exchange between administrations and stakeholders. SVG W3C reference: https://www.w3.org/TR/SVG11/
'The purpose of the Core Criterion and Core Evidence Vocabulary is not related to the availability of interfaces with internal information systems. Therefore, this criterion does not apply to this specification. Core Criterion and Core Evidence Vocabulary reference (v1.0.0): https://joinup.ec.europa.eu/release/core-criterion-and-core-evidence-vocabulary-v100 '
DCAT-AP is an RDF vocabulary for representing data catalogues that allows data owners to provide metadata about the datasets they publish. By describing catalogues, datasets and resources, a publisher makes them easily searchable and discoverable. In fact, DCAT-AP is used for the publication of datasets in linked open data portals at a National (e.g. ) and European scale ( European Data Portal) See: https://joinup.ec.europa.eu/solution/dcat-application-profile-data-portals-europe/releases
CAMSS Assessment of IPSec EIF Scenario v2.0.0
'Core Criterion and Core Evidence Vocabulary has a good market acceptance. Some parts of this vocabulary have been used to develop European solutions, for example, ESPD-EDM (European Single Procurement Document - Exchange Data Model) which is the technical representation of the legal European Single Procurement Document. It is used to support interoperability between ESPD services provided all over Europe. Additionally, other projects/initiatives like The Once-Only Principle (TOOP), and the eCertis are based on the CCCEV. ESPD documentation: https://docs.peppol.eu/pracc/espd/edm/ Core Criterion and Core Evidence Vocabulary reference (v1.0.0): https://joinup.ec.europa.eu/release/core-criterion-and-core-evidence-vocabulary-v100 TOOP: http://wiki.ds.unipi.gr/display/TOOP/Core+Vocabularies+and+Application+Profiles eCertis: https://ec.europa.eu/tools/ecertis/#/about '
'In order to meet the standard protocol needs, LDAP can not be customised. LDAP IETF reference: https://tools.ietf.org/html/rfc4511'
"The specification is associated with Controlled Vocabulary Data, Data Model, Data Syntax, Forms Structure, Hash Code, Metadata from Semantic view and eProcurement Awarding Component and eProcurement Awarding from the Technical View in EIRA ABB's in the EIRA Library of Interoperability Specifications (ELIS). EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/v501"
'OData services return URLs to identify resources that may be later requested by clients. Where possible, data reusability increases by exploiting the information found in the route part of the URL, or by easing datasets management. However, data reusability might be limited. There is no evidence of any European solution confirming this aspect. OData reference, 6.1 Query Option Extensibility: http://docs.oasis-open.org/odata/odata/v4.0/errata03/os/complete/part1-protocol/odata-v4.0-errata03-os-part1-protocol-complete.html#_Toc453752211'
'WAI-ARIA is meant to augment semantics in languages such as HTML5 and SVG2, or to serve as an accessibility enhancement technology in other languages that do not specifically include support for ARIA. In this sense, customisation may evolve faster than other web host standards, enabling additional digital service delivery channels. WAI-ARIA reference, section 1.4: https://www.w3.org/TR/wai-aria/'
'The ACL functionality in IPv6 helps to establish an access control. Access lists determine what traffic is blocked and what traffic is forwarded at device interfaces and allow filtering based on source and destination addresses, inbound and outbound to a specific interface. Each access list has an implicit deny statement at the end. IPv6 ACLs are defined and their deny and permit conditions are set using the ipv6 access-list command with the deny and permit keywords in global configuration mode. Access Control Lists for IPv6 reference: https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst2960xr/software/15-2_5_e/configuration_guide/b_1525e_consolidated_2960xr_cg/configuring_ipv6_acls.html'
'The purpose of YAML is not related to the authenticity and authentication of the roles agents involved in the data transactions. Therefore, this criterion is considered not applicable to this specification. YAML specification: https://yaml.org/spec/1.2.2/'
CAMSS Assessment of ETSI TS 119 512 EIF Scenario v1.0.0
SMP can be implemented in any platform, and it is independent of any technology. The specification: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505000
'While it uses the EU’s General Data Protection Regulation (GDPR) as a guiding source for the creation and interpretation of concepts, the ambition and scope of DPV is to provide a broad globally useful vocabulary that can be extended to jurisdiction or domain specific applications. '
'The specification is a protocol focused on the transaction of data, specifically on the certification of certain data, information or documents which either exist or not. Despite its relation to the data exchange, the specification is not related to data portability itself, but the trustworthy data exchange amongst Systems and European Public Services. TSP IETF reference: https://tools.ietf.org/html/rfc3161'
'The SAML 2.0 specification is designed with extensibility in mind. Extensibility in SAML allows for the addition of new elements and attributes within the confines of the existing XML schema to accommodate specific use cases, environments, or new functionalities without altering the core specification. SAML 2.0 Reference: http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-tech-overview-2.0.html'
LDAP can be used independently of any other technical specifications or operating system. However, it is often used to complement Active Directory (AD) as a directory services protocol. LDAP IETF reference: https://tools.ietf.org/html/rfc4511 LDAP with Active Directory: https://www.solarwindsmsp.com/blog/difference-between-ldap-ad
'ADMS is included in the national catalogue of Slovakia. The National Interoperability Framework (NIF) of this Member State is fully aligned with at least 2 out of 3 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. Slovakia’s Catalogue: https://www.mirri.gov.sk/sekcie/informatizacia/governance-a-standardy/standardy-isvs/index.html NIFO factsheets: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public-administration-factsheets-2022 CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards '
'TSP enables digital service delivery channels in many ways among which we could highlight the maintenance of the data integrity, facilitation of compliance to regulaory requirements or enhancing security in transactions, that is why they are used in document and records management system. The Ministry of economic and transformation Digital has a TSA, which is synchronized with the royal navy Observatory. One of the services available in the TSA is "resellado request", which preserves the longevity of the validity of the seals generated on the official or transactions, guaranteeing security and trustworthy of data. TSP IETF reference: https://www.rfc-editor.org/rfc/rfc3161 "Beijing platform for time-stamping TSA" reference: https://administracionelectronica.gob.es/ctt/tsa/infoadicional'
'There is a TLS Working Group Github where this community focuses on the development, refinement, and maintenance of the TLS 1.3 specification. The repository provides access to draft specifications, tools for building the drafts, and guidelines for contributing to the project. TLS Working Group Github Reference: https://github.com/tlswg/tls13-spec TLS 1.3 Reference: https://www.rfc-editor.org/rfc/rfc8446.html'
'By using digital signatures, presents in ETSI TS 119 612, data can be shared securely, ensuring that the information exchanged between public administrations or organisations and citizens has not been modified. This mechanism provides a secure way to exchange information, guaranteeing that data shared for the delivery of public services is both secure and trustworthy. ETSI TS 119 612: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf'
'OTel is not included in any national catalogue of recommended specifications whose Member State NIF has a high performance on interoperability according to NIFO factsheets. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards 2023 NIFO factsheets: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital\x02publicadministration-factsheets-2023'
'There are no requirements for compliance and conformance analysis testing defined by the SFIA specification. SFIA reference: https://sfia-online.org/en/sfia-8'
Xforms 2.0 is a business domain agnostic specification that can be reused in a cross-domain way. Xforms 2.0 W3C reference: https://www.w3.org/community/xformsusers/wiki/XForms_2.0
The specification does not foster the publication of data as linked open data since it is dedicated to the standardisation of processes within a project from a management perspective and not related to data publication. Nonetheless, the methodology can help to establish priorities and enhance how services or products are oriented to the linked open data. OpenPM2 specification reference: https://op.europa.eu/en/publication-detail/-/publication/ac3e118a-cb6e-11e8-9424-01aa75ed71a1/language-en/format-PDF/source-83307127 5-star linked open data: https://www.w3.org/DesignIssues/LinkedData.html
"GraphQL is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, GraphQL will define the interoperability aspects of the Virtual DataSet ABB of the EIRA Semantic View, as well as the Data Exchange Service, Data Exchange Component, Data Management Service, Data Management Component, 'Data Extraction, Transformation, and Loading Service', 'Data Extraction, Transformation, and Loading Component', Knowledge Discovery Component Service, Knowledge Discovery Component of the EIRA Technical View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/v501"
'The specification performs effectively in accordance with the TR-ESOR middleware techincal guidelines. ETSI TS 119 512 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.02_60/ts_119512v010102p.pdf TR-ESOR Preservation of Evidence of Cryptographically Signed Document: https://www.bsi.bund.de/EN/Service-Navi/Publications/TechnicalGuidelines/TR03125/TechnicalGuidelines_03125_node.html'
'As it is specified in the section 2 of the specification, it has defined conformance as a requirements to be followed. ADMS Reference, Conformance section reference: https://www.w3.org/TR/vocab-adms/#conformance'
'The Asset Administration Shell (AAS) is the standardised digital representation of an asset. The AAS may be the logical representation of a simple component, a machine or a plant at any level of the equipment hierarchy. In this sense the specification can contribute to the comprehensibility of the manufacturing processes and the generated data to the administrators. Details of the Asset Administration Shell (AAS) https://industrialdigitaltwin.org/en/wp-content/uploads/sites/2/2024/06/IDTA-01001-3-0-1_SpecificationAssetAdministrationShell_Part1_Metamodel.pdf'
"IEEE Std 802.3-2022 doesn't directly address data reuse, but its design indirectly supports it by enabling communication between different systems. However, to fully implement the Once-Only Principle, additional measures related to data semantics and access control are needed. IEEE Std 802.3-2022 Reference: https://ieeexplore.ieee.org/document/9844436"
'SAREF itself does not define mechanisms for protecting information against unauthorized changes. The responsibility for ensuring the protection of information against unauthorized changes lies with the implementers and the systems using SAREF. SAREF: https://saref.etsi.org/core/v3.1.1/ '
'The purpose of CSV is not related to organisational interoperability. Therefore, this criterion is not applicable to the specification. CSV reference: https://datatracker.ietf.org/doc/html/rfc4180'
The purpose of HTML is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification. HTML W3C reference: https://www.w3.org/TR/html401/
'According to the Public Procurement Directive 2014/24/EU and the Commission Implementing Regulation (EU) 2016/7, the ESPD shall be used and adopted by all stakeholders, thus becoming a European Standard. Public Procurement Directive 2014/24/EU: https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=CELEX:32014L0024 Commission Implementing Regulation (EU) 2016/7: https://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=CELEX:32016R0007'
TSP is publicly available for study and use at no cost on the IETF webpage. TSP IETF reference: https://tools.ietf.org/html/rfc3161
'The effectiveness of the Dataspace Protocol is often evaluated through various means, including practical implementations and pilot projects. A 2020-paper discusses about the implementation of the IDS Information Model, which is part of the Dataspace Protocol, on top of standard ontologies as well as the process for its continuous evolution and usage of instances of the ontology with the focus on data control and protection in a federated ecosystem, which demonstrates the effectiveness of the specification. The International Data Spaces Information Model – An Ontology for Sovereign Exchange of Digital Content: https://link.springer.com/chapter/10.1007/978-3-030-62466-8_12'
PDF-Tools provides a conformance validation for PDF and its extensions, including PDF/A. There are for free and under payment. PDF/A validators: https://www.pdf-online.com/osa/validate.aspx https://www.pdf-tools.com/pdf20/en/products/pdf-converter-validation/pdf-validator
'Estonia: https://www.emta.ee/en/business-client/e-services-training-courses/how-use-e-services/x-tee-services#xbrl-gl https://www.emta.ee/en/business-client/e-services-training-courses/how-use-e-services/x-tee-services#materials '
'SHACL can significantly contribute to policy-based access control systems by defining rules that determine whether access to certain data should be granted or denied. These rules can also help ensure data processing accuracy by specifying the conditions under which data can be accessed and modified. By enforcing these conditions, SHACL helps prevent errors and inconsistencies in data processing. "SHACL-ACL: Access Control with SHACL" study: https://link.springer.com/chapter/10.1007/978-3-031-43458-7_4 SHACL W3C reference: https://www.w3.org/TR/shacl/'
All specifications are publicly and openly referenced on the RDA web platform. All specifications are deposited in official repositories and have DOIs See: at https://www.rd-alliance.org/recommendations-outputs/adoption-recommendations
'ISO/IEC 19944-1 supports the implementation of secure exhange of data is provided through its emphasis on security controls, data classification, and data governance. Nonetheless, organisations should complement ISO/IEC 19944-1 with relevant industry standards, best practices, and legal requirements to ensure the secure exchange of data within their cloud computing environments. ISO/IEC 19944-1 specification: https://www.iso.org/standard/60545.html'
'DQV focuses on describing fundamental data quality concepts such as accuracy, completeness, consistency, and timeliness. These concepts are applicable across different domains, including business, government, healthcare, education, and more. By providing a common vocabulary for expressing these concepts, DQV facilitates interoperability and consistency in data quality assessment across various domains. Data Quality Vocabulary: https://www.w3.org/TR/vocab-dqv/'
The specification is independent of any technology or software. Although most image software can open TIFF/IT images, there are some that may not. TIFF/IT ISO reference: https://www.iso.org/standard/34342.html
"Schema.org relies on more than one development community, mainly the Community Group and the Steering Group (see Schema.org homepage reference, 'About Schema.org' section). In order to contribute to the development of shema.org specification, stakeholder's participation is only possible through the Community Group or the dedicated mailing list. While the Community Group requires stakeholders to register to the W3 community (see W3 community reference, Mailing List), the mailing list does not require any type of registration process (see Schema.org homepage reference, 'About Schema.org' section). Additionally, anyone interested can contribute to the mailing list using the dedicated contact point (by contacting public-vocabs@w3.org), or participate via the schema.org Github (e.g. in the Issues or Discussions section) prior to a registration process. Schema.org homepage reference, 'About Schema.org' section: https://schema.org/docs/about.html W3 community reference, Mailing List: https://lists.w3.org/Archives/Public/public-vocabs/ Schema.org-W3 Github reference, Issues section: https://github.com/schemaorg/schemaorg/issues Schema.org-W3 Github reference, Discussions section: https://github.com/schemaorg/schemaorg/discussions"
SHACL is publicly available for implementation and use for free on Github. See: https://github.com/w3c/data-shapes
'There can be found a DCAT-AP discussion forum on the Githoub platform in Danish. Moreover, The Joinup platforms hosts a community of developers and implementers of DCAT-AP discussing their results from implmenting the specification, and recommending best practices. DCAT-AP discussions in Joinup: https://joinup.ec.europa.eu/search?keys=dcat%20ap&sort_by=relevance&f%5B0%5D=group%3Ahttp%3A//data.europa.eu/w21/ac376c94-74cf-4dd7-ade7-267d6a4ec4dc&f%5B1%5D=type%3Adiscussion DCAT-AP DK: https://github.com/digst/DCAT-AP-DK'
As part of the "IP Stack", IPsec has been selected by several public administrations for secure data exchange over the internet. By allowing the secure exchange of data, the specification fosters the visibility of data across borders. An example of its implementation is the TESTA project, which provides a secure cross-border data communication network service for public administrations. See: https://ec.europa.eu/idabc/en/document/2097.html https://ec.europa.eu/isa2/solutions/testa_en
ETSI and ENISA are recommending it within documents about guidelines and best practices for securing solutions and services. ETSI SmartM2M; Security; Standards Landscape and best practices: https://www.etsi.org/deliver/etsi_tr/103500_103599/103533/01.01.01_60/tr_103533v010101p.pdf ENISA Advancing Software Security in the EU: https://www.enisa.europa.eu/publications/advancing-software-security-through-the-eu-certification-framework ENISA Good Practices for Security of IoT - Secure Software Development Lifecycle: https://www.enisa.europa.eu/publications/good-practices-for-security-of-iot-1
'The purpose of TLS 1.3 is not related to enable the visibility of administrative procedures, rules data, and services. Therefore this criterion is not applicable to this specification. TLS 1.3 2018 Reference: https://www.rfc-editor.org/rfc/rfc8446.html'
'The specification is not a European Standard. SOAP Reference: https://www.w3.org/TR/soap12/'
Betterr Regulation Toolbox is publicly available for its implementation and its use for free on the European Comission's webpage. Better Regulation Toolbox reference: https://ec.europa.eu/info/sites/info/files/better-regulation-toolbox_2.pdf
'EuroVoc is a public asset developed by a European Institution and can be accessed and reused without any payment conditions. Therefore, it can be considered that the specification is licensed under royalty-free basis and (F)RAND basis. EuroVoc: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource /dataset/eurovoc'
'Even though the specification defines conformance criteria, no testing mechanism or tool has been found to validate an SMP implementation. SMP OASIS reference: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505009'
'The specification is mentioned in IPv6 section of the Internet standards in the EU. Thus, IPv4 is indirectly mentioned as a oldesr version of the IPv6 standard. IPv6 standard: https://ec.europa.eu/internet-standards/'
' While Domibus itself is not tied to a specific operating system or platform, its implementation and deployment may have dependencies and considerations related to the underlying infrastructure. Domibus specification: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/Domibus'
'After research nothing has found about the specification being technology agnostic. The specification relies on some ISO standards. For example, the Syntax Encoding Schemes, rely among others, on ISO3166, ISO639-2 and ISO639-3. DCMI Terms: https://www.dublincore.org/specifications/dublin-core/dcmi-terms/'
HTML 4 comes from the evolution of different versions of HTML that they were already recommendations in W3C. HTML 4 became a W3C recommendation on December 1997. It had a good acceptance because it was the best markup language. This fact proves that the specification is mature enough for its use in the development of products and services. HTML W3C reference: https://www.w3.org/TR/html401/
The outputs / recommendations are aiming to achieve seamless interoperability, trust, and ultimately to provide growth and employment opportunities by facilitating data exchange across organisations, disciplines and geographical borders.
'The specification clearly encourages the creation of communities along with the sharing of their data and results as its purpose is to improve cloud computing portability and interoperability, thus improving communication between different actors. Furthermore, ISO 19941 has been included in different catalogues of ICT standards in a European level therefore, it is an important stard to consider. ISO 19941:2017: https://www.iso.org/standard/66639.html '
'ETSI EN 319 422 is a European standard, delivered by a European Standardisation organisation (ETSI), according to the specification documentation. ETSI EN 319 422 reference: https://www.etsi.org/deliver/etsi_en/319400_319499/319422/01.01.01_60/en_319422v010101p.pdf'
OpenPM2 is the open version of the PM2 developed by the Commission, therefore, it is publicly available for its use and implementation. Moreover, it is available for everyone with no cost. OpenPM2 specification reference: https://op.europa.eu/en/publication-detail/-/publication/ac3e118a-cb6e-11e8-9424-01aa75ed71a1/language-en/format-PDF/source-83307127
'The developers producing dynamic content applications using the IndexedDB should ensure that the content is accessible to users with a variety of technologies and needs. Moreover, the API does not define or require any a user to generate a user interface to enable interaction with the API. In this context, users can provide user interface elements to support the API. Indexed Database API: https://www.w3.org/TR/IndexedDB/'
'The XFDL specification, being based on XML can facilitate organisational interoperability by providing a standardised way to represent data. Organisations and Public Administrations can easily exchange XFDL forms and data, ensuring that systems can read, process, and share information consistently across different platforms. Extensible Forms Description Language reference: https://www.w3.org/TR/NOTE-XFDL'
"By helping administrations to identify and manage possible risks, ISO/IEC 27001 ensures and fosters the continuous availability of administration's data and information. ISO/IEC 27001 reference website: https://www.iso.org/standard/54534.html"
'Genericode is developed by OASIS, a standard development organisation based in the US. Moreover, the specification does not appear in any of the main European standard development bodies, therefore, the specification is not a European standard. Code List Representation (genericode): https://docs.oasis-open.org/codelist/genericode/v1.0/os/genericode-v1.0-os.html'
ODRL is a policy expression language that provides a flexible and interoperable information model, vocabulary, and encoding mechanisms for representing statements about the usage of content and services. This fact is a key aspect for the interaction and the collaboration between parties and how they need to consume content or services. W3C specification reference: https://www.w3.org/TR/odrl-vocab/#vocab-core
Data on the Web Best Practices is publicly available for implementation and study for free on W3C's webpage. W3C reference: https://www.w3.org/TR/dwbp/
'WAI-ARIA enhances assistive technologies to interact with accessibility APIs and can restructure, simplify, stylise, or rescale content to help a different set of users. EU Commission accessibility: https://www.eacea.ec.europa.eu/about-eacea/accessibility_en WAI-ARIA reference: https://www.w3.org/TR/wai-aria-1.2/#at_support'
'The specification is related to the capacity of extension as it has DCAM available for its use. DCMI About: https://www.dublincore.org/about/ '
The adoption of CLV as a data model does not hamper the scalability of systems. The use of existing data models for the development of common information systems facilitates the development of those systems and improves their interoperability. Additionally, as it happens with all the Core Vocabularies, it can be extended to properly cover a specific need under a specific domain. CLV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-location-vocabulary
Xforms 2.0 is publicly available for implementation and study for free on W3C's webpage. Xforms 2.0 W3C reference: https://www.w3.org/community/xformsusers/wiki/XForms_2.0
'There has not been found any community sharing their data and results on national platforms. However, ETSI TS 119 612 indirectly encourages the creation of communities on national platforms through ETSI membership and directives. ETSI TS 119 612 specification: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf'
"Customisations in E-ARK CSIP can be made and they typically involve adapting or extending certain aspects of the specification to align with a given organisation's needs. These adaptations may range from metadata customisation to the integration of the specification within existing systems. E-ARK CSIP specification: https://earkcsip.dilcis.eu/#introduction"
The specification has been selected as one of the key elements for the data interchange between administrations and stakeholders. Europeana is using JSON within the Search API, the method created to diving into the european cross-border project data. These features allow retrieving information from EUROPEANA. Moreover, the Single Electronic Data Interchange Area (SEDIA) is using JSON as the basis to make data available for stakeholders. Examples SEDIA activity is the Call for Tenders, a key point on European eProcurement. Additionally, the EU Open Data Portal is another cross-border initiative that relies on JSON as a message format for API’s communication. See: https://pro.europeana.eu/resources/apis/search https://ec.europa.eu/info/funding-tenders/opportunities/portal/screen/support/apis http://data.europa.eu/euodp/en/data/dataset/eu-open-data-portal-api
'The purpose of DAPS is not related to facilitating organisational interoperability agreements. Therefore, this criterion is not applicable to the specification. DAPS: https://github.com/International-Data-Spaces-Association/IDS-G/tree/main/Components/IdentityProvider/DAPS'
'The SAML 2.0 specification is a business domain agnostic specification, designed to be implemented and/or used in any domain. SAML 2.0 Reference: http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-tech-overview-2.0.html'
'The IPv4 specification allows for extensions in the areas of security and privacy. One example of an available extension is IPsec, which works with both IPv4 and IPv6 and can improve data integrity and authenticity through the AH and ESP protocols. IPsec extension: https://www.ionos.es/digitalguide/servidores/know-how/ipsec-arquitectura-de-seguridad-para-ipv4-e-ipv6/ IPv4 IETF: https://www.rfc-editor.org/rfc/rfc791'
'The Spanish "Accessibility Observatory" offers a methodology to ensure the monitoring and evolution of e-accessibility services, and includes WAI-ARIA as one of the elements reporting the current status of e-Accessibility in digital public services. The WAI-ARIA specification is implemented in this methodology and scopes comprehensibility of website contents when combined mainly with HTML. PAe reference, Survey Methodology PDF: https://administracionelectronica.gob.es/pae_Home/en/pae_Estrategias/pae_Accesibilidad/pae_Observatorio_de_Accesibilidad.html?idioma=en'
'Joinup offers several services that aim to help e-Government professionals share their experience with each other. Joinup supports them to find, choose, re-use, develop and implement interoperability solutions. LDAP appears in many Joinup entries as a discussion topic, and the specification is distributed and can also be found in the platform. LDAP distribution in Joinup: https://joinup.ec.europa.eu/collection/dutch-standardisation-forum-comply-or-explain-standards/solution /lightweight-directory-access-protocol'
The Zaragoza's city council is using HTML5 to developments services in an independent way from the platform used by the citzens. Another example is the Accessibilitly Foundation, HTML5 offers great possibilities for improving accessibility of web and mobile web applications, digital signs, ebooks and devices not yet known for people with disabilities. See: https://www.w3.org/TR/2014/REC-html5-20141028/
'Slovakia is recommending ADMS in its ICT National Catalogues. Slovakia’s Catalogue: https://www.mirri.gov.sk/sekcie/informatizacia/governance-a-standardy/standardy-isvs/index.html CAMSS List of standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
'The European Union Agency for Cybersecurity (ENISA) has invested in the fifth generation of mobile telecommunication (5G), and includes the NFVI specification as a core element of the 5G implementation. Publications Office (OP), ENISA THREAT LANDSCAPE FOR 5G NETWORKS document: https://op.europa.eu/en/home'
TSP is developed and maintained by IETF, a widely recognised open international community developing standards to enhance the internet. IETF Reference: https://www.ietf.org/ TSP IETF reference: https://tools.ietf.org/html/rfc3161
'SAML 2.0 itself is primarily focused on authentication and expressing attributes and entitlements about subjects, rather than enforcing access controls on resources. Therefore, the specification neither addresses confidentiality nor prevents it. SAML 2.0 Reference: http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-tech-overview-2.0.html'
The purpose of CAdES is not related to e-accessibility. Therefore, this criterion is considered not applicable to this specification. CAdES ISO reference: https://www.iso.org/standard/64756.html CAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/101700_101799/101733/02.01.01_60/ts_101733v020101p.pdf
'This specification is currently not included in the EIRA Library of Interoperability Specifications (ELIS), but will be included in the next release of the ELIS. The response to this criterion is positive because OData is mappable to the European Interoperability Reference Architecture (EIRA). EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/v110'
'The specification performs effectively in accordance with the TR-ESOR middleware techincal guidelines. The goal of the TR-ESOR Guideline is to assist in the process of choosing and using suitable security measures for the preservation of evidence of signed electronic documents over long periods of time. TR-ESOR details testing methodologies, including functional and security tests, that are necessary to evaluate the implementation of digital signatures. This includes examining signature creation, validation, and the management of keys. TR-ESOR Preservation of Evidence of Cryptographically Signed Document: https://www.bsi.bund.de/SharedDocs/Downloads/EN/BSI/Publications/TechGuidelines/TR03125/TR-03125_v1_2_2-main-doc.pdf?__blob=publicationFile&v=1 ETSI TS 119 512 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.02_60/ts_119512v010102p.pdf'
"The specification is associated with EIRA ABB's in the EIRA Library of Interoperability Specifications (ELIS). It is associated with Data Interface, Data Server Software Environment from Technical Infrastructure. Data Exchange Component, Data Exchange Service from Technical Application. ELIS link: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /solution/elis/release/v501 "
OWL is an extension of RDF that adds more vocabulary for describing properties and classes. RDF is considered an agnostic specification which defines reusable cross-sector data model. IBM Knowledge Center has a document where explains how to generate a logical data model from a Web Ontology Language (OWL). IBM Data Model from OWL: https://www.ibm.com/support/knowledgecenter/en/SS9UM9_9.1.2/com.ibm.datatools.transform.owl.ldm.doc/topics/c_owl2ldm_cont.html RDF Data Model: https://www.w3.org/TR/rdf11-primer/#section-data-model
DCAT-AP is already associated to EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, DCAT can define the interoperability aspects of the "Data Publication Component" and "Data Publication Service" ABBs of the EIRA Semantic View. See: https://joinup.ec.europa.eu/sites/default/files/distribution/access_url/2019-03/76cb237b-0de8-464c-84ca-1327945eac3e/EIRA_v3_0_0_Overview.pdf
TIFF/IT is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, TIFF/IT can define the interoperability aspects of the "Representation" ABB of the EIRA Semantic View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/solution/elis/release/v100
JPEG is an image extension which allows visualizing and storing images. However, as they cannot be protected with a password or something, everyone who has access to a JPEG file can visualize it. JEPG ISO reference: https://www.iso.org/standard/18902.html JPEG public reference: https://jpeg.org/jpeg/
'Schema.org mark-up can be used on web pages written in any language. Therefore, the specification is designed to fully support multilingualism. Schema.org reference, FAQs section: https://schema.org/docs/faq.html#7'
'The specification is not related to enabling the exposure of interfaces. Therefore this criterion is not applicable to this specification. The Dublin Core Ontology enables the exposure of interfaces. The specification provides sets of data elements, described as application profile schemas, which are derived from one or more namespace schemas and optimised for the local needs. DCMI About: https://www.dublincore.org/about/ DCMI Application Profile: https://www.dublincore.org/blog/2011/application_profile'
'DAPS uses Apache 2.0 license therefore, software developers area allowed to alter the source code of existing software’s source code, copy the original source code or update the source code. Furthermore, developers can then distribute any copies or modifications that they make of the software’s source code. The specification is maintained by International Data Spaces Global (IDS-G) and any user can modify it on GitHub. IDS-G DAPS: https://github.com/International-Data-Spaces-Association/IDS-G/tree/main/Components/IdentityProvider/DAPS'
'UBL is an open standard based on XML. UBL v2.3 reference: http://docs.oasis-open.org/ubl/os-UBL-2.3/UBL-2.3.html Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/en/'
'Since internationalization is not core to context information management, any direct support within NGSI-LD systems is limited. Annex G of the specification proposes a series of best practices for maintaining, querying and displaying interoperable internationalized data. For instance, there are specific provisions to associate an Entity or a Property with a Natural Language. ETSI Context Information Management (CIM); Security and Privacy: https://www.etsi.org/deliver/etsi_gr/CIM/001_099/007/01.01.02_60/gr_cim007v010102p.pdf'
As a common data exchange format, CSV fosters the visibility of administration's data. It eases the publication of structured data for the consumption by the different stakeholders. Therefore, CSV fosters the visibility of administrations data. Additionally, it can be used internally easing as well de decision-making process.
It requires pre-payment for getting access to the documentation. However, it is included in Joiunp, JEPG ISO reference: https://www.iso.org/standard/18902.html JPEG in Joinup: https://joinup.ec.europa.eu/solution/digital-compression-and-coding-continuous-tone-still-images-requirements-and-guidelines
'The purpose of ISO 639-2 is not related to ensure the protection of personal data. Therefore, this criterion is not applicable to this specification. ISO 639-2 reference: https://www.iso.org/standard/4767.html ISO 639-2 FAQs: https://www.loc.gov/standards/iso639-2/faq.html#5'
The specification is a protocol focused on the transaction of data, specifically on the certification of certain data, information or documents which either exist or not. Even though its relation to the data exchange, the specification is not related to data portability in itself, but the data trustworthy exchange amongst Systems and European Public Services. TSP IETF reference: https://tools.ietf.org/html/rfc3161
'The specification is not a European Standard. World Wide Web Consortium (W3C) reference: https://www.w3.org/'
The purpose of JPEG is not related to the availability of interfaces with internal information systems. Therefore, this criterion is not applicable to this specification. JEPG ISO reference: https://www.iso.org/standard/18902.html JPEG public reference: https://jpeg.org/jpeg/
'HTTPS is included in 7 national catalogues of recommended specifications. They belong to Croatia, Cyprus, France, Germany, Greece, Portugal, and Sweden. CAMSS List of standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards'
'The purpose of DNS is not related to the delivery of multilingual services. Therefore this criterion is not applicable to the specification. DNS IETF reference: https://datatracker.ietf.org/doc/html/rfc8499 '
"While Registered Organization Vocabulary became a W3C Recommendation, its origins lie within the European Commission's ISA Programme, aimed at the interoperability within European public administrations. Additionally, its integration with Asset Description Metadata Schema (ADMS) ensures robust metadata management, facilitating discoverability and semantic consistency across organisational data frameworks in Europe. However, according to recent discussions on the CBV GitHub, W3C has discontinued the Registered Organization Vocabulary and the community along with the continuation for the development moved to the Core Business Vocabulary. Registered Organization Vocabulary specification reference: https://www.w3.org/TR/vocab-regorg/ Core Business Vocabulary Github reference: https://github.com/SEMICeu/Core-Business-Vocabulary/tree/master Asset Description Metadata Schema (ADMS) reference: https://www.w3.org/TR/vocab-adms/ ISA Programmae Reference: https://publications.europa.eu/resource/cellar/c80c7ff1-14e7-43d6-a56f-99bf254c33f9.0001.02/DOC_1"
'DQV directly addresses data accuracy by allowing organizations to define and document specific accuracy metrics. It provides a framework for describing how data accuracy is assessed, maintained, and complied with industry standards therfore enhancing data usability, discovery, and trust among users by transparently communicating the reliability and suitability of data for specific purposes. Data accuracy DQV: https://www.w3.org/TR/vocab-dqv/#DimensionsOfISOIEC25012'
'The purpose of DAPS is not related to enabling digital service delivery channels. Therefore, this criterion is considered not applicable to this specification. DAPS: https://github.com/International-Data-Spaces-Association/IDS-G/tree/main/Components/IdentityProvider/DAPS'
'The effectiveness of the Advanced Encryption Standard has been assed by the Institute of Electrical and Electronics Engineers (IEEE), dedicated to standardisation and development in technical areas. In the study "Advanced Encryption Standard (AES) Security Enhancement Using Hybrid Approach," a mechanism is proposed to enhance security in message transmission. This involves using the AES algorithm combined with Dynamic Key Generation and Dynamic S-box Generation. "Advanced encryption standard (AES) security enhancement using hybrid approach" study: https://ieeexplore.ieee.org/abstract/document/8229881 AES Standard Reference: https://csrc.nist.gov/pubs/fips/197/final'
'XSD is widely used when exchanging information in XML is needed. Among others, there are two European initiatives that are using XSD to provide e-procurement services. The first initiative is TED eSentool, a free web service of the Publications Office which is focused in allow eSenders to follow-up the process of their notices until publication. The ESPD, is another cross border initiative using XSD for the validation of the XML documents generated while generating eProcurement process and documentation. TED eSentool Reference: https://esentool.ted.europa.eu/ ESPD Reference: https://ec.europa.eu/growth/single-market/public-procurement/digital/espd'
ETSI is recommending it within a technical report that provides the standards landscape and best practices on security aspects. Therefore, since the European Telecommunications Standards Institute is recommending its use it can be considered compliant with the European Law of standardisation. ETSI SmartM2M; Security; Standards Landscape and best practices: https://www.etsi.org/deliver/etsi_tr/103500_103599/103533/01.01.01_60/tr_103533v010101p.pdf ENISA Advancing Software Security in the EU: https://www.enisa.europa.eu/publications/advancing-software-security-through-the-eu-certification-framework ENISA Good Practices for Security of IoT - Secure Software Development Lifecycle: https://www.enisa.europa.eu/publications/good-practices-for-security-of-iot-1
Data on the Web Best Practices gives some advice on how to publish data on the web. However, it does not support the principles of linked open data. Data on the Web Best Practices W3C: https://www.w3.org/TR/dwbp/ 5-star linked open data: https://www.w3.org/DesignIssues/LinkedData.html
'While the specification does not provide explicit mechanisms for ensuring data processing accuracy, it can indirectly contribute to it. SMP OASIS reference: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505009'
'By validating data published as RDF (Resource Description Framework), SHACL ensures that the data adheres to predefined shapes and constraints, enhancing its accuracy and reliability. This validation process fosters the comprehensibility of administrative data, making it easier for public administrations to manage and utilise their data effectively. SHACL W3C reference: https://www.w3.org/TR/shacl/'
"CPOV is included in 1 Member States' catalogues of recommended specifications. Moreover, OSLO extension is used by Belgium. OSLO extension: https://joinup.ec.europa.eu/collection/oslo-open-standards-local-administrations-flanders Belgium Catalogue: https://www.belgif.be/page/specifications.en.html Spain Catalogue: https://administracionelectronica.gob.es/ctt/verPestanaActivosSemanticos.htm?idIniciativa=3351 Joinup Catalogue: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards"
Since the RegOrg is involved in cross-border projects like BRIS, it can be considered that exists an interoperability agreement for the inclusion of the specification as part of interoperable solutions. Core Vocabularies in action: https://joinup.ec.europa.eu/sites/default/files/news/attachment/eu_core_vocabularies_in_action_using_core_business_vocabulary_in_the_eu_.pdf
'There is no Member State that includes the DPV in their national catalogue with Their National Interoperability Framework (NIF) in alignment with the three categories 1. Conceptual model for integrated public servicesprovision, 2. interoperability layers, and 3. interoperability principles. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards NIFO Factsheets: https://joinup.ec.europa.eu/collection/national-interoperability-framework-observatory-nifo/nifo-factsheets'
CSV has been developed and maintained by IETF. Additionally, the W3C has published a recommendation enhancing specific features of the specification. Both organisation are International Organisations concerned with the development of the Internet. See: https://tools.ietf.org/html/rfc4180 https://www.w3.org/TR/tabular-data-model/
'The purpose of CPOV is not related to the authenticity and authentication of the roles agents involved in the data transactions. Therefore, this criterion is considered not applicable to this specification. CPOV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-organisation-vocabulary'
'Data Quality Vocabulary (DQV) is not included in any national catalogue of recommended specifications whose Member State NIF has a high performance on interoperability according to the NIFO factsheets. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards 2023 NIFO factsheets: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public\x02administration-factsheets-2023'
Xforms can be found for free along within the European Collaborative Platform, Joinup. Xforms 2.0 in Joinup platform: https://joinup.ec.europa.eu/collection/w3c-standards-and-technical-reports/solution/xforms-20
'The XACML specification provides robust mechanisms for restricting access to information and data through detailed and flexible access control policies. These policies can be based on various attributes, combined and enforced in sophisticated ways to ensure that access is tightly controlled according to the specific requirements of Public Administrations or any organization implementing XACML. XACML OASIS reference: https://docs.oasis-open.org/xacml/3.0/xacml-3.0-core-spec-os-en.html'
'DCAT-AP is already associated to EIRA ABBs in the EIRA Library Of Specifications (ELIS). More specifically, DCAT can define the interoperability aspects of the "Data Publication Component", "Data Publication Service", "Metadata Management Component" and "Metadata Management Service" ABBs of the EIRA Technical View; the "Base Registry", "Controlled Vocabulary", "Data", "Data Model", "Data Policies", "Data Set", "Data Set Catalogue", "Data Syntax","Forms Structure", "Hash Code", "Metadata", "Reference Data" ABBs of the EIRA Semantic View. ELIS Catalogue: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/news/new-release-elis-501 '
EuroVoc was developed to support the processing of documentary information. Besides, since it helps to classify the knowledge domains and subdomains it is helpful fostering the visibility of administrative data and supporting the decision-making process. EuroVoc webpage: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/eurovoc
CAMSS Assessment of CPSV-AP EIF Scenario v1.0.0
'The specification can be used as a global ledger by any domain. It can capture a broad set of business transaction related data e.g. accounting and taxation related details, parties involved, products or services traded. '
TSP tracks the creation and modification time of digital documents. Therefore, it fosters the creation and digitalisation of services at the same time that guarantees the data trustworthy exchange. By providing these capabilities to administrations, allows the reduction of administrative burden avoiding non-digital exchanges and the procedures for ensuring data reliability. TSP IETF reference: https://tools.ietf.org/html/rfc3161
'As described on the Oracle documentation about securtity features, the ebXML specification includes mechanisms that help guarantee data accuracy, such as data encryption and user authentication. By authenticating users, it helps ensure that data comes from a reliable and trustworthy source. Additionally, other mechanisms, such as encryption, can help ensure that data has not been altered by an unauthorised user since it was sent. ebXML security: https://www.oracle.com/technical-resources/articles/enterprise-architecture/ebxml-security1.html ebXML RegRep OASIS reference: https://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html'
"The Better Regulation Guidelines and Toolbox aim to ensure that EU policies and laws are developed with comprehensive stakeholder involvement. To facilitate communication and interaction with stakeholders and the general public, the Commission organises a consultation process, which is published on the 'Have your say' web portal. As part of this commitment, the Commission ensures that all collected contributions are made publicly available. The guidelines and toolbox outline the framework for both public and targeted consultation activities. Better Regulation Guidelines and Toolbox reference: https://commission.europa.eu/law/law-making-process/better-regulation/better-regulation-guidelines-and-toolbox_en European Parliamentary Research Service briefing https://www.europarl.europa.eu/RegData/etudes/BRIE/2022/699463/EPRS_BRI(2022)699463_EN.pdf Have your say portal: https://ec.europa.eu/info/law/better-regulation/have-your-say_en European Comission webpage: https://commission.europa.eu/law/law-making-process/better-regulation_en#stakeholder-engagement"
W3C provides a Markup Validation Service for free to validate XML 1.1 implementations. See: https://validator.w3.org/
'Using other specifications and the requirements defined in there, the specification and the implementation can be customized. ETSI EN 319 422 reference: https://www.etsi.org/deliver/etsi_en/319400_319499/319422/01.01.01_60/en_319422v010101p.pdf'
'ETSI TS 119 612 does not rely on any specific platform. ETSI TS 119 612 specification: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf'
'By simplifying and standardizing the procurement process, the ESPD can contribute to the delivery of more efficient and effective public services across the EU. The use of a single, standardized document can help to reduce administrative burden and increase transparency in procurement procedures, leading to more streamlined and cost-effective procurement of goods and services for public authorities, therefore, simplifying the delivery of European public services. ESPD Business handbook: https://docs.ted.europa.eu/ESPD-EDM/latest/xml_business_handbook.html'
The specification is included in 5 Member States' catalogues of recommended specifications. Some examples of Member States including JSON on their catalogues are the Netherlands, Spain or Belgium. See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
UTF-8 does not hamper the scalability of systems, but the implementation of the specification is proportionate to users' needs. The specification is a variable-width encoding character set which allows avoiding the overhead of byte growth. Moreover, due to the wide sample of alphabetic scripts that can be encoded by means of UTF-8 and its high adoption avoids the interoperability hampering.
'[To be checked] The publiccode.yml specification does not incorporate access control mechanisms. Its primary focus is on documenting metadata for public code projects, and it lacks provisions for establishing user roles or managing access to resources. Consequently, it does not align with the access control requirements outlined in EIF Recommendation 15. Publiccode.yaml documentation: https://docs.italia.it/italia/developers-italia/publiccodeyml-en/en/master/index.html'
The purpose of this Core Vocabulary is to harmonise public services (information) stored in different local, regional and national information sources, allowing the information to be searched and shared easily within and across public administrations all over Europe. CPSV-AP reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-service-vocabulary-application-profile
'While XHTML is a reformulation of HTML 4 using XML, it is not entirely independent of these standards or other technologies. XHTML relies on XML parsing capabilities and enforces specific XML-based rules. XHTML W3C reference: https://www.w3.org/TR/xhtml1/'
'The specification has enough market acceptance as its first year of release it was inactive, in March 2016 it had enough market acceptance to become active. EN 319 422 defines a profile for time-stamping associated to a signature. Standards Globalspec reference: https://standards.globalspec.com/std/9998069/EN%20319%20422 '
"Schema.org allows the exchange of metadata across borders which, in some cases can reduce the administrative burden. For example, by linking the DCAT Application Profile for Data Portals in Europe (DCAT-AP) and schema.org data discoverability on the web (Schema.org profile of DCAT Application Profile for Data Portals in Europe, or DCAT-AP-SDO) will increase, considerably easing access to European public services. Schema.org homepage reference, 'About Schema.org' section: https://schema.org/docs/about.html DCAT reference: https://www.w3.org/TR/vocab-dcat-3/ DCAT-AP-SDO reference: https://ec-jrc.github.io/dcat-ap-to-schema-org/"
SAML 2.0 is not defining a cross-sector reusable data model. The specification defines a schema for the assertions that are involved in SAML performance but it cannot be considered as a data model.
'UDDI uses WSDL to describe interfaces to web services and it is a platform-independent framework. In addition, it is an open framework. UDDI techtarget reference: https://www.techtarget.com/whatis/definition/UDDI-Universal-Description-Discovery-and-Integratio'
The specification is included in 1 Member States' catalogues of recommended specifications. This Member States is Germany. National catalogue Germany: http://www.cio.bund.de/SharedDocs/Publikationen/DE/Architekturen-und-Standards/SAGA/saga_modul_tech_spez_de_bund_5_0_download.pdf?__blob=publicationFile
'The purpose of SAREF is not related to e-accessibility. Therefore, this criterion is considered not applicable to this specification. SAREF: https://saref.etsi.org/core/v3.1.1/ '
'There are already existing studies assessing the efficiency of JSON. For example, the study from 2017 assessing the "Efficiency of JSON for Data Retrieval in Big Data". Efficiency of JSON for Data Retrieval in Big Data: https://www.researchgate.net/profile/Kamir-Yusof/publication/320045078_Efficiency_of_JSON_for_Data_Retrieval_in_Big_Data/links/5a3f14ea458515f6b0456f54/Efficiency-of-JSON-for-Data-Retrieval-in-Big-Data.pdf'
"There is no direct assessment on the effectiveness of the ebXML specification. However, according to the OASIS Technology Reports, several studies on different digital solutions from the public and private domain indirectly assess the specification's effectiveness. OASIS Technology Reports reference: http://xml.coverpages.org/ebXML.html"
'OData defines a set of best practices for building and consuming REST APIs by using simple HTTP messages; however, openness may be compromised since these agreements have sense in proprietary platforms, specifically Microsoft. Microsoft reference: https://learn.microsoft.com/es-es/odata/ OData reference: https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#_Toc31358832'
'The CSV specification does not specify any access control mechanisms. CSV Reference: https://datatracker.ietf.org/doc/html/rfc4180'
There are existing mechanisms for assessing the conformity of XSD implementations. W3C provides with a XSD test suit that is available for free. See: https://github.com/w3c/xsdtests
'The specification is included in 10 Member States catalogues of recommended specifications. This Member States are Austria, Croatia, France, Germany, Greece, Malta, Netherlands, Spain, Sweden and Cyprus. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards'
'Syslog protocol is not included in an open repository/catalogue of standards at European level. Syslog Protocol: https://datatracker.ietf.org/doc/html/rfc5424'
Better Regulation Toolbox has the support of the European Commission as a developer community. It is the most powerful party giving support to its development and working to enhance through the experience. Better Regulation Toolbox reference: https://ec.europa.eu/info/sites/info/files/better-regulation-toolbox_2.pdf . European Commission webpage: https://ec.europa.eu/info/index_en
'GITB TDL implementations can be partial by supporting only a limited set of constructs. To support this last point, GITB TDL concepts and constructs are formalised using a published taxonomy that can be referenced to understand the TDL constructs that are used (within a test case) or supported (by a test bed). GITB TDL reference: https://www.itb.ec.europa.eu/docs/tdl/latest/introduction/index.html#where-is-it-used'
By allowing the exchange of digital images, which can provide sensitive information for administrations and stakeholders, the specification helps to avoid the administrative burden related to the non-digital communications. JEPG ISO reference: https://www.iso.org/standard/18902.html JPEG public reference: https://jpeg.org/jpeg/
'To transmit files that are discontinuous, FTP defines a page structure. Files of this type are sometimes known as"random access files" or even as "holey files". In these files there is sometimes other information associated with the file as a whole (e.g., a file descriptor), or with a section of the file (e.g., page access controls), or both. This type includes an additional header field for paged files with page level access control information. The header length must be 5. FTP Specification Reference: https://datatracker.ietf.org/doc/html/rfc959'
The Multi-stakeholder platform (MSP) has identified SHACL as referenceable for its use in procurement. The following step is its recommendation by the European Commission based on the MSP's identification. Although this step has not taken place yet, it will take place with all certainty. Therefore, it can be considered that SHACL has been included in an interoperability agreement between organisations involved in European public service provision.
'An OCSP client requests status from an OCSP responder and suspends acceptance of the concerned certificates until the responder provides a response. In this sense, OCSP enables the secure exchange of data. OCSP reference, section 2: https://datatracker.ietf.org/doc/html/rfc2560'
'ESPD can be found in the Tenders Electronic Daily (TED) Developer Docs website. This website publishes projects related to the development of e-procurement related specifications. ESPD business handbook: https://docs.ted.europa.eu/ESPD-EDM/latest/xml_business_handbook.html TED Developer Docs: https://docs.ted.europa.eu/home/index.html'
PNG is included in 3 national catalogues of recommended specifications. They belong to Estonia, Spain and Sweden. The National Interoperability Framework (NIF) of these Member States is fully aligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. National catalogue Estonia: https://www.mkm.ee/sites/default/files/interoperability-framework_2011.doc National catalogue Spain: https://administracionelectronica.gob.es/pae_Home/pae_Estrategias/pae_Interoperabilidad_Inicio/pae_Normas_tecnicas_de_interoperabilidad.html#CATALOGOESTANDARES National catalogue Sweden: https://www.avropa.se/globalassets/dokument/open-it-standards.pdf?_t_id=1B2M2Y8AsgTpgAmY7PhCfg%3d%3d&_t_q=standards&_t_tags=language%3asv%2csiteid%3a95d515a5-23ca-47bf-87a9-07b10d8ac360&_t_ip=178.139.72.144&_t_hit.id=Avropa_Core_Models_Media_GenericMedia/_ff07d720-f793-44b0-994d-27e79b28f6bd&_t_hit.pos=7 NIFO factsheets: https://joinup.ec.europa.eu/collection/national-interoperability-framework-observatory-nifo/nifo-factsheets
The specification is compliant with Tim Berners Lee's principles for the Linked Data and, as well, is highly aligned with the different levels of maturity of Tim Berners Lee's 5 stars schema for open data. In fact, RDF is one of the proposed standards for the publication of data as Linked Data. See: https://www.w3.org/DesignIssues/LinkedData.html https://5stardata.info/en/ https://www.w3.org/TR/ld-bp/
'ISO 3166-1 could be used in a multilingual context beyond a statistical purpose. The specification could be useful in determining the linguistic and dialectical areas when establishing a specific European public service. ISO 3166-1 reference: https://www.iso.org/standard/72482.html'
'The purpose of HTTP is not related to e-accessibility. Therefore this criterion is considered not applicable specification. HTTP /1.1 RFC 2616 Reference: https://www.rfc-editor.org/rfc/rfc2616.html'
The specification is included in 5 Member States' catalogues of recommended specifications. These Member States are France, Germany, Norway, Poland and Spain. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
CAMSS Assessment of SMP EIF Scenario v1.0.0
'The specification does not allow customisation. Therefore, this criterion does not apply to this specification. Core Criterion and Core Evidence Vocabulary reference (v1.0.0): https://joinup.ec.europa.eu/release/core-criterion-and-core-evidence-vocabulary-v100 '
XSD is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). Specifically, XSD can define the interoperability aspects of the "Data Syntax" ABBs of the EIRA Semantic View. See: https://joinup.ec.europa.eu/solution/elis
'Yes, the European Member States that recommends the specification in their ICT National Catalogues are Bulgaria, Cyprus France, Germany, Greece, Malta, Netehrlands, Portugal, Spain, Sweden. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
The purpose of OWL2 is not related to e-accessibility. Therefore, this criterion is considered not applicable to this specification. OWL2 W3C reference: https://www.w3.org/TR/owl2-overview/
'One of the main benefits of the e-Government Core Vocabularies (CLV) is that they provide a concrete starting point for promoting semantic interoperability among European public administrations. In this sense, the Core Location Vocabulary specification allows organisations to avoid some manual processes and to digitalise some services, improving the quality of public services. In addition, the CLV vocabulary is related to the INSPIRE project. In this context, the development of the Core Location Vocabulary was chaired by JRC/H6 Digital Earth and Reference Data involved in the implementation of the INSPIRE Directive. Therefore, it fosters the creation of innovative solutions. INSPIRE project: https://interoperable-europe.ec.europa.eu/sites/default/files/inline-files/EU01%281%29_0.pdf Core Location Vocabulary: https://interoperable-europe.ec.europa.eu/collection/semic-support-centre/solution/core-location-vocabulary/release/100'
"Schema.org was originally conceived for the semantic web. Nonetheless, the specification project has successfully extended schema.org to other domains because of the variety of attributes and types it presents (see Schema.org reference, Data model section). Besides, schema.org also offers additional domain-related schema extensions that may differ from each other (see Schema.org homepage reference, 'Organization of Schemas' section), increasing the specification usability beyond a unique business-specific domain. Schema.org homepage reference, 'About Schema.org' section: https://schema.org/docs/about.html Schema.org reference, Data model section: https://schema.org/docs/datamodel.html Schema.org homepage reference, 'Organization of Schemas' section: https://schema.org/docs/schemas.html"
'ETSI TS 119 512 is not related to multilingualism. Therefore this criterion is not related to this specification. ETSI TS 119 512 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.02_60/ts_119512v010102p.pdf'
There is a code validator for WS-BPEL that helps developers create well-formed, valid and standard-compliant code. The code is checked for errors and the user is notified if validation fails. The WS-BPEL Validator: https://docs.oracle.com/cd/E19182-01/821-0539/cnfg_bpel-guide-validation_r/index.html
'IPv6 allows data exchange between systems and it is compatible with the previous version IPv4. Furthermore, the European Union fosters IPv6 to the pursuing of the Digital Agenda for Europe and the Digital Single Market Strategy. "IPv6 framework for European Governments" Reference: https://ec.europa.eu/isa2/sites/isa/files/ipv6_framework_for_european_governments_0.pdf IPv6 IETF: https://www.rfc-editor.org/rfc/rfc2460'
'Preservation profiles may contain descriptions in more than one language, (see section 6.4 of the specification). Nontheless, specific provisions to this end are not given. ETSI TS 119 511 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119511/01.01.01_60/ts_119511v010101p.pdf'
'The purpose of DNS is not related to the publication of open data. Therefore this criterion is not applicable to this specification. DNS IETF referece: https://www.ietf.org/rfc/rfc1034.txt'
'Digital service delivery channels involve the use of digital technologies to provide services to users or customers. These channels can include websites, mobile applications, APIs (Application Programming Interfaces), and other digital platforms. The OSI model, as a conceptual framework, contributes to the development and interoperability of protocols that may be used in creating these digital service delivery channels. ISO/IEC 7498:1: https://www.iso.org/standard/20269.html'
Although XHTML is a reformulation of HTML 4 using XML, it is not dependant of any version of the two standards. So, XHTML is independent of any technology or software. XHTML W3C reference: https://www.w3.org/TR/xhtml1/
'At the moment of performing the assessment, the specification is associated with several ABB from the latest version published of the ELIS. More specifically, Better Regulation Guidelines and Toolbox can define the interoperability aspects of the Binding Instrument, Non-Binding Instrument, Public Policy, Legal Act, European Legal Act, National Legal Act, Granularity Of Legal Requirements, Public Policy Context Constraint, and Digital-ready Policy making ABBs of the EIRA Legal View. Better Regulation Guidelines and Toolbox reference: https://commission.europa.eu/law/law-making-process/better-regulation/better-regulation-guidelines-and-toolbox_en EIRA Library of Interoperability Specifications (ELIS): https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-andspecifications-camss/solution/camss-assessment-eif-scenario/release/610'
'ETSI TS 119 511 offers some provisions on the portability of documents containing digital signatures. This can be provided by preservation and validation services, whose main functions are to authenticate and preserve the chain of evidence of official documents. Nonetheless, ETSI TS 119 511 only specifies the requirements of these functionalities, while its companion document ETSI TS 119 512 provides the protocols to implement these services. Therefore, ETSI TS 119 511 supports the implementation of European public services. ETSI TS 119 511 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119511/01.01.01_60/ts_119511v010101p.pdf ETSI TS 119 512 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.02_60/ts_119512v010102p.pdf eIDAS blog, New APIs for the eIDAS-Ecosystem: https://blog.eid.as/tag/etsi-ts-119-512-en/'
FTPS is a secure internet protocol for the exchange of data over an Internet network. It makes data accessible on the web which is the first level of maturity defined in the Tim Berners-Lee's 5-star for Open Data. FTPS IETF reference: https://tools.ietf.org/html/rfc4217 Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/en/
'RDF itself does not provide bulit-in mechanisms to ensure data integrity. Nonetheless, there are various techniques and mechanisms that can be used to ensure the integrity, confidentiality and availability of RDF data. RDF primer document: https://www.w3.org/TR/rdf11-primer/'
'While HTTPS can facilitate secure data transfer, it does not provide specific mechanisms or standards for data portability. The ability to exchange data between systems and applications typically relies on other protocols, or data interchange formats such as JSON, XML, or CSV. HTTPS specification: https://tools.ietf.org/html/rfc2818'
'UBL is maintained and developed by OASIS, which is an international community developing open standards; specifically, by the Technical Committee (TC). The specification maintenance is transparent, and even if its development and the approval process is restricted to the specification TC, anyone can contribute by submitting feedback to the mailing list. All the contributions are publicly available. Developer community OASIS: https://www.oasis-open.org/org/'
The purpose of SAML 2.0 is not related to e-accessibility. Therefore, this criterion is not applicable to the specification.
'Although organisational interoperability agreements on the cybersecurity domain are not formalised (see Cybersecurity Act reference), the EN 303 645 specification establishes a cybersecurity baseline for connected consumer products and is intended to set the basis for future IoT certification systems in Europe (see IoT Policy and Legislation reference). This baseline comprises the set of provisions defined in the specification documentation, but is not specifically designed for establishing these agreements. EN 303 645 reference: https://www.etsi.org/deliver/etsi_en/303600_303699/303645/02.01.01_60/en_303645v020101p.pdf Cybersecurity Act reference: https://digital-strategy.ec.europa.eu/en/policies/cybersecurity-act#:~:text=The%20EU%20Cybersecurity%20Act%20introduces%20an%20EU-wide%20cybersecurity,see%20their%20certificates%20recognised%20across%20the%20European%20Union. IoT Policy and Legislation reference: https://joinup.ec.europa.eu/collection/rolling-plan-ict-standardisation/internet-things'
CAdES is referenced in the ETSI collection at the European Platform Joinup. Moreover, it can be found for free at ETSI’s webpage See: https://joinup.ec.europa.eu/solution/electronic-signatures-and-infrastructures-esi-cms-advanced-electronic-signature-formats-cades-part-3/about
'The purpose of ESI/REM is not related to the facilitation of modelling business processes, therefore it does not promote or hinder it. ETSI EN 319 532-3 reference: https://www.etsi.org/deliver/etsi_en/319500_319599/31953203/01.02.01_60/en_31953203v010201p.pd'
Having checked the documentation included in point 2.2.1, the conclusion has been reached of “RDA Data Collections API” not being foreseen to be transposed into a European standard within a reasonable time period.
At the moment of performing the assessment, PAdES is recommended by the European Union as an eSignature standard to ensure that electronic signatures can be created and validated anywhere in Europe. So, PAdES can be considered as an asset to build innovative solutions. eSignature standards: https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eSignature+standards PAdES ISO reference: https://www.iso.org/standard/67937.html PAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/102700_102799/10277801/01.01.01_60/ts_10277801v010101p.pdf
'HTTPS is at the center of many debates in the Joinup platform, where there can be found many forums with discussions on its iplementation. Joinup platdorm HTTPS discussions: https://joinup.ec.europa.eu/search?keys=https+&sort_by=creation-date&f%5B0%5D=type%3Adiscussion'
By allowing the association of information with a domain, DNS facilitate the identification of interfaces. Practically, instead of having a list of interfaces as "IP Addresses", DNS allows the identification "by name" of domain.
'Adherence to AS4 standard guarantees Domibus provision of access control mechanisms that allow administrators to define and manage user roles, permissions, and access rights within the messaging platform. These mechanisms enable organizations to control who can access and perform specific actions within Domibus. Domibus specification: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/Domibus AS4 specification: http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/profiles/AS4-profile/v1.0/AS4-profile-v1.0.html'
There are no Member States recommending XAdES (ISO 14533-2:2012) in their ICT National Catalogues. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
The purpose of XSD 1.1 is not related to e-accessibility. Therefore this criterion is considered not applicable to this specification.
There are no Member States recommending Better Regulation Toolbox in their ICT National Catalogues. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'The purpose of ebXML RepReg is not related to the protection of personal data. Therefore, this criterion is not applicable to this specification. ebXML reference, Notice section: http://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html'
'DNS is already associated to an EIRA ABB in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, DNS can define the interoperability aspects of the "Web Server" and "Data Exchange Application Component", "Application Server", "Domain Name Service" and "Data Exchange Application Service" ABBs of the EIRA Technical View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/v610'
'After being evaluated compliant with the regulation on standardisation 1025/2012, DNS has been identified by Commission Implementing Decision and included in the European list of ICT Standards for e-procurement. COMMISSION IMPLEMENTING DECISION (EU) 2017/168 of 31 January 2017 on the identification of ‘Internet Engineering Task Force’ Technical Specifications for referencing in public procurement: https://eur-lex.europa.eu/legal-content/EN/ALL/?uri=CELEX%3A32017D0168 Commission Implementing Decision of 3 April 2014 on the identification of ICT technical specifications eligible for referencing in public procurement : https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32014D0188'
The specification defines how different parties and transactions have to be done in order to allow proper discoverability and data exchanges. Therefore, it is defining organisational requirements for the data transaction between two or more parties. SMP OASIS reference: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505009
'While ISO/IEC 19944-1 does not specifically address data processing accuracy, it provides a foundation for organizations to establish data governance practices and security controls that indirectly contribute to accurate data processing. Organizations should complement ISO/IEC 19944-1 with additional best practices and standards to ensure data processing accuracy according to their specific requirements. ISO/IEC 19944-1 specification: https://www.iso.org/standard/60545.html'
'The Indexed Database API allows for extension. In this context, there are some available extensions that allow for the improvement of certain features of the specification. One of these extensions is the IndexedDB exporter, which allows for exporting Indexed Database API data to a JSON file. IndexedDB exporter extension: https://chromewebstore.google.com/detail/indexeddb-exporter/kngligbmoipnmljnpphhocajldjplgcj'
"Nowadays, SOAP 1.2 is a de-facto messaging protocol for exchanging information in a structured way, and invoke web services SOAP-based. It is used in a wide variety of solutions, while REST is widely used as well, SOAP remains as one of the main protocol to implement SOAs, and this fact includes innovative solutions. SOAP Reference: https://www.w3.org/TR/soap12/ REST Reference: https://docs.github.com/es/rest?apiVersion=2022-11-28 Advantage of SOA's and explanation Reference: https://medium.com/@amitbd1508/advantage-of-soa-over-msa-ee50636b9655"
The ELI Governance Rules Document establishes that decisions are made using working group discussions and having consensus. However, there is no public review as part of the decision making process. Even though there is no specific public review process open like public consultations, the specifications is evolved following the consensus of participants who are the Member States. ELI reference: https://eur-lex.europa.eu/eli-register/about.html Governance Rules: https://eur-lex.europa.eu/content/eli-register/governance_rules.pdf
'The specification covers the need for a top-level ontology designed to support information system interoperability expressed by ontology users in these and other areas. In this sense the specification can promote the visibility of administrations on the specific fields where they are operating, since users will be able to browse through them following the specific categories. BFO reference: https://www.iso.org/standard/74572.html'
'Genericode is recommended by four different European Member States. For instance, it is included in the Dutch ICT National Catalogue as a useful standard for defining code lists. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards Netherlands Open Standards Catalogue: https://www.forumstandaardisatie.nl/open-standaarden/aanbevolen'
'Genericode allows for customisation to meet specific requirements and use cases. Users can define their own code lists to represent values specific to their domain or application. These custom code lists can include any relevant codes and associated metadata needed for their particular use case. Besides, users can also customise metadata elements to provide additional context, descriptions, or usage guidelines for the codes within their code lists. Code List Representation (genericode): https://docs.oasis-open.org/codelist/genericode/v1.0/os/genericode-v1.0-os.html'
'While ISO/IEC 7498:1 specifies the functions of seven abstraction layers, it does not explicitly address administrative procedures, rules data, or services in the context of visibility. Nonetheless, by adhering to ISO 11179, organizations ensure that their procedures for managing metadata are transparent and well-documented. This transparency facilitates understanding and collaboration among stakeholders involved in data management processes, ultimately promoting more efficient and effective data governance. ISO/IEC 7498:1: https://www.iso.org/standard/20269.html'
6 Member States are recommending FTP in their ICT Catalogues. See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'SOAP 1.2 can be used independently from any other technical specifications or operating system. As is shown in the SOAP 1.2 FAQ from W3C, SOAP can be adopted with no dependence on WSDL. SOAP Reference: https://www.w3.org/TR/soap12/ WSDL Reference: https://www.ibm.com/docs/es/rsas/7.5.0?topic=standards-web-services-description-language-wsdl '
'As defined on the OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) Technical Committee (TC), only TC members are involved in the development of TOSCA. External contribution to this committee is possible through open channels (see Mail Lists and Comments reference). OASIS TOSCA TC reference: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=regrep Mail Lists and Comments reference: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=tosca#feedback'
The Standard for Public Code is a set of criteria that supports public organizations in developing and maintaining software and policy together. So it can be said that it is independent of any platform or technology. The Standard for Public Code webpage: https://standard.publiccode.net/
'The Better Regulation Guidelines and Toolbox provides with means to define a legal framework where the secure and trustworthy data exchange between citizens, businesses and public administrations is ensured. The tool set provides some checklists methods to helps the development of public policies that guarantee secure and trustworthy data processing. Better Regulation Guidelines and Toolbox reference: https://commission.europa.eu/law/law-making-process/better-regulation/better-regulation-guidelines-and-toolbox_en Better Regulation Toolbox reference: https://commission.europa.eu/document/download/9c8d2189-8abd-4f29-84e9-abc843cc68e0_en?filename=BR%20toolbox%20-%20Jul%202023%20-%20FINAL.pdf'
'The specification allows secure messaging channels or share confidential documents. The cryptographic techniques allow secure exchange of documentation and information, making DIDs useful for the secure exchange of data. DIDs restriction of access W3C: https://www.w3.org/TR/did-core/#keep-personal-data-private'
'Although MIME itself does not address data protection issues, it can be extended by the Secure Multipurpose Mail Extension (S/MIME) to enhance the security and privacy of email communications, thus contributing to the protection of personal data. MIME specification: https://tools.ietf.org/html/rfc2045 S/MIME specification: https://www.rfc-editor.org/rfc/rfc5751.html'
The specification is available for its use and implementation at the IETF's webpage defined in several RFCs. SMTP IETF reference: https://tools.ietf.org/html/rfc5321 SMTP Service Extension for Delivery Status Notifications: https://tools.ietf.org/html/rfc3461
DCAT is available on Joinup, the collaborative platform created by the European Commission to share and reuse IT solutions and good practices. See: https://joinup.ec.europa.eu/solution/data-catalog-vocabulary-0
At the moment of performing the assessment, XHTML is used in some cases to develop web pages. However, with the increasing usage of HTML5, no evidences have been found to consider XHTML as an asset to build innovative solutions.
'IPsec, which is included in the IPv6 protocol, guarantees the authenticity and integrity of the sent data. IPsec ensures that the content will not change from the original that was sent by the issuer, and that data will reliably reach the receiver. IPsec IONOS reference: https://www.ionos.es/digitalguide/servidores/know-how/ipsec-arquitectura-de-seguridad-para-ipv4-e-ipv6/'
'The purpose of the NFVI specification is not related to the comprehensibility of administrative procedures, rules data, and services. NFV reference: https://www.etsi.org/technologies/nfv/nfv'
'Core Location Vocabulary is not included in any national catalogue of recommended specifications. NIFO Factsheets: https://interoperable-europe.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public-administration-factsheets-2024 CAMSS list of standards: https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards Core Location Vocabulary: https://interoperable-europe.ec.europa.eu/collection/semic-support-centre/solution/core-location-vocabulary/release/100'
The Data on the Web Best Practices can apply to any technology that can publish data on the web. So it can be said that it is independent of any platform or technology. W3C reference: https://www.w3.org/TR/dwbp/
'There is existing documentation and studies assessing the efficiency of Indexed Database API. The "The role of HTML5 IndexedDB, the past, present and future" study, outlines the background study and the importance of new technologies, such as HTML5's new browser based storage called IndexedDB. In addition, it is proposed a solution to IndexedDB's known security issues in form of a security model, which will extend the current model. "The role of HTML5 IndexedDB, the past, present and future" study: https://ieeexplore.ieee.org/abstract/document/7412126'
CAMSS Assessment of ETSI TS 119 612 EIF Scenario v1.0.0
'The PROV family of documents provides a standardized approach to the representation of provenance information, which can enhance the publication, discovery, and consumption of data on the web by promoting transparency, accountability, and data quality. Moreover, the PROV Ontology (PROV-O) provides a semantic representation of the PROV Data Model (PROV-DM), which allows for linking provenance information with other related metadata and vocabularies on the web. This facilitates the integration and interoperability of data from different sources, as well as the discovery and exploration of datasets based on their provenance characteristics. PROV Primer document: https://www.w3.org/TR/prov-primer/ PROV Ontology: https://www.w3.org/TR/2013/REC-prov-o-20130430/ PROV Data Model: https://www.w3.org/TR/2013/REC-prov-dm-20130430/'
The purpose of this document is not related to the delivery of multilingual public services. Therefore, this criterion is not applicable to the specification. W3C Reference: https://www.w3.org/TR/dwbp/
'The hub format of the UBL is well suited to the public sector. A single adapter interfaces all suppliers to a common consumer and vice versa. It also interfaces all businesses to tax authorities, custom agents, transporters and accountants. Therefore, UBL can be considered a strong enabler of external interfaces for European Public Services. For instance, in the ESPD project, UBL XML behaves as an interface document between tenders and public administrations.\xa0 UBL v2.3 reference: http://docs.oasis-open.org/ubl/os-UBL-2.3/UBL-2.3.html ESPD reference, Legal framework and context section: https://docs.ted.europa.eu/ESPD-EDM/3.0.1/xml_business_handbook.html#_i_1_1_legal_framework_and_context'
SAMM is publicly available for implementation and study for free in its dedicated webpage. SAMM webpage: https://owaspsamm.org/ SAMM documentation: https://github.com/OWASP/samm/blob/master/Supporting%20Resources/v2.0/OWASP-SAMM-v2.0.pdf SAMM model: https://owaspsamm.org/model/
DCAT allows the exchange of metadata across borders which, in some cases can reduces administrative burden.
'TOSCA is maintained and developed by OASIS, which is an international community developing open standards; specifically, by the OASIS TOSCA Technical Committee (OASIS TOSCA TC). The specification maintenance is transparent, and even if its development and the approval process is restricted to the specification TC, anyone can contribute by submitting feedback to the mailing list. All the contributions are publicly available. Developer community OASIS: https://www.oasis-open.org/org/ OASIS TOSCA TC reference: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=regrep'
'REST architectural style streamlines administrative processes by easing the communication and digital exchange of information between clients and servers. For that matter, the implementation of REST architectural constraints helps to simplify the delivery of European Public Services. REST reference: https://restfulapi.net/rest-architectural-constraints/'
Germany is recommending FTPS in their ICT National Catalogues. National catalogue Germany: http://www.cio.bund.de/SharedDocs/Publikationen/DE/Architekturen-und-Standards/SAGA/saga_modul_tech_spez_de_bund_5_0_download.pdf?__blob=publicationFile
'There has not been found any Member State recommending the DPV specification. DPV specification: https://w3c.github.io/dpv/primer/'
The main purpose of CPOV is to provide a reusable data model for describing public organisations in the European Union. It manages a public portfolio that facilitates the discovery of which public authorities and departments are responsible for given areas of the public task. So, it facilitates the visibility of administrative rules. CPOV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-organisation-vocabulary
'XSD is a business domain agnostic specification that can be used at any business domain. XSD Reference: https://www.w3.org/TR/2012/REC-xmlschema11-1-20120405/'
The purpose of the specification is not related to the visibility of administrative rules, data, services, and the decision-making process. Therefore, this criterion does not apply to this specification. XACML OASIS reference: http://docs.oasis-open.org/xacml/3.0/errata01/xacml-3.0-core-spec-errata01.html
'As the SPECIAL project example shows, DPV is encouraging the creation of communities in European Platforms through the DPV Community Group where knowledge and data is shared to contribute to the regulation of data privacy. DPV specification: https://w3c.github.io/dpv/primer/ Special contribution in DPV: https://specialprivacy.ercim.eu/dpvcg/176-special-activity-in-w3c-standardisation'
PAdES Baseline Profile is available for free at the ETSI’s Catalogue of Standards. See: https://www.etsi.org/deliver/etsi_ts/103100_103199/103172/02.02.02_60/ts_103172v020202p.pdf https://www.etsi.org/standards
'The purpose of Extensible Forms Description Language is not related to secure processing of data. Therefore, this criterion is not applicable to the specification. Extensible Forms Description Language reference: https://www.w3.org/TR/NOTE-XFDL'
ADMS’s purpose is the description of Assets within a Catalogue (repository), making them easy to discover and reuse. However, it is not related to foster the one-only principle between administrations and stakeholders. ADMS Specification W3C: https://www.w3.org/TR/vocab-adms/
' YAML is not listed as an official standard by European standardization organizations like CEN (European Committee for Standardization) or ETSI (European Telecommunications Standards Institute). YAML specification: https://yaml.org/spec/1.2.2/'
'Section 8.7 of the protocol addresses data integrity but does not mention any specific provision. Furthermore, section 5 mentions that the document does not specify any transport layer protocol. Even so, it is specified that any syslog transport protocol must not deliberately alter the syslog message. Syslog Protocol Message integrity: https://datatracker.ietf.org/doc/html/rfc5424#section-8.7 Syslog Protocol Transport Layer Protocol: https://datatracker.ietf.org/doc/html/rfc5424#section-5'
Standard for Public Code is publicly available for implementation and study for free in its dedicated webpage. The Standard for Public Code webpage: https://standard.publiccode.net/
DCAT-AP is made available by SEMIC for free on Joinup, the collaborative platform created by the European Commission to share and reuse IT solutions and good practices. See: https://joinup.ec.europa.eu/solution/dcat-application-profile-data-portals-europe/releases
"The EN 303 645 specification ensures the protection of personal data according to the sixth clause of the specification documentation (see EN 303 645 reference, section 6 'Data protection provisions for consumer IoT'). Moreover, as an ETSI specification, EN 303 645 is compliant with all the European Regulations and Policies (see ETSI Role in Europe reference). EN 303 645 reference, section 6: https://www.etsi.org/deliver/etsi_en/303600_303699/303645/02.01.01_60/en_303645v020101p.pdf ETSI Role in Europe reference: https://www.etsi.org/about/etsi-in-europe?highlight=WyJldXJvcGVhbiIsIidldXJvcGVhbiIsImV1cm9wZWFuJ3MiLCJyZWd1bGF0aW9ucyIsImV1cm9wZWFuIHJlZ3VsYXRpb25zIl0="
"UDDI is developed and maintained by OASIS, which is an International Organisation developing Standards. After finishing UDDI's last version (v3) the Technical Committee was closed. Furthermore, there is at least another community which provides support to people who uss UDDI. This community is uddixml.org, and it's hosted by OASIS. UDDI OASIS reference: https://www.oasis-open.org/committees/uddi-spec/doc/spec/v3/uddi-v3.0.2-20041019.htm#_Toc85907967 UDDI XML reference: https://uddi.xml.org/"
'The alignment data and information with a standardized vocabulary such as EuroVoc can contribute to smoother data transfer and understanding across different platforms, indirectly supporting aspects of data portability. EuroVoc: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource /dataset/eurovoc'
'ISO/IEC 7498:1 is not included in any national catalogue of recommended specifications whose Member State NIF has a high performance on interoperability according to NIFO factsheets. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards NIFO Factsheets: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public-administration-factsheets-2023'
The purpose of UDDI is not related data portability, therefore this criterion is considered not applicable to this specification.
Even though the version assessed is a very recent version of the specification, it has a strong community supporting it with a clear process of development that has been working towards the maximisation of quality and usefulness. So it can be used in the development of products and services. SAMM webpage: https://owaspsamm.org/ SAMM documentation: https://github.com/OWASP/samm/blob/master/Supporting%20Resources/v2.0/OWASP-SAMM-v2.0.pdf
The once-only principle is an e-government concept that aims to ensure that citizens, institutions, and companies only have to provide certain standard information to the authorities and administrations once. LDAP fosters the OOP in terms of accessibility by allowing administrations stakeholders to keep the contact and access to different distributed services without providing personal data for authentication more than strictly needed. LDAP IETF reference: https://tools.ietf.org/html/rfc4511
Even the document defining the standard is available under charge, the specification is licensed under royalty-free basis and (F)RAND basis as the disclosures shown. Additionally, the patent holder Adobe did available by means of a non-ISO document. See: https://www.iso.org/standard/51502.html https://www.adobe.com/content/dam/acom/en/devnet/pdf/pdfs/PDF32000_2008.pdf
• The prototype is openly available on-line at DLI Service http://dliservice.research-infrastructures.eu/#/ • Fifteen organisations (including representatives of publishers, data centres, registries, and global service providers) have contributed over 1.4 million data¬literature links into the system. • The proposed long¬term approach to sharing information about the links between the literature and research data (the “SCHOLIX” model) is adopted by CrossRef , DataCite , and OpenAIRE . • Europe PubMedCentral has adopted the DLI metadata standards to describe article/data links in their system, such that the DLI can harvest these links and include them in the service. This dcates the way for fuller interoperability between that system and the DLI. • The RD¬switchboard, which was delivered by the RDA WG “Data Description Registry Interoperability (DDRI)”, is ingesting links from the DLI to combine with other content sources to obtain a more comprehensive network of connected scholarly entities. • The WG received an ad¬hoc request to provide a listing of related data for a set of articles. This was delivered using the DLI’s OAI-PMH interface. • In addition to this, a number of data repositories are currently exploring how to connect with the DLI system to offer a “related publications” kind of functionality to users of their web portals. • Any party that is interested to explore the current corpus of links in the DLI system can freely connect with the system using any of the existing services (web portal, OAI¬PMH delivery, or API connections). • More details on adoption and the service are available on the Scholix public web site http://www.scholix.org/
'DNS comprises different types of security extensions (DNSSEC) among which one can be found to cover the protection of personal data in a way that authenticates the origin and integrity of the data. Protocol Modifications for the DNS Security Extensions: https://datatracker.ietf.org/doc/html/rfc4035 DNS Security Introduction and Requirements: https://datatracker.ietf.org/doc/html/rfc4033#section-3.1'
eDelivery SMP 1.10 is available for everyone to study and implement for free. The specification can be found at Connecting Europe Facility’s (CEF) webpage. See: https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery+SMP+-+1.10
TIFF/IT is high quality image format, it is used to send data for print-ready pages that have been designed on high-end prepress systems. Also, it uses lossless compression. Although the specification complies with the first level of maturity of Tom Berners-Lee's 5-star schema for Open data, it is not enough to consider TIFF/IT as an asset to facilitate the publication of open data. Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/es/ TIFF/IT ISO reference: https://www.iso.org/standard/34342.html
'The XFDL specification itself does not provide direct mechanisms for restricting access to information or data. However, it can be integrated with external systems that enforce access control. For instance, role-based permissions can be applied to XFDL forms, allowing only authorised users to access or modify specific data. Additionally, sensitive information can be secured through features like digital signatures, ensuring that only authorised parties can verify and view the signed data. In this context, the XML Signature Syntax and Processing specification offers a manner to sign data of any type. XML Signature Syntax and Processing reference: https://www.w3.org/TR/xmldsig-core1/ XFDL privacy reference: https://www.w3.org/TR/NOTE-XFDL#button'
'The purpose of DNS is not related to long term preservation of electronic records. Therefore this criterion is considered not applicable to this specification. DNS IETF reference: https://www.ietf.org/rfc/rfc1034.txt'
"The specification is included in two Member States' catalogues of recommended specifications. These Member States are Germany and Norway. Moreover, the specification is not mentioned in any other reference catalogue at European level. Catalogue reference Germany: https://www.cio.bund.de/Web/DE/Architekturen-und-Standards/SAGA/SAGA%205-aktuelle%20Version/saga_5_aktuelle_version_node.html Catalogue reference Norway: https://www.difi.no/fagomrader-og-tjenester/digitalisering-og-samordning/standarder CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards"
'HTTPS is included in 7 national catalogues of recommended specifications. They belong to Croatia, Cyprus, France, Germany, Greece, Portugal, and Sweden. The National Interoperability Framework (NIF) of France and Germany is fully alignes with at least 2 out of 3 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. CAMSS List of standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards NIFO Factsheets: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-publicadministration-factsheets-2022 National Catalogue of France: https://www.numerique.gouv.fr/uploads/Referentiel_General_Interoperabilite_V2.pdf'
'iCalendar can defined parametres in multiple languages, fully supporting multilingualism and internationalisation. For example, the specificaiton enables to define parametres of a same property when two different languages for a time zone exists. iCalendar specification: https://www.rfc-editor.org/rfc/rfc5545'
'DAPS is included in the “Data Spaces Support Centre” (DSSC), an initiative funded by the European Commission to facilitate data sharing and link the expertise of data sharing practitioners and researchers. The collected standards for Data Sovereignty and Trust include DAPS. DSSC Data Sovereignty and Trust standards and technologies landscape: https://dssc.eu/space/SE1/185794711/Data+Sovereignty+and+Trust+standards+and+technologies+landscape'
The purpose of UTF-8 is not related to e-accessibility. Therefore this criterion is not applicable specification.
'As a system requirement enabler for the availability of spatial data among EU public administrations, ISO 3166-1 facilitates digital service delivery channels for the exchange, sharing, access and use of interoperable spatial data and spatial data services at different levels of public authority and in different sectors (see INSPIRE Data Specification on Administrative Units reference and INSPIRE reference, Directive 2007/2/EC document, Article 1). ISO 3166-1 reference: https://www.iso.org/standard/72482.html INSPIRE Data Specification on Administrative Units reference: https://inspire.ec.europa.eu/id/document/tg/au INSPIRE reference, Directive 2007/2/EC document, Article 1: https://inspire.ec.europa.eu/inspire-legislation/26'
'DNS is the hierarchical and decentralised naming system used to identify computers reachable through the Internet or other Internet Protocol (IP) networks. For that matter it can be used in any domain. DNS IETF reference: https://datatracker.ietf.org/doc/html/rfc8499 Domain Names - Implementation and Specification: https://tools.ietf.org/html/1035'
The rules on European standardisation allow the European Commission to identify information and communication technology (ICT) technical specifications - that are not national, European or international standards - to be eligible for referencing in public procurement. This allows public authorities to make use of the full range of specifications when buying IT hardware, software and services, allowing for more competition in the field and reducing the risk of lock-in to proprietary systems. After being evaluated compliant with the regulation on standardisation 1025/2012, HTTPS has been identified by Commission Implementing Decision. During the evaluation process, all the Member States are invited to share their doubts. The positive evaluation of HTTPS and its identification is considered an interoperability agreement. See: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en
'XML is included in several national catalogues from EU Member States. A total of 14 countries listed the XML within their national catalogues (e.g. Belgium, France, Germany, etc.). See Belgium Reference: https://www.belgif.be/nl/specifications See France Reference: http://references.modernisation.gouv.fr/sites/default/files/Referentiel_General_Interoperabilite_V2.pdf See Germany Reference: http://www.cio.bund.de/SharedDocs/Publikationen/DE/Architekturen-und-Standards/SAGA/saga_modul_tech_spez_de_bund_5_0_download.pdf?__blob=publicationFile '
'HTTP appears in Interoperable Europe Portal (also known before as Joinup) as one of the identified ICT specifications for procurement. ICT standards for procurement: https://interoperable-europe.ec.europa.eu/collection/ict-standards-procurement/identified-ict-specifications-procurement'
'The purpose of IPsec is not related to long-term preservation of electronic records. Therefore, this criterion is considered not applicable to this specification. IPSec reference, How IPSec Works: https://datatracker.ietf.org/doc/html/rfc4301#page-9'
'DQV adresses and enables data portability between systems/applications supporting the implementation or evolution of European public services by providing them with the means to describe and manage data quality, which can support data portability initiatives within the European public services ecosystem. Furthermore, one of the quality dimensions defined in section 7.2 is data portability. Data Quality Vocabulary Section 7: https://www.w3.org/TR/vocab-dqv/#DimentsionsMetricsHints'
'There is no evidence found of the creation of any community along with the sharing of their data and resultson national platforms. Therefore this criterion is not applicable to this specification. IPSec reference, What IPSec Does: https://datatracker.ietf.org/doc/html/rfc4301#page-7 IPSec reference: https://datatracker.ietf.org/doc/html/rfc4301'
'TOSCA is included in the EUOS European catalogue of standards. EUOS reference: https://www.standict.eu/standards-repository'
Like all the IETF standards, IPSec is a free and open technical specification, built on IETF standards and licenses from the Open Web Foundation. IPsec is therefore licensed on a royalty-free basis. No IPR disclosures have been submitted directly on the IPsec specification (RFC 4305). See: https://tools.ietf.org/html/rfc3668 https://tools.ietf.org/html/rfc4301
CAMSS Assessment of XML EIF Scenario v3.0.0
"The specification does encourage the creation of communities along with the sharing of their data on European platforms, such as the case of European legislation Identifier ELI XML serialisation._x000D_ Furthermore, XML also has created a wide variety of discussions regarding it's implementation and its features in places like Stack-overflow._x000D_ _x000D_ Stack-overflow dicussion on XML versions:_x000D_ https://stackoverflow.com/questions/6260975/should-i-learn-xml-1-0-or-xml-1-1_x000D_ _x000D_ Stack-overflow dicussion on XML implementation:_x000D_ https://stackoverflow.com/questions/6883084/what-xml-version-to-use_x000D_ _x000D_ Stack-overflow question regarding browsers:_x000D_ https://stackoverflow.com/questions/4508283/xml-version-1-1-not-accepted-by-browsers_x000D_ _x000D_ ELI XML serialisation:_x000D_ https://interoperable-europe.ec.europa.eu/collection/eli-european-legislation-identifier/solution/eli-xml-serialisation_x000D_ _x000D_ XML 1.1 W3C reference:_x000D_ https://www.w3.org/TR/xml11/"
'The purpose of XML is not related to the long-term preservation of electronic records and other kinds of information per se but it can be adapted for storing descriptive and administrative metadata, as show by the DiVA project._x000D_ In this sense it is also worth mentioning the XAdES specification that provides with long term signature preservation._x000D_ _x000D_ DiVA project reference:_x000D_ https://edoc.hu-berlin.de/server/api/core/bitstreams/d5f02188-85d2-444b-9cb9-0845df86af7f/content_x000D_ _x000D_ XML Advanced Electronic Signatures (XAdES) reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31913201/01.03.01_60/en_31913201v010301p.pdf_x000D_ _x000D_ XML 1.1 W3C reference:_x000D_ https://www.w3.org/TR/xml11/'
'The effectiveness of the XML specification has been assessed by the Eindhoven University of Technology (The Netherlands). The "XML interoperability standards for seamless communication: An analysis of industry-neutral and domain-specific initiatives" study, addresses XML in a central and comprehensive manner as a key foundation for achieving interoperability in the e-business environment. In addition, it is noted that the XML format is gaining importance in industry-specific e-business frameworks and dominates in cross-sectoral e-business process frameworks._x000D_ _x000D_ "XML interoperability standards for seamless communication: An analysis of industry-neutral and domain-specific initiatives" study:_x000D_ https://www.sciencedirect.com/science/article/pii/S0166361516302160_x000D_ _x000D_ XML 1.1 W3C reference:_x000D_ https://www.w3.org/TR/xml11/'
'XML can be used independently from any other technical specifications or operating system. It works in all browsers and applications that support it._x000D_ _x000D_ XML and browser:_x000D_ https://kinsta.com/blog/xml-vs-html/_x000D_ _x000D_ XML 1.1 W3C reference:_x000D_ https://www.w3.org/TR/xml11/'
'XML can be used independently from any other technical specifications or operating system. Furthermore, It can be used by any technology (i.e. JAVA) for data storage and data transfer purposes. _x000D_ Formats like RDF or HTML can be encoded within XML without affecting interoperability. This flexibility allows diverse data types and structures to be integrated and exchanged seamlessly across different systems as in the European legislation Identifier ELI XML serialisation._x000D_ The ELI/XML schema is provided with a set of XML transformations to generate ELI in RDF/XML, RDFa header or HTML+RDFa. It is meant to facilitate the integration of ELI in XML-based document workflows._x000D_ _x000D_ ELI XML serialisation:_x000D_ https://interoperable-europe.ec.europa.eu/collection/eli-european-legislation-identifier/solution/eli-xml-serialisation_x000D_ _x000D_ RDF reference:_x000D_ https://www.w3.org/TR/rdf-primer/_x000D_ _x000D_ RDFa reference:_x000D_ https://www.w3.org/TR/rdfa-primer/_x000D_ _x000D_ RDFa HTML reference:_x000D_ https://www.w3.org/TR/html-rdfa/_x000D_ _x000D_ XML in JAVA: _x000D_ https://www.tutorialspoint.com/java_xml/java_xml_quick_guide.htm_x000D_ _x000D_ XML 1.1 W3C reference:_x000D_ https://www.w3.org/TR/xml11/'
'XML is machine readable format that is specifically created to allow the publication of data on the web. In this sense, this corresponds with one of the five elements that constitute open data according to Tim Berners-Lee deployment scheme._x000D_ Additionally, RDF is a W3C specification that defines XML syntax for RDF, the de facto standard for publishing Linked Open Data._x000D_ _x000D_ Tim Berners-Lee 5 star open data:_x000D_ https://5stardata.info/en/_x000D_ _x000D_ RDF syntax:_x000D_ https://www.w3.org/TR/rdf-syntax-grammar/_x000D_ _x000D_ XML 1.1 W3C reference:_x000D_ https://www.w3.org/TR/xml11/'
'The XML specification has published extensive documentation regarding its supporting processes on the XML Core working group page._x000D_ _x000D_ XML is widely used and is the default standard for many products and services across the globe since its original recommendation by W3C in 1996. In this sense the specification has been in constant development for a long time and a lot of minor issues have been corrected over the different versions._x000D_ _x000D_ Finally, a new XML version, rather than a set of errata to XML 1.0, is being created because the changes affect the definition of of the characters permitted on the names (Name characters). Since Unicode is ever expanding it is reasonable that XML is prepared to allow any character to avoid future limitations._x000D_ _x000D_ XML Core working group:_x000D_ https://www.w3.org/XML/Core/_x000D_ _x000D_ XML reference with difference highlight from previous version:_x000D_ https://www.w3.org/TR/2008/REC-xml-20081126/REC-xml-20081126-review.html_x000D_ _x000D_ XML 1.1, section "Rationale and list of changes for XML 1.1":_x000D_ https://www.w3.org/TR/2006/REC-xml11-20060816/#sec-xml11_x000D_ _x000D_ XML 1.1 W3C reference:_x000D_ https://www.w3.org/TR/xml11/'
"XML promotes interoperability between public administrations and cross-border services, supporting the development of eGovernment. It provides rules for encoding documents in both human- and machine-readable formats, enhancing data reusability and system interoperability. XML also allows the creation of custom tags and attributes, which can be defined once and reused across multiple applications for consistent and flexible information representation. Additionally, XSD defines the elements, attributes, and data types in an XML document, enabling schema and information reuse across different contexts._x000D_ _x000D_ For example, the European Single Procurement Document (ESPD) is a standardised, electronic self declaration used in public procurement across the EU that is based on XML 1.0. It simplifies the electronic procurement for SME's since at it's core it reduces the administrative burden. _x000D_ _x000D_ XSD reference:_x000D_ https://www.w3schools.com/xml/schema_intro.asp_x000D_ _x000D_ ESPD reference:_x000D_ https://ec.europa.eu/isa2/solutions/european-single-procurement-document-espd_en/ _x000D_ _x000D_ XML 1.1 W3C reference:_x000D_ https://www.w3.org/TR/xml11/"
'XML is a markup language designed for the structuring and representation of data. By itself it does not provide means to restrict the access to the data but in order to ensure certain degree of data protection the specification has some methods to provide some degree of protection to the information exchanged on the system._x000D_ In light of this, by using the XML Encryption Syntax and Processing, permits the encryption of an entire XML file or certain portions of it. Thus, by encrypting data, restriction access is applied to guarantee that only authorised users can access data._x000D_ _x000D_ XML Encryption Syntax and Processing reference:_x000D_ https://www.w3.org/TR/xmlenc-core1/_x000D_ _x000D_ XML 1.1 W3C reference:_x000D_ https://www.w3.org/TR/xml11/'
'XML is used to encode all communications between web services. Therefore, it fosters the visibility and comprehensibility of public administrations data and services. This is achieved with XML because it enables a standarised description of data via a machine readable format that can be later on transformed to other more user friendly formats like PDF, CSV and others._x000D_ An example of such application is the eForms service for Public procurement standards on the European Union._x000D_ _x000D_ eForms reference:_x000D_ https://docs.ted.europa.eu/eforms/latest/schema/introduction.html_x000D_ _x000D_ XML 1.1 W3C reference:_x000D_ https://www.w3.org/TR/xml11/'
'XML is maintained by W3C which is an international community developing open standards. Specifically by the XML Core Working group._x000D_ _x000D_ XML Core working group:_x000D_ https://www.w3.org/XML/Core/_x000D_ _x000D_ XML 1.1 W3C reference:_x000D_ https://www.w3.org/TR/xml11/'
'The purpose of XML is to store, transport and exchange data through interoperable systems. In this sense, XML defines a set of rules for encoding documents in a human-readable format and machine-readable format alike, enhancing the re-usability of data and therefore allowing the data portability among systems and services._x000D_ _x000D_ Additionally, W3C develops its specification independently from any vendor. So, the adoption of XML does not hamper the data portability of data expressed with it. In fact, the adoption of XML fosters data portability, especially between REST APIs._x000D_ _x000D_ XML 1.1 W3C reference:_x000D_ https://www.w3.org/TR/xml11/'
'XML provides the foundation for creating structured data, and developers and organisations then use that foundation to build specific languages for their particular domains. In this sense the specification is domain agnostic._x000D_ _x000D_ XML 1.1 W3C reference:_x000D_ https://www.w3.org/TR/xml11/'
'The XML specification itself does not provide an access control mechanism. Therefore this criterion is not applicable to the specification._x000D_ However, it is worth mentioning that if authentication methods are applied to the exchange it can be verified the number of users accessing the data. In this sense, if the signature and encryption extensions are applied, certain degree of access control can be achieved._x000D_ _x000D_ W3C XML Signature Syntax and Processing:_x000D_ https://www.w3.org/TR/xmldsig-core/_x000D_ _x000D_ W3C XML Encryption Syntax and Processing:_x000D_ https://www.w3.org/TR/xmlenc-core1/_x000D_ _x000D_ XML 1.1 W3C reference:_x000D_ https://www.w3.org/TR/xml11/'
'XML is a cornerstone of Web Services, which provide a standardised way for applications to communicate over the internet. Many e-government initiatives use Web Services to provide public services, with XML messages forming the core of these communications, enabling automated interactions between government systems and external applications. _x000D_ _x000D_ XML 1.1 W3C reference:_x000D_ https://www.w3.org/TR/xml11/'
'XML can be found a part from XAdES in the context of eDelivery SMP 2.0. In this sense, SMP documents are defined in XML format. By using these XML documents, organisations’ systems can publish and consume service metadata in a standardised and machine-readable format, thereby supporting organisational interoperability._x000D_ _x000D_ eDelivery SMP 2.0 reference:_x000D_ https://ec.europa.eu/digital-building-blocks/sites/display/DIGITAL/eDelivery+SMP+-+2.0_x000D_ _x000D_ XML Advanced Electronic Signatures (XAdES) reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31913201/01.03.01_60/en_31913201v010301p.pdf_x000D_ _x000D_ XML 1.1 W3C reference:_x000D_ https://www.w3.org/TR/xml11/'
'The specification provides a syntax for exchanging information that can be validated against a schema designed to protect data processing. In this sense, XML can be extended with other security specifications, such as the XML Signature Syntax and Processing. This specification can help to encrypt XML data, ensuring its trustworthiness by protecting it from unauthorised users. Thus, data remains in the same form as it was initially sent._x000D_ _x000D_ For further information in the Fog and Edge Computing from ENISA report, the XML specification addresses data security and trustworthy data processing._x000D_ _x000D_ Fog and Edge Computing in 5G report:_x000D_ https://www.enisa.europa.eu/publications/fog-and-edge-computing-in-5g_x000D_ _x000D_ W3C XML Encryption Syntax and Processing:_x000D_ https://www.w3.org/TR/xmlenc-core1/_x000D_ _x000D_ XML 1.1 W3C reference:_x000D_ https://www.w3.org/TR/xml11/'
'The XML specification is included in 17 Member States catalogues of recommended specifications. These Member States are Bulgaria and Croatia, among others._x000D_ _x000D_ Bulgaria reference:_x000D_ https://www.mtitc.government.bg/upload/docs/2016-01/BNIF_EN.pdf_x000D_ _x000D_ Croatia reference:_x000D_ https://ssi.gov.hr/en/catalogue_x000D_ _x000D_ CAMSS list of standards:_x000D_ https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards_x000D_ _x000D_ XML 1.1 W3C reference:_x000D_ https://www.w3.org/TR/xml11/'
'The XML specification itself does not provide inherent mechanisms to ensure or enable data processing accuracy per se. However, there are complementary specifications, such as the XML Encryption Syntax and Processing specification, that can work together to enhance the trustworthiness of data, ensuring that the data received is the same as that sent and that it has not been modified._x000D_ _x000D_ W3C XML Encryption Syntax and Processing:_x000D_ https://www.w3.org/TR/xmlenc-core1/_x000D_ _x000D_ XML 1.1 W3C reference:_x000D_ https://www.w3.org/TR/xml11/'
'XML is a de-facto standard markup language that is used in a wide variety of solutions, including innovative solutions across multiple domains. In this regard it is worth mentioning that version 1.1 is not as widely implemented as version 1.0. In this sense, one of the most relevant European services, the European Single Procurement Document (ESPD) is developed in XML 1.0._x000D_ _x000D_ A part, the lastest release of XML 1.1 revolves around Unicode ever expanding, therefore XML is prepared to allow any character to avoid future limitations by expanding the definition of of the characters permitted on the names (Name characters)._x000D_ _x000D_ ESPD reference:_x000D_ https://ec.europa.eu/isa2/solutions/european-single-procurement-document-espd_en/ _x000D_ _x000D_ XML reference with difference highlight from previous version:_x000D_ https://www.w3.org/TR/2008/REC-xml-20081126/REC-xml-20081126-review.html_x000D_ _x000D_ XML 1.1 W3C reference:_x000D_ https://www.w3.org/TR/xml11/'
'XML documents are based on Unicode, which supports all writing systems. Therefore, any language can be used in an XML document. Additionally, XML can be encoded using formats like UTF-8, ensuring that all languages can be properly included and represented in XML documents. _x000D_ In addition, it is worth mentioning that in the XML 1.0 specification is mentioned that all XML processors must accept the UTF-8 and UTF-16 encodings of Unicode. However, certain Unicode encodings, like UTF-16, can result in larger file sizes compared to single-byte encodings, potentially impacting storage and transmission efficiency._x000D_ _x000D_ UTF-8 reference: _x000D_ https://www.rfc-editor.org/rfc/rfc3629 _x000D_ _x000D_ UTF-16 reference: _x000D_ https://www.iso.org/standard/76835.html _x000D_ _x000D_ XML 1.0 reference:_x000D_ https://www.w3.org/TR/xml/_x000D_ _x000D_ XML 1.1 W3C reference:_x000D_ https://www.w3.org/TR/xml11/'
'XML is used to represent data steaming from business processes, in this sense the specification is the backbone to exchange data and therefore analise and model any process coming from it. Furthermore ebXML is a prime example of this._x000D_ _x000D_ ebXML reference:_x000D_ https://docs.oasis-open.org/ebxml-msg/ebms/v3.0/core/ebms_core-3.0-spec.html_x000D_ _x000D_ XML 1.1 W3C reference:_x000D_ https://www.w3.org/TR/xml11/'
'The XML 1.1 specification is developed by a non-European organisation. In this sense, the specification cannot be considered a European standard, but it lies at the core of many European services and developments and is widely implemented by European institutions. Therefore this criterion is not applicable._x000D_ _x000D_ W3C reference:_x000D_ https://www.w3.org_x000D_ _x000D_ XML 1.1 W3C reference:_x000D_ https://www.w3.org/TR/xml11/'
'Currently the specification is included on the ICT Standards for Procurement list on the Interoperable Europe Portal._x000D_ _x000D_ European list of ICT Standards for e-procurement:_x000D_ https://interoperable-europe.ec.europa.eu/collection/ict-standards-procurement/identified-ict-specifications-procurement_x000D_ _x000D_ XML 1.1 W3C reference:_x000D_ https://www.w3.org/TR/xml11/'
'XML is meant to be used fully, a document can either fully adhere to the specification syntax or not._x000D_ _x000D_ XML 1.1 W3C reference:_x000D_ https://www.w3.org/TR/xml11/'
'17 Member States are recommending XML in their ICT National Catalogues. These Member States are Bulgaria and Croatia, among others._x000D_ _x000D_ Bulgaria reference:_x000D_ https://www.mtitc.government.bg/upload/docs/2016-01/BNIF_EN.pdf_x000D_ _x000D_ Croatia reference:_x000D_ https://ssi.gov.hr/en/catalogue_x000D_ _x000D_ CAMSS list of standards:_x000D_ https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards_x000D_ _x000D_ XML 1.1 W3C reference:_x000D_ https://www.w3.org/TR/xml11/'
'The XML specification provides a syntax for exchanging information that can be validated against a schema designed to protect the data exchange. In this sense, XML can use other specifications, such as the XML Encryption Syntax and Processing, which allows data to be encrypted and better protected against eavesdropping or unauthorised users. Thus, by using this complementary specification, data can be exchanged in a secure and trustworthy manner._x000D_ _x000D_ W3C XML Encryption Syntax and Processing:_x000D_ https://www.w3.org/TR/xmlenc-core1/_x000D_ _x000D_ XML 1.1 W3C reference:_x000D_ https://www.w3.org/TR/xml11/'
'XML does not directly define or expose technical interfaces for accessing public administration services. However, the specification provides a standardised, machine-readable structure for data, which facilitates the exposure of such interfaces. Additionally, XML data can be converted into formats like HTML using converter software, further supporting the presentation and accessibility of these interfaces such as in the eForms application._x000D_ _x000D_ eForms reference:_x000D_ https://docs.ted.europa.eu/eforms/latest/schema/introduction.html_x000D_ _x000D_ XML 1.1 W3C reference:_x000D_ https://www.w3.org/TR/xml11/'
'The XML format, particularly through XAdES (XML Advanced Electronic Signatures), is recognised by the eIDAS Regulation as a compliant format for advanced electronic signatures._x000D_ _x000D_ Overview of Standards for eIDAS document:_x000D_ https://www.enisa.europa.eu/publications/assessment-of-standards-related-to-eidas-i_x000D_ _x000D_ XML Advanced Electronic Signatures (XAdES) reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31913201/01.03.01_60/en_31913201v010301p.pdf_x000D_ _x000D_ eIDAS Regulation:_x000D_ https://digital-strategy.ec.europa.eu/en/policies/eidas-regulation_x000D_ _x000D_ XML 1.1 W3C reference:_x000D_ https://www.w3.org/TR/xml11/'
"XML is included in 17 national catalogues of recommended specifications. They belong to Bulgaria and Croatia, among others. The National Interoperability Framework (NIF) of Bulgaria and the Croatia are aligned with at least 3 out of 4 scoreboards of the EIF Monitoring according to the National Interoperability Framework Observatory (NIFO) factsheets._x000D_ _x000D_ CAMSS List of Standards:_x000D_ https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards_x000D_ _x000D_ NIFO Factsheets:_x000D_ https://interoperable-europe.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public-administration-factsheets-2024_x000D_ _x000D_ Bulgaria's catalogue:_x000D_ https://www.mtitc.government.bg/upload/docs/2016-01/BNIF_EN.pdf_x000D_ _x000D_ Croatia's catalogue:_x000D_ https://ssi.gov.hr/en/catalogue_x000D_ _x000D_ XML 1.1 W3C reference:_x000D_ https://www.w3.org/TR/xml11/"
'The XML specification itself does not provide built-in mechanisms to guarantee the authenticity of the agents involved in data transactions. In systems based on XML exchanges, this is achieved using other specifications, such as XML Signature Syntax and Processing, which is based on XML and developed by W3C. This specification provides a method for digitally endorsing an XML file, allowing authentication of the sender and verification of data integrity._x000D_ _x000D_ Another related specification is XAdES, which extends XML Signature Syntax and Processing by supporting the long-term validity of signatures in accordance with Directive 1999/93/EC of the European Parliament and of the Council of 13 December 1999 on a Community framework for electronic signatures._x000D_ _x000D_ W3C XML Signature Syntax and Processing:_x000D_ https://www.w3.org/TR/xmldsig-core/_x000D_ _x000D_ XML Advanced Electronic Signatures (XAdES) reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31913201/01.03.01_60/en_31913201v010301p.pdf_x000D_ _x000D_ XML 1.1 W3C reference:_x000D_ https://www.w3.org/TR/xml11/'
'The XML specification itself does not provide inherent protection against unauthorised changes to the information it represents. In this sense, XML depends on the implementation of related elements. Thus, specifications such as the XML Signature Syntax and Processing and the XML Encryption Syntax and Processing can be applied to achieve a more robust protection mechanism, ensuring that data is inaccessible to third parties or unauthorised users._x000D_ _x000D_ W3C XML Signature Syntax and Processing:_x000D_ https://www.w3.org/TR/xmldsig-core/_x000D_ _x000D_ W3C XML Encryption Syntax and Processing:_x000D_ https://www.w3.org/TR/xmlenc-core1/_x000D_ _x000D_ XML 1.1 W3C reference:_x000D_ https://www.w3.org/TR/xml11/'
'XML is already associated to EIRA ABBs in the EIRA Library of Interoperability Specifications (ELIS). More specifically, XML can define the interoperability aspects of the "Data Representation" and "Knowledge" ABBs of the EIRA Semantic View._x000D_ _x000D_ EIRA Library of Interoperability Specifications (ELIS):_x000D_ https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/611_x000D_ _x000D_ XML 1.1 W3C reference:_x000D_ https://www.w3.org/TR/xml11/'
'XML is used to encode all communications between web services. Therefore, it fosters the visibility and comprehensibility of public administrations data and services. XML allows the separation of information through tags and attributes, making the structure clearer and easier to understand for users working with the data._x000D_ An example of such application is the eForms service for Public procurement standards on the European Union._x000D_ _x000D_ eForms reference:_x000D_ https://docs.ted.europa.eu/eforms/latest/schema/introduction.html_x000D_ _x000D_ XML 1.1 W3C reference:_x000D_ https://www.w3.org/TR/xml11/'
'The specification does not allow customisation on the syntax. However, although the default attributes of XML can not be changed, new attributes and tags can be created and modified to meet specific needs._x000D_ _x000D_ XML 1.1 W3C reference:_x000D_ https://www.w3.org/TR/xml11/'
'The efficiency of the XML specification has been assessed by the Southern University of Science and Technology (China) and the National University of Singapore (Singapore). In the "Finding XPath Bugs in XML Document Processors via Differential Testing" study, XML is addressed as the essential data format on which the processors under test operate, with meticulous attention to its structure and the controlled generation of XML documents to create effective test cases._x000D_ _x000D_ "Finding XPath Bugs in XML Document Processors via Differential Testing" study:_x000D_ https://dl.acm.org/doi/10.1145/3597503.3639208_x000D_ _x000D_ XML 1.1 W3C reference:_x000D_ https://www.w3.org/TR/xml11/'
'XML is a markup language designed for structuring and representing data, enabling the exchange and storage of information in a standardised format. To ensure a higher degree of personal data protection managed by public administrations, the specification can be combined with the XML Encryption Syntax and Processing specification, which allows data to be encrypted while in transit, ensuring that only authorised parties can access it. In this way, personal data remains protected._x000D_ _x000D_ XML Encryption Syntax and Processing reference:_x000D_ https://www.w3.org/TR/xmlenc-core1/_x000D_ _x000D_ XML 1.1 W3C reference:_x000D_ https://www.w3.org/TR/xml11/'
'Apart from XAdES, the specification is used in the European Single Procurement Document (ESPD), which uses XML 1.0 to standardise information exchange in public procurement, significantly reducing administrative burden for businesses across member states._x000D_ _x000D_ ESPD reference:_x000D_ https://ec.europa.eu/isa2/solutions/european-single-procurement-document-espd_en/ _x000D_ _x000D_ XML Advanced Electronic Signatures (XAdES) reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31913201/01.03.01_60/en_31913201v010301p.pdf_x000D_ _x000D_ XML 1.1 W3C reference:_x000D_ https://www.w3.org/TR/xml11/'
'Although the specification defines the core syntax and parsing rules that all XML documents must follow, components such as attributes and tags can be created and extended to meet specific needs. Therefore, the specification allows for extension._x000D_ _x000D_ XML 1.1 W3C reference:_x000D_ https://www.w3.org/TR/xml11/'
'XML acts as a common, platform-independent language for data exchange. By defining standardised XML schemas (vocabularies) for specific public service domains (e.g., procurement, social security, health), different systems can exchange data in a mutually understandable format. This is crucial for cross-border services and for connecting different government agencies within a single country._x000D_ _x000D_ Examples include the European Single Procurement Document (ESPD), which uses XML to standardise information exchange in public procurement, significantly reducing administrative burden for businesses across member states. It is worth mentioning that ESPD uses XML 1.0 but given the nature of the project and its long development it is normal to use the 1.0 version._x000D_ _x000D_ ESPD reference:_x000D_ https://ec.europa.eu/isa2/solutions/european-single-procurement-document-espd_en/_x000D_ _x000D_ XML 1.1 W3C reference:_x000D_ https://www.w3.org/TR/xml11/'
'The purpose of XML is not related to e-accessibility. Therefore, this criterion is not applicable to this specification._x000D_ _x000D_ XML 1.1 W3C reference:_x000D_ https://www.w3.org/TR/xml11/'
'W3C provides a Markup Validation Service for free to validate XML and other specifications markup online._x000D_ Furthermore, the specification has a set of conformance test suites that can be downloaded separately._x000D_ _x000D_ Extensible Markup Language (XML) Conformance Test Suites:_x000D_ https://www.w3.org/XML/Test/_x000D_ _x000D_ W3C Validator Reference:_x000D_ https://validator.w3.org_x000D_ _x000D_ XML 1.1 W3C reference:_x000D_ https://www.w3.org/TR/xml11/'
CAMSS Assessment of SHACL EIF Scenario v1.0.0
'HTTP Cookies can only be implemented within an HTTP communication protocol. Therefore, this specification is not platform-agnostic. IETF HTTP Cookies: https://datatracker.ietf.org/doc/html/rfc6265'
On the client-side, TLS 1.3 is supported by the Chrome® and Firefox® browsers. Microsoft® announced implementation of version 1.3 in Q1 of 2019 for their office products. In addition, the three largest crypto libraries have indicated that they will support version 1.3, which also guarantees support at server level in the future.
ADMS was developed and it is maintained by W3C which is an international community developing open standards. ADMS in W3C: https://www.w3.org/TR/vocab-adms/ ADMS in Joinup: https://joinup.ec.europa.eu/solution/asset-description-metadata-schema-adms/about
'Restrictions of access can be provided by DNS adding the DNS Security Extensions (DNSSEC), which is, in fact, almost a mandatory extension between major stakeholders. Access is secured by the encryption under which the domain is protected provided by DNSSEC or other extensions addressing security issues. Resource Records for the DNS Security Extensions: https://datatracker.ietf.org/doc/html/rfc4034 Extension Mechanisms for DNS: https://datatracker.ietf.org/doc/html/rfc6891 DNS IETF reference: https://www.ietf.org/rfc/rfc1034.txt'
W3C provides a free source for RDF validation. See: https://www.w3.org/RDF/Validator/
'There has not been found any community sharing their data and results on national platforms. However, ETSI TS 119 612 indirectly encourages the creation of communities on national platforms through ETSI membership and directives. It also can be found assessed in the community of Connecting Europe Facility (CEF) Building Blocks. Connecting Europe Facility (CEF) Building Blocks: https://commission.europa.eu/news/connecting-europe-facility-brings-cross-border-public-services-digital-era-2020-12-23_en#:~:text=The%20CEF%20Building%20Blocks%20are%20open%20and%20reusable%2C,solutions%2C%20which%20connect%20Europe%27s%20varied%20national%20IT%20landscapes.'
SAMM’s purpose is focused to help and improve security capabilities within organisations and software development. Therefore, it can be said that by applying SAMM public administrations can work towards ensuring secure and trustworthy data exchange with all stakeholders. SAMM webpage: https://owaspsamm.org/ SAMM documentation: https://github.com/OWASP/samm/blob/master/Supporting%20Resources/v2.0/OWASP-SAMM-v2.0.pdf
SAML 2.0 has been assessed by CAMSS Team in the context of MSP scenario, which is fully compliant with the Standardisation Regulation 1025/2012. See: https://joinup.ec.europa.eu/solution/camss-assessment-saml-20-msp-scenario
'The purpose of ISO ISO/IEC 7498:1 is not related to e-accessibility. Therefore, this criterion is considered not applicable to this specification. ISO/IEC 7498:1: https://www.iso.org/standard/20269.html'
OASIS has defined a clear process where all the stakeholders involved have the opportunity to participate in the development of the specification development process. See: https://www.oasis-open.org/policies-guidelines/tc-process-2017-05-26
"OAS is designed to ease the process of creating an API. As each API set of requirements may vary, it is necessary for the specification to allow for partial implementations, although, as it is stated in the specification's introduction, there is still a need for a minimal degree of implementation. OAS specification: https://spec.openapis.org/oas/latest.html#openapi-specification OAS in Github: https://github.com/OAI/OpenAPI-Specification/#participation"
"As the specification follows the law of ECLI, which is a uniform identifier that has the same recognizable format for all Member States and EU courts, it can be significant of the specification's efficiency, if used together with other specifications. There is nothing that indicates anything about the specification inside the nifo factsheets or the lists of standards. NIFO Factsheets: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public-administration-factsheets-2022 List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards ECLI Webpage: https://e-justice.europa.eu/175/EN/european_case_law_identifier_ecli?init=true"
EuroVoc offers several services that aim to help e-Government professionals share their experience. Since it is based on European Union and National Knowledge it can be useful when creating eGovernment innovative solutions. Eurovoc: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/eurovoc
'The XFDL specification is based on an XML structure. This format supports clearer, more transparent administrative procedures by improving how data is structured, processed, and shared, making the overall process more accessible and understandable. Extensible Forms Description Language reference: https://www.w3.org/TR/NOTE-XFDL'
'The purpose of Indexed Database API is not related to secure exchange of data since the specification not provide any reference to security considerations. Indexed Database API: https://www.w3.org/TR/IndexedDB/'
'ISO/IEC 27001 in itself is a method to audit the information systems. However, the specification does not publicly provide conformance testing requirements, and both testing techniques and auditing services require payment to third parties. There are, nevertheless, companies such as Vanta, which provide a resource to enable automated measurement of the compliance with ISO 27001 standard. ISO/IEC 27001 reference website: https://www.iso.org/standard/54534.html Vanta website: https://www.vanta.com/products/iso-27001?utm_source=bing&utm_medium=paid&utm_campaign=iso27001_rsu_Spain&utm_term=iso%2027001&utm_campaign=ISO+27001+(RSU)+Spain&utm_source=bing&utm_medium=ppc&utm_adgroup=ISO%2027001%20Head%20Term&hsa_acc=4880914058&hsa_cam=15789616753&hsa_grp=1332609418067234&hsa_ad=&hsa_src=o&hsa_tgt=kwd-83288948889188:loc-170&hsa_kw=iso%2027001&hsa_mt=p&hsa_net=adwords&hsa_ver=3&msclkid=fc00bbfdb553107674c4d9b99642b779'
'FTP is an internet protocol for the exchange of data over an Internet network. It supports the first level of maturity defined in the Tim Berners-Lee´s 5 stars Open Data deployment scheme, "Make your data accessible on the web". FTP Specification Reference: https://datatracker.ietf.org/doc/html/rfc959 Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/en/ '
'Assessments of the efficiency of ETSI TS 119 432 primarily involves evaluating the performance, scalability, and practicality of implementations. A 2022-paper about digital signatures offers an overview on the regulation and standards perspective and present a comparison of several implementations of long-term preservation solutions that are available on the market. ETSI TS 119 432 is mentioned as one of the main components that sustain recent digitisation efforts made by public and private institutions, expressing its efficiency. Long-term Preservation of Digital Signatures: a Need-to-have or a Nice-to-have? https://jmiltechnol.mta.ro/9/6_ARSENI,%20BUREAC%C4%82,%20TOGAN-min.pdf'
"LDES is not included in any Member States' catalogues of recommended specifications. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards"
'UBL is designed to plug directly into existing business, accounting, legal, auditing, and records management practices, eliminating the re-keying of data required by traditional fax, scanned-image and paper-based supply chains and in doing so provides an entry point into electronic business for small and medium-sized businesses. This means that UBL is an enhancer of internal and external visibility of administrative procedures and data as well as it eases the deliery of european public services, as is the case of the ESPD project. Developer community OASIS. UBL functionalities: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ubl#functionality UBL v2.3 reference: http://docs.oasis-open.org/ubl/os-UBL-2.3/UBL-2.3.html ESPD reference, Legal framework and context section: https://docs.ted.europa.eu/ESPD-EDM/3.0.1/xml_business_handbook.html#_i_1_1_legal_framework_and_context'
'SMP is not included in any national catalogue of recommended specifications whose Member State NIF is fully aligned with at least 2 out of 3 sections of the EIF according to NIFO factsheets. NIFO factsheets: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public-administration-factsheets-2022 CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards '
'The ESPD is designed to be a modular document, which means that it can be used to collect information at different stages of the procurement process. Once information is provided in the ESPD, it can be reused throughout the procurement process, eliminating the need for suppliers to provide the same information repeatedly, therefore, allowing relevant information to be reused when needed, by means of integrating the CCCEV model. More information can be found in the ESPD Technical handbook. ESPD business handbook: https://docs.ted.europa.eu/ESPD-EDM/latest/xml_business_handbook.html ESPD Technical handbook: https://docs.ted.europa.eu/ESPD-EDM/latest/xml_technical_handbook.html CCCEV: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/e-government-core-vocabularies/core-criterion-and-core-evidence-vocabulary'
'HTTPS can be customized to some extent based on specific requirements and preferences. While the fundamental principles of HTTPS remain the same, customization options are available in areas such as certificate selection, cipher suites, and server configurations. HTTPS specification: https://tools.ietf.org/html/rfc2818'
'As an encoding specification, UTF is being highly used by public administrations in order to encode data and services. An example of its use is ESCO, the vocabulary generated regarding the standardisation of the skills, competences, qualifications, and occupations at European level. ESCO REST Api Docs: https://ec.europa.eu/esco/api/doc/esco_api_doc.html'
TIFF/IT is an ISO standard and as all ISO standards, they have to be paid to access its content. However, it can be partially checked out in SIS (Swedish institute for standards) website where the content is aligned with the ISO standard. TIFF/IT SIS reference: https://www.sis.se/api/document/preview/904751/ TIFF/IT ISO reference: https://www.iso.org/standard/34342.html
At the time of elaborating this assessment, this specification is not included in any EIRA ABB in the current EIRA Library Of Interoperability Specifications (ELIS). However, HTML5 which is an improved and newer version of the specification is included. More specifically, HTML5 can define the interoperability aspects of the "Human Interface" and "Representation" ABBs from the EIRA Semantic and Technical views. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/solution/elis/release/v100
'There is no Member State that includes AKN4EU in their national catalogue with the National Interoperability Framework (NIF) aligned with at least 2 out of 3 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
'The purpose of DCAT-AP is not related to data confidentiality. Therefore, this criterion is not applicablel to the specification. DCAT-AP Specification: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/dcat-application-profile-data-portals-europe/release/200'
After checking the different standard catalogues at supra-national level, there is no evidence of the inclusion of RegOrg within any European catalogue of standards. ICT technical specifications: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en CEN search tool catalogue: https://standards.cen.eu/dyn/www/f?p=CENWEB:105::RESET:::: CENELEC search tool catalogue: https://www.cenelec.eu/dyn/www/f?p=104:107:0::::FSP_LANG_ID:25
The purpose of the specification is not related to fostering e-accessibility, therefore, this criterion is not applicable. W3C specification reference: https://www.w3.org/TR/odrl-vocab/#vocab-core
'SCIM is recommended by Malta and the Netherlands according to the CAMSS List of Standards. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards'
'The current specification, EN 319 532, supersedes TS 103 640, which has been in force during years as stated in the ETSI TR 110 000 documentation. It has been used and implemented according to user needs and the specification being assessed takes all the inputs gathered during the usage and implementation of the superseded one to improve it and upgrade according to new user needs. TS 103 640 last update is published by ETSI dated at March 2022, version 1.2.1 Technical Report TR 119 000 EN 319 532 (page 32): https://www.etsi.org/deliver/etsi_tr/119000_119099/119000/01.02.01_60/tr_119000v010201p.pdf First release date reference (2018): https://portal.etsi.org/webapp/workprogram/Report_WorkItem.asp?WKI_ID=56725 Last release date reference (2019) in right upper side of any documentation page: https://portal.etsi.org/webapp/workprogram/Report_WorkItem.asp?WKI_ID=56725'
The purpose of this specification is not related to the delivery of multilingual public services. Therefore, this criterion is not applicable to the specification. SAMM webpage: https://owaspsamm.org SAMM documentation: https://github.com/OWASP/samm/blob/master/Supporting%20Resources/v2.0/OWASP-SAMM-v2.0.pdf
'YAML is commonly used for configuration files. The specification can be used to create simple configuration files, thus, ignoring more complex features. In addition, it can be adopted and implemented gradually, depending on the organitzation needs. YAML specification: https://yaml.org/spec/1.2.2/'
'DCAT is an RDF vocabulary for representing data catalogues that allows data owners to provide metadata about the datasets they publish. By describing catalogues, datasets and resources, a publisher makes them easily searchable and discoverable. Following the previous statement it can be said that DCAT can simplify the delivery of European public services. DCAT (v2.0.0) reference: https://www.w3.org/TR/vocab-dcat-2/ '
'There are existing documentation and studies assessing the effectiveness of IPv4. The "A systematic review of transition from IPv4 to IPv6" study, examines and exposes how IPv4 has demonstrated reliability, compatibility with a wide range of protocols, applications and ease of implementation. In addition, it is made a comparision between IPv4 and IPv6, and how IPv6 can improve its predecessor. "A systematic review of transition from IPv4 to IPv6" study: https://www.researchgate.net/publication/343820813_A_Systematic_Review_of_Transition_from_IPV4_To_IPV6'
'Although DCAT-AP itself does not provide means for the enabling of data integrity, the SEMIC Support Centre has developed the DCAT-AP validator, a software tool to check metadata description of datsets for integrity and consistency. DCAT-AP validator: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/dcat-ap-validator'
'HTTP is designed to be technology agnostic, being able to adapt to new technologies and advancements in network infrastructure, ensuring its relevance and longevity. Examples are the creation of new extensions or versions like HTTP/2 and HTTP/3. HTTP /1.1 RFC 2616 Reference: https://www.rfc-editor.org/rfc/rfc2616.html HTTP versions usage: https://blog.cloudflare.com/http3-usage-one-year-on/'
'EN 16234-1 e-CF can be well adapted to new digital service channels and is intended to help new digital service channels to be deployed as describred in the Shaping Europe's digital future approach (see CEN/TC 428 "ICT Professionalism and Digital Competences" Business Plan 2022 reference, section 1.4). CEN reference, CEN/TC 428 - ICT Professionalism and Digital Competences (Published standards), EN 16234-1 e-CF: https://standards.cencenelec.eu/dyn/www/f?p=205:110:0::::FSP_PROJECT:67073&cs=15E62ED24D608A5F10D6BEE8E6D50FA10 CEN/TC 428 "ICT Professionalism and Digital Competences" Business Plan 2022 reference, section 1.4: https://standards.cencenelec.eu/BPCEN/1218399.pdf'
'At the time of elaborating this assessment, DCAT is extensively used to create innovative linked open data solutions. Especially by public administration looking forward to foster cross-border interoperability and transparency. The specification is widely used by public administrations profiling or extending it to fit domain-specific or national requirements - DCAT-AP: Application Profile for Public Sector Datasets. - DCAT-AP-BE: Extension of DCAT-AP for Belgium specific requirements. - StatDCAT-AP: Extension of DCAT-AP for the publication of statistical data. DCAT (v2.0.0) reference: https://www.w3.org/TR/vocab-dcat-2/ DCAT-AP & European Data Portals reference: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/dcat-application-profile-data-portals-europe DCAT-AP-BE reference: http://dcat.be/ StatDCAT-AP Reference: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/statdcat-application-profile-data-portals-europe/release/100'
The purpose of Standard for Public Code is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification. The Standard for Public Code webpage: https://standard.publiccode.net/
ISO has defined a clear procedure to develop its standards. It consist in a 6-steps process where only the full members can participate and influence the development of ISO standards. Individual or organisations cannot be part of the ISO Member bodies, however, ISO has a wide network around the globe in order to capture information from the maximum stakeholders possible. Technical committees are in charge of the development of the standards. ISO has defined the roadmap of standards, it is composed of 6 steps as before said. For the approval of an standard the two thirds majority of P-members of TS is needed. If the result is negative, the document is returned to TC/SC for further studied. See: http://www.isotc292online.org/projects/iso-process/
"The first formal standard version of IP was version 4 (IPv4), created in 1980 and defined in RFC 760. Since then, many assessments and improvements have been made in terms of security and privacy, for example. In addition, despite countries transitioning to IPv6 addresses, IPv4 is still more widely used than IPv6. For example, the USA and Canada alone account for almost half of the world's IPv4 allocation. IPv4 RFC 760: https://datatracker.ietf.org/doc/html/rfc760 IPv4 IETF: https://www.rfc-editor.org/rfc/rfc791 IPv4 history: https://ipv4marketgroup.com/a-brief-history-of-ipv4/ IPv4 adoption: https://www.researchgate.net/figure/Allocation-of-IPv4-and-IPv6-Addresses-IPv6stylecom-2004-Palet-2003_fig1_228757766"
'WAI-ARIA is enhanced by a conformance testing platform that facilitates the assessment of implementations. Additionally, the W3C Accessibility Initiative puts forth tools and methods designed to evaluate these implementations, ensuring that web technologies align with the accessibility standards. WAI-ARIA W3C validation tool list: https://www.w3.org/WAI/ER/tools/ WAI-ARIA Test & Evaluate: https://validator.w3.org/#validate_by_uri WAI-ARIA reference: https://www.w3.org/TR/wai-aria/'
'The specification itself does not provide mechanisms for protecting information against unauthorized changes. While WSDL may include references to security policies and mechanisms (such as WS-Security), the actual implementation and enforcement of security measures are typically handled outside the scope of WSDL at the application and infrastructure levels. OASIS Web Services Security: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wss W3C WSDL specification: https://www.w3.org/TR/wsdl20/'
"The purpose of the EN 303 645 specification is not related to enabling the exposure of interfaces of public administration's services. EN 303 645 reference: https://www.etsi.org/deliver/etsi_en/303600_303699/303645/02.01.01_60/en_303645v020101p.pdf"
'The specification is not specifically designed to be multilingual but since the presentation layer deals with standardising data types and their representations, a single international character code standard such as Unicode is necessary for software internationalisation and multilingual communication of OSI based platforms. This has resulted in multiple attempts to translate the lower layers of communication values onto more universal codification for the upper layers. OSI and multilingualism https://www.sciencedirect.com/science/article/abs/pii/S0920548997000044 OSI reference https://www.iso.org/standard/20269.html'
'Considering the original intent of the specification, it can be affirmed that its role enchances the clarity of data within Public Administrations and pertinent information generated for the decision-making process. ELI offers a unified schema for defining metadata related to legislation, simplifying the comprehension and shareability of legislative documents and facilitating their accessibility. ELI reference: https://eur-lex.europa.eu/eli-register/about.html'
'The specification allows for customization to a certain extent. While the core functionality and commands of FTP are standardized, the specification allows for additional customization through the use of optional features and extensions. FTP implementations can include customizations based on specific requirements, use cases, or system configurations. These customizations can include features such as specific authentication mechanisms, custom command extensions, or additional functionality beyond the basic FTP operations. FTP Specification Reference: https://tools.ietf.org/html/rfc959'
'ADMS’s purpose is the description of Assets within a Catalogue (repository), making them easy to discover and reuse. However, it is not related to foster the one-only principle between administrations and stakeholders. ADMS Specification W3C: https://www.w3.org/TR/vocab-adms/'
UTF-8 is not defining a cross-sector reusable data model. The purpose of the specification is to define a schema for encoding data.
'The specification has been used by several organisations at European and national level across Europe. There are implementations related to taxes in Flanders and Finland, and also implementations related to Smart Cities through Data Spaces. In relation with Data Spaces, EIRA includes an approach that is aligned with major initiatives such as the Data Space Support Centre (DSSC), the International Data Space Association (IDSA). This is a trend at European Level that leads to innovation, where EIRA and its specialisations can support public administrations to innovate. EIRA reference: https://interoperable-europe.ec.europa.eu/collection/european-interoperability-reference-architecture-eira /solution/eira/release/610 EIRA Github Repository: https://github.com/CarTool-EC/EIRA IDSA: https://internationaldataspaces.org/ DSSC: https://dssc.eu/'
'DAPS has a repository which is open source and can be accessed at GitHub. It contains all major releases available and documentation on its supporting processes so, it can be considered that DAPS is mature enough for ts use in the development of digital solutions/services. Further documentation about the IDS Identity Provider/DAPS can be seen at GitHub too. DAPS: https://github.com/International-Data-Spaces-Association/IDS-G/tree/main/Components/IdentityProvider/DAPS'
The purpose of HTML is not related to long term preservation of electronic records. Therefore, this criterion is considered not applicable to this specification. HTML W3C reference: https://www.w3.org/TR/html401/
The adoption of PDF as a document format for exchanging information does not hamper the scalability of systems. It is an widely adopted and used for this purpose and, moreover, it is independent from any platform or software. Therefore, PDF is proportionated to the users' needs and at the same time, it does not hamper the interoperability and scalability of systems.
The purpose of TLS 1.2 is not related to the publication of public data as open data to European public services. Therefore this criterion is considered not applicable specification.
The specification is available for its use and implementation at the IETF's webpage. TSP IETF reference: https://tools.ietf.org/html/rfc3161
"The purpose of OSI is not directly related to data processing and therefore the specification does not provide with specifications for data security. However, one key characteristics of the open systems is the data exchange and the specification provides with the basic elements for it. OSI reference https://www.iso.org/standard/20269.html OSI's Security architecture https://www.iso.org/obp/ui/es/#iso:std:iso:7498:-2:ed-1:v1:en"
'There is no Member State that includes NFVI in their national catalogue with The National Interoperability Framework (NIF) in alignment with the three categories: 1- Conceptual model for integrated public services provision 2- Interoperability layers 3- Interoperability principles CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
'The DCAT vocabulary supports the attribution of data and metadata to various participants such as resource creators, publishers and other parties. In addition, it also supports the association of rights and licenses with catalogued Resources and Distributions. Such metadata improves the reliability of data processing between citizens, businesses and public administrations. DCAT (v2.0.0) reference: https://www.w3.org/TR/vocab-dcat-2/ '
'Any interested party may propose and request modifications to SFIA definitions and skills/competence coverage after a registration process (SFIA reference, Future SFIA section, Change requests subsection). In addition, the SFIA Foundation facilitates a collaborative platform to promote visibility of the specification across different sectors (see SFIA reference, SFIA Views). SFIA reference, Future SFIA section, Change requests subsection: https://sfia-online.org/en/sfia-9/change-requests SFIA reference, SFIA Views: https://sfia-online.org/en/sfia-8/sfia-views'
'The Asset Administration Shell (AAS) has at its core the idea of platform Industrie 4.0 that is the delivery of assets among partners and this simplifies the deliver of digital services. At the same time this is done in the context of the Industrial Digital Twin Initiative (IDTA). The AAS provides the partners with the adequate formats and resources to share a digitalised industrial asset (whether it is a tool or a product) among themselves, thus making possible the design and implementation of new assets in a collaborative manner. Industrie 4.0 initiative: https://www.plattform-i40.de/IP/Navigation/EN/Home/home.html IDTA reference: https://industrialdigitaltwin.org/en/ Details of the Asset Administration Shell (AAS) https://industrialdigitaltwin.org/en/wp-content/uploads/sites/2/2024/06/IDTA-01001-3-0-1_SpecificationAssetAdministrationShell_Part1_Metamodel.pdf'
RDF defines a data model that can be reused in a cross-sector way. There is an extension of RDF vocabulary which extends the definition. This specific section (RDF Schema) belongs to the RDF stack focusing especially on main elements for the data modelling. As RDF is an agnostic specification is defining a reusable cross-sector data model. See: https://www.w3.org/TR/rdf-schema/ https://www.w3.org/TR/rdf11-primer/#section-data-model
By using SAML 2.0, the system administrator is prevented from providing several authentication tokens and, the user does not have to deal with several credentials. This fact helps to adapt the specification to user’s needs without hampering the scalability of systems. In addition, SAML 2.0 allows the exchange of authentication and authorization data between parties. It is mainly used to ensure single sign-on (SSO). It extends SSO across security domains independently from any platform which prevents non-interoperable proprietary technologies.
The purpose of WSDL is not related to the delivery of multilingual services. Therefore this criterion is not applicable to this specification.
CAdES (ISO 14533-1:2014) is an ISO standard and as all ISO standards, they have to be paid to access its content. However, it can be checked out in ETSI website where the content is aligned with the ISO standard. CAdES ISO reference: https://www.iso.org/standard/64756.html CAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/101700_101799/101733/02.01.01_60/ts_101733v020101p.pdf
"The maturity of the specification can be seen on the use cases provided on the Digital twins initiative, the specification is present in already implemented initiatives such as Collaborative Engineering. This IDTA's AAS use case proposes a collaborative environment to design and implement modifications on a specific manufacturing tool. The specification is released on the Github and IDTA. Furthermore, the documentation is readily available on the aforementioned pages. Asset Administration Shell (AAS) Github documentation https://admin-shell-io.github.io/aas-specs-antora/index/home/index.html IDTA use case https://industrialdigitaltwin.org/en/wp-content/uploads/sites/2/2024/10/2024-10_IDTA_UseCases_Collaborative_Engineering_Factsheet_en.pdf Details of the Asset Administration Shell (AAS) https://industrialdigitaltwin.org/en/wp-content/uploads/sites/2/2024/06/IDTA-01001-3-0-1_SpecificationAssetAdministrationShell_Part1_Metamodel.pdf"
'After searching the different national catalogues, there has not been found any European Member State recommending ETSI TS 119 511. ETSI TS 119 511 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119511/01.01.01_60/ts_119511v010101p.pdf'
'Data protection encompasses data confidentiality, integrity and access control. TOSCA does not impose the use of any specific mechanism or technology for security considerations; security aspects should be obtainable by the user infrastructure. TOSCA reference, TOSCA normative type definitions section: https://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.3/os/TOSCA-Simple-Profile-YAML-v1.3-os.html#_Toc26969462'
'The purpose of WAI-ARIA is not related to the delivery of multilingual public services. Therefore, this criterion is not applicable to this specification. WAI-ARIA reference: https://www.w3.org/TR/wai-aria/'
"Schema.org enables the exposure of interfaces to access European public administration's services when combined with other specifications. The specification is currently used in combination with DCAT, in order to propose a common data schema (DCAT-AP-SDO, Schema.org profile of DCAT Application Profile for Data Portals in Europe) enabling administrations and citizens to find and reuse datasets located in EU data portals. Despite the fact that there is no evidence of any public administration's service making use of this common data schema (DCAT-AP-SDO, Schema.org profile of DCAT Application Profile for Data Portals in Europe), the specification may favour the promotion of semantic interoperability between different information systems and promote the adoption of a common mechanism to enhance the exposure of such services. Schema.org homepage reference, 'Documentation' section: https://schema.org/docs/documents.html DCAT reference: https://www.w3.org/TR/vocab-dcat-3/ DCAT-AP-SDO reference: https://ec-jrc.github.io/dcat-ap-to-schema-org/"
'ETSI TS 119 512 is part of the Electronic Signatures Infrastructure (ESI) family of specifications. the ESI dates back to 2012, when the General Policy Requirements for Trust Service Providers supporting Electronic Signatures (ETSI EN 319 401) specification was first issued. Since its first publication, there have been many extensions one of which is ETSI TS 119 512, whose version 2.3 was released in 2020 when the eIDAS regulation identified the need to create protocols to develop preservation services for trust service providers, as mentioned in ETSI SR 019 510, giving birth to both TS 119 511 and TS 199 512 specifications. ESI specification history: https://standards.globalspec.com/std/14387016/EN%20319%20401 ETSI TS 119 512 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.02_60/ts_119512v010102p.pdf ETSI EN 319 401 specification: https://www.etsi.org/deliver/etsi_en/319400_319499/319401/02.03.01_60/en_319401v020301p.pdf eIDAS blog, New APIs for the eIDAS-Ecosystem: https://blog.eid.as/tag/etsi-ts-119-512-en/'
'The specification and its community ensures to give conferences based on metadata aswell as mantaining and developing metadata terms namespaces, contributting to scope comprehensibly administrative procedures, rules data and services may be a side effect of all mentioned actions. A good example is that ECLI implements DCMI which can be meaningful in scoping comprehensibly administrative procedures, rules data and services. DCMI About: https://www.dublincore.org/about/ '
'It can be said that the underlying principles and technologies are designed to be domain-agnostic. In other words, the concepts and standards provided by Linked Data and event streams can be applied to a wide range of domains. The key idea is to represent events and their relationships in a standardized, machine-readable format using Linked Data principles. LDES specification: https://joinup.ec.europa.eu/collection/semic-support-centre/linked-data-event-streams-ldes'
'The IPv6 specification is versatile and applicable across various business domains, facilitating growth, innovation, and collaboration. IPv6 IETF: https://www.rfc-editor.org/rfc/rfc2460'
'The purpose of OSI is not related to the protection of personal data managed by Public Administrations since the specification does not provide any security considerations. OSI reference https://www.iso.org/standard/20269.html'
'LDAP is included in 10 national catalogues of recommended specifications. They belong to Austria, Croatia, Cyprus, France, Germany, Greece, Malta, Netherlands, Spain, and Sweden. The National Interoperability Framework (NIF) of Spain and Austria are fully aligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. Nonetheless, countries like Sweden or Malta do not get a high perfomance, being alligned with 3 out of 5 and 2 out of 5 respectively. National catalogue of Austria: The e-Government Bund-Länder-Städte-Gemeinden platform: http://reference.e\x02government.gv.at/ National catalogue Malta: https://www.forumstandaardisatie.nl/open-standaarden National catalogue Spain: https://administracionelectronica.gob.es/pae_Home/pae_Estrategias/pae_Interoperabilidad_Inicio /pae_Normas_tecnicas_de_interoperabilidad.html#CATALOGOESTANDARES National catalogue Sweden: https://www.avropa.se/globalassets/dokument/open-it-standards.pdf?_t_id=1B2M2Y8AsgTpgAmY7PhCfg% 3d%3d&_t_q=standards&_t_tags=language%3asv%2csiteid%3a95d515a5-23ca-47bf-87a9- 07b10d8ac360&_t_ip=178.139.72.144&_t_hit.id=Avropa_Core_Models_Media_GenericMedia/_ff07d720- f793-44b0-994d-27e79b28f6bd&_t_hit.pos=7 NIFO factsheets: https://joinup.ec.europa.eu/collection/national-interoperability-framework-observatory-nifo/nifo-factsheets '
'ISO/IEC 7498:1, which defines the OSI (Open Systems Interconnection) model, does not comprehensively address administrative procedures, rules data, and services in a detailed manner. Even so, given that the OSI model provides a common basis for the coordination of standards development for the purpose of systems interconnection, it can be understood that comprehensibility is taken into consideration. ISO/IEC 7498:1: https://www.iso.org/standard/20269.html'
'Verifiable Credentials is being directly used to create innovative solutions in different areas. In the emerging Web3 landscape, the need for secure and trustworthy identity solutions has become more important than ever. Thanks to Verifiable Credentials, issuing organizations can generate fraud-proof digital credentials and verifying organizations can instantly check the authenticity of those credentials. One use case would be European Blockchain Services Infrastructure (EBSI), an European initiave that has developed several frameworks to address business problems using the 3WC Verifiable Credentials data model. Verifiable Credentials: https://www.w3.org/TR/vc-data-model/'
After searching in the different official European websites, there is no evidence of any cross-border project that uses W3C Best Practices nor explicit agreements involving the usage of the specification.
HTML5 Geolocation can make an impact to the emergency service and its citizens. It explains the capabilities of the existing web technology for accurate handset derived location using HTML5 Geolocation. See: https://eena.org/document/html5-geolocation/
'The specification does not guarantee the authenticity and authentication of the roles agents involved in the data transactions.Therefore, this criterion is not applicable to the specification. AKN4EU reference: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/akn4eu'
'The Semantic Interoperability Community (SEMIC) has established Working Groups. These Working Groups are open to the participation of everyone interested in semantic solutions working for public administrations in the Member States or in EU institutions. Moreover, the Core Location Vocabulary has been presented in some webinars to get feedback of the community. SEMIC working groups: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/about Core Location Vocabulary webinars: https://interoperable-europe.ec.europa.eu/collection/semic-support-centre/solution/core-location-vocabulary/release/200 Core Location Vocabulary: https://interoperable-europe.ec.europa.eu/collection/semic-support-centre/solution/core-location-vocabulary/release/100'
'The underlying XBRL specification was designed to permit not only the capture and expression of business reporting facts in all of the languages supported by ISO 639, but also the internal capture and expression of regulation and guidance related to the reporting content. The specification has support already for 8 languages and the process for adding new ones is defined. http://www.xbrl.org/specification/xbrl-2.1/rec-2003-12-31/xbrl-2.1-rec-2003-12-31+corrected-errata-2013-02-20.html'
'The purpose of the GITB TDL is to provide a syntax for conformance and interoperability testing. Therefore, this criterion is not applicable to the specification. GITB TDL reference: https://www.itb.ec.europa.eu/docs/tdl/latest/introduction/index.html#introduction'
There are no Member States recommending OpenPM2 in their ICT National Catalogues. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'The IPv4 specification can ensure authentication through an IPv4/IPv6 authentication agent. This mechanism is a software application that securely passes user authentication requests to and from the RSA Authentication Manager. In addition, the IPv4 authentication agent software offers a service (authentication) that processes these requests. IPv4 authentication agent: https://community.rsa.com/s/article/IPv4-IPv6-Authentication-Agents-aa7bd0d4'
"During the project's duration, the E-ARK CSIP received attention and interest from professionals and organizations involved in the management and preservation of digital information. The project team actively sought feedback and input from stakeholders, and the specification was developed in consultation with experts in the field. This collaborative approach helped ensure that the CSIP reflected the needs and requirements of the archival community. An evidence of its market uptake may come from the fact that The DILCIS Board is supported by the European Commission through the CEF eArchiving Building Block. CEF eArchiving: https://joinup.ec.europa.eu/collection/egovernment/solution/cef-earchiving/about E-ARK CSIP specification: https://earkcsip.dilcis.eu/#introduction"
'WSDL is primarily focused on describing the interfaces and operations of web services, providing a standardized way to define the contract between service providers and consumers. The specification focuses on the technical aspects of how services can be invoked and what data structures are involved. W3C WSDL specification: https://www.w3.org/TR/wsdl20/'
PDF 1.7 has been assessed previously by CAMSS Team using the CAMSS method in the Scenario 2 in the CAMSS Tool v1.0.0. The CAMSS method is fully aligned with the European Standardisation Regulation 1025/2012. As the result of the assessment is positive, PDF can be considered compliant with the European regulation. See: https://joinup.ec.europa.eu/release/camss-assessment-pdf-17/v100
'DIDs in not included in an open repository/catalogue of standards at national level. However, DIDs is used in eIDAS project, which is a Cross-border project. DIDs W3C: https://www.w3.org/TR/did-core/'
'ISO/IEC 7498:1 is intended to be a generic and conceptual framework for network communication. Its design and abstraction make it applicable and usable across various business domains. The OSI model provides a structured approach to understanding and developing network protocols, allowing for interoperability between different systems and vendors. ISO/IEC 7498:1: https://www.iso.org/standard/20269.html'
This document provides Best Practices related to the publication and usage of data on the Web designed to help support a self-sustaining ecosystem. Following these Best Practices will facilitate interaction between publishers and consumers. Therefore, this specification does not foster the creation of innovative solutions. W3C Reference: https://www.w3.org/TR/dwbp/
'DIDs can be useful for modeling business processes in public administrations. DIDs addresses the need of enable individuals and organizations to generate their own identifiers using systems they trust. Moreover, organizations and individuals do not depend of centralized authority. DIDs W3C: https://www.w3.org/TR/did-core/#introduction'
The purpose of the Core Location Vocabulary is to create a reusable and extensible data model that captures the fundamental characteristics related to people, locations and businesses. By providing a set of information to describe data in the sectors mentioned before, it helps public administrations with the visualization of people, locations or business. CLV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-location-vocabulary
"Syslog protocol is included in the European Commission's Information System Security Policy as part of the standard on logging and monitoring. This standard provides mandatory instructions for the procedures to be used for logging and monitoring on all types of computer systems that are capable of generating information security-related log events, including servers, network equipment, workstations and mobile devices. Its aim is to ensure that a sound minimum of logging and monitoring is performed consistently across the Commission, without incurring unreasonable costs or administrative burdens. European Commission Information System Security Policy, STANDARD ON LOGGING AND MONITORING: https://extranet.eba.europa.eu/sites/default/documents/files/documents/10180/1449046/4e9f17de-4589-424c-a670-c0cdc1b5f67b/Annex%205%20Standard%20on%20Logging%20and%20Monitoring.pdf?retry=1"
'The publiccode.yml specification facilitates the delivery of digital services by providing a structured framework for documenting public sector software. This standardisation enhances interoperability and enables better integration of APIs, thereby improving the efficiency of digital public services. By streamlining access to information and services, it allows public administrations to respond effectively and promptly to user requests, aligning with the EIF’s recommendation to utilise digital channels in service delivery. Publiccode.yaml documentation: https://docs.italia.it/italia/developers-italia/publiccodeyml-en/en/master/index.html '
'The ELI´s Task Force team encourages ELI specifications to be available in multiple languages. Therefore, the specification can be used to a significant extent in a multilingual context. However, the extent to which it can be used in a specific language would depend on the availability of the specification in that language. ELI reference: https://eur-lex.europa.eu/eli-register/about.html Study on how users of legislation access transposition information: https://eur-lex.europa.eu/content/eli-register/ELI_usability_study_results-final.pdf'
'While SCIM itself does not have explicit language-related features, its extensibility and flexibility allow organizations to adapt the implementation to meet multilingual requirements. The specifics of handling multilingual data may depend on the design and configuration of the identity management system using SCIM and the choices made by the implementing organization. SCIM: https://scim.cloud/'
'TLS 1.3 is a business domain-agnostic protocol, securing communication independently of the application or industry in use. Its handshake protocol establishes encrypted tunnels, guaranteeing confidentiality and integrity for all transmitted data. For instance, HTTPS utilises the secure tunnel established by the TLS handshake to transmit web data. TLS 1.3 2018 Reference: https://www.rfc-editor.org/rfc/rfc8446.html HTTPS Reference: https://www.rfc-editor.org/rfc/rfc9110.html'
'DNS over HTTPS (DoH) primarily focuses on securing the communication between clients and DNS resolvers by encrypting DNS queries and responses. While DoH itself does not define access control mechanisms in the traditional sense, it relies on the existing security mechanisms of the HTTPS protocol, including server authentication through digital certificates. DoH specification: https://datatracker.ietf.org/doc/html/rfc8484'
Although ADMS was developed taking into account the perspective of the eGovernment System Development, it is a vocabulary that could be reused beyond this domain. It aims to ease the standardisation of assets description in assets repositories, to enhance the discoverability and reuse of assets and solutions. ADMS Specification W3C: https://www.w3.org/TR/vocab-adms/
By allowing communications over the internet, IPv6 contributes to the exchange of information between public administrations therefore, it reduces administrative burden https://tools.ietf.org/html/rfc2460
'The ISG NFV community is a large community that continues to work intensively on developing the specification and incorporating the latest technologies. This community is open to ETSI members and non-members alike, with different conditions depending on ETSI membership status. The ISG NFV provides continuous support for the correct referencing of NFV specifications (NFVI included) by service providers and open source communities. NFV reference, Our Role & Activities: https://www.etsi.org/technologies/nfv'
"LDAP has some core functionalities that can't be implemented separately. Nonetheless, the specification has beed developed to support some requirements that are not mandatory but recommended. For example, some security layers such as the SASL can be implemented, but is not required to run the specification. LDAP SASL reference: https://datatracker.ietf.org/doc/html/rfc2444"
The rules on European standardisation allow the European Commission to identify information and communication technology (ICT) technical specifications - that are not national, European or international standards - to be eligible for referencing in public procurement. This allows public authorities to make use of the full range of specifications when buying IT hardware, software and services, allowing for more competition in the field and reducing the risk of lock-in to proprietary systems. After being evaluated compliant with the regulation on standardisation 1025/2012, RDF 1.1 has been identified by Commission Implementing Decision. See: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en
'XSLT specification is designed to transform data from XML into other formats for building such interfaces. XSLT Reference: https://www.w3.org/TR/xslt-30'
"SFIA was first published in 2000 and was a framework for the ICT community. Between 2001 and 2005, SFIA has gone through a second and third release, in which the specification evolved into a framework that defines the skills and competencies required by business and technology professionals (Slideshare-SFIA reference, SFIA version 4). Since the release of SFIA 4 in 2008, successive versions have been incrementally modified to meet the changing needs of the world-wide ICT sector; a major consultation was held in 2011 through SFIA's online consultation forum (see SFIA reference, Transition to SFIA 5 document). All supporting specification processes for versions five (2011), six (2015), seven (2018) and eight (2021) are publicly available on the 'Moving to SFIA' subsections (see SFIA reference, SFIA 8 section, 'Moving to SFIA 8' subsection, and SFIA reference, Older versions-SFIA 7 section, 'Moving to SFIA 7'-'Summary of changes in SFIA 7' subsection). The specification is therefore sufficiently mature for its use in the development of digital solutions and/or services. Slideshare-SFIA reference, SFIA version 4: https://www.slideshare.net/sfiauser/sfia-version-4 SFIA reference, SFIA 8 section, 'Moving to SFIA 8' subsection: https://sfia-online.org/en/sfia-8/moving-to-sfia-8/summary-of-changes-in-sfia-8 SFIA reference, Older versions-SFIA 7 section, 'Moving to SFIA 7'-'Summary of changes in SFIA 7' subsection: https://sfia-online.org/en/legacy-sfia/sfia-7/moving-to-sfia-7/summary-of-changes-in-sfia-7 SFIA reference, Transition to SFIA 5 document: https://sfia-online.org/en/legacy-sfia/sfia-5/transition_sfia_5-en.pdf/@@download/file/transition_SFIA_5.en.pdf"
'There is no Member State that includes the ETSI TS 119 612 in their national catalogue with Their National Interoperability Framework (NIF) in alignment with the three categories 1. Conceptual model for integrated public servicesprovision, 2. interoperability layers, and 3. interoperability principles. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
'The three-letter codes of ISO 639-2 and ISO 639-3 are complementary and compatible. Even if the two codes are designed for different purposes, ISO 639-2 can be considered as an extension of ISO 639-3. ISO 639-3 reference: https://iso639-3.sil.org/about/relationships'
'IPv4 is included in 6 national catalogues of recommended specifications. They belong to Croatia, France, Germany, Netherlands, Norway, and Sweden. The National Interoperability Framework (NIF) of Sweden and Netherlands are aligned with at least 3 out of 4 scoreboards of the EIF Monitoring according to the National Interoperability Framework Observatory (NIFO) factsheets. Nonetheless, countries like Germany do not get a high performance. CAMSS list of standards: https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards National catalogue of Netherlands: https://www.forumstandaardisatie.nl/open-standaarden/lijst National catalogue of Germany: https://www.cio.bund.de/Web/DE/Architekturen-und-Standards/SAGA/SAGA%205-aktuelle%20Version /saga_5_aktuelle_version_node.html National catalogue of sweden: https://www.avropa.se/globalassets/dokument/open-it-standards.pdf?_t_id=1B2M2Y8AsgTpgAmY7PhCfg% 3d%3d&_t_q=standards&_t_tags=language%3asv%2csiteid%3a95d515a5-23ca-47bf-87a9- NIFO factsheets: https://interoperable-europe.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public-administration-factsheets-2024'
'OAIS is already mapped in the Eira Library of Interoperability Specifications, within the Ontologies catalogue and Ontology ABB from the Semantic view. EIRA Library of Interoperability Specifications: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/news/new-release-elis-501'
'As described on the Oracle documentation about security settings, the ebXML specification provides authentication and authorisation mechanisms, helping to prevent unauthorised users from making changes to original data or accessing restricted information. ebXML security: https://www.oracle.com/technical-resources/articles/enterprise-architecture/ebxml-security1.html ebXML RegRep OASIS reference: https://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html'
'IndexedDB can contribute to the client application state storage and can significantly impact the way interfaces are exposed or behave, especially in terms of offline functionality, data persistence, and performance optimisation. Indexed Database API: https://www.w3.org/TR/IndexedDB/'
'The Core Vocabularies are context-neutral semantic building blocks that can be extended into context-specific data models. Handbook for using Core Vocabularies: https://joinup.ec.europa.eu/sites/default/files/inline-files/ISA%20Handbook%20for%20using%20Core%20Vocabularies.pdf'
The specification has been implemented in four different repository platforms as part of the early adoption process. Although these tools are a successful proof of concept for the specification, they are not sufficient to consider that the specification has a significant market share of adoption due to the fact that three out of the four implementations have been performed by the Working Group developing the specifications See: Fedora Commons, ICAT https://github.com/RDAResearchDataRepositoryInteropWG/icat-bagit-tool/tree/master/demo DARIAH Repository https://github.com/RDAResearchDataRepositoryInteropWG/icat-bagit-tool KIT Data Manager https://github.com/RDAResearchDataRepositoryInteropWG/kitdm-bagit-tool
'After searching the different national catalogues, there has not been found any European Member State recommending ETSI TS 119 612. ETSI TS 119 612: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf'
No tools assessing the conformity of implementations with the specification have been found However, there are tools developed by the FTP community assessing FTP servers performance. See: https://ftptest.net/
'By creating a standardised taxonomy for data privacy concepts and terms, the DPV is enabling the exposure of interfaces as it is intended to enhance semantic interoperability about personal data processing and enable data portability for data subjects. DPV specification: https://w3c.github.io/dpv/primer/ '
HTTP does not defines a cross-sector reusable data model. HTTPS is a transfer protocol used for secure communication over a computer network.
'The effectiveness of Verifiable Credentials is often evaluated through various means, including practical implementations, pilot projects, and community feedback. For example, the effectiveness of Verifiable Credentials is often evaluated based on its adoption in various use cases and the W3C Working Group has published a collection of those: Verifiable Credentials Use Cases: https://www.w3.org/TR/vc-use-cases/'
HTTP is the main protocol underlying the world wide web. The protocol supports the exchange of high amounts of data.
At the moment of performing this assessment, Linked Open Data portals are innovative solutions adopted by public administrations all around Europe. DCAT-AP fosters the implementation of Five-Star Linked Open Data by allowing users to discover interlinked information from other portals. See: https://www.ontotext.com/knowledgehub/fundamentals/five-star-linked-open-data/ https://www.europeandataportal.eu/en http://data.europa.eu/euodp/en/home http://data.jrc.ec.europa.eu/
'The GraphQL specification is not recommended by any European Member State. CAMSS Lists Of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
"OpenTelemetry empowers organisations to capture and reuse relevant information effectively through its standardised data collection, flexible instrumentation, interoperability features, custom processing capabilities, dynamic configuration options, and supportive community ecosystem. OTel's data model contributes to the collection of telemetry data so that they are structured in a uniform manner. In addition, context propagation helps to reuse context data as centralised data collection ensure that there are no duplicates and it is collected only once. OpenTelemetry: https://opentelemetry.netlify.app/docs/specs/otel/ OpenTelemetry Context Propagation: https://opentelemetry.io/docs/concepts/context-propagation/"
'Registered Organization Vocabulary facilitates usage in multilingual contexts through its handling of legal names. By using the appropriate tags and properties, the specification acknowledges that a business might have more than one legal name, particularly in countries with multiple official languages, and therefore recommends that the language of each legal name string should be identified. Registered Organization Vocabulary reference: https://www.w3.org/TR/vocab-regorg/'
'As specification fostering the interoperability between public administrations, RDF helps to enhance the data exchange and reuse in a cross-border way and impacts positively on the development of eGovernment. This fact includes the support to Once-only principle implementation. RDF primer document: https://www.w3.org/TR/rdf11-primer/'
'HTTP provides a framework for access control and authentication, enabling servers to challenge client requests and clients to provide authentication information. HTTP /1.1 RFC 2616 Reference: https://www.rfc-editor.org/rfc/rfc2616 HTTP/1.1 Authentication, RFC 9110 Reference: https://www.rfc-editor.org/rfc/rfc9110#name-http-authentication'
IPv4 is a sector agnostic specification that allows its implementation independently form the business domain.
'SCIM has a specific section that lists SCIM 2.0 and SCIM 1.1 implementations that are directly used to create innovative solutions. For instance, Microsoft uses SCIM 2.0 to develop and plan provisioning for a SCIM endpoint in Microsoft Entra ID. SCIM: https://scim.cloud/ Azure Active Directory SCIM Provisioning: https://learn.microsoft.com/en-us/entra/identity/app-provisioning/use-scim-to-provision-users-and-groups'
'Linked Data Event Streams (LDES) is designed to be platform-agnostic. The key idea behind Linked Data Event Streams is to provide a standardized approach for representing and publishing real-time event data on the web using Linked Data principles. The use of web standards, such as RDF (Resource Description Framework) and HTTP, contributes to the platform-agnostic nature of Linked Data Event Streams. LDES specification: https://joinup.ec.europa.eu/collection/semic-support-centre/linked-data-event-streams-ldes'
CAMSS Assessment of IPSec EIF Scenario v1.0.0
There are no Member States recommending CLV in their ICT National Catalogues. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
JSON in itself does not provide security features, which is a weakness per se. The storage of private date as JSON format is not recommended in order to avoid malicious activities against stored information. Despite this, there are several additional features with the aim of protecting data exchange.
The Registered Organisation Vocabulary was first developed and published by the European Commission ISA Programme with support from the Directorate General Internal Market and Services. The Semantic Interoperability Community (SEMIC) as an action of ISA², has established Working Groups. These Working Groups are open to the participation of everyone interested in semantic solutions working for public administrations in the Member States or in EU institutions. SEMIC working groups: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/about
"DNS does not relate to data integrity, but its DNS Security Extensions (DNSSEC) contributes in this area by ensuring that DNS responses haven't been tampered with during transmission, which enhances data integrity. DNS IETF reference: https://datatracker.ietf.org/doc/html/rfc8499"
'The purpose of EN 303 645 is not related to the long-term preservation of data/information/knowledge. Therefore, this criterion is considered not applicable to this specification. EN 303 645 reference: https://www.etsi.org/deliver/etsi_en/303600_303699/303645/02.01.01_60/en_303645v020101p.pdf'
'SAREF is maintained by the European Telecommunications Standards Institute (ETSI), a European Standards Organization (ESO) that is recognised as the regional standards body dealing with telecommunications, broadcasting and other electronic communications networks and services. ETSI has created a specific community for users to discuss about SAREF and report possible bugs. ETSI: https://www.etsi.org/about SAREF Discussion Forum: https://labs.etsi.org/rep/saref/'
The purpose of the Core Location Vocabulary is not related to long term preservation of electronic records. Therefore, this criterion is considered not applicable to this specification. CLV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-location-vocabulary
The LegalRuleML works to advance worldwide best practices for the use of XML within a Parliaments', Assembly's or Congress' document management processes, within courts' and tribunals' judgment management systems, and generally in legal documents including contracts. The specification as can be domonstrated for its implementation in LEOS project and pilot, can ease and foster the visibility of data, administrative rules and ease the decision making process of public administrations. LegalRuleML reference: http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/legalruleml-core-spec-v1.0.html LEOS: https://joinup.ec.europa.eu/collection/justice-law-and-security/solution/leos-open-source-software-editing-legislation
'The available information does not specifically mention if the specification is included in any initiative at European or National level covering privacy aspects.Therefore, this criterion is considered not applicable to this specification. OGC TrainingDML-AI Standard: https://docs.ogc.org/is/23-008r3/23-008r3.html'
'XHTML does not provide access control mechanism. Therefore, this criterion is not applicable to the specification. XHTML W3C reference: https://www.w3.org/TR/xhtml1/'
'SmartM2M (Study for oneM2M) and the European Student Card are considering the use of GraphQL. Furthermore, the VAT4SME initiative is willing to include in their formal agreements with organisations or administrations involved the use of GraphQL as a European public service component. SmartM2M - Study for oneM2M (ETSI): https://www.etsi.org/deliver/etsi_tr/103700_103799/103715/01.01.01_60/tr_103715v010101p.pdf European Student Card (Erasmus+): https://erasmus-plus.ec.europa.eu/european-student-card-initiative/help-support/technical VAT scheme for Small Businesses reference: https://taxation-customs.ec.europa.eu/vat-scheme-small-businesses_en'
The specification of SVG is available for free, at the European Platform Joinup. Also, it can be checked on the W3C official webpage: SVG 1.1 on Joinup: https://joinup.ec.europa.eu/solution/scalable-vector-graphics-svg-11-specification/distribution/scalable-vector-graphics-svg-11-specification W3C Specification: https://www.w3.org/TR/SVG11/
"WSDL enables service providers to define the interfaces and operations of their web services in a standardized manner. This can facilitate interoperability between different systems and services, making it easier for European public services to exchange information and functionality. Moreover, the specification helps to make administrations and stakeholders' web services available, with information related to them and endpoints that ease the consumption. This fact supports the reuse of data and web services avoiding administration and stakeholders to carry out unnecessary steps or transactions. W3C WSDL specification: https://www.w3.org/TR/wsdl20/"
XML can be used independently from any other technical specifications or operating system. See: https://www.w3.org/TR/2006/REC-xml11-20060816/
'There are pilot assessments made in Finland, Nordic countries and Estonia. However these are not official assessments endorsed by XBRL International Inc. https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/2021/03/22/eInvoicing+helping+standardise+transactional+data+in+Estonia https://www.oecd.org/tax/forum-on-tax-administration/publications-and-products/45045602.pdf : " In their implementation strategy for SAF-T, revenue bodies should consider data formats that permit audit automation today while minimising potential costs to all stakeholders when moving to new global open standards for business and financial data such as XBRL, and XBRL- GL in particular. " page 10 https://www2.deloitte.com/content/dam/Deloitte/in/Documents/risk/in-risk-xbrl-the-new-world-of-reporting-noexp.pdf '
The main objective of the Portable Document Format/A (PDF/A) is to allow text format and images to be independent and work for any software, hardware, or operating system while transferring. Additionally, PDF/A is widely used by administrations to share their information and data. Fostering the availability of data and information, it fosters the data portability using documents. Moreover, the PDF/A includes features that impact positively the preservation of the information contained in this format. It is an extended method to ensure the availability of digital information over time.
The purpose of FTPS is not related to organisational interoperability. Therefore, this criterion is not applicable to the specification. FTPS IETF reference: https://tools.ietf.org/html/rfc4217
'While SCIM itself does not provide specific mechanisms for protecting information against unauthorized changes, identity management technologies inherently include access control that allows organisations to define who has permissions to perform specific operations on user identities, which is indirectly enabling data integrity. SCIM: https://scim.cloud/'
'DAPS is not included in any national catalogue of recommended specifications whose Member State NIF has a high performance on interoperability according to NIFO factsheets. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards'
'Many communities can be found in the internet addressing DNS and sharing their implementation results. One of them is the Github repository, where a large community of developers mantaining discussions around the main issues and subjects that DNS arises. DNS in Github: https://github.com/topics/domain-name-system'
The specification is available for evaeryone to implement and study at SDO's webpage. LegalRuleML reference: http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/legalruleml-core-spec-v1.0.html
'This Core Vocabulary offers several services that aim to help e-Government professionals share their experience with each other, so it fosters the creation of innovative solutions. CPSV-AP Joinup webpage: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/core-public-service-vocabulary-application-profile/release/22'
'The ebXML specification can be found in the UBL 2.1, which is a library of standard electronic business documents in XML (Extensible Markup Language) format that is free from copyright. UBL 2.1 operates within a standardised commercial framework, such as ISO 15000 (ebXML), providing a complete and standardised infrastructure. ebXML UBL 2.1 eur-lex: https://eur-lex.europa.eu/legal-content/ES/TXT/?uri=CELEX%3A32014D0771&qid=1743495780482 ebXML RegRep OASIS reference: https://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html'
The purpose of SVG is not related to the once-only principle. Therefore, this criterion is not applicable to the specification. SVG W3C reference: https://www.w3.org/TR/SVG11/
'After searching in the different official European websites, there is a piece of evidence of a cross-border project that use OCSP involving the usage of the specification. Digital Signature Service framework reference: https://ec.europa.eu/cefdigital/DSS/webapp-demo/doc/dss-documentation.html'
'Currently the specification does not include a public review of the release life-cycle although the specification and its releases are publicly available. This is dependent on the members off the committee involved on the review. Any IS/IEC Publicly Available Standard (PAS) is systematically reviewed every 3 years, the committee members re-asses the standard and propose updates (if necessary). OSI reference https://www.iso.org/standard/20269.html ISO public review guide: https://www.iso.org/files/live/sites/isoorg/files/store/en/PUB100413.pdf'
'The ebXML specification can help guarantee data integrity by providing mechanisms such as digital signatures. In this context, XML digital signatures are used in ebXML to ensure data integrity on messages, existing authentication and authorisation schemes, as well as non-repudiation between entities. As described in the "Secure ebXML Business Transaction Models Applying Web Service Security Standards" article, SAML is recommended to provide identification, authentication, and authorisation, and is often used with XACML to allow or deny access to an XML resource. Secure ebXML Business Transaction Models Applying Web Service Security Standards: http://article.nadiapub.com/IJSIA/vol6_no2/46.pdf ebXML RegRep OASIS reference: https://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html'
'ISO/IEC 19944-1 emphasizes the importance of security controls within cloud computing environments. Public Administrations can use the specification as a basis for implementing security controls to protect personal data. This may include measures such as encryption, access controls, data anonymization, and data breach response procedures. ISO/IEC 19944-1 specification: https://www.iso.org/standard/60545.html'
'The purpose of SFIA is not related to enabling the long-term preservation of data, information nor knowledge. Therefore, this criterion does not apply to this specification. SFIA reference: https://sfia-online.org/en/sfia-8'
'There is no public consultation foreseen in the development process of the EuroVoc. However, the maintenance team at the Publications Office collects and examines the proposals made by EuroVoc users. EuroVoc Handbook: https://publications.europa.eu/resource/cellar/a2723a83-574f-11eb-b59f-01aa75ed71a1.0001.01/DOC_1 EuroVoc: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource /dataset/eurovoc'
'ETSI TS 119 511 specifies policy and security requirements for trust service providers providing long-term preservation of digital signatures and general data using digital signature techniques. The specification performance is closely related to the different specifications involved in electronic signatures across borders. In the context of the European internal market (see article below), it can be considered an asset for the creation of solutions enhancing the interoperability between administrations and businesses when eSignature, and long-term preservation of electronic records are needed. ETSI TS 119 511 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119511/01.01.01_60/ts_119511v010101p.pdf Article: Towards a standardised preservation service for qualified electronic signatures and qualified electronic seals: https://dl.gi.de/bitstream/handle/20.500.12116/20980/proceedings-01.pdf?sequence=1&isAllowed=y'
Like all the IETF standards, LDAP is a free and open technical specification, built on IETF standards and licenses from the Open Web Foundation. LDAP is therefore licensed on a royalty-free basis. No IPR disclosures have been submitted directly on the LDAP specification (RFC 4511). Intellectual Property Rights in IETF: https://tools.ietf.org/html/rfc3668
CAMSS Assessment of FTP EIF Scenario v1.0.0
Even though EuroVoc is mainly focused on eGovernment since it was developed to support the data processing and classification within European Institutions, it covers different domains and subdomains that go beyond eGovernment such as energy or transports. Therefore, it can be considered as reusable amongst other business domains. EuroVoc webpage: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/eurovoc
UDDI is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). Specifically, UDDI can define the interoperability aspects of the "Service Discovery Component", "Service Discovery Service", "Service Registration Service "and "Service Registry Component" ABBs of the EIRA Technical View. See: https://joinup.ec.europa.eu/solution/elis/distribution/eliscataloguev100betaxlsx
CSS v2.1 has had market acceptance for unified web design for years used with HTML which is widely accepted, but with the release of the CSS3 version that uses CSS v2.1 specification as its core, its use has been reduced. CSS3 has implemented some modules and functionalities of the CSS v2.1 specification. Moreover, some modules of CSS3 have been accepted as standard by W3C, for example: CSS Colour Module Level 3 (W3C Recommendation 06 November 2018). CSS v2.1 W3C reference: https://www.w3.org/TR/2011/REC-CSS2-20110607/ CSS Color Module Level 3 W3C reference: https://www.w3.org/TR/2018/REC-css-color-3-20180619/
'The purpose of this specification is not related to ensuring the protection of personal data managed by Public Administrations. Therefore, this criterion does not apply to this specification. LDES specification: https://joinup.ec.europa.eu/collection/semic-support-centre/linked-data-event-streams-ldes'
There is no Member State that includes FTPS in their national catalogue with The National Interoperability Framework (NIF) aligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'AMQP does not enable the visibility of administrative procedures, rules data, and services. Therefore this criterion is not applicable. OASIS AMQP Reference: http://docs.oasis-open.org/amqp/core/v1.0/amqp-core-complete-v1.0.pdf'
'BFO is already associated to the EIRA ABB Ontology in the EIRA Library Of Interoperability Specifications (ELIS). EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /solution/elis/release/v610'
MIME is included in 3 national catalogues of recommended specifications. They belong to the Netherlands, Spain and Sweden. The National Interoperability Framework (NIF) of these Member States is fully aligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. CAMSS List of standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards National Interoperability Framework Observatory: https://joinup.ec.europa.eu/collection/national-interoperability-framework-observatory-nifo/nifo-factsheets The Netherlands Catalogue: https://www.forumstandaardisatie.nl/open-standaarden/lijst Spain Catalogue: https://administracionelectronica.gob.es/pae_Home/pae_Estrategias/pae_Interoperabilidad_Inicio/pae_Normas_tecnicas_de_interoperabilidad.html#CATALOGOESTANDARES Sweden Catalogue: http://www.avropa.se/dynamiska-sidor/sok/?query=standards&searchtype=web
The standard provides security features that foster the trustworthy data exchange between administration and stakeholders. PDF protects in itself data integrity, but also provides capabilities to protect with passwords and user roles the access to the document.
The purpose of CSS is not related to organisational interoperability. Therefore, this criterion is not applicable to the specification. CSS v2.1 W3C reference: https://www.w3.org/TR/2011/REC-CSS2-20110607/
'The SMP 2.0 specification aims to simplify the delivery of European public services. By providing a standardized approach to service metadata publishing and discovery, the specification enables easier access to and integration of public services across different systems and organizations. SMP OASIS reference: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505009'
FTPS as an extension of FTP, is used for file exchange by some public organisations. By allowing public administration to share information with others, it fosters the visibility of data (e.g. administrative rules, processes etc.) and facilitates public administrations the decision-making. FTPS IETF reference: https://tools.ietf.org/html/rfc4217
'Currently, ELI is associated with EIRA ABBs in the European Library Of Specifications. Specifically, ELI can define the interoperability aspects of the "Legislation Catalogue" ABBs of the EIRA Legal View, and "Ontology" ABB from the Semantic View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /solution/elis/release/600'
"ebXML allows extensibility or the addition of plugins in the specification's ebRIM and ebRS components. Although such extensibility is limited to some of the ebRIM and ebRS features, ebXML RegRep 4.0 - Part 1 and Part 2 specify how extensibility may be achieved, that is, either by extending ebRIM or modifying the ebRS service interface. It is the case of the ebXML RegRep SWG specification (see ebXML RegRep SWG reference), which is an Open Geospatial Consortium's authoring of the ebXML specification and which deals with the use of geo-data in a variety of contexts. ebXML reference: http://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html ebXML RegRep Part 1, Extending ebRIM section: http://docs.oasis-open.org/regrep/regrep-core/v4.0/csprd01/regrep-core-rim-v4.0-csprd01.html#__RefHeading__39225_1821683062 ebXML RegRep Part 2, Cataloguer Plugin section: http://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-rs-v4.0-os.html#__RefHeading__32575_422331532 ebXML RegRep SWG reference: https://www.ogc.org/projects/groups/ebxmlregrepswg"
The adoption of Ogg as a media container format for exchanging data does not hamper the scalability of systems. It is widely adopted for this purpose because it is independent of any platform. Ogg XIPH reference: https://xiph.org/ogg/doc/rfc3533.txt
'The main goal of DPV is to develop a taxonomy of privacy terms, which include in particular terms from the new European General Data Protection Regulation (GDPR) in order to ease proof of compliance with the GDPR and related privacy protection regulations. DPV specification: https://w3c.github.io/dpv/dpv/ DPV primer document: https://w3c.github.io/dpv/primer/#introduction'
After searching in the different official European websites, there is no evidence of any cross-border project that use JPEG nor explicit agreements involving the usage of the specification.
'The ESPD itself does not enable access control mechanisms, but it can be used as part of a wider system or platform that includes these mechanisms. Commission Decision (EU, Euratom) 2017/46 of 10 January 2017 on the security of communication and information systems in the European Commission: https://eur-lex.europa.eu/legal-content/EN/TXT/?qid=1548093747090&uri=CELEX:32017D0046 ESPD business handbook: https://docs.ted.europa.eu/ESPD-EDM/latest/xml_business_handbook.html'
'The use of a shared ontology like SAREF can significantly reduce complexities and barriers in establishing interoperable systems across organizational boundaries. SAREF can be used to technogically maintain a single consistent definition of various concepts in the IoT domain, which can facilitate interoperability agreements in that field. SAREF: https://saref.etsi.org/core/v3.1.1/ SAREF repository: https://labs.etsi.org/rep/saref/ '
'OASIS specifications operate under OASIS IPR Policy, which is aligned with F/RAND principles. Genericode is freely available for anyone to use, implement, and distribute without the need for royalties or licensing fees. In fact, it is often promoted by the standards organisations and industry bodies because of its openess and accessibility. OASIS Intellectual Property Rights (IPR) Policy: https://www.oasis-open.org/policies-guidelines/ipr/'
'The PROV family is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). Specifically, the PROV family can define the interoperability aspects of the "Controlled Vocabulary" "Data", "Data Model", "Data Syntax", "Forms Structure", "Hash Code", "Metadata" and "Ontology ABB of the EIRA Semantic view. ELIS reference: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /solution/elis/release/v501'
The message returned by a Service Metadata Publisher service is signed using one or more [XML-DSIG1] XML-Signatures. Moreover, the purpose of the specification is to ease and ensure the discoverability of different parties to exchange the desired information. The specification defines a set of requirements regarding the authentication of parties that ensures secure and trustworthy data exchange. The specification: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505000
"The specification conformance could be tested against a manual checking or even implementing a schematron validator based on the specification data model to check it's implementation. CCCEV: https://joinup.ec.europa.eu/solution/core-criterion-and-core-evidence-vocabulary/about"
'By allowing the authentication for using services SAML 2.0 can enable the exposure of interfaces to access the public administrations services by simplifying its access. Moreover, it can be used internally by public officers which enhances the decision-making process, but it is not its main purpose. SAML 2.0 Reference: http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-tech-overview-2.0.html'
Like all the IETF standards, MIME is a free and open technical specification, built on IETF standards and licenses from the Open Web Foundation. Therefore, MIME is licensed on a royalty-free basis. Intellectual Property Rights in IETF: https://tools.ietf.org/html/rfc3668
'The purpose of the Core Location Vocabulary is to create a reusable and extensible data model that captures the fundamental characteristics related to locations. By providing a set of information to describe data in the sectors mentioned before, it helps public administrations with the visualisation of people, locations or business. Core Location Vocabulary: https://interoperable-europe.ec.europa.eu/collection/semic-support-centre/solution/core-location-vocabulary/release/100'
'Better Regulation Guidelines and Toolbox includes requirements for the alignment with relevant regulations at European level such as eIDAS, GDPR, Cybersecurity Act, etc. Ensuring that the development of policies and laws is aligned with the main legal acts, including the interoperability ones. In this sense, the Better Regulation Toolbox supports the establishment of public services and tools fostering data portability, specifically on Tool 28. DIGITAL-READY POLICYMAKING. Better Regulation Guidelines and Toolbox reference: https://commission.europa.eu/law/law-making-process/better-regulation/better-regulation-guidelines-and-toolbox_en Better Regulation Toolbox reference: https://commission.europa.eu/document/download/9c8d2189-8abd-4f29-84e9-abc843cc68e0_en?filename=BR%20toolbox%20-%20Jul%202023%20-%20FINAL.pdf eIDAS reference: https://digital-strategy.ec.europa.eu/en/policies/eidas-regulation GDPR reference: https://eur-lex.europa.eu/EN/legal-content/summary/general-data-protection-regulation-gdpr.html# Cybersecurity Act reference: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=LEGISSUM%3A4398780'
Zaragoza's City Town hall using HTML5 exemplifies the promotion of the once-only principle work towards unifying the services offered regardless of the platform. See: https://www.w3.org/2012/12/html5-cr.html.en
The purpose of RegOrg is not related to e-accessibility. Therefore, this criterion is considered not applicable to this specification. RegOrg Joinup reference: https://joinup.ec.europa.eu/solution/registered-organization-vocabulary
'The specification can help to ensure the privacy by design, as EIRA foresees and includes specific ABBs related to guarantee that privacy is considered as requirements in the analysis of solutions that will lead to privacy in the implementation phase. To be more specific, EIRA provides the set of specific ABBs in a viewpoint that are key to achieve privacy, and to consider it from the very beginning. Additionally, which the flexibility that provides the specifications, it can be extended and specialised as needed to ensure that specific needs and requirements are covered. EIRA reference: https://interoperable-europe.ec.europa.eu/collection/european-interoperability-reference-architecture-eira /solution/eira/release/610 EIRA Github Repository: https://github.com/CarTool-EC/EIRA'
'YAML can help enabling the visibility of administrative procedures by listing public administrations services or having a record of interested people. Moreover, configuration management allows to store software configurations to make them more accesible. In addition, it also allows defining automation workflows, making the steps and logic of administrative processes more explicit and reviewable. YAML specification: https://yaml.org/spec/1.2.2/'
'The Advanced Encryption Standard (AES) allows information protected by AES in one system to be used and understood by any other system that also correctly implements the standard and possesses the appropriate key. AES Standard Reference: https://csrc.nist.gov/pubs/fips/197/final'
'In the specification's documentation it is mention in section 2.4 "Conformance" that XSD has a property that can work both ways with the value on "full" or on "partial", that means it can potentially be implemented partially. XSD Reference: https://www.w3.org/TR/2012/REC-xmlschema11-1-20120405/'
The project is based on openness and this philosophy has led to establish a framework for development that allows everyone with interest and knowledge to contribute to the improvement of the specification. The Standard for Public Code webpage: https://standard.publiccode.net/ The Standard for Public Code contributing section: https://standard.publiccode.net/CONTRIBUTING.html
'By associating a name to an IP, DNS facilitates the identification of the content of domains and therefore, it can be said to reduce the administrative burden. DNS IETF reference: https://datatracker.ietf.org/doc/html/rfc8499'
'According to the NFV home page, services are deployed by complementing Software Defined Networking (SDN) and NFV. However, the NFVI specification does not rely on any operating system, therefore this specification is platform-agnostic. NFV reference: https://www.etsi.org/technologies/nfv/nfv'
The purpose of SOAP 1.2 is not related to organisational interoperability. Therefore, this criterion is not applicable to the specification.
'GITB TDL provides a framework for testing the efficient and secure processing of information/data. See an example of this characteristics in the reference provided: GITB TDL example reference: ASiC container validation for eTendering processes https://www.itb.ec.europa.eu/docs/tdl/latest/examples/index.html#example-7-asic-container-validation-for-etendering-processes'
'EN 16234-1 e-CF does not foresee public reviews. There is no direct evidence that a public review is conducted according to the CEN/TC 428 "ICT Professionalism and Digital Competences" and IT Professionalism Europe (ITPE) documentation. CEN/TC 428 "ICT Professionalism and Digital Competences" Business Plan 2022 reference: https://standards.cencenelec.eu/BPCEN/1218399.pdf IT Professionalism Europe (ITPE) reference, Archive section: https://itprofessionalism.org/resource-library/reports-publications/archive/'
'CPOV is included in 1 national catalogue of recommended specifications. It belong to Spain. The National Interoperability Framework (NIF) of Spain is fully aligned with at least 2 out of 3 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. CPOV Spain national catalogue: https://administracionelectronica.gob.es/ctt/verPestanaActivosSemanticos.htm?idIniciativa=3351 NIFO factsheets: https://joinup.ec.europa.eu/collection/national-interoperability-framework-observatory-nifo/nifo-factsheets CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards'
'Numerous studies have been conducted to evaluate the efficiency of TLS 1.3, offering detailed insights into how this version addresses critical security challenges, optimises performance, and meets modern technological demands. One report worth highlighting is the Encrypted Traffic Analysis by the European Union Agency for Cybersecurity (ENISA) which explores the current state of affairs in Encrypted Traffic Analysis and in particular discusses research and methods in 6 key use cases. Encrypted Traffic Analysis by the European Union Agency for Cybersecurity: https://www.enisa.europa.eu/sites/default/files/publications/ENISA%20Report%20-%20Encrypted%20Traffic%20Analysis.pdf TLS 1.3 ADOPTION IN THE ENTERPRISE by Paula Musich: https://www.f5.com/pdf/reports/tls-1-3-ema-report.pdf'
By allowing the exchange of digital documents, ODF avoids sharing non-digital documents and then helps to the reduction of administrative burden. UK Sharing and collaborating with government documents https://www.gov.uk/government/publications/open-standards-for-government/sharing-or-collaborating-with-government-documents ODF ISO reference: https://www.iso.org/standard/66363.html ODF OASIS reference: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office
'XML is included in several national catalogues from Member States. A total of 14 countries listed the XML within their national catalogues (e.g. Belgium, France, Germany, etc.). See CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards '
"DAPS is not included in any Member States' catalogues of recommended specifications. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards"
'Schema.org allows for partial implementation as long as the schema implementation is conformant with the specification requirements, namely those requirements concerning the schema data structure. The schema.org project highly recommends the use of authoring schema validators. Schema.org reference, Data model section, Conformance section: https://schema.org/docs/datamodel.html'
'Extensibiltiy is one of the key factors that make LDAP a popular standard protocol. LDAP functionalities can be extended depending on the developer needs. Common extensions are the SASL Authentication mechanism or the Dynamic Password Verifiers. LDAP IETF Extension: https://datatracker.ietf.org/wg/ldapext/about/'
'The Asset Administration Shell (AAS) is the standardised digital representation of an asset. The AAS may be the logical representation of a simple component, a machine or a plant at any level of the equipment hierarchy. The specification can contribute to the visibility of manufacturing processes and the generated data to the administrators. In this sense the specification helps the different partners modulate their manufacturing processes to the same specifications and make any given part interchangeable. Details of the Asset Administration Shell (AAS) https://industrialdigitaltwin.org/en/wp-content/uploads/sites/2/2024/06/IDTA-01001-3-0-1_SpecificationAssetAdministrationShell_Part1_Metamodel.pdf'
"In the specification's documentation there is no mention to customisation. SMP OASIS reference: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505009"
'ETSI TS 119 432 addresses and enables the implementation of features to guarantee data accuracy. For instance, it guarantees data accuracy by providing a interface capable of warning if it cannot accurately present all parts of the SD according to the data content type when the SCASC presents the document to the signer. ETSI TS 119 432: https://www.etsi.org/deliver/etsi_ts/119400_119499/119432/01.02.01_60/ts_119432v010201p.pdf'
'SCIM is based on web standards, particularly RESTful principles and JSON (JavaScript Object Notation) for data representation. This design choice makes it easy to integrate SCIM with different platforms that support HTTP-based communication and JSON data format. As a result, SCIM can be implemented in a wide range of environments. SCIM: https://scim.cloud/'
'The OpenTelemetry specification is primarily designed for observability, focusing on the collection and analysis of telemetry data such as traces, metrics, and logs from software systems. Modelling business processes typically involves higher-level concepts and frameworks that go beyond the scope of network protocols like OTel. OpenTelemetry: https://opentelemetry.netlify.app/docs/specs/otel/'
'The CPSV-AP specification provides a standard way of describing public services that can be used across different countries and jurisdictions, and it facilitates the exchange of information and data between different systems and platforms. CPSV-AP Joinup webpage: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/core-public-service-vocabulary-application-profile/release/22'
After checking the different standard catalogues at supra-national level, there is no evidence of the inclusion of SMTP within any European catalogue of standards. However, a variant of SMTP that is safer in terms of network security, DANE for SMTP, is included in the European list of ICT Standards for e-procurement. ICT technical specifications: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en
'The secure exchange of data using iCalendar can be achieved by implementing additional security measures, such as encryption, authentication, and using secure communication protocols like HTTPS, when transmitting iCalendar data between systems and applications. iCalendar specification: https://www.rfc-editor.org/rfc/rfc5545'
'After being evaluated compliant with the Regulation on Standardisation 1025/2012, IPv6 has been identified by Commission Implementing Decision and included in the European list of ICT Standards for eprocurement. The specification can also be found in the Joinup repository. ICT Technical Specifications: https://single-market-economy.ec.europa.eu/single-market/european-standards/ict-standardisation/ict-technical-specifications_en'
'ISO/IEC 27001 was published back in 2005 and has undergone several changes, being last modified in 2015. Although Draft versions are publicly available, change management and release management processes are not open to the public. ISO/IEC 27001 foreword: https://www.iso.org/obp/ui/#iso:std:54534:en ENISA-ISO/IEC 27001 reference: https://www.enisa.europa.eu/topics/threat-risk-management/risk-management/current-risk/laws-regulation/rm-ra-standards/iso-iec-standard-27001?msclkid=81681be8affa11ecb89769e4176d852c '
This Core Vocabulary is not included in any Member States' catalogues of recommended specifications. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'The XML specification itself does not provide inherent protection against unauthorized changes to the information it represents. Therefore this criterion is not applicable to the specification.'
CSS is a style sheet language used for describing the presentation of a document written in a markup language like HTML. CSS is a cornerstone technology of the World Wide Web. CCS v2.1 went to proposed recommendation on 12 April 2011. After being reviewed by the W3C Advisory Committee, it was finally published as a W3C Recommendation on 7 June 2011 and it has been used for the development of many webs. Therefore, the maturity of the specifications is widely demonstrated. CSS v2.1 W3C reference: https://www.w3.org/TR/2011/REC-CSS2-20110607/
JPEG is a business domain agnostic specification that can be reused in a cross-domain way. JEPG ISO reference: https://www.iso.org/standard/18902.html JPEG public reference: https://jpeg.org/jpeg/
'DQV has not been found included in any national or European initiative covering privacy aspects. Data Quality Vocabulary: https://www.w3.org/TR/vocab-dqv/'
'The purpose of this specification is not related to ensuring and enabling data processing accuracy. Therefore, this criterion is not applicable to this specification. LDES specification: https://joinup.ec.europa.eu/collection/semic-support-centre/linked-data-event-streams-ldes'
'Being a standard protocol for mantaining and accessing directory services, LDAP can be used across business domains as long as they require the storage and management of user information. LDAP IETF reference: https://tools.ietf.org/html/rfc4511 '
IETF is a consensus-based group, and authority to act on behalf of the community requires a high degree of consensus and the continued consent of the community. The process of creating and Internet Standard is straightforward: a specification undergoes a period of development and several iterations of review by the Internet community and revision based upon experience, is adopted as a Standard by the appropriate body... and is published. In practice, the process is more complicated, due to (1) the difficulty of creating specifications of high technical quality; (2) the need to consider the interests of all of the affected parties; (3) the importance of establishing widespread community consensus; and (4) the difficulty of evaluating the utility of a particular specification for the Internet community. The goals of the Internet Standards Process are: - Technical excellence; - prior implementation and testing; - clear, concise, and easily understood documentation; - openness and fairness; and - timeliness. The goal of technical competence, the requirement for prior implementation and testing, and the need to allow all interested parties to comment all require significant time and effort. The Internet Standards Process is intended to balance these conflicting goals. The process is believed to be as short and simple as possible without sacrificing technical excellence, thorough testing before adoption of a standard, or openness and fairness. See: https://tools.ietf.org/id/draft-gutmann-tls-lts-10.html
The adoption of EuroVoc as a mechanism for the standardisation and processing of administrations data is useful and proportionate to administration's needs but also external users like citizens and businesses. EuroVoc webpage: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/eurovoc
After searching in the different official European websites, there is no evidence of any cross-border project that use Ogg nor explicit agreements involving the usage of the specification.
'The purpose of FTP is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification. FTP Specification Reference: https://datatracker.ietf.org/doc/html/rfc959'
'The specification is independent from any particular software, hardware, or operating system. So, it can be said that EuroVoc is independent of any specific technology. EuroVoc: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource /dataset/eurovoc'
"HTTP Cookies is the most widely used standard protocol serving essential functions on the web such as storing stateful information on the user's device or tracking the user's browsing activity. The first version of HTTP Cookies was released on 1997, oundergoing several improvements until the last version from 2011. Therefore, we can say that HTTP Cookies is sufficiently mature for the development of products and services. HTTP Cookies reference: https://datatracker.ietf.org/doc/html/rfc6265 HTTP Cookies first release: https://datatracker.ietf.org/doc/html/rfc2109 Google Analytics reference: https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage?hl=es#analyticsjs "
"Like all the IETF standards subject to the IETF Trust's Legal Provisions Relating to IETF Documents, OCSP is a free and open technical specification, built on IETF standards and licenses from the Open Web Foundation. Therefore, OCSP is licensed under (F)RAND basis. Intellectual Property Rights in IETF, section 8: https://tools.ietf.org/html/rfc3668 IETF Trust's Legal Provisions Relating to IETF Documents: http://trustee.ietf.org/license-info"
'ODRL is a standard language that makes digital content rules clear, uniform and easy to automate across systems ensuring transparent and controlled access to content or services. Furthermore, the specification is designed to address administrative procedures, rules data, and services related to the management of digital rights. By providing interoperable vocabulary, model and encoding mechanisms, the specification contributes to the standardisation of the statements and conditions of use for public services and improves the comprehensibility of administrative services. W3C specification reference: https://www.w3.org/TR/odrl-vocab/#vocab-core'
'The purpose of the EuroVoc is not related to the availability of interfaces with internal information systems. Therefore, this criterion is not applicable to this specification. EuroVoc: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource /dataset/eurovoc'
No mechanisms assessing the compliance of implementations with the specification have been found.
'The purpose of NUTS is not related to the implementation of the once-only principle. Therefore, this criterion does not apply to this specification. EUROSTAT reference, NUTS Principles and Characteristics section: https://ec.europa.eu/eurostat/web/nuts/principles-and-characteristics'
9 Member States are recommending JSON in their ICT National Catalogues. See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'The OGC TrainingDML-AI Standard indirectly supports data accuracy by defining standardized formats and detailed metadata for geospatial training data, which helps ensure the quality and reliability of data used in AI /ML applications. OGC TrainingDML-AI Standard: https://docs.ogc.org/is/23-008r3/23-008r3.html'
The purpose of Xforms is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification. Xforms 2.0 W3C reference: https://www.w3.org/community/xformsusers/wiki/XForms_2.0
'There can be found many extensions for domain-specific OAIS implementations, such as for the preservation of digital publications, or service-based extensions such as the OAIS archive for science data management. Service-Based Extensions to an OAIS Archive for Science Data Management: https://ui.adsabs.harvard.edu/abs/2014AGUFMIN53C3820F/abstract Preservation of Digital Publications: An OAIS Extension and Implementation: https://www.researchgate.net/publication/221352905_Preservation_of_Digital_Publications_An_OAIS_Extension_and_Implementation'
The purpose of DNS is not related with data portability. Therefore, this criterion is not applicable for this specification.
'Better Regulation Guidelines and Toolbox is publicly available and aims to help public administrations in the development of public policies and laws according to real needs while it makes the process and data generated more transparent, fostering the accountability of public administrations. Better Regulation Guidelines and Toolbox reference: https://commission.europa.eu/law/law-making-process/better-regulation/better-regulation-guidelines-and-toolbox_en Better Regulation Guidelines reference: https://commission.europa.eu/document/download/d0bbd77f-bee5-4ee5-b5c4-6110c7605476_en?filename=swd2021_305_en.pdf Better Regulation Toolbox reference: https://commission.europa.eu/document/download/9c8d2189-8abd-4f29-84e9-abc843cc68e0_en?filename=BR%20toolbox%20-%20Jul%202023%20-%20FINAL.pdf'
'CPOV is part of the Core Vocabularies, which allow for extension. One of the extensions available for Core Vocabulary family is the OSLO extension, which extends the Core Vocabularies to include properties and relationships, like family composition, contact details, or persons acting on behalf of a registered organization. Despite this, CPOV its also a simplified, reusable, and extensible data model. OSLO extension for Core Vocabularies: https://www.w3.org/2013/share-psi/workshop/berlin/EuropeanInteroperabilityTheISACoreVocabularies CPOV extension reference: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/core-public-organisation-vocabulary/distribution/core-public-organisation-vocabulary-version-100-pdf'
'TSP is not adressed to access control mechanisms, although it can indirectly help improve them through verification processes and audit trails. TSP/TSA reference: https://www.rfc-editor.org/rfc/rfc3161'
'FTP is not a European Standard. FTP Specification Reference: https://datatracker.ietf.org/doc/html/rfc959'
'The Indexed Database API specification is addressed to the storage of information. In this context, the specification allows for the storage of large numbers of objects locally and retrieving them when needed, by using an index. However, the reuse of information is limited to browsers. Indexed Database API: https://www.w3.org/TR/IndexedDB/'
The purpose of Xforms is not related to the publication of public data as open data. Therefore, this criterion is not applicable to this specification. Xforms 2.0 W3C reference: https://www.w3.org/community/xformsusers/wiki/XForms_2.0
Although PNG’s purpose is not the long-term preservation of data, it can be used to store images digitally. PNG W3C reference: https://www.w3.org/TR/PNG/ PNG ISO reference: https://www.iso.org/standard/29581.html
'AMQP is only recommended by the Member State of France. The Référentiel général d'interopérabilité (RGI) currently has AMQP "under observation", meaning that if the experiments prove conclusive, it will be included in a subsequent version of the General Interoperability Framework Status Explanation as "recommended". Otherwise, it will be "withdrawn" from the repository. Référentiel général d'interopérabilité (RGI) Reference: https://www.numerique.gouv.fr/uploads/Referentiel_General_Interoperabilite_V2.pdf NIFO Factsheets: https://interoperable-europe.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public-administration-factsheets-2024 CAMSS list of standards: https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
'NFVI fosters and simplifies the digital exchange in network specific domains. Wireless network, e.g. 5G, deployment is a domain case where the NFVI specification is being considered at a European level. The counterside is that this specification has to be deployed collectively by all Public Administrations. NFVI Deliver, Infrastructure Overview section 7.3: https://www.etsi.org/deliver/etsi_gs/NFV-INF/001_099/001/01.01.01_60/ 5G NFV whipe paper: http://portal.etsi.org/NFV/NFV_White_Paper_5G.pdf'
'Even though EIRA is not a business process modelling tool, withing the organisational view, Public Administrations are able to identify which is the delivery model, the agents, the capability, services and information involved. By establishing the traceability with other views, users can establish the relationship between elements at different levels such as semantic or technical, helping to provide a comprehensive approach of how are services going to be provided and the different components involved. EIRA reference: https://interoperable-europe.ec.europa.eu/collection/european-interoperability-reference-architecture-eira /solution/eira/release/610 EIRA Github Repository: https://github.com/CarTool-EC/EIRA'
'IPv6 allows for implementations and extensions that can be implemented incrementally or separately. There is a recommended command to implement the header extensions, but it is possible to implement them independently. IPv6 extension headers: https://www.rfc-editor.org/rfc/rfc2460#section-4'
The Internet Protocol is a key point in the data exchange through the internet. In its aim to ensure communication over computer networks eases the availability of interfaces with internal information. This fact allows the administrations to exchange and reuse data with each other.
'OAS has been found to be include in the national catalogues of The Netherlands and Malta. National Catalogue of The Netherlands: https://www.forumstandaardisatie.nl/open-standaarden National Catalogue of Malta: https://mccaa.org.mt/Section/Content?contentId=1243'
The main objective of the Portable Document Format/A (PDF/A) is to allow text format and images to be independent and work for any software, hardware or operating system. So it can be said that PDF/A is independent of any specific technology or platform.
"The specification is included in 10 Member States' catalogues of recommended specifications. This are: Bulgaria, Cyprus France, Germany, Greece, Malta, Netehrlands, Portugal, Spain, Sweden. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards"
'The purpose of HTTP Cookies is not related to organisational interoperability. Therefore this criterion is not applicable to this specification. HTTP Cookies reference: https://developer.mozilla.org/en-US/docs/Web/HTTP/Cookies#creating_cookie'
​The Semantic Interoperability Community (SEMIC) that developed this specification, is in charge of developing solutions to help European public administrations perform seamless and meaningful cross-border and cross-domain data exchanges. They develop semantic specifications and interoperability solutions under the ISA² Programme. When a new solution release is finished, it is submitted for a public review with a minimum period of four weeks. Specification development process by the ISA Programme: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/document/description-change-management-release-and-publication-process-structural-metadata-specifications Detailed document ISA Programme: https://joinup.ec.europa.eu/sites/default/files/document/2016-10/description_of_a_change_management_release_and_publication_process_for_structural_metadata_specifications_developed_by_the_isa_progr.pdf
2 Member States are recommending HTML5 in their ICT National Catalogues. See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
There are existing documentation and studies assessing the effectiveness and efficiency of CSS v2.1. It is a comparison between 3 versions, CSS, CSS2 and CSS3. As well, the study shows the improvement of the different versions over time as resulting in more efficient and faster web designs. Comparison CSS2 and CSS3: https://hackr.io/blog/difference-between-css-css2-and-css3
After checking the different standard catalogues at supra-national level, there is no evidence of the inclusion of TIFF/IT within any European catalogue of standards. ICT technical specifications: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en CEN search tool catalogue: https://standards.cen.eu/dyn/www/f?p=CENWEB:105::RESET:::: CENELEC search tool catalogue: https://www.cenelec.eu/dyn/www/f?p=104:107:0::::FSP_LANG_ID:25
EuroVoc is used for the EU Open Data Portal, the site where EU Institutions publish their datasets for their reuse. In there, it is also used the classification of EuroVoc in order to improve the shareability, researchability and interoperability when processing the data. It helps to link data under knowledge domains. EuroVoc in EU Open Data Portal: https://data.europa.eu/euodp/es/data/dataset/building-stock-observatory EuroVoc reference: https://eur-lex.europa.eu/browse/eurovoc.html?locale=en Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/en/
CPOV is a business domain agnostic data model that can be reused in a cross-domain way. CPOV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-organisation-vocabulary
HTML5 is included in several national catalogues from Member States. A total of 2 countries listed the HTML5 within their national catalogues. See CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'According to the 5 star Open Data model suggested by Tim Berners-Lee about how to publish linked data, schema.org is a structured data mark-up schema enabling search engines and other information systems to query data in a structured manner. As well as supporting the publication of data as open data, the specification facilitates the publication of public data as open data since it fulfils all the requirements to generate Linked Data. Schema.org reference, Getting started section: https://schema.org/docs/gs.html Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/en/'
'IPsec enables implementation of different profiles, which involve a set of specific requirements depending on the context of implementation: integration into the native IP stack, or "underneath" an existing implementation of an IP protocol stack. IPSec reference, Where IPSec can be implemented: https://datatracker.ietf.org/doc/html/rfc4301#section-3.3'
'ETSI TS 119 432 does not mention any specific action to support the reuse of relevant information when needed. Therefore, this criterion is considered not applicable to this specification. ETSI TS 119 432: https://www.etsi.org/deliver/etsi_ts/119400_119499/119432/01.02.01_60/ts_119432v010201p.pdf'
'The specification can contribute to the implementation of the once-only principle by setting the principles to manage and reduce the risk related to the information being exchanged between parties. In this sense, by securing and establishing the methods to control and reduce risks when treating sensitive information the specification can contribute, enhance and enable the implementation of the once-only principle. ISO/IEC 27001 reference website: https://www.iso.org/standard/54534.html'
The purpose of the specification is not related to e-accessibility. Therefore, e-Delivery SMP 1.10 is not easing the e-accessibility.
'The purpose of the specification is not related to scope comprehensibly the administrative procedures, rules data and services, therefore it does not promote or hinder it. ETSI EN 319 422 reference: https://www.etsi.org/deliver/etsi_en/319400_319499/319422/01.01.01_60/en_319422v010101p.pdf'
Although TIFF/IT’s purpose is not to foster the visibility of administrative data or services, it can help with the visualization and visibility of public administrations by providing high quality images and print-ready pages that can be easily edited later. TIFF/IT ISO reference: https://www.iso.org/standard/34342.html TIFF/IT explanation: https://www.prepressure.com/library/file-formats/tiffit
LegalDocML is aimed to define a common data and metadata model towards the maximisation of information reuse. It is focused on administration purposes mainly for public administrations, but it also can be extended to more specific sectors requiring legal document management and processing. LegalDocML reference: https://www.oasis-open.org/committees/legaldocml/charter.php
When XHTML became W3C recommendation it had a good acceptance, but when HTML5 appeared, its use has been decreased considerably. In the following link there is a comparison of usage of the different HTML languages and it can be seen that XHTML 1.0 is declining more and more while HTML5 is increasing. XHTML trend: https://try.powermapper.com/Stats/HtmlVersions
Although ADMS’s purpose is not the long-term preservations, it can be used to document and store semantic assets. ADMS on Joinup: https://joinup.ec.europa.eu/solution/asset-description-metadata-schema-adms/about ADMS Specification W3C: https://www.w3.org/TR/vocab-adms/
'The purpose of Advanced Encryption Standard is not related to enable digital service delivery channels. Therefore this criterion is not applicable to this specification. AES Standard Reference: https://csrc.nist.gov/pubs/fips/197/final'
'HTTP does contribute to the authenticity and authentication of agents involved in data transactions by providing a framework for authentication schemes and emphasising the use of secure transport. HTTP/1.1, RFC 2616 Reference: https://www.rfc-editor.org/rfc/rfc2616 HTTP/1.1 Authentication, RFC 9110 Reference: https://www.rfc-editor.org/rfc/rfc9110#name-http-authentication'
eDelivery SMP 1.10 fosters the implementation of the Once-Only Principle by allowing public administrations to share and reuse their information across borders.
"ISO 19941 supports customization to a degree given that applications are transferred and integrated with cloud services, providing flexibility to meet various business objectives and technical needs. ISO 19941 can be tailored to meet the customer's needs. ISO 19941: https://www.iso.org/obp/ui/en/#iso:std:iso-iec:19941:ed-1:v1:en "
"This Technical Specification (TS) has been produced by ETSI Technical Committee Context Information Management (CIM). There are two paths to get involved in ETSI's Industry Specification Groups: as an ETSI member, or as a direct participant. The participation in the technical group is reserved to ETSI members, who require registration, fees, and membership approval. Organizations who are not members of ETSI may still participate in the ISG, attend meetings, subscribe to the e-mail lists and help build the specifications by making technical contributions. They do not have voting rights and must pay a participation fee per person per meeting day to attend ISG meetings. ETSI Technical Committee CIM: https://www.etsi.org/committee/cim Member benefits: https://www.etsi.org/images/files/membership/Membership-leaflet.pdf ETSI ISG Participation: https://www.etsi.org/how-to-get-involved-in-an-isg"
'While the purpose of Dataspace Protocol is not related to enabling digital service delivery channels directly, providing a common framework for the creation of IDS can improve data exchange between systems that implement digital services, improving effectiveness and efficiency. IDSA Dataspace Protocol: https://docs.internationaldataspaces.org/ids-knowledgebase/v/dataspace-protocol/overview/readme'
'Currenlty OSI is used at European level and promoted through the Interoperable europe portal. Given that it can be implemented via different layers it gives the flexibility necessary to have a wide presence in multiple services via partial implementations. OSI on the Interoperable Europe Portal https://interoperable-europe.ec.europa.eu/collection/ict-standards-procurement/solution/isoiec-7498-11994-information-technology-open-systems-interconnection-basic-reference-model-basic OSI reference https://www.iso.org/standard/20269.html'
'ETSI, the SDO/SSO that created and currently maintains the SAREF ontology, explains that most ETSI test specifications are developed according to the well-proven methodology defined in ISO/IEC 9646. This standard, which covers the entire test development process, provides an excellent basis for the production of high-quality test frameworks and specifications. ETSI Conformance Testing: https://portal.etsi.org/Services/Centre-for-Testing-Interoperability/ETSI-Approach/Conformance'
"TLS 1.3 specification permits extensions to provide further customisation and add features to the core protocol. For example, The ClientHello message includes several customisable extensions, enabling the client to communicate its specific preferences and capabilities. Additionally, TLS can facilitate the integration of extensions such as Server Name Indication (SNI), which allows a client to specify the hostname of the server to which it is connecting. This is important for servers that host multiple virtual domains on a single IP address. Without SNI, the server wouldn't know which certificate to present, leading to potential security errors. TLS 1.3 Extensions reference: https://www.rfc-editor.org/rfc/rfc8446.html#section-4.2"
'BFO is independent of any specification and can be implemented without dependencies with technologies. BFO reference: https://www.iso.org/standard/74572.html'
'The specification is designed to facilitate the creation and exchange of legal documents in a machine-readable format, which includes administrative procedures, rules data, and services. By providing a common framework for the representation of legal documents, it enables greater visibility and accessibility of administrative procedures, rules data, and services. Specifically, the specification enables the creation of structured legal documents that include information about the administrative procedures, rules data, and services contained within them. AKN4EU reference: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/akn4eu'
"EU Member States' trusted lists were established in the EU and are primarily aimed at supporting the validation of advanced electronic signatures that are backed by a qualified certificate, as well as advanced electronic signatures supported by both a qualified certificate and a secure signature creation device. These trusted lists include, at a minimum, trust services that are supervised or accredited to issue qualified certificates. This approach explicitly facilitates the secure and trustworthy exchange of data, as it relies on advanced electronic signatures supported by a qualified certificate and a secure signature creation device. ETSI TS 119 612: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf"
The purpose of SAMM is not related to the visibility of administrative information, data or services. Therefore, this criterion is not applicable to this specification. SAMM webpage: https://owaspsamm.org/ SAMM documentation: https://github.com/OWASP/samm/blob/master/Supporting%20Resources/v2.0/OWASP-SAMM-v2.0.pdf
'The purpose of NUTS is not related to facilitating the publication of open data. Therefore, this criterion is not applicable to this specification. EUROSTAT reference, NUTS Principles and Characteristics section: https://ec.europa.eu/eurostat/web/nuts/principles-and-characteristics'
"Schema.org can scope the comprehesibility of administrative procedures, rules data and services on European websites. The specification favours the promotion of semantic interoperability between different applications, basing its logic on the reuse of existing controlled vocabularies and potential mappings to existing metadata vocabularies. The specification will be used along with another specification, DCAT, in order to propose a common DCAT schema (DCAT-AP-SDO, Schema.org profile of DCAT Application Profile for Data Portals in Europe) enabling administrations and citizens to find and understand datasets located in the European Union and all Member States' data portals. Schema.org homepage reference, 'Documentation' section: https://schema.org/docs/documents.html DCAT reference: https://www.w3.org/TR/vocab-dcat-3/ DCAT-AP-SDO reference: https://ec-jrc.github.io/dcat-ap-to-schema-org/"
'As its name states, it is a Reference Architecture. It is the basis for the analysis and design of Digital Public Services in different areas. The specification provides wide range of flexibility, allowing users create solution architecture templates based on EIRA but with Architecture Building Block specific to users needs, or extensions/specialisations of these ABBs. EIRA reference: https://interoperable-europe.ec.europa.eu/collection/european-interoperability-reference-architecture-eira /solution/eira/release/610 EIRA Github Repository: https://github.com/CarTool-EC/EIRA '
'When facilitating information exchange between systems and applications, the specification contributes to enabling data portability. In this context, it plays a significant role in exporting stored data in JSON format, promoting data portability. Indexed Database API: https://www.w3.org/TR/IndexedDB/'
'Section 7.3.3 of the specification addresses language. It is mentioned that the "language" parameter may be specified by the originator to convey information about the natural language used inside the message. If it is specified, it must contain a language identifier as defined in BCP 47 [RFC4646]. Syslog Protocol Language: https://datatracker.ietf.org/doc/html/rfc5424#section-7.3.3 IETF RFC4646: https://datatracker.ietf.org/doc/html/rfc4646'
SMP is maintained by OASIS which is an international community developing open standards. The specification: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505000
'The modularity of ODRL allows the implementation to the specific needs of a particular application or use case. Users can focus on the aspects of the standard that are most relevant to their digital rights management requirements. This flexibility is beneficial because different industries and applications may have diverse needs when it comes to expressing and managing digital rights. An example of this extension is the work done within the scope of SERAMIS project, which is a GDPR validation tool that uses an ODRL extended model as basis for the validation. SERAMIS: https://cordis.europa.eu/docs/projects/cnect/2/612052/080/deliverables/001-D55v4GDPR.pdf W3C specification: https://www.w3.org/TR/odrl-vocab/#vocab-core '
'The purpose of ESI/REM is not related to the visibility of administrative procedures, rules data and services, therefore it does not promote or hinder it. ETSI EN 319 532-3 reference: https://www.etsi.org/deliver/etsi_en/319500_319599/31953203/01.02.01_60/en_31953203v010201p.pdf'
'According to section 4.4 of the documentation, ETSI TS 119 511 provides an interface between users and preservation services, however, specific provisions are fully achieved if it is combined with its companion documents ETS TS 119 512 therefore, enabling the visibility of administrative procedures, rules and services if combined with other specifications. ETSI TS 119 511 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119511/01.01.01_60/ts_119511v010101p.pdf TR-ESOR Preservation of Evidence of Cryptographically Signed Document: https://www.bsi.bund.de/SharedDocs/Downloads/DE/BSI/Publikationen/TechnischeRichtlinien/TR03125/BSI_TR_03125_Anlage_PEPT_V1_2_1_higher.html'
'ISO/IEC 27001 defines security aspects for information in IT systems, it is a key element when designing business processes and the requirements that the system and the organisation will need to meet. ISO/IEC 27001 reference website: https://www.iso.org/standard/54534.html'
'The simplification of the delivery of public services is not on how they are deliver, it starts with the analysis and design phase of these services. There is where EIRA is meant to focus and support the simplification of European public services. The holistic approach of the specification ensures that there is a translation between legal requirements into the technical implementations. By providing different perspectives to different aspects such how services interact between them, how information is transferred, how user can send/receive information, EIRA can help public administrations to develop services that are completely aligned with their needs and expectations, including delivery channels that are more appropriate given the conditions of each Public Administration. EIRA reference: https://interoperable-europe.ec.europa.eu/collection/european-interoperability-reference-architecture-eira /solution/eira/release/610 EIRA Github Repository: https://github.com/CarTool-EC/EIRA'
'The purpose of the specification is not related to e-accessibility. Therefore, this criterion does not apply. ETSI EN 319 532-3 reference: https://www.etsi.org/deliver/etsi_en/319500_319599/31953203/01.02.01_60/en_31953203v010201p.pdf'
"XHTML has been used by the EU comission in the context of the publication of regulations (EURLEX), in this sense the proposal for a regulation on reduction of legal and administrative obstacles in a cross border context is a prime example of it's use. XHTML implementation by Eur-lex: https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:52018PC0373&from=EN"
'ShEx is built around RDF and is highly dependent from it since its purpose is to validate RDF graphs. Nonetheless, it has many known implementations that range through a variety of business domains allowing for RDF graphs validation across business domains. ShEx primer document: https://shexspec.github.io/primer/ ShEx Community Group: https://www.w3.org/community/shex/ ShEx Github: https://github.com/shexSpec/spec/issues'
'The NFVI ensures the deployment and execution of Virtualised Network Functions (VNFs). The specification spans across multiple locations where data centres are operating. Connectivity between these locations is considered part of the specification. NFVI Deliver, Infrastructure Overview: https://www.etsi.org/deliver/etsi_gs/NFV-INF/001_099/001/01.01.01_60/'
'Registered Organization Vocabulary facilitates organisational interoperability agreements primarily by providing a common vocabulary and a consistent semantic framework for describing legally registered organisations. This enables different systems and organisations, particularly business registers, to understand and exchange information about these entities in a more standardised way. Registered Organization Vocabulary specification reference: https://www.w3.org/TR/vocab-regorg/'
'The purpose of TS 119 614-1 is not related to ensuring the protection of personal data managed by public administrations. Therefore, this criterion is not applicable to the specification. ETSI TS 119 614-1 reference: https://www.etsi.org/deliver/etsi_ts/119600_119699/11961401/01.01.01_60/ts_11961401v010101p.pdf'
Data on the Web Best Practices gives some advice on how to publish data on the web. It encourages and enables the continued expansion of the Web as a medium for the exchange of data. It does not directly foster the visibility of data, but the usage of this best practice can help to implement solutions to foster the visibility of data and services of public administration. Data on the Web Best Practices W3C: https://www.w3.org/TR/dwbp/
The specification is aimed to participate in the evaluation of access policies, participating in authentication processes that can ease the secure and trustworthy exchange of data. An example of this fact is the European project SEMIRAMIS, a pilot infrastructure to provide e-services with the required underlying secure authentication SEMIRAMIS project: https://joinup.ec.europa.eu/solution/semiramis/about
'As defined on the OASIS Technical Committee (TC), only TC members are involved in the development of the UBL specification. External contribution to this committee is possible through open channels. UBL OASIS Technical Committee reference: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ubl UBL v2.3: http://docs.oasis-open.org/ubl/os-UBL-2.3/UBL-2.3.html'
'The ISO 639-2 code suite was developed to be used by libraries, information services and publishers to indicate language in the exchange of information, especially in computerised systems. It can foster data portability in the context of a an interoperability solution (e.g., the ADMS from the ISA Programme). ISO 369-2 FAQs: https://www.loc.gov/standards/iso639-2/faq.html#5 ADMS ISA Programme reference: https://joinup.ec.europa.eu/sites/default/files/document/2013-06/Case%20Study%20-%20%20How%20to%20describe%20semantic%20interoperability%20assets%20in%20an%20ADMS%20compliant%20way%20-%20v1.06.pdf'
'The specifications first version was released in 2012, since then, it has undergone one major release, being now the version 2.0.0 In the TGF OASIS technical committee, there can be found information about the change management and release management processes. TGF Technical Committee: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=tgf'
'The purpose of iCalendar is not related to e-accessibility. Therefore this criterion is considered not applicable to the specification. iCalendar specification: https://www.rfc-editor.org/rfc/rfc5545'
'AMQP specification can be used in a multilingual context. AMQP uses IETF language tags. These tags are used to specify the language of informational text, including connection, session, and link error descriptions but implementations should understand at least the en-US language tag. (Refer to section 2.8.12 IETF Language Tag) OASIS AMQP Reference: http://docs.oasis-open.org/amqp/core/v1.0/amqp-core-complete-v1.0.pdf'
As a protocol for data exchange, FTP allows the provision of data using an endpoint and therefore makes available interfaces of public administrations internal information systems. An example of implementation support this fact would be the Flemish initiative MAGDA. This initiative provides a platform that allows the different administrations to reuse the information contained within their registries. FTP has been selected by MAGDA to enable data exchange between the different administrations. See: https://joinup.ec.europa.eu/solution/magda-platform/about https://cordis.europa.eu/project/rcn/198414/factsheet/en
'One of the key features of LDAP is that it enables a centralized managment of directory information, and the administrators can mantain consistency and control of the data across the organization. Moreover, there are mechanisms that guarantee the confidentiality of data, like SASL or TLS. LDAP Wirex reference: https://wirexsystems.com/resource/protocols/ldap TLS cloudfare reference: https://www.cloudflare.com/learning/ssl/transport-layer-security-tls/ SASL gnu reference: https://www.gnu.org/software/gsasl/manual/gsasl.html#SASL-Overview'
'The purpose of NFVI is not related to the delivery of multilingual public services. Therefore, this criterion is not applicable to this specification. NFVI Deliver, Infrastructure Overview section 4: https://www.etsi.org/deliver/etsi_gs/NFV-INF/001_099/001/01.01.01_60/ '
'Although no evidence of BFO facilitating digital service delivery channels, the specification could enable the migration of services and data across various platforms, making it an efficient and flexible solution for digital services. BFO reference: https://www.iso.org/standard/74572.html'
'UDDI is included in 8 national catalogues of recommended specifications. They belong to Bulgaria, Cyprus, France, Germany, Greece, Malta, Netherlands, and Spain. The National Interoperability Framework (NIF) of Spain and Netherlands are fully aligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. NIFO factsheets: https://joinup.ec.europa.eu/collection/national-interoperability-framework-observatory-nifo/nifo-factsheets National catalogue Spain: https://administracionelectronica.gob.es/pae_Home/pae_Estrategias/pae_Interoperabilidad_Inicio /pae_Normas_tecnicas_de_interoperabilidad.html#CATALOGOESTANDARES National catalogue Netherlands: https://www.forumstandaardisatie.nl/open-standaarden '
'This specifiation is the foundation for many different innovative solutions. For instance, syslog-ng, developed byBalabit IT Security Ltd, is a log management solution that improves the performance Security Information and Event Management (SIEM) solution by reducing the amount and improving the quality of data feeding the SIEM for Unix and Unix-like systems. It is widely adopted by many applications and devices, facilitating interoperability. Syslog-ng: https://www.syslog-ng.com/'
"The Registered Organization Vocabulary is not included in any Member States' catalogues of recommended specifications. Registered Organization Vocabulary reference: https://www.w3.org/TR/vocab-regorg/ CAMSS list of standards: https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-andspecifications-camss/camss-list-standards NIFO factsheets: https://interoperable-europe.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public-administration-factsheets-2024"
'At the moment of performing this assessment, Linked Open Data portals are innovative solutions adopted by public administrations all around Europe. DCAT-AP fosters the implementation of Five-Star Linked Open Data by allowing users to discover interlinked information from other portals. European Data Portal: http://data.europa.eu/euodp/en/home Joint research center data catolgue: http://data.jrc.ec.europa.eu/ DCAT-AP - a key for European data publishers to reach the data consumers and create a European open data ecosystem: https://ec.europa.eu/isa2/dcat-ap-key-european-data-publishers-reach-data-consumers-and-create-european-open-data-ecosystem_en/'
'As it happens with all the e-Government Vocabularies, SEMIC is the responsible for the maintenance of the development. SEMIC in Interoperable Europe Portal: https://interoperable-europe.ec.europa.eu/collection/semic-support-centre Core Location Vocabulary: https://interoperable-europe.ec.europa.eu/collection/semic-support-centre/solution/core-location-vocabulary/release/100'
'Since 1990, HTTP has been developed based on practical experience and extensive feedback from developers and organisations, demonstrating significant market acceptance. Major version releases, including HTTP/2 and HTTP/3, have been developed, each offering specific benefits and limitations depending on the context of use. All three major versions relies on the semantics defined by the original specification, and implementations are expected to choose the most appropriate transport and messaging syntax for their particular needs. HTTP /1.1 RFC 2616 Reference: https://www.rfc-editor.org/rfc/rfc2616.html HTTP/1.1: Semantics, RFC 9110 Reference: https://www.rfc-editor.org/rfc/rfc9110.html'
'JSON is included in 9 national catalogues of recommended specifications. They belong to Cyprus, Denmark, Finland, France, Iceland, Malta, The Netherlands, Slovakia and Slovenia. The National Interoperability Framework (NIF) of France and The Netherlands is fully alignes with at least 2 out of 3 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. CAMSS List of standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards NIFO Factsheets: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public-administration-factsheets-2022 National Catalogue of France: https://www.numerique.gouv.fr/uploads/Referentiel_General_Interoperabilite_V2.pdf'
'While the purpose of this specification is not directly related to restricting access to information/data, the Catalog Protocol part of the Dataspace Protocol defines how a Catalog is requested from a Catalog Service by a Consumer using an abstract message exchange format. Details for including authorisation tokens can be found in the protocol binding, e.g., Catalog HTTPS Binding. IDSA Dataspace Protocol Catalog HTTPS Binding: https://docs.internationaldataspaces.org/ids-knowledgebase/v/dataspace-protocol/catalog/catalog.binding.https'
After checking the different standard catalogues at supra-national level, there is no evidence of the inclusion of XAdES (ISO 14533-2:2012) within any European catalogue of standards. ICT technical specifications: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en CEN search tool catalogue: https://standards.cen.eu/dyn/www/f?p=CENWEB:105::RESET:::: CENELEC search tool catalogue: https://www.cenelec.eu/dyn/www/f?p=104:107:0::::FSP_LANG_ID:25
'Although designed for use in business supply chains it can be (and has been) adapted for other contexts of use. This is because all the business document constructs in a UBL are drawn from a single library of reusable components. Therefore, UBL can be used across business domains. UBL v2.3 reference: http://docs.oasis-open.org/ubl/os-UBL-2.3/UBL-2.3.html Developer community OASIS. UBL functionalities: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ubl#functionality'
'CSV is a commonly used format for data exchange. It allows to provide data in a simple way. Moreover, as is structured data and non-proprietary format it eases data consumption by different stakeholders. An example of initiative relaying on CSV to provide data to users is ESCO, that allows the download data sets in CSV format. It can also serve as an example the use of CSV in the Kohesio inititative. Kohesio Initiative: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/kohesio-validator/specification CSV EC Reference:: https://ec.europa.eu/esco/portal/escopedia/Comma-separated_values__40_CSV_41_#ESCO_data_in_CSV_files CSV reference: https://datatracker.ietf.org/doc/html/rfc4180'
'REST is an architecture style that defines how different systems should interact. REST APIs generate a way of accessing web services in a simple and flexible way without having any processing thus allowing greater interoperability between clients and servers. The french government website data.gouv.fr which hosts the french governments datasets is built under the REST architectural style. REST reference: https://restfulapi.net/ Data.gouv.fr reference: https://doc.data.gouv.fr/api/intro/'
After carrying out an exhaustive research on this topic, no evidence has been found regarding the existence of a formal agreement between European public services providers involving the implementation of eDelivery SMP 1.10. However, the specification appears included within the eDelivery stack in the EU eGovernment Action Plan 2016-2020. The European communication coming from European Parliament, the Council, the European Economic and Social Committee and the Committee of the Regions aims to propose recommendations and actions to be done in order to enhance the interoperability across borders. See: https://ec.europa.eu/isa2/sites/isa/files/docs/publications/eu-egovernment-action-plan-2016-2020_en.pdf
The purpose of CAdES is not related to the implementation of the once-only principle. Therefore, this criterion does not apply to this specification. CAdES ISO reference: https://www.iso.org/standard/64756.html CAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/101700_101799/101733/02.01.01_60/ts_101733v020101p.pdf
"EN 303 645 is associated to the consumer IoT device and the data security domain. EN 303 645 is a comprehensive, single-purpose specification that manufacturers and IoT stakeholders need in order to meet basic security requirements (see EN 303 645 homepage, 'International alignment and adoption' section). There is no evidence of the use of the specification in the public sector. EN 303 645 homepage, 'International alignment and adoption' section: https://www.etsi.org/technologies/consumer-iot-security"
The purpose of CAdES is not related to the visibility of administrative information, data or services. Therefore, this criterion is not applicable to this specification. CAdES ISO reference: https://www.iso.org/standard/64756.html CAdES ETSI reference: https://www.etsi.org/deliver/etsi_ts/101700_101799/101733/02.01.01_60/ts_101733v020101p.pdf
'Secure processing of data can be provided by DNS adding the DNS Security Extensions (DNSSEC), which is, in fact, almost a mandatory extension between major stakeholders. Processing of data is secured by the encrytion under which the domain is protected provided by DNSSEC or other extensions addressing security issues. Resource Records for the DNS Security Extensions: https://datatracker.ietf.org/doc/html/rfc4034 Extension Mechanisms for DNS: https://datatracker.ietf.org/doc/html/rfc6891 DNS IETF reference: https://datatracker.ietf.org/doc/html/rfc8499'
'The purpose of ADMS is not related to organisational interoperability. Therefore, this criterion is not applicable to the specification. ADMS Specification W3C: https://www.w3.org/TR/vocab-adms/'
"Both cloud data interoperability and portability contain a semantic section in the implementation's release. Therefore, it can be considered that the specification is involved in fostering the comprehensibility of Public Administrations data as well as relevant data produced for the decision-making process. ISO 19941: https://www.iso.org/obp/ui/en/#iso:std:iso-iec:19941:ed-1:v1:en"
'iCalendar could allow third-party standards to protect data by applying access restrictions. The protocol for exchanging calendaring and scheduling data should prevent possible unwanted access to information. iCalendar Security Considerations: https://www.rfc-editor.org/rfc/rfc5545#section-7'
W3C has a defined and publicly available Process for the Development and approval process of the specification as a recommended standard. Also, a clear Release Notes tracking the changes of the different versions is archived. See: W3C Process document https://www.w3.org/2018/Process-20180201/#Policies
'WSDL is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). Specifically, WSDL can define the interoperability aspects of the "Machine to machine interface" ABB of the EIRA "Technical View". EIRA Library Of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis'
2 Member States are recommending SAML 2.0 in their ICT National Catalogues. See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
The specification is independent of any technology and PNG images can be readable in any platform. PNG W3C reference: https://www.w3.org/TR/PNG/
'Internet Protocol Security (IPsec), a protocol providing a network layer security (authentication and encryption), is included as a mandatory feature in the IPv6 specification. IPv6 is more secure than the alternative Internet protocol, IPv4, its previous version. IPsec IETF reference: https://tools.ietf.org/html/rfc2460'
'ISO 639-2 is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, ISO 639-2 can define the interoperability aspects of the Data Set ABB of the EIRA Semantic View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/v110'
By describing web services in terms of functionalities and accessibility to them, WSDL fosters the visibility of administration web services for the reusing of existing applications by other administrations and stakeholders.
'Some aspects of LDES contribute to the authenticity of the data such as the use of linked data principles, and above all, the "immutable event streams" that allows transparent registration and traceability of the data. LDES specification: https://joinup.ec.europa.eu/collection/semic-support-centre/linked-data-event-streams-ldes'
'OData is a recommendation and protocol for data exchange. Therefore, the specification can contribute to enabling the secure processing of data. OData reference: http://docs.oasis-open.org/odata/odata/v4.0/odata-v4.0-part1-protocol.html'
'IEEE Std 802.3-2022 is a flexible and adaptable standard that supports new features and capabilities as technology evolves. This is evident in numerous extensions like IEEE 802.3ca and 802.3ch, which introduced higher data rates and support for applications like passive optical networks and automotive Ethernet. IEEE Std 802.3-2022 extensions references: https://standards.ieee.org/beyond-standards/new-ieee-802-3-standards-provide-platforms-for-the-next-ethernet-innovations/ IEEE Std 802.3-2022 Reference: https://ieeexplore.ieee.org/document/9844436'
'The IPsec protocol allows for the encryption of IP packets, making the exchange of information more secure. In addition, encrypting IP packets ensures that all information exchanged by public administrations, or between a public administration and its citizens, is protected and trustworthy. IPsec protocol: https://www.cloudflare.com/learning/network-layer/what-is-ipsec/'
UDDI does not help the availability of interfaces with internal information. In fact, the purpose of the specifications is not related to this action. Despite this, UDDI supports the availability of technical interfaces that may be used to access web services.
As all the IETF specifications, DNS is licensed on a Royalty-free basis according to the documents “Rights Contributors Provide to the IETF Trust” and ”IETF Trust's Legal Provisions Relating to IETF Documents” See: https://trustee.ietf.org/
The purpose of LegalRuleML is not related to e-accessibility. Therefore, this criterion is not applicable to this specification. LegalRuleML reference: http://docs.oasis-open.org/legalruleml/legalruleml-core-spec/v1.0/legalruleml-core-spec-v1.0.html
The purpose of HTTPS is not related in any way to e-accessibility. Therefore, this criterion is not applicable to the specification.
'The CSV specification itself does not provide any built-in means for restricting access to information or data. While the CSV specification does not provide these features directly, they can be implemented in conjunction with the systems or applications that handle CSV files to ensure proper access control and data protection. CSV reference: https://datatracker.ietf.org/doc/html/rfc4180'
"The syslog protocol is not included in any Member States' catalogues of recommended specifications. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards "
'DPV can be mapped to the Eira Library of Interoperability Specifications (ELIS) in the "Privacy Policy", "Controlled Vocabulary", "Data", "Data Mapping Catalogue","Metadata", "Open Data", "Hash Code", "Linked Open Data", "Linked Data in the Semantic View", "Data Model" and "Ontology" Semantic View as well as the "Privacy Framework" of the Organisational View. DPV specification: https://w3c.github.io/dpv/primer/'
The purpose of CPOV is not related to long term preservation of electronic records. Therefore, this criterion is considered not applicable to this specification. CPOV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-public-organisation-vocabulary
'The specification is not recomended by any European Member State. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards'
"TOSCA may simplify the delivery of ditigal public services, but up to date there is no evidence of any specific application in public administrations at European level. It seems that there is still work to do for increasing TOSCA's capabilities in terms of service deployments (see EUBRA-BIGSEA project reference), and this may include public administrations to the extent that there is no evidence of TOSCA as a leading force in European public services. TOSCA reference: https://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.3/os/TOSCA-Simple-Profile-YAML-v1.3-os.html EUBRA-BIGSEA project reference: http://www.eubra-bigsea.eu/standards"
PNG could help understand the data of public administration by adding PNG image. In this sense, the specification can play an active role on the representation of the information in an easier visual way. This fact can consider PNG to foster the comprehensibility of administrative rules and data. PNG W3C reference: https://www.w3.org/TR/PNG/ PNG ISO reference: https://www.iso.org/standard/29581.html
At the time of elaborating this assessment, this specification is not included in any EIRA ABB in the last version of the EIRA Library Of Interoperability Specifications (ELIS). However, it has been associated to "Security Framework" of the Organisational view for the on-going version that is going to be published in May 2021. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis EIRA Library of Interoperability Specifications v1.0.1 (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/v101-0
'The rules on European standardisation allow the European Commission to identify information and communication technology (ICT) technical specifications - that are not national, European or international standards - to be eligible for referencing in public procurement. This allows public authorities to make use of the full range of specifications when buying IT hardware, software and services, allowing for more competition in the field and reducing the risk of lock-in to proprietary systems. After being evaluated compliant with the regulation on standardisation 1025/2012, HTTPS has been identified by Commission Implementing Decision and included in the European list of ICT Standards for e-procurement. European ICT Technical specifications: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en '
'GITB TDL enables digital service delivery channels by verifying that the requirement of a given specification are met, as well as verifying that two or more parties can interact as expected. GITB TDL reference: https://www.itb.ec.europa.eu/docs/tdl/latest/introduction/index.html#what-is-the-gitb-tdl'
DCAT is a domain-agnostic specification that can be reused for the description of any dataset independently from the business domain addressed. For DCAT users having business-specific requirements, the specification is generally extended (e.g. StatDCAT-AP for statistical data)
"After carrying out information retrieval, the Spanish CERES (Certification Authority Portal) is using OCSP proving its efficiency. All the certificate validation services from the Spanish Certification Authorities are using OCSP. CERES' OCSP reference: https://www.cert.fnmt.es/en/catalogo-de-servicios/validacion-de-certificados/ocsp"
'OData offers a way to both break down data silos and increase the shared value of data. The specification contributes to creating an ecosystem where data consumers and producers can interoperate more than ever, allowing more applications to make sense of a broader set of data. In this sense, the specification promotes comprehensibility, for example through the OData data model. However, no evidence was found in terms of promoting and supporting the comprehensibility of European public services. Interoperable Europe Portal OASIS Open Data Protocol reference: https://interoperable-europe.ec.europa.eu/collection/ict-standards-procurement/solution/odp-oasis-open-data-protocol-odata-tc'
'There are existing documentation and studies assessing the effectiveness of SHACL. In "SHACL-ACL: Access Control with SHACL", the SHACL effectiveness is assessed. In this study, is shown how SHACL can be utilised in a policy-based access control approach. "SHACL-ACL: Access Control with SHACL" study: https://link.springer.com/chapter/10.1007/978-3-031-43458-7_4 SHACL W3C reference: https://www.w3.org/TR/shacl/'
"Syslog is designed to be flexible, and partial implementations are possible based on the specific needs and requirements of a system or application. Implementer Guidelines in the protocol (Appendix A) show the extent to which syslog allows partial implementations depends on the features and components being implemented or omitted. It's important to note that while partial implementations are possible, interoperability may be impacted if the syslog implementation diverges significantly from the standard. Syslog Protocol: https://datatracker.ietf.org/doc/html/rfc5424"
'SAML 2.0 is a modular and extensive specification that accommodates a variety of use cases across diverse domains. The specification consists of various components and flows, meaning that implementers can choose to support certain parts of the standard based on their needs. SAML 2.0 Reference: http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-tech-overview-2.0.html'
'Section 6.4 of the specification explains that in many instances data confidentiality is afforded by the application of encryption to content, although techniques such as path segregation (e.g. VPNs) and the use of secure enclaves in data processing are other measures that can be applied to give assurance of data confidentiality. ETSI Context Information Management (CIM); Security and Privacy: https://www.etsi.org/deliver/etsi_gr/CIM/001_099/007/01.01.02_60/gr_cim007v010102p.pdf'
'At the moment of performing the assessment, the specification is not widespread known and used. However, it is a national initiative from Italy, that can have a great impact in the current European interoperability environment. Currently, the specification has been used in Italy to describe the software created in the country. This has permitted the creation of a national catalogue of software by crawling the content of the publiccode.yaml available within the software repositories. The standard is also applied in opencode.de, Germany’s registry for open-source software in public administration. Publiccode.yaml documentation: https://docs.italia.it/italia/developers-italia/publiccodeyml-en/en/master/index.html Italian National Software Catalogue: https://developers.italia.it/ Open CoDE: https://opencode.de/en'
'NFVI is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, NFVI can define the interoperability aspects of the Hosting Facility, Hosting Service, Private Hosting Facility and Public Hosting Facility ABBs of the EIRA Technical View. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/v110'
'The purpose of the EN 303 645 specification is not related to data portability. Therefore, this criterion does not apply to this specification. EN 303 645 reference: https://www.etsi.org/deliver/etsi_en/303600_303699/303645/02.01.01_60/en_303645v020101p.pdf'
'HTTPS is domain-agnostic, meaning it can be used with any domain or website. It is not specific to any particular domain or type of website. HTTPS can be implemented on various types of domains, including government websites, e-commerce platforms, social media platforms, news websites, and more. HTTPS specification: https://tools.ietf.org/html/rfc2818'
'One of the principles which is considered by the W3C working group is that DQV should be easy to map to as well as to re-use and extend. Therefore, DQV could facilitate organisational interoperability agreements. Interoperability reference: https://www.semantic-web-journal.net/system/files/swj2079.pdf'
'The efficiency of the syslog protocol is often assessed based on several factors that relate to its performance, scalability, and practical implementation. For instance, a 2020-paper for the Institute of Electrical and Electronics Engineering (IEEE) talks about efficient and robust syslog parsing for network devices in datacenter networks. Syslog usefulnes in this matter can be used as a testimony of its efficiency. Efficient and Robust Syslog Parsing for Network Devices in Datacenter Networks: https://ieeexplore.ieee.org /abstract/document/8988255'
After checking the different standard catalogues at supra-national level, there is no evidence of the inclusion of IPv4 within any European catalogue of standards.
'This specification can enhance cloud computing services that support the development and deployment of e-government services, making it easier for citizens to access and interact with government services online. This can lead to streamlined processes, reduced paperwork, and improved citizen satisfaction. Also, it facilitates the migration of services and data across various cloud environments, making it an efficient and flexible solution for digital services. ISO 19941: https://www.iso.org/obp/ui/en/#iso:std:iso-iec:19941:ed-1:v1:en'
At the moment of performing the assessment, the specification is not mapped with any EIRA ABBs and therefore it is not included in the ELIS v1.0.1. However, it has been associated with Legal ABBs from EIRA Legal View and is being included in the on-going version of the ELIS that will be released in May 2021. The ABBs included are: Legal Act, Binding Instrument, Legislation On Data Information and Knowledge Exchange and Non-Binding Instrument. ELIS Solution: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis ELIS v1.0.1: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/v101-0
'The purpose of SOAP 1.2 is not related to the long-term preservation of electronic records and other kinds of information. Therefore, this criterion is not applicable to the specification. SOAP Reference: https://www.w3.org/TR/soap12/ '
'The AES specification is designed to be adaptable and extended in the future. This means that future versions of the official AES standard could introduce changes or additions to the allowed values for some of its key parameters. For example, they might permit modify technical settings. However, at this moment the specification cannot be extended, and if it is modified, it can cause a loose of security capabilities. Computer Security Objects Register (CSOR) reference: https://csrc.nist.gov/projects/computer-security-objects-register AES Standard Reference: https://csrc.nist.gov/pubs/fips/197/final'
After searching in the different official European websites, there is no evidence of any cross-border project that use PDF/A nor explicit agreements involving the usage of the specification.
The purpose of FTPS is not related to long term preservation of electronic records. Therefore, this criterion is considered not applicable to this specification. FTPS IETF reference: https://tools.ietf.org/html/rfc4217
WSDL is a business agnostic specification that can be implemented in any domain requiring web services description and access.
'The purpose of EuroVoc is not related to e-accessibility. Therefore, this criterion is considered not applicable to this specification. EuroVoc: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource /dataset/eurovoc'
JSON is a specification used for data exchange between different platforms, this fact facilitates the visibility and comprehensibility of administration's data. Moreover, it eases the communication between administrations enhancing the decision-making process.
'The specification does not support the implementation of data accuracy mechanisms as SOAP does not focus on the content of the message. SOAP Reference, section 7 Security Considerations: https://www.w3.org/TR/soap12/#secconsiderations'
'Participation and contribution in the development of the OASIS AMQP Technical Committee is open to all interested stakeholders. Stakeholders can actively contribute by joining the AMQP TC, providing input and offering feedback during public reviews of released specifications. TC members engage in committee work via the AMQP mailing list, which requires TC membership to post. The OASIS AMQP Technical Committee operates under OASIS Open, an organisation that promotes collaboration among individuals, organisations, and governments to address technical challenges through open standards and is open to all interested stakeholders. AMQP OASIS Technical Committee reference: https://groups.oasis-open.org/communities/tc-community-home2?CommunityKey=969c2da1-55c4-4bba-92d2-018dc7d3efe9 AMQP OASIS TC, Charter reference: https://www.oasis-open.org/committees/amqp/charter.php OASIS Open Reference: https://www.oasis-open.org/ AMQP working groups: https://www.amqp.org/ OASIS AMQP Reference: http://docs.oasis-open.org/amqp/core/v1.0/amqp-core-complete-v1.0.pdf'
'Currently Microsoft has provided some insights regarding the specification effectiveness, but while it is implemented with other specifications, in this case via Microsoft network drivers. OSI and Microsoft https://learn.microsoft.com/en-us/windows-hardware/drivers/network/windows-network-architecture-and-the-osi-model OSI reference https://www.iso.org/standard/20269.html'
'Stakeholders have several opportunities to contribute to the development of these frameworks and specifications. The ISA² program regularly organizes public consultations and workshops to gather feedback and suggestions from stakeholders across Europe. No public consultation or review have been identified, but the OP opens up different channels to participate in the development and adoption of its specifications. AKN4EU reference: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/akn4eu'
'Data portability is one of the key attributes of the specification.'
SHACL does not defines a cross-sector reusable data model. SHACL is a web standard whose only purpose is RDF data graph validation.
'There are two Member States recommending ISO 3166-1 in their ICT National Catalogues. These Member States are Malta and the Netherlands. National catalogue Malta: https://mccaa.org.mt/Section/Content?contentId=1243 National catalogue The Netherlands: https://www.forumstandaardisatie.nl/open-standaarden/lijst'
'There are many communities that share their data and results of their implementations of HTTP Cookies. Some examples of such communities can be found in the following links. Stack overflow forum: https://stackoverflow.com/questions/12373738/how-do-i-set-a-cookie-on-httpclients-httprequestmessage Microsoft community: https://powerusers.microsoft.com/t5/General-Power-Automate/Passing-Cookies-Between-HTTP-Actions/td-p/69761'
'The Advanced Encryption Standard is developed by a non-European organisation. Therefore, the specification cannot be considered a European standard. AES Standard Reference: https://csrc.nist.gov/pubs/fips/197/final'
The version being assessed is not included in the ICT technical specification in itself, however the version 1.0 of the specification was already identified and included within this list of specifications that are compliant with the standardisation regulation for being used in eProcurement. ICT technical specifications: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en
'The purpose of OSI is not related to data processing accuracy. Therefore, this criterion is not applicable to the specification. OSI reference https://www.iso.org/standard/20269.html'
'Syslog protocol is developed by IETF, a standard development organisation based in the US. Moreover, the syslog protocol specification does not appear in any of the main European standard development bodies, therefore, the specification is not a European standard. Syslog Protocol: https://datatracker.ietf.org/doc/html/rfc5424'
'The Core Location Vocabulary specification can be found in the Interoperable Europe Portal. In this Portal, people can discuss about the specification, and the maintainers can publish all of the releases available. In addition, the namespace of the vocabulary is given by the W3C, promoting the sharing of data and results regarding the specification. Finally, the specification can also be found in the Publications Office of the European Union (PO). Core Location Vocabulary PO: https://op.europa.eu/en/web/eu-vocabularies/corevocs#:~:text=The%20Core%20Location%20Vocabulary%20%28latest%20version%29%20is%20a,Vocabulary%20is%20aligned%20with%20the%20INSPIRE%20data%20specifications. Core Location Vocabulary Interoperable Europe Portal: https://interoperable-europe.ec.europa.eu/collection/semic-support-centre/solution/core-location-vocabulary Core Location Vocabulary: https://interoperable-europe.ec.europa.eu/collection/semic-support-centre/solution/core-location-vocabulary/release/100'
'The Advanced Encryption Standard can be implemented in any software, firmware, hardware or any combination of them. Therefore, the standard is platform agnostic. AES Standard Reference: https://csrc.nist.gov/pubs/fips/197/final'
"HTTP Cookies enable web servers to store stateful information on the user's device or to track the user's browsing activity. They can also be used to save for subsequent use information that the user previously entered into form fields, such as names, addresses, passwords, and payment card numbers. Therefore, HTTP Cookies can facilitate data portability having a positive impact in interoperability. HTTP Cookies reference: https://datatracker.ietf.org/doc/html/rfc6265#section-5.2 "
PAdES Baseline profile provides the main requirements to ensure the correct use and exchange of signed data in the context of the European Internal Market. Furthermore, the conformance levels included in this profile of PAdES have the objective of ensuring the trustworthy data exchange between public administrations and stakeholders.
The purpose of IPSec is not related to long term preservation of electronic records. Therefore this criterion is considered not applicable to this specification. See: https://tools.ietf.org/html/rfc4301
CSV makes sure content is available on the web, structures data and makes it usable in a non-proprietary open format. So it can be said that CSV facilitates the reduction of administrative burdens when making it usable and open.
'There are existing documentation and studies assessing the effectiveness of IPv6. The "IPv6 performance - and how to test it" study, makes an assessment for measure the efectiveness of IPv6 using scores for city (Frankfurt in this case), region (Europe) and Global. Moreover, the assessment almost includes other themes such as connectivity. "IPv6 performance - and how to test it" reference: https://www.swissipv6council.ch/sites/default/files/images/sonar_article_02-2013-final.pdf'
'DPV is based on European Union legislative requirements such as the GDPR, which aims to harmonize data privacy laws across Europe. Therefore, public administrations benefit from the definition of a data model based on this regulation given that it promotes the transparency of the procedures and personal data handled by public administrations. DPV specification: https://w3c.github.io/dpv/dpv/ DPV primer document: https://w3c.github.io/dpv/primer/#introduction GDPR reference: https://gdpr.eu/'
'AMQP does not scope comprehensibly administrative procedures, rules data, and services. Therefore this criterion is not applicable. OASIS AMQP Reference: http://docs.oasis-open.org/amqp/core/v1.0/amqp-core-complete-v1.0.pdf'
'Assessments of the efficiency of this asssessment primarily involve evaluating the performance, scalability, and practicality of implementations. A 2019-paper about Integrated Security Management Systems mentions ISO/IEC 7498:1 as one of the key standards analysed to suggest an approach to the development of integrated security and safety management system struc-ture considering threats of intrusion into physical, information and signal spaces, demonstrating how efficient the specification can be. Integrated Security Management System for Enterprises in Industry 4.0: https://www.researchgate.net/publication/336027597_Integrated_Security_Management_System_for_Enterprises_in_Industry_40'
There are no competitors for RPKI since no standards with overlapping functional scope have been found. No interoperability issues with the implementation of existing European or international standards exist.
'The purpose of the specification is not related to supporting the implementation of European public services, therefore it does not promote or hinder it. ETSI EN 319 422 reference: https://www.etsi.org/deliver/etsi_en/319400_319499/319422/01.01.01_60/en_319422v010101p.pdf'
"XHTML is available for implementation and use for free on the W3C's webpage to cover any user needs. However, since XHTML is superseded in favour of HTML5, the coverage of business domains is larger when using HTML5. XHTML W3C reference: https://www.w3.org/TR/xhtml1/ HTML5 W3C Reference: https://html.spec.whatwg.org/multipage/"
IPSec is not related to interfaces. Therefore, this criterion is not applicable to this specification. See: https://ec.europa.eu/isa2/solutions/testa_en
'The IPv6 specification supports digital service delivery channels by providing a much larger address space than IPv4, which facilitates the connection of a vast number of devices to the internet. This expanded address space is crucial for the Internet of Things (IoT) and other services that require unique IP addresses for each device. IPv6 IETF: https://www.rfc-editor.org/rfc/rfc2460'
IPv6 as a protocol with objective of enhancing communications over a computer network, allows the scalability of systems. Moreover, the European Union promotes the usage of IPv6 and the public administration are able to reuse it. "MS as for instance Germany could bring strong support to the deployment of IPv6 within the European public administrations." Source: https://ec.europa.eu/isa2/sites/isa/files/ipv6_framework_for_european_governments_0.pdf
The purpose of the specification is not related to the long-term preservation of electronic records. Therefore, this criterion does not apply to this specification. W3C specification reference: https://www.w3.org/TR/odrl-vocab/#vocab-core
'Syslog itself does not provide a built-in access control mechanism. However, access control mechanisms can be implemented at various levels to restrict access to syslog-related resources. Syslog Protocol: https://datatracker.ietf.org/doc/html/rfc5424'
'The ebXML specification is assessed and discussed in various forums and across the Internet. For example, the ebXML Forum News discusses the specification. Additionally, there are many papers that explore ebXML and its implementation, such as the "EbXML simplified: a guide to the new standard for global e-commerce" document. ebXML Forum News: https://ebxmlforum.blogspot.com/ "EbXML simplified: a guide to the new standard for global e-commerce" document: https://books.google.es/books?hl=es&lr=&id=y5mwRBUXgAAC&oi=fnd&pg=PR3&dq=ebxml+&ots=yYosABWG9D&sig=wjypDYsboxfGo7abUyoaQFyIBSg&redir_esc=y#v=onepage&q=ebxml&f=false ebXML RegRep OASIS reference: https://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html'
'The purpose of UTF-8 is not related to the implementation of the once-only principle. Therefore this criterion is not applicable specification. UTF-8 specification: https://datatracker.ietf.org/doc/html/rfc3629'
XAdES Baseline Profile is an open standards developed and maintained by ETSI, and it is available for free at ETSI’s webpage for everyone to study or implement. See: https://www.etsi.org/standards
'According to the Tim Berners-Lee 5-star, ISO/IEC 27001 cannot be considered as a facilitator of open data as the standard does not make its content publicly available on the web; therefore, the standard does not facilitate the publication of open data. Berners-Lee website: https://5stardata.info/en/ ISO/IEC 27001 reference website: https://www.iso.org/standard/54534.html'
This document about Data on the Web Best Practices is a business domain agnostic document that can be reused in a cross-domain way. W3C reference: https://www.w3.org/TR/dwbp/
There is no Member State that includes LegalDocML in their national catalogue with The National Interoperability Framework (NIF) aligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'EN 303 645 is a set of security best practices for Internet-connected consumer devices and is intended to support all parties involved in the development and manufacture of consumer IoT devices. The specification is not intended to depend on any particular specification, and therefore is platform-agnostic. EN 303 645 reference: https://www.etsi.org/deliver/etsi_en/303600_303699/303645/02.01.01_60/en_303645v020101p.pdf'
This document does not define a cross-sector reusable data model. The specification provides guidance and tools for the development of public policies and law taking into account a holistic perspective. Betterr Regulation Toolbox reference: https://ec.europa.eu/info/sites/info/files/better-regulation-toolbox_2.pdf
'IPsec is included in the Spanish, French, Malta, Greek catalogue of standards. Spain fully complies with the 3 sections of the EIF according to the NIFO factsheets. NIFO Factsheets Spain: https://administracionelectronica.gob.es/pae_Home/pae_Estrategias/pae_Interoperabilidad_Inicio/pae_Normas_tecnicas_de_interoperabilidad.html#CATALOGOESTANDARES NIFO Factsheets France: https://www.numerique.gouv.fr/uploads/Referentiel_General_Interoperabilite_V2.pdf NIFO Factsheets Greece: http://www.e-gif.gov.gr/portal/pls/portal/docs/1/211041.PDF NIFO Factsheets: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public-administration-factsheets-2021'
'AMQP provides a ubiquitous, secure, and reliable internet protocol for high-speed transactional messaging. AMQP also has been approved as ISO/IEC 19464:2014. A major cloud platform uses AMQP to connect to its cloud IoT hub. INTERNET OF THINGS Reference: https://interoperable-europe.ec.europa.eu/collection/rolling-plan-ict-standardisation/internet-things OASIS AMQP Reference: http://docs.oasis-open.org/amqp/core/v1.0/amqp-core-complete-v1.0.pdf'
'ETSI TS 119 612 has been developed by the European Telecommunication Standards Institute (ETSI), an independent, not-for-profit, standardization organization in the field of information and communications. About ETSI: https://www.etsi.org/about/about-us'
'Such means as enabling the secure exchange of data can be provided as SOAP extensions using the SOAP extensibility mode. The SOAP Messaging Framework does not directly provide any mechanism for dealing with it directly. SOAP Reference, section 7 Security Considerations: https://www.w3.org/TR/soap12/#secconsiderations'
'ISO 3166-1 is a key component in the development of some European cross-border projects and initiatives. It is the case of the INSPIRE (Infrastructure for Spatial Information in the European Community) project which makes use of ISO 3166-1 to ensure the maintenance of spatial data sets and corresponding data services in the EU (see INSPIRE Legislation reference, Directive 2007/2/EC document, Article 14). ISO 3166-1 reference: https://www.iso.org/standard/72482.html INSPIRE reference, Directive 2007/2/EC document, Article 14: https://inspire.ec.europa.eu/inspire-legislation/26'
'The specification provides a common vocabulary, semantics, and a set of interoperability agreements that can be used to enable seamless exchange of data between different systems and applications. AKN4EU reference: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/akn4eu'
'Some main principles of the specification is the Open Consensus Building and International Scope and Participation, where the participation is open to all DCMI community that have any interest or expertise in metadata. DCMI About: https://www.dublincore.org/about/ '
The data and information encoding is a key point in data exchange and use. In addition, the adoption of the specification as an encoding format fosters the data portability and reuse of information between administrations.
Not enough pieces of evidence have been found to answer positively or negatively to this criterion. Moreover, it seems that the purpose of the specification is not related to the delivery. OpenPM2 specification reference: https://op.europa.eu/en/publication-detail/-/publication/ac3e118a-cb6e-11e8-9424-01aa75ed71a1/language-en/format-PDF/source-83307127
'RDF allows for partial implementations in the sense that it allows for the creation and use of incomplete or partial data graphs. RDF primer document: https://www.w3.org/TR/rdf11-primer/'
The Open Digital Rights Language (ODRL) is a policy expression language that provides a flexible and interoperable information model, vocabulary, and encoding mechanisms for representing statements about the usage of content and services. Therefore, by implementing it, administrations can benefit from the common framework for representing the statements of digital public services and the provision of clear information. This is a powerful usage not only for administration-citizens interaction but also to enhance the cooperation between administrations. W3C specification reference: https://www.w3.org/TR/odrl-vocab/#vocab-core
"Assessments of the efficiency of the Dataspace Protocol primarily involve evaluating the performance, scalability, and practicality of implementations. For instance, a 2023-paper for Gaia-X Austria describes the main points to consider when building a dataspace and references for it. IDSA offers a dataspace reference architecture where a comprehensive dataspace protocol defines messages and API-bindings based on DCAT and ODRL, which highlights the specification's efficiency. Building a Dataspace Gaia-X Austria: https://www.gaia-x.at/wp-content/uploads/2023/04/WhitepaperGaiaX.pdf"
'One of the main purpose of the DPV is to model the legal aspects of data portability, in order to link them with more technical aspects of electronic data exchange. DPV suggests mechanisms for the data to be protected, and data transfers in contexts where cross-border exchange is needed. DPV specification: https://w3c.github.io/dpv/primer/'
'The XACML (eXtensible Access Control Markup Language) specification itself does not directly simplify processes or use digital channels for the delivery of European public services. XACML OASIS reference: https://docs.oasis-open.org/xacml/3.0/xacml-3.0-core-spec-os-en.html'
'NUTS was conceived for statistical and decision-making purposes. At the time being the specification can contribute to overcome interoperability barriers and enable the exposure of such interfaces. No evidence was found on this regard; however, in future Regulations, the specification may contribute to the exposure of internal information systems within the GEOSTAT initiative. EUROSTAT reference, NUTS Principles and Characteristics section: https://ec.europa.eu/eurostat/web/nuts/principles-and-characteristics EUROSTAT-GISCO reference, GEOSTAT initiative: https://ec.europa.eu/eurostat/web/gisco/gisco-activities/integrating-statistics-geospatial-information/geostat-initiative'
'No evidences have been found of existing studies or documentation assessing HTTP Cookies in terms of efficiency to justify this criterion. HTTP Cookies reference: https://datatracker.ietf.org/doc/html/rfc6265#section-1'
The purpose of XSLT is not related to the long-term preservation of electronic records and other kinds of information. Therefore, this criterion is not applicable to the specification.
'The main purpose of ETSI TS 119 512 is to provide protocols for trust service providers providing long-term data preservation services of e-signatures and of general data. ETSI TS 119 512 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.02_60/ts_119512v010102p.pdf'
XHTML is an application of XML, it is based on HTML 4, but it uses XML syntax which defines a well-formed and more restrictive data model. It can be used for exchanging data across sectors. XHTML W3C reference: https://www.w3.org/TR/xhtml1/
'The TOSCA Technical Committee provides feature requests to open source projects and results of implementation experience to open source communities; however, not in national platforms. OASIS TOSCA TC reference: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=tosca'
XML is a business domain agnostic specification.
'DIDs are designed to enable individuals and organizations to generate their own identifiers using systems they trust. These new identifiers enable entities to prove control over them by authenticating using cryptographic proofs such as digital signatures. Moreover, the specification also adresses the immutability of data. The more locked down a DID method is, while providing the same set of features, the less it can be manipulated by malicious actors. DIDs cryptographic: https://www.w3.org/TR/did-core/#introduction DIDs immutability: https://www.w3.org/TR/did-core/#immutability'
'IEEE Std 802.3-2022 itself does not provide an access control mechanism since it focuses primarily on the physical and data link layers of Ethernet networks. Access control is typically handled at higher layers of the OSI model. IEEE Std 802.3-2022 Reference: https://ieeexplore.ieee.org/document/9844436'
'Changes to the YAML language itself will be made using a "requests for comments (RFC)" process. The working group is currently engaged in finalising the remaining details of this process, with the intention of having them all resolved in the near future. Despite this, some ways to get involved are reporting typos, mistakes, bugs, discussing ideas and submitting fixes for the build system. Contribution to YAML: https://github.com/yaml/yaml-spec/blob/main/.github/contributing.md'
'SAML 2.0 is included in Portugal and Slovakian national catalogues of recommended specifications. The National Interoperability Framework (NIF) of Slovakia and Portugal is fully aligned with at least 2 out of 3 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. NIFO Factsheets: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public-administration-factsheets-2022 CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards Slovakia NIFO Factsheet: https://joinup.ec.europa.eu/sites/default/files/inline-files/NIFO%20-%20Factsheet%20Slovakia_2016_v1_0.pdf SAML 2.0 Reference: http://docs.oasis-open.org/security/saml/Post2.0/sstc-saml-tech-overview-2.0.html'
'The Open Digital Rights Language (ODRL) specification is primarily designed for expressing digital rights and permissions rather than specifically addressing data portability. However, the use of a standardized language like ODRL can contribute to data portability efforts between systems and applications. W3C specification: https://www.w3.org/TR/odrl-vocab/#vocab-core'
'The purpose of FTP is not related to restricting access to information/data. Therefore this criterion is considered not applicable to this specification. FTP Specification Reference: https://datatracker.ietf.org/doc/html/rfc959'
'The FTP (File Transfer Protocol) specification allows for partial implementations to some extent. It defines a set of core commands and behaviors that must be supported by all conforming FTP implementations to ensure basic interoperability. However, the FTP specification also includes optional features and extensions that allow for additional functionality beyond the core commands. These optional features can be selectively implemented based on the specific requirements and capabilities of the FTP server or client. FTP Specification Reference: https://tools.ietf.org/html/rfc959'
'ISO/IEC 19944-1 has been found recommended in a digitalisation report by the Spanish Standardisation Association (UNE) and the Louxembourg Institute for standardisation (ILNAS) as one of the specifications "addressing business challenges and supporting related ICT development". UNE digitalisation report: https://www.une.org/normalizacion_documentos/Informe%20Transformaci%C3%B3n%20Digital_20201127.pdf ILNAS Technical standardisation report: https://portail-qualite.public.lu/dam-assets/publications/normalisation/2022/report-technical-standardization-cloud-computing.pdf ISO/IEC 19944-1 specification: https://www.iso.org/standard/60545.html'
'Using mechanisms such as time-stamping authority, it is possible to ensure that data is secured and that only authorised persons have access to them. Moreover, there are other access control mechanisms that guarantee data is secured and changes are only allowed for authorised persons. ETSI TS 119 512: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.01_60/ts_119512v010101p.pdf ETSI EN 319 401: https://www.etsi.org/deliver/etsi_en/319400_319499/319401/02.03.01_60/en_319401v020301p.pdf'
'IEEE Std 802.3-2022 primarily focuses on the physical and data link layers for Ethernet networks, and while it doesn’t directly address e-accessibility, it supports the infrastructure that enables accessible digital services. Therefore, this criterion is not applicable to this specification. IEEE Std 802.3-2022 Reference: https://ieeexplore.ieee.org/document/9844436'
Tools & Libraries for assessing the conformance of datasets with DCAT or its extensions have been developed by the community. See: http://www.dcat.be/validator/ https://www.npmjs.com/package/dcat-validator https://joinup.ec.europa.eu/solution/dcat-ap-validator
SOAP 1.2 is a sector domain agnostic specification that can be used independently from the business domain.
'The purpose of MIME is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification. MIME specification: https://tools.ietf.org/html/rfc2045'
'DCAT-AP has a strong support from different communities. In fact, it is a joint initiative of the DCAT-AP Working Group, which comprises the Directorate-General for Informatics: (DG DIGIT), in particular the SEMIC action of the ISA² programme, the Directorate-General for Communications Networks, Content & Technology (DG CONNECT), and The Publications Office of the EU. DCAT Application profiles for data portals in Europe: https://joinup.ec.europa.eu/solution/dcat-application-profile-data-portals-europe/about DCAT-AP leaflet: https://ec.europa.eu/isa2/sites/isa/files/leaflet_dcat-ap_lr_v13.pdf '
'One of the supporting documents of this specification is ETSI GR CIM 007, which identifies the security and privacy aspects that are relevant when building systems based on the NGSI-LD API and the NGSI-LD information model. Mechanisms for giving proof of authentication are described in ETSI TS 102 165-2, and in the context of attribute based cryptography in ETSI TR 103 719. In the NGSI-LD API context authentication is used in part to verify the identity of each actor in the NGSI-LD API system. ETSI Context Information Management (CIM); Security and Privacy: https://www.etsi.org/deliver/etsi_gr/CIM/001_099/007/01.01.02_60/gr_cim007v010102p.pdf ETSI TS 102 165-2: https://www.etsi.org/deliver/etsi_ts/102100_102199/10216502/04.02.01_60/ts_10216502v040201p.pdf ETSI TR 103 719: https://www.etsi.org/deliver/etsi_tr/103700_103799/103719/01.01.01_60/tr_103719v010101p.pdf'
'There is no reference to WAI-ARIA and a European use case explicitly stating that the specification allows relevant information and data to be reused. However, since WAI-ARIA can extend a host language, a grid can reuse the elements and attributes of an HTML table element. WAI-ARIA reference, section 5.4, Grid subsection: https://www.w3.org/TR/wai-aria/'
'The OGC TrainingDML-AI Standard does not specifically mention the protection of personal data managed by Public Administrations. Therefore, this criterion is considered not applicable to this specification. OGC TrainingDML-AI Standard: https://docs.ogc.org/is/23-008r3/23-008r3.html'
'The ISO community, brings together experts to share knowledge and develop voluntary, consensus-based, market relevant International Standards that support innovation and provide solutions to global challenges. All of ISO’s technical work, including the technical committees, is managed by the Technical Management Board (TMB). Some of the TMB’s tasks include setting up technical committees, appointing chairs and monitoring the progress of technical work. ISO developing standards: https://www.iso.org/who-develops-standards.html'
There is no existing study or documentation assessing the specification in terms of effectiveness and efficiency to justify the criterion.
'The specification is independent from any particular software, hardware, or operating system. So, it can be said that ISO 19941:2017 is independent of any specific technology. ISO 19941: https://www.iso.org/obp/ui/en/#iso:std:iso-iec:19941:ed-1:v1:en'
'ebXML is originally associated to the electronic business domain, specially ebXML v1.0. Since the ebXML v2.0 release, the specification started to be indistinctly used in any domain, although its implementation is usually associated to the business domain (see ebXML Business Process Specification reference). OASIS ebXML Registry TC reference, Announcements section: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=regrep#announcements ebxml.xml.org reference: http://ebxml.xml.org/milestones ebXML Business Process Specification reference: https://docs.oasis-open.org/ebxml-bp/2.0.4/HTML/ebxmlbp-v2.0.4-Spec-cs-en.htm#_Toc148506924'
'The PROV family of documents has not been found included covering privacy aspects in any initiative at national nor European level. PROV Primer document: https://www.w3.org/TR/prov-primer/ PROV Ontology: https://www.w3.org/TR/2013/REC-prov-o-20130430/ PROV Data Model: https://www.w3.org/TR/2013/REC-prov-dm-20130430/'
One of the main benefits of the e-Government Core Vocabularies is that they provide a concrete starting point for promoting semantic interoperability among European public administrations, so it fosters the creation of innovative solutions. CLV Joinup reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-location-vocabulary
RDF is compliant with one of the maximum levels of maturity provided by Tim Berners Lee’s 5 stars schema for open data. Moreover, RDF is highly aligned with the principles for Linked Data promoted by W3C and Tim Berners Lee. In fact, RDF is one of the proposed standards for the publication of Linked Open Data. The specification is compliant with Tim Berners Lee's principles for the Linked Data and, as well, is highly aligned with the different levels of maturity of Tim Berners Lee's 5 stars schema for open data. In fact, RDF is one of the proposed standards for the publication of Linked Data. See: https://www.w3.org/DesignIssues/LinkedData.html https://5stardata.info/en/ https://www.w3.org/TR/ld-bp/
As a specification that aim to allow and stablish exchange of documents, MIME can be used for the exchange of documents solving administrative burden. Additionally, it can avoid the exchange of non-digital documents that are generally a source of administrative burden. MIME reference: https://tools.ietf.org/html/rfc2045
'XSD is included in 8 national catalogues of recommended specifications. Among those we can find the Netherlands and Spain. The National Interoperability Framework (NIF) of these Member States is fully aligned with at least 2 out of 3 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. NIFO factsheets: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public-administration-factsheets-2022 CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards'
"While genericode's primary purpose is to provide a structured and consistent way to represent lists of values, by using Genericode-compliant code lists, organisations can ensure consistency in how these values are represented, improving data clarity, In addition, the inclusion of metadata can improve understanding and interpretation of the codes within various contexts. Code List Representation (genericode): https://docs.oasis-open.org/codelist/genericode/v1.0/os/genericode-v1.0-os.html"
'Section 4 of genericode defines that an XML instance conforms to the OASIS Code List Representation genericode document model if it does not violate any constraints expressed in the genericode.xsd schema associated with this version of the specification, including auxiliary rules marked as “document” rules. Furthermore, appendix E delves into testing select document conformance rules (non-normative), which specifies that some of the document conformance auxiliary rules prescribed in Section 4.2, “Category: document” can be tested using ISO/IEC 19757-3 Schematron. Section 4 genericode: https://docs.oasis-open.org/codelist/genericode/v1.0/os/genericode-v1.0-os.html#S-CONFORMANCE Appendix D genericode: https://docs.oasis-open.org/codelist/genericode/v1.0/os/genericode-v1.0-os.html#A-TESTING-SELECT-DOCUMENT-CONFORMANCE-RULES ISO/IEC 19757-3:2020: https://www.iso.org/standard/74515.html'
"The Indexed Database API specification allows to restrict access to information/data stored by some web that utilise the specification. In this context, only the website that created the data (from the same domain) can access it. If a website is loaded inside an iframe from a different domain, it can't access the data of the parent website. This rule helps protect your data from unauthorised access or manipulation. Indexed Database API privacy: https://www.w3.org/TR/2025/WD-IndexedDB-3-20250110/#privacy"
'By promoting standardized practices, Interoperability considerations, and compliance with relevant standards, the specifications guidelines and recommendations can enhance organisations interoperability with other systems and foster data exchanges. ISO/IEC 19944-1 specification: https://www.iso.org/standard/60545.html'
'The Apache License 2.0 is known for being permissive and allowing users to freely use, modify, and distribute the software. It does not impose restrictions on how the software can be used in proprietary or open-source projects. Furthermore, International Data Space - Global is licensed under License Creative Commons Attribution 4.0 International, which permits almost any use subject to providing credit and license notice. License Creative Commons Attribution 4.0 International: https://github.com/International-Data-Spaces-Association/IDS-G/blob/main/LICENSE.md Apache 2.0: https://www.apache.org/licenses/LICENSE-2.0'
At the moment of performing the assessment, PNG is widely used in across sectors, it is one of the main image extension used. However, no evidences has been found to consider PNG as an asset to build innovative solutions.
'NUTS is intended to serve as a device to identify administrative zones in the EU and beyond the EU borders. There is no possibility of partial implementation of the specification, as NUTS has a single purpose. EUROSTAT reference, NUTS Principles and Characteristics section: https://ec.europa.eu/eurostat/web/nuts/principles-and-characteristics'
'By employing a common data model, adhering to platform-neutral principles, and supporting adaptable resolution processes, DIDs can be effectively implemented across a wide range of platforms. DIDs W3C: https://www.w3.org/TR/did-core/'
The IETF is completely open to newcomers. There is no formal membership, no membership fee, and nothing to sign. The IETF's standards development work is organized into 8 Areas Each Area has 1 or more Area Directors (ADs), which together comprise the Internet Engineering Steering Group (IESG). The IESG is responsible for technical management of IETF activities, the Internet standards process, and for the actions associated with entry into and movement along the Internet ''standards track'', including final approval of specifications as Internet Standards and publication as an RFC. Within each Area there are multiple Working Groups (WG). Each WG has one or more chairs who manage the work, and a written charter defining what the work is and when it is due. There are more than 100 WGs. The WGs produce Internet Drafts (I-Ds) which often lead to the publication of an Internet standard as an RFC._x000D_ See: http://www.ietf.org/newcomers.html
'There are assessments that analyse and proving the effectiveness of the the usage of AMQP and other similar specifications. For a detailed explanation of AMQP's efficiency and comparison with other messaging protocols, refer to the document "Choice of Effective Messaging Protocols for IoT Systems: MQTT, CoAP, AMQP and HTTP." Additionally, numerous real-world scenarios, products, and articles utilise and reference the AMQP specification, demonstrating its effectiveness. Examples of commercially available AMQP products include Microsoft's Azure Service Bus, JBoss A-MQ by Red Hat (built from Qpid), IBM’s MQlight, and many others. Choice of Effective Messaging Protocols for IoT Systems: MQTT, CoAP, AMQP and HTTP Reference: https://pure.port.ac.uk/ws/portalfiles/portal/12197128/IoT_Messaging_Protocols_Naik.pdf Products and Success Stories - AMPQ.org Reference: https://www.amqp.org/about/examples Microsoft Windows Azure Reference: http://www.windowsazure.com/en-us/develop/net/how-to-guides/service-bus-amqp-overview/ RedHat JBoss A-MQ Reference: http://www.redhat.com/en/technologies/jboss-middleware/amq IBM MQlight Reference: https://developer.ibm.com/messaging/mq-light/'
'MIME can play a role in authentication processes such as digital signatures, by specifying content types and headers to handle digitally signed or authenticated messages, but it does not provide the mechanisms for creating or verifying digital signatures or other authenticity features. MIME specification: https://tools.ietf.org/html/rfc2045 S/MIME specification: https://www.rfc-editor.org/rfc/rfc5751.html'
The RFC 3161 Time-Stamp Protocol (TSP) is widely used and involved in e-Signature services. This electronic signatures are part of digital public services, and also private in order to focus the development of digital environments avoiding the non-digital transactions. TSP IETF reference: https://tools.ietf.org/html/rfc3161 DigiStamp: https://www.digistamp.com/ FreeTSA: https://www.freetsa.org/index_en.php
'At the time of the assessment, there has not been found any European platform hosting a community tasked around the ShEx specification. ShEx primer document: https://shexspec.github.io/primer/ ShEx Community Group: https://www.w3.org/community/shex/ ShEx Github: https://github.com/shexSpec/spec/issues'
'The conformance of syslog protocol implementations can be assessed based on several factors, and there are various aspects to consider to ensure that an implementation adheres to the syslog protocol standards. The syslog protocol is defined by several Request for Comments (RFC) documents, including RFC 5424. Assessing the implementation against the requirements and specifications outlined in these RFCs ensures that it adheres to the standard. Syslog Protocol: https://datatracker.ietf.org/doc/html/rfc5424'
'The Registered Organization Vocabulary defined core concepts and properties for describing registered organisations, laying a foundational understanding in this domain, particularly at an international level. However, according to recent discussions on the Core Business Vocabulary GitHub, W3C has discontinued the Registered Organization Vocabulary and the community along with the continuation for the development moved to the Core Business Vocabulary. Registered Organization Vocabulary reference: https://www.w3.org/TR/vocab-regorg/ Core Business Vocabulary Github reference: https://github.com/SEMICeu/Core-Business-Vocabulary/tree/master Core Business Vocabulary Github Issue 51 - RegOrg maintenance reference: https://github.com/SEMICeu/Core-Business-Vocabulary/issues/51'
After searching for a certification or conformity test to validate SVG no tool has been found that assess the conformity of the specification.
The specification is included in 8 Member States' catalogues of recommended specifications. Some examples of Member States including SOAP on their catalogues are the Netherlands, Spain or France. See: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'The PROV family of documents can facilitate the modeling of business processes to some extent by providing concepts such as activities, agents, and dependency relationships. It supports the documentation and traceability of data and activities, aiding in the understanding, analysis, and improvement of business processes. PROV Primer document: https://www.w3.org/TR/prov-primer/ PROV Ontology: https://www.w3.org/TR/2013/REC-prov-o-20130430/ PROV Data Model: https://www.w3.org/TR/2013/REC-prov-dm-20130430/'
'Schema.org is open to any interested party who has agreed to the W3C Community Contributor License Agreement (CLA) (see Schema.org homepage reference, Community Group and Steering Group section). The CLA provisions refer to the W3C Patent Policy, which covers the availability of schema.org with any restrictions related to fair, reasonable and non-discriminatory ((F)RAND) rights. Schema.org homepage reference, Community Group and Steering Group section: https://schema.org/docs/about.html W3C Patent Policy reference: https://www.w3.org/TR/patent-practice#ref-AC '
'This specification includes evaluations of verifiable credentials through a verifiable data registry. This role an entity may perform is the evaluation of whether a verifiable credential or verifiable presentation is an authentic and timely statement of the issuer or presenter, respectively includes checking that: the credential (or presentation) conforms to the specification; the proof method is satisfied; and, if present, the status is successfully checked. Verifiable Credentials: https://www.w3.org/TR/vc-data-model/ Verifiable Credentials conformance: https://www.w3.org/TR/vc-data-model/#conformance'
'The TC(Technical Committe) is the primary group where OGC Standards and many Products are developed, discussed, approved, and maintained. The TC members are responsible for the development and maintenance of all Standards and related technical documents and supporting deliverables. OGC Technical Committee Procedures: https://www.ogc.org/join/ OGC Technical Committee Policies: https://docs.ogc.org/pol/05-020r29/05-020r29.html'
'The specification is widely adopted amongst others like SMTP for the exchange of data over the internet. It allows sharing several file formats, which makes the specification highly reusable. The specification has been implemented and it is supported by numerous mail services as Gmail amongst others, demonstrating the market acceptance of MIME. MIME reference: https://tools.ietf.org/html/rfc2045 SMTP specification: https://datatracker.ietf.org/doc/html/rfc5321 Gmail using MIME: https://developers.google.com/gmail/api/guides/sending?hl=es-419'
"As it can be seen in the example of 'data protection aspects of online shopping - a use case', DPV specifies the personal data that an order delivery has to take from the client, thus, ensuring efficient interactions between clients and citizens. For that matter, DPV can ease digitalisation and simplify the delivery of European public services. DPV specification: https://w3c.github.io/dpv/primer/ Data protection aspects of online shopping - a use case: https://www.w3.org/community/dpvcg/2019/12/12/data-protection-aspects-of-online-shopping-a-use-case/"
'Implementing the Core Location Vocabulary enhances digital services by standardising location data, ensuring interoperability, and automating processes. This reduces reliance on non-digital document exchange, improves data integrity, and facilitates compliance with regulations. Overall, it fosters a more efficient, reliable, and user-friendly digital ecosystem. Core Location Vocabulary: https://interoperable-europe.ec.europa.eu/collection/semic-support-centre/solution/core-location-vocabulary/release/100'
'Up to date, there is no specific mechanism to assess the IPsec conformity in the IPsec documentation. IPSec reference, Conformance Requirements: https://datatracker.ietf.org/doc/html/rfc4301#section-10 IPSec reference: https://datatracker.ietf.org/doc/html/rfc4301'
'The IPv4 specification plays a foundational role in enabling data portability between systems or applications in terms of network communication. Moreover, mechanisms such as IPsec ensures that data is secure transfered between systems. IPv4 IETF: https://www.rfc-editor.org/rfc/rfc791 IPsec protocol: https://www.cloudflare.com/learning/network-layer/what-is-ipsec/'
'DNS over HTTPS (DoH) enhances the security of data exchange at the DNS layer by encrypting DNS queries and responses. It provides a layer of confidentiality and integrity for these communications. Section 4 of the protocol focuses on the HTTPS Exchange, from the request where a DoH client encodes a single DNS query into an HTTP request, to the response. Section 4 DoH specification: https://datatracker.ietf.org/doc/html/rfc8484#section-4'
The purpose of JPEG is not related to the implementation of the once-only principle. Therefore, this criterion does not apply to this specification. JEPG ISO reference: https://www.iso.org/standard/18902.html JPEG public reference: https://jpeg.org/jpeg/
'Among others, UBL has been used to develop the PEPPOL specifiaction, a which enables businesses across Europe to communicate electronically with public buyers in various stages of the procurement process. PEPPOL provides a set of technical specifications that can be implemented in existing eProcurement solutions and eBusiness exchange services to make them interoperable between disparate systems across Europe. PEPPOL website: https://peppol.eu/what-is-peppol/'
After searching for a certification or conformity test to validate EuroVoc no tool has been found that assess the conformity of the specification.
'The available information does not specifically mention any means for restriction of access to information /data. Therefore, this criterion is considered not applicable to this specification. OGC TrainingDML-AI Standard: https://docs.ogc.org/is/23-008r3/23-008r3.html'
'The purpose of HTTP Cookies is other than enabling the e-accessibility, therefore this criterion is not applicable to this specification. HTTP Cookies reference: https://developer.mozilla.org/en-US/docs/Web/HTTP/Cookies#tracking_and_privacy'
'The specification is designed to be technology agnostic, which means that it can be implemented using any technology or programming language. It is based on the principles of XML (eXtensible Markup Language) and uses XML-based schemas to represent legal documents. AKN4EU reference: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/akn4eu'
'All information about IPsec, including details about extensions and implementations that work with IPsec, is published on the IETF datatracker website. Additionally, information about the six versions is provided on the same website. Furthermore, IPsec has been integrated into the IPv6 protocol, for example, providing enhanced security mechanisms. In this sense, IPsec was initially designed as part of the next-generation Internet Protocol (IPv6), but as security became important, it was designed to work with both IPv4 and IPv6. IPSec reference: https://www.rfc-editor.org/rfc/rfc6071.html Datatracker IETF: https://datatracker.ietf.org/ IPsec in IPv6: https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ipv6/configuration/15-2s/ipv6-15-2s-book/ip6-ipsec.pdf IPsec in IPv4 and IPv6: https://networkengineering.stackexchange.com/questions/37025/ipsec-in-ipv4-and-ipv6'
Any cross-border project using internet, uses HTTP. An interesting example is the TESTA network service – which stands for Trans European Services for Telematics between Administrations – provides a European backbone network for data exchange between a wide variety of public administrations. It is an ISA2 solution which has been designed to support the needs for a whole range of application architectures relying on protocols such as HTTPS. See: https://ec.europa.eu/isa2/solutions/testa_en
'UBL is the product of an open and accountable OASIS Technical Committee with participation from a variety of international and industry data standards organizations. It was originally approved as an OASIS standard in 2004 and is among the most mature and widely implemented OASIS Standards. In 2014 the European Commission declared UBL 2.1 was officially eligible for referencing in tenders from public administrations. UBL is also integrated in the European Single Procurement Document (ESPD), a self-declaration form that aims to ease tendering processes in procurement. Developer community OASIS. UBL functionalities: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ubl#sanction UBL in ESPD project: https://ec.europa.eu/growth/single-market/public-procurement/digital-procurement/european-single-procurement-document-and-ecertis_en UBL adoption in ESPD: https://docs.ted.europa.eu/ESPD-EDM/3.0.1/xml_technical_handbook.html#_adoption_of_ubl_2_3'
'The purpose of DNS is not related to long term preservation of electronic records. Therefore, this criterion is considered not applicable to this specification. DNS IETF reference: https://datatracker.ietf.org/doc/html/rfc8499'
'ISO 3166-1 could be beneficial for the application of the one-time principle, as this specification may allow the reuse of relevant information regarding administrative units and the geometry of the maritime area at European level (see INSPIRE Data Specification on Administrative Units reference). ISO 3166-1 reference: https://www.iso.org/standard/72482.html INSPIRE Data Specification on Administrative Units reference: https://inspire.ec.europa.eu/id/document/tg/au'
'The rules on European standardisation allow the European Commission to identify information and communication technology (ICT) technical specifications - that are not national, European or international standards - to be eligible for referencing in public procurement. This allows public authorities to make use of the full range of specifications when buying IT hardware, software and services, allowing for more competition in the field and reducing the risk of lock-in to proprietary systems. After being evaluated compliant with the regulation on standardisation 1025/2012, HTTPS has been identified by Commission Implementing Decision and included in the European list of ICT Standards for e-procurement. ICT Standards for procurement: https://joinup.ec.europa.eu/collection/ict-standards-procurement/eprocurement#eProcurementStandards'
XAdES has provided a conformance testing tool for electronic signatures according to the European Commission Mandate 460. The conformity testing tool involves different standards applied in the development of eSignatures, including PAdES, CAdES and ASiC ant their respective Baseline profiles . See: https://signatures-conformance-checker.etsi.org/pub/ASiCConformanceTestChecker_v1.0.pdf https://signatures-conformance-checker.etsi.org/pub/index.shtml
The IETF is a consensus-based group, and authority to act on behalf of the community requires a high degree of consensus and the continued consent of the community. The process of creating an Internet Standard is straightforward: a specification undergoes a period of development and several iterations of review by the Internet community and revision based upon experience is adopted as a Standard by the appropriate body and is published. In practice, the process is more complicated, due to (1) the difficulty of creating specifications of high technical quality; (2) the need to consider the interests of all the affected parties; (3) the importance of establishing widespread community consensus; and (4) the difficulty of evaluating the utility of a particular specification for the Internet community. The goals of the Internet Standards Process are: - Technical excellence; - prior implementation and testing; - clear, concise, and easily understood documentation; - openness and fairness; and - timeliness. The goal of technical competence, the requirement for prior implementation and testing, and the need to allow all interested parties to comment all require significant time and effort. The Internet Standards Process is intended to balance these conflicting goals. The process is believed to be as short and simple as possible without sacrificing technical excellence, thorough testing before adoption of a standard, or openness and fairness. Standard process IETF: https://www.ietf.org/standards/process/
'The Internet Protocol is a necessary specification for the implementation of the once-only-principle as it allows cross-border communications over the internet. For example, an IPv4 address can be reused and an address block can only be used by any party on the Internet with the permission of others. Specifically, an ISP that is asked to provide connectivity to the party, by “routing” their address block onto the Internet. IPv4 address reuse: https://www.apnic.net/manage-ip/ipv4-exhaustion/ipv4-exhaustion-and-address-transfers/'
'XSLT specification does not address or provide any insights into the modeling of business processes. XSLT Reference: https://www.w3.org/TR/xslt-30'
'There are many forums discussing the implementation of IndexedDB. In addition, papers assessing the specification and offering new extensions can be found on the internet. IndexedDB github: https://github.com/w3c/IndexedDB IndexedDB StackOverflow forum: https://stackoverflow.com/questions/7759376/indexeddb-performance IndexedDB Apple forum: https://forums.developer.apple.com/forums/thread/730023'
'TOSCA is widely known in the field of cloud computing, since it runs on a container (or software unit) and specifies orchestration process models that enable the management of services independently of the application context. In this sense, the specification can be used beyond the business-specific domain and allows its implementation across any business domain. TOSCA reference: https://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.3/os/TOSCA-Simple-Profile-YAML-v1.3-os.html'
'The specification is relevant for administrations and services providers to be compliant with eIDAS. It is recommended and used in several services related to eIDAS compliance. Therefore, it is a clear specification that can be the center of discussions for the improvement of it and the services implementing it. ETSI EN 319 422 reference: https://www.etsi.org/deliver/etsi_en/319400_319499/319422/01.01.01_60/en_319422v010101p.pdf'
"Despite being involved in several projects, ISO 3166-1 has no evaluations that assess it and no evidence of any technological solutions that indirectly assess the specification has been found. Therefore, there is no assessment of the specification's efficiency. ISO 3166-1 reference: https://www.iso.org/standard/72482.html"
The purpose of PDF/A is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification. PDF/A reference: https://www.iso.org/standard/38920.html https://www.iso.org/standard/50655.html
'Syslog is primarily focused on the transmission and storage of log messages related to system events, security incidents, and other operational activities. While syslog itself does not inherently ensure the protection of personal data, its implementation and usage within public administrations can have implications for data protection. Having a standard way for event data logs can improve the protection of personal data. Syslog Protocol: https://datatracker.ietf.org/doc/html/rfc5424 '
'The specification is included in the Publications Office of the European Union (PO). Core Location Vocabulary PO: https://op.europa.eu/en/web/eu-vocabularies/corevocs#:~:text=The%20Core%20Location%20Vocabulary%20%28latest%20version%29%20is%20a,Vocabulary%20is%20aligned%20with%20the%20INSPIRE%20data%20specifications. Core Location Vocabulary: https://interoperable-europe.ec.europa.eu/collection/semic-support-centre/solution/core-location-vocabulary/release/100'
'The purpose of DNS is not related to e-accessibility. Therefore this criterion is not applicable to the specification. DNS IETF reference: https://datatracker.ietf.org/doc/html/rfc8499'
After searching for a certification or conformity test to validate Xforms 2.0 no tool has been found that assess the conformity of the specification. However, there are tools that validate the previous version of Xforms, version 1.1.
SAMM includes recommendations on data protection and requirements for the proper protection and management of relevant data over their lifetime and also over time. More specifically, it is written down under the operational management and the first stream, which states the outcomes and need of establishing a data catalogue. SAMM webpage: https://owaspsamm.org SAMM Documentation: https://github.com/OWASP/samm/blob/master/Supporting%20Resources/v2.0/OWASP-SAMM-v2.0.pdf
The purpose of Ogg is not related to organisational interoperability. Therefore, this criterion is not applicable to the specification. Ogg XIPH reference: https://xiph.org/ogg/doc/rfc3533.txt
'The ISO 3166 Maintenance Agency is responsible for providing public support for any request regarding ISO 3166-1, but does not define the country names itself; the country names come from United Nations (UN) sources. ISO reference, ISO 3166 Country Codes: https://www.iso.org/iso-3166-country-codes.html?msclkid=54aebe8ca9f611ec89ac280389b78309'
'The Asset Administration Shell (AAS) has some specific provisions regarding multilingualism mainly related at the naming of the assets and is characteristics but the specification per se is not multilingual. Details of the Asset Administration Shell (AAS) https://industrialdigitaltwin.org/en/wp-content/uploads/sites/2/2024/06/IDTA-01001-3-0-1_SpecificationAssetAdministrationShell_Part1_Metamodel.pdf'
'While it uses the EU’s General Data Protection Regulation (GDPR) as a guiding source for the creation and interpretation of concepts, the ambition and scope of DPV is to provide a broad globally useful vocabulary that can be extended to jurisdiction or domain specific applications. DPV primer document: https://w3c.github.io/dpv/primer/#introduction '
HTML5 can be found along with other versions and extensions within the European Colaborative Platform, Joinup. See: https://joinup.ec.europa.eu/search?keys=HTML5&f%5B0%5D=type%3Asolution&page=0
'By allowing the association of information with a domain, DNS facilitate the identification of interfaces. Practically, instead of having a list of interfaces as "IP Addresses", DNS allows the identification "by name" of domain. DNS IETF reference: https://tools.ietf.org/html/1034 Domain Names - Implementation and Specification: https://tools.ietf.org/html/1035 '
'The W3C Royalty-Free IPR licences granted under the W3C Patent Policy apply to all W3C specifications, including WAI-ARIA. W3C Patent practice: https://www.w3.org/TR/patent-practice#ref-AC WAI-ARIA participation charter, section 8: https://www.w3.org/2018/11/aria-charter'
'DCAT is a domain-agnostic specification that can be reused for the description of any catalogue of dataset independently from the business domain addressed. For DCAT users having business-specific requirements, the specification is generally extended (e.g. StatDCAT-AP for statistical data). DCAT-AP Specification: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/dcat-application-profile-data-portals-europe/release/200 StatDCAT-AP: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/statdcat-application-profile-data-portals-europe/release/101'
'The NFVI specification facilitates the modelling of business processes because there exist several NFV models that support businesses to model their activity along with all the NFV components. There is a high level overview of the NFVI domains and interfaces in the specification documentation. NFVI Deliver, Infrastructure Overview section 7: https://www.etsi.org/deliver/etsi_gs/NFV-INF/001_099/001/01.01.01_60/ '
The purpose of the specification is not related to the publication of data as linked open data. Therefore, this specification is not applicable for this criterion.
'ShEx is itself a tool to assess the conformity of RDF data graphs against correspondent schemas. Moreover, W3C provides the ShEx Simple Online Validator, an online tool that allows performing RDF data validation using Shape Expressions. ShEx Simple Online Validator: https://rawgit.com/shexSpec/shex.js/master/packages/shex-webapp/doc/shex-simple.html ShEx primer document: https://shexspec.github.io/primer/ ShEx Community Group: https://www.w3.org/community/shex/ ShEx Github: https://github.com/shexSpec/spec/issues '
'XHTML is maintained by the World Wide Web Consortium (W3C), an international community dedicated to developing open standards. This collaboration ensures that web technologies remain accessible, interoperable, and beneficial to users globally. XHTML W3C reference https://www.w3.org/TR/xhtml1/ Developer community W3C: https://www.w3.org/Consortium/'
'WSDL (Web Services Description Language) does enable the exposure of interfaces for web services, including those offered by public administrations. By defining a standardized way to describe the functionalities, operations, and communication protocols of a web service, WSDL makes these services accessible and usable by external systems and applications. WSDL can be combined with other specifications and technologies to enable the exposure of interfaces for accessing services. WSDL, on its own, provides a standardized way to describe the interface and operations of a web service. However, the complete exposure of interfaces often requires additional components and considerations. W3C WSDL specification: https://www.w3.org/TR/wsdl20/#Interface'
CAMSS Assessment of UBL EIF Scenario v2.0.0
'The UBL specification is based on XML, which inherently supports customisation. In this context, UBL adopts a similar approach, allowing for tailored implementations while maintaining a core structure._x000D_ Certain elements within UBL are mandatory and cannot be customised, ensuring consistency and interoperability. However, once these required components are in place, users have the flexibility to select additional elements according to their specific needs, choosing the subset of UBL elements most relevant to their business transactions._x000D_ _x000D_ XML customisation:_x000D_ https://www.xml.com/articles/2017/01/01/what-is-ubl/#d0e126_x000D_ _x000D_ Customisation and extension of UBL:_x000D_ https://docs.oasis-open.org/ubl/guidelines/UBL2-Customization1.0cs01.pdf_x000D_ _x000D_ UBL specification reference:_x000D_ https://docs.oasis-open.org/ubl/os-UBL-2.4/UBL-2.4.html'
'The UBL specification is based on XML, which supports a range of security mechanisms that are also compatible with UBL. One such mechanism is the XML Signature Syntax and Processing specification (XMLDSig), which is supported by both XML and UBL._x000D_ XMLDSig enables authentication of the document sender and verification of data integrity, ensuring that the content has not been altered during transmission and that the origin of the document can be reliably confirmed._x000D_ _x000D_ XMLDSig specification:_x000D_ https://www.w3.org/TR/xmldsig-core/_x000D_ _x000D_ UBL specification reference:_x000D_ https://docs.oasis-open.org/ubl/os-UBL-2.4/UBL-2.4.html'
'UBL is designed to integrate seamlessly with existing business, accounting, legal, auditing, and records management practices. By eliminating the need to re-key data, common in traditional fax, scanned-image, and paper-based supply chains, UBL offers a gateway to electronic business for small and medium-sized enterprises._x000D_ As a result, UBL enhances both internal and external visibility of administrative procedures and data. It also facilitates the delivery of European public services, as exemplified by its role in the ESPD project._x000D_ _x000D_ ESPD Project UBL:_x000D_ https://docs.ted.europa.eu/ESPD-EDM/latest/technical/tech_architecture.html_x000D_ _x000D_ UBL specification reference:_x000D_ https://docs.oasis-open.org/ubl/os-UBL-2.4/UBL-2.4.html'
'UBL was developed through the open and transparent work of an OASIS Technical Committee, involving contributions from numerous international and industry data standards bodies. First ratified as an OASIS Standard in 2004, it has since become one of the most established and widely implemented standards in the OASIS ecosystem._x000D_ _x000D_ In 2014, the European Commission declared UBL 2.1 officially eligible for referencing in tenders issued by public administrations. UBL is also integrated into the European Single Procurement Document (ESPD), a self-declaration form designed to simplify tendering procedures in public procurement at the EU level and adapted for use in national schemes._x000D_ _x000D_ Furthermore, UBL has been increasingly adopted by several countries for business transactions between enterprises and public administrations, as it provides a standardised and interoperable format for communication between organisations._x000D_ _x000D_ ESPD Project UBL:_x000D_ https://docs.ted.europa.eu/ESPD-EDM/latest/technical/tech_architecture.html_x000D_ _x000D_ UBL adoption:_x000D_ https://www.b2brouter.net/global/what-is-ubl-format/_x000D_ _x000D_ UBL specification reference:_x000D_ https://docs.oasis-open.org/ubl/os-UBL-2.4/UBL-2.4.html'
'UBL is the product of the OASIS Technical Committee, with participation from a diverse range of international and industry data standards organisations. Originally approved as an OASIS Standard in 2004, it is now one of the most mature and widely implemented standards within the OASIS framework._x000D_ _x000D_ In 2014, the European Commission officially recognised UBL 2.1 as eligible for referencing in public sector tenders. The following year, UBL 2.1 was also approved as ISO/IEC 19845:2015, establishing it as a true international standard for use by governmental bodies worldwide. This endorsement represents the highest level of formal recognition attainable for an international standard._x000D_ _x000D_ The UBL 2.3 version, approved in 2021, introduced minor updates as part of a minor release. And the latest version, UBL 2.4, launched in 2024, follows the same incremental approach and increases the range of different business documents._x000D_ _x000D_ UBL history:_x000D_ https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ubl_x000D_ _x000D_ UBL specification reference:_x000D_ https://docs.oasis-open.org/ubl/os-UBL-2.4/UBL-2.4.html'
'The UBL specification is primarily intended for use within the business domain. However, while it focuses on the exchange of business documents, it can also be effectively applied in other sectors such as healthcare, accounting, legal, auditing, and various areas of public administration._x000D_ In this context, it is worth highlighting that UBL is increasingly being used by businesses to communicate with public administrations, reflecting its versatility and growing adoption beyond its original scope._x000D_ _x000D_ UBL specification reference:_x000D_ https://docs.oasis-open.org/ubl/os-UBL-2.4/UBL-2.4.html'
'The UBL specification is included in 5 Member States catalogues of recommended specifications. These _x000D_ Member States are Croatia, Denmark, Greece, Malta, and The Netherlands._x000D_ _x000D_ National Catalogue of Croatia:_x000D_ https://ssi.gov.hr/en/catalogue_x000D_ _x000D_ National Catalogue of Denmark:_x000D_ https://arkitektur.digst.dk/sites/default/fileuploads/white_paper_on_a_common_public-sector_digital_architecture_pdfa.pdf_x000D_ _x000D_ National Catalogue of Greece:_x000D_ https://www.e-gif.gov.gr/wp-content/uploads/2022/01/744027.pdf_x000D_ _x000D_ National Catalogue of Malta:_x000D_ https://mccaa.org.mt/Section/Content?contentId=1243_x000D_ _x000D_ National Catalogue of The Netherlands:_x000D_ https://www.forumstandaardisatie.nl/open-standaarden/lijst_x000D_ _x000D_ CAMSS list of standards https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standard_x000D_ _x000D_ UBL specification reference:_x000D_ https://docs.oasis-open.org/ubl/os-UBL-2.4/UBL-2.4.html'
'When existing UBL entities do not fully address specific business requirements, new entities can be introduced as extensions. These extensions build upon the original entities by linking to them and incorporating additional information, effectively creating an expanded version of the original structure._x000D_ _x000D_ Customisation and extension of UBL:_x000D_ https://docs.oasis-open.org/ubl/guidelines/UBL2-Customization1.0cs01.pdf_x000D_ _x000D_ UBL specification reference:_x000D_ https://docs.oasis-open.org/ubl/os-UBL-2.4/UBL-2.4.html'
'The UBL specification is used by PEPPOL. PEPPOL (Pan European Public Procurement Online) is an international network that enables businesses worldwide to exchange electronic documents securely and easily, following a common standard adapted to the needs of each country. In this context, the UBL specification has been defined as a global standard to facilitate the exchange of electronic documents among companies from different countries._x000D_ In addition, the UBL specification is used in both the ESPD and OOTS projects. In the case of OOTS, public entities in the Netherlands use the specification to receive eInvoices. For this purpose, two UBL specialisations have been proposed for eInvoicing: UBL-OHNL and SI-UBL._x000D_ _x000D_ UBL OOTS:_x000D_ https://ec.europa.eu/digital-building-blocks/sites/spaces/einvoicingCFS/pages/406257983/Netherlands+2021+eInvoicing+Country+Sheet_x000D_ _x000D_ UBL-OHNL reference:_x000D_ https://www.logius.nl/domeinen/gegevensuitwisseling/e-procurement/documentatie/ubl-ohnl_x000D_ _x000D_ SI-UBL reference:_x000D_ https://github.com/Peppolautoriteit-nl/validation_x000D_ _x000D_ PEPPOL reference:_x000D_ https://peppol.com/_x000D_ _x000D_ ESPD Project UBL:_x000D_ https://docs.ted.europa.eu/ESPD-EDM/latest/technical/tech_architecture.html_x000D_ _x000D_ UBL specification reference:_x000D_ https://docs.oasis-open.org/ubl/os-UBL-2.4/UBL-2.4.html'
'The UBL specification facilitates digital service delivery channels by digitising processes that were previously carried out manually. Based on XML, it provides a standardised and interoperable data structure that enhances digital communication between users exchanging business documents, such as between public administrations and businesses. Consequently, the specification helps to streamline various procedures by enabling efficient digital service delivery._x000D_ _x000D_ UBL specification reference:_x000D_ https://docs.oasis-open.org/ubl/os-UBL-2.4/UBL-2.4.html'
'The effectiveness of the UBL specification has been assed by the Faculty of Engineering at the University of Porto. In the "A Business Language for a Distributed Simulation Framework" study, the UBL specification is proposed as a business language to promote semantic interoperability within a distributed simulation framework, facilitating communication between industrial simulation models._x000D_ _x000D_ "A Business language for a distributed simulation framework" study:_x000D_ https://www.researchgate.net/profile/Carlos-Braganca-3/publication/241186215_A_business_language_for_a_distributed_simulation_framework/links/0c96051c838d912f10000000/A-business-language-for-a-distributed-simulation-framework.pdf_x000D_ _x000D_ UBL specification reference:_x000D_ https://docs.oasis-open.org/ubl/os-UBL-2.4/UBL-2.4.html'
'5 Member States are recommending UBL in their ICT National Catalogues. These Member States are Croatia, Denmark, Greece, Malta, and The Netherlands._x000D_ _x000D_ National Catalogue of Croatia:_x000D_ https://ssi.gov.hr/en/catalogue_x000D_ _x000D_ National Catalogue of Denmark:_x000D_ https://arkitektur.digst.dk/sites/default/fileuploads/white_paper_on_a_common_public-sector_digital_architecture_pdfa.pdf_x000D_ _x000D_ National Catalogue of Greece:_x000D_ https://www.e-gif.gov.gr/wp-content/uploads/2022/01/744027.pdf_x000D_ _x000D_ National Catalogue of Malta:_x000D_ https://mccaa.org.mt/Section/Content?contentId=1243_x000D_ _x000D_ National Catalogue of The Netherlands:_x000D_ https://www.forumstandaardisatie.nl/open-standaarden/lijst_x000D_ _x000D_ CAMSS list of standards https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standard_x000D_ _x000D_ UBL specification reference:_x000D_ https://docs.oasis-open.org/ubl/os-UBL-2.4/UBL-2.4.html'
'UBL is maintained and developed by OASIS, which is an international community developing open standards; specifically, by the Technical Committee (TC). In addition, it is worth mentioning that its prominence and adoption in the EU also support the development of a European community._x000D_ _x000D_ OASIS organisation:_x000D_ https://www.oasis-open.org/_x000D_ _x000D_ UBL specification reference:_x000D_ https://docs.oasis-open.org/ubl/os-UBL-2.4/UBL-2.4.html'
'UBL is included in 5 national catalogues of recommended specifications. They belong to Croatia, Denmark, Greece, Malta and The Netherlands. The National Interoperability Framework (NIF) of The Netherlands is aligned with at least 3 out of 4 scoreboards of the EIF Monitoring according to the National Interoperability Framework Observatory (NIFO) factsheets._x000D_ _x000D_ NIFO Factsheets:_x000D_ https://interoperable-europe.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public-administration-factsheets-2024_x000D_ _x000D_ National Catalogue of Croatia:_x000D_ https://ssi.gov.hr/en/catalogue_x000D_ _x000D_ National Catalogue of Denmark:_x000D_ https://arkitektur.digst.dk/sites/default/fileuploads/white_paper_on_a_common_public-sector_digital_architecture_pdfa.pdf_x000D_ _x000D_ National Catalogue of Greece:_x000D_ https://www.e-gif.gov.gr/wp-content/uploads/2022/01/744027.pdf_x000D_ _x000D_ National Catalogue of Malta:_x000D_ https://mccaa.org.mt/Section/Content?contentId=1243_x000D_ _x000D_ National Catalogue of The Netherlands:_x000D_ https://www.forumstandaardisatie.nl/open-standaarden/lijst_x000D_ _x000D_ CAMSS list of standards https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standard_x000D_ _x000D_ UBL specification reference:_x000D_ https://docs.oasis-open.org/ubl/os-UBL-2.4/UBL-2.4.html'
'The UBL specification is based on XML, which supports various security mechanisms and complementary specifications that help protect data during exchange. One such mechanism is encryption, which enhances the trustworthiness of data by ensuring that it remains confidential and secure throughout transmission. This prevents unauthorised users from accessing or modifying the information, thereby safeguarding its integrity and authenticity._x000D_ _x000D_ XMLDSig specification:_x000D_ https://www.w3.org/TR/xmldsig-core/_x000D_ _x000D_ XAdES specification:_x000D_ https://www.w3.org/TR/XAdES/_x000D_ _x000D_ UBL specification reference:_x000D_ https://docs.oasis-open.org/ubl/os-UBL-2.4/UBL-2.4.html'
'Participation in the development of the OASIS UBL Technical Committee is open to all interested stakeholders. Contributors may actively engage by joining the UBL TC, submitting input, and offering feedback during public reviews of released specifications. Committee members collaborate through the UBL mailing list, which requires TC membership to post messages._x000D_ The OASIS UBL Technical Committee operates under OASIS Open-an organisation that fosters collaboration among individuals, organisations, and governments to address technical challenges through open standards. Participation is open to all who wish to contribute._x000D_ _x000D_ OASIS Universal Business Exchange Technical Committee:_x000D_ https://www.oasis-open.org/committees/ubl/charter.php_x000D_ _x000D_ UBL OASIS Technical Committee reference:_x000D_ https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ubl_x000D_ _x000D_ UBL specification reference:_x000D_ https://docs.oasis-open.org/ubl/os-UBL-2.4/UBL-2.4.html'
'The UBL specification is based on XML. XML format, particularly through XAdES (XML Advanced Electronic Signatures), is recognised by the eIDAS Regulation as a compliant format for advanced electronic signatures. _x000D_ _x000D_ Overview of Standards for eIDAS document: https://www.enisa.europa.eu/publications/assessment-of-standards-related-to-eidas_x000D_ _x000D_ eIDAS Regulation: _x000D_ https://digital-strategy.ec.europa.eu/en/policies/eidas-regulation_x000D_ _x000D_ UBL specification reference:_x000D_ https://docs.oasis-open.org/ubl/os-UBL-2.4/UBL-2.4.html'
'The efficiency of the UBL specification has been assed by the Fachhochschule Nordwestschweiz Olten (Basel), Switzerland, and the School of Science and Technology - University of Camerino, Italy. In the "The UBL Standard and its Potential in the Exchange of Industrial Data" study, it is concluded that UBL has significantly evolved to cover more detailed phases of business processes, especially in delivery and e-procurement._x000D_ _x000D_ "The UBL Standard and its Potential in the Exchange of Industrial Data" study:_x000D_ https://d1wqtxts1xzle7.cloudfront.net/89803279/EEE2893-libre.pdf?1660726010=&response-content-disposition=inline%3B+filename%3DThe_UBL_Standard_and_its_Potential_in_th.pdf&Expires=1754043009&Signature=WkPeZJ~ubx2R-yEDIsHD-RQ2LktCrT5LD~tKFp5fyM6i~soMhEekM-kfQATH5EpI6s-Ph4sh~Hd48iBALFUsQDIh9nB2BvBHRNrE6AmQWyRa2HVH46QlAhPlIN2ArNSUGGeH5mq~BbQkWk7hbN-PlPwhzIjKgkKyYX1apdxHDMXw-V0h1xIdb8D1DUD5xe0K04a~-10y7bukQeudWJ-mcROxPQv3YA5jad5~xzPRzMl29SCJE2aufZ7lYe86TjR8o-XtwTomJWRWrnyuzeZ9L6s4vZo~i~fZ~Upbbj9EqHiYEIpJ4zT5mz5CUGQ7xup0~XFvLd0jVz~QyEhlxzfBLw__&Key-Pair-Id=APKAJLOHF5GGSLRBV4ZA_x000D_ _x000D_ UBL specification reference:_x000D_ https://docs.oasis-open.org/ubl/os-UBL-2.4/UBL-2.4.html'
'The UBL specification is developed by OASIS, a non-European organisation. However, it is used by many European countries and has also been adopted in different European projects. Therefore, this criterion is not applicable to this specification._x000D_ _x000D_ OASIS organisation:_x000D_ https://www.oasis-open.org/_x000D_ _x000D_ UBL specification reference:_x000D_ https://docs.oasis-open.org/ubl/os-UBL-2.4/UBL-2.4.html'
'The UBL specification does not directly define or expose technical interfaces for accessing public administration services. However, it is built upon XML, which provides a standardised, machine-readable data structure that facilitates the development and exposure of such interfaces._x000D_ Additionally, UBL has been adopted by several countries to support the exchange of documents between businesses and public administrations, owing to its ease of readability and efficient data processing capabilities._x000D_ _x000D_ UBL specification reference:_x000D_ https://docs.oasis-open.org/ubl/os-UBL-2.4/UBL-2.4.html'
'As the UBL specification is based on XML, it supports multilingualism by accommodating all writing systems. Consequently, any language can be used within XML. In this sense, XML can be encoded using formats such as UTF-8, ensuring that all languages are accurately represented in XML documents. Furthermore, the UBL specification complements this by providing a defined structure to manage multilingual texts within the document itself._x000D_ _x000D_ XML 1.1 W3C reference: _x000D_ https://www.w3.org/TR/xml11/_x000D_ _x000D_ UBL specification reference:_x000D_ https://docs.oasis-open.org/ubl/os-UBL-2.4/UBL-2.4.html'
'The UBL specification, based on XML, does not itself include built-in mechanisms for guaranteeing the authenticity or authentication of the roles or agents involved in data transactions. However, complementary specifications such as XAdES, an extension of XMLDSig, can be employed to address this need. XAdES enables the authentication of agents participating in data exchanges, thereby enhancing trust and accountability in electronic transactions._x000D_ _x000D_ XMLDSig specification:_x000D_ https://www.w3.org/TR/xmldsig-core/_x000D_ _x000D_ XAdES specification:_x000D_ https://www.w3.org/TR/XAdES/_x000D_ _x000D_ UBL specification reference:_x000D_ https://docs.oasis-open.org/ubl/os-UBL-2.4/UBL-2.4.html'
'The UBL specification does not offer any mechanism to provide access control. In this regard, there are complementary mechanisms and specifications that help to enhance data security, such as verifying whether data has been altered and protecting it, but none establishes access control mechanisms per se. Therefore, this criterion is not applicable to this specification._x000D_ _x000D_ UBL specification reference:_x000D_ https://docs.oasis-open.org/ubl/os-UBL-2.4/UBL-2.4.html'
'The UBL specification is intended to define a generic XML interchange format for business documents. In this context, XML serves as both a markup language and a file format for storing, transmitting, and reconstructing arbitrary data. It is particularly well-suited for publishing data on the web. In this regard, UBL supports the five stars in Tim Berners-Lee’s deployment scheme by enabling the linking of data to other resources. Specifically, the UBL specification allows attachments to be included, providing references to related documentation._x000D_ _x000D_ XML 1.1 W3C reference: _x000D_ https://www.w3.org/TR/xml11/_x000D_ _x000D_ Tim Berners-Lee 5 star open data: _x000D_ https://5stardata.info/en/_x000D_ _x000D_ UBL Reference:_x000D_ https://docs.oasis-open.org/ubl/UBL-2.4.html'
'The purpose of UBL is not related to e-accessibility. Therefore, this criterion is not applicable to this specification._x000D_ _x000D_ UBL specification reference:_x000D_ https://docs.oasis-open.org/ubl/os-UBL-2.4/UBL-2.4.html'
'The use of UBL offers many benefits for modelling business processes, including detailed textual descriptions, explanations, and examples for each of its specified functions and messages. It also provides clear rules for extension, alongside various subsets and tool resources._x000D_ _x000D_ UBL specification reference:_x000D_ https://docs.oasis-open.org/ubl/os-UBL-2.4/UBL-2.4.html'
'UBL is already associated to EIRA ABBs in the EIRA Library of Interoperability Specifications (ELIS). More _x000D_ specifically, UBL can define the interoperability aspects of the "Controlled Vocabulary", "Data Model" and "Ontology" ABBs of the EIRA Semantic View._x000D_ _x000D_ EIRA Library of Interoperability Specifications (ELIS):_x000D_ https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/611_x000D_ _x000D_ UBL specification reference:_x000D_ https://docs.oasis-open.org/ubl/os-UBL-2.4/UBL-2.4.html'
'The UBL specification is based on the XML standard, which enables the separation of information through the use of tags and attributes. This approach makes the structure of data clearer and more accessible for users working with it._x000D_ By leveraging XML, the UBL specification promotes comprehensibility, offering a straightforward and user-friendly method for understanding business documents._x000D_ _x000D_ UBL specification reference:_x000D_ https://docs.oasis-open.org/ubl/os-UBL-2.4/UBL-2.4.html'
'As defined by the OASIS Technical Committee (TC), the UBL TC plays an active role in the release lifecycle of the specification. External contributions to the committee are welcomed through open channels. To date, the UBL TC has announced several public reviews, each providing a specific period of time for users to submit comments. The most recent invitation for comment was issued in August 2025, concerning UBL v2.5 CSD01._x000D_ _x000D_ UBL OASIS Technical Committee reference:_x000D_ https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ubl_x000D_ _x000D_ Invitation to comment on UBL v2.5 CSD01 reference:_x000D_ https://groups.oasis-open.org/discussion/invitation-to-comment-on-ubl-v25-csd01_x000D_ _x000D_ UBL specification reference:_x000D_ https://docs.oasis-open.org/ubl/os-UBL-2.4/UBL-2.4.html'
'Similar to the XML specification, the UBL specification also supports partial implementations. While certain mandatory elements must be included, the specification offers over 4,000 business objects described as XML elements, which users can selectively adopt based on their specific requirements._x000D_ This flexibility allows implementers to include only the elements relevant to their use case, avoiding unnecessary complexity and streamlining integration._x000D_ _x000D_ XML customisation:_x000D_ https://www.xml.com/articles/2017/01/01/what-is-ubl/#d0e126_x000D_ _x000D_ Customisation and extension of UBL:_x000D_ https://docs.oasis-open.org/ubl/guidelines/UBL2-Customization1.0cs01.pdf_x000D_ _x000D_ UBL specification reference:_x000D_ https://docs.oasis-open.org/ubl/os-UBL-2.4/UBL-2.4.html'
'The UBL specification has been selected for referencing in public procurement, as it is mentioned in the Commission implementig decision of 31 October 2014 on the identification of Universal Business Language version 2.1 for referencing in public procurement._x000D_ _x000D_ "Commission implementig decision of 31 October 2014 on the identification of Universal Business Language version 2.1 for referencing in public procurement" document:_x000D_ https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32014D0771&qid=1754043193358_x000D_ _x000D_ UBL specification reference:_x000D_ https://docs.oasis-open.org/ubl/os-UBL-2.4/UBL-2.4.html'
'The UBL specification, based on XML, does not inherently provide protection against unauthorised changes to the information it represents. However, specifications such as XAdES and XMLDsig can help verify whether data has been altered at any point during the transaction, ensuring that the data is intact and exactly as originally sent._x000D_ _x000D_ XMLDSig specification:_x000D_ https://www.w3.org/TR/xmldsig-core/_x000D_ _x000D_ XAdES specification:_x000D_ https://www.w3.org/TR/XAdES/_x000D_ _x000D_ UBL specification reference:_x000D_ https://docs.oasis-open.org/ubl/os-UBL-2.4/UBL-2.4.html'
'The UBL specification is based on XML and offers a standardised data structure that facilitates the exchange of business documents between organisations. Therefore, the specification is ideal for avoiding manual procedures, making the process more efficient, and ensuring that all organisations are capable of reading the exchanged data._x000D_ _x000D_ UBL specification reference:_x000D_ https://docs.oasis-open.org/ubl/os-UBL-2.4/UBL-2.4.html'
'UBL is based on the XML specification, which supports various mechanisms to protect data and enhance security against unauthorised changes. It can be complemented by other specifications such as XAdES and XMLDSig, which enable verification of whether data has been modified at any stage of the transaction. These complementary specifications and security mechanisms offer a range of capabilities to ensure that the data is as accurate and reliable as possible._x000D_ _x000D_ XMLDSig specification:_x000D_ https://www.w3.org/TR/xmldsig-core/_x000D_ _x000D_ XAdES specification:_x000D_ https://www.w3.org/TR/XAdES/_x000D_ _x000D_ UBL specification reference:_x000D_ https://docs.oasis-open.org/ubl/os-UBL-2.4/UBL-2.4.html'
'The UBL specification is based on XML and, as such, supports security mechanisms applicable to XML, including XML Digital Signatures (XMLDSig), XAdES, and others._x000D_ To ensure a certain level of data protection, the specification allows for methods such as information encryption and digital signing. These measures help safeguard the integrity and confidentiality of the data exchanged, ensuring that documents are transmitted securely and remain unaltered by unauthorised parties._x000D_ _x000D_ XMLDSig specification:_x000D_ https://www.w3.org/TR/xmldsig-core/_x000D_ _x000D_ XAdES specification:_x000D_ https://www.w3.org/TR/XAdES/_x000D_ _x000D_ UBL specification reference:_x000D_ https://docs.oasis-open.org/ubl/os-UBL-2.4/UBL-2.4.html'
'The UBL specification does not depend on any specific technology and is entirely agnostic with respect to web infrastructure. Moreover, as it is based on XML, which itself is technology-agnostic, the UBL specification is considered fully independent of underlying technological platforms._x000D_ This neutrality allows UBL to be implemented across a wide range of systems and environments, enhancing its adaptability and long-term relevance._x000D_ _x000D_ UBL technology and platform agnostic reference:_x000D_ https://www.ibiblio.org/bosak/ubl/pres/generic-ubl-overview.pdf_x000D_ _x000D_ UBL specification reference:_x000D_ https://docs.oasis-open.org/ubl/os-UBL-2.4/UBL-2.4.html'
'The UBL specification enables companies around the world to exchange electronic documents in a common language, while allowing adaptation to the fiscal requirements of each receiving country._x000D_ By conforming to UBL, all business document types remain machine-readable, thereby enhancing interoperability between systems. This standardised approach to document exchange ensures consistency, efficiency, and seamless integration across diverse platforms and jurisdictions._x000D_ _x000D_ b2brouter UBL:_x000D_ https://www.b2brouter.net/global/what-is-ubl-format/_x000D_ _x000D_ UBL specification reference:_x000D_ https://docs.oasis-open.org/ubl/os-UBL-2.4/UBL-2.4.html'
'UBL facilitates and simplifies the delivery of European public services by enabling automated data transactions. Additionally, the specification is based on XML, which provides a standardised data structure that eases interpretation by information systems. As a result, the need for manual intervention and more complex procedures can be avoided, thereby streamlining and simplifying the delivery of public services._x000D_ _x000D_ UBL specification reference:_x000D_ https://docs.oasis-open.org/ubl/os-UBL-2.4/UBL-2.4.html'
'The UBL specification does not rely on any particular platform and is entirely agnostic in this regard. Additionally, as it is based on XML, which functions across all browsers and applications that support it, the UBL specification is considered platform-agnostic._x000D_ This broad compatibility ensures that UBL can be implemented in diverse technological environments without requiring platform-specific adaptations._x000D_ _x000D_ UBL technology and platform agnostic reference:_x000D_ https://www.ibiblio.org/bosak/ubl/pres/generic-ubl-overview.pdf_x000D_ _x000D_ UBL specification reference:_x000D_ https://docs.oasis-open.org/ubl/os-UBL-2.4/UBL-2.4.html'
'The UBL specification is based on XML, and therefore supports all mechanisms applicable to the XML standard. In this context, technologies such as encryption and the XML Signature Syntax and Processing specification (XMLDSig) can be applied to UBL documents. These mechanisms help ensure that data remains inaccessible to unauthorised parties during transmission and that the information received has not been altered in transit, thereby preserving both confidentiality and integrity._x000D_ _x000D_ XMLDSig specification:_x000D_ https://www.w3.org/TR/xmldsig-core/_x000D_ _x000D_ XAdES specification:_x000D_ https://www.w3.org/TR/XAdES/_x000D_ _x000D_ UBL specification reference:_x000D_ https://docs.oasis-open.org/ubl/os-UBL-2.4/UBL-2.4.html'
'The UBL specification is based on XML, which supports other specifications such as XAdES. In this context, the digital signature features of UBL, particularly through integration with XAdES, provide the technical means to ensure the integrity, authenticity, and long-term validity of the data contained in UBL documents._x000D_ _x000D_ XAdES specification:_x000D_ https://www.w3.org/TR/XAdES/_x000D_ _x000D_ UBL specification reference:_x000D_ https://docs.oasis-open.org/ubl/os-UBL-2.4/UBL-2.4.html'
'As an XML-based specification, UBL enables consistent data reuse across systems. Although it does not include explicit provisions dedicated to this topic, its foundation in XML inherently supports structured, repeatable data handling. The specification defines a set of rules for encoding documents in both human-readable and machine-readable formats, thereby enhancing data reusability and promoting interoperability between systems and services._x000D_ _x000D_ UBL specification reference:_x000D_ https://docs.oasis-open.org/ubl/os-UBL-2.4/UBL-2.4.html'
'Implementations of the UBL specification can be assessed through the Interoperability Test Bed, available on the Interoperable Europe Portal. Specifically, the Interoperability Test Bed includes a dedicated page to validate UBL XML implementations. Additionally, there are other platforms available online for validating UBL implementations._x000D_ _x000D_ ITestBed UBL XML validator:_x000D_ https://www.itb.ec.europa.eu/ubl/upload_x000D_ _x000D_ UBL specification reference:_x000D_ https://docs.oasis-open.org/ubl/os-UBL-2.4/UBL-2.4.html'
'The Interoperable Europe Portal platform comprises a large European community of developers, some of whom focus on UBL implementations. Additionally, the specification is also discussed on other forums, such as Stack Overflow, where implementations and questions regarding the specification are addressed._x000D_ _x000D_ UBL Interoperable Europe Portal:_x000D_ https://interoperable-europe.ec.europa.eu/collection/ict-standards-procurement/solution/ubl-universal-business-language-ubl_x000D_ _x000D_ UBL Stackoverflow_x000D_ https://stackoverflow.com/questions/tagged/ubl_x000D_ _x000D_ UBL specification reference:_x000D_ https://docs.oasis-open.org/ubl/os-UBL-2.4/UBL-2.4.html'
'The OASIS Technical Committee, in charge of the development of UBL, operates under RF (royalty-free) on RAND Mode of the UBL IPR Policy. Therefore, the specification is licensed on a (F)RAND basis._x000D_ _x000D_ IPR Policy:_x000D_ https://www.oasis-open.org/policies-guidelines/ipr/_x000D_ _x000D_ UBL specification reference:_x000D_ https://docs.oasis-open.org/ubl/os-UBL-2.4/UBL-2.4.html'
Assessment of the XAdES Baseline Profile with the Common Assesssment Method for Standards and Specifications (CAMSS)
Assessment of the XAdES Baseline Profile EIF Scenario v1.0.0
'The XAdES specification can be found used in different European projects and also by Member States. Since it is suitable for advanced electronic signatures, it is used by companies and public administrations to sign documents. In this sense, the specification has been selected within the CEF Digital Signature Service (DSS) along with CAdES, ASiC and PAdES Baseline profiles. _x000D_ _x000D_ Digital Signature Service is an open-source software library for electronic signature creation and validation supporting the interoperability of electronic signatures. The initiative is an enabler for cross borders interoperability between administrations and businesses._x000D_ _x000D_ Applications such as eCoSignature from the Ministry of Industry and Commerce of Spain use XAdES as their base. _x000D_ _x000D_ eCoSignature reference:_x000D_ https://firmaelectronica.gob.es/en/ciudadanos/cosas-deberias-saber/formatos-firma_x000D_ _x000D_ DSS reference:_x000D_ https://ec.europa.eu/cefdigital/DSS/webapp-demo/doc/dss-documentation.html_x000D_ _x000D_ eSignatureHub - Digital Signature Service DSS:_x000D_ https://ec.europa.eu/digital-building-blocks/sites/spaces/DIGITAL/pages/467109107/Digital+Signature+Service+-+DSS_x000D_ _x000D_ XAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31913201/01.02.01_60/en_31913201v010201p.pdf'
'XAdES is maintained by ETSI, one of the European Agencies for Standardisation, specifically by the ETSI Technical Committee Electronic Signatures and Trust Infrastructures (ESI)._x000D_ _x000D_ ETSI reference:_x000D_ https://www.etsi.org/about_x000D_ _x000D_ Electronic Signatures and Trust Infrastructures (ESI) reference:_x000D_ https://www.etsi.org/committee/1399-esi_x000D_ _x000D_ XAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31913201/01.02.01_60/en_31913201v010201p.pdf'
'The XAdES Baseline Profile is based on XML and XML documents are based on Unicode, which supports all writing systems. Therefore, any language can be used in an XML document. Additionally, XML (both 1.0 and 1.1) can be encoded using formats like UTF-8, ensuring that all languages can be properly included and represented in XML documents. In addition, it is worth mentioning that in the XML 1.0 specification is mentioned that all XML processors must accept the UTF-8 and UTF-16 encodings of Unicode. However, certain Unicode encodings, like UTF-16, can result in larger file sizes compared to single-byte encodings, potentially impacting storage and transmission efficiency._x000D_ _x000D_ UTF-8 reference: _x000D_ https://www.rfc-editor.org/rfc/rfc3629_x000D_ _x000D_ UTF-16 reference: https://www.iso.org/standard/76835.html _x000D_ _x000D_ XML 1.0 reference: _x000D_ https://www.w3.org/TR/xml/ _x000D_ _x000D_ XML 1.1 W3C reference:_x000D_ https://www.w3.org/TR/xml11_x000D_ _x000D_ XAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31913201/01.02.01_60/en_31913201v010201p.pdf'
"XAdES is included in 5 national catalogues of recommended specifications. They belong to Croatia, Cyprus, France, Poland and Spain. The National Interoperability Framework (NIF) of Spain and France are aligned with at least 3 out of 4 scoreboards of the EIF Monitoring according to the National Interoperability Framework Observatory (NIFO) factsheets._x000D_ _x000D_ CAMSS List of Standards:_x000D_ https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards_x000D_ _x000D_ NIFO Factsheets:_x000D_ https://interoperable-europe.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public-administration-factsheets-2024_x000D_ _x000D_ France's catalogue:_x000D_ https://www.numerique.gouv.fr/offre-accompagnement/reference-interoperabilite-rgi/_x000D_ _x000D_ Spains's catalogue:_x000D_ https://administracionelectronica.gob.es/pae_Home/dam/jcr:97912041-c1c3-47c4-b517-df9f51db321d/Guia_aplicacion_Norma_Tecnica_Interoperabilidad_Catalogo_de_estandares.pdf_x000D_ _x000D_ Poland's catalogue:_x000D_ http://isap.sejm.gov.pl/isap.nsf/download.xsp/WDU20170002247/O/D20172247.pdf_x000D_ _x000D_ Cyprus catalogue:_x000D_ https://dits.dmrid.gov.cy/dmrid/dits/dits.nsf/all/B83AA8E4EB4EFD19C225855800288B10/$file/Cyprus%20eGovernment%20Interoperability%20Framework_new%20EIF_v2.0-To%20Publish.pdf_x000D_ _x000D_ Croatia's catalogue:_x000D_ https://ssi.gov.hr/en/catalogue_x000D_ _x000D_ XAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31913201/01.02.01_60/en_31913201v010201p.pdf"
'XAdES was originally developed by W3C and has become one of the main ways to develop suitable security controls and mechanisms in place to protect digital transactions and to ensure trust and confidence among organisations. The XAdES Baseline Profile specification has evolved through several minor and one major releases to address emerging requirements and refine the specfication documentation (which can be superseeded by national recommendations in Europe). According to the change history section of the XAdES specification, the first official release dates back to December 2011, with continuous improvements. It is important to note that the latest version is 1.3.1 (released in July 2024), addressing bug fixes or incremental changes._x000D_ _x000D_ The version 1.2.1 includes core functionalities, but subsequent versions—culminating in 1.3.1—have introduced enhancements, particularly related to the ArchiveTimeStamp element. These updates improve the handling of the signature date in the counter-signature process, enhancing long-term validation and compliance with archival standards, which enables the evolution of electronic signature to evolving digital signature requirements._x000D_ _x000D_ W3C XML Advanced Electronic Signatures (XAdES): _x000D_ https://www.w3.org/TR/XAdES/_x000D_ _x000D_ XAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31913201/01.02.01_60/en_31913201v010201p.pdf'
'The purpose of the XAdES baseline Profile is not related to data processing but with the usage of some XML based complimentary specifications like W3C XML Encryption Syntax and Processing it can be assured that data remains inaccessible and in the same form as it was sent._x000D_ _x000D_ XML Encryption Syntax and Processing reference:_x000D_ https://www.w3.org/TR/xmlenc-core1/ _x000D_ _x000D_ XAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31913201/01.02.01_60/en_31913201v010201p.pdf'
'The XAdES baseline Profile main purpose is to provide the stakeholders involved in any electronic transaction with the certainty that the exchanged documents are truthful for all. _x000D_ In this sense there are other XML based specifications that can complement XAdES, specifications like W3C XML Encryption Syntax and Processing, that provides the stakeholders with the capabilities to encrypt electronic transactions thus fostering security._x000D_ _x000D_ XML Encryption Syntax and Processing reference:_x000D_ https://www.w3.org/TR/xmlenc-core1/_x000D_ _x000D_ XAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31913201/01.02.01_60/en_31913201v010201p.pdf'
'XAdES Baseline Profile is a business sector agnostic specification which is reusable beyond the domain for which it was developed. Specifically, implemented to facilitate the electronic signature in compliance with eIDAS._x000D_ _x000D_ eIDAS regulation:_x000D_ https://digital-strategy.ec.europa.eu/en/policies/eidas-regulation_x000D_ _x000D_ XAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31913201/01.02.01_60/en_31913201v010201p.pdf'
"The XAdES Baseline Profile is designed to guarantee the authenticity and authentication of the agents involved in data transactions. It achieves this by focusing on the signer's identity and their role, which is a core requirement of the eIDAS regulation._x000D_ _x000D_ eIDAS Regulation:_x000D_ https://digital-strategy.ec.europa.eu/en/policies/eidas-regulation_x000D_ _x000D_ XAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31913201/01.02.01_60/en_31913201v010201p.pdf"
'The XAdES Baseline Profile specifies profiles based on XMLDSig that ensure compliance with European legal requirements. XAdES guarantees that signed data remains authentic, integral, and legally defensible when transmitted or archived. Additionally, the specification can be combined with other mechanisms such as XML encryption or XMLDSig itself, allowing selective use of its XML-compliant parts to further enhance security capabilities._x000D_ _x000D_ W3C XML Signature Syntax and Processing Version 1.1: _x000D_ https://www.w3.org/TR/xmldsig-core/_x000D_ _x000D_ XAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31913201/01.02.01_60/en_31913201v010201p.pdf'
'The purpose of the XAdES Baseline Profile is not related to e-accessibility. Therefore, this criterion is not applicable to this specification._x000D_ _x000D_ XAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31913201/01.02.01_60/en_31913201v010201p.pdf'
'The XAdES Baseline Profile includes mechanisms for long-term validation, such as timestamps and embedded certificate information. This means that a signed public record or contract can be securely archived and remain legally verifiable for some time. In this sense the preservation of the date of signature is a partial preservation of the record._x000D_ _x000D_ XAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31913201/01.02.01_60/en_31913201v010201p.pdf'
'The effectiveness of the XAdES specification has been assessed by several individual authors at the Open Identity Summit 2019, dedicated to link practical experiences and requirements with academic innovations. The "Security Analysis of XAdES Validation in the CEF Digital Signature Services (DSS)" study, addresses XAdES as a key functionality of the demonstration service of the Digital Signature Services (DSS) of the Connecting Europe Facility (CEF). The research focuses specifically on the signature verification functionality for XAdES implemented by this service, noting that DSS enables the validation of generic XAdES to verify arbitrarily signed XML documents. Furthermore, it highlights that XAdES is one of the signature formats supported by the DSS library, in line with the eIDAS regulation and compliant with the relevant ETSI standards._x000D_ _x000D_ "Security Analysis of XAdES Validation in the CEF Digital Signature Services (DSS)" study:_x000D_ https://dl.gi.de/items/17c4b8a1-e160-40a5-b598-28e27ae3018d_x000D_ _x000D_ XAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31913201/01.02.01_60/en_31913201v010201p.pdf'
'The XAdES Baseline Profile function is to facilitate the electronic signature in compliance with eIDAS regulation. The signature of a document can provide the involved stakeholders with the possibility to use the extensions (like XML encryption specification and other complementary specifications) on the schema in order to define specific legal or policy references relevant to the context of the signed document like confidentiality._x000D_ _x000D_ eIDAS Regulation:_x000D_ https://digital-strategy.ec.europa.eu/en/policies/eidas-regulation_x000D_ _x000D_ XAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31913201/01.02.01_60/en_31913201v010201p.pdf'
"XAdES is within the European eIDAS regulation which is legally binding for all EU members states._x000D_ Also, XAdES is a core element in some EU countries digital government initiatives, like Belgium's e-procurement system or Poland's financial report signatures._x000D_ _x000D_ Belgium's e-procurement reference:_x000D_ https://bosa.service-now.com/csp?id=kb_article_view&sys_kb_id=fca9cf651ba3b5543ff06421b24bcb98_x000D_ _x000D_ Poland's financial report signatures reference:_x000D_ https://www.podatki.gov.pl/komunikaty-techniczne/sprawozdania-finansowe-osob-fizycznych-w-formacie-xades/_x000D_ _x000D_ eIDAS Regulation:_x000D_ https://digital-strategy.ec.europa.eu/en/policies/eidas-regulation_x000D_ _x000D_ XAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31913201/01.02.01_60/en_31913201v010201p.pdf"
'The efficiency of the XAdES specification has been assessed by the Department of Computer Science at the University of Brasília (UnB). The "A Digital Signature Model Using XAdES Standard as a REST Service" study, addresses XAdES as the essential technological and regulatory foundation for the implementation of digital signatures in university diplomas in Brazil. Although it addresses certain capabilities of XAdES, rather than the XAdES Baseline, a general overview of XAdES, which is the same in both cases, is provided._x000D_ _x000D_ "A Digital Signature Model Using XAdES Standard as a REST Service" study:_x000D_ https://www.mdpi.com/2078-2489/12/8/289_x000D_ _x000D_ XAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31913201/01.02.01_60/en_31913201v010201p.pdf'
'The purpose of the XAdES Baseline Profile is not related to modelling business processes. Therefore, this criterion is not applicable to this specification._x000D_ _x000D_ XAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31913201/01.02.01_60/en_31913201v010201p.pdf'
'The XAdES Baseline Profile is a set of well-defined technical specifications developed by ETSI to ensure both interoperability and legal validity of electronic signatures across Europe, in line with the eIDAS Regulation._x000D_ _x000D_ The specification includes several signature levels: XAdES-B-B, XAdES-B-T, XAdES-B-LT, and XAdES-B-LT, which can be implemented individually based on the desired properties. These levels are designed to be incremental, meaning that a basic signature (e.g. XAdES-B-B) can be progressively enhanced to include additional features like timestamps or long-term validation data, depending on user or system requirements._x000D_ _x000D_ eIDAS regulation: https://digital-strategy._x000D_ ec.europa.eu/en/policies/eidas-regulation_x000D_ _x000D_ XAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31913201/01.02.01_60/en_31913201v010201p.pdf'
"XAdES Baseline Profile guarantees authenticity by cryptographically linking the signature to a specific individual and their certificate. It enables the authentication of roles by providing a dedicated element for including this information within the signature, which is a powerful feature for applications where the signer's function is as important as their identity. In this sense the schema based on XML provides with enough flexibility to include some control mechanisms based on the signature identity._x000D_ _x000D_ XAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31913201/01.02.01_60/en_31913201v010201p.pdf"
'The XAdES Baseline Profile provides the involved stakeholders with a legally binding signature structure to formalise interoperability agreements. In this sense it provides the foundation of any agreement among any kind of participants._x000D_ The specification also fosters and facilitates agreements by establishing a common method for signing documents and data in a secure and trustworthy manner. This enables documents to be exchanged in an interoperable way, ensuring that all parties can access the documents and trust the information or data contained within them. By providing a standardised approach, XAdES helps to build confidence between parties and supports the reliable execution of digital transactions._x000D_ _x000D_ XAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31913201/01.02.01_60/en_31913201v010201p.pdf'
'The XAdES is not related to data portability of data between systems/applications. Therefore this criterion is not applicable._x000D_ _x000D_ XAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31913201/01.02.01_60/en_31913201v010201p.pdf_x000D_ '
'XAdES Baseline Profile function is to facilitate the electronic signature in compliance with eIDAS. In this sense,the specification provides with the "The Signing Certificate" element, which is the public key certificate of the person or entity who signed the document and the timestamp information. This means that a system receiving the signed document doesn't need to perform an entirely new validation process from scratch. It can reuse the included data to verify the signature's authenticity._x000D_ _x000D_ XAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31913201/01.02.01_60/en_31913201v010201p.pdf'
'The XAdES Baseline Profile helps users understand the logic behind electronic signatures. XAdES achieves this by organising information in the XML through the use of tags, which separate different pieces of data and provide a clear, structured format. This separation and clarity make it easier for users to comprehend the details of the signature._x000D_ Furthermore, XAdES builds upon the XMLDSig framework, which is widely supported by applications like PDF viewers. These applications enhance user understanding by visually displaying key information such as whether the signature is valid, the date it was timestamped, and other relevant properties in a simple and straightforward way._x000D_ A practical example of this is the CEF Digital Signature Service (DSS), which leverages XAdES to provide clear and verifiable electronic signatures. Through DSS, users can easily verify signature validity and timestamp information, helping improve trust and transparency in electronic communications._x000D_ _x000D_ eIDAS regulation:_x000D_ https://digital-strategy.ec.europa.eu/en/policies/eidas-regulation_x000D_ _x000D_ DSS reference:_x000D_ https://ec.europa.eu/cefdigital/DSS/webapp-demo/doc/dss-documentation.html_x000D_ _x000D_ XMLDSig reference_x000D_ https://www.w3.org/TR/xmldsig-core1/_x000D_ _x000D_ XAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31913201/01.02.01_60/en_31913201v010201p.pdf'
'The XAdES Baseline Profile function is to facilitate the electronic signature in compliance with eIDAS regulation. In this sense, the specification, in conjuction with other specifications such as CAdES, ASiC and PAdES can enable the visibility of administrative procedures, as shown with the CEF Digital Signature Service (DSS). It is worth mentioning that the specification is encoded in a machine- and human-readable text format. Thus, it can be used in a variety of environments._x000D_ _x000D_ eIDAS regulation:_x000D_ https://digital-strategy.ec.europa.eu/en/policies/eidas-regulation_x000D_ _x000D_ DSS reference:_x000D_ https://ec.europa.eu/cefdigital/DSS/webapp-demo/doc/dss-documentation.html_x000D_ _x000D_ XAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31913201/01.02.01_60/en_31913201v010201p.pdf'
'XAdES does not directly define or expose technical interfaces for accessing public administration services._x000D_ However, the specification provides a standardised, machine- and human-readable structure for electronic signatures, which facilitates interaction between citizens and public administrations when submitting information through public administration portals. By using the XML format, the specification eases such communication and the presentation of information through interfaces._x000D_ _x000D_ eIDAS regulation:_x000D_ https://digital-strategy.ec.europa.eu/en/policies/eidas-regulation_x000D_ _x000D_ DSS reference:_x000D_ https://ec.europa.eu/cefdigital/DSS/webapp-demo/doc/dss-documentation.html_x000D_ _x000D_ XAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31913201/01.02.01_60/en_31913201v010201p.pdf'
'The purpose of the XAdES baseline Profile is not related to data accuracy but the specification can be complemented with other specifications like XML Encryption Syntax and Processing to ensure that signed data remains inaccessible to unauthorised changes and thus remains in the same form as sent by the sender. Apart from that, the specification allows verification of any changes made to the document. When a document is signed, a hash code is generated by XAdES, so if the document is modified, the hash will not match and the verification process will fail. This way, it can be detected if the document has been altered._x000D_ _x000D_ XML Encryption Syntax and Processing reference:_x000D_ https://www.w3.org/TR/xmlenc-core1/ _x000D_ _x000D_ XAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31913201/01.02.01_60/en_31913201v010201p.pdf'
"The XAdES baseline Profile has sparked some online communites that discuss the specification's implementation as well as the data related to it._x000D_ It also created numerous questions and debates on developer forums like stackoverflow._x000D_ _x000D_ IBM TechXchange:_x000D_ https://community.ibm.com/community/user/discussion/xml-xades-with-webmethods_x000D_ _x000D_ Stack-overflow communities and discussions:_x000D_ https://stackoverflow.com/questions/tagged/xades_x000D_ _x000D_ XAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31913201/01.02.01_60/en_31913201v010201p.pdf"
'The XAdES is not related to publication of data on the web. Therefore this criterion is not applicable._x000D_ _x000D_ XAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31913201/01.02.01_60/en_31913201v010201p.pdf'
'ETSI has provided a conformance testing tool for electronic signatures. The conformity testing tool involves different standards applied in the development of eSignatures, including PAdES, CAdES and XAdES and their respective baseline profiles. _x000D_ _x000D_ Conformance Checker reference:_x000D_ https://signatures-conformance-checker.etsi.org/pub/index.shtml_x000D_ _x000D_ XAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31913201/01.02.01_60/en_31913201v010201p.pdf'
'While the primary purpose of the XAdES Baseline Profile may not be solely focused on data integrity, its design supports mechanisms that uphold it. The extensible syntax allows stakeholders to incorporate additional fields that can facilitate the detection of unauthorised changes, thereby reinforcing document integrity. Moreover, when combined with complementary XML-based specifications such as W3C XML Encryption Syntax and Processing, the framework enables robust data encryption, further enhancing the protection and trustworthiness of the exchanged information._x000D_ _x000D_ XML Encryption Syntax and Processing reference:_x000D_ https://www.w3.org/TR/xmlenc-core1/ _x000D_ _x000D_ XAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31913201/01.02.01_60/en_31913201v010201p.pdf'
CAMSS Assessment of OAS EIF Scenario v2.0.0
Assessment of the OAS with the Common Assesssment Method for Standards and Specifications (CAMSS)
'OAS supports the delivery of European public services by providing a clear structure for designing and describing APIs, including their security requirements. It helps reduce administrative burden by keeping API documentation aligned with the source code and enabling users to understand and use APIs without needing to know their technical implementation._x000D_ _x000D_ OpenAPI Specification Reference:_x000D_ https://spec.openapis.org/oas/v3.1.0.html'
'Despite the OAS being adopted by numerous organisations and projects, it does not explicitly address or cover privacy aspects. Therefore, this criterion is considered not applicable to this specification._x000D_ _x000D_ OpenAPI Specification Reference:_x000D_ https://spec.openapis.org/oas/v3.1.0.html'
'OAS does not directly address long-term data preservation, but its standardised and technology-independent format helps maintain the accessibility and reuse of API documentation over time, preserving knowledge about data and system interactions._x000D_ _x000D_ OpenAPI Specification Reference:_x000D_ https://spec.openapis.org/oas/v3.1.0.html'
'Many leading organisations and platforms use OpenAPI Specification (OAS) to achieve market acceptance for their APIs, as it provides a widely recognised, standardised way to describe RESTful services.The real-world examples of GitHub, Stripe, Postman, Netflix, Twilio, Kubernetes, Axway, MuleSoft, Nest, and Plaid underscore its versatility and effectiveness in diverse domains. _x000D_ _x000D_ A statement of some of this real world examples are Netfilx with having a complex microservices architecture that requires seamless communication between various services. The company uses OpenAPI to ensure well-defined contracts between their microservices, making it easier to manage and scale their infrastructure._x000D_ _x000D_ Another statement is Twilio, a cloud communications platform that provides a suite of communication APIs, leverages OpenAPI to help developers understand and use their APIs quickly. Through detailed documentation generated from OpenAPI definitions, Twilio ensures that new developers can get up to speed rapidly._x000D_ _x000D_ Examples of real-world usages:_x000D_ https://openapispec.com/docs/what/what-are-some-real-world-examples-of-openapi-usage/_x000D_ _x000D_ OpenAPI Specification Reference:_x000D_ https://spec.openapis.org/oas/v3.2.0.html'
'OAS does not implement security itself but provides a standardised description of the security mechanisms required to protect API resources. It allows API designers to specify authentication and authorisation methods, such as OAuth2, OpenID Connect, API keys, and HTTP authentication, through defined security schemes._x000D_ _x000D_ OAS Security Requirements Object:_x000D_ https://spec.openapis.org/oas/latest.html#security-requirement-object_x000D_ _x000D_ OpenAPI Specification Reference:_x000D_ https://spec.openapis.org/oas/v3.1.0.html'
'OAS is already associated to EIRA ABBs in the EIRA Library of Interoperability Specifications (ELIS). More _x000D_ specifically, OAS can define the interoperability aspects of the "API", "API Manager", "Machine to Machine", "Data Space" and "Web Service" ABBs of the EIRA Technical View-Application._x000D_ _x000D_ ELIS Refrence:_x000D_ https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/611_x000D_ _x000D_ OpenAPI Specification Reference:_x000D_ https://spec.openapis.org/oas/v3.1.0.html'
'The purpose of OAS is not related to the reuse of information, therefore this criterion is not applicable to this specification._x000D_ _x000D_ OpenAPI Specification Reference:_x000D_ https://spec.openapis.org/oas/v3.1.0.html'
'OAS does not itself provide mechanisms to protect information against unauthorised changes. It serves to describe APIs and may include documentation of security measures. Therefore, this criterion is not directly applicable to the specification._x000D_ _x000D_ OpenAPI Specification Reference:_x000D_ https://spec.openapis.org/oas/latest.html#openapi-specification_x000D_ _x000D_ OpenAPI Specification Reference:_x000D_ https://spec.openapis.org/oas/v3.1.0.html'
'The efficiency of the OpenAPI specfication has been assed by the Institute of Electrical and_x000D_ Electronics Engineers (IEEE), dedicated to standardisation and development in technical areas.In the “Automatic Generation of Test Cases for REST APIs: A Specification-Based Approach” study, adresses how the REpresentation State Transfer (REST) has gained momentum as the preferred technique to design Web APIs but lacks of a specification to describe how to create/consume REST APIs, thus creating new challenges for their integration, testing and verification._x000D_ _x000D_ Automatic Generation of Test Cases for REST APIs: A Specification-Based Approach: https://ieeexplore.ieee.org/abstract/document/8536162_x000D_ _x000D_ OpenAPI Specification Reference:_x000D_ https://spec.openapis.org/oas/v3.1.0.html'
'OAS is included in two national catalogues of recommended specifications. They belong to Malta and The Netherlands. The national interoperability framework of The Netherlands is fully alligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. Malta, nonetheless, does not have a high performance, being aligned only with two sections of the EIF. _x000D_ _x000D_ National Catalogue of The Netherlands:_x000D_ https://www.forumstandaardisatie.nl/open-standaarden_x000D_ _x000D_ National Catalogue of Malta:_x000D_ https://mccaa.org.mt/Section/Content?contentId=1243_x000D_ _x000D_ CAMSS List of Standards: _x000D_ https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards_x000D_ _x000D_ OpenAPI Specification Reference:_x000D_ https://spec.openapis.org/oas/v3.1.0.html_x000D_ _x000D_ NIFO Factsheets: _x000D_ https://interoperable-europe.ec.europa.eu/collection/iopeu-monitoring/digital-public-administration-factsheets-2024'
'OAS development is guided by the Techincal Steering Commitee (TSC) a group of committers in charge of _x000D_ implementing new versions of the specification. Moreover, the OAS has support from the community in _x000D_ Github, where anyone interested is encouraged to pull requests and give feedback on its implementation._x000D_ _x000D_ TSC Working Group Reference:_x000D_ https://www.openapis.org/about/technical-developer-community_x000D_ _x000D_ OpenAPI Specification Reference:_x000D_ https://spec.openapis.org/oas/v3.2.0.html_x000D_ _x000D_ OpenAPI Specification in Github:_x000D_ https://github.com/OAI/OpenAPI-Specification_x000D_ '
'Through the Github platform, the OAS community is encharged of reviewing all the releases as well as _x000D_ raising issues and proposing improvements. Although the specification does not contemplate a specific session or section to leave feedback about a specific minor or major release, it allows people to contribute by reviewing the contributing process so users can understand how the specification is evolving. Also, sessions where feedback is collected are open to the community, and all users can see the comments that have been made._x000D_ _x000D_ OpenAPI Specification Reference:_x000D_ https://spec.openapis.org/oas/v3.1.0.html_x000D_ _x000D_ OpenAPI Specification in Github:_x000D_ https://github.com/OAI/OpenAPI-Specification/#participation'
'OAS specification is included in 2 Member States catalogues of recommended specifications. These _x000D_ Member States are Malta and The Netherlands._x000D_ _x000D_ Malta ICT National Catalogue Reference:_x000D_ https://mccaa.org.mt/Section/Content?contentId=1243_x000D_ _x000D_ Netherlands ICT National Catalogue Reference:_x000D_ https://www.forumstandaardisatie.nl/open-standaarden/lijst_x000D_ _x000D_ OpenAPI Specification Reference:_x000D_ https://spec.openapis.org/oas/v3.1.0.html_x000D_ _x000D_ CAMSS list of standards:_x000D_ https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
'Conformance of OpenAPI implementations is supported by the official conformance test suite maintained by Swagger with the support of SMARTBEAR. It provides a collection of valid and invalid example files used by tools to verify adherence to the specification. _x000D_ _x000D_ OpenAPI Conformance Test Reference:_x000D_ https://swagger.io/solutions/api-testing/_x000D_ _x000D_ SMARTBEAR Reference:_x000D_ https://smartbear.com/solutions/api-lifecycle/openapi-spec/_x000D_ _x000D_ OpenAPI Specification Reference:_x000D_ https://spec.openapis.org/oas/v3.1.0.html'
'OAS does facilitate the publication of data on the Web since it defines a standard, language-agnostic interface to HTTP APIs which allows both humans and computers to discover and understand the capabilities of the service without access to source code or documentation, or through network traffic inspection. A use of OAS is the automated generation of API portals and documentation, generally by using JSON. This tooling automatically displays the API in a user-friendly format, effectively producing a detailed web interface or API portal that outlines every available endpoint._x000D_ _x000D_ OpenAPI Specification Reference:_x000D_ https://spec.openapis.org/oas/v3.1.0.html_x000D_ _x000D_ JSON Specification Reference:_x000D_ https://jsonapi.org/format/'
'OAS serves as a framework for the development and documentation of APIs, it allows for customisation provided that the defined structure of the specification is respected. In this sense, the specification permits the inclusion of additional information or extensions while maintaining the core structure and integrity of the standard._x000D_ _x000D_ OpenAPI Specification Reference:_x000D_ https://spec.openapis.org/oas/v3.1.0.html'
'OAS simplifies the delivery of European public services by promoting interoperability and reuse of digital components. For example, the European Data Portal uses OAS-based APIs to expose and integrate open datasets across Member States, enabling consistent, secure, and efficient data exchange between public administrations and users._x000D_ _x000D_ OpenAPI Specification Reference:_x000D_ https://spec.openapis.org/oas/v3.1.0.html_x000D_ _x000D_ European Data Portal Reference:_x000D_ https://dataeuropa.gitlab.io/data-provider-manual/pdf/documentation_data-europa-eu_V1.2.pdf'
'The effectiveness of the OpenAPI specfication has been assed by the Institute of Electrical and_x000D_ Electronics Engineers (IEEE), dedicated to standardisation and development in technical areas. In the “Analyzing OpenAPI Specifications for Security Design Issues” study, the OpenAPI specification is approached as the fundamental and standardised input for carrying out a semi-automatic design security analysis of web service APIs._x000D_ _x000D_ Analyzing OpenAPI Specifications for Security Design Issues:_x000D_ https://ieeexplore.ieee.org/abstract/document/9652639_x000D_ _x000D_ OpenAPI Specification Reference:_x000D_ https://spec.openapis.org/oas/v3.1.0.html'
'Applications built on OpenAPI interface files can automatically generate documentation for methods, parameters, and models. This ensures that documentation, client libraries, and source code remain synchronised, therefore supporting data portability across systems._x000D_ _x000D_ OpenAPI Specification Reference:_x000D_ https://spec.openapis.org/oas/v3.1.0.html'
'Despite OAS is not included in an open repository/catalgue of standards at the European level, CENELEC provides a dedicated API portal where it publishes and manages a comprehensive catalogue of APIs, all of which are formally documented using the OpenAPI Specification (OAS) to ensure consistent, machine-readable definitions for developers._x000D_ _x000D_ CENELEC Catalogue of API Reference:_x000D_ https://api-portal.cenelec.eu/_x000D_ _x000D_ OpenAPI Specification Reference:_x000D_ https://spec.openapis.org/oas/v3.1.0.html'
'OAS can facilitate the interoperability agreements by providing a standardised description for APIs, enabling the documentation of security mechanisms, and streamlining the tasks required to work with APIs from other organisations._x000D_ _x000D_ OpenAPI Specification Reference:_x000D_ https://spec.openapis.org/oas/v3.2.0.html'
'OAS facilitates the exposure of interfaces by supporting documentation tools that make APIs easy to understand and code generation tools that create clients and servers in multiple languages, simplifying public sector integration. When combined with other specifications and tools such as JSON Schema for data validation and documentation or code generation tools like Swagger UI, the specification enables interfaces to be both visible and usable across different contexts._x000D_ _x000D_ OpenAPI Specification Reference:_x000D_ https://spec.openapis.org/oas/v3.1.0.html_x000D_ _x000D_ JSON Schema Reference:_x000D_ https://json-schema.org/draft/2020-12/json-schema-core_x000D_ _x000D_ Swagger UI Reference:_x000D_ https://swagger.io/tools/swagger-ui/'
'Currently, the OAS is maintained, evolved and promoted by the OpenAPI Initiative (OAI), a consortium of industry experts with an open governance structure under the Linux Foundation umbrella. There are different ways in which a user can participate: via GitHub, weekly discussions on Zoom, or by joining the Slack workspace. In addition, there are special interest groups that can be taken into account, as well as blog posts and questions through this mail: info@openapis.org._x000D_ _x000D_ Moreover, the Technical Steering Committee (TSC) holds weekly web conferences to review open pull requests and discuss open issues related to the evolving OpenAPI Specification. Participation in weekly calls and scheduled working sessions is open to the community._x000D_ _x000D_ OpenAPI Initiative Reference:_x000D_ https://learn.openapis.org/introduction.html_x000D_ _x000D_ OpenAPI Participate Reference:_x000D_ https://www.openapis.org/participatehow-to-contribute_x000D_ _x000D_ OpenAPI Github Participation Reference:_x000D_ https://github.com/OAI/OpenAPI-Specification/#participation_x000D_ _x000D_ OpenAPI Github Community:_x000D_ https://github.com/OAI/community/blob/main/SPECIAL_INTEREST_GROUPS.md_x000D_ _x000D_ OpenAPI Specification Reference:_x000D_ https://spec.openapis.org/oas/v3.2.0.html'
'Originating from Swagger in 2010 and formalised as OAS under the OpenAPI Initiative in 2016, the OAS is a mature and stable standard for defining RESTful APIs, widely adopted across the industry. Its tools for documentation, client generation, validation, and testing, combined with active governance by the Linux Foundation, ensures that it is reliable for both enterprise and production use. _x000D_ _x000D_ Updates, such as 3.2.0, revolve around enhanced support for multi-document descriptions and resolving references (Base URI management), expanded parameter and content encoding capabilities (especially for cookies and query strings), and improved data modeling for complex structures (such as XML)._x000D_ _x000D_ Linux Foundation OAS Reference:_x000D_ https://www.openapis.org/tag/oas_x000D_ _x000D_ OpenAPI Specification Reference:_x000D_ https://spec.openapis.org/oas/v3.1.0.html_x000D_ _x000D_ OpenAPI 3.2.0 Specification Reference:_x000D_ https://spec.openapis.org/oas/v3.2.0.html'
'The purpose of OAS is not related to the modelling of business processes, therefore this criterion is not applicable to this specification._x000D_ _x000D_ OpenAPI Specification Reference:_x000D_ https://spec.openapis.org/oas/v3.1.0.html'
'OAS does not directly ensure data processing accuracy. Therefore, this criterion is not directly applicable to the specification._x000D_ _x000D_ OpenAPI Specification Reference:_x000D_ https://spec.openapis.org/oas/latest.html#openapi-specification_x000D_ _x000D_ OpenAPI Specification Reference:_x000D_ https://spec.openapis.org/oas/v3.1.0.html'
'OAS allows relevant information to be widely reused by defining reusable components such as schemas, parameters, responses, and security schemes. These can be referenced across multiple endpoints and operations, reducing duplication and ensuring consistency._x000D_ _x000D_ OpenAPI Specification Reference:_x000D_ https://spec.openapis.org/oas/v3.1.0.html'
'OAS is not a European Standard. It is an open specification developed and maintained by the OpenAPI Initiative under the Linux Foundation. However, it is widely recognised and adopted across Europe, including by EU institutions and national public administrations, to support interoperability and standardised API design._x000D_ _x000D_ Data Europa Reference:_x000D_ https://dataeuropa.gitlab.io/data-provider-manual/pdf/documentation_data-europa-eu_V1.2.pdf_x000D_ _x000D_ OpenAPI Specification Reference:_x000D_ https://spec.openapis.org/oas/v3.1.0.html'
'OAS has been found to be used in the Research Infrastructure for Science and Innovation Policy Studies (named as RISIS), where OpenAPI takes part in a project aiming to automatise query-centric APIs for accessing to linked data. Moreover, All APIs on data.europa.eu are documented via OpenAPI._x000D_ _x000D_ Automatic Query-centric API for Routine Access to Linked Data:_x000D_ https://iswc2017.semanticweb.org/wp-content/uploads/papers/MainProceedings/430.pdf_x000D_ _x000D_ Data Europa Reference:_x000D_ https://dataeuropa.gitlab.io/data-provider-manual/pdf/documentation_data-europa-eu_V1.2.pdf_x000D_ _x000D_ RISIS webpage:_x000D_ https://www.risis2.eu/about/_x000D_ _x000D_ OpenAPI Specification Reference:_x000D_ https://spec.openapis.org/oas/v3.1.0.html'
'The Github platform hosts the OpenAPI guidelines and specifications, is as well as a space for contributions _x000D_ and proposals of improvements in which any individual interested is encouraged to participate and raise _x000D_ issues regarding OAS implementation. OAS has also been found in multiple platforms, such as Stackoverflow or the Central Digital and Data Office platform from the United Kingdom. In this platform, information about the use and implementation of OAS is shared and reviewed. Additionally, CENELEC mantains and distribute a Catalogue of APIs based on OAS._x000D_ _x000D_ UK API technical and data standards reference:_x000D_ https://www.gov.uk/guidance/gds-api-technical-and-data-standards_x000D_ _x000D_ OpenAPI Specification Stackoverflow refrence:_x000D_ https://stackoverflow.com/questions/48111459/how-to-define-a-property-that-can-be-string-or-null-in-openapi-swagger_x000D_ _x000D_ OpenAPI Specification CENELEC Catalogue of APIs Reference:_x000D_ https://api-portal.cenelec.eu/_x000D_ _x000D_ OpenAPI Specification in Github:_x000D_ https://github.com/OAI/OpenAPI-Specification/discussions'
'2 Member States are recommending OAS in their ICT National Catalogues. These Member States are Malta and The Netherlands._x000D_ _x000D_ Malta ICT National Catalogue Reference:_x000D_ https://mccaa.org.mt/Section/Content?contentId=1243_x000D_ _x000D_ Netherlands ICT National Catalogue Reference:_x000D_ https://www.forumstandaardisatie.nl/open-standaarden/lijst_x000D_ _x000D_ OpenAPI Specification Reference:_x000D_ https://spec.openapis.org/oas/v3.1.0.html_x000D_ _x000D_ CAMSS list of standards:_x000D_ https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards_x000D_ '
'OAS enables authentication and role identification to a high degree through the mandatory definition of security schemes and requirements, which inform users how to prove their identity. The specification uses the Security Scheme Object to define the types of security protocols the API supports, such as OAuth2, OpenID Connect, API keys, and HTTP authentication._x000D_ _x000D_ OAS Security Requirements Object:_x000D_ https://spec.openapis.org/oas/latest.html#security-requirement-object_x000D_ _x000D_ OpenAPI Specification Reference:_x000D_ https://spec.openapis.org/oas/v3.1.0.html'
'OAS is an open-source, royalty-free specification, licensed under the Apache License, Version 2.0. It is also available with any restrictions related to Fair, Reasonable, and Non Discriminatory (F/RAND) principles, and it can be accessed from its website and in the Github repository._x000D_ _x000D_ OpenAPI Specification Reference:_x000D_ https://spec.openapis.org/oas/v3.1.0.html_x000D_ _x000D_ OpenAPI Specification in Github:_x000D_ https://github.com/OAI/OpenAPI-Specification/#participation_x000D_ _x000D_ Apache License Version 2.0 Reference:_x000D_ https://www.apache.org/licenses/LICENSE-2.0.html'
'OAS seeks to cover most use cases, it also permits the inclusion of additional data through extensions at specific points. These extensions may not always be supported by existing tools, but internal or open-source tooling can likewise be extended to provide the required support. Moreover, OpenAPI can be complemented and extended through other OpenAPI Initiative specifications, such as Overlays, which enable modular and context-specific adaptations without altering the core definition._x000D_ _x000D_ OpenAPI Specification Reference:_x000D_ https://spec.openapis.org/oas/v3.1.0.html_x000D_ _x000D_ OpenAPI Overlay Reference:_x000D_ https://spec.openapis.org/overlay/v1.0.0.html'
'The purpose of OAS does not directly ensure the protection of personal data since it focuses more on the documentation and share of APIs. However, the specification does support the implementation of security measures with the inclusion of security schemes, such as OAuth2, OpenID Connect, or even metadada that can describe authentication, autherisation and encryption requirements._x000D_ _x000D_ OpenAPI Specification Reference:_x000D_ https://spec.openapis.org/oas/v3.1.0.html_x000D_ _x000D_ OAuth 2.0 Authorization Framework Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc6749.html_x000D_ _x000D_ OpenID Connect Core Reference:_x000D_ https://openid.net/specs/openid-connect-core-1_0.html'
'OAS allows the description of the security mechanisms used by an API, such as API Keys or OAuth2. This helps document how users authenticate to access resources, ensuring that only authorised users can retrieve or modify the data._x000D_ _x000D_ OAS Security Requirements Object:_x000D_ https://spec.openapis.org/oas/latest.html#security-requirement-object_x000D_ _x000D_ OpenAPI Specification Reference:_x000D_ https://spec.openapis.org/oas/v3.1.0.html'
'OAS is intended to streamline the creation of APIs. Because the requirements of each API may differ, the specification permits partial implementations; however, a minimum level of implementation remains essential of an OpenAPI document (such as the openapi, info, and paths fields), valid schema definitions, correctly resolved references, and at least one properly defined operation. These elements ensure that even partial implementations remain compatible with OpenAPI tooling and maintain interoperability._x000D_ _x000D_ OpenAPI Specification Reference:_x000D_ https://spec.openapis.org/oas/v3.1.0.html'
'OAS is independent of any specification and can be implemented without any dependency on platforms. This allows tools, clients, and documentation to work across platforms without modification, supporting interoperability and broad adoption._x000D_ _x000D_ OpenAPI Specification Reference:_x000D_ https://spec.openapis.org/oas/v3.1.0.html'
'OAS can serve as an effective tool for enhancing visibility when documenting and developing new APIs. The core of this function is defining a standard, programming language-agnostic interface description for HTTP APIs. This framework ensures that different systems can communicate effectively, thereby increasing interoperability._x000D_ _x000D_ By enabling code generation for documentation, client applications, and server implementations, OAS improves the transparency of administrative processes. This standardisation facilitates API implementation, making them easier to understand and to interact._x000D_ _x000D_ OpenAPI Specification Reference:_x000D_ https://spec.openapis.org/oas/v3.1.0.html'
'OAS is independent of any specification and can be implemented without relying on other technologies. This allows OAS to standardise API descriptions across diverse technological environments, enabling consistent documentation, client generation, and interoperability regardless of the underlying tech._x000D_ _x000D_ OpenAPI Specification Reference:_x000D_ https://spec.openapis.org/oas/v3.1.0.html'
'OAS is designed to describe HTTP APIs regardless of the specific business domain or sector. Whether the API is for finance, healthcare, government, e‑commerce, or IoT, OAS can provide a standardised, programming language‑agnostic format to define endpoints, request/response schemas, authentication methods, and metadata._x000D_ _x000D_ OpenAPI Specification Reference:_x000D_ https://spec.openapis.org/oas/v3.1.0.html'
'OAS can be complemented with the Overlay specification, also from OpenAPI initiative. The Overlay specification allows to do modifications on an OpenAPI document without altering it. Among other functions, Overlay supports multi-language documentation._x000D_ _x000D_ OpenAPI Overlay Reference:_x000D_ https://spec.openapis.org/overlay/v1.0.0.html_x000D_ _x000D_ OpenAPI Specification Reference:_x000D_ https://spec.openapis.org/oas/v3.1.0.html'
'OAS defines a standard, programming language-agnostic interface description for HTTP APIs. This core standard enables both humans and computers to discover and understand the capabilities of a service without requiring access to source code, additional documentation, or inspection of network traffic. _x000D_ _x000D_ The specification attempts to guide API authors to avoid ambiguous requirements in order to maximise interoperability. By defining a fixed format for how data should be exchanged and where resources can be found, the OAS ensures different clients and services can reliably communicate._x000D_ _x000D_ OpenAPI Specification Reference:_x000D_ https://spec.openapis.org/oas/v3.1.0.html'
'The purpose of OAS does not provide means for restriction of access to information or data since it focuses more on the documentation and share of APIs. However, the specification does support the implementation of security measures with the inclusion of security schemes, such as OAuth2, OpenID Connect, or even metadada that can describe authentication, autherisation and encryption requirements. This allow to API designers to specify how information or data should be controlled. Thanks to this security schemes implementations the specification enables developers and tools to implement access restrictions in line with the intended security policies._x000D_ _x000D_ OpenAPI Specification Reference:_x000D_ https://spec.openapis.org/oas/v3.1.0.html_x000D_ _x000D_ OAuth 2.0 Authorization Framework Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc6749.html_x000D_ _x000D_ OpenID Connect Core Reference:_x000D_ https://openid.net/specs/openid-connect-core-1_0.html'
'OAS does not directly provide an access control mechanism. Therefore, this criterion is not directly applicable to the specification._x000D_ _x000D_ OpenAPI Specification Reference:_x000D_ https://spec.openapis.org/oas/latest.html#openapi-specification_x000D_ _x000D_ OpenAPI Specification Reference:_x000D_ https://spec.openapis.org/oas/v3.1.0.html'
CAMSS Assessment of PAdES Baseline Profile EIF Scenario v1.0.0
Assessment of the PAdES Baseline Profile with the Common Assesssment Method for Standards and Specifications (CAMSS)
'The purpose of the PAdES baseline Profile is not related to data processing, therefore this criterion is not applicable._x000D_ _x000D_ PAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31914201/01.02.01_60/en_31914201v010201p.pdf_x000D_ '
'The PAdES is not related to publication of data on the web. Therefore this criterion is not applicable. _x000D_ _x000D_ PAdES reference: https://www.etsi.org/deliver/etsi_en/319100_319199/31914201/01.02.01_60/en_31914201v010201p.pdf'
'The PAdES Baseline Profile helps users simplify the usage of electronic signatures in PDF documents with the PAdES Visible Signature method._x000D_ PAdES achieves this by using the PAdESSignatureParameters object that contains an attribute named SignatureImageParameters where the user allowed to customise the visual signature (with text, image or with image and text) on the document. In this sense the specification provides a concise method to represent not only the signature on the document but also other parameters like visual indications where the signature is located. _x000D_ These applications enhance user understanding by visually displaying key information such as whether the signature is valid, the date it was timestamped, and other relevant properties in a simple and straightforward way. _x000D_ A practical example of this is the CEF Digital Signature Service (DSS), which leverages PAdES to provide clear and verifiable electronic signatures. Through DSS, users can easily verify signature validity and timestamp information, helping improve trust and transparency in electronic communications._x000D_ _x000D_ eIDAS regulation:_x000D_ https://digital-strategy.ec.europa.eu/en/policies/eidas-regulation _x000D_ _x000D_ DSS reference:_x000D_ https://ec.europa.eu/cefdigital/DSS/webapp-demo/doc/dss-documentation.html _x000D_ _x000D_ PAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31914201/01.02.01_60/en_31914201v010201p.pdf'
'PAdES is maintained by ETSI, one of the European Agencies for Standardisation, specifically by the ETSI Technical Committee Electronic Signatures and Trust Infrastructures (ESI). _x000D_ _x000D_ ETSI reference:_x000D_ https://www.etsi.org/about _x000D_ _x000D_ Electronic Signatures and Trust Infrastructures (ESI) reference: _x000D_ https://www.etsi.org/committee/1399-esi_x000D_ _x000D_ PAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31914201/01.02.01_60/en_31914201v010201p.pdf'
'The PAdES Baseline Profile is a set of well-defined technical specifications developed by ETSI to ensure both interoperability and legal validity of electronic signatures across Europe, in line with the eIDAS Regulation. The specification includes several signature levels: PAdES-B-B, PAdES-B-T, PAdES-B-LT, and PAdES-B-LT, which can be implemented individually based on the desired properties. These levels are designed to be incremental, meaning that a basic signature (PAdES-B-B) can be progressively enhanced to include additional features like timestamps or long-term validation data, depending on user or system requirements._x000D_ _x000D_ eIDAS regulation:_x000D_ https://digital-strategy.ec.europa.eu/en/policies/eidas-regulation _x000D_ _x000D_ PAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31914201/01.02.01_60/en_31914201v010201p.pdf'
'The PAdES is not related to data portability of data between systems/applications. Therefore this criterion is not applicable._x000D_ _x000D_ PAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31914201/01.02.01_60/en_31914201v010201p.pdf'
'The PAdES Baseline Profile function is to facilitate the electronic signature of PDF documents in compliance with eIDAS regulation. In this sense, the specification, in conjuction with other specifications such as CAdES, ASiC and XAdES can enable the visibility of administrative procedures, as shown with the CEF Digital Signature Service (DSS). _x000D_ _x000D_ eIDAS regulation:_x000D_ https://digital-strategy.ec.europa.eu/en/policies/eidas-regulation _x000D_ _x000D_ DSS reference:_x000D_ https://ec.europa.eu/cefdigital/DSS/webapp-demo/doc/dss-documentation.html_x000D_ _x000D_ PAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31914201/01.02.01_60/en_31914201v010201p.pdf'
'PAdES is within the European eIDAS regulation which is legally binding for all EU members states._x000D_ PAdES is also a core element of the EUDI Wallet initiative of the European Union, defined under the revised eIDAS Regulation 2.0. It is a secure, EU-backed digital wallet (typically a mobile application) designed to empower EU citizens, residents, and businesses with a universally recognized, user-centric, and privacy-preserving means of digital identification and authentication across the entire European single market._x000D_ _x000D_ EUDI Wallet reference:_x000D_ https://eur-lex.europa.eu/eli/reg_impl/2024/2979/oj_x000D_ _x000D_ PAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31914201/01.02.01_60/en_31914201v010201p.pdf'
'The PAdES Baseline Profile main purpose is to provide the stakeholders involved in any electronic transaction with the certainty that the exchanged documents are truthful for all. In this sense the different signature levels (B-B Basic, B-T Time, B-LT Long-Term and B-LTA Long-Term Archive) provide a wide arrangement of security but it is not exhaustive._x000D_ _x000D_ PAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31914201/01.02.01_60/en_31914201v010201p.pdf'
'PAdES does not directly define or expose technical interfaces for accessing public administration services. However, the specification provides a standardised, machine and human-readable structure for electronic signatures on PDF documents, which facilitates interaction between citizens and public administrations when submitting information through public administration portals. By using the PDF format, the specification eases this communication between citizens and business by using one of most widely available format for document sharing._x000D_ _x000D_ eIDAS regulation:_x000D_ https://digital-strategy.ec.europa.eu/en/policies/eidas-regulation _x000D_ _x000D_ DSS reference:_x000D_ https://ec.europa.eu/cefdigital/DSS/webapp-demo/doc/dss-documentation.html _x000D_ _x000D_ PAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31914201/01.02.01_60/en_31914201v010201p.pdf'
'The PAdES Baseline Profile function is to facilitate the electronic signature in compliance with eIDAS regulation. The signature of a document can provide the involved stakeholders with the possibility to use the extensions on the signature in order to define specific legal or policy references relevant to the context of the signed document like confidentiality._x000D_ _x000D_ PAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31914201/01.02.01_60/en_31914201v010201p.pdf'
'PAdES baseline Profile provides the stakeholders with the certainty that the exchanged documents are truthful for all. In this regard the different signature levels (B-B Basic, B-T Time, B-LT Long-Term and B-LTA Long-Term Archive) that can be embedded on the Document Security Store (DSS) provide a wide arrangement of security levels to guarantee the the correct and secure transmission of data and no tempering of it._x000D_ _x000D_ _x000D_ PAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31914201/01.02.01_60/en_31914201v010201p.pdf'
'While the primary purpose of the PAdES Baseline Profile may not be focused on data integrity, its design supports mechanisms that uphold it. The different signature levels allows stakeholders to incorporate additional fields that can facilitate the detection of unauthorised changes, thereby reinforcing document integrity._x000D_ _x000D_ PAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31914201/01.02.01_60/en_31914201v010201p.pdf'
"The PAdES Baseline Profile is designed to guarantee the authenticity and authentication of the agents involved in data transactions. It achieves this by focusing on the signer's identity and their role, which is a core requirement of the eIDAS regulation._x000D_ _x000D_ eIDAS Regulation:_x000D_ https://digital-strategy.ec.europa.eu/en/policies/eidas- regulation_x000D_ _x000D_ PAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31914201/01.02.01_60/en_31914201v010201p.pdf"
'ETSI has provided a conformance testing tool for electronic signatures. The conformity testing tool involves different standards applied in the development of eSignatures, including PAdES, CAdES and XAdES and their respective baseline profiles._x000D_ _x000D_ Conformance Checker reference_x000D_ https://signatures-conformance-checker.etsi.org/_x000D_ _x000D_ PAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31914201/01.02.01_60/en_31914201v010201p.pdf'
"PAdES is intrinsically tied to the Portable Document Format (PDF) standard (ISO 32000-1). It defines extensions and restrictions on the PDF's internal data structures to support digital signatures. It is not designed to sign other document formats like Microsoft Word files or simple text files. In this regard Microsoft has developed their own proprietary alternative, OOXML._x000D_ _x000D_ PAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31914201/01.02.01_60/en_31914201v010201p.pdf_x000D_ _x000D_ OOXML reference_x000D_ https://www.iso.org/standard/71691.html"
'The effectiveness of the PAdES specification has been assessed in conjunction with other electronic signature specifications in an article on the "Special Issue Advanced Research in Technology and Information Systems" of the "Electronics" publication called "A Comprehensive and Privacy-Aware Approach for Remote Qualified Electronic Signatures". In the article the authors value the specification effectiveness in the integration with other cryptographic resources like blockchain and its eIDAS conformity._x000D_ _x000D_ A Comprehensive and Privacy-Aware Approach for Remote Qualified Electronic Signatures reference:_x000D_ https://doi.org/10.3390/electronics13040757_x000D_ _x000D_ PAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31914201/01.02.01_60/en_31914201v010201p.pdf'
'PAdES Baseline Profile function is to facilitate the electronic signature in compliance with eIDAS. The specification, through the "Long-Term Validation (LTV)" element and in conjunction with the Document Security Store (DSS), ensures the document remains self-contained and verifiable over long periods._x000D_ The DSS is a dictionary object within the PDF file itself, defined by the PAdES standard. Its purpose is to centralize and store the cryptographic data needed for validation. _x000D_ This means that a system receiving the signed document does not need to perform an entirely new validation process from scratch. It can reuse the included data to verify the signature's authenticity_x000D_ _x000D_ PAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31914201/01.02.01_60/en_31914201v010201p.pdf'
'The PAdES Baseline Profile is based on PDF and PDF documents are based on Unicode, which supports all writing systems. Therefore, any language can be used in an PDF document. In particular, ISO 32000-2 version officially introduced UTF-8 encoding on PDF as an allowed format for certain text strings (like metadata and comments), aligning the format more closely with web standards._x000D_ _x000D_ PAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31914201/01.02.01_60/en_31914201v010201p.pdf'
"PAdES is included in 5 national catalogues of recommended specifications. They belong to Croatia, Cyprus, France, Poland and Spain. The National Interoperability Framework (NIF) of Spain and France are aligned with at least 3 out of 4 scoreboards of the EIF Monitoring according to the National Interoperability Framework Observatory (NIFO) factsheets. _x000D_ _x000D_ CAMSS List of Standards: https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards_x000D_ _x000D_ NIFO Factsheets: _x000D_ https://interoperable-europe.ec.europa.eu/collection/iopeu-monitoring/digital-public-administration-factsheets-2024_x000D_ _x000D_ France's catalogue: _x000D_ https://www.numerique.gouv.fr/offre-accompagnement/reference-interoperabilite-rgi/_x000D_ _x000D_ Spains's catalogue:_x000D_ https://administracionelectronica.gob.es/pae_Home/dam/jcr:97912041-c1c3-47c4-b517f9f51db321d/Guia_aplicacion_Norma_Tecnica_Interoperabilidad_Catalogo_de_estandares.pdf_x000D_ _x000D_ Poland's catalogue: _x000D_ http://isap.sejm.gov.pl/isap.nsf/download.xsp/WDU20170002247/O/D20172247.pdf _x000D_ _x000D_ Cyprus catalogue: _x000D_ https://dits.dmrid.gov.cy/dmrid/dits/dits.nsf/all/B83AA8E4EB4EFD19C225855800288B10/$file/Cyprus%20eGovernment%20Interoperability%20Framework_new%20EIF_v2.0-To%20Publish.pdf _x000D_ _x000D_ Croatia's catalogue: _x000D_ https://ssi.gov.hr/en/catalogue_x000D_ _x000D_ PAdES reference: _x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31914201/01.02.01_60/en_31914201v010201p.pdf"
'The PAdES specification can be found used in different European projects and also by Member States. Since it is suitable for advanced electronic signatures in PDF documents, it is used by companies and public administrations to sign this kind of format documents. In this sense, the specification has been selected within the CEF Digital Signature Service (DSS) along with CAdES, ASiC and XAdES Baseline profiles. Digital Signature Service is an open-source software library for electronic signature creation and validation supporting the interoperability of electronic signatures._x000D_ The initiative is an enabler for cross borders interoperability between administrations and businesses._x000D_ Applications such as eCoSignature from the Ministry of Industry and Commerce of Spain use PAdES as one of their base specifications._x000D_ _x000D_ eCoSignature reference: https://firmaelectronica.gob.es/en/ciudadanos/cosas-deberias-saber/formatos- firma DSS reference: https://ec.europa.eu/cefdigital/DSS/webapp-demo/doc/dss-documentation.html _x000D_ _x000D_ eSignatureHub - Digital Signature Service DSS: _x000D_ https://ec.europa.eu/digital-building-blocks/sites/spaces/DIGITAL/pages/467109107/Digital+Signature+Service+-+DSS_x000D_ _x000D_ PAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31914201/01.02.01_60/en_31914201v010201p.pdf'
'The efficiency of the PAdES specification has been assessed on the thesis of Kiira Karonen from the Aalto University. The "PDF advanced electronic signature with smart cards" study describes a case example of a software implementation that signs PDF files according to the PAdES standard using smart cards as the signature creation device. The implementation described in this thesis is a low-abstraction solution that can be used to generate the signature structure required by the PAdES standard based on a raw cryptographic signature, thus showing that the PAdES specification can be efficiently implemented without dependencies on third party PDF reader software._x000D_ _x000D_ Karonen, K. (2025). PDF advanced electronic signature with smart cards. reference:_x000D_ https://urn.fi/URN:NBN:fi:aalto-202508196503_x000D_ _x000D_ PAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31914201/01.02.01_60/en_31914201v010201p.pdf'
'PAdES is an specification derived from the original PDF specification developed by Adobe (ISO 32000-1) back in 2008. In this regard, PAdES is an adaptation of the general signature format for electronic signatures, CAdES (CMS Advanced Electronic Signatures) to the PDF format. _x000D_ The current version of the specification was developed in 2024 and includes four levels of of signatures addressing increasing requirements for long term preservation and security that are compliant with the EU eIDAS Regulation. _x000D_ In this regard the major difference of the previous release (ETSI TS 103 172) from PAdES is that with the consolidation of the eIDAS Regulation the current specification (ETSI EN 319 142-1) has become an European Standard (EN). This step is taken since ETSI may elaborate European Standards and European standardisation deliverables in response to Standardisation Requests to support the European legislation or policies, in accordance with the amended Regulation (EU) 1025/2012. Therefore, with the eIDAS Regulation taking a more mature status the related specifications like PAdES become an European standard via the Standardisation Request deliverables Approval Process (SRdAP) and in accordance with the provisions of Article 21 of the Rules of Procedure, and those of Clause 2.2.2 of the Technical Working Procedures._x000D_ This means PAdES is a consolidated and mature enough specification to use in the development of digital solutions/services. _x000D_ Currently there is an ongoing update that will be published in 2027._x000D_ _x000D_ ISO 32000-1 reference _x000D_ https://www.iso.org/standard/51502.html_x000D_ _x000D_ CAdES (CMS Advanced Electronic Signatures) reference:_x000D_ https://www.etsi.org/deliver/etsi_ts/101700_101799/101733/02.02.01_60/ts_101733v020201p.pdf_x000D_ _x000D_ eIDAS Regulation reference:_x000D_ https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv:OJ.L_.2014.257.01.0073.01.ENG_x000D_ _x000D_ PAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31914201/01.02.01_60/en_31914201v010201p.pdf_x000D_ _x000D_ Regulation (EU) 1025/2012 reference_x000D_ https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32012R1025_x000D_ _x000D_ Standardisation Request deliverables Approval Process (SRdAP) reference:_x000D_ https://www.etsi.org/events/714-how-does-etsi-make-standards_x000D_ _x000D_ PAdES upcoming version:_x000D_ https://portal.etsi.org/eWPM/index.html#/schedule?WKI_ID=73780_x000D_ '
"The PAdES baseline Profile has sparked some online communities that discuss the specification's implementation in regards to others as well as the data related to it. It also created numerous questions and debates on developer forums like stackoverflow._x000D_ _x000D_ Docusign community:_x000D_ https://community.docusign.com/esignature-111/xades-cades-or-pades-2917_x000D_ _x000D_ Stack-overflow communities and discussions:_x000D_ https://stackoverflow.com/questions/tagged/pades_x000D_ _x000D_ PAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31914201/01.02.01_60/en_31914201v010201p.pdf"
'The purpose of the PAdES Baseline Profile is not related to modelling business processes. Therefore, this criterion is not applicable to this specification._x000D_ _x000D_ PAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31914201/01.02.01_60/en_31914201v010201p.pdf'
'PAdES Baseline Profile is a business sector agnostic specification which is reusable beyond the domain for which it was developed. Specifically, implemented to facilitate the electronic signature in compliance with eIDAS._x000D_ _x000D_ eIDAS regulation:_x000D_ https://digital-strategy.ec.europa.eu/en/policies/eidas-regulation _x000D_ _x000D_ PAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31914201/01.02.01_60/en_31914201v010201p.pdf'
'The PAdES Baseline Profile guarantees authenticity by cryptographically linking the signature to a specific individual and their certificate._x000D_ In this sense the signature must be applied after the PDF file has been encrypted. So, while the encryption is done beforehand it will be intrinsically tied to the user signing the document. _x000D_ _x000D_ PAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31914201/01.02.01_60/en_31914201v010201p.pdf'
'The PAdES Baseline Profile provides the involved stakeholders with a legally binding signature structure to formalise interoperability agreements. In this sense it provides the foundation of any agreement among any kind of participants. The specification also fosters and facilitates agreements by establishing a common method for signing PDF documents and data in a secure and trustworthy manner. This enables PDF documents to be exchanged in an interoperable way, ensuring that all parties can access the documents and trust the information or data contained within them. By providing a standardised approach, PAdES helps to build confidence between parties and supports the reliable execution of digital transactions._x000D_ _x000D_ PAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31914201/01.02.01_60/en_31914201v010201p.pdf'
'PAdES guarantees that signed data on PDF format remains authentic, integral, and legally defensible when transmitted or archived._x000D_ PAdES signatures, especially when based on Qualified Certificates (which are common in Public Administrations under eIDAS), link the document directly to a verified identity._x000D_ _x000D_ PAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31914201/01.02.01_60/en_31914201v010201p.pdf'
'The purpose of the PAdES Baseline Profile is not related to e-accessibility. Therefore, this criterion is not applicable to this specification._x000D_ _x000D_ PAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31914201/01.02.01_60/en_31914201v010201p.pdf'
'The PAdES Baseline Profile includes mechanisms for long-term validation, such as timestamps and embedded certificate information. This means that a signed public record or contract can be securely archived and remain legally verifiable for some time. In this sense the preservation of the date of signature is a partial preservation of the record. _x000D_ The highest baseline level, PAdES-B-LTA (Long-Term Archival), facilitates the long term data preservation through the Document Time-Stamp (Archive Time-Stamp) which is a cryptographic seal placed over the entire PDF document, including the Document Security Store (DSS) and all embedded signatures._x000D_ _x000D_ When a new Document Time-Stamp is applied (a form of periodic extension), it essentially reuses the integrity of all preceding data, including the Revocation Information (VRI) data already present in the Document Security Store (DSS)._x000D_ _x000D_ This proves that the validation data (certificates and revocation checks) existed and was valid at the time the Document Time-Stamp was applied, effectively "re-certifying" the entire package against the threat of future cryptographic breaking or certificate expiry._x000D_ _x000D_ PAdES reference:_x000D_ https://www.etsi.org/deliver/etsi_en/319100_319199/31914201/01.02.01_60/en_31914201v010201p.pdf_x000D_ _x000D_ '
CAMSS Assessment of ebXML RegRep EIF Scenario v1.0.0
CSV is one of the main points on the publication of Open Data. Using the specification 3 out of 5 stars from Tim Berners Lee's schema for open data are supported. Moreover, some initiatives for the publication of European Organisations data as open data, consequently Linked Open Data have their datasets stored in CSV format. An example of it is the EU Open Data Portal. See: https://data.europa.eu/euodp/en/home https://5stardata.info/en/
CPOV is not included in any Member States' catalogues of recommended specifications. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
No formal agreement has been found established between organisations or administrations involved in European public service provision including the usage of WS-BPEL.
There is no national or European platform with the specification XACML available for free.
'The purpose of IPv4 is not related to the modelling of business processes. IPv4 is primarily a network protocol designed to facilitate communication over the internet, and it does not inherently focus on modelling business processes. IPv4 IETF: https://www.rfc-editor.org/rfc/rfc791'
"ShEx community group has already published two major releases of the ShEx specification, and as it is stated in the latest editors' draft, the language expressed by ShEx is already stable. In addition, there is public documentation on its supporting processes on Github, and the ShEx Community Group webpage. ShEx primer document: https://shexspec.github.io/primer/ ShEx Community Group: https://www.w3.org/community/shex/ ShEx Github: https://github.com/shexSpec/spec/issues"
The ISO 10918-1:1994 which refers to JPEG is not available for free for everyone to study. Payment is needed to reach access to the standard. JEPG ISO reference: https://www.iso.org/standard/18902.html
PDF 1.7 is already associated to an EIRA ABB in the EIRA Library Of Interoperability Specifications (ELIS). Specifically, PDF 1.7 can define the interoperability aspects of the "Document management service" ABB from the EIRA Technical view. See: https://joinup.ec.europa.eu/solution/elis/distribution/eliscataloguev100betaxlsx
The European Union (EU) Member States are currently implementing the INSPIRE Directive and related regulations, included in the ISA programme. This projects includes the usage of XSLT for each member state of the Union. See: https://ies-svn.jrc.ec.europa.eu/projects/registry-development/wiki/Re3gistry_1_0_documentation#_cp3
'The creation of a DID is a process that is defined by each DID Method. Some DID Methods, such as did:key, are purely generative, such that a DID and a DID document are generated by transforming a single piece of cryptographic material into a conformant representation. Other DID methods might require the use of a verifiable data registry, where the DID and DID document are recognized to exist by third parties only when the registration has been completed, as defined by the respective DID method. DIDs W3C: https://www.w3.org/TR/did-core/#creation-of-a-did'
Data on the Web Best Practices is maintained by W3C which is an international community developing open standards. Developer community W3C: https://www.w3.org/Consortium/
WS-Security is included in the pan-European electronic registered delivery solutions more specifcally SPOCS LP in the Transport layer, Trust establishment and Message protocol. See: https://www.etsi.org/deliver/etsi_sr/019000_019099/019050/01.01.01_60/sr_019050v010101p.pdf
'The OGC TrainingDML-AI standard, despite being in its early development stages, has attracted significant interest from both the geospatial and AI communities. This indicates a robust market acceptance for its utilization in the development of digital solutions/services. The focus on deep learning and emerging technologies implies that the standard is well-positioned to have a substantial impact on shaping future technological advancements within the geospatial domain. OGC TrainingDML-AI Standard: https://www.opengeospatial.org/standards/trainingdml-ai OGC TrainingDML-AI Implementations: https://www.ogc.org/resources/implementations/'
DCAT is an RDF vocabulary for representing data catalogues that allows data owners to provide metadata about the datasets they publish. By describing catalogues, datasets and resources, a publisher makes them easily searchable and discoverable. In fact, DCAT is used for the publication of datasets in linked open data portals at a National (e.g. ) and European scale ( European Data Portal) See: https://joinup.ec.europa.eu/solution/dcat-application-profile-data-portals-europe/releases
'DNS can be extended with several transport protocols to provide a safer data exchange. The Domain Name System Security Extensions (DNSSEC) modify DNS to add support for cryptographically signed responses, while other extensions such as Transaction Signature (TSIG), add support for cryptographic authentication between trusted peers and are commonly used to authorize zone transfer or dynamic update operations. Resource Records for the DNS Security Extensions: https://datatracker.ietf.org/doc/html/rfc4034 Extension Mechanisms for DNS: https://datatracker.ietf.org/doc/html/rfc6891 DNS IETF reference: https://datatracker.ietf.org/doc/html/rfc8499'
TSP is not included in any national catalogue of recommended specifications whose Member State NIF is fully aligned with at least 4 out of 5 sections of the EIF according to NIFO factsheets. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
The specification is available for its use and implementation at the IETF's webpage. FTPS IETF reference: https://tools.ietf.org/html/rfc4217
'The OASIS ebXML Core (ebCore) Technical Committee promotes the sharing of data and results and helps accelerate the specification adoption throughout the international community, particularly within government agencies. In this sense, the specification encourages both the creation of communities and the sharing of their data and results on national platforms. OASIS ebXML Core (ebCore) Technical Committee reference: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ebcore'
By applying the OpenPM2 methodology into the development of initiatives, services or products aiming to implement the once-only principle, it can leverage and promote synergies between organisations working in the same area of application. European Institutions developing initiatives using OpenPM2 can help to develop efficient eGovernment initiatives implying the once-only principle. OpenPM2 specification reference: https://op.europa.eu/en/publication-detail/-/publication/ac3e118a-cb6e-11e8-9424-01aa75ed71a1/language-en/format-PDF/source-83307127
'The OGC TrainingDML-AI standard facilitates online access and retrieval of data, enhancing accessibility and potentially streamlining digital service delivery channels. By establishing a foundation for efficient AI/ML applications and guaranteeing interoperable, high-quality data, the standard indirectly fosters the advancement of digital services in diverse domains, including public administration and environmental management. OGC TrainingDML-AI Standard: https://docs.ogc.org/is/23-008r3/23-008r3.html'
'The Asset Administration Shell (AAS) is the standardized digital representation of an asset, the corner stone for the interoperability of Industrial components organized in Industry 4.0 systems. The AAS may be the logical representation of a simple component, a machine or a plant at any level of the equipment hierarchy. In this sense the specification can be used in other domains rather than the industrial manufacturing but it would be a complicated implementation. Details of the Asset Administration Shell (AAS) https://industrialdigitaltwin.org/en/wp-content/uploads/sites/2/2024/06/IDTA-01001-3-0-1_SpecificationAssetAdministrationShell_Part1_Metamodel.pdf'
'The OData specification is included in the EUOS European catalogue of standards. EUOS reference: https://www.standict.eu/standards-repository'
'The purpose of ISO 639-2 is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification. ISO 3166-1 reference: https://www.iso.org/standard/72482.html'
"HTTP is designed to allow extensibility, allowing specific needs while maintaining a foundation of interoperability. The specification provides the flexibility to introduce new methods, status codes, and header fields, enriching the protocol's vocabulary and functionality. HTTP /1.1 RFC 2616 Reference: https://www.rfc-editor.org/rfc/rfc2616.html HTTP/1.1 Semantics, RFC 7231 Reference: https://www.rfc-editor.org/rfc/rfc7231"
'While EuroVoc was originally designed to facilitate data processing and classification within European Institutions, with a primary focus on eGovernment; it extends its coverage to various domains and subdomains, including but not limited to energy and transportation. Consequently, it can be regarded as adaptable and applicable across diverse business sectors. EuroVoc: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource /dataset/eurovoc'
The purpose of LDAP is not related to the visibility of administrative information, data or services. Therefore, this criterion is not applicable to this specification. LDAP IETF reference: https://tools.ietf.org/html/rfc4511
The purpose of SAMM is not related to the publication of linked open data. Therefore, this criterion is not applicable to the specification. SAMM webpage: https://owaspsamm.org SAMM documentation: https://github.com/OWASP/samm/blob/master/Supporting%20Resources/v2.0/OWASP-SAMM-v2.0.pdf 5-star linked open data: https://www.w3.org/DesignIssues/LinkedData.html
'Domibus can be found in the Joinup platform, as well as in the eDelivery building block of the European Commission-led Digital Europe website, where all the needed documentation for its implementation and study can be found. Domibus specification: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/Domibus Digital Europe webpage: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/Digital+Homepage'
'The JSON specification itself does not provide inherent mechanisms for secure processing of data. JSON is primarily a data interchange format that focuses on representing structured data in a readable and efficient manner. It does not include built-in features for secure processing, encryption, or access control. However, the security of data processing using JSON depends on the implementation and the systems handling the JSON data. How do you secure and encrypt JSON and XML data in web communication: https://www.linkedin.com/advice/0/how-do-you-secure-encrypt-json-xml-data-web-communication'
The specification was developed in 2015, and it has been evolving together with all the related European projects where CCCEV has an active role. Moreover, at the moment of performing the assessment, version 2.0 is being developed in order to ensure that the CCCEV covers the needs of the different cross-border projects (e.g. eCertis, ESPD, etc). CCCEV reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-criterion-and-core-evidence-vocabulary
'The ETSI and any of its committees, in charge of the development of ETSI TS 119 511, operates under the ETSI Intellectual Property Rigths (IPRs) and IPR Policy. The specification is licensed on a royalty-free basis. ETSI ownership of IPRs section: https://www.etsi.org/intellectual-property-rights'
'The SHACL specification can be used to validate data exchanged between different government systems, ensuring that the data meets the required standards before it is processed or shared. This reduces the need for manual checks and corrections, speeding up service delivery and improving the overall user experience. SHACL W3C reference: https://www.w3.org/TR/shacl/'
'Domibus has not been found included in the national catalogue of any Member State. Domibus specification: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/Domibus CAMSS List of standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards '
'There are no Member States recommending Better Regulation Guidelines and Toolbox in their ICT National Catalogues. Better Regulation Guidelines and Toolbox reference: https://commission.europa.eu/law/law-making-process/better-regulation/better-regulation-guidelines-and-toolbox_en CAMSS List of Standards: https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-andspecifications-camss/camss-list-standards'
"The specification's purpose is meant to use or not to use, can not be implemented partially. See: https://www.w3.org/TR/2006/REC-xml11-20060816/ "
The specification defines a core vocabulary related to access rights for distributions or sources that can be reused across sectors and extended to cover specific needs for determined purposes. ODRL defines a model that allow the reuse and exchange of data fostering the interoperability between parties. W3C specification reference: https://www.w3.org/TR/odrl-vocab/#vocab-core
'The specification is platform agnostic because it is sufficiently agnostic to work in any search engine, referring to as a program that searches for and identifies terms in a database that correspond to keywords or characters specified by the user. DCMI About: https://www.dublincore.org/about/ '
'An ebXML RegRep stores any type of electronic content, such as text documents, images, sound or video, and provides a set of protocols enabling data transfer among systems. For example, the ebXML specification has enabled the implementation of the e-SENS AS4 profile. Therefore, the specification enables data portability. ebXML reference: http://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-overview-v4.0-os.html e-SENS AS4 profile reference: https://ec.europa.eu/digital-building-blocks/wikis/display/CEFDIGITAL/e-SENS+AS4+-+1.12'
SHACL is maintained by W3C which is an international community developing open standards. See: https://www.w3.org/Consortium/
'SOAP 1.2 is maintained by W3C which is an international community developing open standards. W3C Consortium Reference: https://www.w3.org/Consortium/ SOAP Reference: https://www.w3.org/TR/soap12/ '
'The purpose of GraphQL is not related to enabling the secure exchange of data. Therefore, this criterion is not applicable to this specification. GraphQL specification: https://spec.graphql.org/October2021/#sec-Overview'
'By establishing constraints on the creation and exchange of XML documents XSD fosters the trustworthy data exchange between administrations and stakeholders. However, XSD does not include security features in itself. Despite this, XML includes several recommendations in order to ensure the security of data and users. XSD Reference: https://www.w3.org/TR/2012/REC-xmlschema11-1-20120405/'
'OData is maintained and developed by OASIS, which is an international community developing open standards; specifically, by the Technical Committee (TC). The specification maintenance is transparent, and even if its development and the approval process is restricted to the specification TC, anyone can contribute by submitting feedback to the mailing list. All the contributions are publicly available. Developer community OASIS: https://www.oasis-open.org/org/ OASIS ebXML Registry Technical Committee reference: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=regrep'
'EN 16234-1 e-CF is included in the CEN-CENELEC repository of standards. CENELEC and CEN search tool catalogue: https://standards.cencenelec.eu/dyn/www/f?p=CEN:105::RESET::::'
The rules on European standardisation allow the European Commission to identify information and communication technology (ICT) technical specifications - that are not national, European or international standards - to be eligible for referencing in public procurement. This allows public authorities to make use of the full range of specifications when buying IT hardware, software and services, allowing for more competition in the field and reducing the risk of lock-in to proprietary systems. After being evaluated compliant with the regulation on standardisation 1025/2012, TLS 1.2 has been identified by Commission Implementing Decision. During the evaluation process, all the Member States are invited to share their doubts. The positive evaluation of TLS 1.2 and its identification is considered an interoperability agreement. See: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en
'Extensibility is possible, as the specification documentation suggests the use of the Roles component of the specification to enable it. WAI-ARIA reference, section 1.1: https://www.w3.org/TR/wai-aria/'
'ODRL specification does not inherently provide features for ensuring the authenticity and authentication of the roles of agents involved in data transactions. W3C specification reference: https://www.w3.org/TR/odrl-vocab/#vocab-core'
'The purpose of the EN 303 645 specification is not related to the comprehensibility of administrative procedures, rules data, and services. EN 303 645 reference: https://www.etsi.org/deliver/etsi_en/303600_303699/303645/02.01.01_60/en_303645v020101p.pdf'
CSV is a text plain document which uses comma to separate values. Lines in a document are data records and records consists one or more fields. Therefore, CSV does not define a cross-sector reusable data model.
'Ecma International has clearly defined the procedures that have to be carried out in order to publish standards or technical reports. Although Ecma is the SDO that first developed the specification, it is currently being maintained by the IETF, thus, adhering to the development process defined by the organisation, which comprehends public reviews where stakeholders can formally appeal or raise objections to the development and approval of specifications. ECMA Directives: http://www.ecma-international.org/memento/policies.htm Standard process IETF: https://www.ietf.org/standards/process/'
'After searching in the different official European websites, there is no evidence of any cross-border project that use GITB TDL nor explicit agreements involving the usage of the specification. GITB TDL reference: https://www.itb.ec.europa.eu/docs/tdl/latest/introduction/index.html#introduction'
'The purpose of EN 16234-1 e-CF is not related to the secure exchange of data. Therefore, this criterion does not apply to this specification. CEN reference, CEN/TC 428 - ICT Professionalism and Digital Competences (Published standards), EN 16234-1 e-CF: https://standards.cencenelec.eu/dyn/www/f?p=205:110:0::::FSP_PROJECT:67073&cs=15E62ED24D608A5F10D6BEE8E6D50FA10'
'Registered Organization Vocabulary is not protected against unauthorised changes. The main purpose of the specification is to define a standardised way of describing organisations that have gained legal entity status through a formal registration process. Therefore, this criterion is considered not applicable to this specification. Registered Organization Vocabulary reference: https://www.w3.org/TR/vocab-regorg/'
'The EIRA is a domain agnostic reference architecture that can be used to develop solutions in multiples domains. Some examples of that reusability across domains are the specialisations that the Interoperability Architecture solutions have: eGovERA Business Agnostic, eGovERA Tax, eGovERA Health, eGovERA Custom. These are specialisations based in EIRA, which demonstrates that it is domain agnostic and can be reused across domains. EIRA reference: https://interoperable-europe.ec.europa.eu/collection/european-interoperability-reference-architecture-eira /solution/eira/release/610 EIRA Github Repository: https://github.com/CarTool-EC/EIRA Interoperability Architecture Solutions Success Stories: https://interoperable-europe.ec.europa.eu/collection/european-interoperability-reference-architecture-eira/success-stories'
'The purpose of genericode is not related to guaranteering the authenticity and authentication of the role agents involved in the data transactions. Therefore, this criterion is considered not applicable to this specification. Code List Representation (genericode): https://docs.oasis-open.org/codelist/genericode/v1.0/os/genericode-v1.0-os.html'
There are no Member States recommending CPOV in their ICT National Catalogues. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'There are existing documentation and studies assessing the efficiency of ETSI TS 119 612 together with other specifications. The "On Migrating from Present Identity Management Services to EIDAS" study, exposes a practical implementation of a sercive similar to eIDAS. This service allows to predict the success of eIDAS at EU level. "On Migrating form Present Identity Management Services to EIDAS" study: https://link.springer.com/chapter/10.1007/978-3-030-03003-2_16'
'ISO/IEC has not been found available in any repository/catalogue of standards at European level. ISO/IEC 19944-1 specification: https://www.iso.org/standard/60545.html'
The Web Services Security (WS-Security) main function is to reinforce integrity and confidentiality of the messages used by SOAP specification.
The purpose of HTTPS is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification.
The purpose of TIFF/IT is not related to the implementation of the once-only principle. Therefore, this criterion does not apply to this specification. TIFF/IT ISO reference: https://www.iso.org/standard/34342.html
'Since the specification is focused on testing the Trusted Lists established on web services and their schema according to the requirements established in ETSI TS 119 612, the implementation and usage of the specification can increase the visibility and reliability of public organisations procedures and rules. ETSI TS 119 614-1 reference: https://www.etsi.org/deliver/etsi_ts/119600_119699/11961401/01.01.01_60/ts_11961401v010101p.pdf'
'There are some optional parts in the REM Structure, but it is not customizable itself. ETSI EN 319 532-3 reference: https://www.etsi.org/deliver/etsi_en/319500_319599/31953203/01.02.01_60/en_31953203v010201p.pdf'
'There has not been found any assessment addressing the efficiency of Domibus implementations. Domibus specification: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/Domibus'
'DPV is based on European Union legislative requirements such as the GDPR, which aims to harmonise data privacy laws across Europe. Therefore, public administrations benefit from the definition of a data model based on this regulation given that it promotes the transparency of the procedures and personal data handled by public administrations. DPV specification: https://w3c.github.io/dpv/primer/ GDPR reference: https://gdpr.eu/'
"The Core Public Service Vocabulary Application Profile is a business domain agnostic specification, fostering the specification's use in any domain. CPSV-AP Joinup webpage: https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/core-public-service-vocabulary-application-profile/release/22"
The purpose of the Core Criterion and Core Evidence Vocabulary is not related to the availability of interfaces with internal information systems. Therefore, this criterion does not apply to this specification. CCCEV reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-criterion-and-core-evidence-vocabulary
'Syslog is a widely used and standardized protocol for message logging, making it relatively versatile and applicable across different domains, including various business sectors. Its standardization allows different systems and devices to communicate using a common logging format. Therefore, it is abstract and can be implemented and/or used in any domain as long as it fulfills the requirements. Syslog Protocol: https://datatracker.ietf.org/doc/html/rfc5424'
'SFIA is a framework for defining skills and competences in digital communities. In this sense, the specification is domain-agnostic and can be implemented across business domains where the ICT sector can operate. SFIA reference: https://sfia-online.org/en/sfia-8'
Eurovoc has the support of the Publication Office of the European Union as a developer community. Publication Office of the European Union: https://op.europa.eu/en/home
'ISO 3166-1 is intended to serve as a code list for the names of countries, dependent territories and special areas of geographical interest. Therefore, it is not designed to address nor prevent data long-term preservation. ISO 3166-1 reference: https://www.iso.org/standard/72482.html'
'XSLT specification does not provide means for restriction of access to information/data. Therefore this criterion is considered not applicable specification. XSLT Reference: https://www.w3.org/TR/xslt-30'
"TLS 1.3 is not classified as a European Standard but is instead an international standard developed by the Internet Engineering Task Force (IETF), used by every public european organisation to provide the necessary security, interoperability, and performance to safeguard sensitive data and ensure trust in online interactions. Additionally, it is included in the ISO/IEC organisation, under the name ISO/IEC 20648:2016 - TLS specification for storage systems, which defines the requirements for utilising the TLS protocol within data storage systems. Furthermore, TLS 1.3 is widely recognised and adopted within Europe, including by the European Commission's Multi-Stakeholder Platform on ICT Standardisation. European Multi-Stakeholder Platform on ICT Standardisation: https://digital-strategy.ec.europa.eu/en/policies/multi-stakeholder-platform-ict-standardisation ISO/IEC 20648:2016 - TLS specification for storage systems Reference: https://www.iso.org/obp/ui/#iso:std:iso-iec:20648:ed-1:v1:en"
PDF 1.7 does not defines a cross-sector reusable data model, but defines a file format for representing electronic documents.
'The specifications promotes innovation as CSV Dialect to simplify the format to be able to describe various CSV dialects. Due to its simplicity, compatibility, and versatility, CSV is widely used across various industries and domains. It is commonly employed for data import/export, data integration, data migration, data transformation, and other scenarios where tabular data needs to be exchanged between different systems or processed programmatically. There are reports that justify the widespread use of CSV in public procurement. CSV reference: https://datatracker.ietf.org/doc/html/rfc4180 'Utilizing open data: a primer for public procurement research" research document: http://www.zbw.eu/econis-archiv/bitstream/11159/8918/1/180709300X_0.pdf'
'After being evaluated compliant with the regulation on standardisation 1025/2012, IPsec has been identified by Commission Implementing Decision. The positive evaluation of IPsec and its identification is considered an interoperability agreement, although no specific provision are given to facilitate the drafting of such agreements. European Commission reference, ICT technical specifications: https://ec.europa.eu/growth/single-market/european-standards/ict-standardisation/ict-technical-specifications_en IPSec reference: https://datatracker.ietf.org/doc/html/rfc4301'
'IPsec has been selected by several public administrations for secure data exchange over the internet. By allowing the secure exchange of data, the specification fosters the visibility of data across borders. An example of its implementation is the TESTA project, which provides a secure cross-border data communication network service for public administrations. TESTA ISA2 project: https://ec.europa.eu/isa2/solutions/testa_en/ IPSec reference: https://www.rfc-editor.org/rfc/rfc6071.html'
'The objective of the Open Systems Interconnection (OSI) is the creation of a common basis for the coordination of standards development for the purpose of systems interconnection. OSI reference https://www.iso.org/standard/20269.html'
'The specification explicitly addresses and enables long-term preservation as it allows clients to replicate the history of a dataset and efficiently synchronise with its latest changes.At the heart, a Linked Data Event Stream can be interpreted as a publishing strategy by which a data provider allows multiple third parties to stay in sync with the latest version of the data source in a resource and cost-effective manner. LDES specification: https://joinup.ec.europa.eu/collection/semic-support-centre/linked-data-event-streams-ldes'
XForms specification became an official W3C Recommendation on 14 October 2003. It has been evolved over the years with versions updates demonstrating that it overcame the possible issues raised on the development and implementation. Xforms 2.0 W3C reference: https://www.w3.org/community/xformsusers/wiki/XForms_2.0
'TSP can use TSA whose role is to time-stamp a datum to establish evidence indicating that a datum existed before a particular time. This can then be used, for example, to verify that a digital signature was applied to a message before the corresponding certificate was revoked thus allowing a revoked public key certificate to be used for verifying signatures created prior to the time of revocation. Moreover, it provides a verifiable order of transactions, which is crucial for detecting unauthorised changes and supporting audits. While not encrypting data, when combined with other security measures like encryption, it strengthens overall data protection, especially in regulated environments like finance and healthcare. TSP IETF reference: https://www.rfc-editor.org/rfc/rfc3161 "Timestamp Authentication Protocol for RemoteMonitoring in eHealth" reference: https://www.researchgate.net/publication/4352969_Timestamp_Authentication_Protocol_for_Remote_Monitoring_in_eHealth'
WS-Security helps defining a data model, which represents application-defined data structures and values as a directed edge-labelled graph of nodes.
'The purpose of Advanced Encryption Standard is not related to scope comprehensibly administrative procedures, rules data, and services. Therefore this criterion is not applicable to the specification. AES Standard Reference: https://csrc.nist.gov/pubs/fips/197/final'
'The purpose of ETSI TS 119 612 is not related to the publication of open data, therefore this criterion is not applicable to the specification. ETSI TS 119 612 specification: https://www.etsi.org/deliver/etsi_ts/119600_119699/119612/02.02.01_60/ts_119612v020201p.pdf Tim Berners-Lee 5-star schema for Open Data: https://5stardata.info/en/'
One of the RFCs defining the IPv4 is available at the European collaborative platform Joinup. However, the other documents defining the specifications are not available at any European platform. See: https://joinup.ec.europa.eu/solution/ietf-rfc-791-1980-internet-protocol/distribution/ietf-rfc-791-1980-internet-protocol
There is no Member State that includes LegalRuleML in their national catalogue with The National Interoperability Framework (NIF) aligned with at least 4 out of 5 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'ETSI TS 119 512 has been developed to provide services for the long-term preservation of data in general. Although its main purpose is not to reuse data when needed, it can be useful for access and use of data in some cases. ETSI TS 119 512 specification: https://www.etsi.org/deliver/etsi_ts/119500_119599/119512/01.01.02_60/ts_119512v010102p.pdf'
'The purpose of DPV is not related to the long-term preservation of information; therefore, this criterion is not applicable to the specification. DPV specification: https://w3c.github.io/dpv/dpv/ DPV primer document: https://w3c.github.io/dpv/primer/#introduction'
'The Asset Administration Shell (AAS) has specific provisions regarding access control of the stakeholders, in this sense it is at the core of the specification the capability to authenticate the users sharing the assets. Details of the Asset Administration Shell (AAS) https://industrialdigitaltwin.org/en/wp-content/uploads/sites/2/2024/06/IDTA-01001-3-0-1_SpecificationAssetAdministrationShell_Part1_Metamodel.pdf'
The main purpose of this Core Vocabulary is to support the exchange of information between organisations that define criteria and organisations that respond to these criteria using evidences. So, it facilitates the visibility of administrative rules. CCCEV reference: https://joinup.ec.europa.eu/solution/e-government-core-vocabularies/core-criterion-and-core-evidence-vocabulary
CAMSS Assessment of CSV EIF Scenario v1.0.0
"This specification has been recommended by the Institut Luxembourgeois de la Normalisation, de l'Accréditation, de la Sécurité et qualité des produits et services (ILNAS), a public administration under the authority of the Minister of the Economy. Cloud Computing Published Standards: https://portail-qualite.public.lu/content/dam/qualite/publications/normalisation/2020/ans-smart-secure-ict/cloud-computing-standards-projects-V1.pdf"
'While ISO/IEC 7498:1 does not prescribe specific security measures for data processing, it provides a conceptual framework that can be part of the broader context of secure communication. Security practices need to be implemented across the entire system architecture, including the application layer, middleware, and underlying infrastructure. ISO/IEC 7498:1: https://www.iso.org/standard/20269.html'
'The purpose of HTTP is not related to the delivery of multilingual European public services. Therefore this criterion is considered not applicable specification. HTTP/1.1, RFC 2616 Reference: https://www.rfc-editor.org/rfc/rfc2616'
The purpose of Standard for Public Code is the reuse of code for the creation of solutions with the most transparent and efficient process, independently from the project type or solution domain. Taking this as a basis, the specification can foster and help the availability of interfaces of internal information systems. The Standard for Public Code webpage: https://standard.publiccode.net/
The purpose of JEPG is not related to organisational interoperability. Therefore, this criterion is not applicable to the specification. JEPG ISO reference: https://www.iso.org/standard/18902.html JPEG public reference: https://jpeg.org/jpeg/
At the moment of performing the assessment, LDAP is widely used at businesses and organizations worldwide for directory-based authentication. These types of resources are included in the development of platforms and services, including innovative solutions. LDAP with Active Directory: https://www.windows-active-directory.com/active-directory-ldap.html
OpenPM2 has the support of the Publication Office of the European Union as a developer community. Publication Office of the European Union: https://op.europa.eu/en/home
XSD is maintained by W3C which is an international community developing open standards. See: https://www.w3.org/TR/xmlschema11-1/ https://www.w3.org/TR/xmlschema11-2/
The purpose of ADMS is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification. ADMS Specification W3C: https://www.w3.org/TR/vocab-adms/
'Conformance to DPV implementation means it is correctly mapped and aligned with the vocabularies it defines. For that matter, the "Development Guide" section found in Github indicates how the conformity process has to be carried out. DPV specification: https://w3c.github.io/dpv/dpv/ DPV primer document: https://w3c.github.io/dpv/primer/#introduction DPV in Github: https://github.com/w3c/dpv '
'CCSDS participants are classified in four categories: member agency, Observer Agency, Liaison and Associate. All of these forms of participation require membership approval and a registration process to become part of a working group and participate in the standard development process. CCSDS Participation: https://public.ccsds.org/participation/default.aspx'
'The purpose of Core Location Vocabulary is not related to the secure exchange of data. Therefore this criterion is considered not applicable to the specification. Core Location Vocabulary: https://interoperable-europe.ec.europa.eu/collection/semic-support-centre/solution/core-location-vocabulary/release/100'
'MIME is included in 9 national catalogues of recommended specifications. They belong to Croatia, Cyprus, France, Germany, Greece, Malta, the Netherlands, Spain and Sweden. The National Interoperability Framework (NIF) of these Member States is fully aligned with at least 2 out of 3 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. CAMSS List of standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards National Interoperability Framework Observatory: https://joinup.ec.europa.eu/collection/national-interoperability-framework-observatory-nifo/nifo-factsheets The Netherlands Catalogue: https://www.forumstandaardisatie.nl/open-standaarden/lijst Spain Catalogue: https://administracionelectronica.gob.es/pae_Home/pae_Estrategias/pae_Interoperabilidad_Inicio/pae_Normas_tecnicas_de_interoperabilidad.html#CATALOGOESTANDARES Sweden Catalogue: http://www.avropa.se/dynamiska-sidor/sok/?query=standards&searchtype=web '
DCAT, as a cross-border and cross-sector vocabulary increases government-to-government reuse of data and therefore can prevent citizens or businesses from providing standard information several times. Like all common vocabularies, DCAT facilitates the implementation of the once-only principle. See: https://ec.europa.eu/isa2/dcat-ap-key-european-data-publishers-reach-data-consumers-and-create-european-open-data-ecosystem_en
'The ESPD is a well-established and widely used document in public procurement processes, platforms and tools across the European Union (EU), and it has been in use since 2016. As such, it can be considered a mature document that is suitable for use in the development of digital solutions and services. ESPD Business handbook: https://docs.ted.europa.eu/ESPD-EDM/latest/xml_business_handbook.html'
'The purpose of IPsec is not related to the long-term preservation of data. Therefore this criterion is not applicable to this specification. IPSec reference: https://www.rfc-editor.org/rfc/rfc6071.html'
'The specification has been developed specifically to support the interoperability and standardization of legal documents across European borders. Therefore, it may be suitable for use in European cross-border projects or initiatives. AKN4EU reference: https://op.europa.eu/en/web/eu-vocabularies/dataset/-/resource?uri=http://publications.europa.eu/resource/dataset/akn4eu'
'The rules on European standardisation allow the European Commission to identify information and communication technology (ICT) technical specifications - that are not national, European or international standards - to be eligible for referencing in public procurement. This allows public authorities to make use of the full range of specifications when buying IT hardware, software and services, allowing for more competition in the field and reducing the risk of lock-in to proprietary systems. After being evaluated compliant with the regulation on standardisation 1025/2012, XML has been identified by Commission Implementing Decision and included in the European list of ICT Standards for e-procurement. See: https://ec.europa.eu/growth/industry/policy/ict-standardisation/ict-technical-specifications_en '
PDF 1.7 does not foster the long-term preservation of electronic records and other kinds of information. The purpose of the specification is not related the preservation of information.
'Genericode is listed in the national catalogue of the Netherlands, Malta, Croatia and Sweden. The National Interoperability Framework (NIF) of these Member States is fully aligned with all the 3 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards 2023 NIFO factsheets: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public-administration-factsheets-2023'
The purpose of SOAP 1.2 is not related to security and privacy. Therefore, this criterion is not applicable to the specification.
Ogg does not provide for any generic encryption or signing of itself or its contained content. However, it is also possible to add an external security mechanism that encrypts or signs an Ogg physical bitstream and thus provides content confidentiality and authenticity. Ogg XIPH reference: https://xiph.org/ogg/doc/rfc3533.txt
ETSI has provided a conformance testing tool for electronic signatures according to the European Commission Mandate 460. The conformity testing tool involves different standards applied in the development of eSignatures, including PAdES, CAdES, XAdES, and ASiC ant their respective Baseline profiles. See: https://signatures-conformance-checker.etsi.org/pub/ASiCConformanceTestChecker_v1.0.pdf https://signatures-conformance-checker.etsi.org/pub/index.shtml
"ODRL is recommeded by Slovenia. Slovenia's National Interoperability Framework is aligned with at least 2 out of 3 sections of the European Interoperability Framework (EIF) according to the National Interoperability Framework Observatory (NIFO) factsheets. CAMSS List of standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /camss-list-standards NIFO Factsheets: https://joinup.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public\x02administration-factsheets-2023"
'According to the CEN/TC 428's Business Plan for 2022, EN 16234-1 e-CF is a European standard since 2016. CEN/TC 428 "ICT Professionalism and Digital Competences" Business Plan 2022 reference, section 1.1: https://standards.cencenelec.eu/BPCEN/1218399.pdf'
'In the context of secure electronic message exchange, Domibus can simplify the delivery of public services by providing a stndardized platform for the transmission of electronic messages and documents between different entities, thus, streamlining communication and securing data exchange processes. Domibus specification: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/Domibus'
The purpose of DNS is not related to the implementation of the once-only principle.
The specification is included in 8 Member States' catalogues of recommended specifications. These Member States are Croatia, France, Germany, Greece, Malta, the Netherlands, Spain and Sweden. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
The purpose of UTF-8 is not related to the modelling of business processes. Therefore, this criterion is not applicable to the specification.
OWL2 is maintained by W3C which is an international community developing open standards. _x000D_ _x000D_ Developer community W3C:_x000D_ https://www.w3.org/Consortium/
TIFF/IT has the ISO community that supports the development of: International standards, Technical Specifications, Technical Report and Publicly Available Specification. The ISO standardization process: http://www.isotc292online.org/projects/iso-process/
'ODRL can be utilized to express permissions and obligations related to preservation activities. By defining rights and obligations for archival content, may contribute to ensuring that preservation activities adhere to specified rules and conditions. W3C specification reference: https://www.w3.org/TR/odrl-vocab/#vocab-core'
There are several success stories and implementation examples that provide visibility on the effectiveness and efficiency of implementing ELI. It allows the description of legal resources and increases the shareability across borders enhancing the cooperation amongst European Institutions removing barriers. ELI reference: https://eur-lex.europa.eu/eli-register/about.html ELI highlights: https://eur-lex.europa.eu/eli-register/index.html ELI Testimonials: https://eur-lex.europa.eu/eli-register/testimonials.html
After carrying out information retrieval, no document or study has been found assessing the SMP in terms of efficiency or effectiveness.
PDF 1.7 is not included in any supra-national catalogue of standards.
'The TGF does not explicitly address data portability between systems. However, one of the basic principles of the TGF is interoperability, a layer for the achievement of which the TGF offers some provisions. Thus, by promoting interoperability, open standards and open data, the TGF can help enable data portability between systems, but no specific requirements or technical considerations are made for such purpose. TGF Specification: http://docs.oasis-open.org/tgf/TGF/v2.0/cs01/TGF-v2.0-cs01.html'
'The specification is focused on the preservation of confidential data and its availability. Therefore this criterion is not applicable to this specification. ISO/IEC 27001 reference website: https://www.iso.org/standard/54534.html'
'ESPD can be mapped into the EIRA Library of Interoperability Specifications (ELIS) covering the eProcurement Evaluating Component and the eProcurement Evaluating Service ABBs from the Technical Application view. EIRA Library of Interoperability Specifications (ELIS): https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss /solution/elis/release/v501'
RDF is already associated with EIRA ABBs in the EIRA Library Of Interoperability Specifications (ELIS). More specifically, RDF can define the interoperability aspects of the "Data model" and "Representation" ABBs of the EIRA Semantic View. See: https://joinup.ec.europa.eu/solution/elis/distribution/eliscataloguev100betaxlsx
PAdES Baseline profile was published in 2013, this demonstrates the maturity of the specification and that it overcame its initital issues. Moreover, this profile of the PAdES Specification is an extension based on the regulation for the Internal Market Enhancing. Additionally, all ETSI’s standards and specifications are strictly related to market needs, which demonstrates market acceptance. Therefore, it is demonstrated that PAdES baseline profile has enough maturity and market acceptance for its use in the development of products and services.
'TOSCA is a language for describing a cloud-based web service topology, its components, relationships and the processes that manage them. Although the specification competes against other cloud-orchestration proprietary formats (such as the AWS CloudFormation Templates), TOSCA v1.3 is contributing to the creation of innovative solutions based on YAML service templates, which has been positively adopted by the market. It is the case of xOpera (within a European project) and the IM infrastructure manager, both open source cloud orcherstrators. TOSCA Simple Profile in YAML reference, section 1.2: https://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.3/os/TOSCA-Simple-Profile-YAML-v1.3-os.html#_Toc26969412 AWS CloudFormation Templates reference: https://aws.amazon.com/cloudformation/resources/templates/?nc1=h_ls xOpera-Github reference: https://github.com/xlab-si/xopera-opera IM Infrastructure Manager reference: https://github.com/grycap/im'
'Although the SHACL specification is not addressed to enhance security mechanisms, it can play an important role in policy-based access control systems. In this context, SHACL can be utilised to define rules to determine whether access to certain data shuld be granted or denied. "SHACL-ACL: Access Control with SHACL" study: https://link.springer.com/chapter/10.1007/978-3-031-43458-7_4 SHACL W3C reference: https://www.w3.org/TR/shacl/'
'The specification is an element with high relevance in the data and information exchange. UTF-8 as a specification to encoding data ensures that files, web applications and systems can be read by both parts implied in the communication ensuring the reliability of transferred data. Therefore, UTF-8 eases the trustworthy data exchange between administration and stakeholders. UTF-8 specification: https://datatracker.ietf.org/doc/html/rfc3629'
'TGF provides means for restricting access to information or data through the use of access control mechanisms. These mechanisms can be applied at different levels, such as the network, application, and data levels, and can include authentication, authorization, and encryption techniques. By applying these mechanisms, TGF can ensure that only authorized users have access to the information or data they need to perform their tasks, while preventing unauthorized access and protecting against data breaches. TGF specification: http://docs.oasis-open.org/tgf/TGF/v2.0/cs01/TGF-v2.0-cs01.html'
'The available information does not specifically mention if the specification could be used in a multilingual context. However, the principles of the standard, such as the use of standardized formats and protocols, could potentially support multilingual data. For instance, it could be possible to use the standard to manage training data for machine learning models that work with text data in multiple languages. OGC TrainingDML-AI Standard: https://docs.ogc.org/is/23-008r3/23-008r3.html Multilingual Multimodal Learning with Machine Translated Text study: https://deepai.org/publication/multilingual-multimodal-learning-with-machine-translated-text'
The purpose of MIME is not related to the publication of public data as linked open data. Therefore, this criterion is not applicable to this specification. MIME reference: https://tools.ietf.org/html/rfc2045
'The specification is independent from any particular software, hardware, or operating system. So, it can be said that EuroVoc is independent of any specific platform. Verifiable Credentials: https://www.w3.org/TR/vc-data-model/'
LDAP was created in 1993 and quickly became one of the foundational authentication protocols used by IT network. The fact that in 1998, OpenLDAP 1.0 was implemented as an open source version of LDAP made it very popular. Therefore, it is demonstrated that LDAP has enough maturity for its use in the development of products and services. LDAP IETF reference: https://tools.ietf.org/html/rfc4511
'IEEE itself, as a leading professional organisation, actively promotes the standard through conferences, publications, and working groups, ensuring ongoing development and enhancement. IEEE Communities: https://www.ieee.org/communities/index.html IEEE 802.3 Working Group: https://www.ieee802.org/3/'
"ISAE 3402 is not focused on the publication of data as open data. It is dedicated to establishing internal controls for the assurance of services' quality from the customer perspective. Therefore this criterion is not applicable to this specification. ISAE 3402 reference: https://www.ifac.org/system/files/downloads/b014-2010-iaasb-handbook-isae-3402.pdf"
As defined on the TC standardisation, only ISO members are involved in the development of ISO standards. A public review is carried out to arrange the consensus firstly within the TC members and subsequently is reviewed by the different ISO member bodies. See: http://www.isotc292online.org/projects/iso-process/
Better Regulation Toolbox is not included in any Member States' catalogues of recommended specifications. CAMSS List of Standards: https://joinup.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards
'Domibus is being implemented in the e-CODEX project, a multilateral, content agnostic, e-Delivery infrastructure that uses building blocks from previous large scale projects to develop a single pan-European interoperability layer to support cross-border e-Justice services. Domibus specification: https://ec.europa.eu/digital-building-blocks/wikis/display/DIGITAL/Domibus Domibus in e-CODEX: https://joinup.ec.europa.eu/release/domain-interopability-bus-domibus'
'DPV provides a taxonomy of technical and organisational measures for representing information about how the access to personal data is technically and organisationally protected, safeguarded, secured, or otherwise managed. By referring to what measures are in place (such as GDPR) DPV directly addresses issues about the access to data pointing to the compliance of legal obligations to ensure data protection. DPV specification: https://w3c.github.io/dpv/primer/'
'SMP is a business domain agnostic specification that can be reused in a cross-domain way. SMP OASIS reference: https://docs.oasis-open.org/bdxr/bdx-smp/v2.0/cs02/bdx-smp-v2.0-cs02.html#_Toc30505009'
Not enough information has been found to answer negatively or positively to this criterion. Moreover, it seems that the specification is not aimed to foster the security and privacy of the data exchange. Therefore, this criterion does not apply to this specification. ELI reference: https://eur-lex.europa.eu/eli-register/about.html
'Linked Data Event Streams (LDES) can contribute to organisational interoperability agreements by providing a standardized and machine-readable format for representing and sharing real-time event data. The specification provides standarised representation, common vocabularies, semantic interoperability, real-time collaboration, etc. LDES specification: https://joinup.ec.europa.eu/collection/semic-support-centre/linked-data-event-streams-ldes'
'The specification is intended to serve as a device to identify a language name. In addition, there might exist other specifications designed to support multilingualism (e.g., the DCAT Application profile for data portals in Europe, DCAT-AP). ISO 369-2 FAQs: https://www.loc.gov/standards/iso639-2/faq.html#7'
'The purpose of the DNS Queries over HTTPS (DoH) is not related to e-accessibility. Therefore, this criterion is considered not applicable to this specification. DoH specification: https://datatracker.ietf.org/doc/html/rfc8484'
"While the standard doesn't explicitly outline mechanisms for safeguarding against unauthorized changes, incorporating detailed metadata and provenance information can enhance data integrity by enabling tracking and auditing of modifications. This structured data management approach inherently contributes to maintaining data integrity. OGC TrainingDML-AI Standard: https://docs.ogc.org/is/23-008r3/23-008r3.html"
Assessment of the Representational State Transfer (REST) EIF Scenario with the Common Assessment Method for Standards and Specifications (CAMSS)
CAMSS Assessment EIF Scenario of REST (2.0.0)
'REST is an architectural style that defines how systems should interact, and it is intrinsically linked to the HTTP protocol. While REST provides the design principles, HTTP provides the actual methods to carry them out. This close relationship means that as the HTTP standards evolve and mature, RESTful implementations become more robust and efficient for public services._x000D_ _x000D_ The latest minor updates to the HTTP/3 specification (RFC 9114) address specific transport-layer efficiencies and security patches._x000D_ _x000D_ The most recent major milestone for RESTful implementations was the release of the RFC 9110 series in June 2022. This major update consolidated and standardised HTTP semantics into a single, mature document, providing a stable and well-documented foundation for developers to plan and implement digital solutions for years to come._x000D_ _x000D_ HTTP Semantics (Major 2022 Update):_x000D_ https://www.rfc-editor.org/rfc/rfc9110.html_x000D_ _x000D_ REST reference:_x000D_ https://restfulapi.net/'
'REST is a sofware architectural style which defines a set of costraints for how the architecture of an internet-scale distributed hypermedia system should behave. REST architectural constraints are designed to provide efficient and scalable client-server applications through a URI resource approach. In this regard, REST allows for a greater interoperability, explicitly addressing and enabling data portability between systems or applications._x000D_ _x000D_ REST reference:_x000D_ https://restfulapi.net/'
'One of REST's architectural properties is the modifiability of components to meet changing needs. While the core architectural constraints remain fixed to ensure consistency, users have the flexibility to choose different media types (such as JSON, XML, or HTML) and decide which optional features, such as "Code on Demand," to include. This ability to select optional elements based on requirements makes the style adaptable to a wide range of digital services._x000D_ _x000D_ REST "Code on demand" reference:_x000D_ https://restfulapi.net/rest-architectural-constraints/#code-on-demand_x000D_ _x000D_ REST reference:_x000D_ https://restfulapi.net/'
'REST relies on the underlying HTTP protocol to ensure that data is protected from unauthorised changes. While it does not define its own encryption, it is designed to work with secure transport layers like HTTPS to safeguard information during transit. Additionally, RESTful systems often use mechanisms such as "ETags" or digital signatures to verify at the final stage that a resource has not been tampered with._x000D_ _x000D_ HTTP Semantics (Conditional Requests and ETags):_x000D_ https://www.rfc-editor.org/rfc/rfc9110.html#section-13_x000D_ _x000D_ REST API Tutorial - REST Security Essentials:_x000D_ https://restfulapi.net/security-essentials/_x000D_ _x000D_ REST reference:_x000D_ https://restfulapi.net/'
'REST is a domain-agnostic architectural style. Its six core constraints emphasise the scalability of interactions between components, uniform interfaces, independent deployment of components and the creation of layered architecture to facilitate its usage across business domains._x000D_ _x000D_ REST reference:_x000D_ https://restfulapi.net/'
'REST represents a set of design principles and constraints rather than a document being actively developed by a committee, there is no evidence found of any working group contributing to the development of REST. _x000D_ _x000D_ REST reference:_x000D_ https://restfulapi.net/'
'The purpose of REST is not related to the delivery of multilingual public services. Therefore, this criterion is_x000D_ not applicable to this specification._x000D_ _x000D_ REST reference:_x000D_ https://restfulapi.net/'
'The effectiveness of the REST specification has been assessed by the VNR Vignana Jyothi Institute of Engineering and Technology. In the "Performance evaluation of RESTful web services" study, the REST specification is proposed as a lightweight architectural style for building web services, facilitating better performance and lower resource consumption compared to traditional protocols._x000D_ _x000D_ "Performance evaluation of RESTful web services" study:_x000D_ https://ieeexplore.ieee.org/abstract/document/8103450_x000D_ _x000D_ REST reference:_x000D_ https://restfulapi.net/'
'REST is an architectural style focused on how systems interact rather than a security or privacy protocol. It does not natively include mechanisms to ensure the protection of personal data or specific alignment with regulations. However, it is designed to be implemented over secure transport layers such as HTTPS (TLS), which provides the encryption and integrity needed to protect data during transmission._x000D_ _x000D_ HTTP Semantics (Security Considerations):_x000D_ https://www.rfc-editor.org/rfc/rfc9110.html#section-17_x000D_ _x000D_ REST API Security Essentials:_x000D_ https://restfulapi.net/security-essentials/_x000D_ _x000D_ REST reference:_x000D_ https://restfulapi.net/'
'REST as an architectural style, relies on universal web standards such as HTTP and URI, which means it can be implemented using any programming language or framework. This flexibility allows different systems to communicate seamlessly, regardless of the specific technology stack they use in the background._x000D_ _x000D_ HTTP Semantics (HTTP Standard):_x000D_ https://www.rfc-editor.org/rfc/rfc9110.html_x000D_ _x000D_ Uniform Resource Identifier (URI): Generic Syntax:_x000D_ https://www.rfc-editor.org/rfc/rfc3986.html_x000D_ _x000D_ REST reference:_x000D_ https://restfulapi.net/'
'The REST specification provides RESTful APIs that are built on key security design principles that ensure data is processed and exchanged in a secure and trustworthy manner. By following these principles, such as using secure transport layers like HTTPS, public administrations can ensure that sensitive information remains protected and unaltered during transit._x000D_ _x000D_ REST API Tutorial - REST Security Essentials:_x000D_ https://restfulapi.net/security-essentials/_x000D_ _x000D_ HTTP Semantics (HTTP Standard):_x000D_ https://www.rfc-editor.org/rfc/rfc9110.html_x000D_ _x000D_ REST reference:_x000D_ https://restfulapi.net/'
'REST is included in several open repositories and catalogues at the European level. It is a fundamental part of the "API Framework for European Public Administrations" published by the Joint Research Centre (JRC), which provides the standard guidelines for building interoperable digital services. Additionally, it is listed on the CAMSS List of Standards further confirms its recognised status at the European level._x000D_ _x000D_ JRC Publications Repository - API Framework for European Public Administrations:_x000D_ https://publications.jrc.ec.europa.eu/repository/handle/JRC115049_x000D_ _x000D_ CAMSS List of Standards:_x000D_ https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards_x000D_ _x000D_ REST reference:_x000D_ https://restfulapi.net/'
'REST is a software architectural style based on standard HTTP methods. Its principles can be applied in any case and, therefore, it is a resource not subject to royalties or any kind of proprietary restrictions. This open nature ensures that any organisation can implement RESTful services freely, without legal barriers or costs, which has led to its universal adoption across the web._x000D_ _x000D_ REST reference:_x000D_ https://restfulapi.net/'
'REST is an architectural style rather than a technical specification, and there is no evidence found of any working group contributing to the development of REST_x000D_ _x000D_ REST reference:_x000D_ https://restfulapi.net/'
'REST specification conformance can be manually assessed by following its architectural constraints to help_x000D_ in obtaining a uniform interface and guiding the behaviour of components. No conformance testing platform has been found, however, there are accessible assessment online guides._x000D_ _x000D_ REST references:_x000D_ https://restfulapi.net/rest-architectural-constraints/_x000D_ _x000D_ REST reference:_x000D_ https://restfulapi.net/'
'REST is the core architectural style that powers the modern web. It is built on open, standardised protocols like HTTP and URI, which are maintained by the IETF. This approach allows data to be shared in structured and non-proprietary formats, making it accessible to everyone without needing special software. It also follows Tim Berners-Lee’s 5-star open data principles by using URIs to identify information and allowing different pieces of data to be linked together._x000D_ _x000D_ IETF - HTTP Semantics:_x000D_ https://www.rfc-editor.org/rfc/rfc9110.html_x000D_ _x000D_ API REST advantages:_x000D_ https://www.bbvaapimarket.com/es/mundo-api/api-rest-que-es-y-cuales-son-sus-ventajas-en-el-desarrollo-de-proyectos/_x000D_ _x000D_ The 5-star of Tim Berners-Lee can be found in the following link:_x000D_ https://5stardata.info/en/_x000D_ _x000D_ REST reference:_x000D_ https://restfulapi.net/'
'REST was first defined in the doctoral thesis of Roy Thomas Fielding and has since become the most popular architectural style for web services. While there is no single organisation dedicated solely to supporting the REST architectural style. Instead, support is found through a vast network of public online channels where users share knowledge and help each other. Platforms such as Stack Overflow and GitHub host millions of discussions regarding RESTful implementations, ensuring that developers have access to a wealth of community-driven expertise._x000D_ _x000D_ Roy Thomas Fielding Doctoral Thesis:_x000D_ https://dl.acm.org/doi/book/10.5555/932295_x000D_ _x000D_ Stack Overflow - REST Community Discussions:_x000D_ https://stackoverflow.com/questions/tagged/rest_x000D_ _x000D_ GitHub - REST API Topic:_x000D_ https://github.com/topics/rest-api_x000D_ _x000D_ REST reference:_x000D_ https://restfulapi.net/'
'REST is a core technology for major European cross-border projects. For instance, the Once-Only Technical System (OOTS) uses RESTful APIs as the primary method for Member States to exchange evidence securely and efficiently. The main goal is to simplify administrative procedures for citizens and businesses by ensuring they only have to provide their information once._x000D_ _x000D_ European Commission - Once-Only Technical System (OOTS) - REST reference:_x000D_ https://oots.pages.code.europa.eu/tdd/apidoc/_x000D_ _x000D_ REST reference:_x000D_ https://restfulapi.net/'
'The purpose of REST is not related to the development of business processes. Therefore this criterion is not applicable to this specification._x000D_ _x000D_ REST reference:_x000D_ https://restfulapi.net/'
'REST is supported by an incredibly active global community. It is extensively discussed on general platforms like Stack Overflow and GitHub, where developers share implementations and solve technical challenges. Within the European context, it is a central technology on the Interoperable Europe Portal, where public administrations share RESTful digital solutions and best practices to improve cross-border interoperability and the sharing of data._x000D_ _x000D_ Stack Overflow - REST Community Discussions:_x000D_ https://stackoverflow.com/questions/tagged/rest_x000D_ _x000D_ GitHub - REST API Topic:_x000D_ https://github.com/topics/rest-api_x000D_ _x000D_ Interoperable Europe Portal - REST reference:_x000D_ https://interoperable-europe.ec.europa.eu/collection/eurostat/solution/rest-api-web-services_x000D_ _x000D_ REST reference:_x000D_ https://restfulapi.net/'
'The purpose of REST is not related to the reuse of information. Therefore, this criterion is not applicable to this specification._x000D_ _x000D_ REST reference:_x000D_ https://restfulapi.net/'
'REST uses the standard features of the HTTP protocol to handle access to information. It does not have its own built-in access control system, but it relies on standard HTTP headers and status codes to make sure only authorised people can access or change data. This allows public administrations to set up their own security rules while using a common, well-known way to manage permissions._x000D_ _x000D_ HTTP Semantics (Authentication and Authorization):_x000D_ https://www.rfc-editor.org/rfc/rfc9110.html#section-11_x000D_ _x000D_ REST API Tutorial - REST Security Essentials:_x000D_ https://restfulapi.net/security-essentials/_x000D_ _x000D_ REST reference:_x000D_ https://restfulapi.net/_x000D_ '
'RESTful systems are built on core security principles that ensure data is handled safely. By using secure transport protocols like HTTPS, REST ensures that information stays private and cannot be tampered with while moving between systems. This approach allows public administrations to process sensitive data with confidence, knowing it is protected from unauthorised access and remains exactly as it was sent._x000D_ _x000D_ REST API Tutorial - REST Security Essentials:_x000D_ https://restfulapi.net/security-essentials/_x000D_ _x000D_ HTTP Semantics (HTTP Standard):_x000D_ https://www.rfc-editor.org/rfc/rfc9110.html_x000D_ _x000D_ REST reference:_x000D_ https://restfulapi.net/'
'REST relies on the underlying HTTP protocol to manage access to resources. It does not define its own specific security or encryption mechanisms, but it uses standard HTTP features, to enable controlled access. This ensures that confidentiality can be maintained by integrating with standard authentication and authorisation frameworks._x000D_ _x000D_ HTTP Semantics (Security Considerations):_x000D_ https://www.rfc-editor.org/rfc/rfc9110.html#section-17_x000D_ _x000D_ REST API Security Essentials:_x000D_ https://restfulapi.net/security-essentials/_x000D_ _x000D_ REST reference:_x000D_ https://restfulapi.net/'
'REST is an architectural style rather than a technical specification maintained by a specific organisation. However, it is a fundamental technology used in many relevant European projects and initiatives, such as the Once-Only Technical System (OOTS) and the Interoperable Europe Portal._x000D_ _x000D_ European Commission - Once-Only Technical System (OOTS):_x000D_ https://ec.europa.eu/digital-building-blocks/sites/spaces/OOTS/overview_x000D_ _x000D_ REST reference:_x000D_ https://restfulapi.net/'
'REST is an architectural style that defines how different systems should interact. REST APIs provide a simple and flexible way to access web services, which helps in creating digital interfaces that can be easily used by assistive technologies. By simplifying how data is accessed and shared, it explicitly supports the goal of making public services accessible to all citizens._x000D_ _x000D_ REST reference:_x000D_ https://restfulapi.net/'
'REST is a key technology used in major European projects that focus on privacy and data protection. For instance, the Once-Only Technical System (OOTS), which powers the "Your Europe" portal's data exchange, relies on RESTful APIs. This initiative is strictly governed by the Single Digital Gateway Regulation and the GDPR, ensuring that personal information is handled securely and privately across European borders._x000D_ _x000D_ General Data Protection Regulation (GDPR):_x000D_ https://eur-lex.europa.eu/eli/reg/2016/679/oj/eng_x000D_ _x000D_ European Commission - Once-Only Technical System (OOTS) - REST reference:_x000D_ https://oots.pages.code.europa.eu/tdd/apidoc/_x000D_ _x000D_ Single Digital Gateway (SDG):_x000D_ https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32018R1724_x000D_ _x000D_ REST reference:_x000D_ https://restfulapi.net/'
'REST is designed to ensure that different systems can work together smoothly by following a set of clear architectural rules. Because it provides a standardised way for systems to communicate, it makes it much simpler for organisations to create interoperability agreements. By referencing RESTful principles, public administrations can easily define the technical terms of their collaboration, ensuring that their digital services remain efficient and easy to manage across different departments or borders._x000D_ _x000D_ HTTP Semantics (Standard for RESTful communication):_x000D_ https://www.rfc-editor.org/rfc/rfc9110.html_x000D_ _x000D_ REST reference:_x000D_ https://restfulapi.net/'
'The uniform interface constraint is fundamental to the design of any RESTful system. It simplifies and decouples the architecture, which enables each part to evolve independently. For that reason, the REST architectural style ensures the standardised transfer of information between software systems, effectively enabling the exposure of interfaces that allow citizens and other organisations to access public services._x000D_ _x000D_ REST reference:_x000D_ https://restfulapi.net/'
"REST is an architectural style that defines how different systems should interact, allowing for greater interoperability between clients and servers. By providing a simple and flexible way to access web services through machine-readable formats, it ensures that administrative data and services are highly visible and easy to discover. A prime example of this is the French government's open data portal, which uses REST APIs to host and share public datasets, making government information transparent and accessible to everyone._x000D_ _x000D_ French government's open data portal:_x000D_ https://doc.data.gouv.fr/api/intro/_x000D_ _x000D_ REST reference:_x000D_ https://restfulapi.net/"
'REST is included in 2 national catalogues of recommended specifications. They belong to Finland and Slovakia. Its recommendation by these Member States highlights its recognised value as a mature architectural style for building interoperable digital services across Europe._x000D_ _x000D_ CAMSS List of Standards:_x000D_ https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards_x000D_ _x000D_ National catalogue of Finland:_x000D_ https://interoperable-europe.ec.europa.eu/sites/default/files/inline-files/Finland%20Factsheet%20Validated.pdf_x000D_ _x000D_ REST reference:_x000D_ https://restfulapi.net/'
'REST relies on standard web protocols, such as HTTP, to manage the identification and authentication of users. While it does not provide its own specific tools for this, it defines how standard headers should be used to carry authentication data._x000D_ _x000D_ REST API Tutorial - REST Security Essentials:_x000D_ https://restfulapi.net/security-essentials/_x000D_ _x000D_ REST reference:_x000D_ https://restfulapi.net/'
'REST is included in 2 national catalogues of recommended specifications. They belong to Finland and_x000D_ Slovakia. The National Interoperability Framework (NIF) of Finland and Slovakia are aligned with at least 3 out_x000D_ of 4 scoreboards of the EIF Monitoring according to the National Interoperability Framework Observatory_x000D_ (NIFO) factsheets._x000D_ _x000D_ CAMSS List of Standards:_x000D_ https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-andspecifications-camss/camss-list-standards_x000D_ _x000D_ National catalogue of Finland:_x000D_ https://interoperable-europe.ec.europa.eu/sites/default/files/inline-files/Finland%20Factsheet%20Validated.pdf_x000D_ _x000D_ REST reference:_x000D_ https://restfulapi.net/'
'Through the caching architectural principle, REST has the ability to store copies of frequently accessed data_x000D_ in several places along the requeest-response path. The Cache Control Headers can indicate when a representation never expires, meaning that the data of the representation is well preserved._x000D_ _x000D_ REST reference:_x000D_ https://restfulapi.net/'
'The REST architectural style is the primary way digital service delivery channels are built. By using RESTful APIs, public administrations can digitise procedures that used to be done in person, such as applying for permits or accessing health records. This approach streamlines communication between different government systems and ensures that services are available through various channels such as mobile apps and web portals._x000D_ _x000D_ REST reference:_x000D_ https://restfulapi.net/'
'One of the key properties of REST is the modifiability of its components to meet changing needs. Specifically, the "Code on demand" constraint allows a server to extend or customise the functionality of a client by transferring executable code, such as JavaScript. This ensures that the system can be extended with new features at runtime without needing to manually update the client software, making the architecture highly flexible._x000D_ _x000D_ REST "Code on demand" reference:_x000D_ https://restfulapi.net/rest-architectural-constraints/#code-on-demand_x000D_ _x000D_ REST reference:_x000D_ https://restfulapi.net/'
'REST is an architectural style defined by a specific set of core constraints. For a system to be considered truly RESTful, it must conform to all of these rules together, as they are designed to work as a complete set to ensure performance and scalability. Because missing any of these constraints means the system no longer follows the REST model, the specification is meant to be implemented as a whole._x000D_ _x000D_ REST architectural constraints reference:_x000D_ https://restfulapi.net/rest-architectural-constraints/_x000D_ _x000D_ REST reference:_x000D_ https://restfulapi.net/'
"REST helps ensure data processing accuracy by using standard HTTP features like ETags and conditional headers. These tools allow a system to verify that it is working with the most recent version of a resource before making any changes, which prevents errors such as overwriting someone else's updates. When combined with secure transport layers like HTTPS to prevent unauthorised modifications, these mechanisms ensure that the data remains accurate throughout the entire process._x000D_ _x000D_ HTTP Semantics (Conditional Requests and ETags):_x000D_ https://www.rfc-editor.org/rfc/rfc9110.html#section-13_x000D_ _x000D_ REST API Tutorial - REST Security Essentials:_x000D_ https://restfulapi.net/security-essentials/_x000D_ _x000D_ REST reference:_x000D_ https://restfulapi.net/"
'The REST architectural style simplifies the delivery of public services by providing a common and flexible way for different government systems to communicate. By using RESTful APIs, public administrations can build digital services that are easy for citizens to access from any device, reducing the need for paper-based processes and in-person visits. A practical example is the Once-Only Technical System (OOTS), which relies on REST to help citizens and businesses share information across the EU more efficiently._x000D_ _x000D_ Once-Only Technical System (OOTS):_x000D_ https://ec.europa.eu/digital-building-blocks/sites/spaces/OOTS/overview_x000D_ _x000D_ REST reference:_x000D_ https://restfulapi.net/'
'REST is included in 1 national catalogue of recommended specifications, it belongs to Finland. Its inclusion in these national repositories demonstrates its recognised value as a standard for building interoperable digital services at a national level._x000D_ _x000D_ CAMSS List of Standards:_x000D_ https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards_x000D_ _x000D_ National catalogue of Finland:_x000D_ https://interoperable-europe.ec.europa.eu/sites/default/files/inline-files/Finland%20Factsheet%20Validated.pdf_x000D_ _x000D_ REST reference:_x000D_ https://restfulapi.net/'
"REST is an architectural style that defines how different systems should interact, providing a simple and flexible way to access web services. By providing consistent resource structures with well-defined properties and metadata, the API ensures that clients can easily interpret the data, supporting clearer understanding of administrative procedures and services. A practical example is the French government's open data portal, which is built using REST principles to ensure its datasets are presented in a comprehensible and logical way for the public._x000D_ _x000D_ French government's open data portal:_x000D_ https://doc.data.gouv.fr/api/intro/_x000D_ _x000D_ REST reference:_x000D_ https://restfulapi.net/"
'REST has a wide-spread market acceptance as it is a common method to connect components in_x000D_ microservice architectures. Major global businesses like IBM and Amazon Web Services (AWS) rely on RESTful APIs to power their cloud platforms and manage complex data exchanges. Furthermore, open-source projects such as Spree Commerce use REST APIs to allow external applications to interact with their e-commerce engine, facilitating the management of products and orders in a standardised way._x000D_ _x000D_ Amazon Web Services reference:_x000D_ https://docs.aws.amazon.com/apigateway/latest/developerguide/apigateway-rest-api.html_x000D_ _x000D_ REST IBM reference:_x000D_ https://www.ibm.com/es-es/cloud/learn/rest-apis_x000D_ _x000D_ Spree Commerce - REST API Reference:_x000D_ https://spreecommerce.org/docs/api-reference/store-api/introduction_x000D_ _x000D_ _x000D_ REST reference:_x000D_ https://restfulapi.net/'
'REST is platform agnostic as it is not tied to any specific operating system or hardware. It is designed to be a universal architectural style that works across all devices and environments that support standard web protocols such as HTTP. This ensures that digital content and services remain accessible and consistent regardless of the underlying platform being used by the client or the server._x000D_ _x000D_ HTTP Semantics (HTTP Standard):_x000D_ https://www.rfc-editor.org/rfc/rfc9110.html_x000D_ _x000D_ REST reference:_x000D_ https://restfulapi.net/'
'REST is already associated to EIRA ABBs in the EIRA Library of Interoperability Specifications (ELIS). More specifically, REST can define the interoperability aspects of the "Web Service", "Machine to Machine Interface", "API", and "Data Exchange" ABBs of the EIRA Technical Application View._x000D_ _x000D_ EIRA Library of Interoperability Specifications (ELIS):_x000D_ https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/611_x000D_ _x000D_ REST reference:_x000D_ https://restfulapi.net/'
'The efficiency of the REST specification has been assessed by researchers. In the "Best Practices in REST API Design for Enhanced Scalability and Security" study, the REST specification is proposed as a set of architectural principles for building scalable web services, facilitating the optimisation of data handling and improved system performance through efficient resource management._x000D_ _x000D_ "Best Practices in REST API Design for Enhanced Scalability and Security" study:_x000D_ https://www.researchgate.net/publication/383599280_Best_Practices_in_REST_API_Design_for_Enhanced_Scalability_and_Security_x000D_ _x000D_ REST reference:_x000D_ https://restfulapi.net/'
CAMSS Assessment of JWS EIF Scenario v1.0.0
Assessment of the JSON Web Signature (JWS) EIF Scenario with the Common Assessment Method for Standards and Specifications (CAMSS)
'JWS is not related to enable the long-term preservation of data, information, or knowledge. Therefore, this criterion is not applicable to this specification._x000D_ _x000D_ JWS Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7515.html'
'JWS is platform agnostic. It defines a standardised, JSON-based mechanism for digitally signing data and does not depend on any specific software platform, infrastructure environment, cloud provider, or deployment model. As a result, it can be implemented and operated across different platforms without restriction._x000D_ _x000D_ JWS Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7515.html'
'JWS enables secure exchange of data in terms of integrity and authenticity, but it does not provide confidentiality. It guarantees that data has not been altered and that it originates from a trusted signer, but anyone with access to the token can read the payload._x000D_ _x000D_ If confidentiality is required (so that only authorised recipients can read the data), JWE or another encryption mechanism must be used in combination with JWS._x000D_ _x000D_ JWS Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7515.html'
"JWS is not related to enable the exposure of interfaces to access public administration's services. Therefore, the criterion is not applicable to this specification._x000D_ _x000D_ JWS Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7515.html"
'JWS provides a standardised, interoperable format for signing data, ensuring that the integrity and authenticity of the information are preserved when exchanged between different systems. _x000D_ _x000D_ JWS Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7515.html'
'JWS ensures that the sender of a JSON payload can be verified through the cryptographic signature, confirming that the data originates from a party in possession of the correct private key or shared secret. This provides authentication of the sender and integrity of the data._x000D_ _x000D_ JWS Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7515.html'
'JWS is developed by IETF, a non-European organisation. However, JAdES is built on top of JWS and adds what is needed to use it in official European electronic signatures. JWS provides a way to sign data, while JAdES adds extra features like identifying the signer, adding trusted timestamps, applying signature rules, and supporting long-term validation._x000D_ _x000D_ IETF Organisation:_x000D_ https://www.ietf.org/_x000D_ _x000D_ JWS Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7515.html_x000D_ _x000D_ JAdES Reference:_x000D_ https://www.etsi.org/deliver/etsi_ts/119100_119199/11918201/01.02.01_60/ts_11918201v010201p.pdf'
'JWS is maintained by IETF which is an international organisation based in Fremont, California. More specifically, the standard is developed by the OAuth working group._x000D_ _x000D_ OAuth Working Group Reference:_x000D_ https://oauth.net/specs/_x000D_ _x000D_ JOSE Framework Reference:_x000D_ https://github.com/ietf-wg-jose_x000D_ _x000D_ IETF Reference:_x000D_ https://www.ietf.org/_x000D_ _x000D_ JWS Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7515.html'
'JWS ensures data integrity and authenticity through digital signatures, providing a standard mechanism that enables interoperability between organisations. It is particularly useful in environments that require authentication and the secure exchange of data to support authorisation decisions._x000D_ _x000D_ JWS Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7515.html'
'JWS can be found in both relevant European regulations and European projects. In the case of relevant regulations, it can be found in the “CIR 2025/2531 regarding reference standards and specifications for qualified electronic ledgers” Commission Implementing Regulation. In this regulation, JWS is proposed to provide a standardised, interoperable mechanism for ensuring data integrity and authenticity across different systems, platforms, and organisations._x000D_ _x000D_ Furthermore, the specification is referenced in the EUDI Wallet Architecture and Reference Framework (ARF). Specifically, the specification is mentioned in section 6.3.4, “Attestation revocation” , of the ARF discussion topic. According to this section, the specification provides the cryptographic integrity and authenticity over the attestation data, and the SD-JWT structure is extended so that revocation status can be independently checked by the verifier._x000D_ _x000D_ CIR 2025/2531 regarding reference standards and specifications for qualified electronic ledgers:_x000D_ https://eur-lex.europa.eu/eli/reg_impl/2025/2531/oj_x000D_ _x000D_ EUDI Wallet Architecture and Reference Framework:_x000D_ https://eudi.dev/2.8.0/_x000D_ _x000D_ Section “Attestation revocation”, in EUDI Architecture and Reference Framework (ARF): https://eudi.dev/1.3.0/arf/#634-attestation-revocation_x000D_ _x000D_ JWS Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7515.html'
'JWS enables secure processing of data in terms of integrity and authenticity. Any system processing a JWS-protected payload can verify that the data has not been altered and that it comes from a trusted source. This ensures that decisions or operations based on the data are reliable._x000D_ _x000D_ However, the content is readable by anyone who has the token. For secure processing that requires limiting access to authorised parties, JWE or additional encryption mechanisms must be used alongside JWS._x000D_ _x000D_ JWS Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7515.html'
'JWS allows tokens to be digitally signed, ensuring the integrity and authenticity of the information they contain. If any part of the token is modified, signature verification will fail, indicating that the data has been altered and is no longer trustworthy. Successful verification confirms that the token was issued by the trusted signing authority and has not been tampered with._x000D_ _x000D_ JWS Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7515.html'
'JWS ensures that the data received has not been altered during transmission by providing cryptographic integrity checks. Because the payload is signed, systems can trust that the information they process is exactly what the sender intended, reducing errors caused by tampering or corruption._x000D_ _x000D_ JWS Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7515.html'
'JWS is not currently included in most Member States’ catalogues of recommended specifications. _x000D_ _x000D_ JWS Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7515.html_x000D_ _x000D_ CAMSS List of Standards:_x000D_ https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
'The efficiency of the JWS specification has been assed by the Institute of Electrical and Electronics Engineers (IEEE). The "A JSON Web Signature Based Adaptive Authentication Modality for Healthcare Applications" study, proposes an open standards based authentication modality that can seamlessly integrate with an Adaptive Authentication system. The proposed authentication modality uses JSON, JWS, and supports a means of verifying the authenticity of the requesting client._x000D_ _x000D_ "A JSON Web Signature Based Adaptive Authentication Modality for Healthcare Applications" study:_x000D_ https://ieeexplore.ieee.org/document/9952258_x000D_ _x000D_ JWS Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7515.html'
'JWS supports the simplification of business processes by enabling secure data integrity and authenticity through digital signatures. It allows users to access digital services, such as cross-border public administration platforms, eGovernment portals, and EU digital identity initiatives._x000D_ _x000D_ JWS Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7515.html'
'JWS conformance can be effectively assessed through publicly available test tools. JWT Validator tools let users decode and validate signed tokens (JWS) by checking structure, signature correctness, and claims such as issuer and expiration and JWS Parser/Decoder tools provide decoding of the header, payload, and signature for inspection._x000D_ _x000D_ JWS Parser/Decoder Reference:_x000D_ https://8gwifi.org/jwsparse.jsp_x000D_ _x000D_ JWT Validator Reference:_x000D_ https://jwtsecrets.com/tools/jwt-validator_x000D_ _x000D_ JWS Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7515.html'
'JWS allows extensions by the inclusion of new header parameters, registration of additional cryptographic algorithms and the creation of application specific profiles built on top of the core specification. _x000D_ _x000D_ For example, custom header parameters can be included for domain specific requirements. These extensions can be formally registered through the IANA registries defined by the specification, ensuring uniqueness, transparency, and interoperability._x000D_ _x000D_ IANA Considerations JWS reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7515.html#section-9_x000D_ _x000D_ JWS Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7515.html'
'JWS can help enable digital service delivery channels by protecting the integrity and authenticity of information contained within tokens through digital signatures. By allowing public administrations to verify that data has not been altered and was issued by a trusted authority, JWS supports secure digital procedures. This reduces the need for in-person processes by ensuring that electronic exchanges are reliable and based on verified information._x000D_ _x000D_ JWS Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7515.html'
'JWS can be found in the EUDI Wallet Architecture and Reference Framework (ARF). Specifically, the specification is mentioned in the standards used for the EUDI Wallet. _x000D_ _x000D_ EUDI Wallet Architecture and Reference Framework:_x000D_ https://eudi.dev/2.8.0/_x000D_ _x000D_ JWS Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7515.html'
'JWS is addressed to ensure that data is trustworthy, but the decision to grant or deny access is handled by the surrounding system (application, API, or authorisation server). Therefore, this criterion is not applicable to this specification._x000D_ _x000D_ JWS Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7515.html'
'JWS is widely used in European regulations and cross-border projects. It provides cryptographic integrity and authenticity in the EUDI Wallet, where it protects attestation data, and is considered a stable candidate specification._x000D_ _x000D_ JWS is also a core component of the eSignature Building Block and Digital Signature Services (DSS), enabling advanced and qualified electronic signatures in line with eIDAS. Within DSS, JAdES extends JWS for JSON-based signatures with features like signatory binding, modification detection, trusted timestamps, and long-term validation._x000D_ _x000D_ eSignature Building Block Reference:_x000D_ https://ec.europa.eu/digital-building-blocks/sites/spaces/DIGITAL/pages/467109036/eSignature_x000D_ _x000D_ DSS (Digital Signature Services) Reference:_x000D_ https://ec.europa.eu/digital-building-blocks/sites/spaces/DIGITAL/pages/467109107/Digital+Signature+Service+-+DSS_x000D_ _x000D_ JAdES Reference:_x000D_ https://ec.europa.eu/digital-building-blocks/DSS/webapp-demo/doc/dss-documentation.html#_jades_signature_jws_x000D_ _x000D_ JWS Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7515.html'
'JWS is not related to provide an access control mechanism. Therefore, this criterion is not related to this specification._x000D_ _x000D_ JWS Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7515.html'
'The effectiveness of the JWS has been assed by the Institute of Electrical and Electronics Engineers (IEEE). In the "Validating a Modified JSON Web Signature Format using the Scenario of Ammunition Issuance for Training Purposes" study, the JWS has been shown to be effective for secure identities exchange data directly with each other. _x000D_ _x000D_ "Validating a Modified JSON Web Signature Format using the Scenario of Ammunition Issuance for Training Purposes" study:_x000D_ https://ieeexplore.ieee.org/abstract/document/10356342_x000D_ _x000D_ JWS Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7515.html'
'JWS can simplify the delivery of European public services by ensuring the integrity and authenticity of information exchanged between different systems. By digitally signing data, JWS allows public administrations to verify that the information was issued by a trusted authority and has not been modified during transmission. This supports more reliable and accurate service delivery based on verified information._x000D_ _x000D_ JWS Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7515.html'
'JWS is not related to the publication of data on the web, as it is designed to ensure the integrity and authenticity of data by applying a cryptographic digital signature to a JSON payload. Therefore, this criterion is not applicable to this specification._x000D_ _x000D_ JWS Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7515.html'
'JWS supports customisation through custom header parameters and application-specific claims. This flexibility allows implementations to adapt JWS to specific business or organisational requirements while still remaining compatible with the core specification. JAdES extends JWS by adding features required for advanced electronic signatures, such as trusted timestamps, signature policies, and long-term validation support._x000D_ _x000D_ JAdES Reference:_x000D_ https://www.etsi.org/deliver/etsi_ts/119100_119199/11918201/01.01.01_60/ts_11918201v010101p.pdf_x000D_ _x000D_ JWS Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7515.html_x000D_ _x000D_ '
'JWS can be used in a multilingual context, because it simply signs a JSON payload. The payload can contain text in any language, encoded in UTF‑8, and JWS will preserve the integrity and authenticity regardless of language._x000D_ _x000D_ JWS Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7515.html'
'JWS first appeared as draft in March 2011 and, since May 2025, has been published as an_x000D_ RFC at Proposed Standard level. The available documentation provides clear details on all modifications_x000D_ introduced across the different released drafts._x000D_ _x000D_ Additionally, organisations have already begun adopting this standard. JWS is an open specificacion_x000D_ utilised on multiple European projects and initiatives, such as European Blockchain Services Infrastructure_x000D_ (EBSI) meaning its sufficiently mature for its use in the development of digital solutions/services._x000D_ _x000D_ European Blockchain Services Infrastructure (EBSI) - JWS reference:_x000D_ https://hub.ebsi.eu/arch-req/standards_x000D_ _x000D_ JWS Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7515.html'
'JWS is not related to scope comprehensively scope administrative procedures, rules, data, and services. Therefore, the criterion is not applicable to this specification._x000D_ _x000D_ JWS Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7515.html'
'JWS is technology agnostic. It is based on JSON mechanism for digitally signing data. It does not mandate any specific programming language, operating system, hardware environment, or vendor implementation._x000D_ _x000D_ JWS Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7515.html'
'JWS specification is not included in any national catalogue of recommended specifications._x000D_ _x000D_ CAMSS List of Standards: _x000D_ https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards_x000D_ _x000D_ Digital Public Administration factsheets - 2025: _x000D_ https://interoperable-europe.ec.europa.eu/collection/iopeu-monitoring/digital-public-administration-factsheets_x000D_ _x000D_ JWT standard:_x000D_ https://www.rfc-editor.org/rfc/rfc7519_x000D_ _x000D_ JWS Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7515.html'
'JWS is already associated to EIRA ABBs in the EIRA Library of Interoperability Specifications (ELIS). More specifically, JWS can define the interoperability aspects of the "eSignature Verification and Validation" and "e-Seal Verification and Validation" ABBs of the EIRA Technical-view application._x000D_ _x000D_ EIRA Library of Interoperability Specifications (ELIS):_x000D_ https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/611_x000D_ _x000D_ JWS Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7515.html'
'JWS can support the reuse of relevant information because it allows verified claims or evidence to be exchanged between administrations without requiring the citizen to provide the same data again._x000D_ _x000D_ For example, a JWS could contain signed information such as identity details, proof of residence, qualifications, permits, or business registration data. Once signed by the issuing authority, that information can be reused by other administrations because they can verify its authenticity and integrity directly, without asking the citizen to resubmit the same evidence._x000D_ _x000D_ JWS Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7515.html'
'JWS is discussed across both specialised forums and general developer platforms such as Stack Overflow. The big amount of questions about implementation, security discussions, and best-practice exchanges demonstrates active adoption and continuous community participation._x000D_ _x000D_ JWS Stack Overflow Reference:_x000D_ https://stackoverflow.com/search?q=JWS&s=56cbb160-cc05-4349-a221-1f5b487e167a_x000D_ _x000D_ JWS Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7515.html_x000D_ _x000D_ JOSE Framework Reference:_x000D_ https://jose.readthedocs.io/en/latest/'
'JWS is not recommended by any European Member State._x000D_ _x000D_ JWS Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7515.html_x000D_ _x000D_ CAMSS List of Standards:_x000D_ https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
'JWS helps protect personal data by ensuring the authenticity and integrity of the exchanged information. It does this by attaching a cryptographic signature to a JSON payload. The signature does not hide or encrypt the data, in that case, JWE can be used alongside JWS to encrypt the content so that only authorised recipients can access it._x000D_ _x000D_ JWS Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7515.html_x000D_ _x000D_ JWE Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7516.html'
'JWS is domain agnostic and can be used across multiple business sectors. The specification defines a generic, standardised mechanism for ensuring data integrity and authenticity, without being tied to any specific industry, data model, or business process._x000D_ _x000D_ JWS Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7515.html'
'JWS is included in European initiatives covering privacy aspects through the eSignature Building Block. This building block helps public administrations and businesses accelerate the creation and verification of electronic signatures, while supporting mutual recognition and cross-border interoperability of e-signatures across Member States._x000D_ _x000D_ More specifically, JWS is included within the DSS framework. DSS is an open-source library provided by the European Commission for the creation and validation of electronic signatures. It supports interoperable and secure electronic signatures in line with the eIDAS Regulation and related ETSI standards._x000D_ _x000D_ DSS helps ensure the integrity, authenticity, and non-repudiation of personal data exchanged between organisations and public administrations. Within DSS, JWS is used as the main signature mechanism for JSON-based electronic signatures through JAdES. JAdES extends JWS by enabling signed data to be linked to the signatory, ensuring that any later modification of the data can be detected, and supporting additional privacy-related features such as trusted timestamps, signature policies, and long-term validation._x000D_ _x000D_ eSignature Building Block Reference:_x000D_ https://ec.europa.eu/digital-building-blocks/sites/spaces/DIGITAL/pages/467109036/eSignature_x000D_ _x000D_ DSS (Digital Signature Services) Reference:_x000D_ https://ec.europa.eu/digital-building-blocks/sites/spaces/DIGITAL/pages/467109107/Digital+Signature+Service+-+DSS_x000D_ _x000D_ JAdES Reference:_x000D_ https://ec.europa.eu/digital-building-blocks/DSS/webapp-demo/doc/dss-documentation.html#_jades_signature_jws_x000D_ _x000D_ eIDAS Regulation Reference:_x000D_ https://eur-lex.europa.eu/eli/reg/2014/910/oj/eng_x000D_ _x000D_ JWS Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7515.html'
'JWS allows partial implementations. An example of partial implementation would be a system that supports only one signing algorithm and ignores optional header parameters. As long as the mandatory elements defined by the specification are included, the implementation remains conformant, even if optional features and additional algorithms are not implemented._x000D_ _x000D_ JWS Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7515.html'
'JWS is not related to enable the visibility of administrative procedures, rules data, and services. Therefore, the criterion is not applicable to this specification._x000D_ _x000D_ JWS Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7515.html'
'The specification is not related to enable the e-accessibility. Therefore, this criterion is not applicable to this specification._x000D_ _x000D_ JWS Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7515.html'
CAMSS Assessment of JWT EIF Scenario v1.0.0
Assessment of the JWT with the Common Assesssment Method for Standards and Specifications (CAMSS)
'JWT standard is not related with the long-term preservation of data, information, or knowledge. Therefore, this criterion is not applicable for the standard._x000D_ _x000D_ JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7519.html'
'JWT can carry information about a user, like their identity, roles, and permissions, which helps a system decide if they can access certain resources. When someone logs in, the system gives them a token with this information, and the token can be reused for Single Sign-On (SSO), so the user can access multiple apps or services without logging in again. _x000D_ _x000D_ JWT also has built-in claims to make it more secure: the audience (aud) claim makes sure only the right recipient can use the token; time-based claims (exp, nbf) limit when the token is valid; the issuer (iss) claim checks the token comes from a trusted source; and the JWT ID (jti) prevents the token from being used more than once. These features let JWT support access control methods like role-based (RBAC) and attribute-based (ABAC), giving a simple and secure way to handle who can do what across different apps and services. _x000D_ _x000D_ In addition, the JOSE framework allows JWTs to be encrypted through JWE, helping protect the confidentiality of the information carried inside the token._x000D_ _x000D_ JWT Specification Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7519.html'
'JWT is discussed across both specialised forums and general developer platforms such as Stack Overflow. The big amount of questions about implementation, security discussions, and best-practice exchanges demonstrates active adoption and continuous community participation._x000D_ _x000D_ JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7519.html_x000D_ _x000D_ Stack Overflow JWT Questions Reference:_x000D_ https://stackoverflow.com/questions/tagged/jwt?tab=Newest'
'JWT is not related to comprehensively scope administrative procedures, rules, data, or services.The specification is focused on defining a compact token format for securely transmitting claims between parties. Therefore, this criterion is not applicable to this specification._x000D_ _x000D_ JWT Specification Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7519.html'
'1 Member State is recommending JWT in its ICT National Catalogue. This Member State is Italy._x000D_ _x000D_ CAMSS List of Standards:_x000D_ https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards_x000D_ _x000D_ National Catalogue of Italy Reference:_x000D_ https://www.agid.gov.it/sites/default/files/repository_files/linee_guida_interoperabilit_tecnica_pa.pdf_x000D_ _x000D_ JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7519.html'
'JWT is maintained by IETF which is an international organisation based in Fremont, California. More specifically, the standard is developed by the OAuth working group._x000D_ _x000D_ OAuth Working Group Reference:_x000D_ https://oauth.net/specs/_x000D_ _x000D_ IETF Reference:_x000D_ https://www.ietf.org/about/introduction/_x000D_ _x000D_ JWT Standard Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7519.html'
'JWT enables digital service delivery channels by allowing claims and credentials to be transmitted securely in a digital form. Signed claims allow services to verify users and their permissions without maintaining server-side session state, supporting scenarios like SSO, APIs, and distributed digital services._x000D_ _x000D_ JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7519.html'
'JWT is technology agnostic, it is defined as an open standard and is based on JSON, which is widely supported across programming languages and platforms. Any system capable of processing JSON and implementing the required cryptographic algorithms can issue or validate JWTs._x000D_ _x000D_ JWT Specification Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7519.html'
'JWT is part of the JOSE framework and can be extended through signing, encryption, or custom claims. Its main extensions include JWS for ensuring integrity, JWE for confidentiality, JWA for specifying algorithms, and JWK for representing keys. These extensions make JWT a flexible and secure format that can be adapted to many different identity, authentication, and data exchange scenarios._x000D_ _x000D_ In addition, JWT can be extended through registered public claims maintained by IANA and through application-specific profiles, such as OpenID Connect ID Tokens and OAuth 2.0 access tokens, which define additional constraints and claim requirements._x000D_ _x000D_ IANA Reference:_x000D_ https://www.iana.org/assignments/jwt/jwt.xhtml_x000D_ _x000D_ JSON Object Signing and Encryption(JOSE) Reference:_x000D_ https://datatracker.ietf.org/wg/jose/about/_x000D_ _x000D_ JSON Web Signature (JWS) Reference:_x000D_ https://datatracker.ietf.org/doc/html/rfc7515_x000D_ _x000D_ JSON Web Encryption (JWE) Reference:_x000D_ https://datatracker.ietf.org/doc/html/rfc7516_x000D_ _x000D_ JSON Web Algorithms (JWA)_x000D_ https://datatracker.ietf.org/doc/html/rfc7518_x000D_ _x000D_ JSON Web Key (JWK) Reference:_x000D_ https://datatracker.ietf.org/doc/html/rfc7517_x000D_ _x000D_ JWT Specification Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7519.html'
'JWT is language-neutral because it uses JSON to structure its data, meaning the format itself does not depend on any particular language or character set. Claims within a JWT can carry text in any language, allowing systems to transmit multilingual information such as names, addresses, or messages. A European public service could issue a JWT containing a claim for a user’s preferred language (e.g. "preferred_language": "fr"). The consuming application can read this claim and display the interface or messages in French._x000D_ _x000D_ JWT Specification Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7519.html_x000D_ _x000D_ JWT Prefered Language Reference:_x000D_ https://openbao.org/api-docs/auth/jwt/'
'JWT standard is not related to the e-accessibility. Therefore, this criterion is not applicable to this specification._x000D_ _x000D_ JWT Specification Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7519.html'
'JWT can be found in both relevant European regulations and European projects. In the case of relevant regulations, it can be found in the “Commission Implementing Regulation (EU) 2025/848 of 6 May 2025 laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards the registration of wallet-relying parties” . In this regulation, the JWT specification is adopted as the data exchange format, and the relying party registration certificate shall be represented as a signed JSON Web Token (JWT). _x000D_ _x000D_ JWT also plays a key role in the implementation of the Mobile Driver’s Licence (mDL), where it is covered by ISO/IEC 18013-5:2021. In this context, it provides encryption mechanisms, including the use of signatures, to ensure the integrity and accuracy of the mDL. _x000D_ _x000D_ Mobile Driver’s Licence (mDL):_x000D_ https://ec.europa.eu/digital-building-blocks/sites/spaces/EUDIGITALIDENTITYWALLET/pages/929202846/The+Mobile+Driving+License+manual_x000D_ _x000D_ Commission Implementing Regulation (EU) 2025/848 of 6 May 2025 laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards the registration of wallet-relying parties” reference:_x000D_ https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32025R0848&qid=1766142281877 _x000D_ _x000D_ JWT Specification Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7519.html'
'JWT conformance can be effectively assessed through publicly available test tools, such as the JSON Web Token (JWT) Debugger and Token Debugger from token.io. There test tools allow developers to validate tokens._x000D_ _x000D_ JSON Web Token (JWT) Debugger:_x000D_ https://www.jwt.io/_x000D_ _x000D_ Token Debugger:_x000D_ https://token.dev/jwt/_x000D_ _x000D_ JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7519.html'
'JWT allows customisation by the use of additional signing and encryption algorithms as defined in the related standards (JWS and JWE). Therefore, an implementation may choose algorithms according to its security requirements (e.g. ECDSA-based algorithms), provided they are compliant with the relevant RFCs._x000D_ _x000D_ However, proprietary algorithms can be used without constraint, to fit the application or service needs according to the organisations authentication and authorisation rules. The algorithm must be properly identified in the JWT header and must follow the rules defined by the JSON Web Algorithms (JWA) specification._x000D_ _x000D_ JWE Specification Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7516.html_x000D_ _x000D_ JWS Specification Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7515.html_x000D_ _x000D_ JWT Best practices Algorithms reference:_x000D_ https://www.rfc-editor.org/rfc/rfc8725#name-use-appropriate-algorithms_x000D_ _x000D_ JWT Specification Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7519.html'
'JWT is included in 1 national catalogue of recommended specifications, which is Italy. The National Interoperability Framework (NIF) of Italy is aligned with at least 3 out of 4 scoreboards of the EIF Monitoring according to the National Interoperability Framework Observatory factsheets._x000D_ _x000D_ JWT Standard Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7519.html_x000D_ _x000D_ National Catalogue of Italy Reference:_x000D_ https://www.agid.gov.it/sites/default/files/repository_files/linee_guida_interoperabilit_tecnica_pa.pdf_x000D_ _x000D_ Italy Digital Public Administration Factsheet 2025:_x000D_ https://interoperable-europe.ec.europa.eu/sites/default/files/custom-page/attachment/2025-11/iopeu-monitoring_2025-dpaf_italy_vfinal.pdf_x000D_ _x000D_ CAMSS List of Standards: _x000D_ https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards'
'JWT can simplify the delivery of European public services by securely transmitting claims in a compact, URL-safe format between systems. This allows users to access multiple services without re-entering credentials and enables services to trust and reuse authentication information._x000D_ _x000D_ For example, a user that logs in via EU Login can access different EU services using the same token, which confirms their information securely._x000D_ _x000D_ JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7519.html'
'The purpose of JWT is not related to facilitating the publication of data on the web, as it is designed to securely transmit information between parties. Therefore, this criterion is not applicable to this standard._x000D_ _x000D_ JWT Standard Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7519.html'
'Together with JWS(digital signatures) and JWE(encryption), JWT allows applications to verify the integrity and authenticity of the data before processing it. This ensures that only trusted and untampered information is used in business logic, authorisation decisions, or service workflows._x000D_ _x000D_ JWT Specification Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7519.html_x000D_ _x000D_ JSON Web Signature (JWS) Reference:_x000D_ https://datatracker.ietf.org/doc/html/rfc7515_x000D_ _x000D_ JSON Web Encryption (JWE) Reference:_x000D_ https://datatracker.ietf.org/doc/html/rfc7516'
'JWT is platform agnostic, it is defined as an open standard and is based on JSON, which is widely supported across programming languages and platforms. Any system capable of processing JSON and implementing the required cryptographic algorithms can issue or validate JWTs._x000D_ _x000D_ JWT Specification Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7519.html'
"JWT only supports secure interaction with an existing interface, mainly for authentication and authorisation purposes. It is not related to enable the exposure of interfaces to access the public administration's services. Therefore, this criterion is not applicable to this specification._x000D_ _x000D_ JWT Specification Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7519.html"
'JWT supports integrity and authenticity through digital signatures (JWS), ensuring that the data has not been altered and that the issuer can be verified. It also supports confidentiality when used with encryption (JWE), protecting the content from unauthorised disclosure during transmission._x000D_ _x000D_ In addition, JWT is designed to be compact and standardised, which facilitates secure token exchange across diverse systems and platforms._x000D_ _x000D_ JWT Specification Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7519.html'
'JWT is domain-agnostic. It defines a technical mechanism for representing and securely transmitting claims, without sector-specific ties. The structure (header, payload, signature) is generic and does not impose business constraints. JWT can be used in any context where authentication and authorisation is needed._x000D_ _x000D_ JWT Specification Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7519.html'
'JWT allows relevant information to be reused primarily in authentication and authorisation scenarios. When a user authenticates through a login page, the system issues a token containing identity-related claims, such as the user ID or email address. This token can then be used for Single Sign-On (SSO), allowing the user to access multiple websites or services without having to re-enter their credentials for each one. In this way, applications can rely on the existing authentication token and provide a smoother, more secure user experience._x000D_ _x000D_ JWT Standard Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7519.html'
'JWT can enable data portability between systems/applications supporting the implementation or evolution of European public services by providing a secure authentication and authorisation of data between systems and applications._x000D_ _x000D_ JWT Specification Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7519.html'
'JWT is recognised by ENISA as an open standard for secure digital communication and is referenced in both European regulations and initiatives. In particular, the Commission Implementing Regulation (EU) 2025/848 of 6 May 2025, which implements Regulation (EU) No 910/2014 for the registration of wallet-relying parties, specifies JWT as the required format for data exchange. According to this regulation, relying party registration certificates must be represented as signed JSON Web Tokens._x000D_ _x000D_ Commission Implementing Regulation (EU) 2025/848 of 6 May 2025 laying down rules for the application of Regulation (EU) No 910/2014 of the European Parliament and of the Council as regards the registration of wallet-relying parties:_x000D_ https://eur-lex.europa.eu/eli/reg_impl/2025/848/oj/eng_x000D_ _x000D_ ENISA Security by Design and Default Playbook Reference:_x000D_ https://www.enisa.europa.eu/sites/default/files/2026-03/ENISA_Secure_By_Design_and_Default_Playbook_v0.4_draft_for_consultation.pdf_x000D_ _x000D_ JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7519.html'
'JWT supports access control by carrying claims that describe the user’s roles, permissions, or attributes. For example, a token could indicate whether the user is an admin, a regular user, or has specific privileges. The application can then enforce access rules based on these claims. JWT itself does not define the roles or policies; it only provides a standard way to transmit the information that applications use to make access decisions._x000D_ _x000D_ JWT Specification Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7519.html'
'JWT ensures that the data being processed is exactly what the trusted issuer sent and has not been altered, supporting reliable processing. However, it does not verify the real-world correctness of the data itself. As an example, when a user logs into a public service, the token contains claims such as the user ID or email. The service can trust that these claims so it can safely use the information to personalise the session or make authorisation decisions._x000D_ _x000D_ JWT Specification Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7519.html'
'JWT provides a secure and standardised mechanism for transmitting authentication and authorisation information, supporting organisational interoperability agreements. It is particularly suitable in environments that require both authentication and delegated authorisation._x000D_ _x000D_ JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7519.html'
'JWT supports the simplification of business processes by enabling secure authentication and identity verification. It allows users to access digital services, such as cross-border public administration platforms, eGovernment portals, and EU digital identity initiatives._x000D_ _x000D_ JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7519.html'
'JWT is not related to enabling the visibility of administrative procedures, rules data, and services. Therefore, the criterion is not applicable to this specification._x000D_ _x000D_ JWT Specification Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7519.html'
'The efficiency of the JWT specification has been assed by A. F. Nugraha, H. Kabetta, I. K. S. Buana and R. B. Hadiprakoso. In the "Performance and Security Comparison of Json Web Tokens (JWT) and Platform Agnostic Security Tokens (PASETO) on RESTful APIs" study. Performance tests show that JWT performs better than other token formats, such as PASETO. This advantage comes from its compact size, lightweight JSON encoding, and flexible support for efficient cryptographic algorithms within the JOSE framework, like HS256, RS256, and ES256._x000D_ _x000D_ "Performance and Security Comparison of Json Web Tokens (JWT) and Platform Agnostic Security Tokens (PASETO) on RESTful APIs" study:_x000D_ https://ieeexplore.ieee.org/document/10277377_x000D_ _x000D_ JWT Standard Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7519.html'
'JWT allows partial implementations. An application that uses JWT for authentication and authorisation can implement a simplified version that handles only basic signed tokens and a limited set of claims, while omitting more complex or advanced requirements._x000D_ _x000D_ To be considered a conformant JWT implementation, a system is only required to support a small core set of features. Implementations must support the mandatory algorithms specified by the standard to ensure consistent and interoperable operation._x000D_ _x000D_ Implementation requirements Refrence:_x000D_ https://datatracker.ietf.org/doc/html/rfc7519#section-8_x000D_ _x000D_ JWT Specification Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7519.html'
'JSON Web Token (JWT), developed by the IETF and part of the JOSE family, was first drafted in 2012 and approved as RFC 7519 in 2015. JWT is a token format for carrying claims, secured via JWS (signing) and JWE (encryption)._x000D_ _x000D_ It is used for digital identity, authentication, authorisation, and secure data exchange, including in the European Digital Identity Wallet. Recent updates add stronger security checks, clearer separation of signed and encrypted tokens, and selective disclosure (SD-JWT) for privacy, making it more suitable for digital wallets and verifiable credentials._x000D_ _x000D_ JWT Standard Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7519.html_x000D_ _x000D_ EUDI Wallet Architecture and Reference Framework:_x000D_ https://eudi.dev/2.8.0/#architecture-and-reference-framework _x000D_ _x000D_ Github EU Digital Identity Wallet Reference:_x000D_ https://github.com/eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework/blob/main/docs/architecture-and-reference-framework-main.md'
'JWT is referenced in the EUDI Wallet Architecture and Reference Framework (ARF) as a candidate standard for securely transmitting identity and authorisation information. The ARF defines the structural and functional aspects of the EUDI Wallet ecosystem, detailing its key components and interactions, and providing a technical foundation to ensure interoperability, security, and privacy. _x000D_ _x000D_ JWT is also aligned with international standards such as ISO/IEC 18013-5:2021, which specifies requirements for mobile driving licence (mDL) applications, further supporting its role in secure digital identity and credential management._x000D_ _x000D_ JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7519.html_x000D_ _x000D_ ISO/IEC 18013-5:2021 Reference:_x000D_ https://www.iso.org/standard/69084.html_x000D_ _x000D_ EUDI Wallet Reference:_x000D_ https://eudi.dev/2.4.0/architecture-and-reference-framework-main/'
'JWT ensures data integrity and authenticity through digital signatures, and optionally confidentiality through encryption (when used with JWE). This helps prevent unauthorised modification of personal data and, where encryption is applied, protects it from disclosure during transmission._x000D_ _x000D_ JWT Specification Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7519.html_x000D_ _x000D_ JWE Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7516.html'
'JWT is already associated to EIRA ABBs in the EIRA Library of Interoperability Specifications (ELIS). More specifically, JWT can define the interoperability aspects of the "Access Management" ABB of the EIRA Technical-view application._x000D_ _x000D_ EIRA Library of Interoperability Specifications (ELIS):_x000D_ https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/611_x000D_ _x000D_ JWT Standard Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7519.html'
'JWT is developed by IETF, a non-European organisation. However, it is used by many European countries and has also been adopted in different European projects, such as the EUDI Wallet. Therefore, this criterion is not applicable to this specification._x000D_ _x000D_ JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7519.html_x000D_ _x000D_ IETF Organisation:_x000D_ https://www.ietf.org/'
'JWTs are signed, compact tokens that let systems transmit identity and authorisation information securely without keeping session data on the server. They support stateless authorisation models like role-based (RBAC) and attribute-based (ABAC) access control. JWTs also provide strong protection against tampering: tokens signed with JWS let systems detect any changes to the data during transmission, ensuring that the information received is exactly the same as when it was issued._x000D_ _x000D_ JWT Specification Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7519.html'
'JWT guarantees authenticity and identity verification to a significant extent through digital signatures, allowing systems to confirm the issuer and validity of claims._x000D_ _x000D_ JWT Specification Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7519.html'
'JWT is included in 1 Member State catalogue of recommended specifications. This Member State is Italy._x000D_ _x000D_ National Catalogue of Italy Reference:_x000D_ https://www.agid.gov.it/sites/default/files/repository_files/linee_guida_interoperabilit_tecnica_pa.pdf_x000D_ _x000D_ JWT Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7519.html'
'The effectiveness of the JWT standard has been assed by the International Journal of Recent Technology and Engineering (IJRTE). In the "Insights of JSON Web Token" study, the JWT has been shown to be effective for secure, interoperable, and compact token-based data exchange, particularly in authentication and authorisation scenarios. In addition, JWT ensures data integrity and authenticity when implemented with strong algorithms._x000D_ _x000D_ "Insights of JSON Web Token, 2020, International Journal of Recent Technology and Engineering (IJRTE)" study:_x000D_ https://www.academia.edu/100350122/Insights_of_JSON_Web_Token_x000D_ _x000D_ JWT Standard Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7519.html'
'JWT is a token format used to carry claims between parties, secured through signing (JWS) and encryption (JWE). Its main purpose is to enable secure, interoperable, and verifiable data exchange, making it a dominant standard for identity and authentication. Popular implementations include platforms such as Keycloak and frameworks like the European Digital Identity (EUDI) Wallet._x000D_ _x000D_ JWT plays a key role in both European regulations and projects. For example, the Commission Implementing Regulation (EU) 2025/848 specifies that relying party registration certificates must be represented as signed JWTs, establishing JWT as the official format for this data exchange._x000D_ _x000D_ In European projects, JWT is referenced in the EUDI Wallet Architecture and Reference Framework (ARF), where it is identified as a fit-for-purpose standard with no functional or technical gaps. Its adoption adds value by enabling interoperable, secure, and privacy-respecting identity solutions across different platforms and borders._x000D_ _x000D_ Eur-lex Registration of relying parties of European Digital Identity Wallets Reference:_x000D_ https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=celex%3A32025R0848_x000D_ _x000D_ EUDI Wallet Architecture and Reference Framework:_x000D_ https://eudi.dev/2.8.0/#architecture-and-reference-framework _x000D_ _x000D_ JWT Specification Reference:_x000D_ https://www.rfc-editor.org/rfc/rfc7519.html'
Assessment of the Shape Expressions (ShEx) EIF Scenario with the Common Assessment Method for Standards and Specifications (CAMSS)
'ShEx provides a formal, machine‑readable way to describe and validate RDF data structures, enabling different organisations to agree on common “shapes” as a shared model for data exchange. Moreover, ShEx schemas can be translated into SPARQL queries, meaning that any constraint expressible by a SPARQL graph pattern or data query can be captured as a ShEx shape, making shapes the common agreement on what the data should look like._x000D_ _x000D_ ShEx - Validating RDF data Reference:_x000D_ https://www.weso.es/websem/slides/course2223/03_ShExByExample.pdf_x000D_ _x000D_ Shape Expressions (ShEx) 2.1 Reference:_x000D_ https://shex.io/shex-primer/'
'ShEx ensures and enables data processing accuracy by rigorously validating the structure and content of RDF data before it is processed. ShEx achieves accuracy by eliminating structural errors, controlling value ranges, and preventing the inclusion of unexpected data, therefore ensuring that processing systems only handle verified, predictable input._x000D_ _x000D_ Shape Expressions (ShEx) Reference:_x000D_ https://shex.io/shex-primer/'
'ShEx is not included in any initiative at European or National level covering privacy aspects. Therefore, this criterion is not applicable to this specification._x000D_ _x000D_ Shape Expressions (ShEx) 2.1 Reference:_x000D_ https://shex.io/shex-primer/'
'ShEx allows relevant information to be reused to a significant extent, as it provides a standardised and machine-readable way to define data structures. By specifying the shapes and relationships of data, ShEx ensures that the same definitions can be applied across different datasets, systems, or projects, promoting both consistency and interoperability._x000D_ _x000D_ Shape Expressions (ShEx) 2.1 Reference:_x000D_ https://shex.io/shex-primer/'
'ShEx main purpose is to define and validate the structure of RDF data. When a change (authorised or unauthorised) is made to the data, ShEx acts as a quality gate to ensure the modified data still conforms to the expected model. Therefore this criterion does not apply to the specification._x000D_ _x000D_ Shape Expressions (ShEx) 2.1 Reference:_x000D_ https://shex.io/shex-primer/'
'ShEx is not included in any open repository/catalogue of standards at European level._x000D_ _x000D_ Shape Expressions (ShEx) 2.1 Reference:_x000D_ https://shex.io/shex-primer/'
'The ShEx specification is developed by a non-European organisation. In this sense, the specification cannot be considered a European standard._x000D_ _x000D_ Shape Expressions Github Reference:_x000D_ https://github.com/shexSpec/spec_x000D_ _x000D_ Shape Expressions (ShEx) 2.1 Reference:_x000D_ https://shex.io/shex-primer/'
'ShEx is platform agnostic as it defines a language and validation framework independent of specific software environments or vendors. It can be implemented across different platforms and technologies that support RDF. However, its use is limited outside the RDF ecosystem._x000D_ _x000D_ Shape Expressions (ShEx) 2.1 Reference:_x000D_ https://shex.io/shex-primer/_x000D_ _x000D_ W3C RDF Concepts and Abstract Data Model Reference:_x000D_ https://www.w3.org/TR/rdf12-concepts/'
'ShEx allows extensions. Mechanisms like semantic actions, custom datatypes, and annotations enable controlled, implementation-specific extensions without altering core validation semantics. For example, ShExMap supports mapping and transformation of RDF data. The official ShEx extensions catalogue collects such extensions, showing how ShEx provides flexibility for domain-specific needs._x000D_ _x000D_ ShEx Extensions Github reference:_x000D_ https://shexspec.github.io/extensions/_x000D_ _x000D_ ShExMap Extension Reference:_x000D_ https://shex.io/extensions/Map/_x000D_ _x000D_ Shape Expressions (ShEx) 2.1 Reference:_x000D_ https://shex.io/shex-primer/'
'ShEx is technology-agnostic but depends on the RDF specification. It can be applied across platforms and domains that use RDF, ensuring data consistency and interoperability regardless of the technologies. However, its aplication outside the RDF ecosystem is limited._x000D_ _x000D_ Shape Expressions (ShEx) 2.1 Reference:_x000D_ https://shex.io/shex-primer/_x000D_ _x000D_ W3C RDF Concepts and Abstract Data Model Reference:_x000D_ https://www.w3.org/TR/rdf12-concepts/'
'The ShEx Community Group is an active W3C Community Group of developers, tasked with the maintenance and evolution of the ShEx specification. The group also operates via Github, where anyone interested can raise issues and pull requests about its implementation._x000D_ _x000D_ Shape Expressions (ShEx) 2.1 Reference:_x000D_ https://shex.io/shex-primer/_x000D_ _x000D_ ShEx Community Group:_x000D_ https://www.w3.org/community/shex/_x000D_ _x000D_ ShEx Github:_x000D_ https://github.com/shexSpec/spec/issues'
'ShEx allows the creation of core shape definitions that can be customised to fit specific business or domain requirements, ensuring interoperability without imposing technology-specific constraints._x000D_ _x000D_ Shape Expressions (ShEx) Reference:_x000D_ https://shex.io/shex-primer/'
'ShEx specification does not provide mechanisms for restricting access to information or data, since it focuses more on data validation, ensuring that it conforms to predefined shapes and relationships. Therefore, this criterion is not applicable to this specification._x000D_ _x000D_ Shape Expressions (ShEx) 2.1 Reference:_x000D_ https://shex.io/shex-primer/'
'ShEx allows for partial implementations, as its specification is modular and focused on RDF validation semantics. Implementers can adopt only the core or relevant features needed for their use case without compromising overall interoperability. An example of partial implementation can be shex.js, a javascript implementation, its ideal for browser-based validation tools and lightweight RDF data checks, focusing on core ShEx functionality without full language complexity._x000D_ _x000D_ shex.js Javascript implementation reference:_x000D_ https://github.com/shexjs/shex.js_x000D_ _x000D_ Shape Expressions (ShEx) 2.1 Reference:_x000D_ https://shex.io/shex-primer/_x000D_ _x000D_ W3C RDF Concepts and Abstract Data Model Reference:_x000D_ https://www.w3.org/TR/rdf12-concepts/'
'ShEx can be used in a multilingual context because it provides standardised, machine-readable validation for language information. Built upon RDF native support for language-tagged literals, the specification includes value sets that can also contain stems for IRIs, strings, and language tags. An IRI or string stem matches any IRI or string that starts with the stem._x000D_ _x000D_ Shape Expressions (ShEx) 2.1 Reference:_x000D_ https://shex.io/shex-primer/#value-sets'
'ShEx acts as a language for validating semantic data and ensuring structural consistency within the Linked Data environment. By defining standardised Shapes (data contracts) for specific public service domains built upon RDF, different systems can exchange data that is not only structurally correct but also semantically reliable. _x000D_ _x000D_ For example, projects like the Yosemite project leverage ShEx to create a robust, interoperable data model for clinical data exchange, significantly reducing the administrative and technical burden of integrating health records across organisations and national systems. The Yosemite Project is a collaborative effort dedicated to healthcare information interoperability. It is comprised of experts in healthcare and technology and guided by a six-member steering committee._x000D_ _x000D_ Shape Expressions (ShEx) 2.1 Reference:_x000D_ https://shex.io/shex-primer/_x000D_ _x000D_ Yosemite Project Reference:_x000D_ https://yosemiteproject.org/interoperability-roadmap/_x000D_ _x000D_ Using Shape Expressions (ShEx) to Share RDF Data Models and to Guide Curation with Rigorous _x000D_ Validation:_x000D_ https://link.springer.com/chapter/10.1007/978-3-030-21348-0_39'
'ShEx validates RDF datasets, ensuring they conform to defined shapes and constraints. It is dependent on the RDF specification because it relies on the core concepts of triples, subjects, predicates, objects, and the definitions of RDF Terms (IRIs, blank nodes, and literals) to exist and be functional, without RDF data, ShEx has nothing to validate. By supporting the consistency, correctness, and structure of this foundational RDF data, ShEx can then enable the visibility of administrative procedures, rules data, and services across public administrations._x000D_ _x000D_ Shape Expressions (ShEx) 2.1 Reference:_x000D_ https://shex.io/shex-primer/_x000D_ _x000D_ W3C RDF Concepts and Abstract Data Model Reference:_x000D_ https://www.w3.org/TR/rdf12-concepts/'
'ShEx is not included in any open repository/catalogue of standards at national level._x000D_ _x000D_ CAMSS list of standards: _x000D_ https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards_x000D_ _x000D_ Shape Expressions (ShEx) 2.1 Reference:_x000D_ https://shex.io/shex-primer//'
'ShEx is not recommended by any European Member State._x000D_ _x000D_ CAMSS List of Standards:_x000D_ https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/camss-list-standards_x000D_ _x000D_ Shape Expressions (ShEx) 2.1 Reference:_x000D_ https://shex.io/shex-primer/'
"The ShEx specification is not included in any Member States' catalogue of recommended specifications._x000D_ _x000D_ NIFO factsheets:_x000D_ https://interoperable-europe.ec.europa.eu/collection/nifo-national-interoperability-framework-observatory/digital-public-administration-factsheets-2024_x000D_ _x000D_ Shape Expressions (ShEx) 2.1 Reference: _x000D_ https://shex.io/shex-primer/_x000D_ _x000D_ "
'ShEx demonstrates a good level of maturity and domain acceptance. It is maintained by an active W3C Community Group. Several research and implementation cases, in healthcare and linked-data validation, confirm its practical use._x000D_ _x000D_ Although ShEx is not a formal W3C Recommendation, it is considered a highly stable, community-driven specification. Its current "candidate" status for the Final 2.0 Release, combined with growing academic and technical uptake, makes it a viable and credible choice for RDF-based solutions._x000D_ _x000D_ Shape Expressions (ShEx) 2.1 Reference:_x000D_ https://shex.io/shex-primer/_x000D_ _x000D_ Modeling and validating HL7 FHIR profiles using semantic web Shape Expressions (ShEx):_x000D_ https://pubmed.ncbi.nlm.nih.gov/28213144/_x000D_ _x000D_ Development of a FHIR RDF data transformation and validation framework and its evaluation:_x000D_ https://mayoclinic.elsevierpure.com/en/publications/development-of-a-fhir-rdf-data-transformation-and-validation-fram/'
'ShEx main function is to facilitate data exhange in RDF format by providing the means to validate RDF data graphs and does not directly enable the secure processing of data. ShEx is a schema and validation language, not a security protocol, this criterion is not applicable to this specification. _x000D_ _x000D_ Shape Expressions (ShEx) 2.1 Reference:_x000D_ https://shex.io/shex-primer/'
'ShEx specification itself does not guarantee the authenticity and authentication of the roles or agents involved in data transactions, since its a structural schema language for RDF graphs. Its function is strictly focused on data validation. Therefore this criterion does not apply to the specification._x000D_ _x000D_ Shape Expressions (ShEx) 2.1 Reference:_x000D_ https://shex.io/shex-primer/'
'ShEx specification does not include or define an explicit access control mechanism. The main function of ShEx is limited entirely to describing, validating, and ensuring the structural integrity of RDF data graphs. Therefore this criterion does not apply to the specification._x000D_ _x000D_ Shape Expressions (ShEx) Reference:_x000D_ https://shex.io/shex-primer/'
'The ShEx specification and schemas are publicly available for implementation and use on GitHub. The developer community involved with ShEx uses GitHub to collaborate on the specification, raise issues, and propose solutions for development. Additionally, platforms like StackOverflow serve as key channels where developers can ask and share technical questions, advice, and solutions, further supporting the robust growth and adoption of ShEx._x000D_ _x000D_ Shape Expressions (ShEx) 2.1 Reference:_x000D_ https://shex.io/shex-primer/_x000D_ _x000D_ ShEx Community Group:_x000D_ https://www.w3.org/community/shex/_x000D_ _x000D_ ShEx StackOverflow Reference:_x000D_ https://stackoverflow.com/questions/tagged/shex_x000D_ _x000D_ ShEx Github:_x000D_ https://github.com/shexSpec/spec/issues'
'The effectiveness of the ShEx specification has been assessed by multiple health institutions. In the study, "Modeling and validating HL7 FHIR profiles using semantic web Shape Expressions (ShEx)," researchers evaluated the specification's efficacy in describing and validating FHIR (Fast Healthcare Interoperability Resources) RDF data, which highlighted the considerable benefits of employing the ShEx RDF validator in that domain._x000D_ _x000D_ Modeling and validating HL7 FHIR profiles using semantic web Shape Expressions (ShEx):_x000D_ https://www.sciencedirect.com/science/article/pii/S1532046417300345_x000D_ _x000D_ Using Shape Expressions (ShEx) to Share RDF Data Models and to Guide Curation with Rigorous Validation:_x000D_ https://link.springer.com/chapter/10.1007/978-3-030-21348-0_39_x000D_ _x000D_ Shape Expressions (ShEx) 2.1 Reference:_x000D_ https://shex.io/shex-primer/'
'The purpose of ShEx is not related to e-accessibility. Therefore, this criterion is not applicable to this specification._x000D_ _x000D_ Shape Expressions (ShEx) 2.1 Reference:_x000D_ https://shex.io/shex-primer/'
"ShEx can simplify the delivery of European public services by ensuring that data conforms to specific structural and value constraints (e.g., properties exist, data types are correct, values fall within a range)._x000D_ _x000D_ For instance, a system that processes job applications might use a ShEx rule to ensure the applicant's date of birth field adheres strictly to the standard date format and verifies that the age falls within the eligible range (e.g., 18 to 65). This prevents bad data from entering the service's processing pipeline, directly reducing system errors, exceptions, and crashes that require complex error handling. By providing this common structure, ShEx can eliminate the need to manually verify the data from public administrations._x000D_ _x000D_ Shape Expressions (ShEx) 2.1 Reference:_x000D_ https://shex.io/shex-primer/"
'W3C provides the ShEx Simple Online Validator, an online tool that allows performing RDF data validation using Shape Expressions._x000D_ _x000D_ ShEx Simple Online Validator:_x000D_ https://rawgit.com/shexSpec/shex.js/master/packages/shex-webapp/doc/shex-simple.html_x000D_ _x000D_ Shape Expressions (ShEx) 2.1 Reference:_x000D_ https://shex.io/shex-primer/'
'ShEx is fully dependent on RDF, which serves as a domain-neutral data model. As a result, the specification is inherently reusable across business domains that represent their information in RDF. Its structural validation mechanism can be applied to any RDF-based dataset, whether in public administration, healthcare, research, or other sectors._x000D_ _x000D_ Shape Expressions (ShEx) 2.1 Reference:_x000D_ https://shex.io/shex-primer/_x000D_ _x000D_ W3C RDF Concepts and Abstract Data Model Reference:_x000D_ https://www.w3.org/TR/rdf12-concepts/'
'ShEx enables data portability as it provides a common language to describe and share data structures between different systems or interfaces, making it easier to transfer data across platforms and understand it more easily._x000D_ _x000D_ An example of ShEx in use is the Hercules ASIO project, which aims to build a Research Management System (RMS) based on semantic open data. This system provides a unified view of research information across the Spanish University System (SUE), helping to improve management, analysis, and collaboration among universities and the public. In doing so, it also supports the development of European public services._x000D_ _x000D_ Shape Expressions (ShEx) 2.1 Reference:_x000D_ https://shex.io/shex-primer/_x000D_ _x000D_ Hercules ASIO Project ShEx Reference:_x000D_ https://datos.gob.es/en/blog/hercules-asio-initiative-integration-publication-and-consultation-linked-open-research-data'
'The efficiency and utility of the ShEx specification have been assessed and demonstrated by multiple health institutions. In the study, "Development of a FHIR RDF data transformation and validation framework and its evaluation," researchers evaluated the specification's effectiveness at enhancing data quality and interoperability in both open and domain-specific contexts. ShEx has been successfully applied in areas such as healthcare and digital libraries, demonstrating its value for ensuring data consistency, validation, and reusability across diverse systems._x000D_ _x000D_ Development of a FHIR RDF data transformation and validation framework and its evaluation:_x000D_ https://pubmed.ncbi.nlm.nih.gov/33781919/_x000D_ _x000D_ A Shape Expression approach for assessing the quality of Linked Open Data in digital libraries:_x000D_ https://www.semantic-web-journal.net/content/shape-expression-approach-assessing-quality-linked-open-data-digital-libraries_x000D_ _x000D_ Shape Expressions (ShEx) 2.1 Reference:_x000D_ https://shex.io/shex-primer/'
'ShEx is already associated to EIRA ABBs in the EIRA Library of Interoperability Specifications (ELIS). More specifically, ShEx can define the interoperability aspects of the "Conformance Testing" and "Data Quality" ABBs of the EIRA Technical-Application View, and "Semantic interoperability agreement" ABBs of the EIRA Semantic View._x000D_ _x000D_ ELIS referenece:_x000D_ https://interoperable-europe.ec.europa.eu/collection/common-assessment-method-standards-and-specifications-camss/solution/elis/release/611_x000D_ _x000D_ Shape Expressions (ShEx) 2.1 Reference:_x000D_ https://shex.io/shex-primer/'
'ShEx does work as a data validation and structural constrain language that can enforce precise rules when needed, to protect data quality and preventing errors that could expose sensitive information. The ShEx schema prescribes specific conditions that RDF data graphs must meet to be considered "conformant". This means data managers can ensure that data adheres to established privacy requirements (e.g., ensuring a record for a specific entity is complete or correctly linked)._x000D_ _x000D_ Shape Expressions (ShEx) 2.1 Reference:_x000D_ https://shex.io/shex-primer/'
'ShEx main function is to facilitate data exhange in RDF format by providing the means to validate RDF data graphs and does not directly enable the secure exchange of data. ShEx is a schema and validation language, not a security protocol, this criterion is not applicable to this specification._x000D_ _x000D_ Shape Expressions (ShEx) 2.1 Reference:_x000D_ https://shex.io/shex-primer/'
'ShEx is the product of the ShEx Community Group from the W3C organisation. ShEx was first introduced in June 2014, as Shape Expressions 1.0 Primer (https://www.w3.org/submissions/2014/SUBM-shex-primer-20140602/). Moreover, the Shape Expressions Community Group (ShEx) was initiated in January 2017 on the W3C Community and Business Groups page. Since the release of this specification, several releases have been launched._x000D_ _x000D_ In this sense, in march 2017, the group launched the Shape Expressions (ShEx) Primer, a draft community group report, accompained by the ShapeMap Structure and Language release (ttps://shex.io/shape-map/). Since this release, different releases of the ShEx specification have been launched, being the latest one on the December 2022._x000D_ _x000D_ _x000D_ Shape Expressions (ShEx) 2.1 Reference:_x000D_ https://shex.io/shex-primer/_x000D_ _x000D_ ShEx Community Group Reference:_x000D_ https://www.w3.org/community/shex/_x000D_ _x000D_ ShEx Github Reference:_x000D_ https://github.com/shexSpec/spec/issues'
'The purpose of ShEx is not related to enable the long-term preservation of data/information/knowledge (electronic records included. Therefore, this criterion does is not applicable to this specification._x000D_ _x000D_ Shape Expressions (ShEx) 2.1 Reference:_x000D_ https://shex.io/shex-primer/'
'ShEx schemas ensure data is well-structured for release as open data because they are used for validating instance data, communicating interface parameters, defining complex data structures, and facilitating transformations into other formats. ShEx supports serialisation using ShExJ, a JSON-LD syntax, which is itself considered an open standard developed by the W3C._x000D_ _x000D_ Shape Expressions (ShEx) 2.1 Reference:_x000D_ https://shex.io/shex-primer/_x000D_ _x000D_ RDF Reference:_x000D_ https://www.w3.org/RDF'
"ShEx is being used in projects such as the Hercules-ASIO Initiative. Furthermore, by 2019 ShEx Community Group, announced that Wikidata's support for ShEx moved from testing to deployment. Using a new Wikidata extension, ShEx schemas are stored in ShEx compact syntax on wiki pages and linked to a tool for checking selected data, which clearly demonstrates its value and effectiveness._x000D_ _x000D_ Hercules-ASIO Initiative:_x000D_ https://datos.gob.es/en/blog/hercules-asio-initiative-integration-publication-and-consultation-linked-open-research-data_x000D_ _x000D_ Wikidata W3C Announcement: _x000D_ https://www.w3.org/community/shex/2019/06/18/wikidata-infrastructure-supports-shex/_x000D_ _x000D_ Wikidata Schemas Reference:_x000D_ https://www.wikidata.org/wiki/Wikidata:WikiProject_Schemas_x000D_ _x000D_ Shape Expressions (ShEx) 2.1 Reference:_x000D_ https://shex.io/shex-primer/"
'ShEx provides a schema mechanism for RDF data, enabling precise validation and documentation of data structures. While it does not directly expose or implement service interfaces, ShEx can support their development by ensuring that the RDF data exchanged through APIs or datasets is consistent and well-structured._x000D_ _x000D_ Shape Expressions (ShEx) 2.1 Reference:_x000D_ https://shex.io/shex-primer/_x000D_ _x000D_ W3C RDF Concepts and Abstract Data Model Reference:_x000D_ https://www.w3.org/TR/rdf12-concepts/'
'ShEx can be applied in data model development (creating new ones and refining existing ones) and is useful for reviewing or validate data, as it identifies and corrects issues before the data enters a business workflow._x000D_ _x000D_ Shape Expressions (ShEx) 2.1 Reference:_x000D_ https://shex.io/shex-primer/'
'Since public administration procedures, rules, and services are often represented in RDF, ShEx can be applied to validate these datasets. By enforcing consistent and complete structures, ShEx ensures that all relevant elements of administrative procedures and services are correctly represented._x000D_ _x000D_ Shape Expressions (ShEx) 2.1 Reference:_x000D_ https://shex.io/shex-primer/_x000D_ _x000D_ W3C RDF Concepts and Abstract Data Model Reference:_x000D_ https://www.w3.org/TR/rdf12-concepts/'
The standard or specification eases the implementation of the once-only principle.
The standard or specification has a strong support from at least one developer community.
The specification facilitates the publication of public data as open data.
Mechanisms to assess conformity of the implementations of the standard or specification (e.g. conformity tests, certifications) are available for free.
To what extent do restrictions and royalties apply to the specification's use?
The standard or specification is included in a catalogue of standards at EU level.
The standard or specification fosters the visibility and comprehensibility of administrative rules, processes, data, services and decision-making of a public administration.
The specification fosters the publication of data as Linked Open Data.
The standard or specification is proportionate to the needs of its users (citizens, businesses or administrations).
Is the specification licensed on a (F)RAND basis?
The specification is available for free on at least one national or European platform.
Does the implementation of the specification hamper interoperability with the implementation of existing European or international standards?
The specification fosters the visibility of administrative rules, data, services and decision-making of a public administration.
The standard or specification fosters the delivery of multilingual European public services.
The specification is licensed on a royalty-free basis
The standard or specification is a commonly accepted business process modelling standard or specification.
The specification fosters the creation of innovative solutions.
Are the specifications approved in a decision making process which aims at reaching consensus?
Does the specification provide means for restriction of access to information/data?
Has the specification been used for different implementations by different vendors/suppliers?
The specification is available for everyone to study.
Is the specification largely independent from specific vendor products?
The specification helps to ensure the availability of interfaces with internal information systems of a public administration.
The standard or specification is included in a catalogue of standards at national level.
The standard or specification is included in an interoperability agreement established between organisations involved in European public service provision.
The adoption of the standard or specification reduces the administrative burden.
The specification has been selected for its use in an EU cross-border project or initiative after agreed identification and assessment.
The specification is reusable beyond the domain for which it was originally developed.
The standard or specification is available for free on at least one national or European platform.
The standard or specification is reusable beyond the domain for which it was originally developed.
Is participation in the creation process of the specification open to all interested parties (e.g. organisations, companies or individuals)?
The standard or specification fosters the publication of data as Linked Open Data.
Is the specification included in any initiative at European or National level covering privacy aspects?
The standard or specification is available for everyone to study.
The specification fosters the delivery of multilingual European public services.
The specification is compliant with a European standardisation regulation (e.g. regulation 1025/2012 on European standardisation).
Does the specification address and facilitate interoperability between public administrations?
There are already existing studies or documentation assessing the standard or specification in terms of effectiveness and efficiency.
The standard or specification can be mapped to the EIRA.
The specification is independent of any specific technology and/or platform.
To what extent information is protected against unauthorised changes?
Is information on (new) standardisation activities widely announced through suitable and accessible means?
The specification is included in an interoperability agreement established between organisations involved in European public service provision.
The specification eases the implementation of the once-only principle.
The specification is sufficiently mature for its use in the development of products and services.
The specification defines organisational interoperability aspects (e.g. skills, language, etc.).
The standard or specification fosters data portability between systems and applications supporting the implementation and evolution of European public services when legally possible.
Has the specification sufficient detail, consistency and completeness for the use and development of products and services?
The standard or specification defines organisational interoperability aspects (e.g. skills, language, etc.).
The specification is included in a catalogue of standards at EU level.
The standard or specification fosters e-accessibility.
The specification fosters the comprehensibility of administrative rules, data, services and decision-making of a public administration.
The specification can be mapped to the European Interoperability Reference Architecture (EIRA).
Is the specification publicly available for implementation and use on reasonable terms?
The specification is included in a catalogue of standards at national level.
The standard or specification fosters the long-term preservation of electronic records and other kinds of information.
Does the specification encourage the creation of communities along with the sharing of their data and results in national and/or European platforms?
The specification defines a cross-sector reusable data model.
The specification fosters the long-term preservation of electronic records and other kinds of information.
Are you aware of public references of the respective specification by public authorities (especially policies or in procurements) ?
The specification is recommended by an EU Member State.
The specification has been included in a national catalogue from a Member State whose NIF is fully aligned with at least 4 out of 5 sections of the EIF according to NIFO factsheets.
Are there existing European standards with market uptake which cover the same areas as the proposed specification (or standard) being assessed?
Is the specification recommended by a European Member State?
To what extent does the specification ensure and enable data processing accuracy?
The standard or specification defines a cross-sector reusable data model.
Is the standards developing organisation a non-profit making organisation?
The standard or specification has been selected for its use in a EU cross-border project or initiative after agreed identification and assessment.
Is the specification selected for its use in a European Cross-border project/initiative?
The standard or specification is sufficiently mature and has sufficient market acceptance for its use in the development of products and services.
The specification is licensed on a (F)RAND basis
Is the specification largely independent from specific platforms or technologies?
All relevant stakeholders can formally appeal or raise objections to the development and approval of specifications?
The specification fosters data portability between systems and applications supporting the implementation and evolution of European public services when legally possible.
The specification has a strong support from at least one developer community.
Does the specification facilitate the publication of data on the web?
The standard has been made available for its reuse by the organisations, administrations, open communities, etc. that developed it.
The standard or specification is recommended by a EU Member State.
The standard or specification facilitates the publication of public data as open data.
To what extent does the specification enable data portability between systems/applications supporting the implementation or evolution of European public services?
To what extent does the specification provide an access control mechanism?
The specification is proportionate to the needs of its users (citizens, businesses or administrations).
The specification is a commonly accepted business process modelling specification.
The specification has been made available for its reuse by the organisations, administrations, open communities, etc. that developed it.
To what extent the specification guarantees the authenticity and authentication of the roles agents involved in the data transactions?
Is the adoption of new European Standards which cover the same areas as the proposed specification (or standard) foreseen within a reasonable timeframe?
Mechanisms to assess conformity of the implementations of the specification (e.g. conformity tests, certifications) are available for free.
Does the specification have a defined maintenance and support process?
There are already existing studies or documentation assessing the specification in terms of effectiveness and efficiency.
The standard or specification fosters the creation of innovative solutions.
The specification has sufficient market acceptance for its use in the development of products and services.
Is relevant documentation of the development and approval process of the specification archived and identified?
The standard or specification has been included in a national catalogue from a Member State whose NIF is fully aligned with at least 4 out of 5 sections of the EIF according to NIFO factsheets.
Is there evidence that the adoption of the specification positively impacts one or several of the following: organisational processes; the environment; the administrative burden; the disability support; cross-border services, public policy objectives and societal needs ?
The standard or specification is licensed on a (F)RAND basis
The standard or specification is independent from any specific technology and/or platform.
The standard or specification is compliant with a European standardisation regulation (e.g. regulation 1025/2012 on European standardisation).
The standard or specification is licensed on a royalty-free basis
The standard or specification helps ensuring the availability of interfaces with internal information systems of a public administration.
Does the technical specification or standard cover areas different from areas addressed by technical specifications being under consideration to become a European standard? (i.e. technical specifications provided by a non-formal standardisation organisation, that is other than CEN, CENELEC or ETSI can be under consideration to become a European standard or alternatively an identified technical specification)
The specification fosters e-accessibility.
The adoption of the specification reduces the administrative burden.
Does the specification encourage the creation of communities along with the sharing of their data and results on national platforms?
To what extent is the specification usable beyond the business-specific domain, allowing its implementation across business domains?
Is the specification selected for its use in an European Cross-border project/initiative?
To what extent does the specification enable data portability between systems/applications supporting the evolution of European public services?
The specification fosters the secure and trustworthy data exchange between citizens and businesses, and public administrations.
Is the specification available with any restrictions related to Fair, Reasonable, and Non-Discriminatory ((F)RAND)?
Is the specification recommended by an European Member State?
A public review is part of the decision-making process.
To what extent does the specification facilitate the publication of public data as open data?
To what extent does the specification enable data portability between systems/applications supporting the implementation of European public services?
Does the specification encourage the creation of communities along with the sharing of their data and results on European platforms?
Does the specification facilitate the publication of open data?
All stakeholders have the opportunity to contribute to the development of the specification
Is the specification included in an open repository/catalogue of standards at national level?
To what extent are there assessments of the specification's effectiveness?
Is the specification a European Standard?
Does the specification facilitate the modelling of business processes?
To what extent does the specification enable the long-term preservation of data/information/knowledge (electronic records included)?
To what extent does the specification enable the visibility of administrative procedures, rules data, and services?
To what extent could the specification be used in a multilingual context?
To what extent is a public review part of the release lifecycle?
To what extent does the specification enable the secure exchange of data?
To what extent does the specification ensure the protection of personal data managed by Public Administrations?
To what extent is the specification usable beyond the business-specific domain, allowing its usage across business domains?
To what extent does the specification facilitate organisational interoperability agreements?
Is the specification included in an open repository/catalogue of standards at European level?
Is the (or could it be) specification mapped to the European Interoperability Architecture (EIRA)?
Is the specification technology agnostic?
To what extent does the specification scope comprehensibly administrative procedures, rules data, and services?
To what extent has the specification been included in a national catalogue from a Member State whose National Interoperability Framework has a high performance on interoperability according to National Interoperability Framework Observatory factsheets?
Is the specification platform agnostic?
Does the specification enable digital service delivery channels?
To what extent does the specification enable the secure processing of data?
To what extent has the specification sufficient market acceptance for its use in the development of digital solutions/services?
To what extent can the conformance of the specification's implementations be assessed?
To what extent does the specification enable the e-accessibility?
To what extent does the specification enable the exposure of interfaces to access the public administration's services?
Is the specification licensed on a royalty-free basis?
To what extent does the specification allow relevant information to be reused when needed?
To what extent are there assessments of the specification's efficiency?
To what extent do stakeholders have the opportunity to contribute to the development of the specification?
Does the specification allow extension?
Does the specification allow customisation?
Does the specification simplify the delivery of European public services?
To what extent does the specification allow for partial implementations?
To what extent is the specification sufficiently mature for its use in the development of digital solutions/services?
To what extent has the specification support from at least one community?
The European Interoperability Framework(EIF) provides guidance to public administrations on how to improve governance of their interoperability activities, establish cross-organisational relationships, streamline processes supporting end-to-end digital services, and ensure that existing and new legislation do not compromise interoperability efforts.This CAMSS Scenario allows to assess the compliance of interoperability specifications with the EIF. The objective of the obtained assessment is to determine the suitability of the assessed interoperability specification for the delivery of interoperable European public services.
MSP
EIF
CAMSS Team European Commission DG-DIGIT