diff --git a/resources/fixtures/EIRA_SKOS.rdf b/resources/fixtures/EIRA_SKOS.rdf index 6d26162d6b..a47a61d0b4 100644 --- a/resources/fixtures/EIRA_SKOS.rdf +++ b/resources/fixtures/EIRA_SKOS.rdf @@ -26,13 +26,13 @@ xmlns:cc="http://creativecommons.org/ns#"> Controlled vocabulary for the European Interoperability Reference Architecture (EIRA) - 2021-01-28 + 2021-08-02 Copyright (c) 2016 European Union. European Commission This file specifies the controlled vocabulary defined by the EIRA as SKOS concept schemes and SKOS concepts. This file specifies the controlled vocabulary defined by the EIRA as SKOS concept schemes and SKOS concepts. This file specifies the controlled vocabulary defined by the EIRA as SKOS concept schemes and SKOS concepts. - EIRA v4.0.0 + EIRA v4.1.0 eira http://data.europa.eu/dr8/ @@ -45,121 +45,177 @@ EIRA EIRA taxonomy - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - - LegalView - Legal View - - - - - - - - - - - - - - - PublicPolicy - Public Policy - + LegalView + Legal View + + + + + + + + + + + + + + + + PublicPolicy + [ABB9] Public Policy + DESCRIPTION: Set of principles followed by a public authority to bring about social change in the medium and long term in a given area. It is based on certain values and objectives and is implemented using a variety of methods. It applies on the territory within which the authority is authorised to act. Based on EuroVoc @@ -171,56 +227,39 @@ Syn. Policy Action INTEROPERABILITY SALIENCY: IoP Dimension: Governance IoP -The Public Policy ABB  is salient for legal interoperability because it drives the production and formulation of legislation, and it is one of the main context elements to be taken into account when organisation need to work together, as stated in the EIF: "Legal interoperability is about ensuring that organisations operating under different legal frameworks, policies and strategies are able to work together". +The Public Policy ABB is salient for legal interoperability because it drives the production and formulation of legislation, and it is one of the main context elements to be taken into account when organisation need to work together, as stated in the EIF: "Legal interoperability is about ensuring that organisations operating under different legal frameworks, policies and strategies are able to work together". EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Common Agricultural Policy (CAP) -The common agricultural policy (CAP) – one of Europe’s oldest policies – has evolved along with the EU. Today's CAP supports a modern, market-oriented farming sector ensuring the provision of safe, affordable, high quality food, produced sustainably and respecting strict standards (environmental, animal welfare, food safety, etc.), as well as supporting investment in the broader rural economy. -https://ec.europa.eu/info/strategy/agriculture_en - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- dct:spatial: The spatial (geographic) coverage related to this building block -- eira:status: The development or realisation status of this building block -- eira:specific_policy_issue: The specific policy issue that this solution supports -- eira:synonym: An alternative name for the building block/solution -- eira:policy_area: The policy area coverage of this solution -- eira:view]]> - ABB9 - - - - - - - - - InteroperableDigitalPublicServicesImplementationOrientation - Interoperable Digital Public Services Implementation Orientation - + + + + + InteroperableDigitalPublicServicesImplementationOrientation + [ABB111] Interoperable Digital Public Services Implementation Orientation + DESCRIPTION: It is the specific set of decision making rules/criteria/principles followed at implementing a digital public services through organisations, persons, objects or events (Hill & Hupe, 2002). In the MIS literature it is considered as the focus selected for the implementation (Hill & Hupe, 2002; Marchand et al., 2000; Santosuosso & Malerba, 2014). The following implementation orientations are identified in the literature: integration, technology, governance and legal. -• The INTEGRATION ORIENTATION (Marchand et al., 2000) is characterized by a focus on data resources and on information management capabilities to manage information resources over their life cycle (i.e. scanning, collecting, organising, processing, maintaining, etc.) to understand societal needs, to embed data throughout the policy cycle, and to develop a culture of data analytics (OECD, 2018). The integration orientation will be based on semantic interoperability aiming for the design of a shared knowledge base of usable data, information and knowledge resources that enables: + The INTEGRATION ORIENTATION (Marchand et al., 2000) is characterized by a focus on data resources and on information management capabilities to manage information resources over their life cycle (i.e. scanning, collecting, organising, processing, maintaining, etc.) to understand societal needs, to embed data throughout the policy cycle, and to develop a culture of data analytics (OECD, 2018). The integration orientation will be based on semantic interoperability aiming for the design of a shared knowledge base of usable data, information and knowledge resources that enables: i) structural interoperability by using and/or sharing of data, organisational information and organisational knowledge (i.e. data set catalogue, base registries, catalogue of ontologies); ii) behavioural interoperability by exchanging capabilities of data, organisational information and organisational knowledge with the environment (i.e. representation, data mappings); and iii) governance interoperability by semantic interoperability agreements (i.e. ontologies). -• The TECHNOLOGY ORIENTATION (Marchand et al., 2000) is characterized by a focus on ICT resources like solutions and infrastructure and on ICT management capabilities to manage the provision of services (i.e. business operations, decision making, internal support, etc.) to users and the consumption of services by ministries and agencies (OECD, 2018). The technology orientation will be based on technical interoperability aiming for the design of a shared platform of ICT resources (i.e. the platform) that enables: + The TECHNOLOGY ORIENTATION (Marchand et al., 2000) is characterized by a focus on ICT resources like solutions and infrastructure and on ICT management capabilities to manage the provision of services (i.e. business operations, decision making, internal support, etc.) to users and the consumption of services by ministries and agencies (OECD, 2018). The technology orientation will be based on technical interoperability aiming for the design of a shared platform of ICT resources (i.e. the platform) that enables: i) structural interoperability by reusing and/or sharing of software components (i.e. service registry service, networks, reusable building blocks, common [back office] services); ii) behavioural interoperability with ICT exchanging capabilities of data, information or knowledge with internal/external peers (i.e. intermediation services, interfaces); an iii) governance interoperability with technical interoperability agreements (i.e. protocols, choreography rules). -• The GOVERNANCE ORIENTATION (Marchand et al., 2000) is characterized by a focus on the governance resources (Grant et al., 2007) and on governance management capabilities/archetypes to manage the effective use of information (i.e. sharing, security, privacy, etc.) for the effective use of information (i.e. sharing, security, privacy, etc.) to achieve a more agile, effective, and digitally inclusive public engagement, to increase trust in government, and to enhance government transparency (OECD, 2018; Weill & Woodham, 2002). The governance orientation will be based on organisational interoperability aiming for the design of a shared governance framework of [re]usable organisational resources that enables: + The GOVERNANCE ORIENTATION (Marchand et al., 2000) is characterized by a focus on the governance resources (Grant et al., 2007) and on governance management capabilities/archetypes to manage the effective use of information (i.e. sharing, security, privacy, etc.) for the effective use of information (i.e. sharing, security, privacy, etc.) to achieve a more agile, effective, and digitally inclusive public engagement, to increase trust in government, and to enhance government transparency (OECD, 2018; Weill & Woodham, 2002). The governance orientation will be based on organisational interoperability aiming for the design of a shared governance framework of [re]usable organisational resources that enables: i) structural interoperability by reusing and/or sharing of digital public services (i.e. public services catalogue); ii) behavioural interoperability with organisational exchanging capabilities of data, information or knowledge with internal/external peers (i.e. service delivery model); and iii) governance interoperability with organisational interoperability agreements (i.e. service level agreements, governance structures). -• The LEGAL ORIENTATION (Santosuossa and Malerba, 2014) is characterized by a focus on legal and regulatory frameworks based in displayed leadership and political commitment to ensure adaptation to rapidly changing technological and diverse social environments with high-level requirements to achieve coherence and effective support to digital public services implementation (OECD, 2018). The legal orientation will be based in legal interoperability aiming for the design of a shared legal framework of [re]usable legal resources that enables: + The LEGAL ORIENTATION (Santosuossa and Malerba, 2014) is characterized by a focus on legal and regulatory frameworks based in displayed leadership and political commitment to ensure adaptation to rapidly changing technological and diverse social environments with high-level requirements to achieve coherence and effective support to digital public services implementation (OECD, 2018). The legal orientation will be based in legal interoperability aiming for the design of a shared legal framework of [re]usable legal resources that enables: i) structural interoperability by legislation on reusing and/or sharing orientation and guidelines (i.e. legislation catalogue, interoperability reference architectures); ii) behavioural interoperability by legislation on exchanging capabilities of data, information or knowledge with internal/external peers (i.e. interoperability frameworks); and iii) governance interoperability by legislation on governance agreements (i.e. GDPR). @@ -233,26 +272,15 @@ The following implementation is an example on how this specific Architecture Bui Next Generation Digital Government Architecture v1.0 by Republic of Estonia (2020) https://docs.google.com/document/d/1UJ-5wi9wavWzA2n4LhsbONJqdxjUSIgMxKJNaZZslas/edit?fbclid=IwAR2rrBNjwHFagHIvi-9Pv6uvKI0IZH_m4IdAfaq7hbjALlIjRH8nEuUVuic -Customs 2020 is an EU cooperation programme providing national customs administrations with the possibility to create and exchange information and expertise. It allows developing and operating major trans-European IT systems in partnership and establishing various human networks by bringing together national officials from across Europe. The programme has a budget of € 547.3 million and will run for 7 years from January 1 2014. -https://ec.europa.eu/taxation_customs/business/customs-cooperation-programmes/customs-2020-programme_en - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:synonym: An alternative name for the building block/solution -- eira:view]]> - ABB111 - - - - - - - PublicPolicyCycle - Public Policy Cycle - + + + + + PublicPolicyCycle + [ABB102] Public Policy Cycle + DESCRIPTION: The series of public policy phases that are regularly repeated in order to manage all aspects of a public policy. Based on EU Better Regulation (list of phases) and Oxford dictionary (cycle definition) @@ -270,28 +298,18 @@ The following implementation is an example on how this specific Architecture Bui Performance-based Full Policy Cycle for the Digital Single Market The key features of a performance-based full policy cycle are a clear articulation of policy objectives, the identification and use of quantitative indicators of expected short-term and longer-term policy impacts, the identification of synergies between policies, a much greater use of quantitative data in ex-ante impact assessments, the implementation of robust, data-based, independent ex post assessments of the performance of policies relative to their expected impacts and a wide dissemination of lessons learned in such ex-post performance assessments. -http://www.europarl.europa.eu/RegData/etudes/etudes/join/2013/507457/IPOL-IMCO_ET(2013)507457_EN.pdf - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:synonym: An alternative name for the building block/solution -- eira:view]]> - ABB102 - - - - - - BindingInstrument - Binding Instrument - + + + + + BindingInstrument + [ABB17] Binding Instrument + DESCRIPTION: Legal means, involving an obligation, which are available to the European institutions to carry out their tasks. The European binding instruments listed in Article 288 of the Treaty on the Functioning of the European Union are: -• regulations: these are binding in their entirety and directly applicable in all EU countries; -• directives: these bind the EU countries as to the results to be achieved; they have to be transposed into the national legal framework and thus leave margin for manoeuvre as to the form and means of implementation; -• decisions: these are fully binding on those to whom they are addressed. + regulations: these are binding in their entirety and directly applicable in all EU countries; + directives: these bind the EU countries as to the results to be achieved; they have to be transposed into the national legal framework and thus leave margin for manoeuvre as to the form and means of implementation; + decisions: these are fully binding on those to whom they are addressed. Based on EUR-Lex http://eur-lex.europa.eu/summary/glossary/community_legal_instruments.html @@ -317,29 +335,17 @@ The following implementation is an example on how this specific Architecture Bui Decision No 922/2009/EC of the European Parliament and of the Council of 16 September 2009 on interoperability solutions for European public administrations (ISA) 1. This Decision establishes, for the period 2010-2015, a programme on interoperability solutions for European public administrations, including local and regional administrations and Community institutions and bodies, providing common and shared solutions facilitating interoperability (the ISA programme). 2. The objective of the ISA programme is to support cooperation between European public administrations by facilitating the efficient and effective electronic cross-border and cross-sectoral interaction between such administrations, including bodies performing public functions on their behalf, enabling the delivery of electronic public services supporting the implementation of Community policies and activities. -http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX%3A32009D0922 - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- dct:description: A short description providing an overview of this building block -- dct:spatial: The spatial (geographic) coverage related to this building block -- eira:supporting_a_TES: Is the enforcement of this legal instrument supported by the solution? -- eira:implementation_supported_by_a_TES: Is the enforcement of this legal instrument supported by the solution? -- eira:view]]> - ABB17 - - - - - Non-bindingInstrument - Non-binding Instrument - + + + + + Non-bindingInstrument + [ABB113] Non-binding Instrument + DESCRIPTION: Legal means, involving no obligation, which are available to the European institutions to carry out their tasks. The European non-binding, declaratory instruments listed in Article 288 of the Treaty on the Functioning of the European Union are recommendations and opinions: -• Recommendations are non-mandatory acts issued by the European Commission, the Council of the European Union, or the European Central Bank which suggest a certain form of conduct to those to whom they are addressed without imposing any legal obligations. -• Opinions are non-binding legal acts adopted by the European institutions which do not bind those to whom they are addressed. + Recommendations are non-mandatory acts issued by the European Commission, the Council of the European Union, or the European Central Bank which suggest a certain form of conduct to those to whom they are addressed without imposing any legal obligations. + Opinions are non-binding legal acts adopted by the European institutions which do not bind those to whom they are addressed. Based on EUR-Lex and EuroVoc http://eur-lex.europa.eu/summary/glossary/community_legal_instruments.html?locale=en @@ -361,25 +367,14 @@ The following implementation is an example on how this specific Architecture Bui Action Plan for the future of Organic Production in the European Union The Commission launched a consultation for the review of the European policy on organic agriculture in 2012-2013. This consultation has also been an opportunity to consult experts, stakeholders and the public on areas where a new action plan might be needed. To help organic farmers, producers and retailers adjust to the proposed policy changes and meet future challenges, the Commission has also approved an Action Plan on the future of Organic Production in Europe. The Plan foresees to better inform farmers on rural development and EU farm policy initiatives encouraging organic farming, to strengthen links between EU research and innovation projects and organic production and to encourage the use of organic food, e.g. in schools. -https://ec.europa.eu/agriculture/organic/eu-policy/european-action-plan_en - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- dct:description: A short description providing an overview of this building block -- dct:spatial: The spatial (geographic) coverage related to this building block -- eira:supporting_a_TES: Is the enforcement of this legal instrument supported by the solution? -- eira:implementation_supported_by_a_TES: Is the enforcement of this legal instrument supported by the solution? -- eira:view]]> - ABB113 - - - - LegalAct - Legal Act - + + + + + LegalAct + [ABB164] Legal Act + DESCRIPTION: Formalised set of rules on a subject potentially including requirements concerning digital public services. The granularity of the requirements might be of high level or detail level. Requirements of high-level granularity contain generic/abstract functional requirements like principles and/or recommendations with considerable degrees for transposition/execution and of not binding nature. On the other side, requirements of detail-level granularity imply a limited degree for transposition/execution and they contain specific/concrete functionalities, solution components, data, procedures, and/or technical specifications or standards to be used. EU legal acts are legislative or non-legislative acts adopted by the European institutions (Article 288 TFEU). With the entry into force of the Treaty of Lisbon on 1 December 2009. The names "European Union" or "EU" have replaced "European Community", "Community" or "EC". Source: https://eur-lex.europa.eu/summary/glossary/legislative_acts.html @@ -394,35 +389,14 @@ The following implementation is an example on how this specific Architecture Bui COMMISSION REGULATION (EU) 2018/1881 of 3 December 2018 amending Regulation (EC) No 1907/2006 of the European Parliament and of the Council on the Registration, Evaluation, Authorisation and Restriction of Chemicals (REACH) as regards Annexes I, III,VI, VII, VIII, IX, X, XI, and XII to address nanoforms of substances. -https://eur-lex.europa.eu/legal-content/EN/TXT/?qid=1544102387245&uri=CELEX:32018R1881 - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- dct:spatial: The spatial (geographic) coverage related to this building block -- eira:description: A short description providing an overview of this building block -- eira:requirement_or_constraint: Does this legal intrument act as a requirement for the solution or a constraint? -- eira:implementation_supported_by_a_TES: Is the enforcement of this legal instrument supported by the solution? -- eira:supporting_a_TES: Is the enforcement of this legal instrument supported by the solution? -- eira:legislation_catalogue_uri: URI to the legislation catalogue -- eira:legislation_catalogue_scheme_identifier: Scheme identifier of the legislation catalogue -- eira:view]]> - ABB164 - - - - - - - - - - - LegislationCatalogue - Legislation Catalogue - + + + + + LegislationCatalogue + [ABB165] Legislation Catalogue + DESCRIPTION: Indexed inventory of legal documents with comprehensiveness and trustiness value (*)DECISION (EU) 2015/2240 OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 25 November 2015 establishing a programme on interoperability solutions and common frameworks for European public administrations, businesses and citizens (ISA2 programme) as a means for modernising the public sector @@ -442,34 +416,24 @@ The following implementation is an example on how this specific Architecture Bui EUR-Lex EUR-Lex provides free access, in the 24 official EU languages, to: -• the authentic Official Journal of the European Union -• EU law (EU treaties, directives, regulations, decisions, consolidated legislation, etc.) -• preparatory acts (legislative proposals, reports, green and white papers, etc.) -• EU case-law (judgments, orders, etc.) -• international agreements -• EFTA documents -• summaries of EU legislation, which put legal acts into a policy context, explained in plain language -• other public documents. + the authentic Official Journal of the European Union + EU law (EU treaties, directives, regulations, decisions, consolidated legislation, etc.) + preparatory acts (legislative proposals, reports, green and white papers, etc.) + EU case-law (judgments, orders, etc.) + international agreements + EFTA documents + summaries of EU legislation, which put legal acts into a policy context, explained in plain language + other public documents. It also allows you to follow the procedures leading to the adoption of legal acts. -http://eur-lex.europa.eu/ - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:synonym: An alternative name for the building block/solution -- eira:view]]> - ABB165 - - - - - - LegalInteroperabilityAgreement - Legal Interoperability Agreement - + + + + + LegalInteroperabilityAgreement + [ABB226] Legal Interoperability Agreement + DESCRIPTION: A legal interoperability agreement is legal resource formalizing governance rules enabling collaboration between digital public services Based on EIF: @@ -484,22 +448,14 @@ The following implementation is an example on how this specific Architecture Bui RDA-CODATA Agreement that provides the guidelines and principles on the legal interoperability of research data. -http://www.codata.org/uploads/Legal%20Interoperability%20Principles%20and%20Implementation%20Guidelines_Final2.pdf - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:policy_area: The policy area coverage of this solution -- eira:view]]> - ABB226 - - - - - LegislationOnDataInformationAndKnowledgeExchange - Legislation on Data Information and Knowledge Exchange - + + + + + LegislationOnDataInformationAndKnowledgeExchange + [ABB356] Legislation on Data Information and Knowledge Exchange + DESCRIPTION: Legal act on the exchange of data, information, and knowledge between different agents (private and public) at national and/or cross-border level. INTEROPERABILITY SALIENCY @@ -516,23 +472,14 @@ The Regulation ensures: - The availability of data for regulatory control: public authorities will retain access to data, also when it is located in another Member State or when it is stored or processed in the cloud, - Easier switching of cloud service providers for professional users. The Commission has started facilitating self-regulation in this area, encouraging providers to develop codes of conduct regarding the conditions under which users can port data between cloud service providers and back into their own IT environments, - Full consistency and synergies with the cybersecurity package, and clarification that any security requirements that already apply to businesses storing and processing data will continue to do so when they store or process data across borders in the EU or in the cloud. -https://ec.europa.eu/knowledge4policy/publication/regulation-free-flow-non-personal-data_en - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- dct:description: A short description providing an overview of this building block -- eira:view]]> - ABB356 - - - - - LegalAuthority - Legal Authority - + + + + + LegalAuthority + [ABB227] Legal Authority + DESCRIPTION: It is an entity with entitled powers. The powers that a public administration exercises during the above mentioned life cycle are of the following four types: Legislation, control (monitoring, enforcing, sanctioning, etc.), economic (taxes, subsidies, expenditures, funding, etc.) and (public service) provision (Thijs et al., 2017). Sources: @@ -543,7 +490,7 @@ https://ec.europa.eu/isa2/sites/isa/files/eif_brochure_final.pdf INTEROPERABILITY SALIENCY: IoP Dimension: Governance IoP -The Legal Authority ABB  is salient for interoperability because it supports legal interoperability by providing reliability and trustworthiness of Legal Interoperability Agreement. +The Legal Authority ABB is salient for interoperability because it supports legal interoperability by providing reliability and trustworthiness of Legal Interoperability Agreement. EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): @@ -551,24 +498,14 @@ The following implementation is an example on how this specific Architecture Bui EU Parliament European Parliament The European Parliament (EP) is the directly elected parliamentary institution of the European Union (EU). Together with the Council of the European Union (the Council) and the European Commission, it exercises the legislative function of the EU. -http://www.europarl.europa.eu/plenary/en/home.html - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:view]]> - ABB227 - - - - - - - SharedLegalFramework - Shared Legal Framework - + + + + + SharedLegalFramework + [ABB357] Shared Legal Framework + DESCRIPTION: A shared legal framework is formed by [re]usable legal resources, with convergence power, in relation to public policy goals attainment, given by their legally binding nature, across the levels of a public administration (central, regional, local) towards the achievement of the public policy goals, enabling : i) structural interoperability by legal resources supporting reusing and/or sharing legislation (i.e. legislation catalogue enabling provisioning/consuming legal texts cross public administrations and cross borders); ii) behavioural interoperability by legal resources supporting exchanging capabilities of data, information or knowledge with internal/external peers (i.e. Legislation on Knowledge, Information and data exchange enabling that data/information/knowledge be provisioned/consumed cross public administrations and cross borders ); and @@ -576,27 +513,14 @@ iii) governance interoperability by legislation supporting the collaboration wit INTEROPERABILITY SALIENCY: IoP dimensions: Structural IoP, Behavioral IoP, Governance IoP -This ABB is a key interoperability enabler because it supports to achieve legal interoperability with public policy goals convergence value by all in all enabling i) sharing/provisioning/reusing/consumption of legislation on digital public services, ii) the exchange of data, information, and knowledge between digital public services, and iii) collaboration between digital public services - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- dct:description: A short description providing an overview of this building block -- eira:view]]> - ABB357 - - - - - - - - - LegalAgreements/InternationalTreaties - Legal Agreements / International Treaties - + + + + + LegalAgreements/InternationalTreaties + [ABB368] Legal Agreements / International Treaties + DESCRIPTION: Under international law, a treaty is any legally binding agreement between states (countries). A treaty can be called a Convention, a Protocol, a Pact, an Accord, etc.; it is the content of the agreement, not its name, which makes it a treaty. Based on EIF: @@ -608,59 +532,44 @@ Not applicable EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): -An example of a treaty that does have provisions for further binding agreements is the UN Charter. By signing and ratifying the Charter, countries agreed to be legally bound by resolutions passed by UN bodies such as the General Assembly and the Security Council. Thus, UN resolutions are legally binding on UN Member States, and no signature or ratification is necessary. - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:policy_area: The policy area coverage of this solution -- eira:view -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified]]> - ABB368 - - - - - - - OrganisationalView - Organisational View - - - - - - - - - - - - - - - - - - - - - - - - - - - - - InteroperableDigitalPublicService - Interoperable Digital Public Service - + + + + + OrganisationalView + Organisational View + + + + + + + + + + + + + + + + + + + + + + + + + + + + PublicService + [ABB1] Public Service + DESCRIPTION: +It is an interoperable public service provisioned by or on behalf of a public administration in support to the realization of a Public Administration digital business capability. An European digital public service comprises any digital public service exposed to a cross-border dimension in the Union. Sources: EIF, ISA2 Core Vocabularies, IMM http://eur-lex.europa.eu/resource.html?uri=cellar:2c2f2554-0faf-11e7-8a35-01aa75ed71a1.0017.02/DOC_3&format=PDF @@ -677,34 +586,14 @@ The following implementation is an example on how this specific Architecture Bui EUROPASS2 - Make better use of skills and opportunities across Europe Europass is a service to help individuals to communicate their skills, qualifications and experience through the use of standardised documents templates. -http://ec.europa.eu/social/main.jsp?catId=1266&langId=en - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:view]]> - ABB1 - - - - - - - - - - - - - - - - - InteroperabilityStrategy - Interoperability Strategy - + + + + + InteroperabilityStrategy + [ABB208] Interoperability Strategy + DESCRIPTION: The overarching strategic plan in the area of cross-border interoperability. Source: ISA2 @@ -712,7 +601,7 @@ https://ec.europa.eu/isa2/actions/continuously-updating-european-interoperabilit INTEROPERABILITY SALIENCY: IoP Dimension: Governance IoP -The Interoperability Strategy ABB  is an interoperability enabler because it helps achieve organisational interoperability by setting up the vision and principles for the development of the interoperability capabilities. The European Interoperability Framework implements the European Interoperability Strategy. +The Interoperability Strategy ABB is an interoperability enabler because it helps achieve organisational interoperability by setting up the vision and principles for the development of the interoperability capabilities. The European Interoperability Framework implements the European Interoperability Strategy. EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): @@ -720,25 +609,15 @@ The following implementation is an example on how this specific Architecture Bui European Interoperability Strategy (EIS) COMMUNICATION FROM THE COMMISSION TO THE EUROPEAN PARLIAMENT, THE COUNCIL, THE EUROPEAN ECONOMIC AND SOCIAL COMMITTEE AND THE COMMITTEE OF THE REGIONS - Towards interoperability for European public services This Communication introduces the European Interoperability Strategy (EIS) and the European Interoperability Framework (EIF) for European public services, two key elements in the Digital Agenda. Together, they promote interoperability among public administrations. -The European Interoperability Strategy (EIS) is developed by the European Commission’s Directorate-General for Informatics. The EIS aims to provide guidance and to prioritise the actions needed to improve interaction, exchange and cooperation among European public administrations across borders and across sectors for the delivery of European public services. -http://eur-lex.europa.eu/resource.html?uri=cellar:f132547a-7d66-4626-8eb6-9f7428394de7.0017.03/DOC_2&format=PDF - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:reusability: Whether or not this building block could be reused as part of another solution -- eira:view]]> - ABB208 - - - - - - InteroperabilityFramework - Interoperability Framework - + + + + + InteroperabilityFramework + [ABB206] Interoperability Framework + DESCRIPTION: An agreed governance approach to interoperability for organisations that wish to collaborate towards the joint delivery of public services. Within its scope of applicability, it specifies a set of common elements such as vocabulary, concepts, principles, guidelines, and recommendations, Source: ISA2, EIFv2 @@ -748,7 +627,7 @@ Syn. Interoperability Supporting Structure INTEROPERABILITY SALIENCY: IoP Dimension: Governance IoP -The Interoperability Framework ABB  is an interoperability enabler because it helps achieve organisational interoperability by defining a set of rules, practices and a commonly agreed approach to the delivery of European public services. The EIF is an instance of this building block: "The European interoperability framework is a commonly agreed approach to the delivery of European public services in an interoperable manner. It defines basic interoperability guidelines in the form of common principles, models and recommendations." +The Interoperability Framework ABB is an interoperability enabler because it helps achieve organisational interoperability by defining a set of rules, practices and a commonly agreed approach to the delivery of European public services. The EIF is an instance of this building block: "The European interoperability framework is a commonly agreed approach to the delivery of European public services in an interoperable manner. It defines basic interoperability guidelines in the form of common principles, models and recommendations." EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): @@ -756,28 +635,16 @@ The following implementation is an example on how this specific Architecture Bui The new European Interoperability Framework (EIF) The new European Interoperability Framework (EIF) is part of the Communication (COM(2017)134) from the European Commission adopted on 23 March 2017. The framework gives specific guidance on how to set up interoperable digital public services. It offers public administrations 47 concrete recommendations on how to improve governance of their interoperability activities, establish cross-organisational relationships, streamline processes supporting end-to-end digital services, and ensure that both existing and new legislation do not compromise interoperability efforts. -The new EIF is undertaken in the context of the Commission priority to create a Digital Single Market in Europe. The public sector, which accounts for over a quarter of total employment and represents approximately a fifth of the EU’s GDP through public procurement, plays a key role in the Digital Single Market as a regulator, services provider and employer. +The new EIF is undertaken in the context of the Commission priority to create a Digital Single Market in Europe. The public sector, which accounts for over a quarter of total employment and represents approximately a fifth of the EUs GDP through public procurement, plays a key role in the Digital Single Market as a regulator, services provider and employer. The successful implementation of the EIF will improve the quality of European public services and will create an environment where public administrations can collaborate digitally. -https://ec.europa.eu/isa2/eif_en - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:view]]> - ABB206 - - - - - - - - - InteroperabilityGovernance - Interoperability Governance - + + + + + InteroperabilityGovernance + [ABB214] Interoperability Governance + DESCRIPTION: Set of organizing rules assuring the functioning of an Interoperability Framework . These rules include structures, roles, responsibilities, policies, standards, specifications, practices, decision making and operational procedures. Source: the New EIF @@ -787,7 +654,7 @@ Syn. Interoperability management method or system INTEROPERABILITY SALIENCY: IoP Dimension: Governance IoP -The Interoperability Governance ABB  is an interoperability enabler because it helps achieve organisational interoperability as it is " the key to a holistic approach on interoperability, as it brings together all the instruments needed to apply it" (EIF). As stated in EIF Recommendation 20: "Ensure holistic governance of interoperability activities across administrative levels and sectors." +The Interoperability Governance ABB is an interoperability enabler because it helps achieve organisational interoperability as it is " the key to a holistic approach on interoperability, as it brings together all the instruments needed to apply it" (EIF). As stated in EIF Recommendation 20: "Ensure holistic governance of interoperability activities across administrative levels and sectors." EXAMPLES: The following implementations are examples on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): @@ -797,25 +664,15 @@ Member States shall ensure that appropriate structures and mechanisms are design http://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=CELEX:32007L0002&from=EN Governance defined in the new European Interoperability Framework (EIF) -§ 3.1 of the new EIF Annex II: Interoperability governance refers to decisions on interoperability frameworks, institutional arrangements, organisational structures, roles and responsibilities, policies, agreements and other aspects of ensuring and monitoring interoperability at national and EU levels. The European interoperability framework, the Interoperability Action Plan (Annex 1 to the Communication) and the European interoperability architecture (EIRA) are important parts of interoperability governance at the EU level. -http://eur-lex.europa.eu/resource.html?uri=cellar:2c2f2554-0faf-11e7-8a35-01aa75ed71a1.0017.02/DOC_3&format=PDF - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:view]]> - ABB214 - - - - - - - InteroperabilityOrganisationalAuthority - Interoperability Organisational Authority - + + + + + InteroperabilityOrganisationalAuthority + [ABB205] Interoperability Organisational Authority + DESCRIPTION: An organisation having the powers to govern the interoperability of public administration Based on the definitions of authority and organisational in the Oxford dictionary. @@ -825,7 +682,7 @@ Syn. Interoperability Coordination Power or Right, or Control INTEROPERABILITY SALIENCY: IoP Dimension: Governance IoP -The Interoperability Organisational Authority ABB  is an interoperability enabler because it helps achieve organisational interoperability by ensuring political and/or administrative governance of the interoperability capabilities of an organisation as stated in the EIF Recommendation 20: "Ensure holistic governance of interoperability activities across administrative levels and sectors". +The Interoperability Organisational Authority ABB is an interoperability enabler because it helps achieve organisational interoperability by ensuring political and/or administrative governance of the interoperability capabilities of an organisation as stated in the EIF Recommendation 20: "Ensure holistic governance of interoperability activities across administrative levels and sectors". EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): @@ -835,22 +692,14 @@ INSPIRE Directive 2007/2/EC of 14 March 2007, Article 19 1. The Commission shall be responsible for coordinating Inspire at Community level and shall be assisted for that purpose by relevant organisations and, in particular, by the European Environment Agency. 2. Each Member State shall designate a contact point, usually a public authority, to be responsible for contacts with the Commission in relation to this Directive. This contact point will be supported by a coordination structure, taking account of the distribution of powers and responsibilities within the Member State. -http://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=CELEX:32007L0002&from=EN +http://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=CELEX:32007L0002&from=EN + + -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:view]]> - ABB205 - - - - - SecurityFramework - Security Framework - + SecurityFramework + [ABB223] Security Framework + DESCRIPTION: Agreed governance approach focusing on protection aspects on data, information and knowledge assets and organizational resources handling them. Source: ISA2, EIFv2 @@ -858,7 +707,7 @@ https://ec.europa.eu/isa2/isa2_en INTEROPERABILITY SALIENCY: IoP Dimension: Governance IoP -The Security Framework ABB  is salient for interoperability because "security and privacy are primary concerns in the provision of public services" (EIF) and, as stated in EIF Recommendation 15: "Define a common security and privacy framework and establish processes for public services to ensure secure and trustworthy data exchange between public administrations and in interactions with citizens and businesses." +The Security Framework ABB is salient for interoperability because "security and privacy are primary concerns in the provision of public services" (EIF) and, as stated in EIF Recommendation 15: "Define a common security and privacy framework and establish processes for public services to ensure secure and trustworthy data exchange between public administrations and in interactions with citizens and businesses." EXAMPLES: @@ -869,25 +718,14 @@ Certification plays a critical role in increasing trust and security in products The proposed certification framework will provide EU-wide certification schemes as a comprehensive set of rules, technical requirements, standards and procedures. This will be based on agreement at EU level for the evaluation of the security properties of a specific ICT-based product or service e.g. smart cards. The certification will attest that ICT products and services that have been certified in accordance with such a scheme comply with specified cybersecurity requirements. The resulting certificate will be recognized in all Member States, making it easier for businesses to trade across borders and for purchasers to understand the security features of the product or service. The schemes proposed in the future European framework will rely as much as possible on international standards as a way to avoid creating trade barriers and ensuring coherence with international initiatives." -https://ec.europa.eu/digital-single-market/en/eu-cybersecurity-certification-framework - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:view]]> - ABB223 - - - - - - - - PrivacyFramework - Privacy Framework - + + + + + PrivacyFramework + [ABB228] Privacy Framework + DESCRIPTION: Agreed governance approach focusing on confidentiality aspects on data, information and knowledge assets and organizational resources handling them. Source: ISA2, EIFv2 @@ -895,32 +733,20 @@ https://ec.europa.eu/isa2/isa2_en INTEROPERABILITY SALIENCY: IoP Dimension: Governance IoP -The Privacy Framework ABB  is salient for interoperability because "security and privacy are primary concerns in the provision of public services" (EIF) and, as stated in EIF Recommendation 15: "Define a common security and privacy framework and establish processes for public services to ensure secure and trustworthy data exchange between public administrations and in interactions with citizens and businesses." +The Privacy Framework ABB is salient for interoperability because "security and privacy are primary concerns in the provision of public services" (EIF) and, as stated in EIF Recommendation 15: "Define a common security and privacy framework and establish processes for public services to ensure secure and trustworthy data exchange between public administrations and in interactions with citizens and businesses." EXAMPLES: European Privacy Framework European privacy legislation is made up of two parts: The Data Protection Directive (95/46/EC) exists as a common ground across Europe. The Directive is a legislative act of the European Union that requires all member states to ensure there is an "adequate" level of data protection. The second part consists of diverse national laws. -https://www.privacy-europe.com/european-privacy-framework.html - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:view]]> - ABB228 - - - - - - - - - InteroperabilitySkill - Interoperability Skill - + + + + + InteroperabilitySkill + [ABB220] Interoperability Skill + DESCRIPTION: Expertise in organizing, implementing and managing interoperability in digital public services Based on the definitions of skill and organisational in the Oxford dictionary. @@ -930,29 +756,21 @@ Syn. Interoperability Competence INTEROPERABILITY SALIENCY: IoP Dimension: Governance IoP -The Interoperability Skill ABB  is an interoperability enabler because it helps achieve organisational interoperability by removing a barrier to implement interoperability policies, as stated in the EIF: "Member States should include interoperability skills in their interoperability strategies, acknowledging that interoperability is a multi-dimensional issue that needs awareness and skills in legal, organisational, semantic and technical." +The Interoperability Skill ABB is an interoperability enabler because it helps achieve organisational interoperability by removing a barrier to implement interoperability policies, as stated in the EIF: "Member States should include interoperability skills in their interoperability strategies, acknowledging that interoperability is a multi-dimensional issue that needs awareness and skills in legal, organisational, semantic and technical." EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Surveillance3 - Knowledge of English to access and use the open data provided through the EU Open Data Portal -Knowledge of English is required in order to access and use the database of specific products under ‘surveillance’ or monitoring imported into the EU customs territory in the present and past years. The database for surveillance on the EUROPA web-site displays the volumes of specific products imported into the EU customs territory in the present and in the past year. -https://data.europa.eu/euodp/data/dataset/surveillance - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:view]]> - ABB220 - - - - - Business - Business - + + + + + Business + [ABB169] Business + DESCRIPTION: Economic operator with a legal entity entitled to perform a private activity for a profit. Source: IATE (definition of business, entry Environment [CdT]) @@ -969,21 +787,14 @@ The following implementation is an example on how this specific Architecture Bui Cosmetic Product Notification Portal - Economic operators Economic operators involved in intra-community trade are using the Cosmetic Product Notification Portal in order to either notify cosmetic products put on the EU market (distributors) or notify and update the data (manufacturers and importers). -https://webgate.ec.europa.eu/cpnp/faq/?event=faq.show - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:view]]> - ABB169 - - - - PublicAdministration - Public Administration - + + + + + PublicAdministration + [ABB172] Public Administration + DESCRIPTION: A state, regional or local authority governed by public law or an association formed by one or several such authorities or a private entity mandated by at least one of those authorities or associations to provide public services, when acting under such a mandate. Source: Connecting Europe Facility (CEF), eIDAS regulation @@ -998,25 +809,16 @@ The Public Administration ABB is salient for organisation interoperability becau EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): -EWRS – ECHA +EWRS ECHA The European Chemicals Agency (ECHA) is the driving force among regulatory authorities in implementing the EU's ground breaking chemicals legislation for the benefit of human health and the environment as well as for innovation and competitiveness. -https://echa.europa.eu/about-us - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- dct:spatial: The spatial (geographic) coverage related to this building block -- eira:view]]> - ABB172 - - - - - Organisation - Organisation - + + + + + Organisation + [ABB7] Organisation + DESCRIPTION: An Organisation is a principal that provides and/or consumes Public Services. Based on the New EIF and the ISA2 Core Vocabularies @@ -1033,24 +835,15 @@ EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): AFIS - Europol organisation -Europol is the European Union’s law enforcement agency. Its main goal is to achieve a safer Europe for the benefit of all the EU citizens. -https://www.europol.europa.eu/ - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:view]]> - ABB7 - - - - - - Citizen - Citizen - + + + + + Citizen + [ABB8] Citizen + DESCRIPTION: An individual is a principal that provides and/or consumes Public Services. A citizen is a member of a particular country and who has rights because of being born there or because of being given rights. Every national of a Member State shall be a citizen of the Union. Citizenship of the Union shall be additional to national citizenship and shall not replace it (Treaty of Maastricht on European Union, Title II Provisions on democratic principles, article 8). The main difference between the two (European citizenship and citizenship of a Member State) is that the rights that citizens enjoy as a result of European citizenship are not matched with duties. Legal basis: Articles 9 to 12 TEU and 18 to 25 TFEU (European Parliament). @@ -1070,26 +863,14 @@ The following implementation is an example on how this specific Architecture Bui EUROPASS2 - EU citizen Every national of a Member State shall be a citizen of the Union. -http://europass.cedefop.europa.eu/europass-and-you - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:view]]> - ABB8 - - - - - - - - - PublicServiceAgent - Public Service Agent - + + + + + PublicServiceAgent + [ABB229] Public Service Agent + DESCRIPTION: An agent that consumes or delivers a public service on behalf of a principal. Source: @@ -1100,28 +881,16 @@ IoP Dimension: Governance IoP The Public Service Agent is salient for organisational interoperability because it acts on behalf of a Public Service Consumer Agent to consume a Public Service and Public Service Provider Agent to deliver a Publice Service. EXAMPLES: -Your Europe Advice – ECAS -Your Europe Advice is an EU advice service provided by legal experts from ECAS (European Citizen Action Service) operating under contract with the European Commission. It consists of a team of about 60 lawyers who cover all 24 official EU languages and are familiar both with EU law and national laws in all EU countries. Your Europe Advice replies to questions from citizens or businesses on their personal EU rights. The experts respond to the questions within one week, free of charge and in the language chosen by the user. ECAS’ mission is to empower citizens to exercise their rights and promote open and inclusive decision-making through the provision of high quality advice, research and advocacy, as well as capacity building for civil society organisations. -http://ecas.org/services/your-europe-advice-yea/ " - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:view]]> - ABB229 - - - - - - - - - PublicServiceConsumerAgent - Public Service Consumer Agent - + + + + + PublicServiceConsumerAgent + [ABB230] Public Service Consumer Agent + DESCRIPTION: Any agent that consumes a public service on behalf of a principal. Source: @@ -1132,25 +901,16 @@ IoP Dimension: Governance IoP The Public Service Consumer Agent is salient for organisational interoperability because it acts on behalf of a Public Service Consumer (the "Principal") to consume a Public Service. An agent is described by the tuple <agent_type, principal_type>, where agent_type belongs to {human, machine}, and principal_type belongs to {citizen, business, PA}. EXAMPLES: -Your Europe Advice – ECAS -Your Europe Advice is an EU advice service provided by legal experts from ECAS (European Citizen Action Service) operating under contract with the European Commission. It consists of a team of about 60 lawyers who cover all 24 official EU languages and are familiar both with EU law and national laws in all EU countries. Your Europe Advice replies to questions from citizens or businesses on their personal EU rights. The experts respond to the questions within one week, free of charge and in the language chosen by the user. ECAS’ mission is to empower citizens to exercise their rights and promote open and inclusive decision-making through the provision of high quality advice, research and advocacy, as well as capacity building for civil society organisations. -http://ecas.org/services/your-europe-advice-yea/ " - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:view]]> - ABB230 - - - - - - PublicServiceConsumer - Public Service Consumer - + + + + + PublicServiceConsumer + [ABB5] Public Service Consumer + DESCRIPTION: A principal consuming public services. Source: Based on EIF 2.0 @@ -1167,39 +927,24 @@ The following implementation is an example on how this specific Architecture Bui Cosmetic Product Notification Portal CPNP - Poison centre, Responsible person, Market surveillance authority, Distributor, Health advisor, Administrations The CPNP is making this information available electronically to: -• Competent Authorities (for the purposes of market surveillance, market analysis, evaluation and consumer information) -• Poison Centres or similar bodies established by EU countries (for the purposes of medical treatment). + Competent Authorities (for the purposes of market surveillance, market analysis, evaluation and consumer information) + Poison Centres or similar bodies established by EU countries (for the purposes of medical treatment). The CPNP is accessible to: -• Competent Authorities -• European Poison Centres -• Cosmetic products responsible persons -• Distributors of cosmetic products - -https://ec.europa.eu/growth/sectors/cosmetics/cpnp_fr - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:view]]> - ABB5 - - - - - - - - - - - - OrganisationalInteroperabilityAgreement - Organisational Interoperability Agreement - + + + + + OrganisationalInteroperabilityAgreement + [ABB119] Organisational Interoperability Agreement + DESCRIPTION: An organisational interoperability agreement is a resource of private nature formalizing governance rules enabling collaboration between digital public services with enabling seamless functioning value The Organisational Interoperability Agreement ABB is a key interoperability enabler because it supports organisational governance interoperability by enabling collaboration between digital public services. @@ -1208,42 +953,29 @@ https://ec.europa.eu/isa2/isa2_en (*)DECISION (EU) 2015/2240 OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 25 November 2015 establishing a programme on interoperability solutions and common frameworks for European public administrations, businesses and citizens (ISA2 programme) as a means for modernising the public sector. -The agreement should include purposes and goals, terms and conditions, governance, and the description of the channel(s). The EIRA© differentiates the following Interoperability Agreements: +The agreement should include purposes and goals, terms and conditions, governance, and the description of the channel(s). The EIRA differentiates the following Interoperability Agreements: -• Interoperability Service Agreement (between Public Service Consumers and Public Service Providers; -• Interoperability Collaboration Agreement (between Organisations); or -• Interoperability Provider Agreement (between Public Service Providers). + Interoperability Service Agreement (between Public Service Consumers and Public Service Providers; + Interoperability Collaboration Agreement (between Organisations); or + Interoperability Provider Agreement (between Public Service Providers). INTEROPERABILITY SALIENCY: IoP Dimension: Governance IoP -Concrete and binding documents which set out the precise obligations of two parties cooperating across an ‘interface’ to achieve interoperability. +Concrete and binding documents which set out the precise obligations of two parties cooperating across an interface to achieve interoperability. EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): ICAO Service Level Agreement Template A Service Level Agreement (SLA) is an example of Interoperability Agreement in which parties agree on the description of the services to be provided by one or several parties to the other one(s). The SLA tackles topics like: service description, optional services, exclusions, limitations, service levels, service credits, escalation procedure, reporting and points of contact. -https://www.icao.int/ESAF/Documents/APIRG/APIRG18/Docs/wp17_appendices_en.pdf - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:reusability: Whether or not this building block could be reused as part of another solution -- eira:reuse_status: The type of reuse (if reusable): 'Exposed for reuse as main service' means that the building block is exposed to other solutions for reuse as the current solution's primary service. 'Exposed for reuse as supporting service' means that the building block is exposed to other solutions for reuse but only if the solution is already being reused for it's primary service. 'Reused' means that the building block is actually reused from another solution. -- eira:interoperability_type: The type of interoperability agreement this represents -- eira:view]]> - ABB119 - - - - - - - PublicServiceProvider - Public Service Provider - + + + + + PublicServiceProvider + [ABB174] Public Service Provider + DESCRIPTION: A principal deliverying public services. Based on IATE definition (definition of service producer, entry Economics, Taxation [Council]) @@ -1259,32 +991,16 @@ The following implementation is an example on how this specific Architecture Bui Ecolabel - Member State Competent Body The Competent Body is the independent organisation responsible for assessing, awarding, and managing EU Ecolabel applications and licences on the national level. The Competent Body provides guidance on the documents needed for the dossier, such as declarations, data sheets, and test results. Recommendations on product testing laboratories that are ISO 17025 accredited or equivalent are shared, along with any relevant technical expertise needed to complete the application. -Upon application approval, the Competent Body issues the contract and licence upon approving the application. This contract sets out the services or range of products covered within the licence, including any trade names or manufacturer’s internal reference numbers. It will also lay out the terms of use of the EU Ecolabel, following the standard contract in Annex IV of the Regulation (EC) No 66/2010 of 25 November 2009. Once the contract has been signed, a certificate can be asked for/will be sent, depending on the Competent Body. This certificate will detail: the licence number that can be used with the EU Ecolabel logo; the legal name of the applicant; the services or range of products awarded the EU Ecolabel; all relevant trade names under which the product is sold or the service is marketed. The Competent Body will give the final validation on when the EU Ecolabel logo and the licence number can be used on the EU Ecolabel services and products that have met the criteria. +Upon application approval, the Competent Body issues the contract and licence upon approving the application. This contract sets out the services or range of products covered within the licence, including any trade names or manufacturers internal reference numbers. It will also lay out the terms of use of the EU Ecolabel, following the standard contract in Annex IV of the Regulation (EC) No 66/2010 of 25 November 2009. Once the contract has been signed, a certificate can be asked for/will be sent, depending on the Competent Body. This certificate will detail: the licence number that can be used with the EU Ecolabel logo; the legal name of the applicant; the services or range of products awarded the EU Ecolabel; all relevant trade names under which the product is sold or the service is marketed. The Competent Body will give the final validation on when the EU Ecolabel logo and the licence number can be used on the EU Ecolabel services and products that have met the criteria. http://ec.europa.eu/environment/ecolabel/how-to-apply-for-eu-ecolabel.html -http://ec.europa.eu/environment/ecolabel/competent-bodies.html#be - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:unit_in_DG: The Directorate-General in charge of the solution (EC only) -- eira:view]]> - ABB174 - - - - - - - - - - - - PublicServiceDeliveryAgent - Public Service Delivery Agent - + + + + + PublicServiceDeliveryAgent + [ABB173] Public Service Delivery Agent + DESCRIPTION: Any agent that delivers a public service on behalf of a principal. Based on definition of Agent class in ISA2 Core Vocabularies @@ -1297,26 +1013,17 @@ The Public Service Delivery Agent is salient for organisational interoperability EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): -Your Europe Advice – ECAS -Your Europe Advice is an EU advice service provided by legal experts from ECAS (European Citizen Action Service) operating under contract with the European Commission. It consists of a team of about 60 lawyers who cover all 24 official EU languages and are familiar both with EU law and national laws in all EU countries. Your Europe Advice replies to questions from citizens or businesses on their personal EU rights. The experts respond to the questions within one week, free of charge and in the language chosen by the user. ECAS’ mission is to empower citizens to exercise their rights and promote open and inclusive decision-making through the provision of high quality advice, research and advocacy, as well as capacity building for civil society organisations. -http://ecas.org/services/your-europe-advice-yea/ +Your Europe Advice ECAS +Your Europe Advice is an EU advice service provided by legal experts from ECAS (European Citizen Action Service) operating under contract with the European Commission. It consists of a team of about 60 lawyers who cover all 24 official EU languages and are familiar both with EU law and national laws in all EU countries. Your Europe Advice replies to questions from citizens or businesses on their personal EU rights. The experts respond to the questions within one week, free of charge and in the language chosen by the user. ECAS mission is to empower citizens to exercise their rights and promote open and inclusive decision-making through the provision of high quality advice, research and advocacy, as well as capacity building for civil society organisations. +http://ecas.org/services/your-europe-advice-yea/ + + -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:view]]> - ABB173 - - - - - - ServiceDeliveryModel - Service Delivery Model - + ServiceDeliveryModel + [ABB15] Service Delivery Model + DESCRIPTION: +The way of delivering to public service consumers, or otherwise interacting with them, for the purpose of supplying specific public services with accessibility value. This involves a number of management practices to ensure that the public services are provided as agreed between the public service provider and the consumer. The service delivery mode should also ensure a constant and stable access to public service in alarm and crisis situations (e.g., COVID 19 pandemic, natural disasters, etc.). Here some examples of service delivery mode: i) Mobile App; ii) Web Portal; iii) Web Services; iv) Contact Center, etc. Based on the definitions in Innovation Policy Platform (World Bank and OECD) https://www.innovationpolicyplatform.org/printpdf/12406 @@ -1332,27 +1039,14 @@ Ecolabel - EU and Member State web sites EU web site: permits to discover the types of products and services that can be awarded with the EU Ecolabel. Furthermore, the site permits to browse through the EU Ecolabel Product Catalogue and Tourist Accommodation Catalogue to find currently awarded products and services. Member State Competent Bodies provide information to businesses and consumers. http://ec.europa.eu/environment/ecolabel/index_en.htm https://www.ecolabel.be/fr -https://www.gov.uk/guidance/apply-for-an-eu-ecolabel - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:view]]> - ABB15 - - - - - - - - - - BusinessCapability - Business Capability - + + + + + BusinessCapability + [ABB12] Business Capability + DESCRIPTION: A particular ability or capacity that an organisation may possess or exchange to achieve a specific purpose or outcome. Defining a business capability involves identifying and describing what needs to be done by the business in support of its overall mission. Business capabilities provide an abstraction of the business reality in a way that helps to simplify conversations between interested stakeholders. @@ -1363,7 +1057,7 @@ Syn. Business Ability INTEROPERABILITY SALIENCY: IoP Dimension: Structural IoP, Behavioral IoP -The Business Capability ABB  is salient for organisational interoperability because it defines the main business reason for exchanging business information with other business capabilities in another organisation or in the same organisation. +The Business Capability ABB is salient for organisational interoperability because it defines the main business reason for exchanging business information with other business capabilities in another organisation or in the same organisation. EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): @@ -1373,29 +1067,14 @@ The reporting and generation of data sets business capability brought by Surveil 1. The BTI usage for the DG TAXUD BTI sector users and for Member State users and 2. Surveillance statistical data -http://ec.europa.eu/taxation_customs/dds2/surv/surv_consultation.jsp?Lang=en - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- dct:description: A short description providing an overview of this building block -- eira:owner: The owner of this business capability -- eira:reusability: Whether or not this building block could be reused as part of another solution -- eira:reuse_status: The type of reuse (if reusable): 'Exposed for reuse as main service' means that the building block is exposed to other solutions for reuse as the current solution's primary service. 'Exposed for reuse as supporting service' means that the building block is exposed to other solutions for reuse but only if the solution is already being reused for it's primary service. 'Reused' means that the building block is actually reused from another solution. -- eira:view]]> - ABB12 - - - - - - - - ExchangeOfBusinessInformation - Exchange of Business Information - + + + + + ExchangeOfBusinessInformation + [ABB170] Exchange of Business Information + DESCRIPTION: Business capability on exchanging data, information, and Knowledge Based on TOGAF definitions. @@ -1415,27 +1094,14 @@ The following implementation is an example on how this specific Architecture Bui Easi-MicPro - Agreement of Code of good conduct Proof of transparency and usage of pan-European reporting standards. -https://webgate.ec.europa.eu/easi-micpro/application#!cogcPublicPage - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- dct:description: A short description providing an overview of this building block -- eira:reusability: Whether or not this building block could be reused as part of another solution -- eira:reuse_status: The type of reuse (if reusable): 'Exposed for reuse as main service' means that the building block is exposed to other solutions for reuse as the current solution's primary service. 'Exposed for reuse as supporting service' means that the building block is exposed to other solutions for reuse but only if the solution is already being reused for it's primary service. 'Reused' means that the building block is actually reused from another solution. -- eira:view]]> - ABB170 - - - - - - - BusinessInformation - Business Information - + + + + + BusinessInformation + [ABB13] Business Information + DESCRIPTION: Organizationally constructed meaning describing business facts, assets, or opinions that are exchanged in the context of a public service to support its delivery. Examples include an invoice, a medical prescription, a driving license. Based on TOGAF guide about business capabilities and TOGAF definition of information. @@ -1446,38 +1112,21 @@ Syn. Business Facts, Business Data, Business Opinions INTEROPERABILITY SALIENCY: IoP Dimension: Behavioral IoP -The Business Information ABB  is salient for organisational interoperability because it represents the entity being exchanged between organisations. Its interoperability needs to be guaranteed by means of organisational and semantic interoperability specifications. +The Business Information ABB is salient for organisational interoperability because it represents the entity being exchanged between organisations. Its interoperability needs to be guaranteed by means of organisational and semantic interoperability specifications. EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Surveillance3 - Surveillance information Published Surveillance information (Business Information) on Europa: Textile category 1 - Cotton yarn, not put up for retail sale [Council Regulation (EEC) No 3030/93] from Belarus in 2015: see URL for details. -http://ec.europa.eu/taxation_customs/dds2/surv/surv_data_list.jsp?Lang=en&survNumber=670010&survType=1&startDate=20150101&originCode=BY - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:view -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:view]]> - ABB13 - - - - - - - - - PublicServiceCatalogue - Public Service Catalogue - + + + + + PublicServiceCatalogue + [ABB124] Public Service Catalogue + DESCRIPTION: A catalogue of public services is a collection of descriptions of active public services that are provided by public administrations at any administrative level (i.e. local, regional, national or pan-European). All public service descriptions published in a catalogue of public services conform to a common data model for representing public services. This ABB is a key interoperability enabler (*) for sharing/PROVISIONING and reusing/CONSUMING of front-office public services. @@ -1497,141 +1146,61 @@ The following implementation is an example on how this specific Architecture Bui FEDICT service catalogue FEDICT, part of the Federal Public Service Policy and Support of Belgium, offers a public service catalogue. Here are a few examples of the offered services: Company data (company information and certificates), Digiflow (access to online certificates), E-mail Relay (relay of e-mail to and from the federal public services and institutions, as a protection to viruses and spam), eBirth (birth online notification and transfer of statistics), eDepot (for notaries), Federal Authentication Service (authentication of individuals for access to online government applications), etc. -http://www.fedict.belgium.be/en/service_catalogue - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:view]]> - ABB124 - - - - - - SharedGovernanceFramework - Shared Governance Framework - + + + + + SharedGovernanceFramework + [ABB358] Shared Governance Framework + DESCRIPTION: +A shared governance framework is formed by [re]usable governance resources, with convergence power, in relation to public policy goals attainment, given by their functioning impact via communication and harmonization, across the levels of a public administration (central, regional, local) towards the achievement of the public policy goals, enabling : i) structural interoperability by organisational resources supporting reusing and/or sharing of digital public services (i.e. public services catalogue enabling provisioning/consuming public services cross public administrations and cross borders); ii) behavioural interoperability by organisational resources supporting exchanging capabilities of data, information or knowledge with internal/external peers (i.e. service delivery model enabling that data/information/knowledge be provisioned/consumed cross public administrations and cross borders); and iii) governance interoperability by governance resources supporting the collaboration with internal/external peers exchanging data, information or knowledge (i.e. Organisational Interoperability Agreements on organisational terms/conditions enabling sharing, reuse and exchange of data/information/knowledge cross public administrations and cross borders). INTEROPERABILITY SALIENCY IoP dimensions: Structural IoP, Behavioral IoP, Governance IoP -This ABB is a key interoperability enabler because it supports to achieve legal interoperability with public policy goals convergence value by all in all enabling i) sharing/provisioning/reusing/consumption of legislation on digital public services, ii) the exchange of data, information, and knowledge between digital public services, and iii) collaboration between digital public services - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- dct:description: A short description providing an overview of this building block -- eira:view]]> - ABB358 - - - - - - - - DigitalBusinessCapability - Digital Business Capability - - ABB370 - - - - - OrganisationalAgreement - Organisational Agreement - - ABB371 - - - - - - - - SemanticView - Semantic View - - - - - - - - - - - - - - - - - - - - - - - - - - - - - DataPolicy - Data Policy - + + + + + SemanticView + Semantic View + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + DataPolicy + [ABB30] Data Policy + DESCRIPTION: A set of broad, high level principles which form the guiding framework in which data management can operate. Source: OECD @@ -1639,7 +1208,7 @@ https://stats.oecd.org/glossary/detail.asp?ID=4454 INTEROPERABILITY SALIENCY: IoP Dimension: Governance IoP -The Data Policy ABB is salient for semantic interoperability because it provides a guiding framework to manage data and information according to interoperability principles as stated in the EIF recommendation n° 30: "Perceive data and information as a public asset that should be appropriately generated, collected, managed, shared, protected and preserved." +The Data Policy ABB is salient for semantic interoperability because it provides a guiding framework to manage data and information according to interoperability principles as stated in the EIF recommendation n 30: "Perceive data and information as a public asset that should be appropriately generated, collected, managed, shared, protected and preserved." EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): @@ -1649,42 +1218,28 @@ The JRC's data policy is driven by transparency with the aim of contributin The objectives for adopting and implementing the JRC data policy include: -• Share and use data on the basis of the JRC Open Data principles: fully, freely, openly and timely; -• To be transparent on the reasons for restricted access to certain data; -• Provide a coordinated approach to the acquisition of data by the JRC; -• Facilitate management, broaden access and use of JRC data; -• Reinforce goals of Horizon 2020; -• Support EU implementation of the G8 Open Data Charter; -• Continuously support evidence-based decision making and research; -• Ensure that JRC data is made available through the EU Open Data Portal. + Share and use data on the basis of the JRC Open Data principles: fully, freely, openly and timely; + To be transparent on the reasons for restricted access to certain data; + Provide a coordinated approach to the acquisition of data by the JRC; + Facilitate management, broaden access and use of JRC data; + Reinforce goals of Horizon 2020; + Support EU implementation of the G8 Open Data Charter; + Continuously support evidence-based decision making and research; + Ensure that JRC data is made available through the EU Open Data Portal. For a successful implementation process, the JRC's data policy lays down implementation principles with respect to responsible entities, overall implementation guidelines, and their individual elements like data management plans, as well as the monitoring of its implementation. https://ec.europa.eu/jrc/en/about/jrc-in-brief/data-policy -http://publications.jrc.ec.europa.eu/repository/bitstream/JRC95307/lb-na-27163-en-n%20.pdf - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- dct:description: A short description providing an overview of this building block -- eira:policy_type: The purpose(s) of this data policy -- eira:view]]> - ABB30 - - - - - - - - - Representation - Representation - + + + + + Representation + [ABB182] Representation + DESCRIPTION: The description of the perceptible configuration of business information or a Legal act. Representations can be classified in various ways; for example, in terms of medium (e.g. electronic or paper documents, audio, etc.) or format (HTML, ASCII, PDF, RTF, etc.). -Source: ArchiMate® v3 +Source: ArchiMate v3 http://pubs.opengroup.org/architecture/archimate3-doc/chap08.html INTEROPERABILITY SALIENCY: @@ -1698,28 +1253,14 @@ The following implementation is an example on how this specific Architecture Bui ESPD data - XML representation European Single Procurement Document (ESPD) is a self-declaration of the businesses' financial status, abilities and suitability for a public procurement procedure. It is available in all EU languages and used as a preliminary evidence of fulfilment of the conditions required in public procurement procedures across the EU. Thanks to the ESPD, the tenderers no longer have to provide full documentary evidence and different forms previously used in the EU procurement, which means a significant simplification of access to cross-border tendering opportunities. [...] The online form can be filled in, printed and then sent to the buyer together with the rest of the bid. -https://ec.europa.eu/tools/espd/filter?lang=en - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:view]]> - ABB182 - - - - - - - - - - - DataSetCatalogue - Data Set Catalogue - + + + + + DataSetCatalogue + [ABB24] Data Set Catalogue + DESCRIPTION: Indexed inventory of data sets with comprehensiveness and trustiness value. This ABB is a key interoperability enabler (*) for sharing/PROVISIONING and reusing/CONSUMING Data. @@ -1739,26 +1280,14 @@ The following implementation is an example on how this specific Architecture Bui Agricultural and Vegetable Catalogue The seed of varieties of agricultural and plant species and varieties of vegetable species that are published in the EU level common catalogue is subject to no marketing restrictions with the Community. Publication in the catalogue must be approved as fulfilling minimum requirements laid down in legislation. Data is published on the contents of the catalogues for agricultural and vegetal species and maintainers with details of the reference list. -https://data.europa.eu/euodp/data/dataset/7A98oEqVa83q6L7tHQ - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:reusability: Whether or not this building block could be reused as part of another solution -- eira:actual_use: Specifies if the solution is currently used, planned to be used or not yet used -- eira:view]]> - ABB24 - - - - - - - DataSet - Data Set - + + + + + DataSet + [ABB23] Data Set + DESCRIPTION: A Data Set is a collection of data, published or curated by a single agent, and available for access or download in one or more formats. It is useful to remember that when a common interconnecting infrastructure for base registries is available, legislation is used to force its use. The use of interconnecting infrastructure prevents the proliferation of pointto-point interconnections. Stakeholders should be involved in developing the @@ -1772,31 +1301,20 @@ https://ec.europa.eu/isa2/sites/isa/files/publications/access-to-base-registries INTEROPERABILITY SALIENCY: IoP Dimension: Structural IoP -The Data Set ABB is salient for semantic interoperability because it provides a collection of data to be shared or exchanged between ICT systmes as stated in the EIF recommendation n° 30: "Perceive data and information as a public asset that should be appropriately generated, collected, managed, shared, protected and preserved." +The Data Set ABB is salient for semantic interoperability because it provides a collection of data to be shared or exchanged between ICT systmes as stated in the EIF recommendation n 30: "Perceive data and information as a public asset that should be appropriately generated, collected, managed, shared, protected and preserved." EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): European Union Data Portal - The European Union Open Data Portal (EU ODP) gives you access to open data published by EU institutions and bodies. All the data you can find via this catalogue are free to use and reuse for commercial or non-commercial purposes. -https://data.europa.eu/euodp/data/dataset - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:reusability: Whether or not this building block could be reused as part of another solution -- eira:actual_use: Specifies if the solution is currently used, planned to be used or not yet used -- eira:view]]> - ABB23 - - - - - - Data - Data - + + + + + Data + [ABB22] Data + DESCRIPTION: Data are symbols obtained through an encoding process of business information or a legal act. Source: ISO-IEC-2382-1 * 1993 * @@ -1808,53 +1326,21 @@ Syn. Information INTEROPERABILITY SALIENCY: IoP Dimension: Structural IoP -The Data ABB is salient for semantic interoperability because it represents the most important mean of interaction between ICT systems of organisations in order to ensure interoperability as stated in the EIF recommendation n° 30: "Perceive data and information as a public asset that should be appropriately generated, collected, managed, shared, protected and preserved." +The Data ABB is salient for semantic interoperability because it represents the most important mean of interaction between ICT systems of organisations in order to ensure interoperability as stated in the EIF recommendation n 30: "Perceive data and information as a public asset that should be appropriately generated, collected, managed, shared, protected and preserved." EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Aggregated data of the Emission Trading System (ETS): EU ETS data is aggregated by country, by main activity type and by year on the verified emissions, allowances and surrendered units of the more than 12 000 stationary installations reporting under the EU emission trading system, as well as 1400 aircraft operators. Aggregated data can be viewed with the EU ETS data viewer, which provides an easy access to emission trading data contained in the European Union Transaction Log (EUTL). -https://www.eea.europa.eu/data-and-maps/dashboards/emissions-trading-viewer-1 - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:reusability: Whether or not this building block could be reused as part of another solution -- eira:actual_use: Specifies if the solution is currently used, planned to be used or not yet used -- eira:data_usage: Type of usage of the data entity [Open Data, Master Data, Reference Data, Descriptive Metadata, Base Registry Data] in the context of the solution -- eira:view]]> - ABB22 - - - - - - - - - - - - - - - - - - - - - - - - - - DescriptiveMetadataPolicy - Descriptive Metadata Policy - + + + + + DescriptiveMetadataPolicy + [ABB352] Descriptive Metadata Policy + DESCRIPTION: A Data Policy aiming at making data discoverable and identifiable. It may mandate elements such as title, abstract, author, and keywords. Source: @@ -1862,7 +1348,7 @@ http://www.niso.org/publications/press/UnderstandingMetadata.pdf INTEROPERABILITY SALIENCY: IoP Dimension: Governance IoP -The Descriptive Metadata Policy ABB is salient for semantic interoperability because metadata facilitates opening and sharing data by providing the appropriate format, description of the content, high level of quality in order to achieve interoperability as stated in the EIF recommendation n° 42: "[..] Ensure that open data is accompanied by high quality, machine-readable metadata in non-proprietary formats, including a description of their content, the way data is collected and its level of quality and the licence terms under which it is made available. The use of common vocabularies for expressing metadata is recommended." +The Descriptive Metadata Policy ABB is salient for semantic interoperability because metadata facilitates opening and sharing data by providing the appropriate format, description of the content, high level of quality in order to achieve interoperability as stated in the EIF recommendation n 42: "[..] Ensure that open data is accompanied by high quality, machine-readable metadata in non-proprietary formats, including a description of their content, the way data is collected and its level of quality and the licence terms under which it is made available. The use of common vocabularies for expressing metadata is recommended." EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): @@ -1870,23 +1356,14 @@ The following implementation is an example on how this specific Architecture Bui Dublin Core Metadata Element Set, Version 1.1: Reference Description The Dublin Core Metadata Element Set is a vocabulary of fifteen properties for use in resource description. The name "Dublin" is due to its origin at a 1995 invitational workshop in Dublin, Ohio; "core" because its elements are broad and generic, usable for describing a wide range of resources. The fifteen element "Dublin Core" described in this standard is part of a larger set of metadata vocabularies and technical specifications maintained by the Dublin Core Metadata Initiative (DCMI). The full set of vocabularies, DCMI Metadata Terms [DCMI-TERMS], also includes sets of resource classes (including the DCMI Type Vocabulary [DCMI-TYPE]), vocabulary encoding schemes, and syntax encoding schemes. The terms in DCMI vocabularies are intended to be used in combination with terms from other, compatible vocabularies in the context of application profiles and on the basis of the DCMI Abstract Model [DCAM]. -http://dublincore.org/documents/dces/ - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- dct:description: A short description providing an overview of this building block -- eira:policy_type: The purpose(s) of this data policy -- eira:view]]> - ABB352 - - - - MasterDataPolicy - Master Data Policy - + + + + + MasterDataPolicy + [ABB353] Master Data Policy + DESCRIPTION: A Data Policy applying to the authoritative, most accurate data that is available about key business entities, used to establish the context for business transactions and transactional data. Source: DAMA DM_BOK @@ -1894,32 +1371,23 @@ http://www.dama.org INTEROPERABILITY SALIENCY: IoP Dimension: Governance IoP -The Master Data Policy ABB is salient for semantic interoperability because Master Data is used to establish the context for business transactions and transactional data by providing accurate data usually stored and available for reuse by other parties. Its management should be prioritised as stated in the EIF recommendation n° 31: "Put in place an information management strategy at the highest possible level to avoid fragmentation and duplication. Management of metadata, master data and reference data should be prioritised." +The Master Data Policy ABB is salient for semantic interoperability because Master Data is used to establish the context for business transactions and transactional data by providing accurate data usually stored and available for reuse by other parties. Its management should be prioritised as stated in the EIF recommendation n 31: "Put in place an information management strategy at the highest possible level to avoid fragmentation and duplication. Management of metadata, master data and reference data should be prioritised." EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): EMVO: EMVS Master Data Guide -The EMVS (European Medicines Verification System) requires that OBP’s (OnBoarding Partners) upload both product master data and product batch/pack data. +The EMVS (European Medicines Verification System) requires that OBPs (OnBoarding Partners) upload both product master data and product batch/pack data. The aim of this guide is to clarify what data is expected to be used for the EMVS master data noting that the long-term goal is to source directly from the IDMP/SPOR system. -https://emvo-medicines.eu/new/wp-content/uploads/EMVO_0122_EMVS-Master-Data-Guide-1.pdf - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- dct:description: A short description providing an overview of this building block -- eira:policy_type: The purpose(s) of this data policy -- eira:view]]> - ABB353 - - - - OpenDataPolicy - Open Data Policy - + + + + + OpenDataPolicy + [ABB354] Open Data Policy + DESCRIPTION: The rules and practice of publishing (raw) data in a way that is accessible, reusable, machine readable and licensed permissively. It can be generated by a wide range of parties, including public authorities, the semi-public sector, businesses and the public. In the case of public authorities, such as European Union organisations, making their data available for public reuse supports economic development, openness and transparency. Source: EU Open Data guide @@ -1927,30 +1395,21 @@ http://bookshop.europa.eu/en/eu-open-data-pbOA0416036/downloads/OA-04-16-036-EN- INTEROPERABILITY SALIENCY: IoP Dimension: Governance IoP -The Open Data Policy ABB is salient for semantic interoperability because Open Data is a part of the basic components of the EIF's conceptual model for integrated public services. Opening of public sector datasets for sharing and reuse is encouraged by the Directive on the reuse of public sector information, which provides a common legal framework for reuse of public sector data as stated in the EIF recommendation n° 2: "Publish the data you own as open data unless certain restrictions apply." +The Open Data Policy ABB is salient for semantic interoperability because Open Data is a part of the basic components of the EIF's conceptual model for integrated public services. Opening of public sector datasets for sharing and reuse is encouraged by the Directive on the reuse of public sector information, which provides a common legal framework for reuse of public sector data as stated in the EIF recommendation n 2: "Publish the data you own as open data unless certain restrictions apply." EXAMPLES: EU implementation of the G8 Open Data Charter -https://ec.europa.eu/digital-single-market/en/news/eu-implementation-g8-open-data-charter - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- dct:description: A short description providing an overview of this building block -- eira:policy_type: The purpose(s) of this data policy -- eira:view]]> - ABB354 - - - - BaseRegistryDataPolicy - Base Registry Data Policy - + + + + + BaseRegistryDataPolicy + [ABB351] Base Registry Data Policy + DESCRIPTION: A Data Policy applying to a trusted authentic source of information under the control of an appointed public administration or organisation appointed by government. -According to the European Interoperability Framework, base registries are: “reliable sources of basic information on items such as persons, companies, vehicles, licenses, buildings, locations and roads” and “are authentic and authoritative and form, separately or in combination, the cornerstone of public services”. +According to the European Interoperability Framework, base registries are: reliable sources of basic information on items such as persons, companies, vehicles, licenses, buildings, locations and roads and are authentic and authoritative and form, separately or in combination, the cornerstone of public services. Source: the New EIF http://eur-lex.europa.eu/resource.html?uri=cellar:2c2f2554-0faf-11e7-8a35-01aa75ed71a1.0017.02/DOC_3&format=PDF @@ -1964,64 +1423,46 @@ The following implementation is an example on how this specific Architecture Bui GOOD PRACTICES ON BUILDING SUCESSFUL INTERCONNECTIONS OF BASE REGISTRIES In order to provide quick and user-friendly public services to citizens and businesses, public administrations are trying to adopt customer-centric approaches and readjust their ways of working. -One way to achieve efficiency and increase user-friendliness is through the ‘once-only principle’. Instead of asking the citizen for information that they have already provided, public administrations will reuse the information they already have. Much of this information is stored in authoritative databases called base registries. As the authentic sources of data for public administrations, base registries are one of the basic building blocks of public services and are the key to making the once-only principle a reality. +One way to achieve efficiency and increase user-friendliness is through the once-only principle. Instead of asking the citizen for information that they have already provided, public administrations will reuse the information they already have. Much of this information is stored in authoritative databases called base registries. As the authentic sources of data for public administrations, base registries are one of the basic building blocks of public services and are the key to making the once-only principle a reality. The document contains some good practices to foster access to the data contained in these base registries. The good practices presented, are grouped according to the layered interoperability model proposed by the European Interoperability Framework (EIF). -https://ec.europa.eu/isa2/sites/isa/files/publications/access-to-base-registries-good-practices-on-building-successful-interconnections-of-base-registries.pdf - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- dct:description: A short description providing an overview of this building block -- eira:policy_type: The purpose(s) of this data policy -- eira:view]]> - ABB351 - - - - DataPortabilityPolicy - Data Portability Policy - + + + + + DataPortabilityPolicy + [ABB362] Data Portability Policy + DESCRIPTION: The data portability policy implements the right to data portability, which is one of eight rights enforced by the EU General Data Protection Regulation (GDPR). It regulates the exchange of data, allowing data subjects to obtain data that a data controller holds on them and to reuse it for their own purposes. -Accourding to GDPR, Individuals are free to either store the data for personal use or to transmit it to another data controller. The data must be received “in a structured, commonly used and machine-readable format”. +Accourding to GDPR, Individuals are free to either store the data for personal use or to transmit it to another data controller. The data must be received in a structured, commonly used and machine-readable format. -According to the Article 29 of the Data Protection Working Party (WP29), an advisory body made up of representatives from each EU member state, this right “support[s] the free flow of personal data in the EU and foster[s] competition between controllers”. +According to the Article 29 of the Data Protection Working Party (WP29), an advisory body made up of representatives from each EU member state, this right support[s] the free flow of personal data in the EU and foster[s] competition between controllers. The right to data portability applies: - To personal data that an individual has given to a data controller; - When the processing is carried out by automated means; and -- Where the processing is based on the individual’s consent or for the performance or a contract. +- Where the processing is based on the individuals consent or for the performance or a contract. INTEROPERABILITY SALIENCY: IoP Dimension: Governance IoP The Data Portability Policy ABB is salient for semantic interoperability because it regulates how data can be exchanged and its reuse. EXAMPLE: -The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- dct:description: A short description providing an overview of this building block -- eira:policy_type: The purpose(s) of this data policy -- eira:view]]> - ABB362 - - - - ReferenceDataPolicy - Reference Data Policy - + + + + + ReferenceDataPolicy + [ABB355] Reference Data Policy + DESCRIPTION: A Data Policy applying to data used to organise or categorise other data, or for relating data to information both within and beyond the boundaries of the enterprise. Usually it mandates the use of codes and descriptions, or definitions. Source: DAMA DM_BOK http://www.dama.org -Reference data consists typically of a small, discrete set of values that are not updated as part of business transactions but are usually used to impose consistent classification. Reference data normally has a low update frequency. Reference data is relevant across more than one business systems belonging to different organisations and sectors +Reference data consists typically of a small, discrete set of values that are not updated as part of business transactions but are usually used to impose consistent classication. Reference data normally has a low update frequency. Reference data is relevant across more than one business systems belonging to different organisations and sectors [Source: J. Jordan & C. Ellen (2009). Business need, data and business intelligence]. INTEROPERABILITY SALIENCY: @@ -2040,24 +1481,15 @@ for the uploading of data to the Financial Instruments Reference Data System. This document aims to specify the exchange of Reference Data Information (RDI) between NCAS, Trading Venues, Systematic Internalisers and the Financial Instruments Reference System. -https://www.esma.europa.eu/sites/default/files/library/esma65-11-1193_firds_reference_data_reporting_instructions_v2.0.pdf - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- dct:description: A short description providing an overview of this building block -- eira:policy_type: The purpose(s) of this data policy -- eira:view]]> - ABB355 - - - - DataEntity - Data Entity - + + + + + DataEntity + [ABB20] Data Entity + DESCRIPTION: +A classification of objects found in the real world described by the Noun part of speech persons, places, things, concepts, and events of interest to the enterprise. Source: DAMA DM_BOK http://www.dama.org @@ -2073,27 +1505,16 @@ The following implementation is an example on how this specific Architecture Bui EURES - Job vacancy Most of the jobs on the EURES Job Mobility Portal come from the job vacancies databases managed by the Public Employment Services of the countries participating in EURES. Using a technology called Web Services, the EURES search engine instantly, in real time, interrogates each national database for jobs. These jobs can be of two types: -“EURES jobs", displayed with a blue flag, which are jobs where an employer has expressed an interest in recruiting from another country, or any other jobs advertised in the national jobs databases. +EURES jobs", displayed with a blue flag, which are jobs where an employer has expressed an interest in recruiting from another country, or any other jobs advertised in the national jobs databases. There is, in addition, a central database where EURES advisers can manually post jobs that will all be flagged as "EURES jobs". This is for the time being the only way for those few countries that are not yet fully connected to Web Services to advertise jobs on the EURES portal. This solution can, however, also be used for other specific purposes, such as when an employer wishes to publish a vacancy in several languages etc., which may not always be possible in a national database. -https://ec.europa.eu/eures/public/en/advertise-a-job?lang=en&app=1.8.1p6-build-0&pageCode=advertise_job - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:url: The URL at which the specification can be referenced online -- eira:identifier: The identifier is unique. It identifies univocally the specification in the Cartography -- eira:body: The body contains statements on one or several Building Blocks. It informs either (i.e. proposed mode) on the proposed specification at the ABB level to achieve interoperability for its SBBs or (i.e. in solution descriptive mode) on a specification to which an SBB is actually compliant to achieve interoperability -- eira:domain: The domain can be either domain-neutral (not related to any public policy domain) or domain-specific to a given set of public policy domains. It informs on the public policy domain of application of the specification -- eira:view]]> - ABB20 - - - - CoreDataModel - Core Data Model - + + + + + CoreDataModel + [ABB194] Core Data Model + DESCRIPTION: A context-neutral data model that captures the fundamental characteristics of an entity or a core set of entities. Based on Core Vocabularies Handbook @@ -2110,11 +1531,11 @@ ISA2 Core Vocabularies Core Vocabularies are simplified, re-usable and extensible data models that capture the fundamental characteristics of an entity in a context-neutral fashion. Public administrations can use and extend the Core Vocabularies in the following contexts: -• Development of new systems: the Core Vocabularies can be used as a default starting point for designing the conceptual and logical data models in newly developed information systems. -• Information exchange between systems: the Core Vocabularies can become the basis of a context-specific data model used to exchange data among existing information systems. -• Data integration: the Core Vocabularies can be used to integrate data that comes from disparate data sources and create a data mash-up. -• Open data publishing: the Core Vocabularies can be used as the foundation of a common export format for data in base registries like cadastres, business registers and service portals. -• ISA² has developed the Core Vocabularies for public administrations in an open process with the active involvement of specific working groups. The Core Vocabularies developed are the following: + Development of new systems: the Core Vocabularies can be used as a default starting point for designing the conceptual and logical data models in newly developed information systems. + Information exchange between systems: the Core Vocabularies can become the basis of a context-specific data model used to exchange data among existing information systems. + Data integration: the Core Vocabularies can be used to integrate data that comes from disparate data sources and create a data mash-up. + Open data publishing: the Core Vocabularies can be used as the foundation of a common export format for data in base registries like cadastres, business registers and service portals. + ISA has developed the Core Vocabularies for public administrations in an open process with the active involvement of specific working groups. The Core Vocabularies developed are the following: - Core Person: captures the fundamental characteristics of a person, e.g. name, gender, date of birth, location. - Registered organisation: captures the fundamental characteristics of a legal entity (e.g. its identifier, activities) which is created through a formal registration process, typically in a national or regional register. - Core Location: captures the fundamental characteristics of a location, represented as an address, a geographic name or geometry. @@ -2122,25 +1543,14 @@ Public administrations can use and extend the Core Vocabularies in the following - Core Criterion and Core Evidence: describe the principles and the means that a private entity must fulfil to become eligible or qualified to perform public services. A Criterion is a rule or a principle that is used to judge, evaluate or test something. An Evidence is a means to prove a Criterion. - Core Public organisation: describes public organisations in the European Union. -https://ec.europa.eu/isa2/solutions/core-vocabularies_en - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:url: The URL at which the specification can be referenced online -- eira:identifier: The identifier is unique. It identifies univocally the specification in the Cartography -- eira:body: The body contains statements on one or several Building Blocks. It informs either (i.e. proposed mode) on the proposed specification at the ABB level to achieve interoperability for its SBBs or (i.e. in solution descriptive mode) on a specification to which an SBB is actually compliant to achieve interoperability -- eira:domain: The domain can be either domain-neutral (not related to any public policy domain) or domain-specific to a given set of public policy domains. It informs on the public policy domain of application of the specification -- eira:view]]> - ABB194 - - - - DataSyntax - Data Syntax - + + + + + DataSyntax + [ABB231] Data Syntax + DESCRIPTION: Data Syntax is a set of rules defining the way in which data is put together with appropriate identifiers, delimiters, separator character(s), and other non-data characters to form messages. Source: reference: https://www.iso.org/obp/ui/#iso:std:iso:14817:-1:ed-1:v1:en:term:4.59 @@ -2154,30 +1564,14 @@ The following implementation is an example on how this specific Architecture Bui XML syntax XML syntax refers to the rules that determine how an XML application can be written. The XML syntax is very straight forward, and this makes XML very easy to learn. Below are the main points to remember when creating XML documents. -https://www.quackit.com/xml/tutorial/xml_syntax.cfm - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:url: The URL at which the specification can be referenced online -- eira:identifier: The identifier is unique. It identifies univocally the specification in the Cartography -- eira:body: The body contains statements on one or several Building Blocks. It informs either (i.e. proposed mode) on the proposed specification at the ABB level to achieve interoperability for its SBBs or (i.e. in solution descriptive mode) on a specification to which an SBB is actually compliant to achieve interoperability -- eira:domain: The domain can be either domain-neutral (not related to any public policy domain) or domain-specific to a given set of public policy domains. It informs on the public policy domain of application of the specification -- eira:view]]> - ABB231 - - - - - - - - - DataModel - Data Model - + + + + + DataModel + [ABB26] Data Model + DESCRIPTION: A collection of entities, their properties and the relationships among them, which aims at formally representing a domain, a concept or a real-world thing. Source: ISA2 - SEMIC Action @@ -2203,25 +1597,14 @@ OASIS UBL-2.1 standard was chosen as the best candidate to base the ESPD-EDM upo i. The European Commission is already using (and recommending) UBL-2.1 for e-Documents.[5] ; ii. Most of the concepts and components necessary for the ESPD documents were already defined by UBL specifically for e-Procurement; (3) Methodology and tools are available for the development of new documents, the extension of the existing UBL libraries, the semantic validation of XML instances, etc. -https://joinup.ec.europa.eu/release/espd-exchange-data-model-v101 - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:url: The URL at which the specification can be referenced online -- eira:identifier: The identifier is unique. It identifies univocally the specification in the Cartography -- eira:body: The body contains statements on one or several Building Blocks. It informs either (i.e. proposed mode) on the proposed specification at the ABB level to achieve interoperability for its SBBs or (i.e. in solution descriptive mode) on a specification to which an SBB is actually compliant to achieve interoperability -- eira:domain: The domain can be either domain-neutral (not related to any public policy domain) or domain-specific to a given set of public policy domains. It informs on the public policy domain of application of the specification -- eira:view]]> - ABB26 - - - - ControlledVocabulary - Controlled Vocabulary - + + + + + ControlledVocabulary + [ABB359] Controlled Vocabulary + DESCRIPTION: A controlled vocabulary is an organized arrangement of words and phrases used to index content and/or to retrieve content through browsing or searching. It typically includes preferred and variant terms and has a defined scope or describes a specific domain. INTEROPERABILITY SALIENCY @@ -2232,22 +1615,15 @@ EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): EuroVoc -EuroVoc is a multilingual, multidisciplinary thesaurus covering the activities of the EU, the European Parliament in particular. It contains terms in 23 EU languages (Bulgarian, Croatian, Czech, Danish, Dutch, English, Estonian, Finnish, French, German, Greek, Hungarian, Italian, Latvian, Lithuanian, Maltese, Polish, Portuguese, Romanian, Slovak, Slovenian, Spanish and Swedish), plus in three languages of countries which are candidates for EU accession: македонски (mk), shqip (sq) and cрпски (sr). -https://op.europa.eu/en/web/eu-vocabularies/th-dataset/-/resource/dataset/eurovoc - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:view]]> - ABB359 - - - - SharedKnowledgeBase - Shared Knowledge Base - + + + + + SharedKnowledgeBase + [ABB366] Shared Knowledge Base + DESCRIPTION: A shared Knowledge Base is formed by usable data, information and knowledge resources, with convergence power, in relation to public policy goals attainment, given by their impact in the enactment of common understanding from the existing organisational information, across the levels of a public administration (central, regional, local) towards the achievement of the public policy goals, enabling : i) structural interoperability by semantic resources supporting reusing and/or sharing of data, information and knowledge (i.e. data set catalogue enabling provisioning/consuming data, information and knowledge cross public administrations and cross borders); ii) behavioural interoperability by semantic resources supporting exchanging capabilities of data, information or knowledge with internal/external peers (i.e. Metadata mappings enabling that data/information/knowledge be provisioned/consumed cross public administrations and cross borders); and @@ -2255,32 +1631,14 @@ iii) governance interoperability by semantic resources supporting the collaborat INTEROPERABILITY SALIENCY: IoP Dimension: Structural IoP, Behavioral IoP, Governance IoP -This ABB is a key interoperability enabler because it supports to achieve semantic interoperability with public policy goals convergence value by all in all enabling i) the provision/consumption of data by public services, ii) the exchange of data, information, and knowledge between digital public services, and iii) collaboration between digital public services - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:reusability: Whether or not this building block could be reused as part of another solution -- eira:actual_use: Specifies if the solution is currently used, planned to be used or not yet used -- eira:view]]> - ABB366 - - - - - - - - - - - - - DataMapping - Data mapping - + + + + + DataMapping + [ABB360] Data mapping + DESCRIPTION: Data mapping is an equivalence relationship between two data items with ontological value. Data mapping is used for a wide variety of tasks, including: - Data mediation between a data source and a destination; - Data transformation @@ -2290,62 +1648,20 @@ Data mapping is an equivalence relationship between two data items with ontologi INTEROPERABILITY SALIENCY IoP Dimension: Behavioral IoP -The Data Mapping ABB is a key interoperability enabler because it supports to achieve legal behavioral interoperability by enabling the exchange of data, information, and knowledge between digital public services. +The Data Mapping ABB is a key interoperability enabler because it supports to achieve legal behavioral interoperability by enabling the exchange of data, information, and knowledge between digital public services. EXAMPLE The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Microsoft Dynamics CRM Mapping Schema: -Microsoft Dynamics CRM contains several data sets which comprise of different objects, such as Leads, Opportunities, and Competitors. Each of these data sets has several fields like Name, Account Owner, City, Country, Job Title, and more. The application has a defined schema along with attributes, enumerations, and mapping rules. Therefore, if a new record is to be added to the schema of a data object, a data map needs to be created from the data source to the Microsoft Dynamics CRM account. - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:reusability: Whether or not this building block could be reused as part of another solution -- eira:actual_use: Specifies if the solution is currently used, planned to be used or not yet used -- eira:view]]> - ABB375 - - - - - - - DataMappingCatalogue - Data Mapping Catalogue - - ABB376 - - - - - - OntologiesCatalogue - Ontologies Catalogue - + + + + + OntologiesCatalogue + [ABB365] Ontologies Catalogue + DESCRIPTION: Indexed inventory of ontologies with comprehensiveness and trustiness value. This ABB is a key interoperability enabler (*) for sharing/PROVISIONING and reusing/CONSUMING Data. @@ -2357,26 +1673,15 @@ EXAMPLE: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): BioPortal BioPortal is a repository of over 300 biomedical ontologies and includes tools for working with these ontologies. Holds most widely used Biomedical ontologies. Allows ontologies to be browsed, searched, and reviewed. Allows uses to create notes on ontologies terms. Allows arbitrary text to be annotated with ontology terms. Also supports search of biomedical resources (e.g. PubMed) for combinations of terms from ontologies. Allows programmatic access to ontologies through a REST interface. -http://bioportal.bioontology.org/ - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:reusability: Whether or not this building block could be reused as part of another solution -- eira:actual_use: Specifies if the solution is currently used, planned to be used or not yet used -- eira:view]]> - ABB365 - - - - - - Ontology - Ontology - + + + + + Ontology + [ABB364] Ontology + DESCRIPTION: +An Ontology is a formal description of knowledge as a set of concepts within a domain and the axioms connecting concepts and allowing for logic inferences. When speaking about an ontology, we do not refer only to the terminology (or T-Box) but also to all the assertions about the concepts and roles (the A-Box), i.e. all the individuals or instances of concepts and roles of the terminology and as important, the rules for logic inference: the semantics part. INTEROPERABILITY SALIENCY: IoP Dimension: Governance IoP @@ -2387,26 +1692,15 @@ The following implementation is an example on how this specific Architecture Bui Medical Dictionary for Regulatory Activities Terminology (MedDRA) The university ontology includes classes, e.g., :Staff, :Students, :Department or :Course. These classes denote natural concepts that are shared or at least understood by users familiar with universities all over the world. Universities ontologies can be view in university portals. -http://bioportal.bioontology.org/ontologies/MEDDRA - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:reusability: Whether or not this building block could be reused as part of another solution -- eira:actual_use: Specifies if the solution is currently used, planned to be used or not yet used -- eira:view]]> - ABB364 - - - - - - DataOwner - Data Owner - + + + + + DataOwner + [ABB361] Data Owner + DESCRIPTION: +Data owners are either individuals or teams who make decisions such as who has the right to access and edit data and how its used. Owners may not work with their data every day, but are responsible for overseeing and protecting a data domain. In the context of the GDPR, data owners are accountable for the quality, integrity, and protection of their data space. INTEROPERABILITY SALIENCY: @@ -2419,27 +1713,14 @@ Slovenian portal eGovernment is the main point for e-services for citizens. Students can buy subsidized tickets electronically on the eGovernment portal "eUprava"). Data Owner - Ministry of Interior The Ministry of Interior is the owner of the personal data from Central Population register. -https://e-uprava.gov.si/podrocja/izobrazevanje-kultura/visoka-in-visja-sola/subvencionirana-vozovnica.html - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:view -- eira:unit_in_DG: The Directorate-General in charge of the solution (EC only)]]> - ABB361 - - - - - - - - - SemanticInteroperabilityAgreement - Semantic Interoperability Agreement - + + + + + SemanticInteroperabilityAgreement + [ABB232] Semantic Interoperability Agreement + DESCRIPTION: A Semantic interoperability agreement is a semantic resource formalizing governance rules enabling collaboration between digital public services with ontological value. Source: @@ -2454,25 +1735,56 @@ The following implementation is an example on how this specific Architecture Bui e-Invoicing Semantic Data Model The semantic data model includes only the essential information elements that an electronic invoice needs to ensure legal (including fiscal) compliance and to enable interoperability for cross-border, cross-sector and for domestic trade. The semantic data model may be used by public and private sector organisations for public procurement invoicing and took into account the physical and financial supply chain perspective, reflecting both private and public sector requirements, with a view to allowing the full straight-through processing of an electronic invoice. -https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/2017/06/28/CEN+Publishes+eInvoicing+Semantic+Data+Model - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:url: The URL at which the specification can be referenced online -- eira:identifier: The identifier is unique. It identifies univocally the specification in the Cartography -- eira:body: The body contains statements on one or several Building Blocks. It informs either (i.e. proposed mode) on the proposed specification at the ABB level to achieve interoperability for its SBBs or (i.e. in solution descriptive mode) on a specification to which an SBB is actually compliant to achieve interoperability -- eira:view]]> - ABB232 - - - - - SemanticAgreement - Semantic Agreement - + + + + + DataMapping + [ABB375] Data mapping + DESCRIPTION: +Data mapping is an equivalence relationship between two data items with ontological value. Data mapping is used for a wide variety of tasks, including: +- Data mediation between a data source and a destination; +- Data transformation +- Identification of data relationships as part of data lineage analysis; +- Discovery of hidden sensitive data such as the last four digits of a social security number hidden in another user id as part of a data masking or de-identification project; +- Consolidation of multiple databases into a single database and identifying redundant columns of data for consolidation or elimination. + +INTEROPERABILITY SALIENCY +IoP Dimension: Behavioral IoP +The Data Mapping ABB is a key interoperability enabler because it supports to achieve legal behavioral interoperability by enabling the exchange of data, information, and knowledge between digital public services. + +EXAMPLE +The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): + +Microsoft Dynamics CRM Mapping Schema: +Microsoft Dynamics CRM contains several data sets which comprise of different objects, such as Leads, Opportunities, and Competitors. Each of these data sets has several fields like Name, Account Owner, City, Country, Job Title, and more. The application has a defined schema along with attributes, enumerations, and mapping rules. Therefore, if a new record is to be added to the schema of a data object, a data map needs to be created from the data source to the Microsoft Dynamics CRM account. + + + + + DataMappingCatalogue + [ABB376] Data Mapping Catalogue + DESCRIPTION: +Indexed inventory of data mappings with comprehensiveness and trustiness value. +This ABB is a key interoperability enabler (*) for sharing/PROVISIONING and reusing/CONSUMING Data. + +INTEROPERABILITY SALIENCY: + + +EXAMPLE: +CEMS Rapid Mapping - JRC +The Joint Research Centre (JRC) is the European Commission's science and knowledge service which employs scientists to carry out research in order to provide independent scientific advice and support to EU policy. +Rapid Mapping is one of the two on-demand mapping services under the Copernicus Emergency Management Service (CEMS). Rapid Mapping delivers geospatial information (in different vector and raster formats) in the midst of or immediately after catastrophic events or humanitarian crises. It is available 24/7/365. Supported disaster types range from natural hazards such as floods, fires, storms, tsunamis, volcanic eruptions, landslides, and earthquakes to industrial accidents and humanitarian crises. + +https://data.jrc.ec.europa.eu/collection/id-0072 + + + + + SemanticAgreement + [ABB374] Semantic Agreement + DESCRIPTION: An agreement from a peer to the common ontology is the result of a matching or mapping process that is used to resolve their semantic discrepancies. The combination matching process consists of linguistic base, internal and external structure comparison. Result of matching combination will be used to develop agreement unit as component of agreement. There are some assumptions for the agreement, such as using same language to representation of schema/ontology, labels represent the meaning of concept, and there is no individual at the common ontology. Source: Work Group Information System @@ -2486,57 +1798,33 @@ The following implementation is an example on how this specific Architecture Bui SEMIC "Supporting alignments and agreements on common definitions and specifications at the semantic layer for the Member States and the EU institutions". -https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/about - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:url: The URL at which the specification can be referenced online -- eira:identifier: The identifier is unique. It identifies univocally the specification in the Cartography -- eira:body: The body contains statements on one or several Building Blocks. It informs either (i.e. proposed mode) on the proposed specification at the ABB level to achieve interoperability for its SBBs or (i.e. in solution descriptive mode) on a specification to which an SBB is actually compliant to achieve interoperability -- eira:view]]> - ABB374 - - - - - - - - SecurityPolicy - Security Policy - + + + + + SecurityPolicy + [ABB372] Security Policy + DESCRIPTION: A privacy or security policy is a statement or a legal document (in privacy law) that discloses some or all of the ways a party gathers, uses, discloses, and manages a customer or client's data. INTEROPERABILITY SALIENCY: IoP Dimension: Governance IoP -The Data Policy ABB is salient for semantic interoperability because it provides a guiding framework to ensure the security of data and information according to interoperability principles as stated in the EIF recommendation n° 46 and 47: "Consider the specific security and privacy requirements and identify measures for the provision of each public service according to risk management plans." +The Data Policy ABB is salient for semantic interoperability because it provides a guiding framework to ensure the security of data and information according to interoperability principles as stated in the EIF recommendation n 46 and 47: "Consider the specific security and privacy requirements and identify measures for the provision of each public service according to risk management plans." EXAMPLE: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Common Foreign and Security Policy (CFSP) The Common Foreign and Security Policy (CFSP) is the organised, agreed foreign policy of the European Union (EU) for mainly security and defence diplomacy and actions. -https://eeas.europa.eu/topics/common-foreign-security-policy-cfsp_en - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- dct:description: A short description providing an overview of this building block -- eira:policy_type: The purpose(s) of this data policy -- eira:view]]> - ABB372 - - - - - PrivacyPolicy - Privacy Policy - + + + + + PrivacyPolicy + [ABB373] Privacy Policy + DESCRIPTION: A privacy policy is a document that explains how an organization handles any customer, client or employee information gathered in its operations. Source: Techtarget @@ -2544,54 +1832,50 @@ https://whatis.techtarget.com/definition/privacy-policy INTEROPERABILITY SALIENCY: IoP Dimension: Governance IoP -The Data Policy ABB is salient for semantic interoperability because it provides a guiding framework to ensure the privacy of data and information according to interoperability principles as stated in the EIF recommendation n° 46 and 47: "Consider the specific security and privacy requirements and identify measures for the provision of each public service according to risk management plans." +The Data Policy ABB is salient for semantic interoperability because it provides a guiding framework to ensure the privacy of data and information according to interoperability principles as stated in the EIF recommendation n 46 and 47: "Consider the specific security and privacy requirements and identify measures for the provision of each public service according to risk management plans." EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Protection of individuals with regard to the processing of personal data -"The policy on protection of individuals with regard to the processing of personal data by the European Union institutions is based on the Regulation (EU) 2018/1725 on the protection of personal data by the EU institutions, bodies, offices and agencies". https://ec.europa.eu/info/privacy-policy_en - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- dct:description: A short description providing an overview of this building block -- eira:policy_type: The purpose(s) of this data policy -- eira:view]]> - ABB373 - - - - TechnicalView-Application - Technical View - Application - - - - - - - - - - - - - - - - - - - - - - - - MachineToMachineInterface - Machine to Machine Interface - + + + + + TechnicalView-Application + Technical View - Application + + + + + + + + + + + + + + + + + + + + + + + + + + + + + MachineToMachineInterface + [ABB38] Machine to Machine Interface + DESCRIPTION: A boundary set of means enabling the exchange of data between a service and other services. This ABB is a key interoperability enabler (*) for assessing compatible interfaces. @@ -2601,7 +1885,7 @@ Source: ISA2 - EIA Action INTEROPERABILITY SALIENCY: IoP Dimension: Behavioral IoP -The Machine to machine interface ABB is a key interoperability enabler because it supports to achieve technical behavioral interoperability by enabling the exchange of data, information, and knowledge between digital public services as stated in the EIF recommendation n°5: ""Ensure internal visibility and provide external interfaces for European public services" and recommendation n°9:"Ensure data portability, namely that data is easily transferable between systems and applications supporting the implementation and evolution of European public services without unjustified restrictions, if legally possible." +The Machine to machine interface ABB is a key interoperability enabler because it supports to achieve technical behavioral interoperability by enabling the exchange of data, information, and knowledge between digital public services as stated in the EIF recommendation n5: ""Ensure internal visibility and provide external interfaces for European public services" and recommendation n9:"Ensure data portability, namely that data is easily transferable between systems and applications supporting the implementation and evolution of European public services without unjustified restrictions, if legally possible." EXAMPLES: @@ -2617,29 +1901,14 @@ Advanced Message Queuing Protocol (AMQP); Application Performance Index (APDEX); HAL-FORMS. -The study lists 80 APIs standards, which can be consulted at the following link: https://ec.europa.eu/knowledge4policy/node/35863_el - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:actual_use: Specifies if the solution is currently used, planned to be used or not yet used -- eira:view]]> - ABB38 - - - - - - - - - - - HumanInterface - Human Interface - + + + + + HumanInterface + [ABB37] Human Interface + DESCRIPTION: A boundary set of means enabling the exchange of data between an individual and a service. This ABB is a key interoperability enabler (*) for assessing compatible interfaces. @@ -2658,32 +1927,17 @@ The following implementation is an example on how this specific Architecture Bui GrapesJS GrapesJS is an open-source, multi-purpose, Web Builder Framework which combines different tools and features with the goal to help you (or users of your application) to build HTML templates without any knowledge of coding. It's a perfect solution to replace the common WYSIWYG editors, which are good for content editing but inappropriate for creating HTML structures. You can see it in action with the official demos, but using its API you're able to build your own editors. -https://grapesjs.com/ - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:actual_use: Specifies if the solution is currently used, planned to be used or not yet used -- eira:view]]> - ABB37 - - - - - - - - - - - InteroperableEuropeanSolutionService - Interoperable European Solution Service - + + + + + InteroperableEuropeanSolutionService + [ABB187] Interoperable European Solution Service + DESCRIPTION: Represents an explicitly defined shared application behavior of an Inteoperable European Solution. -Based on ArchiMate® v3 +Based on ArchiMate v3 http://pubs.opengroup.org/architecture/archimate3-doc/chap09.html INTEROPERABILITY SALIENCY: @@ -2695,34 +1949,17 @@ The following implementation is an example on how this specific Architecture Bui EU Login EU Login is the European Commission's user authentication service. It allows authorised users to access a wide range of Commission web services and websites, using a single email address and password. EU Login implements the single sign-on functionality. -https://webgate.ec.europa.eu/cas/help.html - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:reusability_score -- eira:reusability_level -- eira:actual_reuse: Specifies if the solution is currently being reused -- dct:references: The specific building block type this refers to -- eira:view]]> - ABB187 - - - - - - - - - InteroperableEuropeanSolutionComponent - Interoperable European Solution Component - + + + + + InteroperableEuropeanSolutionComponent + [ABB233] Interoperable European Solution Component + DESCRIPTION: Interoperable European Solution Component represents the encapsulation of a functionality provided by an Interoperable European Solution. -Based on ArchiMate® v3 +Based on ArchiMate v3 http://pubs.opengroup.org/architecture/archimate3-doc/chap09.html INTEROPERABILITY SALIENCY: @@ -2734,38 +1971,14 @@ The following implementation is an example on how this specific Architecture Bui EU Login EU Login is the European Commission's user authentication service. It allows authorised users to access a wide range of Commission web services and websites, using a single email address and password. EU Login implements the single sign-on functionality. -https://webgate.ec.europa.eu/cas/help.html - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- eira:status: The development or realisation status of this building block -- eira:data_quality_level -- eira:data_quality_score: Overall data quality score -- eira:reusability_level -- eira:reusability_score -- eira:iop_level -- eira:iop_score -- eira:actual_use: Specifies if the solution is currently used, planned to be used or not yet used -- dct:references: The specific building block type this refers to -- eira:view]]> - ABB233 - - - - - - - - - - - - - AccessManagementService - Access Management Service - + + + + + AccessManagementService + [ABB57] Access Management Service + DESCRIPTION: Shares the functionality of allowing users to make use of i) IT services, ii) data, and/or iii) other assets. Access management helps to protect the confidentiality, integrity and availability of assets by ensuring that only authorized users are able to access or modify the assets. Based on ITIL v3 @@ -2775,7 +1988,7 @@ Syn. Role Management Service INTEROPERABILITY SALIENCY: IoP Dimension: Behavioral IoP -The Access Management Service ABB  is salient for technical interoperability because it provides the functionality of allowing user to make an authorized and trusted use of IT Services, data and other assets as stated in the EIF: "Public administrations should ensure that a 'data access and authorisation plan’ which determines who has access to what data and under what conditions, to ensure privacy. Unauthorised access and security breaches should be monitored and appropriate actions should be taken to prevent any recurrence of breaches" +The Access Management Service ABB is salient for technical interoperability because it provides the functionality of allowing user to make an authorized and trusted use of IT Services, data and other assets as stated in the EIF: "Public administrations should ensure that a 'data access and authorisation plan which determines who has access to what data and under what conditions, to ensure privacy. Unauthorised access and security breaches should be monitored and appropriate actions should be taken to prevent any recurrence of breaches" EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): @@ -2784,37 +1997,24 @@ Belgian Federal Public Service Policy and Support - Role Management service The Role Management service gives access managers the possibility to manage roles. A role gives access to an online government application. Characteristics: -• A federal access management platform for public e-gov applications -• Three separate contexts: Businesses, Officials and Independent -• Roles that can only be attributed by a specific group of managers for a specific application within one of the three contexts -• Two different security levels of the application depending on the sensitivity of the information: user name, password and token; and electronic identity card with associated PIN code -• Authentication when connecting to an application -• Support with the implementation of the service -• Support while the service is being used + A federal access management platform for public e-gov applications + Three separate contexts: Businesses, Officials and Independent + Roles that can only be attributed by a specific group of managers for a specific application within one of the three contexts + Two different security levels of the application depending on the sensitivity of the information: user name, password and token; and electronic identity card with associated PIN code + Authentication when connecting to an application + Support with the implementation of the service + Support while the service is being used Users: All public services and institutions that want a secure access management for their applications: federal public services and institutions; Communities and Regions; Provinces, municipalities and local public social welfare centres; businesses or persons implementing government contracts. Requirements: application with Fedict Service Desk and signing up to a user agreement. -http://www.fedict.belgium.be/en/identificatie_beveiliging/rollenbeheer - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:reusability_level -- eira:reusability_score -- eira:actual_reuse: Specifies if the solution is currently being reused -- eira:view]]> - ABB57 - - - - - - AccessManagementComponent - Access Management Component - + + + + + AccessManagementComponent + [ABB70] Access Management Component + DESCRIPTION: Implements the functionalities of allowing users to make use of i) IT services, ii) data, and/or iii) other assets. Access management helps to protect the confidentiality, integrity and availability of assets by ensuring that only authorised users are able to access or modify the assets. Based on ITIL v3 @@ -2822,37 +2022,21 @@ https://www.axelos.com/Corporate/media/Files/Glossaries/AXELOS-Common-Glossary.p INTEROPERABILITY SALIENCY: IoP Dimension: Structural IoP -The Access Management Component ABB  is salient for technical interoperability because it provides the implementation the functionality of allowing user to make an authorized and trusted use of IT Services, data and other assets as stated in the EIF: "Public administrations should ensure that a 'data access and authorisation plan’ which determines who has access to what data and under what conditions, to ensure privacy. Unauthorised access and security breaches should be monitored and appropriate actions should be taken to prevent any recurrence of breaches" +The Access Management Component ABB is salient for technical interoperability because it provides the implementation the functionality of allowing user to make an authorized and trusted use of IT Services, data and other assets as stated in the EIF: "Public administrations should ensure that a 'data access and authorisation plan which determines who has access to what data and under what conditions, to ensure privacy. Unauthorised access and security breaches should be monitored and appropriate actions should be taken to prevent any recurrence of breaches" EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): OpenIAM Access Manager OpenIAM Access Management solution is based on a professional open source model. This is a robust, scalable solution built with Service Oriented Architecture. It integrates seamlessly with the OpenIAM Identity Manager product to provide a comprehensive solution that allows to take control of not only who can access the systems, but what they can do once they are in there. Corporate security policy is enforced across multiple points and managed centrally to improve effectiveness and reduce administrative costs. -http://www.openiam.com/products/access-manager/overview/ - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:data_quality_level -- eira:data_quality_score: Overall data quality score -- eira:reusability_level -- eira:reusability_score -- eira:iop_level -- eira:iop_score -- eira:actual_reuse: Specifies if the solution is currently being reused -- eira:view]]> - ABB70 - - - - - AuditService - Audit Service - + + + + + AuditService + [ABB58] Audit Service + DESCRIPTION: Shares the audit functionality of providing support for the principle of accountability, which is holding users of a system accountable for their actions within the system, and detection of policy violations. The audit policy defines the elements of an information system which need to be traced, for example to assure traceability of actions: what, how, when, where and with what. Based on The Open Group @@ -2860,7 +2044,7 @@ http://www.opengroup.org/security/das/xdas_int.htm INTEROPERABILITY SALIENCY: IoP Dimension: Behavioral IoP -The Audit Service ABB  is salient for technical interoperability because it defines the elements of an information system which need to be traced, for example to assure traceability of user actions as stated in the EIF: "Public administrations should ensure that a 'data access and authorisation plan’ which determines who has access to what data and under what conditions, to ensure privacy. Unauthorised access and security breaches should be monitored and appropriate actions should be taken to prevent any recurrence of breaches" +The Audit Service ABB is salient for technical interoperability because it defines the elements of an information system which need to be traced, for example to assure traceability of user actions as stated in the EIF: "Public administrations should ensure that a 'data access and authorisation plan which determines who has access to what data and under what conditions, to ensure privacy. Unauthorised access and security breaches should be monitored and appropriate actions should be taken to prevent any recurrence of breaches" EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): @@ -2868,36 +2052,23 @@ The following implementation is an example on how this specific Architecture Bui OpenIAM audit service OpenIAM Auditing Service ensures that detailed information about events and activities associated with identities or resources are logged into a centralized repository and be tracked. It offers the following features: -• Sign-on, Sign-off -• User: create, update, delete or disable accounts -• Role: create, update, delete or disable accounts -• Resource: create, update, delete or disable accounts -• Password changes, resets, challenge response questions changes -• Synchronization events -• Reconciliation events + Sign-on, Sign-off + User: create, update, delete or disable accounts + Role: create, update, delete or disable accounts + Resource: create, update, delete or disable accounts + Password changes, resets, challenge response questions changes + Synchronization events + Reconciliation events Several reporting templates are provided for a BIRT report writer for use in an Eclipse designer. Organizations can also generate their own reports in BIRT with SQL. -https://www.openiam.com/products/identity-manager/features/audit-compliance/ - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:reusability_level -- eira:reusability_score -- eira:actual_reuse: Specifies if the solution is currently being reused -- eira:view]]> - ABB58 - - - - - - AuditComponent - Audit Component - + + + + + AuditComponent + [ABB71] Audit Component + DESCRIPTION: Implements the functionality of providing support for the principle of accountability, which is holding users of a system accountable for their actions within the system, and detection of policy violations. The audit policy defines the elements of an information system which need to be traced, for example to assure traceability of actions: what, how, when, where and with what. Based on The Open Group @@ -2905,7 +2076,7 @@ http://www.opengroup.org/security/das/xdas_int.htm INTEROPERABILITY SALIENCY: IoP Dimension: Structural IoP -The Audit Component ABB  is salient for technical interoperability because it allows the implementation of audit policies as stated in the EIF: "Public administrations should ensure that a 'data access and authorisation plan’ which determines who has access to what data and under what conditions, to ensure privacy. Unauthorised access and security breaches should be monitored and appropriate actions should be taken to prevent any recurrence of breaches" +The Audit Component ABB is salient for technical interoperability because it allows the implementation of audit policies as stated in the EIF: "Public administrations should ensure that a 'data access and authorisation plan which determines who has access to what data and under what conditions, to ensure privacy. Unauthorised access and security breaches should be monitored and appropriate actions should be taken to prevent any recurrence of breaches" EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): @@ -2913,30 +2084,14 @@ The following implementation is an example on how this specific Architecture Bui Activiti audit feature The audit feature of Activiti archives all process instances, activity instances, keeps variable values continuously in sync and all form properties that are submitted so that all user interaction through forms is traceable and can be audited. Authenticated users who submitted the forms are accessible in the history as well as for start forms and task forms. -https://www.activiti.org/userguide/#historyFormAuditPurposes - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:data_quality_level -- eira:data_quality_score: Overall data quality score -- eira:reusability_level -- eira:reusability_score -- eira:iop_level -- eira:iop_score -- eira:actual_reuse: Specifies if the solution is currently being reused -- eira:view]]> - ABB71 - - - - - InteroperableEuropeanSolution - Interoperable European Solution - + + + + + InteroperableEuropeanSolution + [ABB60] Interoperable European Solution + DESCRIPTION: A solution, developed by Public Administrations that facilitate the delivery of electronic Public Services and cross-border exchange of information between Public Administrations (or Citizens) in support to the implementation and advancement of EU, national or local Public Policies. Based on ISA TES definition @@ -2950,65 +2105,21 @@ The following implementation is an example on how this specific Architecture Bui eDelivery Supporting secure and reliable exchange of data and documents eDelivery is a network of nodes for digital communications. It is based on a distributed model where every participant becomes a node using standard transport protocols and security policies. eDelivery helps public administrations to exchange electronic data and documents with other public administrations, businesses and citizens, in an interoperable, secure, reliable and trusted way. eDelivery is one of the building blocks of the European Commission's Connecting Europe Facility (CEF). These building blocks are reusable specifications, software and services that will form part of a wide variety of IT systems in different policy domains of the EU. The CEF eDelivery building block is based on the AS4 messaging protocol, open and free for all, developed by the OASIS standards development organisation. To ease its adoption in Europe, eDelivery uses the AS4 implementation guidelines defined by the Member States in the e-SENS Large Scale Pilot. Organisations must install an Access Point, or use a Service Provider, to exchange information with the AS4 messaging protocol. -https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:description: A short description providing an overview of this building block -- dct:modified: The date that the information documented for this building block was last modified -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:type: The type of the architecture building block -- eira:actual_policy_coverage: The current policy domain coverage of this solution -- eira:actual_reuse: Specifies if the solution is currently being reused -- eira:confidentiality_level: The confidentiality level of this solution and its processed data -- eira:data_quality_level -- eira:data_quality_score: Overall data quality score -- eira:reusability_level -- eira:reusability_score -- eira:behavioural_iop_level -- eira:structural_iop_level -- eira:governance_iop_level -- eira:behavioural_iop_score -- eira:structural_iop_score -- eira:governance_iop_score -- eira:operational_date: The date this solution entered into operation -- eira:GovIS_ID: The identifier assigned to this solution in GovIS (if applicable) -- eira:IES_category: -- eira:importance_for_the_functioning_of_the_EU: The level of importance of this solution for the functioning of the European Union -- eira:integrity_and_availability_level: The integrity and availability level of this solution -- eira:policy_area_extension: Whether or not this solution is foreseen to be extended to other policy domains -- eira:published_in_catalogue_or_software_forge: Is the solution published in a catalogue and/or made available in a software forge? -- eira:rationalisation_domain: The European Commission rationalisation domain(s) to which the solution belongs to -- eira:scalability: The solution's scalability level -- eira:security_requirements: The level of measures taken by the solution to address security -- eira:state: The development status of this solution -- eira:view]]> - ABB60 - - - - - - - - - - - - - - - - DataTransformationService - Data Transformation Service - + + + + + DataTransformationService + [ABB40] Data Transformation Service + DESCRIPTION: Shares the functionality of conversion of one data representation to another. -Source: ISA2 – EIA Action +Source: ISA2 EIA Action INTEROPERABILITY SALIENCY: IoP Dimension: Behavioral IoP -The Data Transformation Service ABB  is salient for technical interoperability because it provides the functionalities to transform internal data structures to common and agreed interoperable formats as stated in the EIF recommendation n° 41: "Establish procedures and processes to integrate the opening of data in your common business processes, working routines, and in the development of new information systems." +The Data Transformation Service ABB is salient for technical interoperability because it provides the functionalities to transform internal data structures to common and agreed interoperable formats as stated in the EIF recommendation n 41: "Establish procedures and processes to integrate the opening of data in your common business processes, working routines, and in the development of new information systems." EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): @@ -3016,35 +2127,21 @@ The following implementation is an example on how this specific Architecture Bui Eurostat transformation service The transformation service allows datasets to be converted from one file format to another, optionally performing additional tasks, such as mapping and transcoding. The service is operational but is currently only available for internal consumption within Eurostat. However, the source code of both web service and software component is available in the SDMX webspace: -http://ec.europa.eu/eurostat/web/sdmx-infospace/validation-transformation/transformation-services - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:reusability_level -- eira:reusability_score -- eira:actual_reuse: Specifies if the solution is currently being reused -- eira:view]]> - ABB40 - - - - - - - DataTransformationComponent - Data Transformation Component - + + + + + DataTransformationComponent + [ABB61] Data Transformation Component + DESCRIPTION: Implements the functionality of conversion of data from one data representation to another. -Source: ISA2 – EIA Action +Source: ISA2 EIA Action INTEROPERABILITY SALIENCY: IoP Dimension: Structural IoP -The Data Transformation Component ABB  is salient for technical interoperability because it enables the implementation of the functionalities to transform internal data structures to common and agreed interoperable formats as stated in the EIF recommendation n° 41: "Establish procedures and processes to integrate the opening of data in your common business processes, working routines, and in the development of new information systems." +The Data Transformation Component ABB is salient for technical interoperability because it enables the implementation of the functionalities to transform internal data structures to common and agreed interoperable formats as stated in the EIF recommendation n 41: "Establish procedures and processes to integrate the opening of data in your common business processes, working routines, and in the development of new information systems." EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): @@ -3052,30 +2149,14 @@ The following implementation is an example on how this specific Architecture Bui Eurostat SDMX converter Eurostat SDMX converter The SDMX Converter is a tool that converts statistical datasets between different formats. It is a Java application which is actively developed by Eurostat and is published as open source software. -http://ec.europa.eu/eurostat/web/sdmx-infospace/sdmx-it-tools/sdmx-converter - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:data_quality_level -- eira:data_quality_score: Overall data quality score -- eira:reusability_level -- eira:reusability_score -- eira:iop_level -- eira:iop_score -- eira:actual_reuse: Specifies if the solution is currently being reused -- eira:view]]> - ABB61 - - - - - DataValidationService - Data Validation Service - + + + + + DataValidationService + [ABB42] Data Validation Service + DESCRIPTION: Shares the functionality of referring to any activity aimed at verifying that the value of a data item comes from a given set of acceptable values. Data validation may be followed by corrective actions, such as data editing or data imputation. Based on Eurostat Data Validation @@ -3083,7 +2164,7 @@ http://ec.europa.eu/eurostat/data/data-validation INTEROPERABILITY SALIENCY: IoP Dimension: Behavioral IoP -The Data Validation Service ABB  is salient for technical interoperability because it shares the functionality to validate if data received (or to be sent) is compliant with common and agreed interoperable formats as stated in the EIF recommendation n° 41: "Establish procedures and processes to integrate the opening of data in your common business processes, working routines, and in the development of new information systems." +The Data Validation Service ABB is salient for technical interoperability because it shares the functionality to validate if data received (or to be sent) is compliant with common and agreed interoperable formats as stated in the EIF recommendation n 41: "Establish procedures and processes to integrate the opening of data in your common business processes, working routines, and in the development of new information systems." EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): @@ -3091,33 +2172,19 @@ The following implementation is an example on how this specific Architecture Bui Eurostat Struval The Structural Validation service (called STRUVAL) performs structural validation of statistical data files following the SDMX Information Model for a given data flow. It ensures that a data file respects the following key elements: -• SDMX compliance in terms of checks on file format and completeness in terms of mandatory fields; -• SDMX compliance in terms of the structure and coding defined by the Data Structure Definition (DSD); -• The constraints defined for respective data flows. + SDMX compliance in terms of checks on file format and completeness in terms of mandatory fields; + SDMX compliance in terms of the structure and coding defined by the Data Structure Definition (DSD); + The constraints defined for respective data flows. The STRUVAL service returns a response containing a machine-readable message that is processed by the process manager. The invoker of the service receives a validation report, regardless of the result of the process (in case of no failures the reports hold no records). -http://ec.europa.eu/eurostat/web/sdmx-infospace/validation-transformation/structural-validation - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:reusability_level -- eira:reusability_score -- eira:actual_reuse: Specifies if the solution is currently being reused -- eira:view]]> - ABB42 - - - - - - - DataValidationComponent - Data Validation Component - + + + + + DataValidationComponent + [ABB63] Data Validation Component + DESCRIPTION: Implements the functionality of referring to any activity aimed at verifying that the value of a data item comes from a given set of acceptable values. Data validation may be followed by corrective actions, such as data editing or data imputation. In statistics, imputation is the process of replacing missing data with substituted values. Based on Eurostat Data Validation @@ -3125,7 +2192,7 @@ http://ec.europa.eu/eurostat/data/data-validation INTEROPERABILITY SALIENCY: IoP Dimension: Structural IoP -The Data Validation Component ABB  is salient for technical interoperability because it allows the implementation of the functionality to validate if data received (or to be sent) is compliant with common and agreed interoperable formats as stated in the EIF recommendation n° 41: "Establish procedures and processes to integrate the opening of data in your common business processes, working routines, and in the development of new information systems." +The Data Validation Component ABB is salient for technical interoperability because it allows the implementation of the functionality to validate if data received (or to be sent) is compliant with common and agreed interoperable formats as stated in the EIF recommendation n 41: "Establish procedures and processes to integrate the opening of data in your common business processes, working routines, and in the development of new information systems." EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): @@ -3135,35 +2202,19 @@ Express validation rules in a standardized way using annotation-based constraint Application layer agnostic validation: Hibernate Validator allows to express and validate application constraints. The default metadata source are annotations, with the ability to override and extend through the use of XML. It is not tied to a specific application tier or programming model and is available for both server and client application programming. Hibernate Validator presents the following characteristics: -• Extendable: Hibernate Validator offers a configurable bootstrap API as well as a range of built-in constraints. The latter can easily be extended by creating custom constraints. -• Rich metadata API: Hibernate Validator gives access to constraint configuration via a metadata API facilitating, for example, tooling integration. -• Reference implementation: Hibernate Validator 6.x is the reference implementation Bean Validation 2.0. -• Added value: Hibernate Validator offers additional value on top of the features required by Bean Validation. For example, a programmatic constraint configuration API as well as an annotation processor which plugs into the build process and raises compilation errors whenever constraint annotations are incorrectly used. - -http://hibernate.org/validator/ - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:data_quality_level -- eira:data_quality_score: Overall data quality score -- eira:reusability_level -- eira:reusability_score -- eira:iop_level -- eira:iop_score -- eira:actual_reuse: Specifies if the solution is currently being reused -- eira:view]]> - ABB63 - - - - - ServiceDiscoveryService - Service Discovery Service - + + + + + ServiceDiscoveryService + [ABB159] Service Discovery Service + DESCRIPTION: Shares the functionality of locating a machine-processable description of a service-related resource that may have been previously unknown and that meets certain functional criteria. It involves matching a set of functional and other criteria with a set of resource descriptions. The goal is to find an appropriate service-related resource. Based on W3C @@ -3171,7 +2222,7 @@ https://www.w3.org/TR/2004/NOTE-ws-gloss-20040211/ INTEROPERABILITY SALIENCY: IoP Dimension: Behavioral IoP -The Service Discovery Service ABB is salient for technical interoperability because it allows to discover service available for reuses as stated in the EIF recommendation n°36: "Develop a shared infrastructure of reusable services and information sources that can be used by all public administrations." +The Service Discovery Service ABB is salient for technical interoperability because it allows to discover service available for reuses as stated in the EIF recommendation n36: "Develop a shared infrastructure of reusable services and information sources that can be used by all public administrations." EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): @@ -3180,44 +2231,31 @@ jUDDI jUDDI is an open source Java implementation of OASIS the Universal Description, Discovery, and Integration (UDDI) specification for (Web) Services. The jUDDI project includes Scout. Scout is an implementation of the JSR 93 - JavaTM API for XML Registries 1.0 (JAXR). Features: -• Platform Independent -• Use with any relational database that supports ANSI standard SQL (MySQL, Oracle, DB2, Sybase, Derby etc.) -• Deployable on any Java application server that supports the Servlet 2.3 specification -• jUDDI registry supports a clustered deployment configuration. -• Easy integration with existing authentication systems -• Supports InVM embeddable mode + Platform Independent + Use with any relational database that supports ANSI standard SQL (MySQL, Oracle, DB2, Sybase, Derby etc.) + Deployable on any Java application server that supports the Servlet 2.3 specification + jUDDI registry supports a clustered deployment configuration. + Easy integration with existing authentication systems + Supports InVM embeddable mode jUDDIv3 Services: -• UDDI Specification version 3.0.2 compliant -• UDDI Specification version 2.0.4 interoperability services (BETA) -• Built on JAXB and JAX-WS standardized interfaces, tested on Apache CXF -• Built on JPA standardized interfaces, tested with Apache OpenJPA and Hibernate -• Pre-configured bundle deployed to Apache Tomcat -• Full featured user interface (based on Bootstrap) -• User, Administrative and Developer Documentation -• Includes extensive predefined tModels, such as Quality of Service Metrics - -http://juddi.apache.org/ - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:reusability_level -- eira:reusability_score -- eira:actual_reuse: Specifies if the solution is currently being reused -- eira:view]]> - ABB159 - - - - - - ServiceDiscoveryComponent - Service Discovery Component - + + + + + ServiceDiscoveryComponent + [ABB221] Service Discovery Component + DESCRIPTION: Implements the functionality of locating a machine-processable description of a service-related resource that may have been previously unknown and that meets certain functional criteria. It involves matching a set of functional and other criteria with a set of resource descriptions. The goal is to find an appropriate service-related resource. Based on W3C @@ -3225,7 +2263,7 @@ https://www.w3.org/TR/2004/NOTE-ws-gloss-20040211/ INTEROPERABILITY SALIENCY: IoP Dimension: Structural IoP -The Service Discovery Component ABB  is salient for technical interoperability because it allows to implement the funcionality of sharing services available for reuse as stated in the EIF recommendation n°36: "Develop a shared infrastructure of reusable services and information sources that can be used by all public administrations". +The Service Discovery Component ABB is salient for technical interoperability because it allows to implement the funcionality of sharing services available for reuse as stated in the EIF recommendation n36: "Develop a shared infrastructure of reusable services and information sources that can be used by all public administrations". EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): @@ -3233,34 +2271,18 @@ The following implementation is an example on how this specific Architecture Bui Consul Consul has multiple components, but as a whole, it is a tool for discovering and configuring services in an infrastructure. It provides several key features: -• Service Discovery: Clients of Consul can provide a service, such as api or mysql, and other clients can use Consul to discover providers of a given service. Using either DNS or HTTP, applications can easily find the services they depend upon. -• Health Checking: Consul clients can provide any number of health checks, either associated with a given service ("is the webserver returning 200 OK"), or with the local node ("is memory utilization below 90%"). This information can be used by an operator to monitor cluster health, and it is used by the service discovery components to route traffic away from unhealthy hosts. -• KV Store: Applications can make use of Consul's hierarchical key/value store for any number of purposes, including dynamic configuration, feature flagging, coordination, leader election, and more. The simple HTTP API makes it easy to use. -• Multi Datacenter: Consul supports multiple datacenters out of the box. This means users of Consul do not have to worry about building additional layers of abstraction to grow to multiple regions. -https://www.consul.io/ - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:data_quality_level -- eira:data_quality_score: Overall data quality score -- eira:reusability_level -- eira:reusability_score -- eira:iop_level -- eira:iop_score -- eira:actual_reuse: Specifies if the solution is currently being reused -- eira:view]]> - ABB221 - - - - - OrchestrationService - Orchestration Service - + + + + + OrchestrationService + [ABB45] Orchestration Service + DESCRIPTION: Shares the functionality of defining the sequence and conditions in which one service invokes other services in order to realize some useful function. Based on W3C @@ -3268,35 +2290,21 @@ https://www.w3.org/TR/ws-arch/ INTEROPERABILITY SALIENCY: IoP Dimension: Behavioral IoP -The Orchestration Service ABB  is salient for technical interoperability because it provides the functionality of "automated" business processes coordination. The EIF's Conceptual model for integrated EU public services foresees the concept a Coordination for Integrated Service Delivery. The Model comprises an "integrated service delivery" is based on a "coordination function", which is related to SOA principles such as choreography and orchestration, to manage internal business processes in order to remove complexity for the end-user, as stated in the EIF: "The coordination function ensures that needs are identified and appropriate services are invoked and orchestrated to provide a European public service. This function should select the appropriate sources and services and integrate them. Coordination can be automated or manual." +The Orchestration Service ABB is salient for technical interoperability because it provides the functionality of "automated" business processes coordination. The EIF's Conceptual model for integrated EU public services foresees the concept a Coordination for Integrated Service Delivery. The Model comprises an "integrated service delivery" is based on a "coordination function", which is related to SOA principles such as choreography and orchestration, to manage internal business processes in order to remove complexity for the end-user, as stated in the EIF: "The coordination function ensures that needs are identified and appropriate services are invoked and orchestrated to provide a European public service. This function should select the appropriate sources and services and integrate them. Coordination can be automated or manual." EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Apache ODE Apache ODE (Orchestration Director Engine) software executes business processes written following the WS-BPEL standard. It talks to web services, sending and receiving messages, handling data manipulation and error recovery as described by your process definition. It supports both long and short living process executions to orchestrate all the services that are part of your application. -http://ode.apache.org/ - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:reusability_level -- eira:reusability_score -- eira:actual_reuse: Specifies if the solution is currently being reused -- eira:view]]> - ABB45 - - - - - - - OrchestrationComponent - Orchestration Component - + + + + + OrchestrationComponent + [ABB186] Orchestration Component + DESCRIPTION: Implements the functionality of defining the sequence and conditions in which one service invokes other services in order to realize some useful function. Based on W3C @@ -3304,37 +2312,21 @@ https://www.w3.org/TR/ws-arch/ INTEROPERABILITY SALIENCY: IoP Dimension: Structural IoP -The Orchestration Component ABB  is salient for technical interoperability because it provides a set of various methods to manage existing business processes or define and establish new ones. BPM components also execute business process documented through accepted modelling techniques, as recommended by the EIF n.28: "Document your business processes using commonly accepted modelling techniques and agree on how these processes should be aligned to deliver a European public service." +The Orchestration Component ABB is salient for technical interoperability because it provides a set of various methods to manage existing business processes or define and establish new ones. BPM components also execute business process documented through accepted modelling techniques, as recommended by the EIF n.28: "Document your business processes using commonly accepted modelling techniques and agree on how these processes should be aligned to deliver a European public service." EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Activiti Activiti is an open-source workflow engine written in Java that can execute business processes described in BPMN 2.0. Activiti supports open standards such as BPMN and DMN with open REST APIs for demanding human- and system-centric processes. It provides business intelligence and audit logs features for free. And with building the solution on business processes, Activiti help to structure the software, think about user tasks, external systems and timers that need to be managed, think about transaction boundaries of the application. Building that kind of features becomes easier when structuring an application around a business process. Managing wait states, timers and asynchronous continuations becomes easier. A business process can express that structure more compact than working with the fundamental instruments that the Java platform offers like JDBC and JMS. Activiti also makes possible to link in Java or scripting for jobs. -https://www.activiti.org/ - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:data_quality_level -- eira:data_quality_score: Overall data quality score -- eira:reusability_level -- eira:reusability_score -- eira:iop_level -- eira:iop_score -- eira:actual_reuse: Specifies if the solution is currently being reused -- eira:view]]> - ABB186 - - - - - TechnicalSpecification - Technical Specification - + + + + + TechnicalSpecification + [ABB125] Technical Specification + DESCRIPTION: A document that prescribes technical requirements to be fulfilled by a product, process or service. - Note 1 to entry: A technical specification should indicate, whenever appropriate, the procedure(s) by means of which it may be determined whether the requirements given are fulfilled. - Note 2 to entry: A technical specification may be a standard, a part of a standard or independent of a standard. @@ -3352,22 +2344,14 @@ The following implementation is an example on how this specific Architecture Bui AS4 Profile specification The eDelivery AS4 Profile is a modular profile of the ebMS3 and AS4 OASIS specifications. Its core is a mandatory Common Profile that selects, extends and profiles the AS4 ebHandler Conformance Profile and AS4 Additional Features and provides a common Usage Profile. This Common Profile can be implemented using open source or closed source AS4 software implementations. It is aligned with, and corresponds to a subset of, the AS4 profile for TSOs (Transmission System Operators) developed by ENTSOG (the European Network of Transmission System Operators for Gas). In addition to the Common Profile, this specification provides a number of optional Profile Enhancement modules that specify functionality enhancements covering AS4 message exchange in four corner topologies, the use of AS4 in conjunction with the UN/CEFACT Standard Business Document Header (SBDH) specification, and Dynamic Receiver and Dynamic Sender behavior. -https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eDelivery+AS4+-+1.13 - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:domain: The domain can be either domain-neutral (not related to any public policy domain) or domain-specific to a given set of public policy domains. It informs on the public policy domain of application of the specification -- eira:view]]> - ABB125 - - - - TechnicalInteroperabilityAgreement - Technical Interoperability Agreement - + + + + + TechnicalInteroperabilityAgreement + [ABB234] Technical Interoperability Agreement + DESCRIPTION: Technical Interoperability Agreement is the means through which Technical Authorities mandate specific Technical Interoperability Specifications, ensuring organisations (operating under different technical frameworks, policies and strategies) are able to work together. @@ -3383,22 +2367,14 @@ The following implementation is an example on how this specific Architecture Bui ETA The European Technical Assessment (ETA) is an alternative for construction products not covered by a harmonised standard. It is a document providing information on their performance assessment. The procedure is established in the Construction Products Regulation and offers a way for manufacturers to draw up the Declaration of Performance and affix the CE marking. It contributes to the free movement of construction products and the creation of a strong Single Market. -https://ec.europa.eu/growth/sectors/construction/product-regulation/european-assessment_en - -Attributes: -- ID: Internal key used to identify an architecture building block -- eira:view -- dct:type: The type of the architecture building block]]> - ABB234 - - - - - - - SharedPlatform - Shared Platform - + + + + + SharedPlatform + [ABB367] Shared Platform + DESCRIPTION: A shared platform is formed by [re]usable ICT resources (i.e. the platform), with convergence power, in relation to public policy goals attainment, given by the impact of the availability of common problem-solving instruments, across the levels of a public administration (central, regional, local) towards the achievement of the public policy goals, enabling : i) structural interoperability by ICT resources supporting reusing and/or sharing of data, information and knowledge (i.e. service registry service enabling provisioning/consuming [back-office] services cross public administrations and cross borders); ii) behavioural interoperability by ICT resources supporting exchanging capabilities of data, information or knowledge with internal/external peers (i.e. technical interfaces enabling that data/information/knowledge be provisioned/consumed cross public administrations and cross borders); an @@ -3406,107 +2382,14 @@ iii) governance interoperability by ICT resources supporting the collaboration w INTEROPERABILITY SALIENCY: IoP dimensions: Structural IoP Behavioral IoP, Governance IoP -This ABB is a key interoperability enabler because it supports to achieve technical interoperability with public policy goals convergence value by all in all enabling i) the provision/consumption of back-office digital public services, ii) the exchange of data, information, and knowledge between digital public services and individuals , and iii) collaboration between digital public services. - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:view]]> - ABB367 - - - - - - - - - TechnicalAgreement - Technical Agreement - - ABB377 - - - - - TechnicalView-Infrastructure - Technical View - Infrastructure - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ConformanceTestingService - Conformance Testing Service - + + + + + ConformanceTestingService + [ABB128] Conformance Testing Service + DESCRIPTION: Shares the functionality of verifying that several solutions can interoperate at one or more layers of the interoperability stack, while conforming to one or more specifications. This type of testing is executed by operating SUTs (System Under Test) and capturing their exchanges. The logistics of interoperability testing is usually more costly (time, coordination, interoperability), and interoperability testing is no substitute for a conformance test suite. Experience shows that interoperability testing is more successful and less costly when conformance of implementations has been tested first. @@ -3515,7 +2398,7 @@ https://www.cen.eu/work/areas/ict/ebusiness/pages/ws-gitb.aspx INTEROPERABILITY SALIENCY: IoP Dimension: Behavioral IoP -The Conformance Testing Services ABB  is salient for technical interoperability because it enables the validation and verification that several solutions at one or more layers of the interoperability stack and they satisfy certain interoperability requirements. +The Conformance Testing Services ABB is salient for technical interoperability because it enables the validation and verification that several solutions at one or more layers of the interoperability stack and they satisfy certain interoperability requirements. EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): @@ -3524,29 +2407,14 @@ Interoperability Testbed The Test Bed allows users to execute predefined test cases on their systems in order to test the conformance to standards and requirements, simulate a web-service, validate content and test a complete message exchange protocol. The Testbed manages test cases and users, and orchestrates domain-specific components, the domain-specific logic is in separate components that are used via web services. Test results are provided in a standardised, machine-readable format. The Test Bed also offers a test registry and repository (TRR) to store test artefacts (assertions, test cases, validation schemas, etc.) and compile test services (validation services, simulator services, etc.). Please visit the following website for more information: -https://ec.europa.eu/isa2/solutions/interoperability-test-bed_en - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:reusability_level -- eira:reusability_score -- eira:actual_reuse: Specifies if the solution is currently being reused -- eira:view]]> - ABB128 - - - - - - - - ConformanceTestingComponent - Conformance Testing Component - + + + + + ConformanceTestingComponent + [ABB129] Conformance Testing Component + DESCRIPTION: Implements the functionality of allowing a structured and modular approach to implement test automation. Based on ISTQB @@ -3554,7 +2422,7 @@ http://glossary.istqb.org/search/test INTEROPERABILITY SALIENCY: IoP Dimension: Structural IoP -The Conformance Testing Component ABB  is salient for technical interoperability because it enables the validation and verification that several solutions at one or more layers of the interoperability stack and they satisfy certain interoperability requirements. +The Conformance Testing Component ABB is salient for technical interoperability because it enables the validation and verification that several solutions at one or more layers of the interoperability stack and they satisfy certain interoperability requirements. EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): @@ -3563,34 +2431,14 @@ Interoperability Testbed The Test Bed allows users to execute predefined test cases on their systems in order to test the conformance to standards and requirements, simulate a web-service, validate content and test a complete message exchange protocol. The Testbed manages test cases and users, and orchestrates domain-specific components, the domain-specific logic is in separate components that are used via web services. Test results are provided in a standardised, machine-readable format. The Test Bed also offers a test registry and repository (TRR) to store test artefacts (assertions, test cases, validation schemas, etc.) and compile test services (validation services, simulator services, etc.). Please visit the following website for more information: -https://ec.europa.eu/isa2/solutions/interoperability-test-bed_en - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:data_quality_level -- eira:data_quality_score: Overall data quality score -- eira:reusability_level -- eira:reusability_score -- eira:iop_level -- eira:iop_score -- eira:actual_reuse: Specifies if the solution is currently being reused -- eira:view]]> - ABB129 - - - - - - - - - ConformanceTestReport - Conformance Test Report - + + + + + ConformanceTestReport + [ABB131] Conformance Test Report + DESCRIPTION: Data from testing activities and subsequently consolidated in a report to inform stakeholders. Based on ISTQB @@ -3600,7 +2448,7 @@ Syn. Test results INTEROPERABILITY SALIENCY: IoP Dimension: Structural IoP -The Conformance Test Report ABB  is salient for technical interoperability because it provides reports of data testing to inform stakeholders. +The Conformance Test Report ABB is salient for technical interoperability because it provides reports of data testing to inform stakeholders. EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): @@ -3608,23 +2456,14 @@ The following implementation is an example on how this specific Architecture Bui Jenkins jUnit plug-in The JUnit plugin provides a publisher that consumes XML test reports generated during the builds and provides some graphical visualization of the historical test results (see JUnit graph for a sample) as well as a web UI for viewing test reports, tracking failures, and so on. Jenkins understands the JUnit test report XML format (which is also used by TestNG). When this option is configured, Jenkins can provide useful information about test results, such as trends. -https://wiki.jenkins.io/display/JENKINS/JUnit+Plugin - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:view]]> - ABB131 - - - - - - ConformanceTestScenario - Conformance Test Scenario - + + + + + ConformanceTestScenario + [ABB130] Conformance Test Scenario + DESCRIPTION: A document specifying a sequence of actions for the execution of a test. Also known as test script or manual test script. Based on ISTQB @@ -3634,7 +2473,7 @@ Syn. Test procedure INTEROPERABILITY SALIENCY: IoP Dimension: Structural IoP -The Conformance Testing Scenario ABB  is salient for technical interoperability because it provides a document of a list of activities for the execution of interoperability tests. +The Conformance Testing Scenario ABB is salient for technical interoperability because it provides a document of a list of activities for the execution of interoperability tests. EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): @@ -3643,23 +2482,98 @@ SoapUI SoapUI is the world's most widely-used open source API testing tool for SOAP and REST APIs. SoapUI offers SOAP Web Services functional testing, REST API functional testing, WSDL coverage, message assertion testing and test refactoring. Scenario-based tests should be directly tied to user stories, which were probably provided by the product owner or some business stakeholder. Under ideal circumstances, these tests should be the user stories, so that business stakeholders can both easily help the tester develop the test cases and understand the results. https://www.soapui.org/testing-dojo/best-practices/scenario-based-testing.html -https://www.soapui.org/testing-dojo/world-of-api-testing/test-first.html - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:view]]> - ABB130 - - - - - - DigitalServiceInfrastructure - Digital Service Infrastructure - + + + + + TechnicalAgreement + [ABB377] Technical Agreement + DESCRIPTION: +These agreements constitute a framework and a privileged forum to identify common interests, priorities, policy dialogue, and the necessary tools for Strategic & Technological collaboration.. + +Based GMP Quality / Technical Agreements: https://ec.europa.eu/research/iscp/index.cfm?pg=countries + +INTEROPERABILITY SALIENCY: +Not applicable + +EXAMPLES: +The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): + +WTO Data Exchange technical agrement: +The agreement regulates the echange of data between systems and applications +https://olc.worldbank.org/sites/default/files/PMT-4.pdf + + + + + TechnicalView-Infrastructure + Technical View - Infrastructure + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + DigitalServiceInfrastructure + [ABB188] Digital Service Infrastructure + DESCRIPTION: Infrastructure which enable networked services to be delivered electronically, typically over the internet, providing trans-European interoperable services of common interest for citizens, businesses and/or public authorities, and which are composed of core service platforms and generic services Source: Regulation (EU) No 283/2014 @@ -3667,7 +2581,7 @@ http://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=CELEX:32014R0283&from INTEROPERABILITY SALIENCY: IoP Dimension: Structural IoP, Behavioral IoP -The Digital Infrastructure Service ABB  is salient for technical interoperability because it a central element through which interoperability is ensured and by definition, as intended in the EIRA, Digital Service Infrastructure provide trans-European interoperable services. +The Digital Infrastructure Service ABB is salient for technical interoperability because it a central element through which interoperability is ensured and by definition, as intended in the EIRA, Digital Service Infrastructure provide trans-European interoperable services. EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): @@ -3676,40 +2590,14 @@ eHealth refers to tools and services using information and communication technol - Cross-border patient summary service - ePrescriptions and eDispensations In the future, two other services, the European Reference Networks and Interoperable Patient registries might be deployed. -https://webgate.ec.europa.eu/sanco-xmlgate/Login.jsp - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:reusability: Whether or not this building block could be reused as part of another solution -- eira:actual_reuse: Specifies if the solution is currently being reused -- dct:references: The specific building block type this refers to -- eira:view]]> - ABB188 - - - - - - - - - - - - - - - - - - - MetadataManagementService - Metadata Management Service - + + + + + MetadataManagementService + [ABB52] Metadata Management Service + DESCRIPTION: Shares the functionalities for the i) creation, ii) storage, iii) categorisation and iv) retrieval of metadata. Based on DAMA @@ -3717,32 +2605,20 @@ http://www.dama.org/ INTEROPERABILITY SALIENCY: IoP Dimension: Behavioral IoP -The Metadata management Service ABB  is salient for interoperability because it provides and shares the functionalities to manage metadata. EIF recommends to prioritise it: "Put in place an information management strategy at the highest possible level to avoid fragmentation and duplication. Management of metadata, master data and reference data should be prioritised". +The Metadata management Service ABB is salient for interoperability because it provides and shares the functionalities to manage metadata. EIF recommends to prioritise it: "Put in place an information management strategy at the highest possible level to avoid fragmentation and duplication. Management of metadata, master data and reference data should be prioritised". EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Eurostat SDMX repository -The Euro SDMX Registry is Eurostat’s implementation of an SDMX registry to facilitate the exchange of statistical data and metadata by serving as a metadata repository. It stores the SDMX artefacts needed for the parties to access and interpret the content of the exchanged statistical data and metadata sets. -http://ec.europa.eu/eurostat/web/sdmx-infospace/sdmx-it-tools/sdmx-registry - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:reusability_level -- eira:reusability_score -- eira:actual_reuse: Specifies if the solution is currently being reused -- eira:view]]> - ABB52 - - - - - MetadataManagementComponent - Metadata Management Component - + + + + + MetadataManagementComponent + [ABB74] Metadata Management Component + DESCRIPTION: Implements the functionalities for the i) creation, ii) storage, iii) categorisation and iv) retrieval of metadata. Based on DAMA @@ -3750,119 +2626,73 @@ http://www.dama.org/ INTEROPERABILITY SALIENCY: IoP Dimension: Structural IoP -The Metadata management Component ABB  is salient for interoperability because it provides the implementation of the functionalities to manage metadata. EIF recommends to prioritise it: "Put in place an information management strategy at the highest possible level to avoid fragmentation and duplication. Management of metadata, master data and reference data should be prioritised." +The Metadata management Component ABB is salient for interoperability because it provides the implementation of the functionalities to manage metadata. EIF recommends to prioritise it: "Put in place an information management strategy at the highest possible level to avoid fragmentation and duplication. Management of metadata, master data and reference data should be prioritised." EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Eurostat SDMX repository -The Euro SDMX Registry is Eurostat’s implementation of an SDMX registry to facilitate the exchange of statistical data and metadata by serving as a metadata repository. It stores the SDMX artefacts needed for the parties to access and interpret the content of the exchanged statistical data and metadata sets. -http://ec.europa.eu/eurostat/web/sdmx-infospace/sdmx-it-tools/sdmx-registry - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:data_quality_level -- eira:data_quality_score: Overall data quality score -- eira:reusability_level -- eira:reusability_score -- eira:iop_level -- eira:iop_score -- eira:actual_reuse: Specifies if the solution is currently being reused -- eira:view]]> - ABB74 - - - - - - E-archivingService - e-Archiving Service - + + + + + E-archivingService + [ABB156] e-Archiving Service + DESCRIPTION: Shares the functionality of enabling the permanent or long-term storage of selected (by an authority) electronic documents or information for preservation purposes like their enduring research value and memory aid. The EIRA(c) differentiates between document management, record management and e-archiving as follows: - Document management is primarily about day-to-day use of electronic documents (create/update/delete/versioning) within the operational environment; - Record management is primarily about ensuring that information (e.g. in form of an electronic document or database record) is available for business and legal purposes (e.g. to proof and track the handling of contracts). If an electronic document or information is becoming a record (an authority declares it as a record) that electronic document or information needs to be handled by the record management service (based on specific business or legal reasons (e.g. contract negotiation)). -- e-Archiving is primarily about storing records which have been selected (by an authority) for permanent or long-term preservation due to their enduring research value and as a memory aid. An electronic document or information which a) is managed by the document management service or the record management service and b) is no longer needed for business or legal purposes or day-to-day activities, and c) still has value for research purposes or as a memory aid, the electronic document should be managed by the e-archiving service”. +- e-Archiving is primarily about storing records which have been selected (by an authority) for permanent or long-term preservation due to their enduring research value and as a memory aid. An electronic document or information which a) is managed by the document management service or the record management service and b) is no longer needed for business or legal purposes or day-to-day activities, and c) still has value for research purposes or as a memory aid, the electronic document should be managed by the e-archiving service. Source: ISA2 - EIA Action INTEROPERABILITY SALIENCY: IoP Dimension: Behavioral IoP -The e-Archiving Service ABB  is salient for technical interoperability because it provides and shares the functionality for the long-term or permanent preservation of records and information in electronic form in order to ensure their temporal egibility, reliability and integrity as stated in the EIF: "Legislation requires that decisions and data are stored and can be accessed for a specified time. This means that records and information in electronic form held by public administrations for the purpose of documenting procedures and decisions must be preserved and be converted, where necessary, to new media when old media become obsolete. The goal is to ensure that records and other forms of information keep their legibility, reliability and integrity and can be accessed as long as needed subject to security and privacy provisions." +The e-Archiving Service ABB is salient for technical interoperability because it provides and shares the functionality for the long-term or permanent preservation of records and information in electronic form in order to ensure their temporal egibility, reliability and integrity as stated in the EIF: "Legislation requires that decisions and data are stored and can be accessed for a specified time. This means that records and information in electronic form held by public administrations for the purpose of documenting procedures and decisions must be preserved and be converted, where necessary, to new media when old media become obsolete. The goal is to ensure that records and other forms of information keep their legibility, reliability and integrity and can be accessed as long as needed subject to security and privacy provisions." EXAMPLES: +The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): CEF eArchiving eArchiving provides the core specifications, software, training and knowledge to tackle the challenge of short, medium and long-term data management and reuse in a sustainable, authentic, cost-efficient, manageable and interoperable way. -https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eArchiving - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:reusability_level -- eira:reusability_score -- eira:actual_reuse: Specifies if the solution is currently being reused -- eira:view]]> - ABB156 - - - - - - E-archivingComponent - e-Archiving Component - + + + + + E-archivingComponent + [ABB157] e-Archiving Component + DESCRIPTION: Shares the functionality of enabling the permanent or long-term storage of selected (by an authority) electronic documents or information for preservation purposes like their enduring research value and memory aid. -The EIRA© differentiates between document management, record management and e-archiving as follows: -• Document management is primarily about day-to-day use of electronic documents (create/update/delete/versioning) within the operational environment; -• Record management is primarily about ensuring that information (e.g. in form of an electronic document or database record) is available for business and legal purposes (e.g. to proof and track the handling of contracts). If an electronic document or information is becoming a record (an authority declares it as a record) that electronic document or information needs to be handled by the record management service (based on specific business or legal reasons (e.g. contract negotiation)). -• e-Archiving is primarily about storing records which have been selected (by an authority) for permanent or long-term preservation due to their enduring research value and as a memory aid. An electronic document or information which a) is managed by the document management service or the record management service and b) is no longer needed for business or legal purposes or day-to-day activities, and c) still has value for research purposes or as a memory aid, the electronic document should be managed by the e-archiving service”. +The EIRA differentiates between document management, record management and e-archiving as follows: + Document management is primarily about day-to-day use of electronic documents (create/update/delete/versioning) within the operational environment; + Record management is primarily about ensuring that information (e.g. in form of an electronic document or database record) is available for business and legal purposes (e.g. to proof and track the handling of contracts). If an electronic document or information is becoming a record (an authority declares it as a record) that electronic document or information needs to be handled by the record management service (based on specific business or legal reasons (e.g. contract negotiation)). + e-Archiving is primarily about storing records which have been selected (by an authority) for permanent or long-term preservation due to their enduring research value and as a memory aid. An electronic document or information which a) is managed by the document management service or the record management service and b) is no longer needed for business or legal purposes or day-to-day activities, and c) still has value for research purposes or as a memory aid, the electronic document should be managed by the e-archiving service. Source: ISA2 - EIA Action Syn. Preservation Service INTEROPERABILITY SALIENCY: IoP Dimension: Structural IoP -The e-Archiving Component ABB  is salient for technical interoperability because it provides the implementation of the functionalities for the long-term or permanent preservation of records and information in electronic form in order to ensure their temporal egibility, reliability and integrity as stated in the EIF: "Legislation requires that decisions and data are stored and can be accessed for a specified time. This means that records and information in electronic form held by public administrations for the purpose of documenting procedures and decisions must be preserved and be converted, where necessary, to new media when old media become obsolete. The goal is to ensure that records and other forms of information keep their legibility, reliability and integrity and can be accessed as long as needed subject to security and privacy provisions." +The e-Archiving Component ABB is salient for technical interoperability because it provides the implementation of the functionalities for the long-term or permanent preservation of records and information in electronic form in order to ensure their temporal egibility, reliability and integrity as stated in the EIF: "Legislation requires that decisions and data are stored and can be accessed for a specified time. This means that records and information in electronic form held by public administrations for the purpose of documenting procedures and decisions must be preserved and be converted, where necessary, to new media when old media become obsolete. The goal is to ensure that records and other forms of information keep their legibility, reliability and integrity and can be accessed as long as needed subject to security and privacy provisions." EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): CEF eArchiving eArchiving provides the core specifications, software, training and knowledge to tackle the challenge of short, medium and long-term data management and reuse in a sustainable, authentic, cost-efficient, manageable and interoperable way. -https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eArchiving - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:data_quality_level -- eira:data_quality_score: Overall data quality score -- eira:reusability_level -- eira:reusability_score -- eira:iop_level -- eira:iop_score -- eira:actual_reuse: Specifies if the solution is currently being reused -- eira:view]]> - ABB157 - - - - - - FormsManagementService - Forms Management Service - + + + + + FormsManagementService + [ABB49] Forms Management Service + DESCRIPTION: Shares the functionalities of i) dynamic creation, ii) distribution and ii) analysis of forms and online surveys. Source: ISA2 - EIA Action @@ -3871,7 +2701,7 @@ Syn. e-Forms Service INTEROPERABILITY SALIENCY: IoP Dimension: Behavioral IoP -The Forms Management Service ABB  is salient for technical interoperability because it provides and shares the functionalities of dynamic creation, distribution and analysis of forms and online surveys as stated in the EIF: " Catalogues help others to find reusable resources (e.g. services, data, software, data models). Various types of catalogue exist, e.g. directories of services, libraries of software components, open data portals, registries of base registries, metadata catalogues, catalogues of standards, specifications and guidelines. Commonly agreed descriptions of the services, data, registries and interoperable solutions published in catalogues are needed to enable interoperability between catalogues." +The Forms Management Service ABB is salient for technical interoperability because it provides and shares the functionalities of dynamic creation, distribution and analysis of forms and online surveys as stated in the EIF: " Catalogues help others to find reusable resources (e.g. services, data, software, data models). Various types of catalogue exist, e.g. directories of services, libraries of software components, open data portals, registries of base registries, metadata catalogues, catalogues of standards, specifications and guidelines. Commonly agreed descriptions of the services, data, registries and interoperable solutions published in catalogues are needed to enable interoperability between catalogues." EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): @@ -3880,26 +2710,14 @@ EACEA e-Forms Electronic Application Forms - eForms This page contains the resources and information required by applicants who wish to complete and submit an electronic application form (eForm) for a funding opportunity or for an accreditation. The programmes and actions are listed for which electronic application forms are currently available. The Application eForm homepage is where applicants for funding and applicants for accreditation must follow a series of steps in order to create their new application. -https://eacea.ec.europa.eu/about-eacea/electronic-application-forms-eforms_en - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:reusability_level -- eira:reusability_score -- eira:actual_reuse: Specifies if the solution is currently being reused -- eira:view]]> - ABB49 - - - - - FormsManagementComponent - Forms Management Component - + + + + + FormsManagementComponent + [ABB77] Forms Management Component + DESCRIPTION: Implements the functionalities of i) dynamic creation, ii) distribution and ii) analysis of forms and online surveys. Source: ISA2 - EIA Action @@ -3909,7 +2727,7 @@ Syn. e-Forms Component INTEROPERABILITY SALIENCY: IoP Dimension: Structural IoP -The Forms Management Component ABB  is salient for technical interoperability because it provides the implementation of the functionalities of dynamic creation, distribution and analysis of forms and online surveys as stated in the EIF: " Catalogues help others to find reusable resources (e.g. services, data, software, data models). Various types of catalogue exist, e.g. directories of services, libraries of software components, open data portals, registries of base registries, metadata catalogues, catalogues of standards, specifications and guidelines. Commonly agreed descriptions of the services, data, registries and interoperable solutions published in catalogues are needed to enable interoperability between catalogues." +The Forms Management Component ABB is salient for technical interoperability because it provides the implementation of the functionalities of dynamic creation, distribution and analysis of forms and online surveys as stated in the EIF: " Catalogues help others to find reusable resources (e.g. services, data, software, data models). Various types of catalogue exist, e.g. directories of services, libraries of software components, open data portals, registries of base registries, metadata catalogues, catalogues of standards, specifications and guidelines. Commonly agreed descriptions of the services, data, registries and interoperable solutions published in catalogues are needed to enable interoperability between catalogues." EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): @@ -3918,32 +2736,14 @@ Form Tools Form Tools is a forms framework written in PHP and MySQL. You download and install the script on your own website. At its heart, Form Tools is a web form creator, processor, data storage and access script. It was originally designed to work with any existing web form, but has since been expanded to create forms automatically as well. Form Tools is extremely versatile in how it integrates with your forms. You can use the bundled Form Builder module to create the forms automatically on your website (no programming or HTML skills necessary); you can use the PHP API to integrate your own custom form with the script; or you can simply POST your form to Form Tools, and just use it to store the form data. Anything goes! You can read about the different integration methods / form creation methods here. Form Tools works by creating custom database tables to store your unique form data. It provides a range of functionality customized to your data set, such as allowing you to view, update, cross-reference and export your submission data, create subsets of your data for viewing/editing by client accounts, data visualizations, and much more. -https://formtools.org/ - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:data_quality_level -- eira:data_quality_score: Overall data quality score -- eira:reusability_level -- eira:reusability_score -- eira:iop_level -- eira:iop_score -- eira:actual_reuse: Specifies if the solution is currently being reused -- eira:view]]> - ABB77 - - - - - - - DataPublicationService - Data Publication Service - + + + + + DataPublicationService + [ABB215] Data Publication Service + DESCRIPTION: Shares the functionality of making data available for common use. Based on DAMA @@ -3951,7 +2751,7 @@ http://www.dama.org/ INTEROPERABILITY SALIENCY: IoP Dimension: Behavioral IoP -The Data Pubblication Service ABB  is salient for technical interoperability because it provides the functionalities to make public data freely available for use and reuse by others unless restriction aoply as stated in the EIF recommendation n.2: "Publish the data you own as open data unless certain restrictions apply." +The Data Pubblication Service ABB is salient for technical interoperability because it provides the functionalities to make public data freely available for use and reuse by others unless restriction aoply as stated in the EIF recommendation n.2: "Publish the data you own as open data unless certain restrictions apply." EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): @@ -3970,7 +2770,7 @@ https://www.europeandataportal.eu/ Belgian Data Portal The Belgian Data Portal provides data (more than 6500 datasets), tools and resources. -Open Data is a driver for innovation, economic growth, transparency and participation. According to a European study (ref.COM (2011) 882) the cumulative economic benefits arising from the provision of public data would amount to € 40 billion per year in the EU. These data lend themselves to reuse in the context of new products and services and can improve the efficiency of public authorities. Making public sector data accessible makes it possible to involve citizens more in political and social life and to make an active contribution to policy areas such as the environment, mobility, the economy, and so on. +Open Data is a driver for innovation, economic growth, transparency and participation. According to a European study (ref.COM (2011) 882) the cumulative economic benefits arising from the provision of public data would amount to 40 billion per year in the EU. These data lend themselves to reuse in the context of new products and services and can improve the efficiency of public authorities. Making public sector data accessible makes it possible to involve citizens more in political and social life and to make an active contribution to policy areas such as the environment, mobility, the economy, and so on. The 2014-2018 Belgian government agreement states that the government will focus on opening public sector data (Open Data policy). Open public data is now the rule. Public services make available to citizens, researchers, companies and public authorities the reuse of data already available to them in the framework of their missions. It is more specifically data that: - Public services have collected as part of their data collection missions; @@ -3978,27 +2778,14 @@ It is more specifically data that: - Are published in a format that is easy to reuse automatically ("machine readable "); - Can be reused for commercial and non-commercial purposes. It is not only a matter of making public service data available, but also of building a community environment around these data. Companies can reuse some data and enrich it with their own information to market new products and services. Citizens benefit from more transparent public authorities and public services can help improve the quality of existing public data and services. -http://data.gov.be/en - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:reusability_level -- eira:reusability_score -- eira:actual_reuse: Specifies if the solution is currently being reused -- eira:view]]> - ABB215 - - - - - - DataPublicationComponent - Data Publication Component - + + + + + DataPublicationComponent + [ABB209] Data Publication Component + DESCRIPTION: Implements the functionality of making data available for common use. Based on DAMA @@ -4006,14 +2793,14 @@ http://www.dama.org/ INTEROPERABILITY SALIENCY: IoP Dimension: Structural IoP -The Data Pubblication Component ABB  is salient for technical interoperability because it provides the implementation of the functionalities to make public data freely available for use and reuse by others unless restriction aoply as stated in the EIF recommendation n.2: "Publish the data you own as open data unless certain restrictions apply." +The Data Pubblication Component ABB is salient for technical interoperability because it provides the implementation of the functionalities to make public data freely available for use and reuse by others unless restriction aoply as stated in the EIF recommendation n.2: "Publish the data you own as open data unless certain restrictions apply." EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): CKAN CKAN is a data management system that makes data accessible by providing tools to streamline publishing, sharing, finding and using data. This is a tool for making open data websites. It helps you manage and publish collections of data. It is used by national and local governments, research institutions, and other organizations who collect a lot of data. -Once your data is published, users can use its faceted search features to browse and find the data they need, and preview it using maps, graphs and tables – whether they are developers, journalists, researchers, NGOs, citizens, or even your own staff. +Once your data is published, users can use its faceted search features to browse and find the data they need, and preview it using maps, graphs and tables whether they are developers, journalists, researchers, NGOs, citizens, or even your own staff. CKAN is open source and free software, with an active community of contributors who develop and maintain its core technology. CKAN is modified and extended by an even larger community of developers who contribute to a growing library of CKAN extensions. https://ckan.org/ @@ -4029,102 +2816,58 @@ A dataset comprises data and metadata. Policies can be set on communities or col - Storage Datasets undergo curation based on a workflow defined by the community that will publish the data. Workflows may be customized by each community to capture their specific metadata and to reflect the community's review process. After the dataset is published, it is discoverable using a faceted search that allows the researcher to progressively filter results and rapidly focus in on the data of interest. The data may then be transferred to a Globus endpoint where the investigator can inspect and further process the data. Data publication is a premium feature available with a Globus Subscription -https://www.globus.org/data-publication - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:data_quality_level -- eira:data_quality_score: Overall data quality score -- eira:reusability_level -- eira:reusability_score -- eira:iop_level -- eira:iop_score -- eira:actual_reuse: Specifies if the solution is currently being reused -- eira:view]]> - ABB209 - - - - - - PrivacyService - Privacy Service - + + + + + PrivacyService + [ABB235] Privacy Service + DESCRIPTION: Privacy Service shares the functionalities of storing, securing, anonymising, pseudonymising, rectifying and erasing personal data. INTEROPERABILITY SALIENCY: IoP Dimension: Behavioral IoP -The Privacy Service ABB  is salient for interoperability because "security and privacy are primary concerns in the provision of public services" (EIF) and, as stated in EIF Recommendation 15: "Define a common security and privacy framework and establish processes for public services to ensure secure and trustworthy data exchange between public administrations and in interactions with citizens and businesses." +The Privacy Service ABB is salient for interoperability because "security and privacy are primary concerns in the provision of public services" (EIF) and, as stated in EIF Recommendation 15: "Define a common security and privacy framework and establish processes for public services to ensure secure and trustworthy data exchange between public administrations and in interactions with citizens and businesses." EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): SOLVIT Solvit is a mailbox service for the access, rectification or deletion of personal data. -http://ec.europa.eu/solvit/privacy-statement/#maincontentSec8 - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:reusability_level -- eira:reusability_score -- eira:actual_reuse: Specifies if the solution is currently being reused]]> - ABB235 - - - - - PrivacyComponent - Privacy Component - + + + + + PrivacyComponent + [ABB236] Privacy Component + DESCRIPTION: Privacy Component implements the functionalities of storing, securing, anonymising, pseudonymising, rectifying and erasing personal data. INTEROPERABILITY SALIENCY: IoP Dimension: Structural IoP -The Privacy Service ABB  is salient for interoperability because "security and privacy are primary concerns in the provision of public services" (EIF) and, as stated in EIF Recommendation 15: "Define a common security and privacy framework and establish processes for public services to ensure secure and trustworthy data exchange between public administrations and in interactions with citizens and businesses." +The Privacy Service ABB is salient for interoperability because "security and privacy are primary concerns in the provision of public services" (EIF) and, as stated in EIF Recommendation 15: "Define a common security and privacy framework and establish processes for public services to ensure secure and trustworthy data exchange between public administrations and in interactions with citizens and businesses." EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): SOLVIT Solvit is a mailbox service for the access, rectification or deletion of personal data. -http://ec.europa.eu/solvit/privacy-statement/#maincontentSec8 - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:data_quality_level -- eira:data_quality_score: Overall data quality score -- eira:reusability_level -- eira:reusability_score -- eira:iop_level -- eira:iop_score -- eira:actual_reuse: Specifies if the solution is currently being reused]]> - ABB236 - - - - - - ConfigurationAndSolutionCartographyService - Configuration and Solution Cartography Service - + + + + + ConfigurationAndSolutionCartographyService + [ABB210] Configuration and Solution Cartography Service + DESCRIPTION: Shares the functionality of documenting the configuration and architecture of solutions. Source: ISA2 - EIA Action INTEROPERABILITY SALIENCY: -The Configuration and Solution of Cartography Service ABB  is salient for technical interoperability because it can be used to document the interoperabilty features of a solution or a set of solution/services. +The Configuration and Solution of Cartography Service ABB is salient for technical interoperability because it can be used to document the interoperabilty features of a solution or a set of solution/services. EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): @@ -4132,30 +2875,20 @@ The following implementation is an example on how this specific Architecture Bui Essential The EA Essential tool provides with a semantically-rich meta-model. This means accurate modelling which allows for sophisticated reporting. Essential can be configured to import data from a wide range of sources such as CMDBs, Business Process Modelling tools, PMO tools, etc. The Essential Import Utility REST API allows to schedule automated imports from external data sources to keep the repository accurate and current. Complex queries can be built on the repository using the query wizard in Essential Open Source. In addition to traditional the Enterprise Architecture assets, Essential also manages information about the entire organization including resources, skills, contracts, risk, security and more. -https://www.enterprise-architecture.org/features.php - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:reusability: Whether or not this building block could be reused as part of another solution -- eira:reuse_status: The type of reuse (if reusable): 'Exposed for reuse as main service' means that the building block is exposed to other solutions for reuse as the current solution's primary service. 'Exposed for reuse as supporting service' means that the building block is exposed to other solutions for reuse but only if the solution is already being reused for it's primary service. 'Reused' means that the building block is actually reused from another solution. -- eira:ABB_Status: Status of the building block (completed | obsolete | underDevelopment | withdrawn)]]> - ABB210 - - - - ConfigurationAndSolutionCartographyServiceComponent - Configuration and Solution Cartography Service Component - + + + + + ConfigurationAndSolutionCartographyServiceComponent + [ABB213] Configuration and Solution Cartography Service Component + DESCRIPTION: Implements the functionality of documenting the configuration and architecture of solutions. Source: ISA2 - EIA Action INTEROPERABILITY SALIENCY: -The Configuration and Solution of Cartography Component ABB  is salient for technical interoperability because it provides the implementation of the functionalities which can be exploited to document the interoperabilty features of a solution or a set of solution/services. +The Configuration and Solution of Cartography Component ABB is salient for technical interoperability because it provides the implementation of the functionalities which can be exploited to document the interoperabilty features of a solution or a set of solution/services. EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): @@ -4163,21 +2896,14 @@ The following implementation is an example on how this specific Architecture Bui Essential The EA Essential tool provides with a semantically-rich meta-model. This means accurate modelling which allows for sophisticated reporting. Essential can be configured to import data from a wide range of sources such as CMDBs, Business Process Modelling tools, PMO tools, etc. The Essential Import Utility REST API allows to schedule automated imports from external data sources to keep the repository accurate and current. Complex queries can be built on the repository using the query wizard in Essential Open Source. In addition to traditional the Enterprise Architecture assets, Essential also manages information about the entire organization including resources, skills, contracts, risk, security and more. -https://www.enterprise-architecture.org/features.php - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:ABB_Status: Status of the building block (completed | obsolete | underDevelopment | withdrawn)]]> - ABB213 - - - - E-paymentService - e-Payment Service - + + + + + E-paymentService + [ABB48] e-Payment Service + DESCRIPTION: Shares the functionality of executing payment transactions where the consent of the payer to execute a payment transaction is given by means of any telecommunication, digital or IT device. Source: Directive 2007/64/EC @@ -4185,7 +2911,7 @@ http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=CELEX:32007L0064:EN:NOT INTEROPERABILITY SALIENCY: IoP Dimension: Behavioral IoP -The e-Payment Service ABB is salient for technical interoperability because it enables the possibility of executing payment transactions by any means of telecommunication, digital or IT device as stated in the EIF: "Public administrations need to exploit services delivered outside their organisational boundaries by third parties, such as payment services provided by financial institutions or connectivity services provided by telecommunications providers." +The e-Payment Service ABBis salient for technical interoperability because it enables the possibility of executing payment transactions by any means of telecommunication, digital or IT device as stated in the EIF: "Public administrations need to exploit services delivered outside their organisational boundaries by third parties, such as payment services provided by financial institutions or connectivity services provided by telecommunications providers." EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): @@ -4201,26 +2927,14 @@ https://ec.europa.eu/info/business-economy-euro/banking-and-finance/consumer-fin UniPay Payment Gateway The open source payment transactions processing platform UniPay Payment Gateway is a robust, flexible and scalable payment gateway software. The platform has a powerful, processor-agnostic payment gateway at its foundation, which supplies numerous direct-to-processor backend integrations and includes a powerful routing engine configurable through web service calls. With unified API as your entry point (for both credit card transactions and ACH - Automated Clearing House), you gain access to numerous banks and credit card payment processors across the globe. -http://opensourcepaymentgateway.com/ - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:reusability_level -- eira:reusability_score -- eira:actual_reuse: Specifies if the solution is currently being reused -- eira:view]]> - ABB48 - - - - - E-paymentComponent - e-Payment Component - + + + + + E-paymentComponent + [ABB68] e-Payment Component + DESCRIPTION: Implements the functionality of executing payment transactions where the consent of the payer to execute a payment transaction is given by means of any telecommunication, digital or IT device. Source: Directive 2007/64/EC @@ -4229,7 +2943,7 @@ http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=CELEX:32007L0064:EN:NOT INTEROPERABILITY SALIENCY: IoP Dimension: Structural IoP -The e-Payment Component ABB  is salient for technical interoperability because it provides the implementation of functionalities of executing payment transactions. +The e-Payment Component ABB is salient for technical interoperability because it provides the implementation of functionalities of executing payment transactions. EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): @@ -4242,31 +2956,14 @@ OpenACH is several things: - An easy to use ACH payment gateway, using REST and JSON to put payments on the ACH network - A BYOB (Bring Your Own Bank) ACH processing platform - A third-party ACH originator, processing your payments on your behalf -https://openach.com/ - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:data_quality_level -- eira:data_quality_score: Overall data quality score -- eira:reusability_level -- eira:reusability_score -- eira:iop_level -- eira:iop_score -- eira:actual_reuse: Specifies if the solution is currently being reused -- eira:view]]> - ABB68 - - - - - - ServiceRegistrationService - Service Registration Service - + + + + + ServiceRegistrationService + [ABB189] Service Registration Service + DESCRIPTION: Shares the functionality of registering the system service within a catalogue to be discovered by other services. Source ISA2 - EIA Action @@ -4285,27 +2982,14 @@ Apache ZooKeeper is an effort to develop and maintain an open-source server whic ZooKeeper is a centralized service for maintaining configuration information, naming, providing distributed synchronization, and providing group services. All of these kinds of services are used in some form or another by distributed applications. Each time they are implemented there is a lot of work that goes into fixing the bugs and race conditions that are inevitable. Because of the difficulty of implementing these kinds of services, applications initially usually skimp on them, which make them brittle in the presence of change and difficult to manage. Even when done correctly, different implementations of these services lead to management complexity when the applications are deployed. ZooKeeper aims at distilling the essence of these different services into a very simple interface to a centralized coordination service. The service itself is distributed and highly reliable. Consensus, group management, and presence protocols will be implemented by the service so that the applications do not need to implement them on their own. Application specific uses of these will consist of a mixture of specific components of Zoo Keeper and application specific conventions. ZooKeeper Recipes shows how this simple service can be used to build much more powerful abstractions. Apache have Java and C interfaces to Zoo Keeper for the applications themselves. A variety of client bindings is available for a number of languages including Python, Ruby and Go. -https://cwiki.apache.org/confluence/display/ZOOKEEPER/Index - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:reusability_level -- eira:reusability_score -- eira:actual_reuse: Specifies if the solution is currently being reused -- eira:view]]> - ABB189 - - - - - - ServiceRegistryComponent - Service Registry Component - + + + + + ServiceRegistryComponent + [ABB133] Service Registry Component + DESCRIPTION: Implements the functionality of registering the system service within a catalogue to be discovered by other services. This ABB is a key interoperability enabler (*) for sharing/PROVISIONING and reusing/CONSUMING back-office services. @@ -4318,39 +3002,21 @@ Syn. Service Catalogue Component INTEROPERABILITY SALIENCY: IoP Dimension: Structural IoP -The Service Registration Component ABB  is a key interoperability enabler because it supports to achieve technical interoperability by provisioning and consuming back-office services as stated in the EIF recommendation n°44: "Put in place catalogues of public services, public data, and interoperability solutions and use common models for describing them." +The Service Registration Component ABB is a key interoperability enabler because it supports to achieve technical interoperability by provisioning and consuming back-office services as stated in the EIF recommendation n44: "Put in place catalogues of public services, public data, and interoperability solutions and use common models for describing them." EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): jUDDI jUDDI is an open source Java implementation of OASIS Universal Description, Discovery, and Integration (UDDI) specification for (Web) Services. -https://juddi.apache.org/ - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:data_quality_level -- eira:data_quality_score: Overall data quality score -- eira:reusability_level -- eira:reusability_score -- eira:iop_level -- eira:iop_score -- eira:actual_reuse: Specifies if the solution is currently being reused -- eira:view]]> - ABB133 - - - - - - - MachineTranslationService - Machine Translation Service - + + + + + MachineTranslationService + [ABB41] Machine Translation Service + DESCRIPTION: Shares the functionality of serving any current or future Digital Service Infrastructure (DSI) requiring cross-lingual functionality. The main functionality is automated translation of text, metadata and concept classes or nomenclatures. Based on CEF Automated Translation @@ -4358,32 +3024,21 @@ https://ec.europa.eu/digital-single-market/en/news/tools-and-resources-cef-autom INTEROPERABILITY SALIENCY: IoP Dimension: Behavioral IoP -The Machine Translation Service ABB  is salient for technical interoperability because it enables cross-lingual functionality by providing automated translation of text, metadata and concept classes or nomenclatures as stated in the EIF recommendation n°16: "Use information systems and technical architectures that cater for multilingualism when establishing a European public service. Decide on the level of multilingualism support based on the needs of the expected users." +The Machine Translation Service ABB is salient for technical interoperability because it enables cross-lingual functionality by providing automated translation of text, metadata and concept classes or nomenclatures as stated in the EIF recommendation n16: "Use information systems and technical architectures that cater for multilingualism when establishing a European public service. Decide on the level of multilingualism support based on the needs of the expected users." EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): CEF Digital - eTranslation building block eTranslation is a Connecting Europe Facility (CEF) building block provided by the European Commission (EC). eTranslation provides an online machine translation service. -https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eTranslation " - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:reusability_level -- eira:reusability_score -- eira:actual_reuse: Specifies if the solution is currently being reused]]> - ABB41 - - - - - MachineTranslationComponent - Machine Translation Component - + + + + + MachineTranslationComponent + [ABB62] Machine Translation Component + DESCRIPTION: Implements the functionality of serving any current or future Digital Service Infrastructure (DSI) requiring cross-lingual functionality. The main functionality is automated translation of text, metadata and concept classes or nomenclatures. Based on CEF Automated Translation @@ -4392,46 +3047,30 @@ https://ec.europa.eu/digital-single-market/en/news/tools-and-resources-cef-autom INTEROPERABILITY SALIENCY: IoP Dimension: Structural IoP -The Machine Translation Component ABB  is salient for technical interoperability because it provides the implementation of functionalities for cross-lingual functionality by providing automated translation of text, metadata and concept classes or nomenclatures as stated in the EIF recommendation n°16: "Use information systems and technical architectures that cater for multilingualism when establishing a European public service. Decide on the level of multilingualism support based on the needs of the expected users." +The Machine Translation Component ABB is salient for technical interoperability because it provides the implementation of functionalities for cross-lingual functionality by providing automated translation of text, metadata and concept classes or nomenclatures as stated in the EIF recommendation n16: "Use information systems and technical architectures that cater for multilingualism when establishing a European public service. Decide on the level of multilingualism support based on the needs of the expected users." EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): "CEF Digital - eTranslation building block eTranslation is a Connecting Europe Facility (CEF) building block provided by the European Commission (EC). eTranslation provides a web-user interface for direct use by individuals (human-to-machine). -https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eTranslation " - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:data_quality_level -- eira:data_quality_score: Overall data quality score -- eira:reusability_level -- eira:reusability_score -- eira:iop_level -- eira:iop_score -- eira:actual_reuse: Specifies if the solution is currently being reused]]> - ABB62 - - - - - - E-signatureCreationService - e-Signature Creation Service - + + + + + E-signatureCreationService + [ABB55] e-Signature Creation Service + DESCRIPTION: Shares the functionality of signing data in electronic form by a natural person. -An ‘electronic signature’ means data in electronic form which is attached to or logically associated with other data in electronic form and which is used by the signatory to sign. +An electronic signature means data in electronic form which is attached to or logically associated with other data in electronic form and which is used by the signatory to sign. Based on eIDAS - 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. http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv%3AOJ.L_.2014.257.01.0073.01.ENG INTEROPERABILITY SALIENCY: IoP Dimension: Behavioral IoP -The e-Signature Creation Service ABB  is salient for technical interoperability because it provides +The e-Signature Creation Service ABB is salient for technical interoperability because it provides the functionalities required for e-signature creation service. EXAMPLES: @@ -4441,46 +3080,34 @@ CEF eSignature DSS DSS (Digital Signature Services) is an open-source software library for electronic signature creation and validation. DSS supports the creation and verification of interoperable and secure electronic signatures in line with European legislation. In particular, DSS aims to follow the eIDAS Regulation and related standards closely. DSS can be re-used in an IT solution for electronic signatures to ensure that signatures are created and verified in line with European legislation and standards. DSS allows re-use in a variety of different ways: in an applet, in a stand-alone application or in a server application. DSS can also be used as a reference implementation for IT solutions which do not directly re-use it. CEF eSignature's DSS open-source library delivers the following benefits to its users: -• Open-source software under LGPL 2.1, a non-viral open source license; -• Interoperability of the e-signatures; -• Supports both e-signatures and e-seals; -• Validation of countersignatures and multiple signatures; -• Alignment with the eIDAS Regulation and related standards; -• Supports EU standards on: + Open-source software under LGPL 2.1, a non-viral open source license; + Interoperability of the e-signatures; + Supports both e-signatures and e-seals; + Validation of countersignatures and multiple signatures; + Alignment with the eIDAS Regulation and related standards; + Supports EU standards on: o Signature formats and packaging methods; o Signature validation procedures; -• Validation relying on Member States' trusted lists: + Validation relying on Member States' trusted lists: o Status of trust service providers/trust service, compensation of information, path validation. -https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eSignature - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:reusability_level -- eira:reusability_score -- eira:actual_reuse: Specifies if the solution is currently being reused -- eira:view]]> - ABB55 - - - - - E-signatureVerificationAndValidationService - e-Signature Verification and Validation Service - + + + + + E-signatureVerificationAndValidationService + [ABB144] e-Signature Verification and Validation Service + DESCRIPTION: Shares the functionality of the verification of documents that are signed electronically. -An ‘electronic signature’ means data in electronic form which is attached to or logically associated with other data in electronic form and which is used by the signatory to sign. -‘validation’ means the process of verifying and confirming that an electronic signature or a seal is valid. +An electronic signature means data in electronic form which is attached to or logically associated with other data in electronic form and which is used by the signatory to sign. +validation means the process of verifying and confirming that an electronic signature or a seal is valid. Based on eIDAS - 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. http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv%3AOJ.L_.2014.257.01.0073.01.ENG INTEROPERABILITY SALIENCY: IoP Dimension: Behavioral IoP -The e-Signature Verification and Validation Service ABB  is salient for technical interoperability because it provides +The e-Signature Verification and Validation Service ABB is salient for technical interoperability because it provides the functionalities required for e-signature verification and validation service. EXAMPLES: @@ -4490,38 +3117,26 @@ CEF eSignature DSS DSS (Digital Signature Services) is an open-source software library for electronic signature creation and validation. DSS supports the creation and verification of interoperable and secure electronic signatures in line with European legislation. In particular, DSS aims to follow the eIDAS Regulation and related standards closely. DSS can be re-used in an IT solution for electronic signatures to ensure that signatures are created and verified in line with European legislation and standards. DSS allows re-use in a variety of different ways: in an applet, in a stand-alone application or in a server application. DSS can also be used as a reference implementation for IT solutions which do not directly re-use it. CEF eSignature's DSS open-source library delivers the following benefits to its users: -• Open-source software under LGPL 2.1, a non-viral open source license; -• Interoperability of the e-signatures; -• Supports both e-signatures and e-seals; -• Validation of countersignatures and multiple signatures; -• Alignment with the eIDAS Regulation and related standards; -• Supports EU standards on: + Open-source software under LGPL 2.1, a non-viral open source license; + Interoperability of the e-signatures; + Supports both e-signatures and e-seals; + Validation of countersignatures and multiple signatures; + Alignment with the eIDAS Regulation and related standards; + Supports EU standards on: o Signature formats and packaging methods; o Signature validation procedures; -• Validation relying on Member States' trusted lists: + Validation relying on Member States' trusted lists: o Status of trust service providers/trust service, compensation of information, path validation. -https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eSignature - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:reusability_level -- eira:reusability_score -- eira:actual_reuse: Specifies if the solution is currently being reused -- eira:view]]> - ABB144 - - - - - E-signaturePreservationService - e-Signature Preservation Service - + + + + + E-signaturePreservationService + [ABB197] e-Signature Preservation Service + DESCRIPTION: Shares the functionality of extending the trustworthiness of the qualified electronic signature beyond the technological validity period. -An ‘electronic signature’ means data in electronic form which is attached to or logically associated with other data in electronic form and which is used by the signatory to sign. +An electronic signature means data in electronic form which is attached to or logically associated with other data in electronic form and which is used by the signatory to sign. Based on eIDAS - 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. http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv%3AOJ.L_.2014.257.01.0073.01.ENG @@ -4530,7 +3145,7 @@ Syn. e-Signature Archiving Service INTEROPERABILITY SALIENCY: IoP Dimension: Behavioral IoP -The e-Signature Preservation Service ABB  is salient for technical interoperability because it provides +The e-Signature Preservation Service ABB is salient for technical interoperability because it provides the functionalities required for e-signature preservation service. EXAMPLES: @@ -4539,39 +3154,27 @@ The following implementation is an example on how this specific Architecture Bui Namirial Spa Long term archiving solution Namirial is a Trust Service Provider, focused on addressing the fast growing market of Digital Transaction Management (DTM), which includes legally compliant electronic signatures, managing and tracking documents flows, conducting secure transactions and ensuring secure storage of data. It provides a long term archiving: -• Protect and preserve all documents generated while performing digital business transactions -• Make those documents easily searchable -• Accredited for Long-Term Archiving/Digital Preservation Services -• SaaS, high-availability, multi-company solution built to archive large volumes of documents -https://www.xyzmo.com/digital-signature/e-signature-products - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:reusability_level -- eira:reusability_score -- eira:actual_reuse: Specifies if the solution is currently being reused -- eira:view]]> - ABB197 - - - - - E-sealCreationService - e-Seal Creation Service - + + + + + E-sealCreationService + [ABB198] e-Seal Creation Service + DESCRIPTION: Shares the functionality of signing data in electronic forms on behalf of a legal person. -An ‘electronic seal' means data in electronic form, which is attached to or logically associated with other data in electronic form to ensure the latter’s origin and integrity. The ‘creator of a seal’ is a legal person who creates an electronic seal. +An electronic seal' means data in electronic form, which is attached to or logically associated with other data in electronic form to ensure the latters origin and integrity. The creator of a seal is a legal person who creates an electronic seal. Based on eIDAS - 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. http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv%3AOJ.L_.2014.257.01.0073.01.ENG INTEROPERABILITY SALIENCY: IoP Dimension: Behavioral IoP -The e-Seal Creation Service ABB  is salient for technical interoperability because it provides +The e-Seal Creation Service ABB is salient for technical interoperability because it provides the functionalities required for e-seal creation service. EXAMPLES: @@ -4581,45 +3184,33 @@ CEF eSignature DSS DSS (Digital Signature Services) is an open-source software library for electronic signature creation and validation. DSS supports the creation and verification of interoperable and secure electronic signatures in line with European legislation. In particular, DSS aims to follow the eIDAS Regulation and related standards closely. DSS can be re-used in an IT solution for electronic signatures to ensure that signatures are created and verified in line with European legislation and standards. DSS allows re-use in a variety of different ways: in an applet, in a stand-alone application or in a server application. DSS can also be used as a reference implementation for IT solutions which do not directly re-use it. CEF eSignature's DSS open-source library delivers the following benefits to its users: -• Open-source software under LGPL 2.1, a non-viral open source license; -• Interoperability of the e-signatures; -• Supports both e-signatures and e-seals; -• Validation of countersignatures and multiple signatures; -• Alignment with the eIDAS Regulation and related standards; -• Supports EU standards on: + Open-source software under LGPL 2.1, a non-viral open source license; + Interoperability of the e-signatures; + Supports both e-signatures and e-seals; + Validation of countersignatures and multiple signatures; + Alignment with the eIDAS Regulation and related standards; + Supports EU standards on: o Signature formats and packaging methods; o Signature validation procedures; -• Validation relying on Member States' trusted lists: + Validation relying on Member States' trusted lists: o Status of trust service providers/trust service, compensation of information, path validation. -https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eSignaturefile:///C:/Users/bocquilp/Downloads/DSS(ServiceOfferingDescription)%20(v0.03)%20(5).pdf - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:reusability_level -- eira:reusability_score -- eira:actual_reuse: Specifies if the solution is currently being reused -- eira:view]]> - ABB198 - - - - - E-sealVerificationAndValidationService - e-Seal Verification and Validation Service - + + + + + E-sealVerificationAndValidationService + [ABB199] e-Seal Verification and Validation Service + DESCRIPTION: Shares the functionality of the verification of documents that are signed electronically. -An ‘electronic seal' means data in electronic form, which is attached to or logically associated with other data in electronic form to ensure the latter’s origin and integrity. The ‘creator of a seal’ is a legal person who creates an electronic seal. +An electronic seal' means data in electronic form, which is attached to or logically associated with other data in electronic form to ensure the latters origin and integrity. The creator of a seal is a legal person who creates an electronic seal. Based on eIDAS - 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. http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv%3AOJ.L_.2014.257.01.0073.01.ENG INTEROPERABILITY SALIENCY: IoP Dimension: Behavioral IoP -The e-Seal Verification and Validation Service ABB  is salient for technical interoperability because it provides +The e-Seal Verification and Validation Service ABB is salient for technical interoperability because it provides the functionalities required for e-seal verification and validation service. EXAMPLES: @@ -4629,38 +3220,26 @@ CEF eSignature DSS DSS (Digital Signature Services) is an open-source software library for electronic signature creation and validation. DSS supports the creation and verification of interoperable and secure electronic signatures in line with European legislation. In particular, DSS aims to follow the eIDAS Regulation and related standards closely. DSS can be re-used in an IT solution for electronic signatures to ensure that signatures are created and verified in line with European legislation and standards. DSS allows re-use in a variety of different ways: in an applet, in a stand-alone application or in a server application. DSS can also be used as a reference implementation for IT solutions which do not directly re-use it. CEF eSignature's DSS open-source library delivers the following benefits to its users: -• Open-source software under LGPL 2.1, a non-viral open source license; -• Interoperability of the e-signatures; -• Supports both e-signatures and e-seals; -• Validation of countersignatures and multiple signatures; -• Alignment with the eIDAS Regulation and related standards; -• Supports EU standards on: + Open-source software under LGPL 2.1, a non-viral open source license; + Interoperability of the e-signatures; + Supports both e-signatures and e-seals; + Validation of countersignatures and multiple signatures; + Alignment with the eIDAS Regulation and related standards; + Supports EU standards on: o Signature formats and packaging methods; o Signature validation procedures; -• Validation relying on Member States' trusted lists: + Validation relying on Member States' trusted lists: o Status of trust service providers/trust service, compensation of information, path validation. -https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eSignaturefile:///C:/Users/bocquilp/Downloads/DSS(ServiceOfferingDescription)%20(v0.03)%20(5).pdf - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:reusability_level -- eira:reusability_score -- eira:actual_reuse: Specifies if the solution is currently being reused -- eira:view]]> - ABB199 - - - - - E-sealPreservationService - e-Seal Preservation Service - + + + + + E-sealPreservationService + [ABB200] e-Seal Preservation Service + DESCRIPTION: Shares the functionality of extending the trustworthiness of the qualified electronic signature beyond the technological validity period. -An ‘electronic seal' means data in electronic form, which is attached to or logically associated with other data in electronic form to ensure the latter’s origin and integrity. The ‘creator of a seal’ is a legal person who creates an electronic seal. +An electronic seal' means data in electronic form, which is attached to or logically associated with other data in electronic form to ensure the latters origin and integrity. The creator of a seal is a legal person who creates an electronic seal. Based on eIDAS - 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. http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv%3AOJ.L_.2014.257.01.0073.01.ENG @@ -4669,7 +3248,7 @@ Syn. e-Seal Archiving Service INTEROPERABILITY SALIENCY: IoP Dimension: Behavioral IoP -The e-Seal Preservation Service ABB  is salient for technical interoperability because it provides +The e-Seal Preservation Service ABB is salient for technical interoperability because it provides the functionalities required for e-seal preservation service. EXAMPLES: @@ -4679,38 +3258,26 @@ CEF eSignature DSS DSS (Digital Signature Services) is an open-source software library for electronic signature creation and validation. DSS supports the creation and verification of interoperable and secure electronic signatures in line with European legislation. In particular, DSS aims to follow the eIDAS Regulation and related standards closely. DSS can be re-used in an IT solution for electronic signatures to ensure that signatures are created and verified in line with European legislation and standards. DSS allows re-use in a variety of different ways: in an applet, in a stand-alone application or in a server application. DSS can also be used as a reference implementation for IT solutions which do not directly re-use it. CEF eSignature's DSS open-source library delivers the following benefits to its users: -• Open-source software under LGPL 2.1, a non-viral open source license; -• Interoperability of the e-signatures; -• Supports both e-signatures and e-seals; -• Validation of countersignatures and multiple signatures; -• Alignment with the eIDAS Regulation and related standards; -• Supports EU standards on: + Open-source software under LGPL 2.1, a non-viral open source license; + Interoperability of the e-signatures; + Supports both e-signatures and e-seals; + Validation of countersignatures and multiple signatures; + Alignment with the eIDAS Regulation and related standards; + Supports EU standards on: o Signature formats and packaging methods; o Signature validation procedures; -• Validation relying on Member States' trusted lists: + Validation relying on Member States' trusted lists: o Status of trust service providers/trust service, compensation of information, path validation. -https://ec.europa.eu/cefdigital/wiki/display/CEFDIGITAL/eSignaturefile:///C:/Users/bocquilp/Downloads/DSS(ServiceOfferingDescription)%20(v0.03)%20(5).pdf - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:reusability_level -- eira:reusability_score -- eira:actual_reuse: Specifies if the solution is currently being reused -- eira:view]]> - ABB200 - - - - - E-timestampCreationService - e-Timestamp Creation Service - + + + + + E-timestampCreationService + [ABB201] e-Timestamp Creation Service + DESCRIPTION: Shares the functionality of the verification of timestamps used for establishing evidence that a give piece of data existed at a given point in time. -An ‘electronic time stamp’ means data in electronic form which binds other data in electronic form to a particular time establishing evidence that the latter data existed at that time. +An electronic time stamp means data in electronic form which binds other data in electronic form to a particular time establishing evidence that the latter data existed at that time. Based on eIDAS - 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. http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv%3AOJ.L_.2014.257.01.0073.01.ENG @@ -4719,50 +3286,38 @@ Syn. eTS Creation Service INTEROPERABILITY SALIENCY: IoP Dimension: Behavioral IoP -The e-Timestamp Creation Service ABB  is salient for technical interoperability because it provides +The e-Timestamp Creation Service ABB is salient for technical interoperability because it provides the functionalities required for e-Timestamp creation service. EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): -DigiStamp eTimeStamp® -DigiStamp eTimeStamp® protects the intellectual property in any computer file: -• Use Desktop and Web applications for on-demand protection -• Plug the Timestamp Authority into the automated systems +DigiStamp eTimeStamp +DigiStamp eTimeStamp protects the intellectual property in any computer file: + Use Desktop and Web applications for on-demand protection + Plug the Timestamp Authority into the automated systems Plug-in rigorous implementation of US & EU standards: -• Secure, reliable, RFC 3161 timestamp cloud service -• Archiving and Hash Chaining keyless security -• Elliptic Curve Upgrade + Secure, reliable, RFC 3161 timestamp cloud service + Archiving and Hash Chaining keyless security + Elliptic Curve Upgrade Implementation of the Internet Engineering Task Force's RFC 3161 means DigiStamp timestamps are understood by data validation systems the world over: -• Implementation of ANSI X9.95 further increases the compatibility of our timestamps. -• Compliance with IETF RFC 3628 gives credence to the trustworthiness of our Time Stamp Authorities. -• Conformance to IETF RFC 3126 makes our timestamps usable for long-term, legally binding agreements. + Implementation of ANSI X9.95 further increases the compatibility of our timestamps. + Compliance with IETF RFC 3628 gives credence to the trustworthiness of our Time Stamp Authorities. + Conformance to IETF RFC 3126 makes our timestamps usable for long-term, legally binding agreements. https://www.digistamp.com/ freeTSA.org offers free NTP and DNSCRYPT services freeTSA.org provides a free Time Stamp Authority. Adding a trusted timestamp to code or to an electronic signature provides a digital seal of data integrity and a trusted date and time of when the transaction took place. Trusted timestamping is the process of securely keeping track of the creation and modification times of a document. Security here means that no one - not even the owner of the document - should be able to change it once it has been recorded provided that the timestamper's integrity is never compromised. FreeTSA trusted timestamping Software as a Service (SaaS) provides an easy method to apply RFC 3161 trusted timestamps to time-sensitive transactions through independently verified and auditable date and UTC (Coordinated Universal Time) sources. -https://www.freetsa.org/index_en.php - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:reusability_level -- eira:reusability_score -- eira:actual_reuse: Specifies if the solution is currently being reused -- eira:view]]> - ABB201 - - - - - E-timestampVerificationAndValidationService - e-Timestamp Verification and Validation Service - + + + + + E-timestampVerificationAndValidationService + [ABB202] e-Timestamp Verification and Validation Service + DESCRIPTION: Shares the functionality of the verification of timestamps used for establishing evidence that a give piece of data existed at a given point in time. -An ‘electronic time stamp’ means data in electronic form which binds other data in electronic form to a particular time establishing evidence that the latter data existed at that time. +An electronic time stamp means data in electronic form which binds other data in electronic form to a particular time establishing evidence that the latter data existed at that time. Based on eIDAS - 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. http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv%3AOJ.L_.2014.257.01.0073.01.ENG @@ -4771,7 +3326,7 @@ Syn. eTS Verification and Validation Service INTEROPERABILITY SALIENCY: IoP Dimension: Behavioral IoP -The e-Timestamp Verification and Validation Service ABB  is salient for technical interoperability because it provides +The e-Timestamp Verification and Validation Service ABB is salient for technical interoperability because it provides the functionalities required for e-timestamp verification and validation service. EXAMPLES: @@ -4779,26 +3334,14 @@ The following implementation is an example on how this specific Architecture Bui OpenSSL timestamp verification OpenSSL is an open-source tool that can be used to retrieve and verify digital timestamps. https://wiki.openssl.org/index.php/Manual:Ts(1) -https://www.digistamp.com/technical/software-alternatives/using-openssl-to-request-timestamps/ - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:reusability_level -- eira:reusability_score -- eira:actual_reuse: Specifies if the solution is currently being reused -- eira:view]]> - ABB202 - - - - - RegisteredElectronicDeliveryService - Registered Electronic Delivery Service - + + + + + RegisteredElectronicDeliveryService + [ABB203] Registered Electronic Delivery Service + DESCRIPTION: Shares the functionalities that i) makes it possible to transmit data between third parties by electronic means and ii) provides evidence relating to the handling of the transmitted data, including proof of sending and receiving the data, and iii) that protects transmitted data against the risk of loss, theft, damage or any unauthorised alterations; Based on eIDAS - 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. @@ -4806,35 +3349,23 @@ http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv%3AOJ.L_.2014.257.01.0 INTEROPERABILITY SALIENCY: IoP Dimension: Behavioral IoP -The Registered Electronic Delivery Service ABB  is salient for technical interoperability because it provides the functionalities related to the handling of data transmission. +The Registered Electronic Delivery Service ABB is salient for technical interoperability because it provides the functionalities related to the handling of data transmission. EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Qualified electronic registered delivery services listed with CEF Trusted List Browser tool Qualified electronic registered delivery services are listed on https://webgate.ec.europa.eu/tl-browser/#/search/1 -https://webgate.ec.europa.eu/tl-browser/#/search/1 - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:reusability_level -- eira:reusability_score -- eira:actual_reuse: Specifies if the solution is currently being reused -- eira:view]]> - ABB203 - - - - - TrustServiceProvisioningComponent - Trust Service Provisioning Component - + + + + + TrustServiceProvisioningComponent + [ABB69] Trust Service Provisioning Component + DESCRIPTION: Implements the functionalities encapsulating the trust services functionalities. -A ‘trust service’ means an electronic service normally provided for remuneration which consists of these functionalities: +A trust service means an electronic service normally provided for remuneration which consists of these functionalities: i) the creation, verification, and validation of electronic signatures, electronic seals or electronic time stamps, electronic registered delivery services and certificates related to those services, or ii) the creation, verification and validation of certificates for website authentication; or iii) the preservation of electronic signatures, seals or certificates related to those services. @@ -4844,8 +3375,8 @@ http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv%3AOJ.L_.2014.257.01.0 INTEROPERABILITY SALIENCY: IoP Dimension: Structural IoP -The Trust Service Provisioning Component ABB  is salient for technical interoperability because it provides -the implementation of the functionalities of information exchange between between administrations, businesses and citizens (e-signature and e-seal creation, verification,validation and preservation, timestamping creation, verification and validation, identity management, etc.) as stated in the EIF recommendation n°47: "Use trust services according to the Regulation on eID and Trust Services as mechanisms that ensure secure and protected data exchange in public services." +The Trust Service Provisioning Component ABB is salient for technical interoperability because it provides +the implementation of the functionalities of information exchange between between administrations, businesses and citizens (e-signature and e-seal creation, verification,validation and preservation, timestamping creation, verification and validation, identity management, etc.) as stated in the EIF recommendation n47: "Use trust services according to the Regulation on eID and Trust Services as mechanisms that ensure secure and protected data exchange in public services." EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): @@ -4853,42 +3384,17 @@ The following implementation is an example on how this specific Architecture Bui e-TrustEx Open e-TrustEx is a platform offered by the Directorate-General for Informatics of the European Commission to Public Administrations at European, national and regional level to set up secure exchange of natively digital documents from system to system via standardized interfaces. Open e-TrustEx provides a set of generic web services, which Public Administrations can use to connect heterogeneous applications, removing the need for complex point-to-point connections. http://eur-lex.europa.eu/legal-content/DE/TXT/?uri=CELEX%3A52016SC0279 -https://joinup.ec.europa.eu/solution/open-e-trustex - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:data_quality_level -- eira:data_quality_score: Overall data quality score -- eira:reusability_level -- eira:reusability_score -- eira:iop_level -- eira:iop_score -- eira:actual_reuse: Specifies if the solution is currently being reused -- eira:view]]> - ABB69 - - - - - - - - - - - - - - IdentityManagementService - Identity Management Service - + + + + + IdentityManagementService + [ABB204] Identity Management Service + DESCRIPTION: Shares the functionality of user authentication. -‘Electronic identification’ means the process of using person identification data in electronic form uniquely representing either a natural or legal person, or a natural person representing a legal person; -‘Authentication’ means an electronic process that enables the electronic identification of a natural or legal person, or the origin and integrity of data in electronic form to be confirmed; +Electronic identification means the process of using person identification data in electronic form uniquely representing either a natural or legal person, or a natural person representing a legal person; +Authentication means an electronic process that enables the electronic identification of a natural or legal person, or the origin and integrity of data in electronic form to be confirmed; Based on eIDAS - 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. http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv%3AOJ.L_.2014.257.01.0073.01.ENG @@ -4897,7 +3403,7 @@ Syn. Authentication Service, eID INTEROPERABILITY SALIENCY: IoP Dimension: Behavioral IoP -The Identity Management Service ABB  is salient for technical interoperability because it provides the functionalities of user authentication. +The Identity Management Service ABB is salient for technical interoperability because it provides the functionalities of user authentication. EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): @@ -4905,52 +3411,40 @@ The following implementation is an example on how this specific Architecture Bui EU Login EU Login is the European Commission's user authentication service. It allows authorised users to access a wide range of Commission web services. EU Login is the entry gate to sign in to different European Commission services and/or other systems. EU Login verifies your identity and allows recovering your personal settings, history and access rights in a secure way. You can sign in using social media accounts or the EU Login account. EU Login supports a variety of verification methods: -• Password; -• ECAS Mobile App PIN code; -• ECAS Mobile App QR code; -• On mobile authentication; -• Mobile phone + SMS; -• Token and Token CRAM. + Password; + ECAS Mobile App PIN code; + ECAS Mobile App QR code; + On mobile authentication; + Mobile phone + SMS; + Token and Token CRAM. https://webgate.ec.europa.eu/cas/about.html https://webgate.ec.europa.eu/cas/manuals/EU_Login_Tutorial_1.1.pdf Federal Public Service Policy and Support - Federal Authentication Service (FAS) Via the Federal Authentication Service (FAS) individuals are authenticated so that they can access secure online government applications. Characteristics: -• Three different security levels depending on the sensitivity of the information: user name and password; user name, password and token; electronic identity card with associated PIN code. -• Authentication when connecting to an application -• Support with the implementation of the service -• Support while the service is being used + Three different security levels depending on the sensitivity of the information: user name and password; user name, password and token; electronic identity card with associated PIN code. + Authentication when connecting to an application + Support with the implementation of the service + Support while the service is being used Attribute Publication Service: -• Collecting a user´s attributes from one or more reliable sources that are located in other government institutions (i.e., National Register, Crossroads Bank for Social Security and Crossroads Bank for Enterprises) -• Sending of the requested attributes to the requesting government application within the framework of a successful authentication + Collecting a users attributes from one or more reliable sources that are located in other government institutions (i.e., National Register, Crossroads Bank for Social Security and Crossroads Bank for Enterprises) + Sending of the requested attributes to the requesting government application within the framework of a successful authentication Users: -• All public services and institutions that want a secure authentication process for their applications: Federal public services and institutions; Communities and Regions; Provinces, municipalities and local public social welfare centres; businesses or persons implementing government contracts + All public services and institutions that want a secure authentication process for their applications: Federal public services and institutions; Communities and Regions; Provinces, municipalities and local public social welfare centres; businesses or persons implementing government contracts Requirements: -• Application with Fedict Service Desk and signing up to a user agreement -http://www.fedict.belgium.be/en/identificatie_beveiliging/federal_authentication_service - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:reusability_level -- eira:reusability_score -- eira:actual_reuse: Specifies if the solution is currently being reused -- eira:view]]> - ABB204 - - - - - IdentityManagementComponent - Identity Management Component - + + + + + IdentityManagementComponent + [ABB158] Identity Management Component + DESCRIPTION: Implements the functionality of user authentication. -‘Electronic identification’ means the process of using person identification data in electronic form uniquely representing either a natural or legal person, or a natural person representing a legal person; -‘Authentication’ means an electronic process that enables the electronic identification of a natural or legal person, or the origin and integrity of data in electronic form to be confirmed; +Electronic identification means the process of using person identification data in electronic form uniquely representing either a natural or legal person, or a natural person representing a legal person; +Authentication means an electronic process that enables the electronic identification of a natural or legal person, or the origin and integrity of data in electronic form to be confirmed; Based on eIDAS - 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. http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv%3AOJ.L_.2014.257.01.0073.01.ENG @@ -4959,7 +3453,7 @@ Syn. Authentication Component, eID INTEROPERABILITY SALIENCY: IoP Dimension: Structural IoP -The Identity Management Component ABB  is salient for technical interoperability because it provides the functionalities of user authentication. +The Identity Management Component ABB is salient for technical interoperability because it provides the functionalities of user authentication. EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): @@ -4967,35 +3461,19 @@ The following implementation is an example on how this specific Architecture Bui OpenIAM Identity Manager The OpenIAM Identity Manager automates the task of managing identities across the various devices and applications used by the enterprise. This includes applications within the enterprise such as Active Directory and Exchange, and cloud based applications such as Google Apps. OpenIAM Identity Manager provides capabilities such as: -• Provisioning, De-provisioning, Workflow -• Password Management, Password Policies, Synchronization -• Self-Service, allowing locked users to reset their accounts, manage their profiles, challenge response security questions -• Audit, Attestation, Reporting -• Delegated Administration -http://www.openiam.com/products/identity-manager/idm-overview/ - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:data_quality_level -- eira:data_quality_score: Overall data quality score -- eira:reusability_level -- eira:reusability_score -- eira:iop_level -- eira:actual_reuse: Specifies if the solution is currently being reused -- eira:view]]> - ABB158 - - - - - - TrustRegistryService - Trust Registry Service - + + + + + TrustRegistryService + [ABB145] Trust Registry Service + DESCRIPTION: Shares the functionality of the discovery of essential information about e.g. supervised/accredited trust service providers issuing certificates for electronic signatures, for electronic seals or for website authentication; supervised/accredited trust services for eSignature, eSeal or TimeStamp creation and validation; supervised/accredited trust services for eSignature or eSeal preservation; supervised/accredited trust services for electronic registered delivery. Based on eIDAS - 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. @@ -5005,33 +3483,21 @@ Syn. Trusted List Service INTEROPERABILITY SALIENCY: IoP Dimension: Behavioral IoP -The Trust Registry Service ABB  is salient for technical interoperability because it provides the functionalities of the discovery of essential information about accredited service providers. +The Trust Registry Service ABB is salient for technical interoperability because it provides the functionalities of the discovery of essential information about accredited service providers. EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): BE:Trusted BE:Trusted list including information related to the qualified trust service providers which are supervised by the issuing Member State, together with information related to the qualified trust services provided by them, in accordance with the relevant provisions laid down in 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://tsl.belgium.be/archive/TSL-BE-2016-T3_vi5_sn27%20SPF%20Economie_signed.pdf - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:reusability_level -- eira:reusability_score -- eira:actual_reuse: Specifies if the solution is currently being reused -- eira:view]]> - ABB145 - - - - - TrustRegistryComponent - Trust Registry Component - + + + + + TrustRegistryComponent + [ABB146] Trust Registry Component + DESCRIPTION: Implements the functionality of the discovery of essential information about e.g. supervised/accredited trust service providers issuing certificates for electronic signatures, for electronic seals or for website authentication; supervised/accredited trust services for eSignature, eSeal or TimeStamp creation and validation; supervised/accredited trust services for eSignature or eSeal preservation; supervised/accredited trust services for electronic registered delivery. Based on eIDAS - 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. @@ -5041,7 +3507,7 @@ Syn. Trusted List Component INTEROPERABILITY SALIENCY: IoP Dimension: Structural IoP -The Trust Registry Component ABB  is salient for technical interoperability because it implements the functionalities of the discovery of essential information about accredited service providers. +The Trust Registry Component ABB is salient for technical interoperability because it implements the functionalities of the discovery of essential information about accredited service providers. EXAMPLES The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): @@ -5054,31 +3520,14 @@ Trusted Lists are therefore essential in ensuring certainty and building trust a Member States may add trust services other than the qualified ones in the trusted lists, on a voluntary basis, at national level, provided that it is clearly indicated that they are not qualified according to Regulation (EU) No 910/2014. In order to allow access to the trusted lists of all Member States, the Commission makes them available to the public, through a secure channel to an authenticated web server, the trusted lists as notified by Member States, in a signed or sealed form suitable for automated processing. https://ec.europa.eu/digital-single-market/en/eu-trusted-lists-trust-service-providers -https://ec.europa.eu/information_society/policy/esignature/trusted-list/tl-mp.xml - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:data_quality_level -- eira:data_quality_score: Overall data quality score -- eira:reusability_level -- eira:reusability_score -- eira:iop_level -- eira:iop_score -- eira:actual_reuse: Specifies if the solution is currently being reused -- eira:view]]> - ABB146 - - - - - - DataExchangeService - Data Exchange Service - + + + + + DataExchangeService + [ABB43] Data Exchange Service + DESCRIPTION: Shares the functionality that enables the secure exchange of messages, records, forms and other kinds of data between different ICT systems. This includes data routing, except endpoint discovery. Based on EIFv2 @@ -5086,33 +3535,20 @@ http://ec.europa.eu/isa/documents/isa_annex_ii_eif_en.pdf INTEROPERABILITY SALIENCY: IoP Dimension: Behavioral IoP -The Data Exchange Service ABB  is salient for technical interoperability because it provides secure and trustworthy data exchange between different ICT systems as stated in the EIF: "Define a common security and privacy framework and establish processes for public services to ensure secure and trustworthy data exchange between public administrations and in interactions with citizens and businesses." +The Data Exchange Service ABB is salient for technical interoperability because it provides secure and trustworthy data exchange between different ICT systems as stated in the EIF: "Define a common security and privacy framework and establish processes for public services to ensure secure and trustworthy data exchange between public administrations and in interactions with citizens and businesses." EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): XMLGate XMLGate is a Web service application used to validate an XML instance against a well-defined schema. The XML flow is submitted either via a PDF form or by uploading the XML file. -https://webgate.ec.europa.eu/sanco-xmlgate/Login.jsp;jsessionid=2MPn_N5Wg9Dar4_W2-yVL_Xg-VlW3kn47PLVbNise9X5Kycx1yLI!-25226473 - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:reusability_level -- eira:reusability_score -- eira:actual_reuse: Specifies if the solution is currently being reused -- eira:view]]> - ABB43 - - - - - - DataExchangeComponent - Data Exchange Component - + + + + + DataExchangeComponent + [ABB64] Data Exchange Component + DESCRIPTION: Implements the functionality that enables the secure exchange of messages, records, forms and other kinds of data between different ICT systems. This includes data routing, except endpoint discovery. Based on EIFv2 @@ -5126,31 +3562,14 @@ EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): Open e-TrustEx Open e-TrustEx is a secure document exchange platform. Solution for European public administration that needs to electronically exchange information with other entities in a secure way. Open e-TrustEx is a cross-sector, open source tool that helps administrations to exchange structured and unstructured documents and to connect to pan-European e-delivery infrastructures with reduced investment. For Commission services, DG Informatics operates the e-TrustEx platform for a fee. -https://ec.europa.eu/isa2/solutions/open-e-trustex_en - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:data_quality_level -- eira:data_quality_score: Overall data quality score -- eira:reusability_level -- eira:reusability_score -- eira:iop_level -- eira:iop_score -- eira:actual_reuse: Specifies if the solution is currently being reused -- eira:view]]> - ABB64 - - - - - - HostingAndNetworkingInfrastructure - Hosting and Networking Infrastructure - + + + + + HostingAndNetworkingInfrastructure + [ABB190] Hosting and Networking Infrastructure + DESCRIPTION: Shares the functionalities for i) hosting Interoperable European Solutions and ii) providing the necessary networks for operating these solutions. Source: ISA2 - EIA Action @@ -5166,39 +3585,20 @@ DIGIT Hosting and Networking Infrastructure Service The mission of the Directorate General for Informatics (DIGIT) is to deliver digital services to enable EU policies and to support the Commission's internal administration. Mission statement With this goal in mind, DIGIT as trusted partner has the responsibility to: -• Provide the EC, and whenever appropriate other European Institutions and bodies, with high quality and innovative: -o Workplace solutions – creating new ways of working and collaboration for staff; -o Business solutions – delivering information systems supporting rationalised business processes within the framework of the corporate IT Governance strategy; -o Infrastructure solutions – providing reliable, cost-effective and secure infrastructure and services; -o Effective solutions – aligning IT investments with business priorities, facilitating relationships with our strategic partners, balancing risk with business value for the Institution. -• Support the modernisation of public administrations by promoting and facilitating interoperability so that European public administrations can work seamlessly together and with businesses and citizens across boundaries. -https://ec.europa.eu/info/sites/info/files/strategic-plan-2016-2020-dg-digit_march2016_en.pdf - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:reusability: Whether or not this building block could be reused as part of another solution -- eira:reuse_status: The type of reuse (if reusable): 'Exposed for reuse as main service' means that the building block is exposed to other solutions for reuse as the current solution's primary service. 'Exposed for reuse as supporting service' means that the building block is exposed to other solutions for reuse but only if the solution is already being reused for it's primary service. 'Reused' means that the building block is actually reused from another solution. -- eira:view]]> - ABB190 - - - - - - - - - - - - - PublicNetwork - Public Network - + + + + + PublicNetwork + [ABB94] Public Network + DESCRIPTION: A network that can be accessed by the public (public administrations, businesses and citizens) without specific authorisations. Interoperable European Solutions can rely on Public Networks (e.g. the Internet) to realise the physical communication between nodes. Source: ISA2 - EIA Action @@ -5212,23 +3612,14 @@ The following implementation is an example on how this specific Architecture Bui World-Wide-Web (WWW) The WorldWideWeb (W3) is a wide-area hypermedia information retrieval initiative aiming to give universal access to a large universe of documents. -http://info.cern.ch/hypertext/WWW/TheProject.html - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:actual_use: Specifies if the solution is currently used, planned to be used or not yet used -- eira:view]]> - ABB94 - - - - - PrivateNetwork - Private Network - + + + + + PrivateNetwork + [ABB93] Private Network + DESCRIPTION: A network that is used for the only purpose of realising the physical communication among Interoperable European Solution (e.g. sTESTA), and cannot be accessed by the public. Source: ISA2 - EIA Action @@ -5244,26 +3635,16 @@ Any private network Hosts within enterprises that use IP can be partitioned into two categories: Category 1: hosts that do not require access to hosts in other enterprises or the Internet at large; hosts within this category may use IP addresses that are unambiguous within an enterprise, but may be ambiguous between enterprises. Category 2: hosts that need access to a limited set of outside services (e.g., E-mail, FTP, netnews, remote login) which can be handled by mediating gateways (e.g., application layer gateways). For any hosts in this category an unrestricted external access (provided via IP connectivity) may be unnecessary and even undesirable for privacy/security reasons. Just like hosts within the first category, such hosts may use IP addresses that are unambiguous within an enterprise, but may be ambiguous between enterprises. -A third category is what is called a 'public network’ and consist of the following: +A third category is what is called a 'public network and consist of the following: Category 3: hosts that need network layer access outside the enterprise (provided via IP connectivity); hosts in the last category require IP addresses that are globally unambiguous. -https://tools.ietf.org/html/rfc1918 - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:actual_use: Specifies if the solution is currently used, planned to be used or not yet used -- eira:view]]> - ABB93 - - - - - Network - Network - + + + + + Network + [ABB92] Network + DESCRIPTION: Transmission systems and, where applicable, switching or routing equipment and other resources which permit the conveyance of signals by wire, by radio, by optical or by other electromagnetic means, including satellite networks, fixed (circuit- and packet- switched, including Internet) and mobile terrestrial networks, electricity cable systems, to the extent that they are used for the purpose of transmitting signals, networks used for radio and television broadcasting, and cable television networks, irrespective of the type of information conveyed. Source: DIRECTIVE 2002/21/EC on a common regulatory framework for electronic communications networks and services @@ -5276,28 +3657,16 @@ The Network ABB is salient for technical interoperability because it provides th EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): sTESTA -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. +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. The network uses the Internet Protocols (IP) to ensure universal reach, but is operated by the EU Commission separately from the Internet. It provides guaranteed performance and a high level of security and has connections with all the EU Institutions and national networks. It caters for the exchange of both unclassified and classified information. -https://ec.europa.eu/isa2/solutions/testa_en - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:actual_use: Specifies if the solution is currently used, planned to be used or not yet used -- eira:view]]> - ABB92 - - - - - - - NetworkingService - Networking Service - + + + + + NetworkingService + [ABB150] Networking Service + DESCRIPTION: Shares the functionalities provided by a network provider which is the combination of transmission systems and, where applicable, switching or routing equipment and other resources which permit the conveyance of signals by wire, by radio, by optical or by other electromagnetic means, including satellite networks, fixed (circuit- and packet- switched, including Internet) and mobile terrestrial networks, electricity cable systems, to the extent that they are used for the purpose of transmitting signals, networks used for radio and television broadcasting, and cable television networks, irrespective of the type of information conveyed. Based on DIRECTIVE 2002/21/EC on a common regulatory framework for electronic communications networks and services @@ -5305,32 +3674,22 @@ http://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=CELEX:32002L0021&from INTEROPERABILITY SALIENCY: IoP Dimension: Behavioural IoP -The Networking Service ABB is salient for technical interoperability because it provides all the required functionalities in order to create the suitable network underlayer where can operate interoperable solutions. +The Networking Service ABBis salient for technical interoperability because it provides all the required functionalities in order to create the suitable network underlayer where can operate interoperable solutions. EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): sTESTA -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. +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. The network uses the Internet Protocols (IP) to ensure universal reach, but is operated by the EU Commission separately from the Internet. It provides guaranteed performance and a high level of security and has connections with all the EU Institutions and national networks. It caters for the exchange of both unclassified and classified information. -https://ec.europa.eu/isa2/solutions/testa_en - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:actual_use: Specifies if the solution is currently used, planned to be used or not yet used -- eira:view]]> - ABB150 - - - - - - HostingService - Hosting Service - + + + + + HostingService + [ABB151] Hosting Service + DESCRIPTION: Shares the functionalities of a hosting provider, typically a high availability and high performance hosting infrastructure that is being comprised, among other elements, of back-end web server instances and application servers for hosting and serving both static and dynamic sites. Based on DIGIT C Infrastructure Services Provision @@ -5345,24 +3704,14 @@ The following implementation is an example on how this specific Architecture Bui DIGIT/C Hosting Service DIGIT/C offers a high availability and high performance hosting infrastructure that is being comprised, among other elements, of back-end web server instances and application servers for hosting and serving both static and dynamic sites. -http://ec.europa.eu/ipg/build/infrastructure/index_en.htm - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:actual_use: Specifies if the solution is currently used, planned to be used or not yet used -- eira:view]]> - ABB151 - - - - - - HostingFacility - Hosting Facility - + + + + + HostingFacility + [ABB191] Hosting Facility + DESCRIPTION: The equipment supporting the hosting of Interoperable European Solutions and their components, usually embodied in a building. Based on DIGIT C Infrastructure Services Provision @@ -5380,26 +3729,14 @@ DIGIT/C offers a high availability and high performance hosting infrastructure t The dynamic sites supported by the standard Apache web servers are mainly sites based on Coldfusion and in some cases also sites using CGI scripts. Dynamic sites based on particular technologies (i.e. Weblogic) are being hosted on individual application servers and are being integrated with the other related sites using reverse proxy mappings. Direct HTTP access to the back-end web servers hosting the static sites is denied by the standard web server configuration. -http://ec.europa.eu/ipg/build/infrastructure/index_en.htm - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- secure_access: Does the hosting facility provide secure access capabilities? -- processing: Does the hosting facility provide processing resources? -- storage: Does the hosting facility provide storage capacity? -- eira:actual_reuse: Specifies if the solution is currently being reused -- eira:view]]> - ABB191 - - - - - PublicHostingFacility - Public Hosting Facility - + + + + + PublicHostingFacility + [ABB193] Public Hosting Facility + DESCRIPTION: The equipment supporting the hosting of Interoperable European Solutions and their components, usually embodied in a building, which is owned by a third party and shared between organizations (e.g. cloud services). Based on DIGIT C Infrastructure Services Provision @@ -5413,26 +3750,14 @@ EXAMPLES: Amazon Web Services (AWS) AWS provides a comprehensive suite of services and solutions to run sophisticated and scalable applications to help achieve better business outcomes. Running your applications in the AWS Cloud can help you move faster, operate more securely, and save substantial costs; all while benefitting from the agility, scale and performance of the cloud. -https://aws.amazon.com/solutions/?nc2=h_ql_sol - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:secure_access: Does the hosting facility provide secure access capabilities? -- eira:processing: Does the hosting facility provide processing resources? -- eira:storage: Does the hosting facility provide storage capacity? -- eira:actual_reuse: Specifies if the solution is currently being reused -- eira:view]]> - ABB193 - - - - - PrivateHostingFacility - Private Hosting Facility - + + + + + PrivateHostingFacility + [ABB192] Private Hosting Facility + DESCRIPTION: A Hosting Facility, meaning the equipment supporting the hosting of Interoperable European Solutions and their components, usually embodied in a build-in, which is owned by or dedicated to one organization (e.g. data centre or private cloud). Based on DIGIT C Infrastructure Services Provision @@ -5447,28 +3772,16 @@ The following implementation is an example on how this specific Architecture Bui DG TAXUD Surveillance3 IES Datawarehouse servers hosted in DG TAXUD Data Centre The Surveillance3 Data Warehouse plays multiple roles: -• The role of ‘hub-and-spoke’ within the Surveillance3 system where data from different systems are integrated and linked and made available for report & analytics as well as the central place from which other systems are fed with the correct information. -• The role of reporting environment offering all the required reporting, data analysis & discovery and data mining functionality. -https://ec.europa.eu/assets/taxud/taxation_customs/tenders/2016ao02_a2_technical_en.pdf - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- secure_access: Does the hosting facility provide secure access capabilities? -- processing: Does the hosting facility provide processing resources? -- storage: Does the hosting facility provide storage capacity? -- eira:actual_reuse: Specifies if the solution is currently being reused -- eira:view]]> - ABB192 - - - - - ContentManagementService - Content Management Service - + + + + + ContentManagementService + [ABB380] Content Management Service + DESCRIPTION: A Content Management System (CMS) is responsible for: - developing Website templates and functionalities assigning appropriate user permissions and workflows @@ -5485,7 +3798,7 @@ Source: https://www.eui.eu/ServicesAndAdmin/CommunicationsService/WebUnit/Web-CM INTEROPERABILITY SALIENCY: IoP Dimension: Behavioral IoP -The Content Management Service ABB  is salient for technical interoperability because it provides and shares the functionalities of dynamic creation, distribution and analysis of contents (images, videos, etc.) as stated in the EIF: " Catalogues help others to find reusable resources (e.g. services, data, software, data models). Various types of catalogue exist, e.g. directories of services, libraries of software components, open data portals, registries of base registries, metadata catalogues, catalogues of standards, specifications and guidelines. Commonly agreed descriptions of the services, data, registries and interoperable solutions published in catalogues are needed to enable interoperability between catalogues." +The Content Management Service ABB is salient for technical interoperability because it provides and shares the functionalities of dynamic creation, distribution and analysis of contents (images, videos, etc.) as stated in the EIF: " Catalogues help others to find reusable resources (e.g. services, data, software, data models). Various types of catalogue exist, e.g. directories of services, libraries of software components, open data portals, registries of base registries, metadata catalogues, catalogues of standards, specifications and guidelines. Commonly agreed descriptions of the services, data, registries and interoperable solutions published in catalogues are needed to enable interoperability between catalogues." EXAMPLES: FPFIS-CMS: @@ -5493,35 +3806,25 @@ FPFIS-CMS: Web sites are a key tool for external communications. They are the institution's business card. Websites are a very cost-effective and efficient means of communication. EUROPA now hosts over 460 websites. EUROPA would benefit from fewer and better sites to respond to user needs. To address the shortcomings, as part of the Commission's IT governance process, the College on 30 November 2011, instructed Commission departments to rationalise the Institution's web presence. Reduce the cost (human, financial, technical) of the Commission's web presence via exploiting economies of scale and eliminating redundancies by building corporate solutions. The European Commission should offer a corporate service which optimizes and harmonizes the use of different website tools, which speeds up the creation of new external dynamic and social websites (i.e. in days or weeks and not months) and which provides a common solid modern shared infrastructure to support the rapid deployment of these sites". -Source: https://webgate.ec.europa.eu/fpfis/mwikis/thinktank/index.php/Content_Management_System_of_the_Flexible_Platform - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:reusability_level -- eira:reusability_score -- eira:actual_reuse: Specifies if the solution is currently being reused -- eira:view]]> - ABB380 - - - - - DataWarehouseService - Data Warehouse Service - + + + + DataWarehouseService + [ABB378] Data Warehouse Service + DESCRIPTION: +A data warehouse is a central repository where raw data is transformed and stored in query-able forms. It is an information system that contains historical and commutative data from single or multiple sources. It simplifies reporting and analysis process of the organization. INTEROPERABILITY SALIENCY: IoP Dimension: Behavioral IoP -The Data Warehouse Service ABB  is salient for technical interoperability because it provides and shares the functionality for the short-term or medium-term preservation of records and information in electronic form in order to ensure their temporal egibility, reliability and integrity and to ease their management as stated in the EIF: "Legislation requires that decisions and data are stored and can be accessed for a specified time. This means that records and information in electronic form held by public administrations for the purpose of documenting procedures and decisions must be preserved and be converted, where necessary, to new media when old media become obsolete. The goal is to ensure that records and other forms of information keep their legibility, reliability and integrity and can be accessed as long as needed subject to security and privacy provisions." +The Data Warehouse Service ABB is salient for technical interoperability because it provides and shares the functionality for the short-term or medium-term preservation of records and information in electronic form in order to ensure their temporal egibility, reliability and integrity and to ease their management as stated in the EIF: "Legislation requires that decisions and data are stored and can be accessed for a specified time. This means that records and information in electronic form held by public administrations for the purpose of documenting procedures and decisions must be preserved and be converted, where necessary, to new media when old media become obsolete. The goal is to ensure that records and other forms of information keep their legibility, reliability and integrity and can be accessed as long as needed subject to security and privacy provisions." EXAMPLES: -ESSnet: The overall objective of this ESSnet is to provide assistance in the development of more integrated databases and data production systems for business statistics in Member States. Therefore the ESSnet has to work on issues that are common for the majority of the ESS NSIs when applying a data warehousing approach for statistics. +The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): + +ESSnet: +The overall objective of this ESSnet is to provide assistance in the development of more integrated databases and data production systems for business statistics in Member States. Therefore the ESSnet has to work on issues that are common for the majority of the ESS NSIs when applying a data warehousing approach for statistics. Its general objectives are: - Review of current best practices in integrated business data systems @@ -5530,1973 +3833,955 @@ that a data warehouse might provide - Examination of ways in which data can be combined to support new outputs - Provision of recommendations on how the ESS can improve data warehousing -Source: https://ec.europa.eu/eurostat/cros/content/data-warehouse-sga1_en - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:reusability_level -- eira:reusability_score -- eira:actual_reuse: Specifies if the solution is currently being reused -- eira:view]]> - ABB378 - - - - - - DataWarehouseComponent - Data Warehouse Component - + + + + DataWarehouseComponent + [ABB379] Data Warehouse Component + DESCRIPTION: +A data warehouse Component is part of the central repository where raw data is transformed and stored in query-able forms. It is an information system that contains historical and commutative data from single or multiple sources. It simplifies reporting and analysis process of the organization. INTEROPERABILITY SALIENCY: IoP Dimension: Structural IoP -The Data Warehouse Component ABB  is salient for technical interoperability because it provides and shares the functionality for the short-term or medium-term preservation of records and information in electronic form in order to ensure their temporal egibility, reliability and integrity and to ease their management as stated in the EIF: "Legislation requires that decisions and data are stored and can be accessed for a specified time. This means that records and information in electronic form held by public administrations for the purpose of documenting procedures and decisions must be preserved and be converted, where necessary, to new media when old media become obsolete. The goal is to ensure that records and other forms of information keep their legibility, reliability and integrity and can be accessed as long as needed subject to security and privacy provisions." +The Data Warehouse Component ABB is salient for technical interoperability because it provides and shares the functionality for the short-term or medium-term preservation of records and information in electronic form in order to ensure their temporal egibility, reliability and integrity and to ease their management as stated in the EIF: "Legislation requires that decisions and data are stored and can be accessed for a specified time. This means that records and information in electronic form held by public administrations for the purpose of documenting procedures and decisions must be preserved and be converted, where necessary, to new media when old media become obsolete. The goal is to ensure that records and other forms of information keep their legibility, reliability and integrity and can be accessed as long as needed subject to security and privacy provisions." EXAMPLES: -ESSnet: The overall objective of this ESSnet is to provide assistance in the development of more integrated databases and data production systems for business statistics in Member States. Therefore the ESSnet has to work on issues that are common for the majority of the ESS NSIs when applying a data warehousing approach for statistics. +The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): + +ESSnet: +The overall objective of this ESSnet is to provide assistance in the development of more integrated databases and data production systems for business statistics in Member States. Therefore the ESSnet has to work on issues that are common for the majority of the ESS NSIs when applying a data warehousing approach for statistics. Its general objectives are: - Review of current best practices in integrated business data systems - Identification of problems and solutions in current practices and the opportunities that a data warehouse might provide - Examination of ways in which data can be combined to support new outputs - Provision of recommendations on how the ESS can improve data warehousing -Source: https://ec.europa.eu/eurostat/cros/content/data-warehouse-sga1_en - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:status: The development or realisation status of this building block -- eira:reusability_level -- eira:reusability_score -- eira:actual_reuse: Specifies if the solution is currently being reused -- eira:view]]> - ABB379 - - - - - IopSpecificationUnderpinningView - IOP specification underpinning View - - - - - - - - InteroperabilitySpecification - Interoperability Specification - + + -Source: ISA2 – EIA Action + + DataRepository + [ABB419] Data Repository + DESCRIPTION: +A data repository can be defined as a place that holds data, makes data available to use, and organizes data in a logical manner. A data repository may also be defined as an appropriate, subject-specific location where researchers can submit their data. Data repositories may have specific requirements concerning subject or research domain; data re-use and access; file format and data structure; and the types of metadata that can be used. -IoP dimensions: Structural IoP, Behavioral IoP, Governance IoP - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:url: The URL at which the specification can be referenced online -- eira:identifier: The identifier is unique. It identifies univocally the specification in the Cartography -- eira:body: The body contains statements on one or several Building Blocks. It informs either (i.e. proposed mode) on the proposed specification at the ABB level to achieve interoperability for its SBBs or (i.e. in solution descriptive mode) on a specification to which an SBB is actually compliant to achieve interoperability -- eira:domain: The domain can be either domain-neutral (not related to any public policy domain) or domain-specific to a given set of public policy domains. It informs on the public policy domain of application of the specification -- eira:view]]> - ABB162 - - - - - - - LegalInteroperabilitySpecification - Legal Interoperability Specification - - ABB175 - - - - OrganisationalInteroperabilitySpecification - Organisational Interoperability Specification - + + -Memorandum of Understanding on Economic and Financial Statistics between the DG Statistics of the European Central Bank and Eurostat -The purpose of this Memorandum of Understanding is to set out the respective areas of responsibility in economic and financial statistics at the Community level of the ECB (Directorate General Statistics) and the Commission (Eurostat); to provide a framework for the exchange and reproduction of data; to note the forms which co-operation between the Directorate General Statistics (DG Statistics) and Eurostat will take; and to set down a procedure for resolving disagreements. -https://www.ecb.europa.eu/ecb/legal/pdf/en_mou_with_eurostat1.pdf - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:url: The URL at which the specification can be referenced online -- eira:identifier: The identifier is unique. It identifies univocally the specification in the Cartography -- eira:body: The body contains statements on one or several Building Blocks. It informs either (i.e. proposed mode) on the proposed specification at the ABB level to achieve interoperability for its SBBs or (i.e. in solution descriptive mode) on a specification to which an SBB is actually compliant to achieve interoperability -- eira:domain: The domain can be either domain-neutral (not related to any public policy domain) or domain-specific to a given set of public policy domains. It informs on the public policy domain of application of the specification -- eira:view]]> - ABB176 - - - - - - - SemanticInteroperabilitySpecification - Semantic Interoperability Specification - + DataAnalyticsService + [ABB420] Data Analytics Service + DESCRIPTION: +Shares the functionalities of analysing a great amount of raw data in order to make conclusions about specific information. Data analytics services enable the automation of mechanical processes and algorithms that work over raw data for human consumption. -Source: How does the EIRA© support interoperability? -https://joinup.ec.europa.eu/sites/default/files/how_does_eira_support_interoperability_v1_0_0.pdf +Source: https://www.investopedia.com/terms/d/data-analytics.asp INTEROPERABILITY SALIENCY: -IoP Dimension: Structural IoP, Behavioral IoP, Governance IoP -The Semantic Interoperability Specification ABB is salient for semantic interoperability because it enables organisations to process information from external sources in a meaningful manner and ensuring that the precise meaning of exchanged information is understood and preserved throughout exchanges between parties as stated in the EIF recommendation n°32: "Support the establishment of sector-specific and cross-sectoral communities that aim to create open information specifications and encourage relevant communities to share their results on national and European platforms." +IoP Dimension: Behavioral IoP +The Data Analytics Service ABB is salient for technical interoperability because it enables the automated processing and analysis of different data source. EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): -United Nations Centre for Trade Facilitation and E-Business (UN/CEFACT) standard - International Plant Protection Convention (IPPC) SPSCertificate -Specification of phytosanitary certificates. These certificates are issued to indicate that consignments of plants, plant products or other regulated articles meet specified phytosanitary import requirements and are in conformity with the certifying statement of the appropriate model certificate. -https://www.ippc.int/en/ephyto/ephyto-technical-information/ - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:url: The URL at which the specification can be referenced online -- eira:identifier: The identifier is unique. It identifies univocally the specification in the Cartography -- eira:body: The body contains statements on one or several Building Blocks. It informs either (i.e. proposed mode) on the proposed specification at the ABB level to achieve interoperability for its SBBs or (i.e. in solution descriptive mode) on a specification to which an SBB is actually compliant to achieve interoperability -- eira:domain: The domain can be either domain-neutral (not related to any public policy domain) or domain-specific to a given set of public policy domains. It informs on the public policy domain of application of the specification -- eira:view]]> - ABB177 - - - - - - TechnicalInteroperabilitySpecification - Technical Interoperability Specification - + + -Source: Directive 98/34/EC laying down a procedure for the provision of information in the field of technical standards -and regulations and of rules on Information Society services; -http://eur-lex.europa.eu/LexUriServ/LexUriServ.do?uri=CONSLEG:1998L0034:20070101:EN:PDF + + DataAnalyticsComponent + [ABB421] Data Analytics Component + DESCRIPTION: +Implements the functionality of serving any current or future Digital Service Infrastructure (DSI) requiring data analysis capabilities. Data analytics component enable the automation of mechanical processes and algorithms that work over raw data for human consumption. INTEROPERABILITY SALIENCY: -IoP dimensions: Structural IoP, Behavioral IoP, Governance IoP -The Technical Interoperability Specification ABB is salient for technical interoperability because it assesses the characteristics required of a product to support interoperability solutions. +IoP Dimension: Structural IoP +The Data Analytics Component ABB is salient for technical interoperability because it provides the implementation of functionalities for the automation of mechanical processes and algorithms that work over raw data for human consumption. EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): -HTTPS specification -HTTP [RFC2616] was originally used in the clear on the Internet. However, increased use of HTTP for sensitive applications has required security measures. SSL, and its successor TLS [RFC2246] were designed to provide channel-oriented security. -https://tools.ietf.org/html/rfc2818 - -Attributes: -- ID: Internal key used to identify an architecture building block -- dct:type: The type of the architecture building block -- dct:publisher: The name of the individual or organisation that is documenting the current building block -- dct:modified: The date that the information documented for this building block was last modified -- eira:url: The URL at which the specification can be referenced online -- eira:identifier: The identifier is unique. It identifies univocally the specification in the Cartography -- eira:body: The body contains statements on one or several Building Blocks. It informs either (i.e. proposed mode) on the proposed specification at the ABB level to achieve interoperability for its SBBs or (i.e. in solution descriptive mode) on a specification to which an SBB is actually compliant to achieve interoperability -- eira:domain: The domain can be either domain-neutral (not related to any public policy domain) or domain-specific to a given set of public policy domains. It informs on the public policy domain of application of the specification -- eira:view]]> - ABB178 - - - - - - - - - - - EiraOntologyViewpoint - EIRA Ontology viewpoint - - - - - - - - - - - - - - - - - - - - - - - - - EiraViewpoint - EIRA Viewpoint - - ABB333 - - - - - - ArchitectureBuildingBlock - Architecture Building Block - - ABB334 - - - - - - SolutionBuildingBlock - Solution Building Block - - ABB335 - - - - - - EiraView - EIRA View - - ABB336 - - - - - - - EiraArchitectureBuildingBlock - EIRA Architecture Building Block - - ABB337 - - - - - - - - - - EiraSolutionBuildingBlock - EIRA Solution Building Block - - ABB338 - - - - - - - Solution - Solution - - ABB339 - - - - - - EifInteroperabilityLevel - EIF Interoperability Level - - ABB340 - - - - - PublicServiceAgent - Public Service Agent - - ABB341 - - - - PublicServiceManifestation - Public Service Manifestation - - ABB342 - - - - PublicServiceComponent - Public Service Component - - ABB343 - - - - KeyInteroperabilityEnabler - Key Interoperability Enabler - - ABB344 - - - - - InteroperabilityAspect - Interoperability Aspect - - ABB345 - - - - - - InteroperabilityRequirement - Interoperability Requirement - - ABB346 - - - - - - - - LegalInteroperabilityRequirement - Legal Interoperability Requirement - - ABB347 - - - - OrganisationalInteroperabilityRequirement - Organisational Interoperability Requirement - - ABB348 - - - - SemanticInteroperabilityRequirement - Semantic Interoperability Requirement - - ABB349 - - - - TechnicalInteroperabilityRequirement - Technical Interoperability Requirement - - ABB350 - - - - EifPrinciple - EIF Principle - - ABB300 - - - - - - - ArchitecturePrinciple - Architecture Principle - - ABB381 - - - - - - ArchitectureRequirement - Architecture Requirement - - ABB382 - - - - - - SolutionSpecification - Solution Specification - - ABB383 - - - - - - - - Deprecated - deprecated - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - PublicPolicyDevelopmentEnabler - Public Policy Development Enabler - - ABB167 - - true - - - DefinitionOfPublicPolicyObjectives - Definition of Public Policy Objectives - - ABB103 - - true - - - FormulationOfPublicPolicyScenarios - Formulation of Public Policy Scenarios - - ABB104 - - true - - - ImpactAssessment - Impact Assessment - - ABB105 - - true - - - PublicPolicyEvaluation - Public Policy Evaluation - - ABB107 - - true - - - PublicPolicyImplementation - Public Policy Implementation - - ABB106 - - true - - - PublicPolicyFormulationAndImplementationInstrument - Public Policy Formulation and Implementation Instrument - - ABB168 - - true - - - PublicPolicyImplementationMandate - Public Policy Implementation Mandate - + + -Mandate of the Directorate of Policy Planning of the Council of Europe -Directorate of Policy Planning (DPP). Overall mandate: to provide the Secretary General, the Committee of Ministers and Major Administrative Entities (MAEs) with conceptual and strategic analyses about relevant political and societal developments in Europe and beyond, based on research and on topical exchanges with internal and external networks, thereby enhancing the Organisation’s ability to anticipate major trends and challenges facing member states and to offer coherent short- and long-term responses within its statutory mandate. -https://www.coe.int/en/web/portal/organisation-and-mandates-of-the-secretariat?desktop=true + + ArtificialIntelligenceService + [ABB422] Artificial Intelligence Service + DESCRIPTION: +Shares the functionalities of appling advanced analysis and logic-based techniques, including machine learning, to interpret events, support and automate decisions, and take actions. -Mission statement of the Directorate-General for Taxation and the Customs Union -The Directorate General Taxation and Customs Union's mission is to develop and manage the Customs Union, a foundation of the European Union, and to develop and implement tax policy across the EU for the benefit of citizens, businesses and the Member States. Particular attention is given to the Internal Market, by making sure it functions smoothly and efficiently. -https://ec.europa.eu/taxation_customs/sites/taxation/files/resources/documents/common/about/welcome/mission_statement_en.pdf]]> - ABB112 - - true - - - FinancialResource - Financial Resource - - ABB116 - - true - - - ImplementingGuideline - Implementing Guideline - - ABB117 - - true - - - OrganisationalSkill - Organisational Skill - - ABB219 - - true - - - OrganisationalStructure - Organisational Structure - - ABB14 - - true - - - OrganisationalProcedure - Organisational Procedure - - ABB207 - - true - - - BusinessRule - Business Rule - - ABB16 - - true - - - Specification - Specification - - ABB163 - - true - - - OrganisationalPolicy - Organisational Policy - - ABB18 - - true - - - SecurityAndPrivacyPolicy - Security and Privacy Policy - - ABB222 - - true - - - OperationalEnabler - Operational Enabler - + + -An [Operational Enabler] is influenced by a [Public Policy Implementation Approach] and a [Public Policy Implementation Mandate] which determine the role of the organisation, person, object or event. -This role is determined by the following quadrant: + + ArtificialIntelligenceComponent + [ABB423] Artificial Intelligence Component + DESCRIPTION: +Implements the functionality of serving any current or future Digital Service Infrastructure (DSI) requiring artificial intelligence capabilities. It enables the implementation of functionalities for appling advanced analysis and logic-based techniques, including machine learning, to interpret events, support and automate decisions, and take actions. - | Public Policy Implementation Approach | - |___________________________________________| - | Top / Centralised | Down / Delegated | -______________________________________________________|______________________|____________________| - | | | | -Public | Strongly / Low Level Regulated | A | B | -Policy | ___________________________________| _____________________| ____________________| -Implementation | | | | -Mandate | Softly / High Level Regulated | C | D | -__________________| ___________________________________|______________________|____________________| +Source: https://www.gartner.com/en/information-technology/glossary/artificial-intelligence -Option A: Public Policy Implementation Mandate: Strongly / Low Level Regulated, Public Policy Implementation Approach: Top / Centralised -SETTING THE PUBLIC POLICY KEY IMPLEMENTATION IOP INSTRUMENTS (i.e. focus on data architecture like a base registry solution) - -Option B: Public Policy Implementation Mandate: Strongly / Low Level Regulated, Public Policy Implementation Approach: Down / Delegated -SETTING PUBLIC POLICY IMPLEMENTATION STANDARDS AND RULES (i.e. focus on technology architecture like eID tech specifications) - -Option C: Public Policy Implementation Mandate: Softly / High Level Regulated, Public Policy Implementation Approach: Top / Centralised -SETTING PUBLIC POLICY IMPLEMENTATION OBJECTIVES (i.e. focus on business architecture like a national interoperability strategy) - - -Option D: Public Policy Implementation Mandate: Softly / High Level Regulated, Public Policy Implementation Approach: Down / Delegated -SETTING PUBLIC POLICY IMPLEMENTATION FRAMEWORKS AND COLLABORATION PROTOCOLS CROSS THE DIFFERENT DELEGATION LEVELS (i.e. focus on application architecture like a national reference architecture) +INTEROPERABILITY SALIENCY: +IoP Dimension: Behavioral IoP +The Artificial intelligence Component ABB is salient for technical interoperability because it implements advanced analysis and logic-based techniques, including machine learning, to interpret events, support and automate decisions, and take actions. +EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): -The Customs 2020 Programme -Customs 2020 is an EU cooperation programme providing national customs administrations with the possibility to create and exchange information and expertise. It allows developing and operating major trans-European IT systems in partnership and establishing various human networks by bringing together national officials from across Europe. The programme has a budget of € 547.3 million and will run for 7 years from January 1 2014. -https://ec.europa.eu/taxation_customs/business/customs-cooperation-programmes/customs-2020-programme_en]]> - ABB166 - - true - - - OrganisationalInteroperabilityEnabler - Organisational Interoperability Enabler - + + -RAPEX - Semantic Web Gate -Public set of RAPEX notifications are available via the Semantic Web Gate in the Open Data portal -http://ec.europa.eu/semantic_webgate/query/dataset=rapex - -e-Justice Portal - Commission's approach on the security of communication and information systems in the European Commission -Commission Decision (EU, Euratom) 2017/46 of 10 January 2017 on the security of communication and information systems in the European Commission. The Commission's approach should take into account EU policy initiatives and legislation on network and information security, industry standards and good practices, to comply with all relevant legislation and to allow interoperability and compatibility. This decision applies to all communication and information systems (CISs) which are owned, procured, managed or operated by or on behalf of the Commission and all usage of those CISs by the Commission. -This decision sets out the basic principles, objectives, organisation and responsibilities regarding the security of those CISs, and in particular for Commission departments owning, procuring, managing or operating CISs and including CISs provided by an internal IT service provider. -http://eur-lex.europa.eu/legal-content/EN/TXT/?uri=uriserv:OJ.L_.2017.006.01.0040.01.ENG]]> - ABB171 - - true - - - CharacterEncodingScheme - Character Encoding Scheme - + SmartDevices + [ABB424] Smart Devices + DESCRIPTION: +Technological device means any computer, cellular phone, smartphone, digital camera, video camera, audio recording device, or other electronic device that can be used for creating, storing, or transmitting information in the form of electronic data. -Source: W3C -https://www.w3.org/TR/2003/WD-charmod-20030822/ - -The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): - -Unicode Transformation Format (UTF-8) - -ISO/IEC 10646-1 defines a large character set called the Universal Character Set (UCS) which encompasses most of the world's writing systems. The originally proposed encodings of the UCS, however, were not compatible with many current applications and protocols, and this has led to the development of UTF-8. -UTF-8 has the characteristic of preserving the full US-ASCII range, providing compatibility with file systems, parsers and other software that rely on US-ASCII values but are transparent to other values. -UTF-8 has a one-octet encoding unit. It uses all bits of an octet, but has the quality of preserving the full US-ASCII [US-ASCII] range: US-ASCII characters are encoded in one octet having the normal US-ASCII value, and any octet with such a value can only stand for a US-ASCII character, and nothing else. -UTF-8 encodes UCS characters as a varying number of octets, where the number of octets, and the value of each, depend on the integer value assigned to the character in ISO/IEC 10646 (the character number, a.k.a. code position, code point or Unicode scalar value). -https://tools.ietf.org/html/rfc3629]]> - ABB179 - - true - - - IdentifierScheme - Identifier Scheme - - ABB29 - - true - - - SchemaLevelMapping - Schema Level Mapping - - ABB212 - - true - - - SyntaxEncodingScheme - Syntax Encoding Scheme - - ABB184 - - true - - - DataLevelMapping - Data Level Mapping - - ABB180 - - true - - - PublicServiceComponent - Public Service Component - - ABB343 - - true - - - PublicServiceManifestation - Public Service Manifestation - - ABB342 - - true - - - DataStandard - Data Standard - - ABB183 - - true - - - DataStandardCatalogue - Data Standard Catalogue - - ABB211 - - true - - - TransactionalData - Transactional Data - + + -The following unit transactions are described: -• Issuance; -• Conversion; -• External Transfers; -• Cancellation (Internal Transfer); -• Replacement (Internal Transfer); -• Retirement (Internal Transfer); -• Carry-over; and -• Expiry Date Change. + + HighPerformanceInfrastructure + [ABB425] High Performance Infrastructure + DESCRIPTION: +Shares the functionalities, through the use of computer clusters, to create computing systems capable of delivering very high performance in the range of PetaFLOPS, typically using parallel computing. -http://unfccc.int/kyoto_protocol/registry_systems/itl/items/4065.php]]> - ABB185 - - true - - - BaseRegistryData - Base Registry Data - + + -The municipalities (and the Immigration Office for the last category of the population) are responsible for recording the information. As a pillar of e-government, the National Register ensures the sharing of authentic data identifying individuals between different public services with limited access to such data. The Sectorial Committee of the National Register established within the Commission for the Protection of Privacy is competent to authorize access to the information of the National Register or the communication thereof. -https://www.ehealth.fgov.be/fr/ehealthplatform]]> - ABB225 - - true - - - DescriptiveMetadata - Descriptive Metadata - + DataInfrastructure + [ABB426] Data Infrastructure + DESCRIPTION: +Shares the functionalities to enable data sharing and consumption through the use of static and dynamic data repositories, data lakes and data hubs. -Source: -http://www.niso.org/publications/press/UnderstandingMetadata.pdf +Source: Gartner INTEROPERABILITY SALIENCY: -The Descriptive Metadata ABB is salient for semantic interoperability because it facilitates opening and sharing data by providing the appropriate format, description of the content, high level of quality in order to achieve interoperability as stated in the EIF recommendation n° 42: "[..] Ensure that open data is accompanied by high quality, machine-readable metadata in non-proprietary formats, including a description of their content, the way data is collected and its level of quality and the licence terms under which it is made available. The use of common vocabularies for expressing metadata is recommended." +IoP Dimension: Structural IoP +The Data Hosting ABB is salient for technical interoperability because it provides all the functionalities to share and consume data. EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): -ISA2 Core Vocabularies - Core Criterion and Core Evidence Vocabulary - Evidence metadata -Evidences are resources and can have associated metadata. The DCMI Type Vocabulary can be used for providing a list of evidences that can be submitted for satisfying a specific criterion. -Note. Initially developed in 2002, the DCMI Type Vocabulary provides a general, cross-domain list of approved terms that may be used as values for the Type element to identify the genre of a resource. Type includes terms describing general categories, functions, genres, or aggregation levels for content. -https://joinup.ec.europa.eu/sites/default/files/distribution/2016-12/core_evidence_and_core_criterion_vocabulary_version_1.0.0.docx -http://dublincore.org/documents/dcmi-type-vocabulary/]]> - ABB195 - - true - - - MasterData - Master Data - + + -Source: DAMA DM_BOK -http://www.dama.org + + DataHub + [ABB427] Data Hub + DESCRIPTION: +A data hub is a collection of data from multiple sources organized for distribution, sharing, and often subsetting and sharing. Generally this data distribution is in the form of a hub and spoke architecture. INTEROPERABILITY SALIENCY: -The Master Data ABB is salient for semantic interoperability because it is used to establish the context for business transactions and transactional data by providing accurate data usually stored and available for reuse by other parties. Its management should be prioritised as stated in the EIF recommendation n° 31: "Put in place an information management strategy at the highest possible level to avoid fragmentation and duplication. Management of metadata, master data and reference data should be prioritised." +IoP Dimension: Structural IoP +The Data Hub ABBis salient for technical interoperability because it provides a single trustworthy location to store and access the data. EIF recommendation 37 "Make authoritative sources of information available to others while implementing access and control mechanisms to ensure security and privacy in accordance with the relevant legislation". EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): -INSPIRE code list register -The INSPIRE code list register contains the code lists and their values, as defined in the INSPIRE implementing rules on interoperability of spatial data sets and services (Commission Regulation (EU) No 1089/2010). -http://inspire.ec.europa.eu/codelist]]> - ABB181 - - true - - - OpenData - Open Data - + + -Source: EU Open Data guide -http://bookshop.europa.eu/en/eu-open-data-pbOA0416036/downloads/OA-04-16-036-EN-C/OA0416036ENC_002.pdf?FileName=OA0416036ENC_002.pdf&SKU=OA0416036ENC_PDF&CatalogueNumber=OA-04-16-036-EN-C + + DataLake + [ABB428] Data Lake + DESCRIPTION: +A data lake is usually a single store of data including raw copies of source system data, sensor data, social data etc., and transformed data used for tasks such as reporting, visualization, advanced analytics and machine learning. A data lake can include structured data from relational databases (rows and columns), semi-structured data (CSV, logs, XML, JSON), unstructured data (emails, documents, PDFs) and binary data (images, audio, video). A data lake can be established "on premises" (within an organization's data centers) or "in the cloud" (using cloud services from vendors such as Amazon, Microsoft, or Google). INTEROPERABILITY SALIENCY: -The Open Data ABB is salient for semantic interoperability because it is a part of the basic components of the EIF's conceptual model for integrated public services. Opening of public sector datasets for sharing and reuse is encouraged by the Directive on the reuse of public sector information, which provides a common legal framework for reuse of public sector data as stated in the EIF recommendation n° 2: "Publish the data you own as open data unless certain restrictions apply." +IoP Dimension: Structural IoP +The Data Lake ABBis salient for technical interoperability because it provides a single trustworthy location to store and access the data. EIF recommendation 37 "Make authoritative sources of information available to others while implementing access and control mechanisms to ensure security and privacy in accordance with the relevant legislation". EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): -European Data Portal -The European Data Portal harvests the metadata of Public Sector Information available on public data portals across European countries. Information regarding the provision of data and the benefits of re-using data is also included. - -Within the Portal, sections are dedicated to: -• Searching datasets: Categories have been established to structure the metadata harvested from the various countries. These categories follow the revision of the DCAT Application Profile and have been mapped against the Eurovoc Thesaurus. -• Providing Data: This section gives an insight into understanding Open Data from the perspective of a data provider. In addition, instructions are offered for those who wish their data portal to be harvested by the European Data Portal. -• Using Data: How Open Data is being used, as well as the economic benefits of Open Data are detailed in this section. -• Training and Library: eLearning modules about Open Data as well as training guides and a knowledge base referencing publications around Open Data and featured projects. - -Portals can be national, regional, local or domain specific. They cover the 28 EU Member States, EEA, countries involved in the EU's neighbourhood policy and Switzerland. -https://www.europeandataportal.eu/]]> - ABB224 - - true - - - ReferenceData - Reference Data - + + -Source: DAMA DM_BOK -http://www.dama.org - -Reference data consists typically of a small, discrete set of values that are not updated as part of business transactions but are usually used to impose consistent classification. Reference data normally has a low update frequency. Reference data is relevant across more than one business systems belonging to different organisations and sectors -[Source: J. Jordan & C. Ellen (2009). Business need, data and business intelligence]. + + DataRepositoryExchangeService + [ABB429] Data Repository Exchange Service + DESCRIPTION +Shares the functionalities of exchanging data structured under a source schema and transforming it into a target schema, so that the target data is an accurate representation of the source data. Data repository exchange service allows data to be shared between different application programs. INTEROPERABILITY SALIENCY: -The Reference Data ABB is salient for semantic interoperability because it can be shared and reused (e.g. in the form of taxonomies or controlled vocabularies) between organisation to agree on some basic information. Management of reference data is a priority as suggested by EIF's recommendation 31: "Put in place an information management strategy at the highest possible level to avoid fragmentation and duplication. Management of metadata, master data and reference data should be prioritised." +IoP Dimension: Structural IoP +The Data Repository Exchange Service ABB is salient for technical interoperability because it provides and shares the functionality for the share of data: "Legislation requires that decisions and data are stored and can be accessed for a specified time. This means that records and information in electronic form held by public administrations for the purpose of documenting procedures and decisions must be preserved and be converted, where necessary, to new media when old media become obsolete. The goal is to ensure that records and other forms of information keep their legibility, reliability and integrity and can be accessed as long as needed subject to security and privacy provisions." EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): -EUROSTAT - Nomenclature of Territorial Units for Statistics (NUTS) -Principle 1: Population thresholds -The NUTS regulation defines minimum and maximum population thresholds for the size of the NUTS regions: - -Level Minimum Maximum -NUTS 1 3 000 000 7 000 000 -NUTS 2 800 000 3 000 000 -NUTS 3 150 000 150 000 - -For administrative levels of NUTS, it is sufficient if the average size of the corresponding regions lies within the thresholds; in case of non-administrative levels, each individual region should do so. Exceptions exist however in case of geographical, socio-economic, historical, cultural or environmental circumstances. -Despite the aim of ensuring that regions of comparable size all appear at the same NUTS level, each level still contains regions which differ greatly in terms of population. -Principle 2: NUTS favours administrative divisions -For practical reasons the NUTS classification generally mirrors the territorial administrative division of the Member States. This supports the availability of data and the implementation capacity of policy. -Principle 3: Regular and extraordinary amendments -The NUTS classification can be amended, but generally not more frequently than every three years. The amendments are usually based on changes of the territorial structure in one or more Member States. -In case of a substantial reorganisation of the administrative structure of a Member State, amendments to the NUTS may be adopted at intervals of less than three years. This has only happened once so far, in 2014 for Portugal. -http://ec.europa.eu/eurostat/web/nuts/overview -http://ec.europa.eu/eurostat/web/nuts/principles-and-characteristics]]> - ABB27 - - true - - - BusinessIntelligenceComponent - Business Intelligence Component - - ABB66 - - true - - - BusinessAnalyticsService - Business Analytics Service - + + -KNIME® -KNIME® Analytics Platform is the leading open solution for data-driven innovation, helping discovering the potential hidden in data, mine for fresh insights, or predict new futures. This enterprise-grade, open source platform is scalable. KNIME Analytics Platform provides to data scientists more than 1000 modules, hundreds of ready-to-run examples, a comprehensive range of integrated tools, and a wide choice of advanced algorithms. + + DataRepositoryExchangeComponent + [ABB430] Data Repository Exchange Component + DESCRIPTION +Shares the functionalities of exchanging data structured under a source schema and transforming it into a target schema, so that the target data is an accurate representation of the source data. Data repository exchange component allows data to be shared between different application programs. -• Data Blending: simple text files, databases, documents, images, networks, and even Hadoop-based data can all be combined within the same visual workflow. -• Tool Blending: integration of more than a dozen tools, including legacy scripting/code, allows expertise to be reused, graphically documented, and shared among data scientists. -• Visual: easy-to-learn graphical interface means that coding is optional and work is visually documented. - -https://www.knime.com/knime-server]]> - ABB46 - - true - - - BusinessReportingService - Business Reporting Service - - ABB47 - - true - - - ConfigurationManagement - Configuration Management - + + -Based on ITIL v3 -https://www.axelos.com/Corporate/media/Files/Glossaries/AXELOS-Common-Glossary.pdf - -The following implementation are examples on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): - -Syn. [Distributed] Version Control, Source Code Management - -Quattor -Quattor is a system administration toolkit providing a powerful, portable, and modular set of tools for the automated installation, configuration, and management of clusters, farms, grids and clouds. Quattor is developed as a community effort and provided as open-source software under the Apache 2.0 license and EU DataGrid Software License. Quattor was originally developed in the framework of European Data Grid project. Since its first release in 2003, Quattor has been maintained and extended by a volunteer community of users and developers, primarily from the community of grid system administrators. Three features make it particularly attractive for managing grid resources: Federated Management, Shared Configuration and Management Efficiency, Coherent Site Model. -http://www.quattor.org/ - -Salt -Salt (also called SaltStack Platform) is a Python-based open-source configuration management software and remote execution engine supporting the "Infrastructure as code" approach to deployment and cloud management. SaltStack takes a new approach to infrastructure management by developing software that is easy enough to get running in seconds, scalable enough to manage tens of thousands of servers, and fast enough to control and communicate with them in milliseconds. SaltStack delivers a dynamic infrastructure communication bus used for orchestration, remote execution, configuration management and much more. The Salt Open project was launched in 2011 and is one of the fastest-growing, most-active infrastructure orchestration and configuration management open source project in the world. The SaltStack community is committed to keeping the Salt Open project focused, healthy and open. -https://saltstack.com/community/]]> - ABB127 - - true - - - ChoreographyService - Choreography Service - + IopSpecificationUnderpinningView + IOP specification underpinning View + + + + + + -A choreography can be distinguished from an orchestration. An orchestration defines the sequence and conditions in which one service invokes other services in order to realize some useful function. + + InteroperabilitySpecification + [ABB162] Interoperability Specification + DESCRIPTION: +An Interoperability Specification is a document of the highest possible level of granularity on an EIRA SBB, formulated as an agreed normative statement in design terms on a legal, organisational, semantic, or technical attribute of an European Public Service. It can refer to existing standards or specifications -Based on W3C -https://www.w3.org/TR/ws-arch/ +Source: ISA2 EIA Action -The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): +IoP dimensions: Structural IoP, Behavioral IoP, Governance IoP + + -Camunda -The core of Camunda BPM is a model execution engine that supports the OMG standards BPMN 2.0 for process automation, CMMN 1.1 for case management and DMN 1.1 for decision management. -Camunda BPM ships with a set of applications to help you model, execute and administer process applications running on the Camunda core engine. Those applications interact with the core engine's public REST API. You can also create your own applications that may also use the core engine's public Java API. It is lightweight and requires less than 3MB of disk space. It can run in any Java Virtual Machine (JVM) and comes with extended integration for different runtime containers. -The engine can be accessed via the REST API, or via the Java API and existing integrations with Spring and Java EE can be used. BPMN service tasks can be implemented in Java code, or the built-in REST and SOAP connectors can be used. Scripts, expressions and templates can also be applied for process implementation. Clustering for horizontal scalability is straightforward as the engine is stateless: multiple instances can share the same database. -BPMN 2.0 Processes permits the fully automated service orchestration and human workflow management. -https://camunda.org/features/]]> - ABB44 - - true - - - OperationalProcedure - Operational Procedure - - ABB126 - - true - - - BusinessProcessManagementComponent - Business Process Management Component - - ABB166 - - true - - - AdministrationComponent - Administration Component - - ABB139 - - true - - - AdministrationAndMonitoringService - Administration and Monitoring Service - - ABB137 - - true - - - AudiovisualService - Audiovisual Service - + LegalInteroperabilitySpecification + [ABB175] Legal Interoperability Specification + DESCRIPTION: +An Legal Interoperability Specification is a document of the highest possible level of granularity on an EIRA SBB, formulated as an agreed normative statement in design terms on a legal attribute of an European Public Service. It can refer to existing standards or specifications. -Source: ISA2 - EIA Action +Source: How does the EIRA support interoperability? +https://joinup.ec.europa.eu/sites/default/files/how_does_eira_support_interoperability_v1_0_0.pdf -Syn. Social Network +INTEROPERABILITY SALIENCY: +IoP Dimension: Structural IoP, Behavioral IoP, Governance IoP +The Legal Interoperability Specification ABB is relevant for interoperability a key interoperability enabler because it helps achieve legal interoperability by addressing the core legal interoperability background for solutions. +EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): -Avalon Media System -The Avalon Media System is an open source system for managing and providing access to large collections of digital audio and video. The freely available system enables libraries and archives to easily curate, distribute and provide online access to their collections for purposes of teaching, learning and research. The Avalon Community is made up of a dozen educational, media and open-technology institutions. -http://www.avalonmediasystem.org/project]]> - ABB54 - - true - - - CollaborationComponent - Collaboration Component - + + + + + OrganisationalInteroperabilitySpecification + [ABB176] Organisational Interoperability Specification + DESCRIPTION: +This aspect of interoperability is concerned with how organisations, such as public administrations in different Member States, cooperate to achieve their mutually agreed goals. In practice, organisational interoperability implies integrating business processes and related data exchange. Organisational interoperability also aims to meet the requirements of the user community by making services available, easily identifiable, accessible and user-focused. -Kune -Kune is a free and open source federated collaborative social network, focused on collaboration rather than just on communication. That is, it provides online real-time collaborative editing (based on Apache Wave), decentralized social networking and web publishing, while focusing on workgroups rather than individuals. It aims to allow the creation of online spaces for collaborative work, where organizations and individuals can build projects online, coordinate common agendas, set up virtual meetings, publish on the web, and join organizations with similar interests. Kune is 100% free software (AGPLv3), built with free tools. -https://github.com/comunes/kune]]> - ABB72 - - true - - - ContentManagementComponent - Content Management Component - - ABB75 - - true - - - ContentManagementService - Content Management Service - - ABB51 - - true - - - DocumentManagementService - Document Management Service - - ABB136 - - true - - - LifecycleManagementService - Lifecycle Management Service - - ABB138 - - true - - - LoggingService - Logging Service - - ABB59 - - true - - - LoggingComponent - Logging Component - - AB224 - - true - - - MessagingService - Messaging Service - + + + + + SemanticInteroperabilitySpecification + [ABB177] Semantic Interoperability Specification + DESCRIPTION: +Semantic interoperability enables organisations to process information from external sources in a meaningful manner. It ensures that the precise meaning of exchanged information is understood and preserved throughout exchanges between parties. In the context of the EIF, semantic interoperability encompasses the following aspects: + Semantic interoperability is about the meaning of data elements and the relationship between them. It includes developing vocabulary to describe data exchanges, and ensures that data elements are understood in the same way by communicating parties. + Syntactic interoperability is about describing the exact format of the information to be exchanged in terms of grammar, format and schemas. +Semantic interoperability specifications support semantic interoperability by addressing the core semantic interoperability background for solutions. -Source: ISA2 - EIA Action +Source: How does the EIRA support interoperability? +https://joinup.ec.europa.eu/sites/default/files/how_does_eira_support_interoperability_v1_0_0.pdf -Syn. Social Network +INTEROPERABILITY SALIENCY: +IoP Dimension: Structural IoP, Behavioral IoP, Governance IoP +The Semantic Interoperability Specification ABB is salient for semantic interoperability because it enables organisations to process information from external sources in a meaningful manner and ensuring that the precise meaning of exchanged information is understood and preserved throughout exchanges between parties as stated in the EIF recommendation n32: "Support the establishment of sector-specific and cross-sectoral communities that aim to create open information specifications and encourage relevant communities to share their results on national and European platforms." +EXAMPLES: The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): -HumHub User Mail System -HumHub is a free and open source social network software coded on top of the Yii PHP framework that provides an easy to use toolkit for creating and launching an own social network. The platform can be used for internal communication and collaboration that can range from a few users up to huge Intranets that serve companies with hundreds and thousands of employees. The platform was meant to be self-hosted and currently comes with pretty normal requirements, working with most shared hosting environments around. HumHub also supports themes and modules to extend the functionality for almost all requirements. -The user mail system module provides a private messaging system to communicate with one or more users. -https://github.com/humhub/humhub-modules-mail]]> - ABB53 - - true - - - PartnerManagementComponent - Partner Management Component - + + + + + TechnicalInteroperabilitySpecification + [ABB178] Technical Interoperability Specification + DESCRIPTION: +A specification contained in a document which lays down the characteristics required of a product such as levels of quality, performance, safety or dimensions, including the requirements applicable to the product as regards the name under which the product is sold, terminology, symbols, testing and test methods, packaging, marking or labelling and conformity assessment procedures. -OpenNebula -The OpenNebula monitoring subsystem gathers information relative to the hosts and the virtual machines, such as the host status, basic performance indicators, as well as VM status and capacity consumption. This information is collected by executing a set of static probes provided by OpenNebula. The information is sent according to the following process: each host periodically sends monitoring data to the front-end which collects it and processes it in a dedicated module. This model is highly scalable and its limit (in terms of number of VMs monitored per second) is bounded to the performance of the server running on and the database server. -OpenNebula also brings resource quota management to allocate, track and limit resource utilization/consumption. -https://opennebula.org/]]> - ABB141 - - true - - - PartnerManagementService - Partner Management Service - - ABB140 - - true - - - RecordManagementComponent - Record Management Component - + + + + + EiraOntologyViewpoint + EIRA Ontology Viewpoint + + + + + + + + + + + + + + + + + + + + + + + EiraViewpoint + [ABB333] EIRA Viewpoint + DESCRIPTION: +The EIRA provides several viewpoints (1) that conform to EIRA views. The viewpoints provide a perspective with specific stakeholders concern in mind. -The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): +(1) A specification of the conventions for a particular kind of architecture view. +Source: TOGAF +https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html#tag_03_18 + + + + + ArchitectureBuildingBlock + [ABB334] Architecture Building Block + DESCRIPTION: +An Architecture Building Block (ABB) is a constituent of the architecture model that describes a single aspect of the overall model. An Architecture Building Block describes generic characteristics and functionalities. Architecture Building Blocks are used to describe reference architectures, solution architecture templates or solution architectures of a specific solutions. -OpenKM -OpenKM is an Enterprise Document and Record Management System that has support for records management software. The file plan of OpenKM records management software specifies how records are to be organized once they have been created or received, provides a roadmap to the records created and maintained by an organizational unit, and facilitates dispositioning of the records. The file plan is created by detailing the file series of the records in your organizational unit, as well as information about how they are managed and by whom. -Features: -• File plan -o The file plan of OpenKM document management describes every type of records in the organization, the location where they should be stored, the rules applying to them, the retention schedule and timeline, manner of their disposition, and the person(s) responsible for their management. -• Inheritance -o OpenKM allows inheritance between file series. -• Security -o Set security by file series of the record. -• Record manager: -o Create your own dynamic logic for each file series, for example, based on metadata values, the file series can be promoted as "record" status. -• Search: -o Define common searches based on file series of record. -• Classification of business activities: -o Classification system reflect the business of the organization from which they derive and are normally based on an analysis of the organization's business activities. The system can be used to support a variety of records management processes. -• Catalogue: -o Create dynamic destinations based on record values. -o Dynamic wizard requiring the user for metadata values based on file series of the record (control of the creation). -• Disposition: -o Set retention schedule and period. -o Create dynamic disposition based on record values. -https://www.openkm.com/ - -ePHOENIX -epoline® PHOENIX (ePHOENIX) is a document and dossier management system designed to support the processes involved in the handling of Intellectual Property (IP)-related documents. -The system, which was developed by the European Patent Office, allows IP offices to manage application dossiers in electronic form. It provides a means for scanning all incoming documents and a user interface to display the resulting electronic dossier on screen, as well as supporting the printing and distribution of work. -ePHOENIX replaces physical paper files, thus removing the need for space-consuming archives and time-consuming transportation and management. Representing a further step towards the paperless office, the system improves efficiency and cost-effectiveness throughout the life-cycle of IP documents. -ePHOENIX is highly configurable. It provides tools and interfaces which allow existing IT systems, organisational structures, working procedures and conventions to be retained. This means minimal development costs, minimal risk and maximum user acceptance. Furthermore, it is a flexible Java-based system that can operate in a wide variety of IT architectures. -Thanks to its customisation possibilities, ePHOENIX can also be used to handle non-IP documents. -http://ephx.sourceforge.net/summary.html]]> - ABB76 - - true - - - RecordManagementService - Record Management Service - - ABB50 - - true - - - ConfigurationAndSolutionCartographyService - Configuration and Solution Cartography Service - + + + + + SolutionBuildingBlock + [ABB335] Solution Building Block + DESCRIPTION: +A Solution Building Block (SBB) is a candidate solution which conforms to the specification of an Architecture Building Block (ABB). -Source: ISA2 - EIA Action +Source: TOGAF +https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html#tag_03_70 + + -INTEROPERABILITY SALIENCY: -The Configuration and Solution of Cartography Service ABB  is salient for technical interoperability because it can be used to document the interoperabilty features of a solution or a set of solution/services. + + EiraView + [ABB336] EIRA View + The EIRA consists of several architecture views(1), including one view for each of the EIF interoperability levels. The EIRA views contain a graphical notation of the EIRA ontology. -EXAMPLES: -The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): +(1) An architecture view is a representation of a system from the perspective of a related set of concerns. +Source: TOGAF +https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap03.html#tag_03_17 + + + + + EiraArchitectureBuildingBlock + [ABB337] EIRA Architecture Building Block + DESCRIPTION: +An EIRA Architecture Building Block is a requirement of an intermediate level of granularity, in alignment with at least one EIF principle, formulated as an agreed normative statement in functional terms on a legal, organisational, semantic, or technical attribute of a To-Be European Public Service. An EIRA ABB might encapsulate several interoperability aspects + + + + + EiraSolutionBuildingBlock + [ABB338] EIRA Solution Building Block + DESCRIPTION: +An EIRA Solution Building Block is a concrete component of an intermediate level of granularity, that it implements one or more EIRA Architecture Building Blocks of an European Public Service, formulated as an agreed normative statement in design terms on a legal, organisational, semantic, or technical attribute of an European Public Service. On the technical view, a Solution Building Block is a specific software component that it might be either procured or developed of a To-Be Interoperable European Solution or that it is integrated in an As-Is Interoperable European Solution + + + + + Solution + [ABB339] Solution + DESCRIPTION: +A solution consists of one or more Solution Building Blocks to meet a certain stakeholder need. Within the context of the EIRA, a solution is usually an Interoperable European Solution developed by public administrations that facilitate the delivery of electronic Public Services and cross-border exchange of information between public administrations or Citizens in support to the implementation and advancement of EU, national or local public policies. -Essential -The EA Essential tool provides with a semantically-rich meta-model. This means accurate modelling which allows for sophisticated reporting. Essential can be configured to import data from a wide range of sources such as CMDBs, Business Process Modelling tools, PMO tools, etc. The Essential Import Utility REST API allows to schedule automated imports from external data sources to keep the repository accurate and current. Complex queries can be built on the repository using the query wizard in Essential Open Source. -In addition to traditional the Enterprise Architecture assets, Essential also manages information about the entire organization including resources, skills, contracts, risk, security and more. -https://www.enterprise-architecture.org/features.php]]> - ABB210 - - true - - - ConfigurationAndSolutionCartographyServiceComponent - Configuration and Solution Cartography Service Component - + + + + + EifInteroperabilityLevel + [ABB340] EIF Interoperability Level + DESCRIPTION: +The New European Interoperability Framework (EIF) is a set of guidelines for developing public services. The EIF defines four interoperability levels, which cover legal, organisational, semantic and technical interoperability. Each level deserves special attention when a new European public service is established. -Source: ISA2 - EIA Action +(1) European Commission, ISA Programme. The New European Interoperability Framework (EIF) for European public services. [Online] 2017. https://ec.europa.eu/isa2/eif_en. + + + + + PublicServiceAgent + [ABB341] Public Service Agent + + + + + + PublicServiceManifestation + [ABB342] Public Service Manifestation + A Public Service Manifestation is a behaviour EIRA Architecture Building Block, i.e. a unit of activity performed by one or more Public Service Components. + + + + + PublicServiceComponent + [ABB343] Public Service Component + A Public Service Component is a structural EIRA Architecture Building Block, i.e. an entity which can perform behaviour (active structure) or on which behaviour is performed (passive structure). + + + + + KeyInteroperabilityEnabler + [ABB344] Key Interoperability Enabler + DESCRIPTION: +A Key Interoperability Enabler is an EIRA Architecture Building Block, which is necessary to enable the efficient and effective delivery of public services across administrations. + + + + + InteroperabilityAspect + [ABB345] Interoperability Aspect + DESCRIPTION: +An Interoperability Aspect encapsulates a set of interoperability requirements to be provided/supported by an European Public Service + + + + + InteroperabilityRequirement + [ABB346] Interoperability Requirement + DESCRIPTION: +An Interoperability Requirement is requirement of the highest possible level of granularity for an EIRA ABB, formulated as an agreed normative statement in functional terms on a legal, organisational, semantic, or technical attribute of a To-Be European Public Service + + + + + LegalInteroperabilityRequirement + [ABB347] Legal Interoperability Requirement + A legal interoperability requirement is an interoperability requirement that must be met to help achieve legal interoperability. + + + + + OrganisationalInteroperabilityRequirement + [ABB348] Organisational Interoperability Requirement + An organisational interoperability requirement is an interoperability requirement that must be met to help achieve organisational interoperability. + + + + + SemanticInteroperabilityRequirement + [ABB349] Semantic Interoperability Requirement + A semantical interoperability requirement is an interoperability requirement that must be met to help achieve semantic interoperability. + + + + + TechnicalInteroperabilityRequirement + [ABB350] Technical Interoperability Requirement + A technical interoperability requirement is an interoperability requirement that must be met to help achieve technical interoperability. + + + + + EifPrinciple + [ABB300] EIF Principle + DESCRIPTION: +It is a requirement of the lowest possible level of granularity providing agreed orientation i) to analyse European public services by driving the identification and formulation of interoperability requirements with higher levels of granularity and ii) to design European public services by driving the identification and formulation of interoperability specifications -INTEROPERABILITY SALIENCY: -The Configuration and Solution of Cartography Component ABB  is salient for technical interoperability because it provides the implementation of the functionalities which can be exploited to document the interoperabilty features of a solution or a set of solution/services. +Source: The New EIF. https://ec.europa.eu/isa2/eif_en +The new European Interoperability Framework (EIF) is part of the Communication (COM(2017)134) from the European Commission adopted on 23 March 2017. The framework gives specific guidance on how to set up interoperable digital public services. + + + + + EiraOntologyViewpoint + EIRA Ontology viewpoint + + + + + + + ArchitecturePrinciple + [ABB381] Architecture Principle + DESCRIPTION: +Architecture Principles define the underlying general rules and guidelines for the use and deployment of all IT resources and assets across the enterprise. They reflect a level of consensus among the various elements of the enterprise, and form the basis for making future IT decisions. -EXAMPLES: -The following implementation is an example on how this specific Architecture Building Block (ABB) can be instantiated as a Solution Building Block (SBB): +Source: TOGAF 9.2 The Open Group +https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap20.html#:~:text=Architecture%20Principles%20define%20the%20underlying,for%20making%20future%20IT%20decisions. + + + + + ArchitectureRequirement + [ABB382] Architecture Requirement + DESCRIPTION: +A Architectrure Requirement is requirement of the highest possible level of granularity for an Architectural Building Block, formulated as an agreed normative statement of a To-Be European Public Service + + + + + SolutionSpecification + [ABB383] Solution Specification + DESCRIPTION: +An Architecture Specification is a document of the highest possible level of granularity on an Solution Building Block, formulated as an agreed normative statement in design of an European Public Service. + + + + + ArchitecturalPrincipleView + Architectural Principle View + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + EvidenceBasedPublicPolicy + [ABB409] Evidence based Public Policy + DESCRIPTION: +"Evidence-based Public Policies are policies designed and periodically reviewed looking at experimental evidences and incontrovertible data. +The primary goal is to improve the reliability of advice concerning the efficiency and effectiveness of policy settings and possible alternatives. +There are three crucial enabling factors that underpin modern conceptions of evidence-based policy (EBP): high-quality information bases on relevant topic areas, cohorts of professionals with skills in data analysis and policy evaluation, and political incentives for utilising evidence-based analysis and advice in governmental decision-making processes." + + + + + Transparency + [ABB410] Transparency + DESCRIPTION: +"Transparency in the EIF context refers to: +i. Enabling visibility inside the administrative environment of a public administration. This is about allowing other public administrations, citizens and businesses to view and understand administrative rules, processes,11 data, services and decision-making. +ii. Ensuring availability of interfaces with internal information systems. Public administrations operate a large number of what are often heterogeneous and disparate information systems in support of their internal processes. Interoperability depends on ensuring the availability of interfaces to these systems and the data they handle. In turn, interoperability facilitates reuse of systems and data, and enables these to be integrated into larger systems. +iii. Securing the right to the protection of personal data, by respecting the applicable legal framework for the large volumes of personal data of citizens, held and managed by Public administrations." + + + + + PublicValue + [ABB411] Public Value + DESCRIPTION: +Public values are rooted in a reciprocal relationship between administrators and the citizenry. Value is created by satisfying politically expressed desires of citizens and clients. A digital public service should create and deliver public value to the society. + + + + + SuccessfulPublicServiceImplementationOrientation + [ABB412] Successful Public Service Implementation Orientation + DESCRIPTION: +This refers to the implementation of the European interoperability framework, which is guided by the following vision: Public administrations should make implementation decisions selecting a focus among alternative implementation orientations and considering the best fit with the public policy context. Examples of resource based implementation orientations are the integration orientation, the technology orientation, the governance orientation, and the legal orientation. + + + + + SocialParticipation + [ABB413] Social participation + DESCRIPTION: +"Social participiation refers to Promoting Civic Participation and Transparency +of Government Decision-Making Processes covering policies concerning ICT: + E-democracy + E-participation + Government-to-citizen (G2C) Citizen-to-government (C2G) Citizen-to-citizen (C2C) + Open governance partnership Grass-root activism and social +networking + Political campaigns Online media + I-voting + Mechanisms: e-petitions, online consultation +and crowd-sourcing platforms etc." + + + + + Accountability + [ABB414] Accountability + DESCRIPTION: +"Digital public services will enable accountability of users and of public administrations. +Transparency, liability, controllability, responsibility, and responsiveness are defined as distinct dimensions of accountability, providing an improvement on the current state of conceptual fuzziness. The typology provides a vocabulary for the core argument, that conflicting expectations borne of disparate conceptions of accountability undermine organizational effectiveness." + + + + + MarketCollaboration + [ABB415] Market collaboration + DESCRIPTION: +"Digital public services will be designed and delivered considering partnership relationships with private sector. +Market Collaboration ensures efficient and effective use of resources, by seeking for reusable standards, that are open and supporting cost-effective interoperability between ICT capabilities and facilitate citizen-oriented business models" + + + + + DigitalInclusion + [ABB416] Digital Inclusion + DESCRIPTION: +Digital Inclusion relates to seamless, transparent, accessible and user-friendly digital government services. Citizens must be able to use such digital services without having legal knowledge. The members of our societies should have the opportunity to help shape the digital transformation and share their ideas and content with others unimpeded, while respecting the rights of third parties. The public sector should encourage such wider participation in policy-making by involving society in the design of public services through co-creation, ex- perimentation and collaboration. + + + + + Accessibility + [ABB403] Accessibility + DESCRIPTION: +Accessibility ensures that people with disabilities, the elderly and other disadvantaged groups can use public services at service levels comparable to those provided to other citizens. + + + + + EuropeanDigitalSovereignty + [ABB417] European digital sovereignty + DESCRIPTION: +European digital sovereignty entails the ensurance that all underlying digital components of ICT solutions (hardware, software, and services) meet European requirements, including the requirements to deploy a secure cloud infrastructure and interoperable services that fully comply with European legal provisions and ethical values. + + + + + EuLegislationCompliance + [ABB389] EU Legislation Compliance + DESCRIPTION: +"EU Legislation Compliance is the property of a (national/local) legislation to be coherent or to implement European legislation. +A compliance assessment of EU Directives must be carried out in two stages: +(1) timely and systematic check whether Member States have transposed Union law; +(2) a timely and systematic conformity check of national transposing measures against the relevant Union legislation (correct transposition). + +While Member States are responsible for the timely and accurate transposition of directives as well as the correct application of the entire acquis, the Commission has to monitor the Member States efforts and ensure that their legislation complies with Union law." + + + + + IntegratedHorizontalUserExperience + [ABB390] Integrated Horizontal User Experience + DESCRIPTION: +"Integrated horizontal user experience refers to a user's experience, when her/his experience using a digital interface is fluent and seamless, also when she/he navigates through different applications/contexts." + + + + + OnceOnly + [ABB391] Once Only + DESCRIPTION: +TheOnce Only Principle entails that citizens and businesses provide diverse data only once in contact with public administrations, while public administration bodies take actions to internally share and reuse these data even across borders always in respect of data protection regulations and other constraints. + + + + + CodeOfEthicsCompliance + [ABB392] Code of ethics compliance + DESCRIPTION: +Code of ethics compliance refers to the expression of important values and standards that are also to be found in the law, but are not encumbered by the limitations and constraints that necessarily attach to legally-binding rules that can be used to impose sanctions. + + + + + Privacy + [ABB393] Privacy + DESCRIPTION: +Privacy refers to any freely given, specific, informed and unambiguous indication of the data subject's wishes by which he or she, by a statement or by a clear affirmative action, signifies agreement to the processing of personal data relating to him or her + + + + + EulfCompliance + [ABB394] EULF compliance + DESCRIPTION: +"The EULF concept consists of a package of case studies, specifications, guidelines, training materials, recommendations and actions required by public administrations and stakeholder communities to facilitate the implementation, use and expansion of INSPIRE in an e-government context." + + + + + TechnologyNeutrality + [ABB395] Technology Neutrality + DESCRIPTION: +Technology Neutrality refers to the independency of specific technology choices, that therefore can operate on a variety of technology platforms + + + + + ServiceOrientation + [ABB386] Service Orientation + DESCRIPTION: +The design and implementation of sufficient mechanisms in order to attain full visibility on effective realisation of public services, based on public policies, by putting in place processes and procedures that provide accountability to stakeholders + + + + + Proactiveness + [ABB397] Proactiveness + DESCRIPTION: +"Proactiveness refers to proactive services, which are public services that a public institution delivers following its own initiative considering the presumable will by the person and that is delivered based on the information stored in the data collections belonging to the state information system. +Proactive service is based on life and business events and circumstances" + + + + + AdministrativeSimplification + [ABB388] Administrative Simplification + DESCRIPTION: +"Administrative Simplification refers to streamlined delivery services. e.g.: +- Harmonised rules on eligibility and durability +- Greater use of simplified costs +- Linking payments with results +- e-Cohesion +- Proportional approach to control +- Simplification of solutions" + + + + + NewPublicManagementApproach + [ABB400] New Public Management approach + DESCRIPTION: +"New Public Management arose out of a concern with government failures, a belief in the efficacy and efficiency of markets, a belief in economic rationality, and a push away from large, centralized government agencies toward devolution and privatization. +In New Public Management, public managers are urged to ""steer, not row."" They steer by determining objectives, or what should be done, and by catalyzing service delivery, or how it should be done (rowing), via their choice of a particular ""tool"" or combination of tools (e.g., markets, regulation, taxes, subsidies, insurance, etc.) for achieving the objectives (Salamon 200)" + + + + + ConvergenceAssuranceOnPublicPolicyGoalsAttainment + [ABB401] Convergence assurance on public policy goals attainment + DESCRIPTION: +The assessment of effective realisation of public services, based on public policies, by evaluating various technological solutions when striving to ensure the effectiveness and efficiency of a European public service. + + + + + Multilingulism + [ABB402] Multilingulism + DESCRIPTION: +Multilingualism requires striking a balance between the expectations of citizens and businesses to be served in their own language(s) or their preferred language(s) and the ability of Member States public administrations to offer services in all official EU languages + + + + + Openness + [ABB404] Openness + DESCRIPTION: +In the context of interoperable public services, the concept ofopennessmainly relates to data, specifications and software. + + + + + User-centricity + [ABB405] User-centricity + DESCRIPTION: +User-centricity refers to putting users needs at the centre when determining which public services should be provided and how they should be delivered. Therefore, as far as possible, user needs and requirements should guide the design and development of public services, in accordance with the following expectations: i A multi-channel service delivery approach; ii A single point of contact should be made available to users; iii Users feedback should be systematically collected, assessed and used to design new public services and to further improve existing ones. + + + + + Reusability + [ABB406] Reusability + DESCRIPTION: +"Reusability refers to IT solutions (e.g. software components, Application Programming Interfaces, standards), European frameworks (reference architectures, architectural frameworks and ontologies), information and data. +- Reference Architecture: Architecture is the structure of components, their interrelationships, and the principles and guidelines governing their design and evolution over time. A reference architecture is a generalized architecture of a solution, based on best-practices, domain neutral and, occasionally, with a focus on a particular aspect. The goal of a reference architecture is reusability; it reduces the amount of work, reduces errors and accelerates the development of solutions. A reference architecture should be based in a [reference] model and in a style. +- Architectural framework: a tool for assisting in the production of organization-specific architectures. An architectural framework consists of a technical reference model, a method for architecture development and a list of component standards, specifications, products and their interrelationships which can be used to build up architectures." + + + + + SubsidiarityAndProportionality + [ABB407] Subsidiarity and proportionality + DESCRIPTION: +Thesubsidiarity principlerequires EU decisions to be taken as closely as possible to the citizen + + + + + DataPortability + [ABB408] Data portability + DESCRIPTION: +Data portability refers to the ability to move and reuse data easily among different applications and systems, which becomes even more challenging in cross-border scenarios. + + + + + Security + [ABB385] Security + DESCRIPTION: +Security refers to the support of the application of the eGovernment security policies in ICT. The primary policies are: 1) Privacy by Design, 2) Encourage the development and use of highly secure systems (long-term), 3) Create stronger institutional supervision and oversight of security, 4) Substantiate the data minimization principle by using anonymization techniques in all European eGovernment systems, 5) Stimulate technical and legal solutions that avoid or limit privacy risks caused by re-identification of previously anonymized data, 6) Make Privacy Impact Assessments of eGovernment systems mandatory and public, 7) Use gateways to achieve interoperability of different national eGovernment security tools, but aim at Europe-wide availability and usability of tools, 7) Ensure open and transparent evaluations of the trade-offs between privacy, security, usability, interoperability and costs of an eGovernment system, 8) Develop a policy strategy for improving the security of IT-systems used in Europe + + + + + ConvergenceControlOnPublicPolicyGoalsAttainment + [ABB386] Convergence control on public policy goals attainment + DESCRIPTION: +The design and implementation of sufficient mechanisms in order to attain full visibility on effective realisation of public services, based on public policies, by putting in place processes and procedures that provide accountability to stakeholders + + + + + PreservationOfInformation + [ABB387] Preservation of information + DESCRIPTION: +Legislation requires that decisions and data are stored and can be accessed for a specified time. This means that records and information in electronic form held by public administrations for the purpose of documenting procedures and decisions must be preserved and be converted, where necessary, to new media when old media become obsolete + + + + + Trust + [ABB388] Trust + DESCRIPTION: +"Administrative Simplification refers to streamlined delivery services. e.g.: +- Harmonised rules on eligibility and durability +- Greater use of simplified costs +- Linking payments with results +- e-Cohesion +- Proportional approach to control +- Simplification of solutions" + + + + + Innovation + [ABB384] Innovation + DESCRIPTION: +Innovation entails rethinking organisations and processes, and changing behaviour so that public services are delivered more efficiently to people. Implemented well, eGovernment enables citizens, enterprises and organisations to carry out their business with government more easily, more quickly and at lower cost. + + -Essential -The EA Essential tool provides with a semantically-rich meta-model. This means accurate modelling which allows for sophisticated reporting. Essential can be configured to import data from a wide range of sources such as CMDBs, Business Process Modelling tools, PMO tools, etc. The Essential Import Utility REST API allows to schedule automated imports from external data sources to keep the repository accurate and current. Complex queries can be built on the repository using the query wizard in Essential Open Source. -In addition to traditional the Enterprise Architecture assets, Essential also manages information about the entire organization including resources, skills, contracts, risk, security and more. -https://www.enterprise-architecture.org/features.php]]> - ABB213 - - true - - diff --git a/tests/features/adms_ap_compliance.feature b/tests/features/adms_ap_compliance.feature index 061d6cc51e..effe907c37 100644 --- a/tests/features/adms_ap_compliance.feature +++ b/tests/features/adms_ap_compliance.feature @@ -37,9 +37,9 @@ Feature: Joinup should be ADMS-AP compliant. | state | validated | | featured | no | And the following solutions: - | title | collection | author | description | logo | banner | owner | contact information | creation date | modification date | documentation | content creation | keywords | landing page | language | metrics page | moderation | topic | related solutions | solution type | source code repository | spatial coverage | status | translation | webdav creation | webdav url | wiki | state | featured | pinned in | - | Early Omega | Morbid Scattered Microphone | Andre Munson |

content

| logo.png | banner.jpg | Teddy Bass | Jocelyn Bass | 2017-11-01T8:00 | 2017-12-01T8:43 | text.pdf | registered users | ADMS, validation | http://www.example.com/landing1 | Interlingua | http://www.example.org/metrics1 | no | EU and European Policies | | Service Delivery Model | http://www.example.org/source | Canada | Completed | | no | http://www.example.org/webdav | http://www.example.org/wiki | validated | no | | - | Snake Timely | Morbid Scattered Microphone | Branson Winthrop |

content

| logo.png | banner.jpg | Teddy Bass | Jocelyn Bass | 2015-03-03T8:00 | 2018-02-14T18:43 | text.pdf | registered users | | http://www.example.com/landing2 | English | http://www.example.org/metrics2 | yes | Demography | Early Omega | Business Information | http://www.example.org/source | Canada | Completed | | yes | http://www.example.org/webdav | http://www.example.org/wiki | validated | no | | + | title | collection | author | description | logo | banner | owner | contact information | creation date | modification date | documentation | content creation | keywords | landing page | language | metrics page | moderation | topic | related solutions | solution type | source code repository | spatial coverage | status | translation | webdav creation | webdav url | wiki | state | featured | pinned in | + | Early Omega | Morbid Scattered Microphone | Andre Munson |

content

| logo.png | banner.jpg | Teddy Bass | Jocelyn Bass | 2017-11-01T8:00 | 2017-12-01T8:43 | text.pdf | registered users | ADMS, validation | http://www.example.com/landing1 | Interlingua | http://www.example.org/metrics1 | no | EU and European Policies | | [ABB15] Service Delivery Model | http://www.example.org/source | Canada | Completed | | no | http://www.example.org/webdav | http://www.example.org/wiki | validated | no | | + | Snake Timely | Morbid Scattered Microphone | Branson Winthrop |

content

| logo.png | banner.jpg | Teddy Bass | Jocelyn Bass | 2015-03-03T8:00 | 2018-02-14T18:43 | text.pdf | registered users | | http://www.example.com/landing2 | English | http://www.example.org/metrics2 | yes | Demography | Early Omega | [ABB13] Business Information | http://www.example.org/source | Canada | Completed | | yes | http://www.example.org/webdav | http://www.example.org/wiki | validated | no | | And the following releases: | title | documentation | release number | release notes | creation date | is version of | state | status | spatial coverage | keywords | language | | Omega3 | text.pdf | 3.0.0 | New 3.0 | 2017-11-11T11:11 | Early Omega | validated | Completed | Andorra | food | Athapascan languages | diff --git a/tests/features/collection/collection_content.feature b/tests/features/collection/collection_content.feature index 96533539b8..8637f46ee8 100644 --- a/tests/features/collection/collection_content.feature +++ b/tests/features/collection/collection_content.feature @@ -51,7 +51,7 @@ Feature: Collection content | Name | Costas Papazoglou | | E-mail address | CostasPapazoglou@example.com | And I select "Data gathering, data processing" from "Topic" - And I select "Logging Service" from "Solution type" + And I select "[ABB58] Audit Service" from "Solution type" And I press "Add existing" at the "Owner" field And I fill in "Owner" with "Particle sweeper" And I press "Add owner" diff --git a/tests/features/joinup_core/reporting.feature b/tests/features/joinup_core/reporting.feature index 30a2366278..6daef461fe 100644 --- a/tests/features/joinup_core/reporting.feature +++ b/tests/features/joinup_core/reporting.feature @@ -44,10 +44,10 @@ Feature: | Monday's Artificial | validated | | Restless Burst | validated | And solutions: - | title | collection | state | creation date | modification date | solution type | - | Worthy Puppet | Monday's Artificial | validated | 2003-01-31T23:00 | 2015-12-07T13:57 | Interoperability Specification, Networking Service | - | Long Artificial | Restless Burst | validated | 2012-09-14T00:00 | 2012-12-04T16:19 | Data Set Catalogue | - | Beta Frozen | Restless Burst | validated | 2017-10-15T14:54 | 2017-11-24T12:43 | e-Signature Creation Service | + | title | collection | state | creation date | modification date | solution type | + | Worthy Puppet | Monday's Artificial | validated | 2003-01-31T23:00 | 2015-12-07T13:57 | [ABB162] Interoperability Specification, [ABB150] Networking Service | + | Long Artificial | Restless Burst | validated | 2012-09-14T00:00 | 2012-12-04T16:19 | [ABB24] Data Set Catalogue | + | Beta Frozen | Restless Burst | validated | 2017-10-15T14:54 | 2017-11-24T12:43 | [ABB55] e-Signature Creation Service | Given I am logged in as a moderator And I click "Reporting" in the "Administration toolbar" region diff --git a/tests/features/moderator/rdf_id_converter.feature b/tests/features/moderator/rdf_id_converter.feature index ca823ed8a6..c8c5441f49 100644 --- a/tests/features/moderator/rdf_id_converter.feature +++ b/tests/features/moderator/rdf_id_converter.feature @@ -11,9 +11,9 @@ Feature: Then I should see the heading "Convert an RDF entity ID" # Deliberately add a blank space in the beginning and the end of the URI to ensure trimming. - When I fill in "RDF entity ID or a URL" with " http://data.europa.eu/dr8/PublicServiceProvider " + When I fill in "RDF entity ID or a URL" with " http://data.europa.eu/dr8/PublicServiceProvider" And I press "Go!" - Then I should see the heading "Public Service Provider" + Then I should see the heading "[ABB174] Public Service Provider" Scenario Outline: Convert a URL of an entity. Given collections: diff --git a/tests/features/solution/about.feature b/tests/features/solution/about.feature index 07dd95d7ab..2f3e7a366f 100644 --- a/tests/features/solution/about.feature +++ b/tests/features/solution/about.feature @@ -23,21 +23,21 @@ Feature: About this solution | Polymer | validated | | Protein | proposed | And solution: - | title | Size exclusion chromatography | - | description | Separating molecules by size. | - | logo | logo.png | - | banner | banner.jpg | - | contact information | Ariel Lucile, "Maiken Bine, Peer Milla" | - | owner | Nova Pharmaceuticals, Senatier | - | state | validated | - | documentation | text.pdf | - | language | Italian, Kallawaya | - | topic | Demography, E-inclusion | - | related solutions | Gel, Polymer, Protein | - | solution type | Non-binding Instrument, Service Discovery Service | - | spatial coverage | Italy, Egypt | - | status | Under development | - | collection | Monoclonal Antibody Development | + | title | Size exclusion chromatography | + | description | Separating molecules by size. | + | logo | logo.png | + | banner | banner.jpg | + | contact information | Ariel Lucile, "Maiken Bine, Peer Milla" | + | owner | Nova Pharmaceuticals, Senatier | + | state | validated | + | documentation | text.pdf | + | language | Italian, Kallawaya | + | topic | Demography, E-inclusion | + | related solutions | Gel, Polymer, Protein | + | solution type | [ABB113] Non-binding Instrument, [ABB159] Service Discovery Service | + | spatial coverage | Italy, Egypt | + | status | Under development | + | collection | Monoclonal Antibody Development | # The link to the about page should be visible on the solution homepage. When I am not logged in diff --git a/tests/features/solution/add_solution.feature b/tests/features/solution/add_solution.feature index 9ceea19be0..4a1471883e 100644 --- a/tests/features/solution/add_solution.feature +++ b/tests/features/solution/add_solution.feature @@ -85,7 +85,7 @@ Feature: "Add solution" visibility options. # Regression test to endure that the language terms "Multilingual Code" are not present. And the available options in the "Language" select should not include the "Multilingual Code" And I should see the description "For best result the image must be larger than 2400x345 pixels." for the "Banner" field - And the "Solution type" field should contain the "IOP specification underpinning View, Legal View, Organisational View, deprecated" option groups + And the "Solution type" field should contain the "IOP specification underpinning View, Legal View, Organisational View" option groups When I fill in the following: | Title | Espresso is the solution | | Description | This is a test text | @@ -196,7 +196,7 @@ Feature: "Add solution" visibility options. | Title | PHP comments parser | | Description | A simple parser that goes through PHP comments. | And I select "Data gathering, data processing" from "Topic" - And I select "Implementing Guideline" from "Solution type" + And I select "[ABB30] Data Policy" from "Solution type" # Submit the incomplete form, so error messages about missing fields will # be shown. @@ -258,7 +258,7 @@ Feature: "Add solution" visibility options. | Name | Angela Crespi | | E-mail address | angela_crespi@glacmon.basel-uni.ch | And I select "Data gathering, data processing" from "Topic" - And I select "Logging Service" from "Solution type" + And I select "[ABB40] Data Transformation Service" from "Solution type" And I press "Add existing" at the "Owner" field And I fill in "Owner" with "University of Basel" And I press "Add owner" @@ -291,13 +291,13 @@ Feature: "Add solution" visibility options. | email | invisible.man@example.com | | name | Invisible Man | And the following solution: - | title | Cleaning solution | - | description | Use on metal surfaces. | - | owner | Organisation example | - | state | validated | - | solution type | Non-binding Instrument, Service Discovery Service | - | topic | Employment and Support Allowance | - | contact information | Invisible Man | + | title | Cleaning solution | + | description | Use on metal surfaces. | + | owner | Organisation example | + | state | validated | + | solution type | [ABB113] Non-binding Instrument, [ABB159] Service Discovery Service | + | topic | Employment and Support Allowance | + | contact information | Invisible Man | Given I am logged in as a moderator When I go to the edit form of the "Cleaning solution" solution diff --git a/tests/features/solution/homepage.feature b/tests/features/solution/homepage.feature index d3c51d3614..3de1816b67 100644 --- a/tests/features/solution/homepage.feature +++ b/tests/features/solution/homepage.feature @@ -89,8 +89,8 @@ Feature: Solution homepage | name | Geronimo | | email | geronimo@example.com | And the following solutions: - | title | description | logo | banner | state | owner | contact information | solution type | topic | - | Chiricahua Server | Serving the web | logo.png | banner.jpg | validated | Chiricahua Foundation | Geronimo | Business | E-inclusion | + | title | description | logo | banner | state | owner | contact information | solution type | topic | + | Chiricahua Server | Serving the web | logo.png | banner.jpg | validated | Chiricahua Foundation | Geronimo | [ABB169] Business | E-inclusion | # There should not be a pager when the solution is empty. When I go to the homepage of the "Chiricahua Server" solution Then I should not see the "Pager" region diff --git a/tests/features/solution/homepage_related_content.feature b/tests/features/solution/homepage_related_content.feature index 72d9f2b063..154db04002 100644 --- a/tests/features/solution/homepage_related_content.feature +++ b/tests/features/solution/homepage_related_content.feature @@ -12,9 +12,9 @@ Feature: Solution homepage | name | Placebo | | email | Placebo@example.com | And the following solutions: - | title | description | logo | banner | state | owner | contact information | solution type | topic | - | Information sharing protocol | Handling information sharing securely | logo.png | banner.jpg | validated | Kostas Agathe | Placebo | Business | E-inclusion | - | Security audit tools | Automated test of security | logo.png | banner.jpg | validated | Kostas Agathe | Placebo | Business | E-inclusion | + | title | description | logo | banner | state | owner | contact information | solution type | topic | + | Information sharing protocol | Handling information sharing securely | logo.png | banner.jpg | validated | Kostas Agathe | Placebo | [ABB169] Business | E-inclusion | + | Security audit tools | Automated test of security | logo.png | banner.jpg | validated | Kostas Agathe | Placebo | [ABB169] Business | E-inclusion | And the following releases: | title | release number | creation date | release notes | is version of | state | spatial coverage | | IS protocol paper | 1 | 2018-10-04 8:01am | First stable version. | Information sharing protocol | validated | Belgium | diff --git a/tests/features/solution/related_solution.feature b/tests/features/solution/related_solution.feature index a6e256accd..b1b0600dc5 100644 --- a/tests/features/solution/related_solution.feature +++ b/tests/features/solution/related_solution.feature @@ -11,13 +11,13 @@ Feature: Related solution | name | type | | Kalikatoures | Company, Industry consortium | And solutions: - | title | related solutions | description | documentation | related by type | moderation | logo | banner | topic | state | solution type | owner | contact information | - | C | | Blazing fast segmentation faults. | text.pdf | yes | no | logo.png | banner.jpg | Demography | validated | | Kalikatoures | Kalikatoura | - | Java | C | Because inheritance is cool. | text.pdf | yes | no | logo.png | banner.jpg | Demography | validated | Citizen | Kalikatoures | Kalikatoura | - | PHP | | Make a site. | text.pdf | yes | yes | logo.png | banner.jpg | Demography | validated | Citizen | Kalikatoures | Kalikatoura | - | Golang | | Concurrency for the masses | text.pdf | yes | yes | logo.png | banner.jpg | Demography | proposed | Citizen | Kalikatoures | Kalikatoura | - | Python | | Get stuff done. | text.pdf | yes | no | logo.png | banner.jpg | Demography | validated | | Kalikatoures | Kalikatoura | - | Javascript | Java | Java is related to javascript. Huh? | text.pdf | no | no | logo.png | banner.jpg | Demography | validated | Citizen | Kalikatoures | Kalikatoura | + | title | related solutions | description | documentation | related by type | moderation | logo | banner | topic | state | solution type | owner | contact information | + | C | | Blazing fast segmentation faults. | text.pdf | yes | no | logo.png | banner.jpg | Demography | validated | | Kalikatoures | Kalikatoura | + | Java | C | Because inheritance is cool. | text.pdf | yes | no | logo.png | banner.jpg | Demography | validated | [ABB8] Citizen | Kalikatoures | Kalikatoura | + | PHP | | Make a site. | text.pdf | yes | yes | logo.png | banner.jpg | Demography | validated | [ABB8] Citizen | Kalikatoures | Kalikatoura | + | Golang | | Concurrency for the masses | text.pdf | yes | yes | logo.png | banner.jpg | Demography | proposed | [ABB8] Citizen | Kalikatoures | Kalikatoura | + | Python | | Get stuff done. | text.pdf | yes | no | logo.png | banner.jpg | Demography | validated | | Kalikatoures | Kalikatoura | + | Javascript | Java | Java is related to javascript. Huh? | text.pdf | no | no | logo.png | banner.jpg | Demography | validated | [ABB8] Citizen | Kalikatoures | Kalikatoura | # Scenario A. A collection owner manages his own collection. When I visit the "Java" solution diff --git a/tests/features/solution/solution.edit.feature b/tests/features/solution/solution.edit.feature index ab1e1013d5..c065c3f09c 100644 --- a/tests/features/solution/solution.edit.feature +++ b/tests/features/solution/solution.edit.feature @@ -49,7 +49,7 @@ Feature: Solution editing. And I attach the file "banner.jpg" to "Banner" And I fill in "Language" with "http://publications.europa.eu/resource/authority/language/VLS" And I select "EU and European Policies" from "Topic" - And I select "Citizen" from "Solution type" + And I select "[ABB8] Citizen" from "Solution type" # Click the button to select an existing owner. And I press "Add existing" at the "Owner" field @@ -89,14 +89,14 @@ Feature: Solution editing. Scenario: A solution facilitator can edit only the solutions he's associated with. Given the following solution: - | title | Solution B | - | description | Second letter | - | logo | logo.png | - | banner | banner.jpg | - | contact information | Seward Shawn | - | owner | Acme inc. | - | state | validated | - | solution type | Citizen | + | title | Solution B | + | description | Second letter | + | logo | logo.png | + | banner | banner.jpg | + | contact information | Seward Shawn | + | owner | Acme inc. | + | state | validated | + | solution type | [ABB8] Citizen | When I am logged in as a facilitator of the "Solution B" solution And I go to the homepage of the "Solution B" solution Then I should see the link "Edit" diff --git a/tests/features/solution/solution.notifications.feature b/tests/features/solution/solution.notifications.feature index d3a9481f6a..56964a4e04 100644 --- a/tests/features/solution/solution.notifications.feature +++ b/tests/features/solution/solution.notifications.feature @@ -23,14 +23,14 @@ Feature: Solution notifications | Ramiro Myers | | Ramiro | Myers | ramiro.myers@example.com | | Edith Poole | | Edith | Poole | edith.poole@example.com | And the following solutions: - | title | author | description | logo | banner | owner | contact information | state | topic | solution type | collection | - | Solution notification to propose changes | Ramiro Myers | Sample text | logo.png | banner.jpg | Karanikolas Kitsos | Information Desk | validated | E-inclusion | Business | Collection of random solutions | - | Solution notification to blacklist | Ramiro Myers | Sample text | logo.png | banner.jpg | Karanikolas Kitsos | Information Desk | validated | E-inclusion | Business | Collection of random solutions | - | Solution notification to publish from blacklisted | Ramiro Myers | Sample text | logo.png | banner.jpg | Karanikolas Kitsos | Information Desk | blacklisted | E-inclusion | Business | Collection of random solutions | - | Solution notification to request changes | Ramiro Myers | Sample text | logo.png | banner.jpg | Karanikolas Kitsos | Information Desk | validated | E-inclusion | Business | Collection of random solutions | - | Solution notification to propose from request changes | Ramiro Myers | Sample text | logo.png | banner.jpg | Karanikolas Kitsos | Information Desk | needs update | E-inclusion | Business | Collection of random solutions | - | Solution notification to delete by moderator team | Ramiro Myers | Sample text | logo.png | banner.jpg | Karanikolas Kitsos | Information Desk | validated | E-inclusion | Business | Collection of random solutions | - | Solution notification to delete by owner | Ramiro Myers | Sample text | logo.png | banner.jpg | Karanikolas Kitsos | Information Desk | validated | E-inclusion | Business | Collection of random solutions | + | title | author | description | logo | banner | owner | contact information | state | topic | solution type | collection | + | Solution notification to propose changes | Ramiro Myers | Sample text | logo.png | banner.jpg | Karanikolas Kitsos | Information Desk | validated | E-inclusion | [ABB169] Business | Collection of random solutions | + | Solution notification to blacklist | Ramiro Myers | Sample text | logo.png | banner.jpg | Karanikolas Kitsos | Information Desk | validated | E-inclusion | [ABB169] Business | Collection of random solutions | + | Solution notification to publish from blacklisted | Ramiro Myers | Sample text | logo.png | banner.jpg | Karanikolas Kitsos | Information Desk | blacklisted | E-inclusion | [ABB169] Business | Collection of random solutions | + | Solution notification to request changes | Ramiro Myers | Sample text | logo.png | banner.jpg | Karanikolas Kitsos | Information Desk | validated | E-inclusion | [ABB169] Business | Collection of random solutions | + | Solution notification to propose from request changes | Ramiro Myers | Sample text | logo.png | banner.jpg | Karanikolas Kitsos | Information Desk | needs update | E-inclusion | [ABB169] Business | Collection of random solutions | + | Solution notification to delete by moderator team | Ramiro Myers | Sample text | logo.png | banner.jpg | Karanikolas Kitsos | Information Desk | validated | E-inclusion | [ABB169] Business | Collection of random solutions | + | Solution notification to delete by owner | Ramiro Myers | Sample text | logo.png | banner.jpg | Karanikolas Kitsos | Information Desk | validated | E-inclusion | [ABB169] Business | Collection of random solutions | When I am logged in as "Pat Harper" diff --git a/tests/features/solution/solution_moderation_integration.feature b/tests/features/solution/solution_moderation_integration.feature index e8480af976..07f1f950a2 100644 --- a/tests/features/solution/solution_moderation_integration.feature +++ b/tests/features/solution/solution_moderation_integration.feature @@ -16,12 +16,12 @@ Feature: As a user of the website | name | type | | Mr Crab | Private Individual(s) | And the following solutions: - | title | description | logo | banner | owner | contact information | solution type | state | topic | - | Professional Dreams | Azure ship | logo.png | banner.jpg | Mr Crab | Crusty crab | Business | draft | E-inclusion | - | The Falling Swords | The Falling Swords | logo.png | banner.jpg | Mr Crab | Crusty crab | Business | proposed | E-inclusion | - | Flight of Night | Rose of Doors | logo.png | banner.jpg | Mr Crab | Crusty crab | Business | validated | E-inclusion | - | Teacher in the Twins | The Guardian of the Stream | logo.png | banner.jpg | Mr Crab | Crusty crab | Business | needs update | E-inclusion | - | Missing Fire | Flames in the Swords | logo.png | banner.jpg | Mr Crab | Crusty crab | Business | blacklisted | E-inclusion | + | title | description | logo | banner | owner | contact information | solution type | state | topic | + | Professional Dreams | Azure ship | logo.png | banner.jpg | Mr Crab | Crusty crab | [ABB169] Business | draft | E-inclusion | + | The Falling Swords | The Falling Swords | logo.png | banner.jpg | Mr Crab | Crusty crab | [ABB169] Business | proposed | E-inclusion | + | Flight of Night | Rose of Doors | logo.png | banner.jpg | Mr Crab | Crusty crab | [ABB169] Business | validated | E-inclusion | + | Teacher in the Twins | The Guardian of the Stream | logo.png | banner.jpg | Mr Crab | Crusty crab | [ABB169] Business | needs update | E-inclusion | + | Missing Fire | Flames in the Swords | logo.png | banner.jpg | Mr Crab | Crusty crab | [ABB169] Business | blacklisted | E-inclusion | And the following solution user memberships: | solution | user | roles | | Flight of Night | Hulk | owner | diff --git a/tests/features/solution/solution_pager_regression.feature b/tests/features/solution/solution_pager_regression.feature index c8de29e025..634a1e018c 100644 --- a/tests/features/solution/solution_pager_regression.feature +++ b/tests/features/solution/solution_pager_regression.feature @@ -9,22 +9,22 @@ Feature: Test for a 'facets' regression on the solution overview page. | name | Pierre Plezant | | email | pierre.plezant@example.com | And the following solutions: - | title | description | logo | banner | state | owner | contact information | solution type | topic | - | Apache | Serving the web | logo.png | banner.jpg | validated | Apache Foundation | Pierre Plezant | Business | E-inclusion | - | Security audit tools | Automated test of security | logo.png | banner.jpg | validated | Apache Foundation | Pierre Plezant | Business | E-inclusion | - | Drupal | Content management | logo.png | banner.jpg | validated | Apache Foundation | Pierre Plezant | Business | E-inclusion | - | MongoDB | Free for all in box | logo.png | banner.jpg | validated | Apache Foundation | Pierre Plezant | Business | E-inclusion | - | NodeJS | Download all the packages | logo.png | banner.jpg | validated | Apache Foundation | Pierre Plezant | Business | E-inclusion | - | Solution 1 | More solution | logo.png | banner.jpg | validated | Apache Foundation | Pierre Plezant | Business | E-inclusion | - | Solution 2 | More solution | logo.png | banner.jpg | validated | Apache Foundation | Pierre Plezant | Business | E-inclusion | - | Solution 3 | More solution | logo.png | banner.jpg | validated | Apache Foundation | Pierre Plezant | Business | E-inclusion | - | Solution 4 | More solution | logo.png | banner.jpg | validated | Apache Foundation | Pierre Plezant | Business | E-inclusion | - | Solution 5 | More solution | logo.png | banner.jpg | validated | Apache Foundation | Pierre Plezant | Business | E-inclusion | - | Solution 6 | More solution | logo.png | banner.jpg | validated | Apache Foundation | Pierre Plezant | Business | E-inclusion | - | Solution 7 | More solution | logo.png | banner.jpg | validated | Apache Foundation | Pierre Plezant | Business | E-inclusion | - | Solution 8 | More solution | logo.png | banner.jpg | validated | Apache Foundation | Pierre Plezant | Business | E-inclusion | - | Solution 9 | More solution | logo.png | banner.jpg | validated | Apache Foundation | Pierre Plezant | Business | E-inclusion | - | Solution 10 | More solution | logo.png | banner.jpg | validated | Apache Foundation | Pierre Plezant | Business | E-inclusion | + | title | description | logo | banner | state | owner | contact information | solution type | topic | + | Apache | Serving the web | logo.png | banner.jpg | validated | Apache Foundation | Pierre Plezant | [ABB169] Business | E-inclusion | + | Security audit tools | Automated test of security | logo.png | banner.jpg | validated | Apache Foundation | Pierre Plezant | [ABB169] Business | E-inclusion | + | Drupal | Content management | logo.png | banner.jpg | validated | Apache Foundation | Pierre Plezant | [ABB169] Business | E-inclusion | + | MongoDB | Free for all in box | logo.png | banner.jpg | validated | Apache Foundation | Pierre Plezant | [ABB169] Business | E-inclusion | + | NodeJS | Download all the packages | logo.png | banner.jpg | validated | Apache Foundation | Pierre Plezant | [ABB169] Business | E-inclusion | + | Solution 1 | More solution | logo.png | banner.jpg | validated | Apache Foundation | Pierre Plezant | [ABB169] Business | E-inclusion | + | Solution 2 | More solution | logo.png | banner.jpg | validated | Apache Foundation | Pierre Plezant | [ABB169] Business | E-inclusion | + | Solution 3 | More solution | logo.png | banner.jpg | validated | Apache Foundation | Pierre Plezant | [ABB169] Business | E-inclusion | + | Solution 4 | More solution | logo.png | banner.jpg | validated | Apache Foundation | Pierre Plezant | [ABB169] Business | E-inclusion | + | Solution 5 | More solution | logo.png | banner.jpg | validated | Apache Foundation | Pierre Plezant | [ABB169] Business | E-inclusion | + | Solution 6 | More solution | logo.png | banner.jpg | validated | Apache Foundation | Pierre Plezant | [ABB169] Business | E-inclusion | + | Solution 7 | More solution | logo.png | banner.jpg | validated | Apache Foundation | Pierre Plezant | [ABB169] Business | E-inclusion | + | Solution 8 | More solution | logo.png | banner.jpg | validated | Apache Foundation | Pierre Plezant | [ABB169] Business | E-inclusion | + | Solution 9 | More solution | logo.png | banner.jpg | validated | Apache Foundation | Pierre Plezant | [ABB169] Business | E-inclusion | + | Solution 10 | More solution | logo.png | banner.jpg | validated | Apache Foundation | Pierre Plezant | [ABB169] Business | E-inclusion | And the following distribution: | title | Apache for MacOS | | description | Apache distribution | diff --git a/tests/features/solution/trr.feature b/tests/features/solution/trr.feature index eaca658263..0431035810 100644 --- a/tests/features/solution/trr.feature +++ b/tests/features/solution/trr.feature @@ -46,17 +46,17 @@ Feature: Creating a test (solution) in the TRR collection. # - Conformance Testing Service # - Conformance Testing Component # - Conformance Test Scenario - When I select "Conformance Testing Service" from "Solution type" + When I select "[ABB128] Conformance Testing Service" from "Solution type" Then the following fields should be visible "Test resource type, Actor, Business process, Product type, Standardization level" # TRR solutions have additional required fields. When I press "Propose" Then I should see the following error messages: - | error messages | - | The field Test resource type is required when Solution type is set to Conformance Testing Service. | - | The field Actor is required when Solution type is set to Conformance Testing Service. | - | The field Business process is required when Solution type is set to Conformance Testing Service. | - | The field Product type is required when Solution type is set to Conformance Testing Service. | - | The field Standardization level is required when Solution type is set to Conformance Testing Service. | + | error messages | + | The field Test resource type is required when Solution type is set to [ABB128] Conformance Testing Service. | + | The field Actor is required when Solution type is set to [ABB128] Conformance Testing Service. | + | The field Business process is required when Solution type is set to [ABB128] Conformance Testing Service. | + | The field Product type is required when Solution type is set to [ABB128] Conformance Testing Service. | + | The field Standardization level is required when Solution type is set to [ABB128] Conformance Testing Service. | # Fill in TRR specific data. When I select "Agent" from "Actor" @@ -67,21 +67,21 @@ Feature: Creating a test (solution) in the TRR collection. # "Test resource type" allowed values vary based on the solution type field. When I select "Test Suite" from "Test resource type" And I press "Propose" - Then I should see the error message 'Test resource type should be either "Test Bed", "Messaging Adapter" or "Document Validator" when solution type is set to "Test service" or "Conformance Testing Component".' - When I select "Test Scenario" from "Solution type" + Then I should see the error message 'Test resource type should be either "Test Bed", "Messaging Adapter" or "Document Validator" when solution type is set to "Test service" or "[ABB129] Conformance Testing Component".' + When I select "[ABB130] Conformance Test Scenario" from "Solution type" And I select "Messaging Adapter" from "Test resource type" And I press "Propose" - Then I should see the error message 'Test resource type should be either "Test Suite", "Test Case", "Test Assertion" or "Document Assertion Set" when solution type is set to "Conformance Test Scenario".' + Then I should see the error message 'Test resource type should be either "Test Suite", "Test Case", "Test Assertion" or "Document Assertion Set" when solution type is set to "[ABB129] Conformance Testing Component".' When I select "Test Suite" from "Test resource type" And I press "Propose" Then I should see the heading "Linked Open Data" Scenario: TRR distribution Given the following solution: - | title | TRR solution foo | - | description | The test repository | - | state | validated | - | solution type | Conformance Test Scenario | + | title | TRR solution foo | + | description | The test repository | + | state | validated | + | solution type | [ABB130] Conformance Test Scenario | And the following solution: | title | TRR solution bar | | description | The test repository | diff --git a/tests/features/taxonomy/eira.deprecated.feature b/tests/features/taxonomy/eira.deprecated.feature deleted file mode 100644 index 404a80ee34..0000000000 --- a/tests/features/taxonomy/eira.deprecated.feature +++ /dev/null @@ -1,33 +0,0 @@ -@api -Feature: - As a user of the website - When I go to the overview page of an EIRA term - I want to be able to see if a term is deprecated. - - Scenario: Show deprecated terms without replacement. - When I am logged in as a moderator - And I am on the homepage - And I click "RDF ID converter" - Then I should see the heading "Convert an RDF entity ID" - - When I fill in "RDF entity ID or a URL" with "http://data.europa.eu/dr8/ConfigurationManagement" - And I press "Go!" - Then I should see the heading "Configuration Management" - And I should see the warning message "This building block is deprecated, and should not be used in new development." - But I should not see the warning message containing "Consider using" - # Ensure caching. - When I reload the page - Then I should see the warning message "This building block is deprecated, and should not be used in new development." - But I should not see the warning message containing "Consider using" - - Scenario: Show deprecated terms with a replacement. - When I am logged in as a moderator - And I am on the homepage - And I click "RDF ID converter" - And I fill in "RDF entity ID or a URL" with "http://data.europa.eu/dr8/ReferenceData" - And I press "Go!" - Then I should see the heading "Reference Data" - And I should see the warning message "This building block is deprecated, and should not be used in new development. Consider using Data (http://data.europa.eu/dr8/Data) instead." - # Ensure caching. - When I reload the page - Then I should see the warning message "This building block is deprecated, and should not be used in new development. Consider using Data (http://data.europa.eu/dr8/Data) instead." diff --git a/tests/features/taxonomy/eira.description_format.feature b/tests/features/taxonomy/eira.description_format.feature index f1e4db8a2d..66b2371143 100644 --- a/tests/features/taxonomy/eira.description_format.feature +++ b/tests/features/taxonomy/eira.description_format.feature @@ -10,7 +10,7 @@ Feature: And I click "RDF ID converter" And I fill in "RDF entity ID or a URL" with "http://data.europa.eu/dr8/PublicPolicy" And I press "Go!" - Then I should see the heading "Public Policy" + Then I should see the heading "[ABB9] Public Policy" # The
tags are not part of the original description. And the response should contain "

DESCRIPTION:
" And the response should contain "

INTEROPERABILITY SALIENCY:
" diff --git a/tests/features/taxonomy/eira.related_terms.feature b/tests/features/taxonomy/eira.related_terms.feature index 408aa6d13c..42e50fab99 100644 --- a/tests/features/taxonomy/eira.related_terms.feature +++ b/tests/features/taxonomy/eira.related_terms.feature @@ -6,14 +6,12 @@ Feature: Scenario: Show related terms on the overview page. Given I am an anonymous user - When I go to the "Public Service Provider" term page - Then I should see the heading "Public Service Provider" - And I should see the following links: - | Citizen | - | Public Service Consumer | - | Public Service Delivery Agent | - | Service Delivery Model | - | Organisational Agreement | - | Semantic Agreement | - | Interoperable Digital Public Service | - | Technical Interoperability Agreement | + When I go to the "[ABB174] Public Service Provider" term page + Then I should see the heading "[ABB174] Public Service Provider" + And I should not see the following links: + | [ABB8] Citizen | + | [ABB5] Public Service Consumer | + | [ABB173] Public Service Delivery Agent | + | [ABB15] Service Delivery Model | + | [ABB374] Semantic Agreement | + | [ABB234] Technical Interoperability Agreement | diff --git a/web/modules/custom/joinup_communities/trr/src/Plugin/Validation/Constraint/SolutionTestResourceTypeConstraint.php b/web/modules/custom/joinup_communities/trr/src/Plugin/Validation/Constraint/SolutionTestResourceTypeConstraint.php index 2f0dc19e15..92244af435 100644 --- a/web/modules/custom/joinup_communities/trr/src/Plugin/Validation/Constraint/SolutionTestResourceTypeConstraint.php +++ b/web/modules/custom/joinup_communities/trr/src/Plugin/Validation/Constraint/SolutionTestResourceTypeConstraint.php @@ -28,13 +28,13 @@ class SolutionTestResourceTypeConstraint extends Constraint { * * @var string */ - public $invalidTestScenarioMessage = 'Test resource type should be either "Test Suite", "Test Case", "Test Assertion" or "Document Assertion Set" when solution type is set to "Conformance Test Scenario".'; + public $invalidTestScenarioMessage = 'Test resource type should be either "Test Suite", "Test Case", "Test Assertion" or "Document Assertion Set" when solution type is set to "[ABB129] Conformance Testing Component".'; /** * The violation message shown on wrong types for test services or components. * * @var string */ - public $invalidTestServiceOrComponentMessage = 'Test resource type should be either "Test Bed", "Messaging Adapter" or "Document Validator" when solution type is set to "Test service" or "Conformance Testing Component".'; + public $invalidTestServiceOrComponentMessage = 'Test resource type should be either "Test Bed", "Messaging Adapter" or "Document Validator" when solution type is set to "Test service" or "[ABB129] Conformance Testing Component".'; } diff --git a/web/modules/custom/joinup_core/joinup_core.deploy.php b/web/modules/custom/joinup_core/joinup_core.deploy.php index f60759fed0..3b612c22b3 100644 --- a/web/modules/custom/joinup_core/joinup_core.deploy.php +++ b/web/modules/custom/joinup_core/joinup_core.deploy.php @@ -13,3 +13,43 @@ */ declare(strict_types = 1); + +use Drupal\Core\Database\Database; +use Drupal\sparql_entity_storage\SparqlGraphStoreTrait; +use EasyRdf\Graph; + +/** + * Update the EIRA vocabulary. + */ +function joinup_core_deploy_0107400(array &$sandbox): void { + // Clean up the existing graph. + $sparql_connection = Database::getConnection('default', 'sparql_default'); + $sparql_connection->query('WITH DELETE { ?s ?p ?o } WHERE { ?s ?p ?o } '); + + $filepath = __DIR__ . '/../../../../resources/fixtures/EIRA_SKOS.rdf'; + $graph_store = SparqlGraphStoreTrait::createGraphStore(); + $graph = new Graph('http://eira_skos'); + $graph->parse(file_get_contents($filepath)); + $graph_store->insert($graph); + + // Repeat steps taken after importing the fixtures that target eira terms. + $sparql_connection->query('WITH INSERT { ?subject a skos:Concept } WHERE { ?subject a skos:Collection . };'); + $sparql_connection->query('WITH INSERT INTO { ?subject skos:topConceptOf } WHERE { ?subject a skos:Concept .};'); + $sparql_connection->query('WITH INSERT { ?member skos:broaderTransitive ?collection } WHERE { ?collection a skos:Collection . ?collection skos:member ?member };'); + + // There is one term removed and replaced. Update database records. + $graphs = [ + 'http://joinup.eu/solution/published', + 'http://joinup.eu/solution/draft', + ]; + + foreach ($graphs as $graph) { + $query = << +DELETE { ?entity_id } +INSERT { ?entity_id } +WHERE { ?entity_id } +QUERY; + $sparql_connection->query($query); + } +}