diff --git a/docs/regulatory-framework/10000ft/data-exchange-contracts.md b/docs/regulatory-framework/10000ft/data-exchange-contracts.md index 998fbd937..a7cdab60c 100644 --- a/docs/regulatory-framework/10000ft/data-exchange-contracts.md +++ b/docs/regulatory-framework/10000ft/data-exchange-contracts.md @@ -36,7 +36,7 @@ Data providers & data consumer have the option of concluding bilateral contracts ![RC Process](./assets/data-exchange-process.png) -Illustration 1: RC Process with the example of an Eclipse Data Space Connector (EDC). Source: [Catena-X Operating Model](../../operating-model/why-introduction/why-introduction.md) +Illustration 1: RC Process with the example of an Eclipse Data Space Connector (EDC). Source: [Catena-X Operating Model](./../../operating-model/why-introduction/) ### 2. EXECUTIVE SUMMARY: CONCLUDING AND PERFORMING DATA EXCHANGE CONTRACTS VIA REGISTERED CONNECTORS diff --git a/docs/regulatory-framework/30000ft/country-clearance-list.md b/docs/regulatory-framework/30000ft/country-clearance-list.md index 569819ac2..a863a08cf 100644 --- a/docs/regulatory-framework/30000ft/country-clearance-list.md +++ b/docs/regulatory-framework/30000ft/country-clearance-list.md @@ -33,6 +33,7 @@ pagination_next: null | Italy | IT | | Japan | JP | | Latvia | LV | +| Liechtenstein | LIE | | Lithuania | LT | | Luxembourg | LU | | Malaysia | MY | @@ -113,4 +114,4 @@ pagination_next: null | Ukraine | UA | | United Arab Emirates | AE | | Uruguay | UY | -| Vanuatu | VU +| Vanuatu | VU | diff --git a/docs/regulatory-framework/changelog.md b/docs/regulatory-framework/changelog.md index a16953e6b..c8371c1af 100644 --- a/docs/regulatory-framework/changelog.md +++ b/docs/regulatory-framework/changelog.md @@ -6,6 +6,13 @@ sidebar_class_name: separator-top The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/). +## [2.0.1] + +### Added + +- Catena-X: Country Clearance List + - add "Liechtenstein" to "Allow List" + ## [2.0.0] ### Added diff --git a/docs/regulatory-framework/governance-framework.md b/docs/regulatory-framework/governance-framework.md index 43c598e50..d2977e8f9 100644 --- a/docs/regulatory-framework/governance-framework.md +++ b/docs/regulatory-framework/governance-framework.md @@ -22,11 +22,11 @@ To easily grasp the layers of our Governance Framework, think of flight level as At this level, the governance framework is defined by the Catena-X Association and the basic principles of the data ecosystem are outlined. Compliance is mandatory for all participants in the data space. There are several normative documents to consider. -The first is the [operating model](../operating-model/why-introduction/why-introduction.md). The operating model lays the foundation and is the pre-requisite for further standardization, certification, implementation, and operations of software components and partners in the Catena-X data space. The operating model is continuously updated to reflect the evolution of business and regulatory requirements, as well as emerging technologies. +The first is the [operating model](./../operating-model/why-introduction). The operating model lays the foundation and is the pre-requisite for further standardization, certification, implementation, and operations of software components and partners in the Catena-X data space. The operating model is continuously updated to reflect the evolution of business and regulatory requirements, as well as emerging technologies. -The ["10 Golden Rules"](../regulatory-framework/30000ft/ten-golden-rules.md) document, which outlines the basic principles of the data ecosystem, is published by the Catena-X association and provides clear guidelines for necessary specifications at lower levels. It also specifies how far a technical standard can go. The agreement between the CSPs and participants (e.g., data providers and data consumers) is established during onboarding. +The ["10 Golden Rules"](./30000ft/ten-golden-rules) document, which outlines the basic principles of the data ecosystem, is published by the Catena-X association and provides clear guidelines for necessary specifications at lower levels. It also specifies how far a technical standard can go. The agreement between the CSPs and participants (e.g., data providers and data consumers) is established during onboarding. -Furthermore, the [Country Clearance List](../regulatory-framework/30000ft/country-clearance-list.md) must be observed, which shows the countries for which onboarding is possible without restrictions and the countries for which onboarding is possible after a due diligence check. +Furthermore, the [Country Clearance List](./30000ft/country-clearance-list) must be observed, which shows the countries for which onboarding is possible without restrictions and the countries for which onboarding is possible after a due diligence check. ## 20,000ft - Use Case Level diff --git a/versioned_docs/version-Jupiter/regulatory-framework/10000ft/data-exchange-contracts.md b/versioned_docs/version-Jupiter/regulatory-framework/10000ft/data-exchange-contracts.md index 998fbd937..a7cdab60c 100644 --- a/versioned_docs/version-Jupiter/regulatory-framework/10000ft/data-exchange-contracts.md +++ b/versioned_docs/version-Jupiter/regulatory-framework/10000ft/data-exchange-contracts.md @@ -36,7 +36,7 @@ Data providers & data consumer have the option of concluding bilateral contracts ![RC Process](./assets/data-exchange-process.png) -Illustration 1: RC Process with the example of an Eclipse Data Space Connector (EDC). Source: [Catena-X Operating Model](../../operating-model/why-introduction/why-introduction.md) +Illustration 1: RC Process with the example of an Eclipse Data Space Connector (EDC). Source: [Catena-X Operating Model](./../../operating-model/why-introduction/) ### 2. EXECUTIVE SUMMARY: CONCLUDING AND PERFORMING DATA EXCHANGE CONTRACTS VIA REGISTERED CONNECTORS diff --git a/versioned_docs/version-Jupiter/regulatory-framework/30000ft/country-clearance-list.md b/versioned_docs/version-Jupiter/regulatory-framework/30000ft/country-clearance-list.md index 569819ac2..a863a08cf 100644 --- a/versioned_docs/version-Jupiter/regulatory-framework/30000ft/country-clearance-list.md +++ b/versioned_docs/version-Jupiter/regulatory-framework/30000ft/country-clearance-list.md @@ -33,6 +33,7 @@ pagination_next: null | Italy | IT | | Japan | JP | | Latvia | LV | +| Liechtenstein | LIE | | Lithuania | LT | | Luxembourg | LU | | Malaysia | MY | @@ -113,4 +114,4 @@ pagination_next: null | Ukraine | UA | | United Arab Emirates | AE | | Uruguay | UY | -| Vanuatu | VU +| Vanuatu | VU | diff --git a/versioned_docs/version-Jupiter/regulatory-framework/changelog.md b/versioned_docs/version-Jupiter/regulatory-framework/changelog.md index a16953e6b..c8371c1af 100644 --- a/versioned_docs/version-Jupiter/regulatory-framework/changelog.md +++ b/versioned_docs/version-Jupiter/regulatory-framework/changelog.md @@ -6,6 +6,13 @@ sidebar_class_name: separator-top The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/). +## [2.0.1] + +### Added + +- Catena-X: Country Clearance List + - add "Liechtenstein" to "Allow List" + ## [2.0.0] ### Added diff --git a/versioned_docs/version-Jupiter/regulatory-framework/governance-framework.md b/versioned_docs/version-Jupiter/regulatory-framework/governance-framework.md index 43c598e50..e41e57989 100644 --- a/versioned_docs/version-Jupiter/regulatory-framework/governance-framework.md +++ b/versioned_docs/version-Jupiter/regulatory-framework/governance-framework.md @@ -22,11 +22,11 @@ To easily grasp the layers of our Governance Framework, think of flight level as At this level, the governance framework is defined by the Catena-X Association and the basic principles of the data ecosystem are outlined. Compliance is mandatory for all participants in the data space. There are several normative documents to consider. -The first is the [operating model](../operating-model/why-introduction/why-introduction.md). The operating model lays the foundation and is the pre-requisite for further standardization, certification, implementation, and operations of software components and partners in the Catena-X data space. The operating model is continuously updated to reflect the evolution of business and regulatory requirements, as well as emerging technologies. +The first is the [operating model](./../operating-model/why-introduction). The operating model lays the foundation and is the pre-requisite for further standardization, certification, implementation, and operations of software components and partners in the Catena-X data space. The operating model is continuously updated to reflect the evolution of business and regulatory requirements, as well as emerging technologies. -The ["10 Golden Rules"](../regulatory-framework/30000ft/ten-golden-rules.md) document, which outlines the basic principles of the data ecosystem, is published by the Catena-X association and provides clear guidelines for necessary specifications at lower levels. It also specifies how far a technical standard can go. The agreement between the CSPs and participants (e.g., data providers and data consumers) is established during onboarding. +The ["10 Golden Rules"](./../regulatory-framework/30000ft/ten-golden-rules) document, which outlines the basic principles of the data ecosystem, is published by the Catena-X association and provides clear guidelines for necessary specifications at lower levels. It also specifies how far a technical standard can go. The agreement between the CSPs and participants (e.g., data providers and data consumers) is established during onboarding. -Furthermore, the [Country Clearance List](../regulatory-framework/30000ft/country-clearance-list.md) must be observed, which shows the countries for which onboarding is possible without restrictions and the countries for which onboarding is possible after a due diligence check. +Furthermore, the [Country Clearance List](./../regulatory-framework/30000ft/country-clearance-list) must be observed, which shows the countries for which onboarding is possible without restrictions and the countries for which onboarding is possible after a due diligence check. ## 20,000ft - Use Case Level