From 5b0183b35b39d0be8657c20ff5f0a6a393aec0c9 Mon Sep 17 00:00:00 2001 From: tom-rm-meyer-ISST <116013795+tom-rm-meyer-ISST@users.noreply.github.com> Date: Wed, 25 Jan 2023 09:09:26 +0100 Subject: [PATCH] 213 Differentiate broker services and standardize (#214) * Differentiate broker services and standardize the term "metadata broker": - if "broker" only refer to metadata brokers, name it like that - if "broker" means multiple types of brokers (app, service, metadata - see 3.1.1. Roles in the IDS), name it "any broker", "broker service providers" or similar - if "data broker", name it "metadata broker" Note: Caps have been ignored (metadata broker, Metadata Broker) * Incorporated review by sebbader-sap * Rename lowercase metadata broker to uppercase Metadata Broker. Ommitted metadata brokerage and metadata brokering for uppercase --- ..._Goals_of_the_International_Data_Spaces.md | 4 +-- ...2_Purpose_and_Structure_of_the_document.md | 2 +- .../2_8_Blockchain.md | 2 +- .../3_1_1_Roles_in_the_IDS.md | 30 +++++++++---------- .../3_1_2_Interaction_of_Roles.md | 4 +-- .../3_2_FunctionalLayer.md | 10 +++---- .../3_2_Functional_Layer/README.md | 2 +- .../3_3_InformationLayer.md | 2 +- .../4_1_2_Identity_and_Trust_Management.md | 2 +- .../4_1_6_Usage_Control.md | 6 ++-- .../4_1_Security_Perspective/README.md | 2 +- .../4_2_4_Component_Certification.md | 4 +-- .../Core-Components-Certification.md | 6 ++-- .../Operational-Environment-Certification.md | 2 +- .../4_3_10_IDS_RuleBook.md | 2 +- .../4_3_11_Privacy_Perspective.md | 4 +-- .../4_3_1_Layers.md | 2 +- .../4_3_2_Data_Governance_Model.md | 10 +++---- .../4_3_7_Data_Quality.md | 2 +- .../4_3_Governance_Perspective/README.md | 2 +- 20 files changed, 50 insertions(+), 50 deletions(-) diff --git a/documentation/1_Introduction/1_1_Goals_of_the_International_Data_Spaces.md b/documentation/1_Introduction/1_1_Goals_of_the_International_Data_Spaces.md index 636e5f31..8594eb4e 100644 --- a/documentation/1_Introduction/1_1_Goals_of_the_International_Data_Spaces.md +++ b/documentation/1_Introduction/1_1_Goals_of_the_International_Data_Spaces.md @@ -80,7 +80,7 @@ requirements: is transferred to a trusted party. This approach requires a comprehensive description of each data source and the value and usability of data for other companies, combined with the ability to - integrate domain-specific data vocabularies. In addition, brokers in + integrate domain-specific data vocabularies. In addition, Metadata Brokers in the ecosystem provide services for real-time data search. - **Standardized interoperability**: The International Data Spaces @@ -101,7 +101,7 @@ requirements: of novel, data-driven services that make use of data apps. It also fosters new business models for these services by providing clearing mechanisms and billing functions, and by creating domain-specific - broker solutions and marketplaces. In addition, the International + metadata broker solutions and marketplaces. In addition, the International Data Spaces provides templates and other methodological support for participants to use when specifying usage restriction information and requesting legal information. diff --git a/documentation/1_Introduction/1_2_Purpose_and_Structure_of_the_document.md b/documentation/1_Introduction/1_2_Purpose_and_Structure_of_the_document.md index ffd4c884..c0027b76 100644 --- a/documentation/1_Introduction/1_2_Purpose_and_Structure_of_the_document.md +++ b/documentation/1_Introduction/1_2_Purpose_and_Structure_of_the_document.md @@ -6,7 +6,7 @@ data' , the IDS-RAM resides at a higher abstraction level than common architecture models of concrete software solutions do. The document provides an overview supplemented by dedicated architecture specifications defining the individual components of the International -Data Spaces (Connector, Broker, App Store, etc.) in detail. +Data Spaces (Connector, Metadata Broker, App Store, etc.) in detail. In compliance with common system architecture models and standards (e.g., ISO 42010, 4+1 view model), the Reference Architecture Model uses diff --git a/documentation/2_Context_of_the_International_Data_Spaces/2_8_Blockchain.md b/documentation/2_Context_of_the_International_Data_Spaces/2_8_Blockchain.md index f3ee8841..3d358f7f 100644 --- a/documentation/2_Context_of_the_International_Data_Spaces/2_8_Blockchain.md +++ b/documentation/2_Context_of_the_International_Data_Spaces/2_8_Blockchain.md @@ -49,7 +49,7 @@ hash code ('fingerprint' of a piece of data) which can be used to verify a larger file (e.g. a complex product design for which an order was sent) being shared with the help of an IDS Connector. In terms of the IDS-RAM, blockchain technology could be used for the Clearing House or -the Broker, for example (see Business Layer). +the Metadata Broker, for example (see Business Layer). In general, the use of Blockchain technology can ensure data consistency and transparency in combination with the general IDS approach for data diff --git a/documentation/3_Layers_of_the_Reference_Architecture_Model/3_1_Business_Layer/3_1_1_Roles_in_the_IDS.md b/documentation/3_Layers_of_the_Reference_Architecture_Model/3_1_Business_Layer/3_1_1_Roles_in_the_IDS.md index 12ba4e2a..bd0a91c8 100644 --- a/documentation/3_Layers_of_the_Reference_Architecture_Model/3_1_Business_Layer/3_1_1_Roles_in_the_IDS.md +++ b/documentation/3_Layers_of_the_Reference_Architecture_Model/3_1_Business_Layer/3_1_1_Roles_in_the_IDS.md @@ -72,7 +72,7 @@ of IDS RAM scope". The table below shows the basic roles defined in the IDS. | | **Create** | **Own** | **Certify / Verify** | **Publish** | **Provide** | **Consume | **Use** | **Delete** | |-----------------|:---------------------:|:------------------:|:--------------------:|:-----------------------:|:----------------------:|:-------------------:|:-----------------------:|:-------------------:| | **Connector** | Connector Creator | Connector Owner | Connector Certifier | Connector Publisher | Connector Provider | (Out of RAM scope) | Connector User | (Out of RAM scope) | -| **Data** | Data Creator | Data Owner | (Out of RAM scope) | Connector / Data Broker | Data Provider | Data Consumer | Data User | Data Eraser | +| **Data** | Data Creator | Data Owner | (Out of RAM scope) | Connector / Metadata Broker | Data Provider | Data Consumer | Data User | Data Eraser | | **Vocabulary** | Vocabulary Creator | Vocabulary Owner | (Out of RAM scope) | Vocabulary Publisher | Vocabulary Provider | Vocabulary Consumer | Vocabulary User | (Out of RAM scope) | | **Identity** | Identity Creator | Identity Owner | Identity Verificator | Identitiy Publisher | Identity Authenticator | (Out of RAM scope) | Identity User | Identity Eliminator | | **App** | App Creator | App Owner | App Certifier | App Broker | App Provider | App Consumer | App User | App Deleter (?) | @@ -96,7 +96,7 @@ more basic role. Their exact scope of comprised basic roles depends on the individual business model of the participant as individual business models (including pricing models) may be applied as deemed appropriate. E.g. a data intermediary (see details below) operating a data hub may -store data as a trustee, act as a broker or do both -- depending on the +store data as a trustee, act as a Metadata Broker or do both -- depending on the business model. Therefore, as the assignment of basic roles to a business role may vary, the assignment is marked with the following symbols: @@ -151,7 +151,7 @@ Payment Model, including the model for reuse of data by third parties. The **Data Provider** makes data technically available in the IDS for being transmitted to a Data Customer on behalf of the Data Owner. To -submit metadata to a Broker, or exchange data with a Data Consumer, the +submit metadata to a Metadata Broker, or exchange data with a Data Consumer, the Data Provider uses software components that are compliant with the Reference Architecture Model of the International Data Spaces. Compliant software is available from Software Developers and App Developers. @@ -223,14 +223,14 @@ pushes data directly to the Data Consumer. If the Data Customer searches for a type of data that is provided by many suppliers, .e.g. weather data, the Data Consumer can search for existing datasets by making an inquiry at a Data Intermediary that -assumes the basic role of a Data Broker (cf. according section below). -The Data Intermediary (Data Broker) then provides the required metadata +assumes the basic role of a Metadata Broker (cf. according section below). +The Data Intermediary (Metadata Broker) then provides the required metadata for the Data Consumer to connect to a Data Provider. Like a Data Provider, the Data Consumer may log the details of a successful (or unsuccessful) data exchange transaction at a Clearing House, use Apps to enrich, transform, etc. the data received, or use a -Data Broker to retrieve data sources. +Metadata Broker to retrieve data sources. #### CATEGORY 2: INTERMEDIARY ##### @@ -251,7 +251,7 @@ providing metadata, and creating a business model around their services. ##### Data Intermediary ##### The Data Intermediary is a platform operator that assumes mainly the -data-related basic roles Data Provider/Data Consumer and Data Broker. +data-related basic roles Data Provider/Data Consumer and Metadata Broker. Assuming the basic role of a **Data Provider** or **Data Consumer**, the Data Intermediary is responsible for the execution of the data exchange @@ -260,16 +260,16 @@ Consumer with data is, hence, the main activity of the Data Provider. To facilitate a data request from a Data Consumer, the Data Intermediary would provide a **Data Broker** with proper metadata about the data. -Acting as a Data Broker, the Data Intermediary stores and manages +Acting as a Metadata Broker, the Data Intermediary stores and manages information about the data sources available in the International Data -Spaces. An organization offering data brokering in the International +Spaces. An organization offering metadata brokering in the International Data Spaces may assume other intermediary basic roles at the same time (e.g. Service Broker, Clearing House or Identity Authority, see below). Assuming further basic roles consequently means additional tasks a participant has to execute. -The activities of the Data Broker mainly focus on receiving and -providing metadata. The Data Broker must provide an interface for Data +The activities of the Metadata Broker mainly focus on receiving and +providing metadata. The Metadata Broker must provide an interface for Data Creators to send their metadata. The metadata should be stored in an internal repository for being queried by Data Consumers in a structured manner. While the core of the metadata model must be specified by the @@ -277,7 +277,7 @@ International Data Spaces (i.e. by the Information Model, see [Information Layer](../3_3_Information_Layer/3_3_InformationLayer.md)), a Metadata Broker may extend the metadata model to manage additional metadata elements. -After the Data Broker has provided the Data Consumer with the metadata +After the Metadata Broker has provided the Data Consumer with the metadata about a certain Data Provider, it is not involved in the subsequent data exchange process. @@ -310,7 +310,7 @@ then operates the service on behalf of the owner. To allow other participants in the IDS to retrieve available services, Service Intermediaries may also assume the role of the **Service Broker**. The Service Broker provides metadata on present services in -the IDS analogously to the Data Broker. +the IDS analogously to the Metadata Broker. ##### APP STORE ##### @@ -325,7 +325,7 @@ by the App Creator that can, but does not have to be identical to the App Owner (cf. Data Owner/Creator above). The App Store is first responsible for managing information about apps. -This is the **Data Broker** role. The App Store should provide +This is the **Metadata Broker** role. The App Store should provide interfaces for publishing and retrieving apps plus corresponding metadata. In most cases, the App Store will, secondly, also assume the basic role of the **App Provider** as it is common for mobile phone app @@ -399,7 +399,7 @@ vocabulary to describe the vocabulary repository. The Clearing House is an intermediary that provides clearing and settlement services for all financial and data exchange transactions. In the International Data Spaces, clearing activities are separated from -broker services, since these activities are technically different from +any broker services, since these activities are technically different from maintaining a metadata repository. As already stated above, it might still be possible that the role Clearing House and other intermediary roles are assumed by the same organization, as both roles require acting diff --git a/documentation/3_Layers_of_the_Reference_Architecture_Model/3_1_Business_Layer/3_1_2_Interaction_of_Roles.md b/documentation/3_Layers_of_the_Reference_Architecture_Model/3_1_Business_Layer/3_1_2_Interaction_of_Roles.md index 571bba77..82ba6df2 100644 --- a/documentation/3_Layers_of_the_Reference_Architecture_Model/3_1_Business_Layer/3_1_2_Interaction_of_Roles.md +++ b/documentation/3_Layers_of_the_Reference_Architecture_Model/3_1_Business_Layer/3_1_2_Interaction_of_Roles.md @@ -26,13 +26,13 @@ Model. The table below gives an overview of possible (mandatory are marked with X or optional marked with (X)) interactions taking place in the IDS. -| | Data Owner | Data Provider | Data Consumer | Data User | Broker | Clearing House | Identity Provider | Service Provider | App Provider | App Store | Vocabulary Provider | Certification Body | Evaluation Facility | +| | Data Owner | Data Provider | Data Consumer | Data User | Metadata Broker | Clearing House | Identity Provider | Service Provider | App Provider | App Store | Vocabulary Provider | Certification Body | Evaluation Facility | |------------------------- |:----------: |:-------------: |:-------------: |:---------: |:------: |:--------------: |:-----------------: |:----------------: |:------------: |:---------: |:------------------: |:------------------: |:--------------------: | | **Data Owner** | - | X | - | - | - | (X) | - | (X) | (X) | (X) | (X) | - | (X) | | **Data Provider** | X | - | X | - | X | (X) | X | (X) | (X) | (X) | (X) | - | X | | **Data Consumer** | - | X | - | X | (X) | (X) | X | (X) | (X) | (X) | (X) | - | X | | **Data User** | - | - | X | - | - | (X) | - | (X) | (X) | (X) | (X) | - | (X) | -| **Broker** | - | (X) | (X) | - | - | - | X | (X) | - | - | ? | - | X | +| **Metadata Broker** | - | (X) | (X) | - | - | - | X | (X) | - | - | ? | - | X | | **Clearing House** | (X) | (X) | (X) | (X) | - | - | X | (X) | (X) | (X) | (X) | - | X | | **Identity Provider** | - | X | X | - | X | X | Federation | - | (X)? | (X)? | - | - | X | | **Service Provider** | (X) | (X) | (X) | (X) | (X) | (X) | - | - | (X) | (X) | (X) | - | X | diff --git a/documentation/3_Layers_of_the_Reference_Architecture_Model/3_2_Functional_Layer/3_2_FunctionalLayer.md b/documentation/3_Layers_of_the_Reference_Architecture_Model/3_2_Functional_Layer/3_2_FunctionalLayer.md index 3727e326..f72c81a4 100644 --- a/documentation/3_Layers_of_the_Reference_Architecture_Model/3_2_Functional_Layer/3_2_FunctionalLayer.md +++ b/documentation/3_Layers_of_the_Reference_Architecture_Model/3_2_Functional_Layer/3_2_FunctionalLayer.md @@ -82,7 +82,7 @@ is given in the [Security Perspective](../../4_Perspectives_of_the_Reference_Arc #### Trustworthy Communication & Security by Design #### -Connectors, App Stores, and Brokers can check if the Connector of the +Connectors, App Stores, and any Metadata Broker can check if the Connector of the connecting party is running a trusted (i.e. certified) software stack. Any communication between (external) Connectors can be encrypted and integrity protected. Each Data Owner and Data Provider must be able to @@ -111,7 +111,7 @@ the International Data Spaces is described on the Information Layer (see [section 3.3](../3_3_Information_Layer/3_3_InformationLayer.md)). The Ecosystem of Data group comprises three major aspects: data -source description, brokering, and vocabularies. +source description, metadata brokering, and vocabularies. #### Data Source Description #### @@ -124,15 +124,15 @@ the pricing model, and the usage policies regarding certain data. More information about data source description is given in the [Information Layer](../3_3_Information_Layer/3_3_InformationLayer.md). -#### Brokering #### +#### Metadata Brokering #### The operator of a Connector must be able to provide an interface for data and metadata access. Each Connector must be able to transmit -metadata of its data sources to one or more brokers. Each participant +metadata of its data sources to one or more Metadata Brokers. Each participant must be able to browse and search metadata in the metadata repository, provided the participant has the right to access the metadata. Furthermore, each participant must be able to browse the list of -participants registered at a broker. More information about brokering is +participants registered at a Metadata Broker. More information about metadata brokering is given in the [Process Layer](../3_4_Process_Layer/3_4_Process_Layer.md). #### Vocabularies #### diff --git a/documentation/3_Layers_of_the_Reference_Architecture_Model/3_2_Functional_Layer/README.md b/documentation/3_Layers_of_the_Reference_Architecture_Model/3_2_Functional_Layer/README.md index 11fe12e2..ca4bcbbf 100644 --- a/documentation/3_Layers_of_the_Reference_Architecture_Model/3_2_Functional_Layer/README.md +++ b/documentation/3_Layers_of_the_Reference_Architecture_Model/3_2_Functional_Layer/README.md @@ -26,7 +26,7 @@ [3.2.3.1 Data Source Description](./3_2_FunctionalLayer.md#data-source-description) -[3.2.3.2](./3_2_FunctionalLayer.md#brokering) +[3.2.3.2](./3_2_FunctionalLayer.md#metadata-brokering) [3.2.3.3 Vocabularies](./3_2_FunctionalLayer.md#vocabularies) diff --git a/documentation/3_Layers_of_the_Reference_Architecture_Model/3_3_Information_Layer/3_3_InformationLayer.md b/documentation/3_Layers_of_the_Reference_Architecture_Model/3_3_Information_Layer/3_3_InformationLayer.md index 8b77a171..56177079 100644 --- a/documentation/3_Layers_of_the_Reference_Architecture_Model/3_3_Information_Layer/3_3_InformationLayer.md +++ b/documentation/3_Layers_of_the_Reference_Architecture_Model/3_3_Information_Layer/3_3_InformationLayer.md @@ -72,7 +72,7 @@ specification of concepts envisaged by the Conceptual Representation, residing at the persistent namespace URI according to best practices for publishing linked data[^bp-ld]. Furthermore, it details and formally defines entities of the International Data Spaces in order to be able to share, search for, and -reason upon the structured metadata describing these entities. The IDS Vocabulary is defined using RDF Schema[^rdfs] and the OWL Web Ontology Language[^owl]; additionally, descriptions of Digital Resources can be validated against SHACL shapes[^shacl] that express syntactic and semantic conditions. Queries against, e.g., Data Resources listed in the Data Catalogue of a Connector or Broker, or against Software Resources available from an App Store, can be formulated in query languages such as SPARQL[^sparql]. Thus, the +reason upon the structured metadata describing these entities. The IDS Vocabulary is defined using RDF Schema[^rdfs] and the OWL Web Ontology Language[^owl]; additionally, descriptions of Digital Resources can be validated against SHACL shapes[^shacl] that express syntactic and semantic conditions. Queries against, e.g., Data Resources listed in the Data Catalogue of a Connector or Metadata Broker, or against Software Resources available from an App Store, can be formulated in query languages such as SPARQL[^sparql]. Thus, the Declarative Representation comprises a complete referential model allowing the derivation of a number of Programmatic Representations. The IDS Vocabulary is typically used and instantiated by knowledge engineers, ontology experts, or diff --git a/documentation/4_Perspectives_of_the_Reference_Architecture_Model/4_1_Security_Perspective/4_1_2_Identity_and_Trust_Management.md b/documentation/4_Perspectives_of_the_Reference_Architecture_Model/4_1_Security_Perspective/4_1_2_Identity_and_Trust_Management.md index 1d4191ad..40e433ac 100644 --- a/documentation/4_Perspectives_of_the_Reference_Architecture_Model/4_1_Security_Perspective/4_1_2_Identity_and_Trust_Management.md +++ b/documentation/4_Perspectives_of_the_Reference_Architecture_Model/4_1_Security_Perspective/4_1_2_Identity_and_Trust_Management.md @@ -16,7 +16,7 @@ In the IDS, each connector instance possesses it's own identity. Each connector The IDS Certification is explained in [Section 4.2](../4_2_Certification_Perspective/4_2_Certification_Perspective.md#certification-perspective). It is always conducted for a blueprint of the entire stack consisting of platform and Connector Core Services. Each such certified blueprint can be instantiated multiple times. -The IDS Connector identity serves to uniquely identify one such instance of the Connector Core Services with their IDS Apps on qualified platforms. The identity concept is equally used for other technical components such as Broker, DAPS, ... in the IDS which have their own Core Services (represented by one or multiple containers) running on a comparable platform. +The IDS Connector identity serves to uniquely identify one such instance of the Connector Core Services with their IDS Apps on qualified platforms. The identity concept is equally used for other technical components such as Broker Services, DAPS, ... in the IDS which have their own Core Services (represented by one or multiple containers) running on a comparable platform. One component always is characterized by the combination of platform and service instances. As an example, this Connector instance is running several data apps. The identity is comprised of the platform, the Connector Core Services and the deployed Data Apps. diff --git a/documentation/4_Perspectives_of_the_Reference_Architecture_Model/4_1_Security_Perspective/4_1_6_Usage_Control.md b/documentation/4_Perspectives_of_the_Reference_Architecture_Model/4_1_Security_Perspective/4_1_6_Usage_Control.md index 08c39fec..8f5b5cbb 100644 --- a/documentation/4_Perspectives_of_the_Reference_Architecture_Model/4_1_Security_Perspective/4_1_6_Usage_Control.md +++ b/documentation/4_Perspectives_of_the_Reference_Architecture_Model/4_1_Security_Perspective/4_1_6_Usage_Control.md @@ -82,9 +82,9 @@ Data Usage Control can be implemented by means of a machine-readable contract, w Usage Control is a cross-sectional concept and technology, which involves several IDS roles. -##### Meta Data Broker ##### +##### Metadata Broker ##### -The IDS Broker manages Connector self-descriptions that can contain usage policies. Therefore the Broker must be able to support usage policies. In addition the Connector self-description itself may be subject of usage policies. +The IDS Metadata Broker manages Connector self-descriptions that can contain usage policies. Therefore the Metadata Broker must be able to support usage policies. In addition the Connector self-description itself may be subject of usage policies. ##### Connector ##### @@ -104,7 +104,7 @@ For Data Apps to take advantage of Usage Control technology, App Providers need #### IDS Usage Control Language #### -The IDS Information Model is a modular meta-model (ontology) describing the capabilities of IDS infrastructure components, such as the Connector or the Data Endpoints. Descriptions of data provided by Data Endpoints are published at dedicated Broker registries, allowing potential Data Consumers to search for and identify data that is relevant (semantics) and applicable (quality) for their particular purpose, and to assess in advance data’s affordability (price) and usability (restrictions). +The IDS Information Model is a modular meta-model (ontology) describing the capabilities of IDS infrastructure components, such as the Connector or the Data Endpoints. Descriptions of data provided by Data Endpoints are published at dedicated Metadata Broker registries, allowing potential Data Consumers to search for and identify data that is relevant (semantics) and applicable (quality) for their particular purpose, and to assess in advance data’s affordability (price) and usability (restrictions). The IDS Usage Control Language refers to an extension of the Open Digital Rights Language ([ODRL](https://www.w3.org/community/odrl/)), a W3C standard. The Information Model’s Usage Control module uses this language to provide machine-readable specifications of Usage Control policies. These specifications define actions that a party is prohibited or permitted to operate with regard to a given data asset. In addition, they codify any potentially involved duties. Despite a simple core model, which is depicted in [Figure 4.1.6.4](#figure-4164-odrl-information-model), ODRL policies are a formal way to declaratively express Usage Control policies at a specification level. This way, the Information Model provides a technology-agnostic, consistent representation of policies across the International Data Spaces. diff --git a/documentation/4_Perspectives_of_the_Reference_Architecture_Model/4_1_Security_Perspective/README.md b/documentation/4_Perspectives_of_the_Reference_Architecture_Model/4_1_Security_Perspective/README.md index fb2d2ab6..1aa90e6c 100644 --- a/documentation/4_Perspectives_of_the_Reference_Architecture_Model/4_1_Security_Perspective/README.md +++ b/documentation/4_Perspectives_of_the_Reference_Architecture_Model/4_1_Security_Perspective/README.md @@ -73,7 +73,7 @@ [4.1.6.3 Roles involved in Usage Control](./4_1_6_Usage_Control.md#roles-involved-in-usage-control) -[4.1.6.3.1 Meta Data Broker](./4_1_6_Usage_Control.md#meta-data-broker) +[4.1.6.3.1 Meta Data Broker](./4_1_6_Usage_Control.md#metadata-broker) [4.1.6.3.2 Connector](./4_1_6_Usage_Control.md#connector) diff --git a/documentation/4_Perspectives_of_the_Reference_Architecture_Model/4_2_Certification_Perspective/4_2_4_Component_Certification.md b/documentation/4_Perspectives_of_the_Reference_Architecture_Model/4_2_Certification_Perspective/4_2_4_Component_Certification.md index 5d24f3c7..391be88b 100644 --- a/documentation/4_Perspectives_of_the_Reference_Architecture_Model/4_2_Certification_Perspective/4_2_4_Component_Certification.md +++ b/documentation/4_Perspectives_of_the_Reference_Architecture_Model/4_2_Certification_Perspective/4_2_4_Component_Certification.md @@ -7,7 +7,7 @@ Within the next two subsections, three different levels of assurance and trust f #### Component Assurance Levels: #### The depth and rigor of a component evaluation consists of the following three assurance levels, -independent on the type of component that is being certified (e.g. Connector, Broker, etc.): +independent on the type of component that is being certified (e.g. Connector, Metadata Brokers, etc.): * Assurance Level 1: Checklist self-assessment and automated interoperability testing * Assurance Level 2: External concept review including functional and security testing @@ -33,4 +33,4 @@ An in-depth description of the Component Certification and its Assurance and Tru #### Certification of other components #### -As the Broker, App Store, Clearing House, ParIS and Vocabulary Provider components are at their core also a Connector, the general certification process and assurance levels apply to them as well, in addition to component specific functional profiles. As an example for these profiles, the criteria catalogue "Components-Broker" can be requested on the [IDSA Homepage](https://internationaldataspaces.org/publications/white-papers/). +As the Metadata Broker, App Store, Clearing House, ParIS and Vocabulary Provider components are at their core also a Connector, the general certification process and assurance levels apply to them as well, in addition to component specific functional profiles. As an example for these profiles, the criteria catalogue "Components-Broker" can be requested on the [IDSA Homepage](https://internationaldataspaces.org/publications/white-papers/). diff --git a/documentation/4_Perspectives_of_the_Reference_Architecture_Model/4_2_Certification_Perspective/CertificationScheme/Core-Components-Certification.md b/documentation/4_Perspectives_of_the_Reference_Architecture_Model/4_2_Certification_Perspective/CertificationScheme/Core-Components-Certification.md index aedc1149..a10dd287 100644 --- a/documentation/4_Perspectives_of_the_Reference_Architecture_Model/4_2_Certification_Perspective/CertificationScheme/Core-Components-Certification.md +++ b/documentation/4_Perspectives_of_the_Reference_Architecture_Model/4_2_Certification_Perspective/CertificationScheme/Core-Components-Certification.md @@ -204,11 +204,11 @@ be ensured by independent evaluation and certification from an approved evaluation facility and the certification body of the Industrial Data Space. -#### Broker +#### Metadata Broker -A Broker service does not have access to primary data, but only to +A Metadata Broker service does not have access to primary data, but only to metadata provided by data providers, which is generally considered -less sensitive. Likewise, Broker services do not assign or enforce +less sensitive. Likewise, Metadata Broker services do not assign or enforce access rights, but merely support data exchange. Nevertheless, integrity and availability of metadata (i.e., correct and secure storing and handling of meta- data) is of high importance for the diff --git a/documentation/4_Perspectives_of_the_Reference_Architecture_Model/4_2_Certification_Perspective/CertificationScheme/Operational-Environment-Certification.md b/documentation/4_Perspectives_of_the_Reference_Architecture_Model/4_2_Certification_Perspective/CertificationScheme/Operational-Environment-Certification.md index edb4f314..48410d88 100644 --- a/documentation/4_Perspectives_of_the_Reference_Architecture_Model/4_2_Certification_Perspective/CertificationScheme/Operational-Environment-Certification.md +++ b/documentation/4_Perspectives_of_the_Reference_Architecture_Model/4_2_Certification_Perspective/CertificationScheme/Operational-Environment-Certification.md @@ -349,7 +349,7 @@ required to participate in the Industrial Data Space itself, it can outsource certain tasks, like publishing their data in the Industrial Data Space to a Service Provider hosting the required infrastructure. If this is the case, this Service Provider assumes the role of a Data -Provider, Data Consumer, Broker Ser- vice Provider, etc. and performs +Provider, Data Consumer, Broker Service Provider, etc. and performs the corresponding activities. They inherit the original role's responsibilities and risks, and shall therefore be subject to the corresponding requirements regarding certification. diff --git a/documentation/4_Perspectives_of_the_Reference_Architecture_Model/4_3_Governance_Perspective/4_3_10_IDS_RuleBook.md b/documentation/4_Perspectives_of_the_Reference_Architecture_Model/4_3_Governance_Perspective/4_3_10_IDS_RuleBook.md index b3fcf578..1b500463 100644 --- a/documentation/4_Perspectives_of_the_Reference_Architecture_Model/4_3_Governance_Perspective/4_3_10_IDS_RuleBook.md +++ b/documentation/4_Perspectives_of_the_Reference_Architecture_Model/4_3_Governance_Perspective/4_3_10_IDS_RuleBook.md @@ -121,7 +121,7 @@ e.g. the IDS standards and services. See attachment “Operational Agreements, L certification, onboarding, operation and usage. See attachment “Operational Agreements. Processes” Typical roles anticipated in an IDS based data driven continuum are described in more detail. Included -are Data Provider and Data Owner, Data Consumer, Data user, metadata Broker, Software-, Service- and +are Data Provider and Data Owner, Data Consumer, Data user, Metadata Broker, Software-, Service- and App-Provider, Appstore Provider, and basic roles like ID Provider, Certification Provider, Clearing House and Vocabulary Provider. diff --git a/documentation/4_Perspectives_of_the_Reference_Architecture_Model/4_3_Governance_Perspective/4_3_11_Privacy_Perspective.md b/documentation/4_Perspectives_of_the_Reference_Architecture_Model/4_3_Governance_Perspective/4_3_11_Privacy_Perspective.md index 4d85cdb4..3bfefa67 100644 --- a/documentation/4_Perspectives_of_the_Reference_Architecture_Model/4_3_Governance_Perspective/4_3_11_Privacy_Perspective.md +++ b/documentation/4_Perspectives_of_the_Reference_Architecture_Model/4_3_Governance_Perspective/4_3_11_Privacy_Perspective.md @@ -26,7 +26,7 @@ it’s protective power. Although TLS does protect data in transit in an efficient and widely accepted way, it is not the best measure in terms of privacy protection. E.g. scinetist were able to identify Google search queries from the size of data TLS protected data packets in the internet due to the still available metadata. The need for End2End encryption arises out of the privacy risks mentioned above. -As Intermediate broker / provider are able to see customer data, it is only prudent to encrypt the data in a way that allows +As intermediate (broker) service providers are able to see customer data, it is only prudent to encrypt the data in a way that allows the use for the primary purpose only. ##### Transport Layer Privacy / Source Anonymitiy ##### @@ -64,7 +64,7 @@ As set of encryption algorithms that allows a limited set of computations on the A more general term for any advanced encryption scheme. The required key size is usually larger, the possible applications have to be choosen from the variety of possible algorithms. e.g. proxy re-encryption allows to send a message to an intermediate -broker, but the message can be re-encrypted to a final recipient at a later point in time. +broker service, but the message can be re-encrypted to a final recipient at a later point in time. #### Minimum required risk mitigations #### diff --git a/documentation/4_Perspectives_of_the_Reference_Architecture_Model/4_3_Governance_Perspective/4_3_1_Layers.md b/documentation/4_Perspectives_of_the_Reference_Architecture_Model/4_3_Governance_Perspective/4_3_1_Layers.md index 523097ba..784cecff 100644 --- a/documentation/4_Perspectives_of_the_Reference_Architecture_Model/4_3_Governance_Perspective/4_3_1_Layers.md +++ b/documentation/4_Perspectives_of_the_Reference_Architecture_Model/4_3_Governance_Perspective/4_3_1_Layers.md @@ -8,7 +8,7 @@ International Data Spaces. It also specifies the roles within the IDS. Thereby, it is directly related to the Governance Perspective by considering the business point of view regarding data ownership, data provision, and data consumption, and by describing core service concepts -such as data brokerage. +such as metadata brokerage. #### Functional Layer #### diff --git a/documentation/4_Perspectives_of_the_Reference_Architecture_Model/4_3_Governance_Perspective/4_3_2_Data_Governance_Model.md b/documentation/4_Perspectives_of_the_Reference_Architecture_Model/4_3_Governance_Perspective/4_3_2_Data_Governance_Model.md index 0502b77d..4b54f2e0 100644 --- a/documentation/4_Perspectives_of_the_Reference_Architecture_Model/4_3_Governance_Perspective/4_3_2_Data_Governance_Model.md +++ b/documentation/4_Perspectives_of_the_Reference_Architecture_Model/4_3_Governance_Perspective/4_3_2_Data_Governance_Model.md @@ -11,7 +11,7 @@ what IDS components are involved. **DG/DM activities** - Define usage constraints for data resources -- Publish metadata including usage constraints to Broker +- Publish metadata including usage constraints to Metadata Broker - Transfer data with usage constraints linked to data - Receive information about data transaction from Clearing House - Bill data (if required) @@ -31,7 +31,7 @@ what IDS components are involved. **DG/DM activities** - Use data in compliance with usage constraints} -- Search for existing datasets by making an inquiry at a Broker Service Provider +- Search for existing datasets by making an inquiry at a ß Broker Service Provider - Nominate Data Users (if needed) - Receive information about data transaction from Clearing House - Monitor policy enforcement @@ -41,7 +41,7 @@ what IDS components are involved. - IDS Connector - Catalogue of rules to act in compliance with usage constraints specified by Data Owner -##### Meta Data Broker Service Provider ##### +##### Metadata Broker Service Provider ##### **DG/DM activities** @@ -50,7 +50,7 @@ what IDS components are involved. **Enabling/Supporting IDS Component:** -- Meta Data Broker Service Provider component +- Metadata Broker Service Provider component - Core of the metadata model must be specified by the International Data Spaces (by the Information Model) - Provide registration interface for Data Provider - Provide query interface for Data Consumer @@ -106,7 +106,7 @@ the IDS ecosystem. RACI stands for 'responsible' , lies on the 'R' and 'A' of the RACI matrix, supported by the notation 'S', which stands for supported. -| Activity | Data Owner / Data Provider | Data User / Data Consumer | Broker | Clearing House| +| Activity | Data Owner / Data Provider | Data User / Data Consumer | Metadata Broker | Clearing House| | :--- | :---: | :---: | :---: | :---: | | **Management** | | | | | | Determine data usage restrictions (execute data ownership rights)| R, A | - | S | - | diff --git a/documentation/4_Perspectives_of_the_Reference_Architecture_Model/4_3_Governance_Perspective/4_3_7_Data_Quality.md b/documentation/4_Perspectives_of_the_Reference_Architecture_Model/4_3_Governance_Perspective/4_3_7_Data_Quality.md index 5370eda6..27b33233 100644 --- a/documentation/4_Perspectives_of_the_Reference_Architecture_Model/4_3_Governance_Perspective/4_3_7_Data_Quality.md +++ b/documentation/4_Perspectives_of_the_Reference_Architecture_Model/4_3_Governance_Perspective/4_3_7_Data_Quality.md @@ -5,7 +5,7 @@ value of data as an economic good, the International Data Spaces explicitly addresses the aspect of data quality. Due to this premise, the International Data Spaces enables its participants to assess the quality of data sources by means of publicly available information and -the transparency it provides with regard to the brokerage functionality +the transparency it provides with regard to the metadata brokerage functionality it offers. Especially in competitive environments, this transparency may force Data Providers to take data maintenance more seriously. By extending the functionality of the Connector with self-implemented Data diff --git a/documentation/4_Perspectives_of_the_Reference_Architecture_Model/4_3_Governance_Perspective/README.md b/documentation/4_Perspectives_of_the_Reference_Architecture_Model/4_3_Governance_Perspective/README.md index 2dd5a0f8..b2ecf1c5 100644 --- a/documentation/4_Perspectives_of_the_Reference_Architecture_Model/4_3_Governance_Perspective/README.md +++ b/documentation/4_Perspectives_of_the_Reference_Architecture_Model/4_3_Governance_Perspective/README.md @@ -24,7 +24,7 @@ [4.3.2.1.2 Data Consumer](./4_3_2_Data_Governance_Model.md#data-consumer) -[4.3.2.1.3 Meta Data Broker Service Provider](./4_3_2_Data_Governance_Model.md#meta-data-broker-service-provider) +[4.3.2.1.3 MetaData Broker Service Provider](./4_3_2_Data_Governance_Model.md#metadata-broker-service-provider) [4.3.2.1.4 Clearing House](./4_3_2_Data_Governance_Model.md#clearing-house)