Merge branch 'main' into hotfix/update_modular_system

Author: ther3sa

docs/operating-model/how-data-space-governance/how-data-space-governance.md

@@ -15,7 +15,7 @@ However, this vision is complex: companies at various stages of the automotive v
 
 The standards of our Catena-X data ecosystem define how the exchange of data and information in our network works. They are the basis for ensuring that the technologies, components, policies, and processes used are developed and operated according to uniform rules. All standards developed for the Catena-X data ecosystem are based on the technological and industry-specific requirements of the automotive industry.
 
-The Catena-X Association publishes standards for generic core and enabling services as well as for domain-specific business applications (see KITs Chapter [KITs - Keep It Together](./../what-service-map/what-service-map.md#kits--keep-it-together)). These standards and artifacts form the basis for the development and operation of software components in the Catena-X network to ensure interoperability and data sovereignty between different software components and providers. All relevant standards are accessible in the [Catena-X standard library](https://catenax-ev.github.io/docs/standards/overview).
+The Catena-X Association publishes standards for generic core and enabling services as well as for domain-specific business applications (see KITs Chapter [KITs - Keep It Together](./../what-service-map/what-service-map.md#kits---keep-it-together)). These standards and artifacts form the basis for the development and operation of software components in the Catena-X network to ensure interoperability and data sovereignty between different software components and providers. All relevant standards are accessible in the [Catena-X standard library](https://catenax-ev.github.io/docs/standards/overview).
 
 ### How do we standardize?
 
@@ -45,7 +45,7 @@ An overview of the certification process is depicted in Figure [Catena-X Certifi
 As part of the certification, the data space participant commits to listing Catena-X solutions on the Catena-X Marketplace in accordance with the mandatory requirement of the Operating Model. This includes adherence to governance components such as Trust ID and related mechanisms. This requirement also applies retroactively to already onboarded partners. However, internal systems that are used solely within a company and are not intended for external provisioning do not require listing on a Catena-X marketplace. Catena-X does not allow the provision of solutions without a marketplace listing.
 For clarification: All solutions that exchange data within the Catena-X data space and pass it on to other Catena-X users must be certified. A list of all currently certified solutions can be made available through the association upon request. All commercial offers must be listed on a marketplace.
 
-The *Catena-X Conformity Assessment Handbook* provides a detailed description of how Catena-X conducts conformity assessment through the Conformity Assessment Bodies. The most current version can always be found on the [Catena-X Library](https://catenax-ev.github.io/docs/next/certification/certification).
+The *Catena-X Conformity Assessment Handbook* provides a detailed description of how Catena-X conducts conformity assessment through the Conformity Assessment Bodies. The most current version can always be found on the [Catena-X Library](https://catena-x.net/ecosystem/certification/).
 
 Prerequisite of any certification is the registration / onboarding of the participant who wants to get certified. The registration (see Chapter [Registration](./../how-data-space-operations/how-data-space-operations.md#registration)) is ideally done before any certification request or latest started with the start of the certification request.
 
@@ -89,7 +89,7 @@ If an company-internal business application meets either of these criteria, Cate
 #### 2. No Catena-X Business Applications without listing on a Certified Catena-X Marketplace
 
 Catena-X is built on trust. All Catena-X certified business applications and services must be listed on a certified Catena-X marketplace.
-Catena-X marketplace providers (i.e. CSP-A) verify that the listed business applications and services have a valid certification issued by a CAB and therefore comply with the Catena-X standards. As already mentioned in [How do we certify](https://catenax-ev.github.io/docs/next/operating-model/how-data-space-governance#why-do-we-certify), internal systems that are used solely within a company and are not intended for external provisioning do not require listing on a Catena-X marketplace. Catena-X does not allow the provision of solutions without a marketplace listing.
+Catena-X marketplace providers (i.e. CSP-A) verify that the listed business applications and services have a valid certification issued by a CAB and therefore comply with the Catena-X standards. As already mentioned in [How do we certify](./how-data-space-governance.md#how-do-we-certify), internal systems that are used solely within a company and are not intended for external provisioning do not require listing on a Catena-X marketplace. Catena-X does not allow the provision of solutions without a marketplace listing.
 
 In the future, there will be multiple CSP-As that enable business applications and services to be verified and listed on various marketplaces, as mentioned in chapter [Increase Decentralization of Core Services](./../outlook/outlook.md#increase-decentralization-of-core-services).
 
@@ -130,7 +130,7 @@ Certified operating companies are companies certified for operating core service
 **Certified Provider**  
 ![Certified Provider](./assets/[email protected])
 
-Certified Providers are companies that have been certified to deliver or operate services as defined in the [Service Map](https://catenax-ev.github.io/docs/next/operating-model/what-service-map) for the general participation in the data ecosystem depending on their role.
+Certified Providers are companies that have been certified to deliver or operate services as defined in the [Service Map](../what-service-map/what-service-map.md) for the general participation in the data ecosystem depending on their role.
 
 **Certified Solution**  
 ![Certified Solution](./assets/[email protected])
@@ -147,7 +147,7 @@ Different from Catena-X Certification, Catena-X qualification is a label held by
  Companies with more than 5 employees with this qualification may refer to their entire company as "Catena-X qualified" and will get the label "Qualified Advisory Provider". Alternatively, if more than 50% of a company's staff is qualified, it may equally refer to the entire company as "Catena-X qualified". Once a company meets the required number of qualified employees, it is automatically highlighted by Catena-X on the following list with an asterisk (*) and bold formatting: [Catena-X Qualified Advisor](https://catena-x.academy/catena-x-qualified-advisor/).
 To use the "Advisory Provider" logo, the company simply needs to contact the Catena-X Association and complete the corresponding application form.
 
-Any "Catena-X qualified" label has a validity of 12 months (for more details see [Qualification Process](https://catenax-ev.github.io/docs/next/operating-model/how-data-space-governance#qualification-process)).
+Any "Catena-X qualified" label has a validity of 12 months (for more details see [Qualification Process](./how-data-space-governance.md#qualification-process)).
 
 ### Scope of Labels (qualified/certified)
 
@@ -162,7 +162,7 @@ Any official Catena-X label can be downloaded from the [Catena-X repository](htt
 
 ## Regulatory Framework
 
-The Catena-X Regulatory Framework for data space operations outlines the non-technical requirements and responsibilities for all stakeholders involved in the Catena-X data ecosystem. It includes detailed information on data sovereignty, mandatory use case requirements, and other regulatory considerations that are relevant and mandatory to our activities. The Regulatory Framework is made up of individual components that each govern a specific layer of our data space operations. Find all the details about the Regulatory Framework [here](https://catenax-ev.github.io/docs/next/regulatory-framework/governance-framework).
+The Catena-X Regulatory Framework for data space operations outlines the non-technical requirements and responsibilities for all stakeholders involved in the Catena-X data ecosystem. It includes detailed information on data sovereignty, mandatory use case requirements, and other regulatory considerations that are relevant and mandatory to our activities. The Regulatory Framework is made up of individual components that each govern a specific layer of our data space operations. Find all the details about the Regulatory Framework [in this chapter](https://catenax-ev.github.io/docs/next/regulatory-framework/governance-framework).
 
 To understand the layers of our Regulatory Framework, Catena-X uses flight levels as a metaphor (see Figure Catena-X Governance Framework flight levels):
 

docs/operating-model/how-data-space-operations/how-data-space-operations.md

@@ -7,7 +7,7 @@ This chapter provides an overview of the key processes and compliance requiremen
 
 ## Onboarding Process
 
-The onboarding process consists of the (i) registration process and (ii) registration approval process and can be extended by the (iii) technical integration process in accordance with the CX-0006 standard (see Figure [Onboarding Process](./how-data-space-operations.md#general-onboarding)). To join the data space, all participants must complete the registration process. To exchange data with partners, participants must also complete the technical integration process and sign the General Data Exchange Framework.
+The onboarding process consists of the (i) registration process and (ii) registration approval process and can be extended by the (iii) technical integration process in accordance with the CX-0006 standard (see Figure [Onboarding Process](./how-data-space-operations.md#onboarding-process)). To join the data space, all participants must complete the registration process. To exchange data with partners, participants must also complete the technical integration process and sign the General Data Exchange Framework.
 
 ![Onboarding Process](./assets/onboarding-process.png)
 *Onboarding Process*
@@ -18,23 +18,23 @@ During the registration process, all participants must add their company data, s
 
 ### Registration Approval
 
-After confirmation, a BPNL (if not yet available) and an identity wallet with the "BPNL" and "Catena-X Membership" credentials are created by the CSP-B as part of the registration approval step. Each participant can collect their proof of identity, credentials and other verifiable information (e.g., roles, rights, services) in their identity wallet. The self-descriptions (SD) of newly registered legal entities and connectors are validated by the GXDCH (see Chapter [Gaia-X Compliance](./how-data-space-operations.md#gaia-x-compliance)). This includes the signing and issuing of credentials to the identity wallet of a DPC, providing proof of Gaia-X compliance and notarization of the legal entity.
+After confirmation, a BPNL (if not yet available) and an identity wallet with the "BPNL" and "Catena-X Membership" credentials are created by the CSP-B as part of the registration approval step. Each participant can collect their proof of identity, credentials and other verifiable information (e.g., roles, rights, services) in their identity wallet. The self-descriptions (SD) of newly registered legal entities and connectors are validated by the Digital Clearing House (see Chapter [Clearing House as a trust anchor](./how-data-space-operations.md#clearing-house-as-a-trust-anchor)). This includes the signing and issuing of credentials to the identity wallet of a DPC, providing proof of Gaia-X compliance and notarization of the legal entity.
 
 ### Technical Integration
 
-After registration, participants can start the technical integration process (e.g., create technical users, regsiter connectors) to enable technical interaction with other participants. The technical user enables a company to link their connectors to its identity wallet. The connector registration is required to ensure that a connector can be searched and discoverd by other participants within the data space.
+After registration, participants can start the technical integration process (e.g., create technical users, regsiter connectors) to enable technical interaction with other participants. The technical user enables a company to link their connectors to its identity wallet. The connector registration is required to ensure that a connector can be searched and discovered by other participants within the data space.
 
 ### Managing Company Hierarchies
 
-After successful registration, participants can create and manage their company hierarchies. Catena-X Business Partner Data Management allows you to create and manage sites and additional addresses for your legal entities. In a future version, it will also be possible to create and manage relationships between two legal entities (e.g., subsidiaries). This is relevant, for example, for the various connector usage scenarios as described [here](https://catenax-ev.github.io/docs/next/operating-model/how-data-space-operations#edc-deployment-and-usage-premises).
+After successful registration, participants can create and manage their company hierarchies. Catena-X Business Partner Data Management allows you to create and manage sites and additional addresses for your legal entities. In a future version, it will also be possible to create and manage relationships between two legal entities (e.g., subsidiaries). This is relevant, for example, for the various connector usage scenarios as described in chapter [EDC Deployment and Usage Premises](./how-data-space-operations.md#edc-deployment-and-usage-premises).
 
 ## Clearing House as a trust anchor
 
 The Digital Clearing House, currently the Gaia-X Digital Clearing House (GXDCH), is an external service that maximizes trust within the Catena-X data space, and data space interoperability with other initiatives based on the (Gaia-X) Trust Framework. The Clearing House enables the validation of legal entities, ensures Gaia-X compliance, and creates an eIDAS conform digital signature (self-description) for all data space participants. There is one GXDCH provider for the Catena-X data space, which is nominated and managed by the Catena-X Association. To ensure compliance with the Catena-X onboarding process, the CSP-B must connect to the GXDCH.
 
 ## Implementation of the Self Sovereign Identity Concept
 
-Self-Sovereign Identity (SSI) is the next step beyond user-centric identity, and that means it begins at the same place: the user must be central to the administration of identity. That requires not just the interoperability of a user's identity across multiple locations, with the user's consent, but also true user control of that digital identity, creating user autonomy. In Catena-X there are several different components to implement the SSI approach. This includes the Issuer Component and the BPN DID Resolution Service (BDRS) which is currently classified as Core Service B due to the current state of our technical architecture, and is accordingly also managed by the CSP-B. In addition to the Issuer Component, the CSP-B also operates an Identity Wallet and the Authority Schema Registry. The Authority Schema Registry is managed by the Catena-X Association, which has nominated and commissioned the CSP-B to operate this service. To enable a stable and secure operation, the CSP-B can put the schemas in a dedicated repository. The CSP-B must use the currently operational version in the Catena-X data space. All the components can be seen in the Service Map (see Chapter [What: Service Map](./../what-service-map/what-service-map.md)) This concept will evolve in future releases, the details of which can be found in Chapter [Further Integration of SSI Technologies](./../outlook/outlook.md#further-integration-of-ssi-technologies).
+Self-Sovereign Identity (SSI) is the next step beyond user-centric identity, and that means it begins at the same place: the user must be central to the administration of identity. That requires not just the interoperability of a user's identity across multiple locations, with the user's consent, but also true user control of that digital identity, creating user autonomy. In Catena-X there are several different components to implement the SSI approach. This includes the Issuer Component and the BPN DID Resolution Service (BDRS) which is currently classified as Core Service B due to the current state of our technical architecture, and is accordingly also managed by the CSP-B. In addition to the Issuer Component, the CSP-B also operates an Identity Wallet and the Authority Schema Registry. The Authority Schema Registry is managed by the Catena-X Association, which has nominated and commissioned the CSP-B to operate this service. To enable a stable and secure operation, the CSP-B can put the schemas in a dedicated repository. The CSP-B must use the currently operational version in the Catena-X data space. All the components can be seen in the Service Map (see Chapter [What: Service Map](./../what-service-map/what-service-map.md)) This concept will evolve in future releases, the details of which can be found in Chapter [Further Integration of SSI Technologies](./../outlook/outlook.md#further-integration-of-self-sovereign-identity).
 
 ## Data Exchange based on SSI