diff --git a/docs-kits/Resiliency/DCM_Kit.mdx b/docs-kits/kits/Resiliency/DCM_Kit.mdx
similarity index 100%
rename from docs-kits/Resiliency/DCM_Kit.mdx
rename to docs-kits/kits/Resiliency/DCM_Kit.mdx
diff --git a/docs-kits/Resiliency/MP_Kit.md b/docs-kits/kits/Resiliency/MP_Kit.md
similarity index 100%
rename from docs-kits/Resiliency/MP_Kit.md
rename to docs-kits/kits/Resiliency/MP_Kit.md
diff --git a/docs-kits/Resiliency/MaaS.md b/docs-kits/kits/Resiliency/MaaS.md
similarity index 100%
rename from docs-kits/Resiliency/MaaS.md
rename to docs-kits/kits/Resiliency/MaaS.md
diff --git a/docs-kits/Resiliency/PURIS_Kit.md b/docs-kits/kits/Resiliency/PURIS_Kit.md
similarity index 100%
rename from docs-kits/Resiliency/PURIS_Kit.md
rename to docs-kits/kits/Resiliency/PURIS_Kit.md
diff --git a/docs-kits/Resiliency/resiliency.mdx b/docs-kits/kits/Resiliency/resiliency.mdx
similarity index 100%
rename from docs-kits/Resiliency/resiliency.mdx
rename to docs-kits/kits/Resiliency/resiliency.mdx
diff --git a/docs-kits/kits/tractusx-edc/CHANGELOG.md b/docs-kits/kits/tractusx-edc/CHANGELOG.md
index 8cb5dc3e4ef..7a2e25696cc 100644
--- a/docs-kits/kits/tractusx-edc/CHANGELOG.md
+++ b/docs-kits/kits/tractusx-edc/CHANGELOG.md
@@ -6,6 +6,13 @@
All notable changes to this Kit will be documented in this file.
+## [0.6.0] - 2023-10-31
+
+
Changed
+
+- restructuring of adoption view
+- new domain model, drawn with drawio
+
## [0.5.0] - 2023-08-09
Changed
diff --git a/docs-kits/kits/tractusx-edc/docs/kit/adoption-view/page_adoption-view.md b/docs-kits/kits/tractusx-edc/docs/kit/adoption-view/page_adoption-view.md
index 271ccbeff95..b98e02cc95d 100644
--- a/docs-kits/kits/tractusx-edc/docs/kit/adoption-view/page_adoption-view.md
+++ b/docs-kits/kits/tractusx-edc/docs/kit/adoption-view/page_adoption-view.md
@@ -13,24 +13,48 @@ The ConnectorKit provides a connector framework, based on the [Eclipse Dataspace
-Trust, interoperability and data sovereignty, these are the objectives and values for secure and sustainable peer-to-peer data exchange between organizations and companies. The claim is data sovereignty: Whoever makes data available retains control and decides individually who is involved in the data exchange, how, when, where and under what conditions.
+## Vision & Mission
-A corresponding concept was developed in the context of [Gaia-X][gaiax-url] and the [International Data Space Association][idsa-url]. The essential software component is the connector.
+### Vision
-With the [EDC][edc-url], a new central communication component was created, which implements the following architectural principles:
+Sharing data along the automotive supply chain adds great value for every participant. The key to such collaboration is trust in the involved partners and assurance that the shared data is not being misused. Within a few years, companies along the automotive value chain will share and exchange data with each other as a matter of course, without anyone fearing that their data will be misused while unlocking significant values for every party.
-- Simple, maintaining a small and efficient core with as few external dependencies as possible
-- Interoperable, independent of platforms and ecosystems
-- Decentralized, software components with the necessary capabilities for participating in a data room are located on the partners' side, data is only exchanged between the agreed points.
-- Data protection is more important than data sharing, data to be transmitted are fundamentally linked to policies via contracts; a transfer without a contract is not possible.
-- Separation of metadata and data enables high throughput rates for the actual data transfer.
-- Consistent semantics for the data is the basis for the consistency of digital value creation.
-- As far as possible, all processes, starting with determining the identity, through ensuring the contractually agreed regulations to data transmission, are automated.
-- Existing standards and protocols ([GAIA-X][gaiax-url] and [IDSA][idsa-url]) are used as far as possible.
+### Mission
+
+Collaboration needs trust. Within Catena-X trust is built on an open-source architecture and components designed to support full sovereignity.
+The Connector KIT provides the single source of information and technology to perform trustful data exchange within Catena-X. The Connector KIT bundles the interaction patterns, relevant standards, APIs, and reference implementations for developers.
+
+## Concept
+
+Trust, interoperability, and data sovereignty are the objectives and values for secure and sustainable peer-to-peer data exchange between organizations and companies. The claim is data sovereignty: Whoever provides data to the Data Space retains control and decides individually who is involved in the data exchange, how, when, where and under what conditions. A corresponding concept was developed in the context of [Gaia-X][gaiax-url] and the [International Data Space Association][idsa-url]. __The essential software component is the EDC.__
+
+With the [EDC][edc-url], a new communication component was introduced, which implements the following architectural principles:
+
+- Simple. Maintaining a small and efficient core with as few external dependencies as possible.
+- Interoperable. Independent of platforms and ecosystems.
+- Decentralized. Software components with the necessary capabilities for participating in a Data Space are located on the partners' side, data is only exchanged within agreed contracts.
+- Data protection is more important than data sharing. Data to be transmitted is fundamentally linked to policies via contracts; a transfer without a contract is not possible.
+- Separation of metadata and data. Enables high throughput rates for the actual data transfer.
+- Consistent semantics. Is the basis for interoperability and digital value creation.
+- Automation. As far as possible, all processes, starting with determining the identity, through ensuring the contractually agreed regulations to data transmission, are automated.
+- Standardization. Existing standards and protocols ([GAIA-X][gaiax-url] and [IDSA][idsa-url]) are used as far as possible.
+
+## Use Case
+
+The EDC is the enabling component for all use cases within Catena-X and the only component to execute the exchange of operational data to Data Space participants. The base use case is therfore the exchange of data between to partners. Value creation along the automotive value chain is tied to processing data in specific contexts. Within Catena-X exist 10 use cases companies can participate in. Active participation in given use cases always requires the use of an [EDC][edc-url]. Depending on the use case a participant chooses to participate in, further components will be required.
+
+- [Sustainability][sustainability-url]
+- [Traceability][traceability-url]
+- [Demand and Capacity Management][DCM-url]
+- [Predictive Unit Real-Time Information Service (PURIS)][PURIS-url]
+- [Business Partner Data Management][BPDM-url]
+- [Digital Product pass][digital-product-pass-url]
+
+## Business Architecture
The [EDC][edc-url] as a connector implements a framework agreement for sovereign, cross-organizational data exchange. The International Data Spaces Standard (IDS) and relevant principles in connection with [GAIA-X][gaiax-url] were implemented. The connector is designed to be extensible to support alternative protocols and to be integrated into different ecosystems.
-The objective is to set up a decentralized software component on the part of the respective partner, which bundles the skills required to participate in a data room and enables peer-to-peer connections between participants.
+The objective is to set up a decentralized software component on the part of the respective partner, which bundles the skills required to participate in a Data Space and enables peer-to-peer connections between participants.
The focus here is particularly on the data sovereignty of the independent companies.
The functionality required for this is bundled in the open-source project "Eclipse Dataspace Connector", to which members of the Eclipse Foundation contribute.
@@ -40,13 +64,106 @@ The main difference between the EDC and the previous connectors of the [IDSA][id
The architecture of the EDC combines various services that are necessary for the above principles:
-- An interface to the Identity Provider service, currently [IDSA][idsa-url]'s [Dynamic Attribute Provisioning System][daps-url]. This central service provides the identity and the corresponding authentication of the participants in the data exchange. (There is no authorization at this point). Decentralized solutions will also be supported in the future.
+- An interface to the Identity Provider service, currently the [Managed identity Wallet][miw-url]. This central service provides the identity and the corresponding authentication of the participants in the data exchange. Decentralized solutions will also be supported in the future, following [Gaia-X]'s[gaiax-url] principles and implementing self sovereign identity.
- The provision of possible offers (contract offering) which, on the one hand, stipulates the data offered and the associated terms of use (policies) in corresponding contracts.
- An interface for manual selection of data and associated contract offers.
- The actual data transfer via the data plane extension
- The connection of software systems on the customer and provider side
+## Additional Resources
+
+### Catena-X Standards
+
+The Connector KIT builds on the [Catena-X Standards][Catena-X-Standards-url]. Every data consumer and provider in Catena-X is required to comply with these standards. The [EDC][edc-url] builds on the following standards:
+
+- [CX - 0002 Digital Twins in Catena - X][CX0002]
+- [CX - 0003 BAMM Aspect Meta Model][CX0003]
+- [CX - 0008 Relevant standards for conformity assessments][CX0008]
+- [CX - 0018 Eclipse Data Space Connector (EDC)][CX0018]
+- [CX - 0044 ECLASS][CX044]
+- [CX - 0047 DCM Data Model Material Demand & Capacity Group][CX0047]
+- [CX - 0059 Triangle Behavioral Twin Endurance Predictor][CX0059]
+
+### Terminology
+
+The shown picture illustrates only a generic view of the Domain Model and is not intended to show all aspects of the project.
+
+
+
+#### Extensions
+
+There are different extenions for the Connector, e.g. for the Data Plane. This enables various tranfer modes like httpData or via blob-storage.
+
+#### Data Plane
+
+The Data Plane handles several forms of actual data exchange by utilizing various extensions.
+
+#### Control Plane
+
+The Control Plane handles meta data exchange with other components and Connectors, as well as transfer of access tokens
+
+#### Data Assets
+
+Data Sources (databases, files, cache information, etc.) are connected to the Connector and are represented by Data Assets. For each asset, a [`DataAddress`](#data-address) needs to be resolvable.
+
+#### Data address
+
+A data address is a pointer into the physical storage location where an asset will be stored.
+
+#### Policy Definition
+
+A standardized set of policies can be used to define actions regarding access to and usage of assets. These actions can be limited further by constraints (temporal or spatial) and duties ("e.g. deletion of the data after 30 days").
+
+#### Contract Definition
+
+By combining [`Assets`](#data asset) and Policies, Contracts for data offerings are defined. These Contracts need to be accepted by consuming participants (Connectors) for the data exchange to take place.
+
+#### Contract offer
+
+The contract offer is a representation of the [`ContractDefinition`](#contract-definition) for a specific consumer and serves as protocol for a data transfer object (DTO) for a particular contract negotiation. If a data consumer wants to conclude a binding data exchange contract based on the terms of a Data Offer, the data consumer can communicate such desire to the data provider by referencing to a specific Data Offer. This constitutes a binding offer by the data consumer. For now, the data consumer only has the option to accept all terms of a Data Offer (or not). The Data Exchange Process does not yet provide for the data consumer to make an offer that deviates from the terms of a Data Offer as set by the data provider.
+
+#### Contract negotiation
+
+A `ContractNegotiation` captures the current state of the negotiation of a contract (`ContractOffer` ->
+`ContractAgreement`) between two parties. This process is inherently asynchronous.
+
+#### Contract agreement
+
+A contract agreement represents the agreed-upon terms of access and usage of an asset's data between two data space
+participants, including a start and an end date and further relevant information.
+
+#### Transfer process
+
+After a successful contract negotiation, `DataRequests` can be sent from the consumer connector to the provider connector to initiate the data transfer. It references the requested [`Asset`](#data asset) and [`ContractAgreement`](#contract-agreement) as well as information about the [data destination](#data-address).
+
+Similar to the `ContractNegotiation`, this object captures the current state of a data transfer. This process is
+inherently asynchronous, so the `TransferProcess` objects are stored in a backing data store (`TransferProcessStore`).
+
+## Notice
+
+This work is licensed under the [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/legalcode).
+
+- SPDX-License-Identifier: CC-BY-4.0
+- SPDX-FileCopyrightText: 2023 sovity GmbH
+- SPDX-FileCopyrightText: 2023 msg systems AG
+- SPDX-FileCopyrightText: 2023 Mercedes-Benz Group AG
+- Source URL: [https://github.com/eclipse-tractusx/tractusx-edc](https://github.com/eclipse-tractusx/tractusx-edc)
+
[edc-url]: https://github.com/eclipse-edc/Connector
[gaiax-url]: https://www.data-infrastructure.eu/GAIAX/Navigation/EN/Home/home.html
[idsa-url]: https://internationaldataspaces.org/
-[daps-url]: https://www.dataspaces.fraunhofer.de/en/software/identity_provider.html
+[miw-url]: https://github.com/eclipse-tractusx/managed-identity-wallet
+[traceability-url]: https://github.com/eclipse-tractusx/traceability-foss
+[sustainability-url]: https://github.com/ChristopherWinterZF/pcf-exchange-kit/tree/featurebranch/devlopmentview
+[BPDM-url]: https://github.com/eclipse-tractusx/bpdm
+[DCM-url]: https://github.com/eclipse-tractusx/demand-capacity-mgmt/blob/main/README.md
+[PURIS-url]: https://github.com/eclipse-tractusx/puris
+[digital-product-pass-url]:https://github.com/eclipse-tractusx/digital-product-pass
+[Catena-X-Standards-url]:https://catena-x.net/de/standard-library
+[CX0002]:https://catena-x.net/fileadmin/user_upload/Standard-Bibliothek/Archiv/Update_Juli_23_R_3.2/CX-0002-DigitalTwinsInCatena-X-v.1.0.2.pdf
+[CX0003]:https://catena-x.net/fileadmin/user_upload/Standard-Bibliothek/Archiv/Update_Juli_23_R_3.2/CX-0003-SAMMSemanticAspectMetaModel-v.1.0.2.pdf
+[CX0008]:https://catena-x.net/fileadmin/user_upload/Standard-Bibliothek/Update_PDF_Maerz/6_Onboarding/CX_-_0008_Conformity_Assessment_PlatformCapabilityOnboarding_v_1.0.1.pdf
+[CX0018]:https://catena-x.net/fileadmin/user_upload/Standard-Bibliothek/Update_PDF_Maerz/3_Sovereign_Data_Exchange/CX_-_0018_EDC_PlatformCapabilitySovereignDataExchange_v_1.0.1.pdf
+[CX044]:https://catena-x.net/fileadmin/user_upload/Standard-Bibliothek/Archiv/Update_Juli_23_R_3.2/CX-0044-ECLASS-v1.0.2.pdf
+[CX0047]:https://catena-x.net/fileadmin/user_upload/Standard-Bibliothek/Archiv/Update_Juli_23_R_3.2/CX-0047-DemandCapacityManagementDataModels-v1.0.0.pdf
+[CX0059]:https://catena-x.net/fileadmin/user_upload/Standard-Bibliothek/Archiv/Update_Juli_23_R_3.2/CX-0059-TriangleBehavioralTwinEndurancePredictorService-v.1.0.0.pdf
diff --git a/docs-kits/kits/tractusx-edc/docs/kit/adoption-view/page_domain_model.md b/docs-kits/kits/tractusx-edc/docs/kit/adoption-view/page_domain_model.md
deleted file mode 100644
index 5143889f9e9..00000000000
--- a/docs-kits/kits/tractusx-edc/docs/kit/adoption-view/page_domain_model.md
+++ /dev/null
@@ -1,64 +0,0 @@
----
-id: Domain Model
-title: Domain Model
-description: 'Connector Kit'
-sidebar_position: 2
----
-
-
-
-> The shown picture illustrates only a generic view of the Domain Model and is not intended to show all aspects of the project.
-
-## Asset
-
-An asset represents data (databases, files, cache information, etc.) which should be published and shared between
-organizations. For each asset, a [`DataAddress`](#data-address) needs to be resolvable.
-
-## Data address
-
-A data address is a pointer into the physical storage location where an asset will be stored.
-
-## Contract
-
-A contract always contains one or more [`Assets`](#asset) and a single [`Policy`](#policy). The contract construct is
-used to define the arrangement between two parties ("consumer" and "provider"). Regarding this arrangement, the contract
-passes several stages which are explained below:
-
-### Contract definition
-
- Contract definitions associate a policy with assets. A `ContractDefinition` object contains an access policy, a contract
- policy, and an asset selector which links the contract to one or more assets.
-
-### Contract offer
-
- The contract offer is a dynamic representation of the [`ContractDefinition`](#contract-definition)
- for a specific consumer and serves as protocol's data transfer object (DTO) for a particular contract negotiation.
- Contract offers are not persisted and will be regenerated on every request. The connector acting as data provider will
- generate contract offers only for contract definitions dedicated to the organization or data space participant
- operating the requesting connector acting as data consumer. A contract offer is always related to a single asset of
- the `ContractDefinition` object (e.g. for a `ContractDefinition` containing three `Asset` objects, the connector will
- generate three `ContractOffer` objects).
-
-### Contract negotiation
-
- A `ContractNegotiation` captures the current state of the negotiation of a contract (`ContractOffer` ->
- `ContractAgreement`) between two parties. This process is inherently asynchronous.
-
-### Contract agreement
-
- A contract agreement represents the agreed-upon terms of access and usage of an asset's data between two data space
- participants, including a start and an end date and further relevant information.
-
-## Policy
-
-Contract policies represent permitted and prohibited actions over a certain asset. These actions can be limited further
-by constraints (temporal or spatial) and duties ("e.g. deletion of the data after 30 days").
-
-## Transfer process
-
-After a successful contract negotiation, a `DataRequest` is sent from a consumer connector to a provider connector to
-initiate the data transfer. It references the requested [`Asset`](#asset) and [`ContractAgreement`](#contract-agreement)
-as well as information about the [data destination](#data-address).
-
-Similar to the `ContractNegotiation`, this object captures the current state of a data transfer. This process is
-inherently asynchronous, so the `TransferProcess` objects are stored in a backing data store (`TransferProcessStore`).
diff --git a/docs-kits_versioned_docs/version-3.1.0/Resiliency/DCM_Kit.mdx b/docs-kits_versioned_docs/version-3.1.0/kits/Resiliency/DCM_Kit.mdx
similarity index 100%
rename from docs-kits_versioned_docs/version-3.1.0/Resiliency/DCM_Kit.mdx
rename to docs-kits_versioned_docs/version-3.1.0/kits/Resiliency/DCM_Kit.mdx
diff --git a/docs-kits_versioned_docs/version-3.1.0/Resiliency/MP_Kit.md b/docs-kits_versioned_docs/version-3.1.0/kits/Resiliency/MP_Kit.md
similarity index 100%
rename from docs-kits_versioned_docs/version-3.1.0/Resiliency/MP_Kit.md
rename to docs-kits_versioned_docs/version-3.1.0/kits/Resiliency/MP_Kit.md
diff --git a/docs-kits_versioned_docs/version-3.1.0/Resiliency/MaaS.md b/docs-kits_versioned_docs/version-3.1.0/kits/Resiliency/MaaS.md
similarity index 100%
rename from docs-kits_versioned_docs/version-3.1.0/Resiliency/MaaS.md
rename to docs-kits_versioned_docs/version-3.1.0/kits/Resiliency/MaaS.md
diff --git a/docs-kits_versioned_docs/version-3.1.0/Resiliency/OSim_Kit.md b/docs-kits_versioned_docs/version-3.1.0/kits/Resiliency/OSim_Kit.md
similarity index 100%
rename from docs-kits_versioned_docs/version-3.1.0/Resiliency/OSim_Kit.md
rename to docs-kits_versioned_docs/version-3.1.0/kits/Resiliency/OSim_Kit.md
diff --git a/docs-kits_versioned_docs/version-3.1.0/Resiliency/PURIS_Kit.md b/docs-kits_versioned_docs/version-3.1.0/kits/Resiliency/PURIS_Kit.md
similarity index 100%
rename from docs-kits_versioned_docs/version-3.1.0/Resiliency/PURIS_Kit.md
rename to docs-kits_versioned_docs/version-3.1.0/kits/Resiliency/PURIS_Kit.md
diff --git a/docs-kits_versioned_docs/version-3.1.0/Resiliency/resiliency.mdx b/docs-kits_versioned_docs/version-3.1.0/kits/Resiliency/resiliency.mdx
similarity index 100%
rename from docs-kits_versioned_docs/version-3.1.0/Resiliency/resiliency.mdx
rename to docs-kits_versioned_docs/version-3.1.0/kits/Resiliency/resiliency.mdx
diff --git a/docs-kits_versioned_sidebars/version-3.1.0-sidebars.json b/docs-kits_versioned_sidebars/version-3.1.0-sidebars.json
index 99daf3fd48f..288733a1c56 100644
--- a/docs-kits_versioned_sidebars/version-3.1.0-sidebars.json
+++ b/docs-kits_versioned_sidebars/version-3.1.0-sidebars.json
@@ -830,23 +830,20 @@
"dirName": "kits/Traceability Kit"
}
]
- }
-
- ],
- "Resiliency": [
+ },
{
"type": "category",
"label": "Resiliency",
"link": {
"type": "doc",
- "id": "Resiliency/resiliency"
+ "id": "kits/Resiliency/resiliency"
},
"items": [
- "Resiliency/DCM Kit",
- "Resiliency/maas",
- "Resiliency/OSIM",
- "Resiliency/PURIS",
- "Resiliency/mp kit"
+ "kits/Resiliency/DCM Kit",
+ "kits/Resiliency/maas",
+ "kits/Resiliency/OSIM",
+ "kits/Resiliency/PURIS",
+ "kits/Resiliency/mp kit"
]
}
]
diff --git a/docs/tutorials/CHANGELOG.md b/docs/tutorials/CHANGELOG.md
deleted file mode 100644
index bbb84f9ff96..00000000000
--- a/docs/tutorials/CHANGELOG.md
+++ /dev/null
@@ -1,18 +0,0 @@
-# Changelog
-
-## E2E Adopter Journey Tutorial
-
-All notable changes to this Tutorial will be documented in this file.
-
-## [0.1.0] - 2023-10-30
-
-### Added
-
-- Initial content structure
-- CHANGELOG.md
-- Provide data and consume data sections
-- Restrict data access section
-
-### Changed
-
-### Removed
diff --git a/docs/tutorials/e2e/boost/boost.md b/docs/tutorials/e2e/boost/boost.md
index e40c65a3a65..2c2b9e1ce91 100644
--- a/docs/tutorials/e2e/boost/boost.md
+++ b/docs/tutorials/e2e/boost/boost.md
@@ -4,3 +4,13 @@ sidebar_position: 5
---
In the `Boost Chapter`, you will configure and register your components so that they are discoverable in your local data space deployment. You will then take on the role of a data provider, build your first data pipeline, add your first `assets`, `policies` and create a `contract offer`` in the EDC. As a data consumer you will discover the data that you have previously created and initiate a data transfer. After completing this step, you have all the foundational knowledge you need to get started with active participation in a use-case.
+
+## Notice
+
+This work is licensed under the [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/legalcode).
+
+- SPDX-License-Identifier: CC-BY-4.0
+- SPDX-FileCopyrightText: 2023 sovity GmbH
+- SPDX-FileCopyrightText: 2023 SAP SE
+- SPDX-FileCopyrightText: 2023 msg systems AG
+- Source URL: [https://github.com/eclipse-tractusx/eclipse-tractusx.github.io](https://github.com/eclipse-tractusx/eclipse-tractusx.github.io)
diff --git a/docs/tutorials/e2e/boost/consumeData.md b/docs/tutorials/e2e/boost/consumeData.md
index 9fd60f43357..44d413f2d0e 100644
--- a/docs/tutorials/e2e/boost/consumeData.md
+++ b/docs/tutorials/e2e/boost/consumeData.md
@@ -5,6 +5,16 @@ sidebar_position: 3
---
**NOTE:**
-This chapter is still work in progress. Check back layer!
+This chapter is still work in progress. Check back later!
---
+
+## Notice
+
+This work is licensed under the [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/legalcode).
+
+- SPDX-License-Identifier: CC-BY-4.0
+- SPDX-FileCopyrightText: 2023 sovity GmbH
+- SPDX-FileCopyrightText: 2023 SAP SE
+- SPDX-FileCopyrightText: 2023 msg systems AG
+- Source URL: [https://github.com/eclipse-tractusx/eclipse-tractusx.github.io](https://github.com/eclipse-tractusx/eclipse-tractusx.github.io)
diff --git a/docs/tutorials/e2e/boost/provideData.md b/docs/tutorials/e2e/boost/provideData.md
index 031d036c5ba..47a0ec480d7 100644
--- a/docs/tutorials/e2e/boost/provideData.md
+++ b/docs/tutorials/e2e/boost/provideData.md
@@ -3,15 +3,6 @@ title: Provide data
sidebar_position: 2
---
----
-**NOTE:**
-This chapter is still work in progress. Check back later!
-
-- Register digital twin (aspect)
-- Register EDC Asset
-
----
-
## Create first data asset
In this step we will focus on inserting data into our provider connector (Alice) using
diff --git a/docs/tutorials/e2e/boost/restrictData.md b/docs/tutorials/e2e/boost/restrictData.md
index e4c6451237f..8d4a013fc3f 100644
--- a/docs/tutorials/e2e/boost/restrictData.md
+++ b/docs/tutorials/e2e/boost/restrictData.md
@@ -3,12 +3,6 @@ title: Restricting users from accessing an asset
sidebar_position: 4
---
----
-**NOTE:**
-This chapter is still work in progress. Check back layer!
-
----
-
## Create an asset
Bob will once again be the data provider and Alice is interested in Bob’s data assets. Bob, as a data provider, creates an asset.
diff --git a/docs/tutorials/e2e/connect/.runSingleTutorials.md b/docs/tutorials/e2e/connect/.runSingleTutorials.md
deleted file mode 100644
index c81f8310671..00000000000
--- a/docs/tutorials/e2e/connect/.runSingleTutorials.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Run single tutorials
-sidebar_position: 3
----
-
----
-**NOTE:**
-This chapter is still work in progress. Check back layer!
-
----
diff --git a/docs/tutorials/e2e/connect/connect.md b/docs/tutorials/e2e/connect/connect.md
index f79701e86da..d1919eb9dca 100644
--- a/docs/tutorials/e2e/connect/connect.md
+++ b/docs/tutorials/e2e/connect/connect.md
@@ -21,3 +21,13 @@ By performing this tutorial a data space will be set up including the following
- 1 Managed Identity Wallet. The Managed Identity Wallet (MIW) service is a central component storing technical identities. Connectors can request the identity, including properties, in order to take decisions if a contract-offer will be made, a contract agreement will be negotiated, or a data-exchange will be processed.
- 1 Keycloak instance. Keycloak is used for Identiy and Access Management of technical users.
- 1 Postgres data base. A data base building the foundation for the MXD setup.
+
+## Notice
+
+This work is licensed under the [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/legalcode).
+
+- SPDX-License-Identifier: CC-BY-4.0
+- SPDX-FileCopyrightText: 2023 sovity GmbH
+- SPDX-FileCopyrightText: 2023 SAP SE
+- SPDX-FileCopyrightText: 2023 msg systems AG
+- Source URL: [https://github.com/eclipse-tractusx/eclipse-tractusx.github.io](https://github.com/eclipse-tractusx/eclipse-tractusx.github.io)
diff --git a/docs/tutorials/e2e/connect/deployComponents.md b/docs/tutorials/e2e/connect/deployComponents.md
index a58fe2a6bf1..a4aa0f6f838 100644
--- a/docs/tutorials/e2e/connect/deployComponents.md
+++ b/docs/tutorials/e2e/connect/deployComponents.md
@@ -3,12 +3,6 @@ title: Deploy components
sidebar_position: 2
---
----
-**NOTE:**
-This chapter is still work in progress. Check back layer!
-
----
-
The "MXD" dataspace initially consists of several components: `Alice` and `Bob` (two Tractus-X EDC connectors),
a Vault instance each, a Postgres database, a Managed Identity Wallet app, a Keycloak instance. `Alice` and `Bob` will
be our dataspace participants. Each of them stores their secrets in their respective vault instances, and there is a
diff --git a/docs/tutorials/e2e/connect/prepareInfrastructure.md b/docs/tutorials/e2e/connect/prepareInfrastructure.md
index 4b44629880e..e09702a9ee4 100644
--- a/docs/tutorials/e2e/connect/prepareInfrastructure.md
+++ b/docs/tutorials/e2e/connect/prepareInfrastructure.md
@@ -3,12 +3,6 @@ title: Prepare the infrastructure
sidebar_position: 1
---
----
-**NOTE:**
-This chapter is still work in progress. Check back later!
-
----
-
## Prerequisites
In order to run the MXD on your local machine, please make sure the following
diff --git a/docs/tutorials/e2e/inform/.deepDives.md b/docs/tutorials/e2e/inform/.deepDives.md
deleted file mode 100644
index 6be821ef224..00000000000
--- a/docs/tutorials/e2e/inform/.deepDives.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Deep dive into concepts
-sidebar_position: 4
----
-
----
-**NOTE:**
-This chapter is still work in progress. Check back later!
-
----
diff --git a/docs/tutorials/e2e/inform/.techAssessment.md b/docs/tutorials/e2e/inform/.techAssessment.md
deleted file mode 100644
index 3e0f1927060..00000000000
--- a/docs/tutorials/e2e/inform/.techAssessment.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Execute the tech assessment
-sidebar_position: 3
----
-
----
-**NOTE:**
-This chapter is still work in progress. Check back layer!
-
----
diff --git a/docs/tutorials/e2e/inform/architecture.md b/docs/tutorials/e2e/inform/architecture.md
index a8f5e25f4ed..876a7592bef 100644
--- a/docs/tutorials/e2e/inform/architecture.md
+++ b/docs/tutorials/e2e/inform/architecture.md
@@ -3,12 +3,6 @@ title: Understand the architecture
sidebar_position: 2
---
----
-**NOTE:**
-This chapter is still work in progress. Check back layer!
-
----
-
If you are interested more in buying services, please get in contact with a operating company.
This section is for the makerr, which are intereste in deploying the services in their own it landscape.
@@ -150,3 +144,13 @@ Rel(SystemPortal, SystemEDCA, "configure BPN")
- Architecture principles in Scope of the Journey or Catena-X
- Data Sovereignty
- Interoperability
+
+## Notice
+
+This work is licensed under the [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/legalcode).
+
+- SPDX-License-Identifier: CC-BY-4.0
+- SPDX-FileCopyrightText: 2023 sovity GmbH
+- SPDX-FileCopyrightText: 2023 SAP SE
+- SPDX-FileCopyrightText: 2023 msg systems AG
+- Source URL: [https://github.com/eclipse-tractusx/eclipse-tractusx.github.io](https://github.com/eclipse-tractusx/eclipse-tractusx.github.io)
diff --git a/docs/tutorials/e2e/inform/inform.md b/docs/tutorials/e2e/inform/inform.md
index 57f924ec23b..64ca6b896c0 100644
--- a/docs/tutorials/e2e/inform/inform.md
+++ b/docs/tutorials/e2e/inform/inform.md
@@ -4,3 +4,13 @@ sidebar_position: 3
---
The `Inform Chapter` shall give a you a first overview over all relevant Catena-X concepts and components and how they interrelate. Starting with references to high-level onboarding information and an architecture overview, this chapter finishes with a list of documents to deep dive into the various technical components.
+
+## Notice
+
+This work is licensed under the [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/legalcode).
+
+- SPDX-License-Identifier: CC-BY-4.0
+- SPDX-FileCopyrightText: 2023 sovity GmbH
+- SPDX-FileCopyrightText: 2023 SAP SE
+- SPDX-FileCopyrightText: 2023 msg systems AG
+- Source URL: [https://github.com/eclipse-tractusx/eclipse-tractusx.github.io](https://github.com/eclipse-tractusx/eclipse-tractusx.github.io)
diff --git a/docs/tutorials/e2e/inform/onboardingMaterial.md b/docs/tutorials/e2e/inform/onboardingMaterial.md
index 014d8d7f9f8..48cc88f1eee 100644
--- a/docs/tutorials/e2e/inform/onboardingMaterial.md
+++ b/docs/tutorials/e2e/inform/onboardingMaterial.md
@@ -6,49 +6,73 @@ sidebar_position: 1
Welcome to this first step of the tutorial. As a developer, you most likely don't want to become an expert on all legal, organizational or business related Catena-X topics.
Nevertheless, it makes sense to familiarize yourself with some of the high-level concepts of Catena-X, before you proceed with the architecture.
-*Important*: To complete this tutorial you will **not** need to read through all the information provided under "further reading".
+:::tip
+
+To complete this tutorial you will **not** need to read through all the information provided under "further reading".
+
+:::
## 1. Catena-X
Catena-X is an open, secure, and standardized data ecosystem for the automotive industry. It is a collaborative initiative of automotive manufacturers, suppliers, and other stakeholders from across the value chain. Catena-X aims to enable the secure and efficient exchange of data across the entire value chain, from the development of new vehicles to the end-of-life recycling of components.
-> Further reading:
->
-> - More information on the Catena-X initiative can be found at the visions and goals section of the association homepage ().
+:::note
+
+More information on the Catena-X initiative can be found at the visions and goals section of the association homepage ().
+
+:::
## 2. Use-Cases
Catena-X is organized around ten initial use-cases. If your company decided to become part of Catena-X, it has chosen at least one use-case it want's to benefit from. Participation in a use-case usually includes the provisioning of data according to a shared semantic and standardized technology stack that shall enable interoperability and data sovereignty.
-> Further reading:
->
-> - The list of the ten initial use-cases as well as a description of each of them can be found here:
+:::note
+
+The list of the ten initial use-cases as well as a description of each of them can be found here:
+
+:::
## 3. The Data Space
To enable the use-cases, Catena-X builds a decentral data space. In a data space, data is directly exchanged between data provider and data consumer, without an intermediary. A data space requires data providers and consumers to use certain components either as managed services or as self-hosted. Furthermore, "core components" are needed within the network to ensure Identity & Trust, provide Data Discovery mechanisms or a Marketplace to find and purchase business applications that can be used to consume the data and generate value.
-> Further reading:
->
-> - For an in depth description of data spaces and the conceptual model behind Catena-X, read the Industrial Data Spaces Association (IDSA) Reference Architecture Model 4.0:
-> - The Catena-X Operating Whitepaper describes how the Catena-X data space is operated:
+:::note
+
+For an in depth description of data spaces and the conceptual model behind Catena-X, read the Industrial Data Spaces Association (IDSA) Reference Architecture Model 4.0:
+The Catena-X Operating Whitepaper describes how the Catena-X data space is operated:
+
+:::
## 4. The Onboarding Journey
Your task to setup the technical components is part of a larger onboarding journey that also includes a registration in the network, a use-case selection, setting up a data governance structure and engagement of the various business departments. The onboarding journey varies depending on your companies decision on how to participate in which use-cases. As you've already read, in case your company only intends to buy a fully managed SAAS business application, you won't need to operate the Catena-X components yourself.
The Catena-X association provides extensive onboarding material such as an onboarding guide or an onboarding status tracker. Both can be found on the association homepage.
->Further reading:
->
-> - For an in-depth understanding of the onboarding process, it can be helpful to read the Onboarding Guide () and especially the Chapter "IT Specialist".
-> - The "Internal Company Onboarding Tracker" provides a checklist for all onboarding steps and can also be found via the link above.
+:::note
+
+For an in-depth understanding of the onboarding process, it can be helpful to read the Onboarding Guide () and especially the Chapter "IT Specialist".
+The "Internal Company Onboarding Tracker" provides a checklist for all onboarding steps and can also be found via the link above.
+
+:::
## 5. Backend Integration
Setting up all technical components is only the first step towards active participation in Catena-X. To be able to send and receive data and participate in use-cases, the backend systems from/to where data is transferred must be connected. Those backend systems can be existing business applications, a data lake or data warehouses. Backend Integration also includes typical ETL tasks, such as adapting data formats to the Catena-X semantic.
-> Further reading:
->
-> - The data integration pattern guide gives an overview over the tasks and challenges associated with backend integration: <>
+:::note
+
+The data integration pattern guide gives an overview over the tasks and challenges associated with backend integration: <>
+
+:::
In the next chapter, you will learn about the Catena-X architecture, and how some of the most important technical components work together.
+
+## Notice
+
+This work is licensed under the [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/legalcode).
+
+- SPDX-License-Identifier: CC-BY-4.0
+- SPDX-FileCopyrightText: 2023 sovity GmbH
+- SPDX-FileCopyrightText: 2023 SAP SE
+- SPDX-FileCopyrightText: 2023 msg systems AG
+- Source URL: [https://github.com/eclipse-tractusx/eclipse-tractusx.github.io](https://github.com/eclipse-tractusx/eclipse-tractusx.github.io)
diff --git a/docs/tutorials/e2e/prerequisites/prerequisites.md b/docs/tutorials/e2e/prerequisites/prerequisites.md
index 00e57e54408..7daf9aa732c 100644
--- a/docs/tutorials/e2e/prerequisites/prerequisites.md
+++ b/docs/tutorials/e2e/prerequisites/prerequisites.md
@@ -8,8 +8,12 @@ sidebar_position: 1
The components and tools that are described here are to be understood as a proposal from Catena-X and not as standards that must be used. Using the proposed software stack of this tutorial will make it easier to complete it. Nevertheless, if your company policy requires e.g. the use of open stack, or you can't use docker containers or kubernetes, the Catena-X components will also work, you might just need a little extra effort.
+:::info
+
You can either complete the tutorial in a cloud space (e.g. AWS or Azure) or locally. If you choose to run the tutorial locally, make sure that your machine fulfils the minimal performance requirements.
+:::
+
## Required Skills and Technologies
AAs mentioned in the introduction, no preliminary knowledge about Catena-X is required. However, to complete the tutorial you will have to work with the following tech stack. A basic understanding of those technologies is advised.
@@ -88,3 +92,13 @@ You may need the support of your local IT department. Once you are confident to
TODO: Add list s:
- Ports to be open
+
+## Notice
+
+This work is licensed under the [CC-BY-4.0](https://creativecommons.org/licenses/by/4.0/legalcode).
+
+- SPDX-License-Identifier: CC-BY-4.0
+- SPDX-FileCopyrightText: 2023 sovity GmbH
+- SPDX-FileCopyrightText: 2023 SAP SE
+- SPDX-FileCopyrightText: 2023 msg systems AG
+- Source URL: [https://github.com/eclipse-tractusx/eclipse-tractusx.github.io](https://github.com/eclipse-tractusx/eclipse-tractusx.github.io)
diff --git a/docusaurus.config.js b/docusaurus.config.js
index 15bc91532c7..5b49d086439 100644
--- a/docusaurus.config.js
+++ b/docusaurus.config.js
@@ -353,7 +353,7 @@ const config = {
label: 'Traceability',
},
{
- to: 'docs-kits/next/Resiliency/',
+ to: 'docs-kits/next/kits/Resiliency/',
label: 'Upcoming KITs',
}
],
diff --git a/sidebarsDocsKits.js b/sidebarsDocsKits.js
index 0d291b51edd..592115986cd 100644
--- a/sidebarsDocsKits.js
+++ b/sidebarsDocsKits.js
@@ -108,7 +108,6 @@ const sidebars = {
collapsed: true,
items: [
'kits/tractusx-edc/docs/README',
- 'kits/tractusx-edc/docs/kit/adoption-view/Domain Model',
{
type: 'category',
label: 'openAPI',
@@ -464,22 +463,20 @@ const sidebars = {
},
],
},
- ],
- Resiliency: [
{
type: 'category',
label: 'Resiliency',
link: {
type: 'doc',
- id: 'Resiliency/resiliency'
+ id: 'kits/Resiliency/resiliency'
},
items: [
- 'Resiliency/DCM Kit',
- 'Resiliency/maas',
- 'Resiliency/PURIS',
- 'Resiliency/mp kit',
+ 'kits/Resiliency/DCM Kit',
+ 'kits/Resiliency/maas',
+ 'kits/Resiliency/PURIS',
+ 'kits/Resiliency/mp kit',
]
},
- ],
+ ]
};
module.exports = sidebars;
\ No newline at end of file
diff --git a/static/img/domain_model.drawio.svg b/static/img/domain_model.drawio.svg
new file mode 100644
index 00000000000..e375d904956
--- /dev/null
+++ b/static/img/domain_model.drawio.svg
@@ -0,0 +1,4 @@
+
+
+
+
\ No newline at end of file
diff --git a/utils/previewKits.js b/utils/previewKits.js
index 05da43497bc..31326b35f67 100644
--- a/utils/previewKits.js
+++ b/utils/previewKits.js
@@ -9,22 +9,22 @@ export const previewKits = [
{
id: 1,
img: DCM_Kit,
- pageRoute: "/docs-kits/Resiliency/DCM%20Kit"
+ pageRoute: "/docs-kits/kits/Resiliency/DCM%20Kit"
},
{
id: 2,
img: Maas_Kit,
- pageRoute: "/docs-kits/Resiliency/maas"
+ pageRoute: "/docs-kits/kits/Resiliency/maas"
},
{
id: 3,
img: PURIS_Kit,
- pageRoute: "/docs-kits/Resiliency/PURIS"
+ pageRoute: "/docs-kits/kits/Resiliency/PURIS"
},
{
id: 4,
img: MP_Kit,
- pageRoute: "/docs-kits/Resiliency/mp%20kit"
+ pageRoute: "/docs-kits/kits/Resiliency/mp%20kit"
},
{
id: 5,
diff --git a/utils/resiliencyItems.js b/utils/resiliencyItems.js
index 83d813cbee8..dd1c25d9369 100644
--- a/utils/resiliencyItems.js
+++ b/utils/resiliencyItems.js
@@ -8,12 +8,12 @@ export const resiliencyItems = [
{
id: 1,
img: DCM_Kit,
- pageRoute: "/docs-kits/Resiliency/DCM%20Kit"
+ pageRoute: "/docs-kits/kits/Resiliency/DCM%20Kit"
},
{
id: 2,
img: Maas_Kit,
- pageRoute: "/docs-kits/Resiliency/maas"
+ pageRoute: "/docs-kits/kits/Resiliency/maas"
},
{
id: 3,
@@ -23,11 +23,11 @@ export const resiliencyItems = [
{
id: 4,
img: PURIS_Kit,
- pageRoute: "/docs-kits/Resiliency/PURIS"
+ pageRoute: "/docs-kits/kits/Resiliency/PURIS"
},
{
id: 5,
img: MP_Kit,
- pageRoute: "/docs-kits/Resiliency/mp%20kit"
+ pageRoute: "/docs-kits/kits/Resiliency/mp%20kit"
},
]