Skip to content

Commit 3b095e6

Browse files
committed
fix broken links in Jupiter
1 parent 3a106df commit 3b095e6

File tree

4 files changed

+7
-7
lines changed

4 files changed

+7
-7
lines changed

versioned_docs/version-Jupiter/operating-model/how-data-space-governance/how-data-space-governance.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ The Catena-X Association publishes standards for generic core and enabling servi
1919

2020
### How do we standardize?
2121

22-
Based on [Catena-X’s Intellectual Property(IP)-Regulations](https://catena-x.net/fileadmin/user_upload/Vereinsdokumente/Catena-X_IP_Regelwerk_IP_Regulations.pdf) and in compliance with applicable antitrust law, the Catena-X standardization process aims to develop and implement uniform standards for networking and data exchange in the automotive sector. A general overview of the process is depicted in Figure [Catena-X Standardization Process](./how-data-space-governance.md#how-do-we-standardize):
22+
Based on [Catena-X’s Intellectual Property(IP)-Regulations](https://catena-x.net/wp-content/uploads/2025/03/Catena-X_IP_Regelwerk_IP_Regulations.pdf) and in compliance with applicable antitrust law, the Catena-X standardization process aims to develop and implement uniform standards for networking and data exchange in the automotive sector. A general overview of the process is depicted in Figure [Catena-X Standardization Process](./how-data-space-governance.md#how-do-we-standardize):
2323

2424
![Catena-X Standardization Process](./assets/catena-x-standardization-process.png)
2525
*Catena-X Standardization Process*
@@ -194,7 +194,7 @@ A general overview of the process is depicted in Figure [Catena-X process for No
194194

195195
### Country Clearance List
196196

197-
The Catena-X association issues a [country clearance list](https://catena-x.net/fileadmin/user_upload/04_Einfuehren_und_umsetzen/Governance_Framework/Catena-X_-_Country_Clearance_list.pdf) that specifies countries, in which companies can be onboarded to the Catena-X data space. This list acts as mandatory guidance to all OSPs for registering participants in the Catena-X data space.
197+
The Catena-X association issues a [country clearance list](https://catenax-ev.github.io/docs/Jupiter/regulatory-framework/30000ft/country-clearance-list) that specifies countries, in which companies can be onboarded to the Catena-X data space. This list acts as mandatory guidance to all OSPs for registering participants in the Catena-X data space.
198198

199199
In the same document, the Catena-X association includes countries currently under clearance review. An onboarding of companies from this category is only possible after a due diligence check, followed by separate approval by the Catena-X association. A request for such a due diligence check can be requested by any OSP to the Catena-X association under [[email protected]](mailto:[email protected]).
200200

versioned_docs/version-Jupiter/operating-model/how-data-space-operations/how-data-space-operations.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ This chapter provides an overview of the key processes and compliance requiremen
77

88
## Onboarding Process
99

10-
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.
10+
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.
1111

1212
![Onboarding Process](./assets/onboarding-process.png)
1313
*Onboarding Process*
@@ -120,7 +120,7 @@ The figure shows a generic section of the value chain. The basic principle - one
120120

121121
Besides this implementation suppliers and customers have to agree on how the 1U1D-Rule applies to their specific contractual agreement and use case. For example, if there are agreements in place to handle directed parts or ad-hoc agreements to handle a critical supply situation, supply chain visibility may be extended.
122122

123-
The default standard for part relationships is defined in Catena-X Standards [CX-0126](../../standards/CX-0126-IndustryCorePartType/CX-0126-IndustryCorePartType.md) and [CX-0127](../../standards/CX-0127-IndustryCorePartInstance/CX-0127-IndustryCorePartInstance.md). An overarching explanation can be found in the [Tractus-X KITS](https://eclipse-tractusx.github.io/docs-kits/24.08/kits/Industry%20Core%20Kit/Business%20View%20Industry%20Core%20Kit).
123+
The default standard for part relationships is defined in Catena-X Standards [CX-0126](../../standards/CX-0126-IndustryCorePartType/CX-0126-IndustryCorePartType.md) and [CX-0127](../../standards/CX-0127-IndustryCorePartInstance/CX-0127-IndustryCorePartInstance.md). An overarching explanation can be found in the [Tractus-X KITS](https://eclipse-tractusx.github.io/docs-kits/category/industry-core-kit).
124124

125125
### Part-based visibility
126126

versioned_docs/version-Jupiter/operating-model/what-service-map/what-service-map.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -102,7 +102,7 @@ The Catena-X data space also enables secure and sovereign data exchange for indi
102102

103103
The exclusions do not prohibit the offering or integration of the Golden Record Service, but it is not required for the operation of a sandbox. The cleansing service of the Golden Record Service is not a mandatory services as this is only required for the testing of special use cases - the majority can also be tested without a cleansing service the Golden Record Service. This also makes it possible to provide a cost-effective offer, as no additional costs are incurred. The GXDCH is only relevant for the productive data space and is therefore only available to the CSP-B. Therefore, there can be no integration with the sandbox provider here. As the Self-Descriptions (SDs) are not required for testing the use cases there is no limitation.
104104

105-
As shown in the [role description](./../who-roles-in-the-catena-x-ecosystem/who-roles-in-the-catena-x-ecosystem.md#sandbox-provider) of the SP, the SP itself and the participants in the sandbox must be onboarded into the productive Catena-X data space via an OSP or CSP-B - see [onboarding](./../how-data-space-operations/how-data-space-operations.md#general-onboarding). The BPNs issued do not have to be used in the Sandbox, so no technical integration has to take place.
105+
As shown in the [role description](./../who-roles-in-the-catena-x-ecosystem/who-roles-in-the-catena-x-ecosystem.md#sandbox-provider) of the SP, the SP itself and the participants in the sandbox must be onboarded into the productive Catena-X data space via an OSP or CSP-B - see [onboarding](./../how-data-space-operations/how-data-space-operations.md#onboarding-process). The BPNs issued do not have to be used in the Sandbox, so no technical integration has to take place.
106106

107107
Catena-X Sandboxes offer participants the option to try out the network and its features while still using test data. On the one hand, they serve the purpose of offering a **Proof of Concept (POC) environment**, both for future Catena-X releases as well as for interested parties to “try out” Catena-X before migrating to the productive operating environment. On the other hand, they provide the foundation for more automated **Catena-X conformity assessment**. Catena-X Sandboxes will require certification in the future and are distinctly recognizable by an official Catena-X label.
108108

versioned_docs/version-Jupiter/operating-model/who-roles-in-the-catena-x-ecosystem/who-roles-in-the-catena-x-ecosystem.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -100,7 +100,7 @@ OSPs are responsible for deploying, operating, and maintaining onboarding servic
100100

101101
**Current Limitations:**
102102

103-
- The OSP currently covers only part of the registration process in the Catena-X data space. The currently available process is depicted in figure [General Onboarding Process](./../how-data-space-operations/how-data-space-operations.md#general-onboarding).
103+
- The OSP currently covers only part of the registration process in the Catena-X data space. The currently available process is depicted in figure [General Onboarding Process](./../how-data-space-operations/how-data-space-operations.md#onboarding-process).
104104
- Offboarding Processes Under Development: Comprehensive offboarding processes are currently in development to ensure that they are as robust as onboarding processes and will be included in future updates. Simple and manual offboarding processes are already available.
105105

106106
### Enablement Service Provider
@@ -199,7 +199,7 @@ solution). Alternatively, a DPC can certify and operate its own business applica
199199

200200
**Prerequisites:**
201201

202-
- A DPC **must** use certified enablement services or business applications. Alternatively, a DPC **must** certify its own enablement services and/or business applications by one of the CABs (as outlined in Chapter [Conformity Assessment](./../how-data-space-governance/how-data-space-governance.md#conformity-assessment)).
202+
- A DPC **must** use certified enablement services or business applications. Alternatively, a DPC **must** certify its own enablement services and/or business applications by one of the CABs (as outlined in Chapter [Conformity Assessment](./../how-data-space-governance/how-data-space-governance.md#conformity-assessment-and-certification)).
203203
- A DPC **must** accept and comply with the Catena-X regulatory framework during onboarding via one of the OSPs
204204

205205
**Current Limitations:**

0 commit comments

Comments
 (0)