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

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.

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

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

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,24 +260,24 @@ 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
 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

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           |

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 ####

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)
 

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 <https://w3id.org/idsa/core/> 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

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.